Legal

Privacy Policy

Effective: September 10, 2026

The short version

We run LetMeModel, a service that turns your photos, video, and voice recordings into new AI-generated images, clips, and audio. To do that, we have to hold onto what you upload and what we make for you, we send parts of it to third-party AI and infrastructure providers that do the actual generating, and we bill you through a payment processor. We don't sell your data, and we don't feed it into a model of our own. The rest of this policy spells out exactly what that means and what you can do about it. If any of the below conflicts with local law, local law wins.

Part 1. Who is responsible for this

This Privacy Policy is issued by LetMeModel (referred to here as "LetMeModel," "we," or "us"), the operator of the LetMeModel service and the party responsible for the personal data described below. You can reach us about anything in this policy at letmemodel-support@googlegroups.com.

This policy covers the LetMeModel website and app. It doesn't cover other companies' sites just because we happen to link to them.

Part 2. What we hold and why

2.1 The account itself

Setting up an account gives us your email address, a password or a Google sign-in token, whatever display name and avatar you pick, plus state we track on our side: whether your email is verified, whether you're subject to any moderation action, which plan you're on, your current credit balance, and a history of credit changes.

2.2 What you feed into a generation

Every time you use a tool (Faceswap, Talking Photo, an image model, a video model, Voice Lab, and so on), you're giving us the text prompt or instructions you typed, plus whatever photo, clip, or audio file you attached as a source or reference. We keep the result too: the image, video, or audio file that came back, sitting in your history so you can revisit or reuse it.

A meaningful share of that material shows a real person's face or carries a real person's voice. We treat that category separately; see Part 3.

2.3 Money moving through the system

Subscriptions and credit packs run through a third-party payment processor, which takes your card details directly; we never see or hold the full number. What comes back to us is limited: whether a charge succeeded, the amount, your subscription state, the last four digits on file, and the email tied to billing, which we use to keep your account and invoices in order.

2.4 The referral program

If you take part in the referral program, we keep a record of who signed up through your link, the payments that earned you a commission, and any reversals. When you request a payout, we keep the payout network and the wallet address you gave us, because we need them to send the transfer and to have a record of it. If you arrived through someone else's referral link, we record that connection on your account and anonymous counts of link visits.

2.5 What your device tells us automatically

Standard web traffic metadata (IP address, browser and operating system, which screens you visit, how a generation job progressed, timing, and error output when something breaks), plus the session tokens that keep you logged in (more on those in Part 8).

2.6 Anything you send us directly

Support messages, bug reports, and any reply you send to an email we sent you (a verification code, a receipt, a service notice).

We're not asking for government ID numbers, medical records, or anything else in the "sensitive" category defined by law, the one exception being whatever incidentally shows up in a photo or voice clip you choose to upload.

Part 3. Faces and voices get extra rules

Faceswap, Talking Photo, Voice Lab, cloning, and dubbing only work because you hand over an image or recording of an actual person. Given how sensitive that is, here's exactly where we draw lines:

• We only use it for the job you asked for. A face you upload gets used to produce the specific swap or animation you requested, nothing more.
• The person in the file has to have said yes. Uploading someone's face or voice without their permission, or anything involving a minor, breaks our Terms of Service and Content Policy outright and can get your content removed and your account closed.
• Results stay until you remove them. LetMeModel isn't a one-shot tool that forgets your input the moment it's done. Your gallery is a real feature, so source uploads and finished outputs involving a face or voice stay in your account until you delete them or delete the account (timing detail in Part 6).
• We don't build a lookup system out of your face. Nothing here converts your photo into a searchable identity record, and we don't cross-reference uploads to figure out who else you might be.
• It's never for sale, and never for ads. No exceptions.
• Your upload is your yes. Submitting a photo, clip, or voice sample and starting a generation counts as your consent to the handling described here. Where a law requires something more formal (a separate signature, an explicit written statement), we'll collect that before letting you use the relevant tool.
• You hold the delete key. Remove one generation, remove a source file, or delete the whole account: any of those removes the associated biometric material from our live systems, subject to the retention periods in Part 6. When you delete your account, voices you created are also deleted at the provider that hosts them.

Part 4. Who else handles your data

We don't build the generation models ourselves. We route your request to third-party AI and infrastructure providers that specialize in image, video, and voice generation. Each provider acts as a processor on our instructions: they run your prompt or upload through their systems and hand the output back, nothing more. We choose providers whose business terms say submitted content isn't used to train their public models; if that ever changes for a provider we use, we'll say so plainly here.

