Privacy
Your data, in plain English.
Last updated: May 23, 2026
What we read
Layne reads emails from a short list of casting-platform senders and your talent agencies. That’s it. Here’s the full list:
- ✓Casting Networks — Audition alerts, submissions, callbacks
- ✓Actors Access — Breakdowns and submission confirmations
- ✓Casting Frontier — Audition notifications
- ✓Casting.com — Submission alerts
- ✓Your agency — Forwarded breakdowns and avail requests from your reps
From those emails we extract the project name, casting director, role, rate, deadline, and body text. The original email stays in your inbox — we never move, delete, or modify it.
What we never see
Layne has no access to anything outside the casting senders listed above. Google’s API lets us request only what we need, and we request the minimum.
- ✕Personal emails — family, friends, newsletters, shopping
- ✕Contacts or address book
- ✕Calendar events
- ✕Passwords, payment info, or financial data
- ✕Drafts, sent mail, or trash
- ✕Google Drive, Photos, or any other Google service
How it works
When a casting email lands in your inbox, Google notifies Layne in real time. Here’s what happens next:
your agency
rate, deadline
briefings
Similar to how Calendly reads only your calendar availability — not your event details, contacts, or files — Layne reads only casting notifications, not your personal mail.
Your controls
Security
Everything in transit is encrypted with TLS. Your data at rest lives in a Postgres database with row-level security — you can only see your own rows, even if someone got into the database directly. Sensitive credentials (Gmail tokens, casting-platform passwords) are encrypted with AES-256-GCM before storage. We don’t store your Google password — only an OAuth token that you can revoke at any time.
What we don’t do
- —We never sell your data.
- —We never use it for advertising.
- —We never train AI models on your emails or audition history.
- —We never share it with third parties except the infrastructure providers that run Layne (Supabase, Vercel, Railway, Anthropic).
Our use of Google API data adheres to the Google API Services User Data Policy, including the Limited Use requirements.
Questions?
Anything at all — privacy questions, deletion requests, or feedback: ccmacmini@gmail.com.