Account information. When you sign up, Clerk (our authentication provider) collects your email address and any social login profile data you authorize (e.g. Google OAuth). We store your email and a Clerk-issued user ID in our database to identify your account.

Billing information. Payments are processed by Stripe. We never see or store your full credit card number. Stripe shares a customer ID and subscription ID with us so we can manage your plan. You can review Stripe’s privacy practices at stripe.com/privacy.

Usage data. We record how many “Wishes” (analysis tokens) you use, when, and for what action. We also log which Claude AI model was called, approximate token counts, and estimated cost per request so we can run the service responsibly.

Project data. When you save a project to the cloud, we store the screenplay title, scene count, uploaded notes, AI-categorized notes, and optionally the raw FDX file content in our Supabase database. If you choose to work entirely in your browser, none of that content reaches our servers.

Contact form data. If you submit the contact form, we receive your name, email address, and message. That message is forwarded to our team email via Resend and is not stored in our database.

Automatically collected data. Like most web services, our infrastructure may log your IP address, browser type, and referring URL for security and debugging purposes. We do not use this data for marketing.

To provide the service. Your account data, subscription status, and Wish balance are used to authenticate you, gate features, and ensure you receive what you paid for.

To run AI analysis. When you submit notes for analysis, the text of those notes (and optionally screenplay content) is sent to Anthropic’s Claude API on your behalf. Anthropic’s own data practices apply to that transmission — see anthropic.com/privacy.

To communicate with you. We may send transactional emails (subscription confirmations, password resets) via Resend. We do not send marketing emails without explicit opt-in.

To improve Screnie. Aggregate, anonymized usage patterns may inform product decisions. We do not sell individual usage data.

To prevent abuse. Usage logs help us detect fraud, enforce rate limits, and protect the integrity of the Wish economy.

Where data lives. User account and project records are stored in Supabase (hosted on AWS). Authentication is managed by Clerk. Payments are processed and stored by Stripe. All three services maintain SOC 2 compliance and encrypt data at rest and in transit.

Script content. By default, your screenplay content is stored in your browser’s local storage and never transmitted to our servers unless you explicitly save a project to the cloud. Cloud-saved projects are stored in Supabase with row-level security — only your authenticated account can read your projects.

Retention. We retain account and project data for as long as your account is active. If you delete your account, we will delete or anonymize your personal data within 30 days, except where we are required by law to retain records (e.g. financial transactions).

Security. We use HTTPS everywhere, environment-variable-managed secrets, and role-based database access. No system is 100% secure; if you discover a vulnerability, please contact us at ovvendoerr@gmail.com.

Screnie integrates the following third-party services. Each processes data under their own privacy policies:

• —Clerk (Authentication & user management) clerk.com/privacy
• —Stripe (Payment processing & subscriptions) stripe.com/privacy
• —Anthropic (Claude AI analysis engine) anthropic.com/privacy
• —Supabase (Database & file storage) supabase.com/privacy
• —Resend (Transactional email delivery) resend.com/privacy

We do not sell your data to any third party.

Authentication cookies. Clerk sets session cookies necessary for you to stay logged in. These are strictly functional and cannot be opted out of while using the service.

Browser local storage. Screnie stores your active screenplay and project state in your browser’s local storage so your work persists between sessions without requiring a cloud save. This data never leaves your device unless you trigger a cloud save.

No tracking cookies. We do not use advertising cookies, third-party analytics cookies, or cross-site tracking cookies.

Depending on where you live, you may have rights regarding your personal data, including:

• —Access — request a copy of the data we hold about you
• —Correction — request that inaccurate data be corrected
• —Deletion — request deletion of your account and associated data
• —Portability — receive your project data in a machine-readable format
• —Objection — object to certain processing activities

To exercise any of these rights, email us at ovvendoerr@gmail.com. We will respond within 30 days. Note that some requests may be limited by our legal obligations or legitimate business interests.

Screnie is not directed at children under 13 years of age. We do not knowingly collect personal information from children. If you believe a child has provided us with personal data, contact us and we will delete it promptly.

We may update this Privacy Policy from time to time. When we do, we will update the “Last updated” date at the top of this page. For material changes, we will notify registered users via email or an in-app notice. Continued use of Screnie after such changes constitutes acceptance of the updated policy.

Questions about this policy? Reach us at:

ovvendoerr@gmail.com
screnie.com