1. Scope and contact
This Privacy Policy applies to the Storyglot mobile application, the Storyglot website, support communications, and related services that link to this policy. In this policy, “Storyglot,” “we,” “us,” and “our” refer to the operator of the Storyglot service. Storyglot is the party responsible for deciding how personal information described in this policy is used.
Questions, privacy requests, and complaints can be sent through the private support form. Please use “Storyglot privacy request” in the subject field. We may need to verify that a request relates to your account before acting on it.
2. Plain-language summary
- Guest mode uses a random account identifier so reading progress can work without requiring your name or email.
- A registered account stores the sign-in details you provide and lets you sync progress and restore access across supported devices.
- Optional usage analytics are collected only with your consent. You can change that choice in Settings.
- Apple or Google processes app marketplace payments. RevenueCat helps us confirm subscription status. We do not receive your full payment card number.
- We do not sell personal information or use it for cross-context behavioral advertising. Free readers may choose a clearly labeled Google rewarded ad to unlock limited access; Premium remains ad-free.
- You can delete your Storyglot account and associated data from the app. Deleting the account does not cancel an Apple or Google Play subscription.
3. Information we collect
The information we handle depends on how you use Storyglot and which optional features you choose.
Account and identity information
- Guest account: When you begin using the app without registering, Storyglot creates a random Supabase user identifier and a guest profile. This allows essential app functions to work without collecting your name or email.
- Registered account: When you create or link an account, we receive your email address, authentication status, and the date your account was created or updated.
- Account preferences: We collect the language, reading, accessibility, and app preferences you choose to sync with your account.
- Authentication records: Our authentication provider stores the information needed to authenticate your account, such as securely processed credentials, session tokens, and account recovery records. Storyglot does not store a readable copy of your password.
Reading and learning information
- Books added to your library, the source from which a book was added, and completion status.
- Reading progress, last chapter, last-read time, saved words, bookmarks, text-size setting, streak information, and language preferences when those features are available.
- Data stored locally on your device, including cached content and preferences. Local data remains on the device unless it is synced or included in a support report you send us.
Subscription and transaction information
- Subscription product, entitlement status, store, purchase and expiration dates, renewal status, trial or introductory status, currency, price, and transaction event identifiers.
- Apple or Google processes the purchase and payment credentials. RevenueCat receives purchase and receipt information from the applicable marketplace and tells Storyglot whether Premium access is active.
- We do not receive or store your full credit or debit card number.
Optional usage analytics
If you affirmatively enable “Share Usage Analytics,” we may collect events such as onboarding completion, screen and feature use, books opened or completed, translation and audio feature use, rewarded-ad offers, impressions, completion and estimated revenue, paywall and subscription flow interactions, error categories, session identifier, book identifier, target language, platform, app version, timestamps, and whether the session used a guest account. Analytics events are associated with your random Storyglot user identifier so we can understand journeys across sessions. We do not include story text you enter, account passwords, payment card numbers, or support message content in analytics.
Device, network, and service records
Our infrastructure and service providers may automatically process IP address, request time, user agent, device and operating system type, app version, authentication logs, crash or error details, and security signals. We use this information to deliver the service, prevent abuse, troubleshoot failures, and maintain security. We do not request precise location, contacts, photos, or microphone access for Storyglot’s core reading features.
Support communications
If you contact us, we receive your email address and the content of your message, plus any screenshots, diagnostics, transaction identifiers, or other information you choose to provide. Do not send passwords, full payment card details, or sensitive information that is not needed to resolve your request.
Website information
The Storyglot marketing site does not use advertising pixels or its own analytics cookies. Before public launch, people could join a launch waitlist. For those historical signups, we collected the email address, consent time, and campaign or referral parameters in the signup link. Those parameters were used to understand which first-party launch efforts produced a signup; they are stored with the waitlist record and are not used for cross-site tracking.
If you previously applied to the Founding Readers beta, we collected the application details shown on that form to select and support the testing cohort. The public beta application is now closed.
If you submit a support ticket, we collect the category, email address, subject, message, optional account and device details, submission time, delivery status, and ticket reference. The site loads fonts from Google Fonts and uses Cloudflare Turnstile to protect support forms from automated submissions. Your browser may send those providers standard connection and security data such as IP address, user agent, request time, and requested resources. If we later add analytics or cookies, we will update this policy and provide any consent controls required by law.
4. How we use information
We use personal information for the following purposes:
- Provide guest and registered accounts, authenticate users, and keep accounts secure.
- Deliver stories, translations, text-to-speech controls, reading progress, saved words, streaks, preferences, offline access, and cross-device synchronization.
- Process purchases, validate receipts, maintain Premium entitlements, restore purchases, and provide subscription support.
- Respond to support, privacy, safety, accessibility, and account recovery requests.
- With your consent, maintain historical launch-update records, send Storyglot product and story updates, and understand which first-party campaigns or referrals produced those signups.
- Maintain and close out records from the completed Founding Readers beta application process.
- With consent, understand feature use, improve the reading experience, evaluate content, and measure subscription performance.
- Detect fraud, abuse, security incidents, technical failures, and violations of our Terms of Service.
- Comply with law, enforce agreements, preserve evidence, resolve disputes, and protect users, Storyglot, and others.
- Create statistics and reports that have been aggregated or deidentified so they no longer reasonably identify an individual.
5. Legal bases for processing
Where laws such as the European Economic Area and United Kingdom data protection rules require a legal basis, we rely on:
| Legal basis | Examples |
|---|---|
| Contract | Creating an account, syncing reading data, delivering Premium content, and restoring purchases. |
| Consent | Optional usage analytics and any other optional processing that is clearly presented as a consent choice. You may withdraw consent at any time. |
| Legitimate interests | Securing the service, preventing fraud, diagnosing failures, responding to support, enforcing rules, and improving core service reliability, balanced against your rights. |
| Legal obligation | Tax, accounting, consumer protection, valid legal process, and responding to legally required privacy requests. |
| Vital interests or public interest | Rare situations involving a credible risk of serious harm, or another processing ground specifically authorized by law. |
7. Analytics choices
Usage analytics are optional. Storyglot asks before enabling analytics and records your choice. You can withdraw consent at any time in Settings > Privacy > Share Usage Analytics. When the setting is off, the app stops creating new optional analytics events, clears events waiting to be uploaded, and the analytics ingestion service rejects events for an opted-out profile.
When analytics are enabled, Storyglot stores the events in its Supabase analytics system and mirrors the same limited event set to PostHog. PostHog automatic capture and person profiles are not enabled. Ad-consent choices are separate from usage analytics; where required, Google’s consent form appears before an ad can be requested, and an Ad Privacy Choices entry is available in Settings.
Turning analytics off does not stop essential operational records needed to sign you in, sync data, provide purchases, protect security, process support, or comply with law. It also does not retroactively remove deidentified statistics already created from earlier events. You may request deletion of identifiable analytics by deleting your account or contacting us.
8. Retention and deletion
We keep personal information only as long as reasonably needed for the purposes described in this policy, including providing the service, meeting legal requirements, resolving disputes, preventing abuse, and enforcing agreements.
| Information | Typical retention |
|---|---|
| Account, profile, library, progress, and preferences | While your account is active, then deleted or deidentified after a verified account deletion request, subject to backup cycles and legal exceptions. |
| Raw opt-in analytics events | Up to 90 days. Aggregated or deidentified reports may be retained longer when they no longer reasonably identify you. |
| Subscription and transaction records | For the subscription lifecycle and as long as needed for tax, accounting, fraud prevention, audit, refund, and consumer protection obligations. Some records may be retained for up to seven years where required or appropriate. |
| Rewarded-ad claims and access grants | Pending claims expire after 15 minutes. A completed reward unlocks the offered book remainder, chapter bundle, or selected chapter narration for 24 hours. Claim and transaction records may be retained longer for fraud prevention, rate limiting, and audit. |
| Support and privacy communications | For as long as needed to resolve the request and maintain a reasonable record of the response, generally no longer than 24 months unless law, safety, or an ongoing dispute requires longer. |
| Historical launch-update list | Until you unsubscribe or ask us to remove the signup, or up to 24 months after the last update. Campaign and referral fields are deleted with the signup record. |
| Founding Readers beta applications | Through the beta selection and testing period, then generally no longer than six months after the public launch unless you join the program, request continued launch updates, or ask us to delete the application sooner. Account and Premium entitlement records created for accepted testers follow the account retention periods above. |
| Security and moderation records | For as long as reasonably needed to protect users, prevent repeat abuse, investigate an incident, or establish and defend legal claims. |
Delete your account and data
You can start deletion in Settings > Delete Account & Data. The app will explain what is deleted and ask you to confirm. Deletion removes the Storyglot authentication account and associated library, reading progress, saved learning data, preferences, and active entitlement record from our live systems. It also signs the device out and clears Storyglot data stored locally, subject to operating system backups outside our control.
Some transaction, security, support, legal, or deidentified records may remain when retention is necessary and permitted by law. Personal information in restricted backups is isolated from normal use and removed through the backup lifecycle. We will not restore deleted information to active use unless needed for security or disaster recovery, and any restored data remains subject to the deletion request.
A waitlist signup or beta application is separate from an in-app account. To remove one before an unsubscribe or withdrawal link is available, submit a privacy ticket using the address you used.
Deleting Storyglot does not cancel marketplace billing
Deleting an account or uninstalling the app does not cancel a subscription. Cancel first in Apple subscription settings or Google Play subscriptions. Premium access may continue until the end of the paid period, subject to the marketplace’s terms.
9. Your privacy rights
Depending on where you live, you may have the right to:
- Know whether we process your personal information and obtain access to it.
- Correct inaccurate or incomplete information.
- Delete personal information.
- Receive certain information in a portable format.
- Restrict or object to certain processing.
- Withdraw consent without affecting earlier lawful processing.
- Appeal a refusal to act on a request where local law provides that right.
- Complain to your local data protection authority.
Use in-app settings where available, or submit a privacy ticket. Describe the right you want to exercise and the email or username connected to the account. We may request reasonable verification. We will respond within the period required by applicable law. Authorized agents may submit requests where permitted, but we may require proof of authority and direct identity verification.
We will not discriminate against you for exercising privacy rights. Storyglot does not sell personal information and therefore does not offer a “Do Not Sell” mechanism. If our practices change, we will update this policy and provide required controls before the change takes effect.
10. Children and teens
Storyglot is a general-audience language-learning service and is not directed to children under 13. A person under 13 may not create a registered account or purchase Premium. We do not knowingly collect personal information from a child under 13. If local law sets a higher minimum age for a child to consent to online data processing, that higher age applies unless a parent or legal guardian provides valid consent through a method we make available.
Users who are under the age of majority should review these terms and any purchase with a parent or legal guardian. A parent or guardian who believes a child submitted personal information without appropriate consent should submit a privacy ticket. We will investigate and delete the information when required.
11. Security and international transfers
Security
We use safeguards designed for the nature of the information we handle, including encrypted network connections, managed authentication, access controls, row-level database policies, least-privilege service access, secret management, logging, and deletion procedures. No method of storage or transmission is completely secure. You are responsible for protecting your device, email account, sign-in credentials, and recovery methods. Contact us promptly if you believe your account or information has been compromised.
International processing
Storyglot and its providers may process information in the United States and other countries whose laws may differ from those where you live. Where required, we use recognized safeguards for international transfers, such as contractual protections, provider data processing terms, and other lawful transfer mechanisms. You can contact us for more information about safeguards relevant to your information.
Third-party services and links
Apple, Google, Supabase, RevenueCat, PostHog, sign-in providers, and websites reached through external links have their own terms and privacy practices. This policy describes Storyglot’s handling and does not replace a third party’s policy. Review the relevant provider’s information before using an external service.
12. Changes and contact
We may update this policy when Storyglot’s features, providers, or legal obligations change. We will post the revised policy with a new effective date. If a change materially affects your rights or how we use personal information, we will provide additional notice in the app or by another appropriate method before the change takes effect when required.
Privacy contact
Submit a private privacy request
For product help, purchase questions, or accessibility support, visit the Storyglot Support page.