We don't train our own general-purpose model on anything you send us.

Running the platform itself also means we rely on a small set of infrastructure and service providers: a cloud hosting provider for account login, the database, file storage, and backend processing; a payment processor for billing (see 2.3); and an email delivery provider for verification codes, receipts, and service messages.

We don't publish the names of these providers here. That's operational detail about how we run the business, not something that changes your rights under this policy, but if you have a specific question (for example, for your own compliance review), write to us at the address in Part 13 and we'll answer directly.

Part 5. When information leaves our hands

Beyond the service providers described in Part 4, data moves outward only when:

• The law makes us: a valid court order, subpoena, or regulatory demand, or a genuine need to protect someone's safety or our own legal position.
• The business changes hands: a merger, acquisition, financing round, or asset sale could mean your account data transfers to the new owner, still bound by this policy or its direct successor.
• You tell us to: anything you actively choose to publish or share.

We do not sell personal information, full stop, and we don't hand it to anyone else so they can run their own ad campaigns with it.

Part 6. How long things stay, and how to remove them

Delete a single generation whenever you want from your history. Deleting your account (Settings in the app) removes your profile, uploads, saved models, voices, and generation history from our live systems, apart from anything we're legally obliged to keep (tax records, fraud investigation material, an active dispute), and even that gets deleted or stripped of identifying detail once the legal reason for keeping it ends.

Part 7. How we protect it

We rely on transport encryption (HTTPS/TLS), access restrictions on our production systems, and a need-to-know policy for anyone handling live user data. Card data flows through our payment processor under its own PCI DSS controls; we never see the full number. No system is unbreakable, and we can't promise perfection, but if we ever confirm a breach involving your information, we'll tell you and any regulator the law requires us to tell.

Part 8. Cookies and local storage

LetMeModel stores only a small amount of data in your browser: session and authentication tokens so you don't have to log in on every click, the local app state that keeps the interface working, your cookie choice, and, if you opened a referral link, that link's code and the moment you opened it (kept for up to 90 days so a later sign up can be credited to the person who referred you). We use no ad trackers, no third-party marketing pixels, and no cross-site tracking scripts. If we ever add analytics, it will only run after you agree to it in the cookie banner, and this section will be updated first. You can reopen the cookie banner at any time from "Cookie settings" at the bottom of our homepage.

Clear your browser storage any time; it just logs you out.

Part 9. Data crossing borders

We and the service providers described in Part 4 run infrastructure in more than one country, the United States included. If you're connecting from the EEA, the UK, or anywhere else with restrictions on exporting personal data, expect your information to be processed somewhere with different privacy rules than where you live. Where that requires a formal safeguard, we use the mechanisms the law provides: the European Commission's Standard Contractual Clauses, an applicable adequacy decision, or an equivalent arrangement with the provider in question.

Part 10. Your rights

If you're covered by GDPR or the UK GDPR (broadly: the EEA, the UK, and similar frameworks), you can ask to see what we hold, get it corrected, have it erased, limit how we use it, object to certain processing, get a portable copy, and withdraw any consent you'd given, at any point. If you think we've handled something badly, your local data protection authority will take a complaint.

If you're in California, Virginia, Colorado, Connecticut, Texas, or a state with a comparable law, you can find out what we've collected and how it's used, ask for deletion, and correct inaccuracies, and we won't penalize you for asking. We don't sell information or share it for cross-context ad targeting, so there's no opt-out needed for that right now.

To use any of these rights, write to letmemodel-support@googlegroups.com from the email address on your account. We'll confirm it's really you before acting, and we'll respond within the period the relevant law sets (typically one month under GDPR, up to 45 days under most US state laws). You can also delete your account and everything in it yourself, at any time, from Settings in the app.

Part 11. Age limit

LetMeModel is built for people 18 and older, full stop. We don't knowingly accept anyone younger. Uploading a photo, clip, or recording of a minor into any generation tool is against our Terms of Service and Content Policy regardless of who's asking. If we discover we've collected something from someone under 18, it gets removed. Think that's happened? Tell us at letmemodel-support@googlegroups.com.

Part 12. If this policy changes

We'll update the effective date at the top whenever this policy changes, and for anything substantial, we'll flag it more directly: an in-app banner, an email, whatever fits the change. Continuing to use the service after a change takes effect counts as accepting the updated policy.

Part 13. Reach us

• Email: letmemodel-support@googlegroups.com

Read this policy alongside our Terms of Service and Content Policy; together they cover the whole relationship.