Snorbit Privacy Policy
Effective date: 2026-10-27
Your data belongs to you. In this policy, we lay out what data is processed and why, how it is handled, and your rights. This policy applies to Snorbit, its support pages and correspondence with Creatrix. Contact: creatrix.studio26@gmail.com.
Recordings and health-related inputs stay on your device unless you choose to share or export them. This does not mean there is no off-device collection: usage analytics and crash reporting process the service data described below, and in-app feedback you choose to send goes to Creatrix’s server.
What we collect and why
Identity and access
Snorbit does not require an app account, email login or account sync. Optional profile details and questionnaire answers are stored locally, not submitted as an account registration. Local attribution storage holds app-generated identifiers and sanitized referral information; the app does not supply those local anonymous, event or recording-session identifiers as Google Analytics event parameters. SDKs can generate their own identifiers, so the absence of an account does not make all service data anonymous.
Billing information
Apple App Store and Google Play handle payments through StoreKit and Play Billing. The app receives purchase and subscription entitlement information to check Premium access, restore purchases and maintain local entitlement state. It does not collect card numbers, bank details or billing addresses. When usage analytics is enabled, allowed events include purchase attempts, verification outcomes and plan categories, without receipts or payment details in custom event parameters. Firebase Analytics may also automatically measure in-app purchase activity when enabled. The stores retain their own transaction records under their policies.
Product interactions and local content
The app stores microphone audio, recording times, sound level samples and activity summaries, notes, tags, pins, optional weight and rested ratings, profile details, adult questionnaire answers, alarm choices and settings in app-private storage. Sound activity summaries are calculated on the device from recorded loudness levels; older stored analysis results remain local too. The app has no Creatrix-operated upload, account-sync or cloud-backup service for this content. Its recording data directory is excluded from system backup; Android app backup is disabled.
The app’s custom analytics code does not send audio, sound levels, scores, health or questionnaire answers, profile values or free-text notes to providers. It does not automatically collect your contacts, photos, messages, browsing history or precise GPS location. A share or export that you initiate can send selected content to an app or destination you choose. Settings export includes session summaries, notes, tags, questionnaire answers and settings; audio is shared separately from a recording. Recipients’ handling of those copies is outside the app’s local storage controls.
Usage analytics (Google Analytics for Firebase, GA4): on by default, without a consent screen, so we can see which steps of the app work and where people stop. If your device region is in the EU/EEA, the United Kingdom or Switzerland, it stays off until you agree, and you can withdraw that agreement in Settings → Privacy and analytics. Elsewhere there is no switch in the app; email us to ask us to stop processing (see “Your rights”). If you turned usage analytics off in an earlier version, it stays off. When it is on, Google receives allowlisted app actions and outcomes, screen/feature categories, sanitized referral metadata and app/device information. The app also sets these user properties, each from a fixed list of values: app language, subscription state (free or paid), notification permission (granted, denied or not asked), the week you installed the app, and whether your device region is in the EU flow. Google’s SDK can process app-instance or device identifiers, IP-derived region and diagnostics, and automatic purchase measurements. Custom events describe actions rather than private values; for example, a profile edit can be logged without the profile content. The app disables automatic screen reporting and analytics advertising purposes; iOS IDFA/IDFV analytics collection and Android advertising-ID analytics collection are disabled. These settings do not eliminate all SDK identifiers or diagnostics.
Microsoft Clarity (public-screen replay): on iOS it is off by default and starts only if you turn it on in Settings. On Android it is on by default with the whole app window masked, so text and images are not captured; in the EU/EEA, the United Kingdom and Switzerland it stays off until you agree, and an earlier choice to turn it off is kept. When it is on, Clarity receives interaction events and reconstructed screen layout for the Premium paywall, subscription help and acknowledgments, along with device/app information, coarse region, performance/error information and SDK-generated user/session identifiers or other usage data. On iOS, app windows are masked by default and public elements may be unmasked; on Android, nothing is unmasked. Replay is paused on private screens, recording and native payment flows on both. The app does not supply a personal identity to Clarity. These are capture restrictions, not a claim that every SDK-generated datum is anonymous or that providers never receive diagnostics.
Crash reports (Google Firebase Crashlytics): follow the same rule as usage analytics: on by default, and off until you agree in the EU/EEA, the United Kingdom and Switzerland. Crash reports include the crash stack, app version, device model, OS version, an installation identifier, the app language and the subscription state (free or paid), and are used only to fix problems. They never include audio, recordings, health or questionnaire answers, scores, notes or anything you type, and are not linked to your identity or used for tracking. Where usage analytics is off, crash reports are off too.
Key app events (Creatrix server): so that no important step is lost, the main events (such as the first scored night, paywall views, purchase and restore results, and permission answers) are also sent to Creatrix’s own server, under the same rule as usage analytics. Each event carries its name, values from a fixed list, the time, a random event ID used only to remove duplicates, the app version, platform and system version. It carries no account or device identifier, recordings, sound levels, scores or anything you type. Like any server, it receives your IP address when the app connects (see “General geolocation data”). Events waiting to be sent are kept on the device for up to 30 days.
General geolocation data
Network providers receive IP addresses when their services are contacted. Google Analytics and Clarity can process approximate region. The app reads the region setting of your device, without location permission, to decide whether to ask for consent first. The app does not request precise location permission or supply GPS coordinates to these SDKs.
Website interactions
These support pages are hosted on GitHub Pages. They contain no analytics, advertising or replay scripts, tracking pixels or embedded forms added by Creatrix. GitHub processes visitors’ connection information, including IP addresses, under the GitHub Privacy Statement. Following external links exposes connection information to those destinations under their policies.
Free first recording and no ads
Your first recording is free with the full result. After that, recording needs Snorbit Premium. The app shows no ads: it contains no third-party advertising SDK, uses no advertising identifier and makes no ad-network requests. It does not track you across other companies’ apps or websites for advertising.
When usage analytics is on, allowlisted screen/button actions and purchase or restore outcomes can be measured without recording content. This does not enable advertising storage or ad personalization. Google/Firebase and Microsoft SDK data is described above. See Firebase privacy information and the Microsoft Privacy Statement.
These pages do not set Creatrix cookies. In the native app, preferences, consent and entitlement state are stored locally; third-party SDK storage and identifiers are governed by the relevant service settings and policies.
In-app feedback
When you tap Send feedback, the app sends Creatrix your message, the category you picked (if any), the app version, platform (iOS or Android), system version, app language and the name of the feedback screen. It does not send your email address, an account or device identifier, recordings, sound levels, scores, notes or questionnaire answers, so we cannot reply to in-app feedback; email us if you want an answer. Please do not put personal or health details in the message. We use feedback only to provide support and improve the app.
The server uses your IP address in memory to limit sending to 5 messages a minute and 30 a day; it is not stored with the message. If the message cannot be sent, the app keeps it on your device and retries when you open the app or the network returns; unsent messages are deleted from the device after 3 days.
Voluntary correspondence
When you email Creatrix with a question or ask for help, we receive your email address and whatever message, attachments or diagnostic details you choose to send. We use that correspondence to respond and investigate the issue, and may keep it as a history of the request. The app does not automatically attach your recordings or health inputs. Please send only information needed for your request.
How we approach mobile app permissions
Microphone permission is needed to record sound. Notification and alarm permissions support the reminders and alarms you choose, including relevant Android exact-alarm access and iOS AlarmKit permission where used. You can change permissions in your operating-system settings; declining a permission can disable the corresponding feature. The current app does not connect to Apple Health or Health Connect to upload or sync health data.
When we access or disclose your information
To provide services you request: In-app feedback is stored for Creatrix by Supabase (database) and Oracle Cloud Infrastructure (server), which act as processors and do not use it for their own purposes. Google/Firebase and Microsoft handle the analytics described above, the same Creatrix server receives the key app events described above, Apple and Google handle store transactions, and GitHub hosts these pages. They receive the service data described above and may process it under their own terms. We do not have remote access to your local recordings.
At your direction: exports, system sharing, email and in-app feedback send content only when you initiate the action. For troubleshooting, we work with information you voluntarily provide; contact us before sending sensitive files. We do not sell your local recordings or health inputs or provide them for ad targeting.
To protect rights or comply with law: we may preserve or disclose information actually in our possession when necessary to comply with applicable legal process or to address unlawful use, fraud or threats to safety. We cannot disclose local content we have never received. A business transfer involving information we hold would require applicable legal safeguards and notice. There is no blanket permission to transfer your local recordings.
Your rights with respect to your information
Depending on applicable law, you may have rights to know about processing, access, correct, delete or receive a copy of your information, restrict or object to processing, withdraw consent, and complain to a privacy authority. Applicable rights relating to sale/sharing, automated decisions, non-discrimination or an appeal also remain available. We do not use the app’s sound summaries to make decisions with legal or similarly significant effects about you. Some information may be exempt from a request under applicable law.
View, edit, export or delete local content in the app. In the EU/EEA, the United Kingdom and Switzerland, Settings → Privacy and analytics lets you withdraw consent for usage analytics and public-screen replay at any time. Elsewhere, iOS users can turn public-screen replay on or off there, and you can ask us by email to stop processing usage analytics, crash reports or Android replay; we will tell you how to stop it on your device. Turning collection off stops future collection; it does not delete information already received by providers or stop separate store processing. Device and provider settings offer additional controls.
For information held by us or help with a provider request, email creatrix.studio26@gmail.com. We may need reasonable proof of identity or an agent’s authority and enough information to locate data. No app account links every provider identifier to your email, so we may not be able to identify all SDK records. We will explain available steps and applicable limits rather than promise erasure we cannot verify. You may also contact Apple, Google, Microsoft or GitHub under their privacy policies.
How we secure your data
Recordings and related local data use the operating system’s app sandbox and backup exclusions described above. The app does not add its own encryption layer to every audio file. Keep your device secured and updated; anyone with access to an unlocked device or an exported file may be able to read its contents. Providers document security measures such as encrypted transport for their services. No method of storage or transmission is completely secure, and this policy does not promise universal end-to-end encryption or protection from every loss.
What happens when you delete content
Deleting a completed session removes its local audio, associated notes and session metadata. Routine “Delete unpinned recordings” cleanup preserves pinned sessions and active recordings; delete pinned sessions individually if you want to remove them. Audio retention modes can discard unselected audio segments while keeping pins. Removed audio cannot be restored by us.
To remove remaining local profile, questionnaire and settings data, delete the app on iOS rather than offloading it, or clear app storage on Android. Export anything you need first. There is no cloud account to delete or recover from. Local deletion does not cancel a subscription, erase copies shared elsewhere, or erase store transactions or provider telemetry.
Data retention
Local data remains until you delete it, remove app storage, or apply the selected audio-retention settings. In-app feedback and key app events are kept for 1 year from receipt and then deleted by a weekly cleanup. To ask us to delete a message sooner, email us its text and the approximate time you sent it. We keep email correspondence for the time necessary to handle the request and meet legal obligations, resolve disputes or enforce agreements.
Google, Microsoft, Apple and GitHub retain service records under their own policies and configured service settings. We do not promise a particular SDK retention period or automatic provider deletion after uninstalling. Contact us for assistance with a request; provider retention and deletion scope may differ from local deletion.
Location of site and data
Private recording content is processed on your device. In-app feedback is stored in the United States: Supabase region us-west-1 (Northern California) and Oracle Cloud Infrastructure region us-phoenix-1 (Arizona). Data sent to Google, Microsoft, Apple, GitHub or an email provider may be processed outside your country, including in the United States and other countries where those providers operate. We do not claim that all data stays in Korea or in a particular provider region.
International transfers
In-app feedback (overseas transfer under the Korean Personal Information Protection Act):
- Items: the message, optional category, app version, platform, system version, app language and screen name described above.
- Country, time and method: the United States; sent over an encrypted HTTPS connection when you tap Send feedback, or when the app retries a saved message.
- Recipients: Supabase, Inc. (database, us-west-1), see the Supabase Privacy Policy; Oracle Corporation (Oracle Cloud Infrastructure server, us-phoenix-1), see the Oracle Privacy Policy.
- Purpose and retention: storing and processing feedback for Creatrix’s support, for 1 year from receipt.
- How to refuse: do not use in-app feedback; you can email us instead. Every other app feature works without it.
Key app events (overseas transfer under the Korean Personal Information Protection Act):
- Items: the event name and fixed-list values, time, random event ID, app version, platform and system version described above.
- Country, time and method: the United States; sent over an encrypted HTTPS connection after a key event, when the app opens, or when it retries saved events.
- Recipients: the same Supabase, Inc. and Oracle Corporation services listed for in-app feedback.
- Purpose and retention: measuring which steps of the app work, for 1 year from receipt.
- How to refuse: in the EU/EEA, the United Kingdom and Switzerland, do not agree or withdraw in Settings; elsewhere, email us and we will tell you how to stop it on your device.
Applicable privacy and international-transfer requirements remain in force, including any required notices, legal grounds, consent or safeguards for information sent abroad. Provider policies describe their transfer practices. We do not claim that Creatrix has adopted Basecamp’s data processing agreement or its contractual transfer arrangements, and use of the app is not a substitute for any consent separately required by law. Contact us for information relevant to your request.
Children
Snorbit is not intended for children under 13, or under the minimum age required in their country if higher (14 in Korea, up to 16 in some EU countries). We do not knowingly collect personal information from children. If you believe a child has used the app and information was sent to a provider, contact creatrix.studio26@gmail.com and we will help remove it where we can.
Changes and questions
We may update this policy as needed to comply with relevant regulations and reflect new practices. Whenever we make a significant change, we will refresh the date at the top of this page and take appropriate steps to notify users, including obtaining consent where required.
Have questions, comments or concerns about this policy, your data or your rights? Email creatrix.studio26@gmail.com. The English version prevails if translations differ, except where Korean law requires otherwise.
Adapted from the Basecamp open-source policies / CC BY 4.0.