Legal
Privacy Policy
What we collect, why we collect it, who we share it with, and how to get rid of it.
Last updated: 15 August 2026
The short version
Who we are
Zeoze is a social fashion app: you share a look, and people vote on it. This policy explains what happens to your data when you do. It applies to the Zeoze mobile app and to this website.
You can reach us about anything in this policy at [email protected].
Information we collect
Things you give us
- Account details: first name, email address, mobile phone number, date of birth, gender and country. Your date of birth is used to work out an age group; we do not display your exact birthday.
- Profile photo, if you choose to add one.
- Content you create: the photos you upload for a vote, the message you attach, your votes, your comments and replies, and your credit activity.
Things your device provides, with your permission
- Camera and photo library: only when you pick or take a photo. We receive the images you choose to upload, nothing else.
- Contacts: only when you choose to find friends. Phone numbers are sent to our server, matched against registered members in memory, and discarded. We store only the resulting member IDs when you build a group. We never keep your contact list, and we never contact anyone on your behalf.
- Microphone: only while you hold the microphone button to dictate a look's title. The audio is transcribed by your phone's own speech service, which is operated by Apple or Google. We receive the resulting text, not the recording.
- Notifications: a push token, so we can tell you when something happens on your requests.
Things we collect automatically
- Analytics: we use Google Firebase Analytics to understand how the app is used, for example how many people finish signing up or cast a vote. These events are associated with your account.
- Crash and error reports: we use Google Firebase Crashlytics so we can find and fix crashes. Reports are associated with your account so we can tell whether a problem is widespread or specific to you.
- Basic service logs needed to operate and secure the service.
How we use your information
- To create and run your account, publish your looks, and show results.
- To show your request to the audience you chose, and to let invited friends respond.
- To operate the credit system, prevent abuse, and keep the service secure.
- To send you in-app and, if you enable them, push notifications about activity on your requests.
- To review reports of content that breaks our rules, and to act on them.
- To fix crashes and understand which parts of the app work and which do not.
We do not use your information to build advertising profiles, and we do not sell or rent it to anyone.
What other people can see
This is the part most worth reading carefully, because it is the part people are usually surprised by.
- Your name and photo appear on the looks you post, unless you post anonymously. Anonymity is a choice you make per request: when you use it, other people see only "[Anonymous]" and your first initial, with no photo.
- Aggregate results are shown as percentages in the feed and in your voting history, never as raw counts.
- Who voted, and how they voted, is visible to people who can see the request. Anyone signed in can open the list of voters on a look and see each voter's name alongside the choice they made. Please treat your vote as attributable, not secret.
- Comments are public to anyone who can see the request, and show the comment author's name and their vote.
- Friend groups are shared: the people in a group can see who else is in it.
- Reports, mutes and hidden looks are private. The person you report or mute is never told, and nobody else's feed changes.
Who we share it with
We do not sell your data and we do not share it for anyone else's marketing. We do rely on a small number of service providers who process data on our behalf, under contract and on our instructions:
| Provider | What it handles | Where |
|---|---|---|
| Cloudinary | Image storage and delivery | EU / global CDN |
| Neon | The application database | EU (Frankfurt) |
| Render | The application server | EU (Frankfurt) |
| Google Firebase | Push notifications, analytics, crash reporting | Google infrastructure |
We may also disclose information where the law requires it, to enforce our Terms, or to protect the safety of our members.
Where your data is stored
Our database and application servers are hosted in the European Union (Frankfurt). Some providers, notably our image CDN and Google Firebase, operate globally, which means data may be processed outside your country under the safeguards those providers offer.
How long we keep it
We keep your information for as long as your account exists. When you delete your account, we delete your personal data from our live systems immediately, and it falls out of encrypted backups within 30 days.
Two narrow exceptions: we keep a minimal record where the law requires it, and we retain abuse reports so that a pattern of behaviour cannot be erased by deleting and re-creating an account. Reports are kept without the reporting member's identity where they are no longer needed.
Deleting your account
Your rights
Depending on where you live, you may have the right to access the personal data we hold about you, correct it, export it, delete it, or object to some of the ways we use it. You also have the right to complain to your local data protection authority.
To exercise any of these, email [email protected]. We will respond within 30 days.
Children
Zeoze is not intended for children. You must be at least 13 years old to create an account, and we ask for your date of birth at sign-up to enforce that. If we learn that we hold data about someone under 13, we delete the account.
If you believe a child under that age is using the service, please tell us at [email protected] and we will act.
AI features
Zeoze includes optional AI styling features that are not enabled for general use at this time. If you are given access to them and choose to use them, the images you submit are sent to Google's Gemini service to generate a result. The "try it on" feature stores a face photo and a full-body photo only after you explicitly consent, and you can withdraw that consent and delete those photos at any time from within the app. We will update this policy before these features are switched on broadly.
Security
Traffic between the app and our servers is encrypted with TLS. Passwords are stored hashed with Argon2, never in plain text. Access to production systems is limited to the people who operate the service. No system is perfectly secure, but we take this seriously and will tell you promptly if something goes wrong that affects you.
Changes to this policy
If we change this policy we will update the date at the top of the page, and for anything material we will tell you in the app.
Contact
Privacy questions: [email protected]. Anything else: [email protected].