Privacy Policy

Introduction

Gramms is a product of SmartCue, Inc. ("we," "our," or "us"), a Delaware corporation. Gramms is an iPhone app that parents and guardians use to make personalized bedtime stories for their children. This policy explains exactly what the app collects, which partners receive it and under what conditions, how long we keep it, and how you remove it.

We comply with the Children's Online Privacy Protection Act (COPPA), including the FTC's 2025 amendments. Children do not use Gramms directly and cannot create an account: a parent or guardian sets everything up, and a child's information is only ever provided by that adult.

This policy describes the current version of the Gramms iPhone app. If an earlier version is installed on your device, some details below may not yet apply to it.

The short version

What We Collect

Account information (parent or guardian)

You sign in with Sign in with Apple. There is no password to create, and Gramms never sees one. From Apple we receive:

• An account identifier from Apple, which is how we recognise you when you return
• Your email address (Apple's private relay address if you chose "Hide My Email")
• Your name, if Apple passes it along (Apple offers this only at the very first sign-in)

Child profile

With your consent, and only what a story actually needs:

• The child's first name (they are the hero of the story)
• Their age, which shapes only how the story is told
• How the child should be referred to in the story: she, he, or they (optional)
• Whether stories are for bedtime or anytime (optional)
• A record that you gave consent, and when

We do not ask for a last name, a birth date, a photograph, a description of how the child looks, a school, a location, or a contact detail of any kind for a child.

What you write, and what the app makes

• The story ideas you type
• The chapters Gramms writes, and their titles
• The notes that keep a continuing story consistent: a short recap, the characters and places it has established, and where the next chapter picks up
• The narration audio, the cover pictures, and the word timings that light up read-along
• Any feedback or report you send us about a story

Voice recordings (optional, and treated as sensitive)

Bringing a loved one's voice into Gramms is entirely your choice, and nothing here is collected unless you do it. If you do, we collect:

• A short recording of that person reading aloud, made in the app or uploaded by you
• The name and relationship you give the voice, such as "Grandma Rose" (optional)
• A record that the person recorded agreed to it, and when
• The voice model built from that recording: a voiceprint, which we treat as the most sensitive thing in the system

Before a recording is used, it is checked automatically. Every recording is classified to confirm the speaker is an adult; Gramms will not build a voice from a child's voice. A recording made inside the app is also transcribed, to confirm the person really read the words shown on screen; a file you upload cannot be checked that way, so it rests on the adult check and on your word that the person agreed. Both checks run at OpenAI. Only then does the recording go to Cartesia to build the voice. See "Who receives your information" below.

Requested story-ready updates (optional)

If your app offers story-ready updates and you ask for one, we store an identifier for this app installation, its notification delivery token, your notification permission and app version, and the request linked to your account and story. We also keep your update preference, delivery results, and when an update is tapped or its story is opened or starts playing. Temporary waiting and playback records help us avoid interrupting an experience already in progress. Device safety records track registration order and timing, a registration revision, a hashed delivery token and whether registration is blocked. These help prevent an old sign-in from taking over a newer registration. Allowing notifications does not sign you up for updates about every story.

Each story update is your choice. You can cancel a request or pause story updates in Gramms Settings, and manage notification permission in iPhone Settings. A change needs a connection before our server can apply it. An update already submitted for delivery may still arrive.

App-health information

So we can tell whether the app is working, Gramms records events such as "a story finished" or "a screen failed to load". Each event carries:

• The name of the event and when it happened
• The app version, which update the device is running, and the kind of phone it is
• Which features were switched on for that device at the time
• One random number for this device, so we can tell whether a first run is working. It sits in the app's own storage, and deleting the app removes it from your phone
• Your account identifier, once you are signed in

We use this number only to understand how the app is behaving, never to identify you or your child, and never for advertising. These events are stored on our own systems, not sent to an advertising or analytics company. Before anything is written down, a filter throws away the fields that would carry a name or a story idea, blanks out anything that looks like an email address or a sign-in token, and shortens long text. Story text and narration are never part of an event. Gramms contains no advertising, no ad networks, and no third-party analytics or attribution software.

How We Use It

We use what we collect only to:

• Write, illustrate and narrate the stories you ask for
• Keep a continuing story consistent from one night to the next
• Check that a story is safe for a child before it is read aloud
• Keep your library available and let you pick up where you left off
• Send the story-ready updates you explicitly ask for, while avoiding an experience already in progress
• Read stories in a family voice, if you have added one
• Run your subscription, if you have one
• Find and fix crashes, failures and slow paths
• Answer you when you write to us

We do not use anyone's information, least of all a child's, for advertising, profiling or marketing. We do not sell or rent personal information, and we do not share it with anyone beyond the service providers named below.

Who Receives Your Information, and When

These companies process information on our behalf and under contract. Each receives only what its job needs, and several receive nothing at all unless you use a particular feature. Each acts as our service provider and handles the information under contract with us.

OpenAI: writing, narration, pictures and safety checks

See OpenAI's privacy policy.

Cartesia: family voices only

Nothing reaches Cartesia unless you bring a loved one's voice into Gramms. If you never use that feature, this section does not apply to you.

When you remove a voice, we ask Cartesia to destroy it and then read back to confirm it is gone before we let go of anything on our side. If that confirmation does not come, we stop and tell you nothing was removed, rather than report a deletion we could not verify. See Cartesia's privacy policy.

Supabase: our database and file storage

Traffic is encrypted in transit, storage is encrypted at rest by the platform, and database rules restrict every row to the household that owns it. See Supabase's privacy policy.

Railway: where our server runs

See Railway's privacy policy.

Apple and RevenueCat: subscriptions

RevenueCat never receives your child's name, age, or any story content. See RevenueCat's privacy policy.

Sentry: crash reports

Sentry is configured not to attach personal information automatically, and error text is filtered and shortened on the way out so a name or a story cannot travel inside an error message. See Sentry's privacy policy.

Expo: app updates

No account, child or story information is involved in an update check. See Expo's privacy policy.

Expo and Apple: requested story-ready updates

To register this delivery route, Expo also receives a device identifier, the app and project identifiers, the notification token type and whether the app uses a development delivery environment. Expo routes the notification through Apple. This is separate from the app-update check above. See Expo's privacy policy and Apple's privacy policy.

We and the providers above are United States companies, and your information is processed on their infrastructure. We may also disclose information if the law requires it, or to protect a child's safety.

How Long We Keep Things

Different records have different retention periods.

We regularly remove notification request, delivery and response details once they are older than 30 days, and temporary waiting and playback records once they are older than one day. Device registrations and preferences remain while needed to honor your choices. Linked notification records are removed when your account is closed. An anonymous admission count remains to keep the limited pilot from expanding. We also retain device safety records, including the installation identifier, after a registration is removed. They contain no raw delivery token or account or household link, but they are not anonymous. Our regular cleanup removes them when no registration remains and they have been inactive for more than 30 days. These are Gramms retention rules; the delivery providers describe their processing in their privacy policies.

App-health events are removed for your account when you close it. We keep the records the law requires us to keep, such as tax and purchase records; those are held by Apple and by us as the seller, and are not part of your child's information.

Children's Information and Parental Consent

Gramms is used by an adult on a child's behalf. A child cannot create an account, cannot sign in, and is never asked for anything by the app.

Before you add a child, the app shows you in plain language what is collected and who receives it, and you agree to it as an identified, signed-in adult. We record which version of that wording you agreed to, so that if it ever changes materially we know who was told what. We collect only a first name and an age, because that is all a story needs.

As a parent or guardian, you may at any time:

• See what we hold about your child: the profile and every story are visible in the app
• Remove your account and family data by closing your account in the app, which also withdraws your consent and stops further collection of your child's information. The device safety records and anonymous pilot count described above are retained separately
• Have one part removed (a single story, or a name) by writing to us. There is no in-app control for a partial removal yet, so we do it for you
• Refuse to let us share your child's information with the partners named above, which means Gramms cannot write a story, so this amounts to not using the app

Removing Your Information

Close your account, in the app

Open Gramms, go to Settings, and tap Close your account at the bottom. The app tells you exactly what will go before you confirm. When you do, in this order:

• Every cloned voice is destroyed at Cartesia, and the destruction is confirmed
• Your recordings are removed from our storage
• Your app-health events are deleted, including those recorded before you signed in
• Your household is deleted, taking your child profiles, stories, chapters, narrations and covers with it
• Your sign-in account is deleted

The anonymous pilot admission count and unlinked device safety records are excluded from account deletion. Safety records follow the 30-day cleanup rule above; they contain no child information or account or household link.

If a step cannot be completed, the app stops there and says so plainly: that it stopped partway and cannot yet tell you how much of it finished, rather than reporting a deletion that did not happen. Trying again picks up where it left off. The audio and picture files the deleted stories pointed at are removed in the hand-run clean-up described above rather than in the moment, and so is a stored recording whose removal did not succeed when its voice was destroyed. Closing your account does not cancel an App Store subscription; cancel that in your Apple subscription settings.

Remove a single voice

Remove a family voice in the app at any time. The clone is destroyed at Cartesia and the destruction confirmed, and our copy of the recording goes with it. Stories that voice already read stay in your library.

Remove one piece

To remove just a part of what we hold (one story, one name), write to robin@gramms.ai and we will take care of it. There is no in-app equivalent for a partial removal yet, so a person handles this one.

If you cannot open the app

Write to robin@gramms.ai from the email address on your account, and we will verify it is you and complete the deletion within 30 days, usually far sooner. Full instructions are on our account deletion page.

Security

• Traffic is encrypted in transit, and storage is encrypted at rest by our platform
• Database rules restrict your profiles, stories and voices to your own household
• Audio, pictures and recordings are served through short-lived links, not public URLs
• You sign in with Apple, so there is no Gramms password to steal
• Crash reports are filtered and shortened on the way out, so a name or a story cannot travel to Sentry inside an error message. Fuller diagnostic logs stay on our own infrastructure

No system is perfect. If we ever discover a breach affecting your information, we will tell you and the relevant authorities as the law requires.

Changes to This Policy

We may update this policy. We will change the "Last updated" date above, and for any change that materially affects what we collect or who receives it, we will tell you in the app and ask for your agreement again before that change applies to your child's information.

Contact Us

Questions about this policy, or about anything we hold: write to us and a person will answer.