3-2-1 Meditate

Privacy policy

Last updated: October 2, 2026

What 3-2-1 Meditate does

3-2-1 Meditate provides guided audio practices for general wellness. Listening does not require an account. Downloaded audio, playback state and a cached purchase entitlement may be stored on your device.

First-party usage measurement

The app sends events such as app opens, practice starts and completions, and catalog refreshes to our service using a random app-install identifier. Events may include the practice identifier, app version and platform. In builds with the welcome guide, we also measure numbered welcome steps, completion and opening a practice from the guide. Goal and time preferences stay on your device and are not included in these events; opening a practice is not proof of playback. The guide stores progress locally so you can resume or replay it. Resetting the analytics identity in the app changes the identifier used for future events; it does not delete events already received.

The web player measures visits, play attempts, audio readiness and failures, actual playback, listening milestones and store-link clicks. It uses a temporary identifier for the current page visit and bounded campaign tags. The listening page has a “Share anonymous listening activity for this visit” control. Browser Do Not Track and Global Privacy Control signals suppress this first-party web measurement. A direct /download navigation may record a separate anonymous redirect-intent request, not an install. Its event does not retain a raw IP address or user agent, and recognized privacy signals, previews and bots are excluded.

Our first-party raw analytics retention policy is 400 days, with a scheduled purge of older received events. Aggregate reports do not expose the random identifiers.

Google and Meta measurement

The mobile app includes Google Firebase Analytics to measure usage, such as screens and practice interactions, where available in the installed app build. Google processes this information under its own terms; see Google’s Privacy Policy. Device privacy settings can limit advertising identifiers, but do not necessarily stop every usage event.

In supported mobile builds, Meta ad measurement is on by default. You can turn it off during the welcome guide (“Turn off ad measurement”) or at any time in the library settings; your choice is saved across app launches. While it is on, the native Meta SDK sends an install signal and, for an eligible verified new full-library purchase, the purchase amount, currency and fixed product identifier. Restoring an existing purchase is not a new Meta purchase event. The SDK also processes standard app, device and network information, including your device advertising identifier: on Android, the Google advertising ID (which you can reset or delete in Android settings); on iOS, the advertising identifier only if you also allow tracking when Apple asks. Meta uses this information to measure whether our ads led to installs and purchases, and it may use it for advertising as described in Meta’s policies. This is not anonymous just because we exclude our own identifiers. Automatic event logging is disabled. We do not send meditation activity, onboarding answers, store receipts or purchase tokens, or your first-party analytics identifier as Meta event parameters. On iOS, if you decline Apple’s tracking request, the app does not share the advertising identifier, and Meta may still receive the install and purchase signals for aggregated, privacy-preserving ad measurement unless you turn ad measurement off. Turning it off does not change access to free or purchased practices. It stops future app event sends and advertising-identifier sharing, but cannot recall data already sent or submitted to the SDK. Your Meta choice does not turn off the separate first-party usage measurement or Firebase Analytics described here.

On the website, Meta measurement is optional and starts only after you choose “Allow Meta measurement.” It sends general page, listening and app-store-link events and may use Meta cookies and device information. It does not send the selected practice name, first-party visit identifier, playback diagnostic identifiers or deletion-form contents as event parameters. You can choose “No thanks” through Privacy choices on the listening, catalog or home page. Do Not Track and Global Privacy Control keep it off. Withdrawal stops future website event sends; it cannot recall information already sent. See Meta’s Privacy Policy.

The privacy, terms and deletion-request pages do not load website analytics or the Meta Pixel.

Website and audio delivery

When you visit the site or download audio, hosting and network services may produce technical logs such as an IP address, request time, user agent and requested URL for security, reliability and operations. These logs are separate from the analytics event fields described above.

Purchases

Apple or Google processes payments under its own policies. The app stores a cached entitlement and checks purchases with the store. Our service may process store purchase evidence to confirm access to protected audio. We do not collect your payment-card details through this website.

Deletion requests and your choices

You can request deletion of server-held data without creating an account. The form stores your contact email, any optional analytics identifier and the request details you provide in a staff review queue. We use those details to review and respond to the request. Submission does not automatically delete data. Request records remain in that queue until staff remove them; there is no automated request-retention schedule.

An email address alone may not identify records linked only to a random app-install or temporary web-visit identifier. We may need more information to locate the relevant data and verify that the request is yours. Please do not send passwords, payment-card details or sensitive health information.

Device storage controls can remove downloaded app data. Deleting the app does not delete server records, store purchase history, or necessarily all operating-system-secured purchase information. The deletion page explains these distinctions.

Contact

Privacy questions can be sent to [email protected]. For a saved deletion request and reference number, use the request form.