Privacy Policy

Last Updated: October 4, 2026

1. Information We Collect

We collect information you provide directly: email address and name. We do not collect or store credit-card or other financial information. We also collect usage data such as pages viewed, IP address, browser type, and device information.

2. How We Use Your Information

We use this information to run the site: to sign you in and keep you signed in; to send the emails the site sends (waiting-list confirmation, your invitation, email verification, password reset, and a notice when a model or photoshoot is ready or a job failed); to keep a character's conversation with you going; to charge and refund your credit; to run the safety filters; to tell people from bots; to keep the operator's record of what was generated and how; to answer your messages; and to meet legal obligations. We do not sell your information. We do not use it for advertising.

3. Payment Processing

All content is accessed using a USD credit balance on a pay-per-use basis. We do not process credit cards or store any financial information.

4. Age Verification Data

When you attempt age verification we store the time your account was verified and the method used. For self-attestation we also store the region code worked out from your IP address (for example US-TX or GB), the result of the regional check, and when it was checked. We store this whether the check lets you through or asks you for stronger proof. For this check, your IP address itself is never stored and never written to logs. The region code, the result and its timestamp are deleted automatically 12 months after the check; the fact that your account was verified, and the method used, are kept for as long as the account exists. If ID-based verification is introduced, identity documents will be processed solely for verification and deleted on a short, fixed schedule; this policy will be updated before any such flow goes live.

Separately from your account, we check which country and US state you appear to be in when you arrive, so that we do not serve videos or photo galleries where the law requires an age check we do not offer. That check reads your IP address once, as you arrive, whether or not you are signed in. Your IP address is not stored, not written to our logs and not attached to your account. To avoid repeating the lookup on every page, our web server holds the result in memory, keyed by the address, for up to 15 minutes. We do not currently set a cookie for this check; if we turn that on, the cookie will carry only the result and an expiry time.

Before your first paid action, we ask you once to confirm that you are 18 or older and that you accept our Terms of Service. We keep a record of that answer: what you confirmed, the version of the terms, the date and time, your browser's identifying string (its user agent), and a one-way code made from your IP address with a secret key. We never store the IP address itself, and the code cannot be turned back into it. We keep this record for as long as your account exists, so that we can show what you agreed to if a charge is ever questioned.

5. Chat and AI Processing

When you send a message to a character, our own server runs two checks on your text first: a crisis check (a message that reads as a crisis gets a support reply, not a character reply) and a blocked-terms filter. Neither check involves an AI model. A message that passes is sent, together with the recent turns of the conversation, the character's persona and the notes she keeps about you, to a large language model hosted on Amazon Bedrock, an Amazon Web Services service, which writes her reply. The reply is run through the same filter before you see it. The model receives the conversation text; it does not receive your name, email address or account details unless you have typed them into the chat.

If you are signed in, your messages and her replies are stored in a thread tied to your account. Roughly every sixth turn, the same model reads the recent turns and updates a short set of notes about you (at most 12 items) that she uses to remember you. You can see, edit and wipe those notes from the chat at any time. If you rate a reply or regenerate one, the rating and the replaced reply are kept; we use them to evaluate the chat model, never to train it.

Visitors who are not signed in can send a few messages. Those go to the model the same way but are not stored; we keep only daily counts of turns.

When the filter refuses a message, we record the matched term, whether it was your text or the model's, the time, and, if you are signed in, your account. For a small set of terms that have no innocent use, we also keep the refused text itself, up to 1,500 characters, for 30 days. For every other term we keep the term only. A crisis reply is recorded by term only, never the text.

When a character sends you a photo in chat, the model also writes a short caption for it, and the photo request is run through the same filter before anything is generated.

Clearing a conversation removes it from your account at once. It stays readable to site staff for 30 days and is then deleted for good. Site staff can read conversations, including for safety review.

6. Characters, Images and Clips You Create

Everything you give a character (her name, bio, persona, traits and wardrobe lines) and everything generated for her is stored on our servers and in our storage bucket, together with a record of how each image was made: the job, the model and service used, the seed and the prompt. Those records are kept indefinitely (see our 2257 statement).

Different steps run at different services:

Headshots, quick gallery photos, chat photos and body reference images are rendered by Replicate, a hosted image-generation service. Replicate receives the prompt our server writes from her traits and, for gallery and chat photos, her profile picture as the face reference.
Training her model and running photoshoots happen on a GPU machine we rent from Hyperstack for the length of the job. The machine downloads her approved headshots and, for photoshoots, her trained model and the scene prompts, uploads the results to our storage, and is deleted when the job ends.
5-second clips are made by WaveSpeed, a hosted video service, which receives the one photoshoot photo you pick and the motion preset.
Before an image is published on the site it is scanned by Amazon Rekognition, an Amazon Web Services image moderation service, and every label it returns is kept with the image.
Checking that a render looks like her (face matching) runs inside our own server. No outside service is used for that.

A render that fails the face check is moved to a quarantine folder with a defect record. A profile picture you upload is stored in the same storage bucket as generated images.

