SNOWBALL PRIVACY POLICY

Your information.
A clear picture.

Scope and contact

This policy covers the Snowball website and mobile app operated by Snowball. It describes the features present in the current implementation. It does not cover the separate Snowballing or Panda apps.

snowball01.app@gmail.com

Website and free starter

The website saves a light or dark preference in browser local storage under snowball-theme. The curated browser starter keeps the selected example, progress, and outcome in page memory; leaving or reloading the page resets it. The public starter does not require sign-in or submit its example selections to a model.

Vercel hosts the website and processes ordinary network and request information, such as IP address, requested URL, browser information, and timestamps, to deliver and secure the service. Read Vercel’s privacy policy. No advertising tracker or third-party analytics script is intentionally included in the current website.

Mobile sign-in and accounts

Where configured, Snowball uses Supabase Auth with Sign in with Apple or Google. The sign-in provider and Supabase process the information needed to authenticate you, such as a provider identifier, account identifier, and an email address if supplied. Apple may supply a private relay address. Snowball does not receive your Apple or Google password.

Native authentication tokens are held in platform secure storage. On the mobile web build, bearer sessions stay in memory and the temporary sign-in verifier can use session storage. Sign-in and service access also involve the request information processed by those providers. See Supabase’s privacy policy, Apple’s privacy policy, and Google’s privacy policy.

Sessions, drafts, History, and Insights

In mobile builds with account sync, tasks, drafts, active sessions, action feedback and History are stored in your signed-in Supabase account, with a local copy for offline use. Insights is calculated from those session records. Appearance preferences stay on the device. Earlier local-only builds do not provide cloud backup; earlier device history is added to account storage only when you choose to import it. Removing app storage can lose changes that have not synced.

Features that let you copy or share content act only when you choose them. The receiving app or destination then handles the shared information under its own terms. Do not share a task or draft containing information you do not want that destination to receive.

AI-assisted starting help

If model help is enabled, the app sends the task description, category, relevant clarification answers, starting difficulty or energy context, corrections, and previous suggestions needed for the request to Snowball’s backend. If you choose to add photos of a letter, form, or screen, those photos are sent once with that request so the model can read them. Snowball does not store the photos; only a short text summary of what was read is kept with that task. The camera is used only when you choose to take a photo for this. If you fill in About you, that text is saved on your device and sent with your requests while “Use in my plans” is on; you can edit, switch off, or delete it in the app at any time. The app’s language is also sent so the help can be written in your language. The backend sends the necessary request content to Anthropic’s Claude API to generate starting help and to understand what kind of task you entered. If you use Insights’ personal review, aggregated counts (such as how many Snowballs you started, at what times, and in which categories) are sent the same way; the text of your tasks is not. Edited draft text is not automatically included in model requests unless you separately put it into information sent for help. In account-sync builds, saved drafts and corrections can still be stored in your Supabase account as part of your session.

Processing takes place outside your device. Anthropic processes this content as a service provider under its commercial terms, does not use it to train its models, and keeps it only for a limited period for safety and abuse monitoring. Do not send private, confidential, medical, financial, or other sensitive information. See Anthropic’s commercial terms and privacy policy.

Account authentication is checked before configured mobile model requests. Signing in is not itself consent to an unrelated purpose. The app explains what is shared and asks for your permission before the first AI request. To change your choice later, contact support and we will reset it for your account.

Microphone and speech recognition

If you choose to dictate instead of typing, Snowball asks for microphone and speech recognition permission. Your voice is converted to text by Apple’s speech recognition on your device or by Apple’s servers, under Apple’s privacy policy. Snowball does not record or store audio; only the resulting text is used, like typed text. You can turn these permissions off at any time in iPhone Settings.

If you allow notifications, Snowball schedules check-in reminders on your device after you leave to do a move. They are created and delivered locally by iOS; no notification content is sent to our servers, and you can turn them off in Settings → Privacy & data → Check-in reminders or in iPhone Settings.

If you turn on Face ID lock in Settings, iOS checks your face on your device. Snowball never receives or stores Face ID data; it only learns whether the check succeeded.

Support and purchases

If you contact support, your email provider and Snowball’s support inbox process the address, message, attachments you choose to include, and correspondence needed to respond. Do not include passwords, sign-in codes, full card numbers, or sensitive task content.

Snowball+ purchases are processed by Apple through the App Store; Snowball never receives your payment details. Snowball uses RevenueCat to verify purchases and manage subscription status. RevenueCat receives an anonymous app user identifier (your Snowball account identifier if you are signed in), the products purchased, and transaction and receipt information from Apple. Snowball stores your subscription status and a count of your daily AI uses in your account to apply plan limits. See RevenueCat’s privacy policy. See Subscription Help.

Retention and deletion

Local mobile records remain until you delete them, remove app storage, or use a control that replaces them. Authentication records and account-synced session records remain until you delete the account or the relevant sessions, subject to applicable provider and legal retention. Other devices refresh synced changes when reopened or synced; support cannot remotely erase an offline device’s local copy. Support correspondence is used to handle your request and follow-up; you can ask for deletion of correspondence that no longer needs to be retained.

The website and backend can generate operational or security records through hosting and service providers. Retention depends on their configuration and applicable requirements. A local session reset cannot erase provider-held records or information already processed by Google. We do not promise a retention period we have not verified.

Visit Account & Data Deletion to distinguish local cleanup from deleting your account and to request operator-held data removal. You can also ask support about access, correction, export, or other privacy rights that apply where you live. Requests may require account-ownership verification. We explain any required retained records and applicable period rather than representing sign-out as deletion.

Other important limits

Snowball is a productivity tool, not a medical service. Do not submit another person’s information without permission. External websites and sign-in providers have their own policies. Data may be processed in countries where the relevant providers operate, under their applicable contractual and legal arrangements.

We will update this policy when data processing materially changes. The date above identifies the latest published revision. For questions, contact Snowball support.