Privacy policy

The short version

When you use blablabla, your scene text passes through third-party services for parsing and voice generation. Your scenes are backed up to your account so you can get them back on another phone, and a scene you share with someone is kept for that link for up to 90 days. Generated rehearsal audio stays in the app's storage on your device. If you sign in with Google or Apple, we store basic account information. You can delete your account and personal server-side data from Settings at any time, subject to the limited retention described below.

We're building toward a fully on-device pipeline so nothing has to leave your phone at all. That's not where we are today, so here's exactly what happens with your data right now.

What we collect and why

Account information

If you sign in with Google or Apple, we receive your name and email address (and profile photo URL from Google). We store these in our database (hosted on Supabase) so you can log in across devices and sync your scenes.

If you prefer not to sign in, you can use the guest experience without giving us your name or email. The service still assigns an anonymous account and install identifier so core features, usage limits, and later account linking work.

Scene content

When you upload or paste a scene that isn't a Fountain or Final Draft file, the text gets sent to our backend for parsing into structured dialogue. We use OpenAI (GPT-5.6 Luna) first, Anthropic (Claude Sonnet) when the first result is low-confidence, and a smaller OpenAI model only if both fail. Photographed or scanned pages are read by Anthropic (Claude). Fountain and Final Draft files are parsed on your device and never sent to these services. The parsed scene comes back to your device and is backed up to your account. If you share a scene, the shared copy is kept for that link for up to 90 days.

Those services do receive the text to process it and do not train on it. What they do with it after that is governed by their own data policies, linked below. Our security page tracks the retention terms we have with each of them.

Voice synthesis

Character dialogue gets sent to ElevenLabs through our backend for text-to-speech generation. The audio comes back to your device. We do not keep ordinary rehearsal audio on our servers, but audio included in a share link is stored for that link for up to 90 days.

ElevenLabs receives the dialogue text to generate speech. Their retention and handling of that text is governed by their own data policy, linked below. We're actively working on on-device voice generation to remove this dependency entirely.

On-device storage

Generated audio files are cached in your device's app sandbox so rehearsals work offline. Scene data (the structured version of your scene) is saved as JSON files on your device and synced to Supabase for cloud backup, whether or not you've signed in. Each scene's rehearsal history is backed up with it: when you ran it, how long for, and how each of your lines compared with the script, which is what your accuracy scores and your dashboard are built from. Recordings of your voice are never sent to us.

Usage tracking

We log scene budget usage in Supabase: your user ID, characters used, and which scene triggered the request. This is how we track your balance. We don't log the actual text content.

Product analytics

We collect pseudonymous usage data to improve blablabla - things like which screens you visit, which rehearsal modes you use, session duration, and general feature usage. This data is stored in our own database (Supabase) and may be linked to your account or install before it is aggregated. No scene content or dialogue text is included in analytics events.

You can opt out of all analytics and diagnostics in Settings using the "Send Diagnostics" toggle. When turned off, no usage data or crash reports leave your device.

Crash reports

We use Sentry for crash reporting. By default, crash reports are anonymous - no personally identifiable information is included. The same "Send Diagnostics" toggle in Settings controls both crash reports and product analytics.

Subscriptions

Subscriptions and credit-pack purchases are handled by Apple through StoreKit or by Google through Google Play Billing. We don't collect or store your payment-card information. The store handles payment details.

If you ask Apple for a refund, Apple asks us about your use of the app before deciding. We tell them the subscription worked and that you had free access before you subscribed. We also tell them whether we think the refund should go through, which we base on how much voice generation you used after you were charged. We don't send your scenes or your account details. Apple makes the decision, not us. You can ask Apple about the data they hold on you at privacy.apple.com.

Gift purchases

When you buy a gift on our website, Stripe handles the payment. We never see or store your card details. Stripe sends us your email address, name and billing country so we can send your receipt and gift code and charge the right tax. If you add a recipient's email address or a personal note, we store them with the gift code so we can deliver the gift. When someone redeems a code, we link the gift to their account so their Pro time works on every device.

Referrals

When you invite a friend, we store the link between your accounts - who referred whom, the code used, and any rewards given - to run the referral program. Our legal basis is legitimate interest. We never read your contacts. The invite goes out from you, not from us.

AI assistants (ChatGPT, Claude and others)

blablabla has a connector for AI assistants such as ChatGPT and Claude. Your assistant uses it to find our free practice scenes and monologues and to suggest a rehearsal routine. If you connect your blablabla account, your assistant can also send your own scripts to blablabla. Vox Vera ApS, the company behind blablabla, runs the connector.

What the connector receives. Only what your assistant sends to answer your request: which scene or monologue to look up, a language, filters such as genre or length, and the details of the routine you asked for, like how many days you have and how many minutes a day. Your assistant may also pass technical hints, such as your language or rough location. The connector doesn't use or keep them. It never receives your name, email address, assistant account or chat history. It receives a script only when you ask your assistant to send one to blablabla. It can never see your blablabla account or saved scenes.

What we keep. Without a connected account, the connector doesn't store your requests and sends no usage analytics. To limit abuse, we count requests using a keyed hash of your IP address or connection, not the address itself, and delete those counts after about a day. Our hosting provider, Vercel, keeps standard request logs, such as IP address and time, for a short period to run and protect the service. If a request fails, we get an error report in Sentry without the content of your request.

