Call for Line – Privacy Policy
Call for Line
Privacy Policy
Effective Date: September 28, 2026
This Privacy Policy explains how Call for Line LLC ("Call for Line," "we," "us," or "our") collects, uses, and protects your information when you use the Call for Line mobile application (the "App") and when you visit our website at callforline.com (the "Website"). We’ve written this in plain English because we believe you deserve to know exactly what happens with your data.
The App and the Website collect different things. Most of this policy describes the App, where you have an account. What the Website collects, including its use of cookies, is set out in its own part of Section 1.
1. Information We Collect
Information You Provide
- Account information. When you sign in through Apple Sign-In or Google Sign-In, we receive your name, email address, and profile photo from those services. This is managed through our authentication provider, Clerk.
- Scripts. You upload scripts as PDF or text files for parsing into scenes and dialogue.
- Voice recordings. When you rehearse, the App records your voice to transcribe your lines and score your accuracy.
- Rehearsal preferences. Your character selections, accuracy goals, speed settings, and hint preferences.
Information Collected Automatically
- Device identifier. We generate a unique device ID the first time you sign in, which is linked to your account.
- Basic device information. Device type, operating system version, and app version.
- Usage metrics. How you interact with the App (e.g., which features you use, session length), collected through PostHog and linked to your account. We do not record your screen.
- Crash and performance data. When something goes wrong, Sentry receives the error and the app state around it, linked to your account so we can follow up.
- Subscription status. If you subscribe to Call for Line Pro, RevenueCat receives your account identifier and the purchase and renewal events for your subscription. Your payment details go to Apple, never to us.
Information Collected on Our Website
The Website works differently from the App. You do not need an account to read it, and most visitors never give us anything.
- Analytics cookies. We use Google Analytics to see which pages people read and roughly where they arrived from. It sets cookies in your browser and assigns you a random identifier. That identifier is not connected to your name, your email, or your App account. Google Signals and user-provided data collection are switched off in our account, so this data is not joined to anyone’s Google profile and is not used to build advertising audiences.
- Hosting measurement. Vercel, which hosts the Website, records basic request and performance data such as page load times. This does not use cookies.
- Where you came from. When you arrive, your browser stores the first page you landed on, the site or app that linked you, and any campaign tags in the link you followed. This sits in your browser’s local storage for up to 90 days. It is never sent to us unless you choose to submit one of our forms, and it contains nothing about you personally until you type in an email address.
- Email addresses you give us. If you join the waitlist, sign up for updates, or send us a question, we receive the address you type, along with your name and message where the form asks for them, and the arrival information described above so we know which page brought you to us.
We do not use advertising cookies, retargeting pixels, or third-party tracking tags on the Website.
Information We Do Not Collect
- We do not use third-party advertising or ad-tracking tools.
- The App does not use cookies. It is a native mobile application, so there is no browser to put them in. The Website does use analytics cookies, described above.
- We do not collect precise location data.
- We do not sell your personal information. We have never sold personal information and have no plans to.
2. How We Use Your Information
We use your information only to provide and improve Call for Line. Here’s specifically what that means:
- Script parsing. Your script text is sent to our processing tools to identify scenes, characters, and dialogue.
- Voice generation. Individual lines from your script are sent to our voice generation tools to create scene partner audio for your rehearsals.
- Transcription and scoring. Your voice recordings are sent to our transcription tools, which convert your speech to text so we can compare it against the script and score your accuracy.
- Account management. Your account information is used to authenticate you and maintain your account.
- Service improvement. Usage metrics help us understand which features are working well and what to improve. We analyze this data in aggregate, not at the individual level.
- Communications. We may use your email to send you important service updates (not marketing, unless you opt in).
- Waitlist and updates. If you sign up on the Website, we use your email to confirm the signup, to tell you when the App is released, and to send occasional notes about it. We use the arrival information collected with it to understand which pages bring people to us, in aggregate.
3. How Our Technology Partners Process Your Data
Call for Line relies on specialized third-party services to power its core features. Here’s exactly what goes where:
- Anthropic. Receives the text of a script you import, to break it into scenes, characters, and lines. It does not receive your name, email, or recordings.
- OpenAI. Receives the text of your scene partners’ lines to generate their spoken audio, and receives your voice recordings to transcribe what you said so it can be scored. Audio is sent for processing and is not stored by us afterward.
- Clerk. Handles sign-in and holds your account record: your name, email address, and profile photo as provided by Apple or Google.
- RevenueCat. If you subscribe to Call for Line Pro, receives your account identifier and your purchase and renewal events so the app knows your subscription is active. Your payment details go to Apple and never reach us or RevenueCat.
- PostHog. Receives product analytics about how you use the App, linked to your account identifier. Screen recording is switched off.
- Sentry. Receives crash and error reports, linked to your account identifier, so we can diagnose problems without asking for your device. Screenshots and screen contents are switched off.
- Railway. Hosts our server and database, where your scripts, scenes, and rehearsal history are stored.
These partners serve the Website rather than the App:
- Google Analytics. Receives the pages you view on the Website, your browser and device type, and an approximate location derived from your IP address, tied to a random cookie identifier rather than to you. Google Signals and user-provided data collection are off in our account, so this data is not joined to your Google profile or used to build an advertising profile of you.
- Vercel. Hosts the Website and records basic request and performance data.
- Google Sheets. If you submit a form on the Website, your email address, anything else the form asked for, and the arrival information described in Section 1 are written to a private spreadsheet in our Google Workspace account.
- Resend. Delivers the confirmation email you receive after signing up and the notification that comes to us, which means it handles your email address and the contents of those messages.
Important: We use the API (business) tiers of these services, which have contractual commitments not to use your data for model training. Your scripts and recordings are not used to train anyone’s systems.
4. What We Store and What We Don’t
Not all data is treated the same. Here’s the distinction:
Transient Data (Processed and Discarded)
- Scripts are sent to our parsing tools, processed, and discarded. The raw script text is not retained on our servers.
- Voice recordings are sent to our transcription tools in real time and discarded immediately after processing. We never store your voice recordings on our servers.
- Individual script lines sent for voice generation are processed and not retained.
Persistent Data (Stored)
- Account information (name, email, profile photo) is stored in Clerk and our database for as long as your account exists.
- Your parsed scripts (the scenes-and-dialogue breakdown, not the raw text) are stored privately in your account so your library can sync across your devices. They are not shared with other users.
- User records (your account ID, device ID, and account preferences) are stored in our PostgreSQL database hosted on Railway.
Data on Your Device
- Scripts, rehearsal progress, and generated audio are stored locally on your device using the App’s local storage. This data is under your control and stays on your device unless you uninstall the App.
5. Data Security
We take reasonable measures to protect your information:
- All data transmitted between your device, our servers, and third-party services uses HTTPS encryption.
- Authentication is handled by Clerk, which provides industry-standard security for sign-in and identity management.
- Our database is hosted on Railway with standard infrastructure security protections.
- We limit employee access to personal data to those who need it to operate the service.
No system is perfectly secure. We cannot guarantee absolute security, but we are committed to protecting your data using commercially reasonable practices.
6. Your Rights and Choices
All Users
- Access. You can view the personal information associated with your account in the App’s settings.
- Deletion. You can delete your account through the App’s settings. This will remove your Clerk authentication record and your user data from our PostgreSQL database. Your synced parsed scripts are deleted with your account. Data stored locally on your device will remain until you uninstall the App.
- Correction. You can update your account information through your Apple or Google account settings, which will sync to Call for Line through Clerk.
- Data Portability. You can request a copy of your personal data by emailing us at support@callforline.com.
- Withdraw Consent. You can stop using the App at any time. For microphone access, you can revoke permission in your device’s settings.
- Website analytics. You can opt out of Google Analytics in any browser using Google’s opt-out add-on, or by blocking cookies for callforline.com. Clearing your browser’s site data for callforline.com also erases the arrival information described in Section 1.
- Email updates. If you are on the waitlist or the update list, you can ask to come off it at any time by replying to any message from us or emailing support@callforline.com. We will remove you and delete the record.
California Residents (CCPA/CPRA)
If you are a California resident, you have additional rights under the California Consumer Privacy Act, as amended by the California Privacy Rights Act:
- Right to Know. You can request details about the categories and specific pieces of personal information we’ve collected, the sources of that information, our business purpose for collecting it, and the categories of third parties with whom we’ve shared it. Under the 2026 regulations, this right extends to data collected going back to January 1, 2022.
- Right to Delete. You can request that we delete your personal information, subject to certain exceptions (e.g., completing a transaction, security, legal obligations).
- Right to Correct. You can request correction of inaccurate personal information.
- Right to Opt Out of Sale/Sharing. We do not sell or share your personal information for cross-context behavioral advertising. If this ever changes, we will provide a clear opt-out mechanism.
- Right to Limit Use of Sensitive Personal Information. We only use sensitive personal information (such as your account credentials) as necessary to provide the service.
- Non-Discrimination. We will not discriminate against you for exercising any of these rights.
To exercise your California privacy rights, email us at support@callforline.com. We will verify your identity before processing your request and respond within 45 days as required by law.
Categories of Personal Information (CCPA Disclosure)
In the preceding 12 months, we have collected the following categories of personal information as defined by the CCPA:
- Identifiers: name, email address, device ID.
- Internet or electronic network activity: App usage metrics, device information, Website page views, the site or app that referred you, and an approximate location derived from your IP address.
- Audio information: voice recordings (processed transiently, not stored).
- Inferences: rehearsal accuracy scores derived from your voice recordings.
We have not sold any personal information. We have disclosed personal information to service providers (Anthropic, OpenAI, Clerk, Google, Vercel, Resend) for the business purposes described in Section 3.
7. Children’s Privacy
Call for Line is not directed at children under 13. We comply with the Children’s Online Privacy Protection Act (COPPA), as amended effective April 22, 2026.
We do not knowingly collect personal information from children under 13. If we become aware that we have collected personal information from a child under 13 without verifiable parental consent, we will take steps to delete that information as quickly as possible.
Users between 13 and 18 may use Call for Line with the consent of a parent or legal guardian. Because voice recordings are processed transiently and not stored, and because the App does not use persistent identifiers for tracking or advertising, we believe our data practices are consistent with COPPA’s requirements for transient data use.
If you believe a child under 13 has provided us with personal information, please contact us at support@callforline.com.
8. Voice Recordings and Biometric Data
We want to be transparent about how we handle voice recordings, given the sensitivity of audio data and the evolving legal landscape around biometric information.
What we do: When you rehearse, the App captures your voice, sends the audio to OpenAI’s Whisper service for transcription, and receives text back. The audio is processed in real time and discarded. We do not create, collect, or store voiceprints or any biometric identifiers derived from your voice.
What we don’t do: We do not analyze your voice for identification purposes. We do not create speaker profiles. We do not use voice data for any purpose other than transcribing your rehearsal lines and scoring accuracy.
Illinois Residents (BIPA): The Illinois Biometric Information Privacy Act regulates the collection of biometric identifiers, including voiceprints. Because we do not extract, store, or use voiceprints or any biometric identifiers from your voice recordings, we believe our practices fall outside BIPA’s scope. If you have questions about how we handle voice data, please contact us at support@callforline.com.
9. International Data Transfers
Call for Line is operated from the United States. Our servers, database, and third-party service providers (Anthropic, OpenAI, Clerk, Railway) are all based in the United States. If you use Call for Line from outside the United States, your data will be transferred to and processed in the United States, which may have different data protection laws than your country.
By using Call for Line, you consent to the transfer of your information to the United States. We apply the same privacy protections to all user data regardless of where it originates.
10. Data Retention
- Account data is retained for as long as your account is active. When you delete your account, we delete your Clerk record and PostgreSQL user data within 30 days.
- Script text and voice recordings are not retained on our servers. They are processed transiently and discarded.
- Parsed script structures are stored privately in your account until you delete the script or your account.
- Usage metrics are retained in aggregate form. Individual-level usage data is deleted within 12 months of collection.
- Device-local data (scripts, progress, audio cache) persists until you uninstall the App.
- Website analytics data is deleted automatically by Google Analytics at the end of the retention window set in our account.
- Waitlist and update-list email addresses are kept until you ask us to remove you.
- The arrival information stored by your browser expires after 90 days, or sooner if you clear your site data.
11. Third-Party Links and Services
The App and the Website may contain links to third-party websites or services. We are not responsible for the privacy practices of those third parties. We encourage you to review their privacy policies before sharing information with them.
12. Changes to This Privacy Policy
We may update this Privacy Policy from time to time. When we make material changes, we’ll notify you through the App or by email at least 30 days before the changes take effect. The “Effective Date” at the top of this page reflects the date of the most recent update.
We encourage you to review this Privacy Policy periodically. Your continued use of Call for Line after the effective date of an updated Privacy Policy means you accept the changes.
13. Contact Us
If you have questions about this Privacy Policy, want to exercise your privacy rights, or have a concern about how we handle your data, contact us at:
Call for Line LLC
1401 21st Street, Suite R
Sacramento, CA 95811
Email: support@callforline.com
For California privacy rights requests, please include “California Privacy Request” in the subject line of your email.
Call for Line