Skip to content
Moss
Esc
navigateopen⌘Jpreview
On this page

Privacy Policy

How Moss handles practice data and limited technical diagnostics.

Effective 16 July 2026

Moss keeps your meditation practice on your device. We collect only technical logs, crash reports, diagnostics, and performance data needed to understand app reliability.

Who this policy covers

This policy applies to the Moss meditation app for iOS and Android, published by Adishwar Rishi. Moss does not require an account and does not sell products, show advertising, or use advertising trackers.

Practice data stored on your device

Your meditation history, active session, schedule, reminders, preferences, and optional reflections are stored locally on your device. We do not receive this practice data. You can delete it from the Privacy & Data screen in Moss or by uninstalling the app.

Technical data we collect

Moss uses observability services, including EAS Observe provided by Expo (650 Industries, Inc.), to collect logs, crash reports, diagnostics, and performance telemetry. We may also use a specialist crash-reporting provider such as Sentry. The technical data these services process may include:

  • startup, rendering, responsiveness, and bundle-loading timings;
  • crash reports, stack traces, error messages, and technical logs generated by the app;
  • device model, operating-system version, app version, update channel, and production environment;
  • country-level location used to understand performance across general regions; and
  • an anonymous identifier unique to this installation of Moss.

The installation identifier is not linked to an account or identity and resets when Moss is uninstalled and reinstalled. We configure our telemetry so that technical logs should not contain meditation history, session durations, reminders, reflections, names, email addresses, contacts, or precise location. We do not intentionally send those details or custom product-analytics events to our observability providers.

How we use and disclose technical data

We use technical data only to investigate crashes and errors, diagnose reliability issues, measure performance, and improve Moss. Expo and any enabled crash-reporting provider process this data as our service providers. We do not sell it, use it for advertising, or share it with data brokers. We may disclose information when required by law or when necessary to protect users, Moss, or the public.

Retention and security

We retain technical data only for as long as reasonably necessary to operate and improve Moss, subject to the retention controls and legal obligations of our service providers. Expo states that EAS Observe metric data is retained for at least 60 days. We limit access to telemetry to people who need it to maintain Moss and use encrypted network connections when transmitting it. No method of storage or transmission can be guaranteed completely secure.

Your choices and requests

You can delete locally stored Moss data at any time from the app. Uninstalling Moss stops future telemetry and resets its anonymous installation identifier. For questions or requests concerning telemetry, contact us at the address below. Because Moss has no accounts and does not collect identity data, we may need information from you to determine whether a telemetry record can be identified and acted upon.

Children and teens

Moss is a general meditation app suitable for teens and adults. It is not directed to children under 13, and we do not knowingly collect personal information from children.

Changes to this policy

We may update this policy as Moss or its service providers change. We will publish the updated policy here and revise the effective date above.

Contact

Email adishwar.rishi+moss-support@gmail.com with privacy questions or requests.

You can learn more about EAS Observe in Expo’s product documentation and review Expo’s privacy policy. If Sentry is enabled for crash reporting, its data handling is described in Sentry’s privacy policy.

Was this page helpful?