Connecting your account. Sending scripts requires connecting your blablabla account to your assistant. You sign in to blablabla and approve that the assistant may send scripts to your account. The connection only works in that direction: no assistant can read your scripts, your scenes or anything else in your account. A connection lasts at most 30 days. Each app can have up to three connections to your account. Connecting it a fourth time replaces the oldest. An account can have twenty connections in all. You can disconnect in your assistant or at sayblablabla.com/auth/mcp/connections at any time, and deleting your blablabla account removes every connection. We store only hashed versions of the connection codes, never the codes themselves.

Sending a script. If you attach a script or photos of its pages, or paste its text, and ask your assistant to send it to blablabla, the connector fetches the file from your assistant, or receives the text, and stores it privately with us. We don't read it on our servers. Your assistant only gets back whether it arrived and a link that opens blablabla. The script waits in your account until you open the app, and the app then imports it like any script you import from your phone, as described in the rest of this policy. We delete our stored copy as soon as you import it or discard it in the app, or after 7 days if you do neither. You can also ask your assistant to delete it. A scene you save is an ordinary scene in your library, kept and deleted like any other.

The upload page. When your assistant can't pass a file to blablabla, it gives you a one-time link to a page on sayblablabla.com. The page shows which app asked for the link, never your email or name. The file goes straight from your browser to our private storage, then into your blablabla inbox like any other script you send. The link works once, for 15 minutes. Files left over from an upload that didn't finish are deleted within about 4 hours. The link's record holds no script content, only the optional title your assistant gave the script, and is deleted about a day after the link expires.

Opening a scene. A scene link opens blablabla on your phone, or our website. From there, the rest of this policy applies.

The assistant itself. What you type in your assistant, and what it does with it, is covered by its maker's privacy policy: OpenAI's for ChatGPT, Anthropic's for Claude. We don't receive your conversation.

Third-party services

These services process some of your data as described above. Each one has its own data handling and retention policies. We have a data processing agreement with each; here are direct links to their policies so you can check for yourself:

• Google Sign-In - authentication
• Apple Sign-In - authentication
• Supabase - database and auth
• Vercel - hosting for our API (scene text in transit)
• ElevenLabs - text-to-speech (receives dialogue text)
• Anthropic - scene parsing and page reading (receives scene text and page images)
• OpenAI - scene parsing (receives scene text)
• Sentry - crash reporting, EU-hosted, opt-out available
• Resend - transactional email (welcome, account-deletion and gift emails)
• Google Play and Apple StoreKit - Android and iOS subscriptions and purchases
• Stripe - payments for gifts bought on our website

What stays on your device

• All generated audio files
• Cached scene data
• Rehearsal history
• App preferences and settings

These files are kept in the app's protected device storage. Platform security controls access while the device is locked. Uninstalling removes the app's private files, but recordings or selftapes you separately saved to Photos or Gallery remain until you delete them there.

Your choices

Delete your account. Go to Settings and tap "Delete Account." This removes your account information, personal synced scenes, shared-scene links and audio, usage logs, and Ensemble membership. Theatre-owned production records remain without a link to the deleted account. Limited account-unlinked commerce audit records may remain for up to 25 months. On-device files stay until you remove them from the app or device.

Opt out of diagnostics and analytics. Toggle "Send Diagnostics" off in Settings. We won't receive any crash data or usage analytics from your device after that.

Use the app without signing in. Skip Google or Apple sign-in to use the anonymous guest experience without giving us your name or email. An anonymous account and install identifier still support core features, usage limits, premium voices, and later account linking.

Data retention

We keep your account data and personal synced scenes for as long as your account exists. Account deletion removes them, your shared-scene links and audio, and your Ensemble membership. Theatre-owned production records remain without a link to the deleted account. Crash reports in Sentry are retained for 90 days. For fraud prevention, purchase support, and reliable webhook processing, we retain limited account-unlinked commerce audit records for no more than 25 months. They may contain an Apple store transaction or order ID, or a Google Play purchase token, but not your blablabla user ID or the original webhook payload. We keep gift orders, gift codes, the buyer's and recipient's email addresses and any personal note for as long as the code can be redeemed or is in use, and after that for as long as accounting law requires us to keep sales records. Unpaid gift checkouts are deleted after 30 days. The full records Stripe sends us about a payment are cut down to an event ID and type after 30 days.

Third-party services listed above retain data according to their own policies. We pass them the minimum data needed to do their job, but we don't control how long they keep it after processing. Check their linked policies for details.

For users in the EU (GDPR)

You have the right to access, correct, or delete your personal data. You can also request a copy of your data or ask us to restrict how we process it. Our legal basis for processing is our agreement with you to provide the app (your account and your scene backups), your consent for sending scripts and dialogue to the AI and voice services, and legitimate interest (keeping the app running, fixing bugs, and improving the product through pseudonymous usage analytics). Some of the services we use are based outside the EU; those transfers rely on the EU Standard Contractual Clauses. You can also complain to your data protection authority (in Denmark, Datatilsynet). To make a request, email support@sayblablabla.com.

For users in California (CCPA)

We don't sell your personal information. Period. You have the right to know what data we've collected, request its deletion, and not face discrimination for exercising these rights. Email support@sayblablabla.com for any requests.

Children

blablabla is not directed at children under 13. We don't knowingly collect data from anyone under 13. If you're a parent and think your child has provided us with personal information, contact us and we'll delete it.

In some US states, the law asks apps to check a person's age range through the App Store or Google Play. Where that applies, blablabla asks Apple or Google for your age range on your phone. It stays on your phone. We don't store it, send it to our servers or share it, and we use it only to follow those laws.

Changes to this policy

If we change this policy, we'll update the date at the top and post the revised version here. For anything major, we'll notify you in the app.

Contact

blablabla is provided by Vox Vera ApS, Denmark.

Questions, concerns, data requests - send them to support@sayblablabla.com.