Who we are
This policy is for the Amityly website at amityly.com — a studio for chats and image generation. It is issued by the operator of that service (“Amityly”, “we”, “us”).
If you have an account, we are the controller of the personal data tied to that account. Model providers only receive what is needed to return a generation. Payment details, when Checkout is on, are handled by Stripe.
What we collect
We only keep what we need to run Amityly, keep it fair, and keep it safe.
Depending on how you use Amityly, we may hold:
- Account. Email, password (stored hashed by our auth partner), public username, and profile fields you choose to give — such as name, date of birth, and billing address.
- Google sign-in. If you continue with Google, Google shares your Google account email and name (and, where Google provides it, a profile image). We do not receive your Google password.
- Studio content. Prompts, chats, and images you generate. Until you sign in, this stays in this browser. When you are signed in, Gallery items and related metadata can sync to your account.
- Usage. How many chats and image generations you have used against the daily plan limits.
- Technical. Device and browser type, IP address, security logs, and a human check (Turnstile) on email signup.
- Payments. If you buy Studio, Stripe holds card details. We receive billing status, plan, and limited invoice metadata — not your full card number.
How we use it
We use this information to:
- create and sign you into an account;
- run chats and image generation, and return results to you;
- sync a signed-in Gallery across your devices;
- apply free and paid limits, and process subscriptions;
- keep the service secure (including staff two-factor on Admin);
- fix faults, measure load, and reply if you contact us.
We do not sell your personal information. We do not use your private chats or images to advertise to you.
Google sign-in
This is the notice Google asks us to show if you use Continue with Google.
Continue with Google uses Google’s sign-in. Google will tell you which details it is sharing — typically your Google account email, name, and profile photo. We use those details only to create or recognise your Amityly account and to show a public username (your Google name, never your email, unless you switch email on in Account). We do not receive your Google password. We do not read Gmail, Drive, or other Google services.
You can disconnect Google from your Google account permissions. Email-and-password accounts can be used instead. Amityly’s use of information received from Google APIs follows this policy and Google’s API Services User Data Policy, including the Limited Use requirements.
Where it lives
Work on this device can stay in browser storage until you sign in. Cloud copies (when you are signed in) are held by our hosting and database partners, which may process data in the UK, EEA, or other countries with appropriate safeguards.
We keep account and billing records for as long as the account is open and for a reasonable period after, where we must for tax, security, or dispute reasons. You can clear local data from Settings, download a copy of your account, or close the account from Settings → This device.
Your rights
If UK or EEA data protection law applies, you may ask to access, correct, delete, or restrict personal data, or to object to certain processing, and you may complain to the ICO (or your local authority). Signed-in export and account deletion are in Settings → This device.
Profile visibility is yours to set: email and city stay off Profile unless you switch them on in Account → Personal details. Public username is never taken from your email address.
Children
Amityly is not for children under 13. Email signup asks for a date of birth and will not accept an age below that. If you believe we hold an account for a child under 13, contact us and we will close it.
Contact
Questions about this policy: use your Amityly account where you can, or write through amityly.com. We may update this page as the product grows. The date at the top is the latest version.
Related: Terms of service.