smasc

Privacy and account data

Updated 20 October 2026. This website is pre-release. We are preparing the smasc app and account features described below; this website does not offer account access or sign-in yet.

Your account and sign-in

When you sign in with Apple or Google, we use the provider's verified account identifier to recognize your smasc account. We retain the email address and verification or Apple private-relay status when the provider shares them. We request basic identity scopes, not access to your mail, contacts, photos, or files. We store whether you meet the minimum age requirement, not your date of birth.

We keep the session records needed to sign you in and an encrypted Apple authorization credential needed to manage and revoke that connection. Credentials are not included in your account data export. Apple and Google also process sign-in under their own privacy notices.

What you choose and watch in the app

Your account stores interests, personalization and language choices, likes, saved stories, collections, and the latest viewing position and completion state for stories in your watch history. Watch history keeps the latest 200 stories. Removing a saved story also removes it from your collections. You can remove history entries or clear watch history in the app.

We store a bounded set of qualified story views for your current interest preferences so the starting mix can adapt consistently across devices. Changing those preferences resets that progress. Clearing watch history does not reset it. These functional records support your account features; they are separate from optional usage analytics. Minimal records of accepted account actions are kept with your account so a retried request cannot repeat an old choice. We do not need a record of every animation frame, pause, tap, or screen to provide these features.

Your account also stores the analytics choice, listen-mode preference, automatic-download-on-Wi-Fi preference, and daily reminder preference and local reminder time. Device notification permission, transient mute and playback state, and downloaded media files remain on your device. Restoring a reminder preference does not grant operating-system notification permission.

Analytics, marketing, and feedback

Usage analytics and marketing choices are separate from functional account data. Turning account analytics off stops optional analytics when the app applies the updated choice. Turning it on still requires an explicit opt-in on each device; a restored account preference alone does not enable analytics. Analytics requests do not include your account authorization, email address, or provider identifier. A device analytics identifier is not used to join analytics events to an account.

More or less like this changes account preferences and may exclude a story from your feed. Error reports retain the reported story, selected reason, any note you submit, and a keyed reporter identifier used to handle duplicate reports. Reports are removed when your account is deleted. Marketing consent is recorded separately with its time and policy version.

Optional Recall questions keep functional learning state: first story completion, questions shown, the latest answer and whether it matches the approved answer, consecutive skips, and the pause-until date. The service keeps at most 200 story learning records and up to 60 shown-question times from the latest 30 days. Removing a history item forgets its learning records; clearing history clears the corresponding Recall state. Answer correctness is derived by the server, and these records are separate from analytics.

Web setup

Web setup asks about topics, storytelling style, and story length. It does not ask for a name, email address, or date of birth. A secure functional cookie lets this browser resume setup for up to seven days. An unfinished setup expires after seven days. A finalized setup code can be used once within 60 days. After use, the setup record is retained for up to 30 days.

To recognize setup on the same phone, we retain a one-way code derived from the network address and basic device details, rather than storing those details themselves. This code expires after 24 hours and is deleted when setup is used. It is used for setup recovery, not advertising or tracking across apps or websites. Setup activity is counted in aggregate without setup codes or account identifiers. Cloudflare Turnstile helps check new setup requests for automated abuse.

Storage, access, and removal

Account records are stored in the service database. Media and account-export files use object storage. Private media access uses time-limited signed links. Operational access controls and security records support sign-in, abuse prevention, and recovery. Google Cloud provides service infrastructure; Cloudflare provides storage and abuse prevention.

When account services launch, you will be able to change account preferences and remove library or history items in the app. Account data export includes your profile, identities, consent history, security events, and functional library records. A completed export is available for 24 hours; each download link lasts 60 seconds.

Account deletion disables account access immediately and starts a 14-day grace period. Final removal is processed after that period. If disconnecting a provider or removing data temporarily fails, the account stays closed while removal is retried. Limited deletion and security records help prevent a deleted account from being reactivated from a backup. Backup copies can retain deleted information until their scheduled retention period ends.

Local downloads and cached data may remain on a device until removed there. Signed-out local caches do not authorize access to another account.

Contact

For privacy, support, or an account-data request, contact mert@smasc.app.