Orb Privacy Policy
Last updated: July 7, 2026
Overview
Orb is designed to be private by default. The app does not require an account, does not use analytics, does not track users, and does not send practice data to an Orb server.
Orb's core data is stored locally on the user's device.
Information Orb Stores On Device
Orb may store the following information locally:
- App preferences, such as language, sleep display behavior, sound settings, bell settings, and haptic settings.
- Orb appearance choices, including light, form, texture, movement, atmosphere, and glow.
- Custom paths, including saved breath rhythms, session length, and sound field choices.
- Practice history, including completed sessions, durations, selected rhythms, mode, and recent session memories.
- Optional post-session reflections, such as selected feelings or intentions.
- Optional user name if the user chooses to add one in Settings.
This information is used to make Orb feel continuous and personal across sessions.
Information Orb Does Not Collect
Orb does not currently:
- Create or require an Orb account.
- Collect analytics.
- Track users across apps or websites.
- Sell user data.
- Use third-party advertising SDKs.
- Use third-party analytics SDKs.
- Record microphone audio.
- Access HealthKit.
- Access location.
- Upload practice history to an Orb server.
Sound, Haptics, and Background Audio
Orb uses local audio and haptic features to support breathing, timer, and sleep sessions. If a user chooses audible sound, Orb may continue playing session audio and bells while the app is in the background, consistent with the user's selected session settings.
Orb does not record audio from the microphone.
Siri, Shortcuts, and Spotlight
Orb may expose practice entry points to Apple system features such as Siri, Shortcuts, and Spotlight. These features help users open Orb sections, start practices, or find saved paths more quickly.
System features are provided by Apple and may be governed by Apple's privacy policies and device settings. Orb does not use these features to send practice data to an Orb server.
Device Backups
Orb stores its app data on device. Depending on the user's iOS and iCloud settings, the operating system may include app data in device backups. Orb does not operate its own cloud sync service.
Users can manage iCloud and device backup behavior in iOS Settings.
Export and Import
Orb may allow users to export or import their own Orb data. Exporting is user initiated. After export, the user is responsible for where that file is saved or shared.
Sharing With Third Parties
Orb does not sell personal information and does not share practice data with third-party advertisers or analytics providers.
If a user voluntarily sends information to support@jnanalab.com, such as a support message or exported file, that information will be used only to respond to the request and provide support.
Data Deletion
Users can delete Orb from their device to remove local app data from that device. If app data has been included in an iCloud or device backup, users may need to manage or delete those backups through Apple account and device settings.
If a user has exported Orb data, deleting the app will not delete exported files stored elsewhere.
Children's Privacy
Orb is not directed to children under 13. If you believe a child has provided personal information through support communication, contact support@jnanalab.com so it can be addressed.
Wellness Disclaimer
Orb is a meditation, breathwork, timer, and sleep-support app. It is not a medical device and does not provide medical advice, diagnosis, or treatment. Users should consult a qualified healthcare professional for medical or mental health concerns.
Changes To This Policy
This policy may be updated as Orb changes. The updated version will be posted with a new "Last updated" date.
Contact
For privacy questions, contact:
Jnana Lab\
App Store Privacy Label Note
Based on the current app design, Orb is intended to fit a no-tracking, no-account, on-device privacy posture. Final App Store Connect privacy answers should be verified against the exact build submitted, Apple's current App Privacy definitions, and any future features added before release.