Images and clips are delivered through the site, which checks each request first. Our storage refuses requests made to it directly. An image marked private is not listed on the site, and the site refuses requests for it, so knowing its address does not open it.

A quality judge that would send finished images to an AI model on Amazon Bedrock is built but switched off. This policy will be updated if it is turned on.

7. Data Storage & Security

Your data is stored on servers hosted on AWS. Connections to the site use TLS. Files in our storage bucket (images, clips and models) are encrypted at rest by the storage provider. Passwords are hashed using BCrypt and are never stored in plain text. The keys and passwords the site needs are kept out of the code and supplied to the server when it starts.

8. Cookies, Analytics and Browser Storage

Cookies we set. One: lc_av_ok, set for 30 days when you click through the 18+ notice, so it is not shown on every visit. Signing in does not use a cookie (see browser storage below). A cookie for the region check (lc_geo) exists in the code but is not in use. A staff-only cookie lets the site owner bypass the region check on his own browser; it is never set for members.

Google Analytics. Every page loads Google Analytics 4 (property G-R53E6K371E). It sets Google's own cookies in your browser, records the pages you view, and receives a few events we send it: joining or confirming the waiting list, with the campaign tags from the link you used, and a report when the page's stylesheet fails to load, with the page address. Google processes that data under its own policy. We have not enabled a consent banner or Google's consent mode. If you block the analytics script, the site still works.

Google reCAPTCHA. The waiting-list form loads Google reCAPTCHA v3 to tell people from bots. Google's script runs on that page and may set Google's cookies. We receive a score, not your identity.

Google sign-in. The login page loads Google's sign-in script from accounts.google.com.

Browser storage (not cookies, and never sent to a third party). While you are signed in, your access and refresh tokens and a copy of your account record (id, email, name, role, email-verified flag and profile picture address) are kept in your browser's local storage. Local storage also holds your light or dark theme choice, unfinished studio drafts, and small interface preferences such as a dismissed progress panel or the chat's full-screen setting. Session storage, which clears when the tab closes, holds the campaign tags and referring site from the link that brought you (used by the waiting-list form) and a one-time stylesheet retry flag.

We do not use advertising cookies and we do not use cookies to track you across other sites.

9. Third-Party Services

These services receive data from us, each under its own privacy policy:

Amazon Web Services: hosting (the server and the database), the storage bucket for images, clips and models, email sending (Amazon SES), image moderation (Amazon Rekognition), the chat model (Amazon Bedrock), and AWS Secrets Manager, which holds some of the site's own keys.
Google: Google Analytics 4 on every page; reCAPTCHA v3 on the waiting-list form; Google Sign-In on the login page.
Replicate: renders headshots, quick gallery photos, chat photos and body reference images. Receives the prompt our server writes and, for gallery and chat photos, the character's profile picture.
Hyperstack: rents us the GPU machine that trains a character's model and runs her photoshoots. Receives her approved headshots, her trained model and the scene prompts for the length of the job.
WaveSpeed: makes 5-second clips. Receives the one photoshoot photo you pick and the motion preset.
Your browser's push service, run by your browser vendor: receives the notification text when you have turned notifications on.
Website Design Company LLC, which operates the removal intake at easy2257.com: receives what you send when you file a removal, likeness or copyright complaint (see our DMCA and 2257 pages).

The region lookup uses a data file from DB-IP that we host ourselves. Your address is not sent to DB-IP.

Messages you send through the contact form are stored by us and emailed to the site operator's inbox.

10. Your Rights

You may request access to, correction of, or deletion of your personal data by contacting us. You may also deactivate your account at any time from Account settings; deactivation disables sign-in and does not delete your data. To have your data deleted, contact us.

11. Data Retention

Your account, email address, name, and the fact and method of age verification: for as long as the account exists.
The waiting list (your email address, when you joined, whether you confirmed and were invited, and the page and link tags that brought you): kept until we add a retention rule. The connection address and browser string stored with a signup are cleared after 90 days.
The region code, result and time of a self-attest age check: 12 months, then cleared by a daily sweep.
The connection address on sign-in attempts and contact-form messages: 90 days, then cleared. The rest of each record stays.
Chat threads: for as long as you keep them. A cleared thread is hidden from you at once and deleted 30 days later.
The text of a refused chat message (kept only for a small set of terms): 30 days. The term and the count stay.
Ratings and regenerated replies: kept as an evaluation record.
Daily chat counts (numbers only, no text and no account): kept.
Characters, images, clips, models and the record of how each was made: for as long as the character exists. Deleting a character removes her gallery, chats, pictures and trained models. The generation records are kept indefinitely.
Images that failed the face check: held in quarantine for 30 days.
Files removed after a complaint: copied to quarantine and kept.
The credit ledger and staff action records: kept.

Deactivating your account keeps your data. To have it deleted, contact us (section 13).

12. Children's Privacy

This Site is not intended for individuals under 18. We do not knowingly collect information from minors.

13. Contact

For privacy inquiries, use the contact form or email privacy@latinacastings.com.