Skip to content

Privacy Policy

Zodiamor keeps as little about you as it can. Here you can read what we keep, why, for how long and how to delete it.

Updated November 22, 2026

Who is responsible for your data

The data controller is the founder of the service, Narek Hovhannisyan, a private person in Armenia. Once the service has a company or a sole proprietorship in Armenia, that will be the controller, and this text will be updated.

The controller’s address is Yerevan, Rubinyants 2/3, apt. 35.

Questions about your data can go to @narek_14.

We follow the Law of the Republic of Armenia “On Protection of Personal Data”. The supervisory authority is the Personal Data Protection Agency of the Ministry of Justice of Armenia.

Who the service is for

Zodiamor is for people aged 18 and over.

The service works from Armenia and is open to people from any country who come to it on their own.

We don’t advertise the service in Russia, the European Union or the United Kingdom, and we don’t offer it in Russia. That is why we have no representative in the EU or the UK.

The founder lets people into the test version of the service by an access list. A row of the list holds only a Telegram id, who added it and when, and an end date if one is set, with no name or notes. If the id is from Telegram’s test environment, where we test payments, the row says so too. A row is deleted when it is removed or its end date passes, and after 30 days if there is still no account. When the row is removed, the person’s sessions in the test version end too. The /mydata file shows the row, and /delete deletes it. Some ids may still also be in the settings of the test version on Vercel. There they are only Telegram ids. The founder removes them by hand, and the /mydata file and the /delete command don’t touch them.

We are still confirming with a lawyer the legal basis for this list. Once it is confirmed, this text will be updated.

What we take from Telegram

You can sign up and sign in only through Telegram.

From the Mini App launch data the server takes your Telegram id and whether we may message you. It also reads the tag of the link that opened the Mini App, for example a button on the website or a friend’s link. The server uses it only to count new accounts by source. That count holds no id, and the server does not store the tag. On your device the Mini App also looks at your Telegram language and at whether you have Telegram Premium. Our Telegram chat and the Mini App speak the language of your profile, and before you have a profile, the language of your Telegram. If we don’t have that language, they speak English.

On the website, signing in with Telegram works only for an account that already exists in the Mini App. From the sign-in we take only the id. If you allow us to message you when you sign in, Telegram tells us.

Telegram also sends us the first name, last name and username from your profile, and sometimes your photo. They come with the Mini App launch data, at sign-in on the website and with every message to our chat in Telegram. We don’t store them or use them in the service. We don’t ask for your phone number or your Telegram contacts.

Telegram is responsible for data inside Telegram, including our chat with you. How it keeps that data is described in Telegram’s privacy policy.

What your account keeps

Your account keeps what matching can’t work without.

  • Your Telegram id and the name you choose in your profile.
  • Your birth date, your birth time if you know it, and a time zone with a note of where it came from. Usually it is your device’s time zone, or the time zone of your birthplace if you pick one in your profile setup. If no time zone can be found, we use UTC. From these the server works out the position of the Sun, your sign and your decan, and keeps them too. On a sign cusp it also keeps the side you pick. From the same data the server works out which signs Venus and Mars were in at the moment of your birth. We don’t keep these signs. The server works them out again whenever they are needed.
  • Your gender and who you’re looking for. Together they may reveal your orientation. We use who you’re looking for only for matching and keep it with your consent. You give it when you tap “Start”. Matching can’t work without it, so you can withdraw it only by deleting your account.
  • Your city and the city where you’re looking, what you’re looking for, the age range and distance of your search, the app language and your bio if you write one.
  • Your height, and your weight if you add it. Height is needed for your profile. Weight is optional, there’s a “Prefer not to say” button for that, and you can erase your weight in your profile at any time. People who are shown your profile see your height, and only people who open your whole profile see your weight. We don’t use height or weight for matching, the order of the feed or filters, and we don’t count them in statistics.
  • Answers to profile questions, up to three, if you pick them, and your interests. When you sign up you pick three to eight interests, and later your profile can have up to ten. We keep which question you chose, the text of your answer, their order and time, and for interests only their list. People who are shown your profile see them, and so does a reviewer if someone reports you. Links, handles, phone numbers and talk of money are not accepted in an answer.
  • Links to your social media accounts, if you add them. These are Instagram, TikTok and X. For each network we keep your handle and the time of your last edit, and if the team removed the handle after a report, a mark saying so. In the field you can paste a handle or a link to your profile on that network, and from a link we take only the handle. Everyone who is shown your profile sees the icons, in the same place as your bio. Tapping an icon opens the social network. We don’t check that the page is yours, and we don’t visit it. You can change or erase a handle in your profile at any time.
  • How complete your profile is. We work this out from the number of photos, your bio, your interests and your answers to profile questions, and keep it as a single number. Only you see the percentage. It affects only the order of the feed among people with the same compatibility. Weight, social media and the selfie check don’t count towards it.
  • Feed filters, if you change them. These are the countries you search in, the distance from the city where you’re looking, the order of profiles and whether the “Only 80%+” filter is on. We keep them so that the feed opens the same way next time, and delete them together with your account.
  • Photos, from one to six, their order and your main photo. For each photo we keep three smaller copies without location or camera data. We don’t keep the original file. Each photo also keeps the focus point you pick, which is two numbers. The screens use it to frame the photo. Each photo also keeps its review status and, if it was rejected, the reason. Each photo also keeps a short hash to find duplicates, described in the “Profile check” section. If the decision on a photo was handed to the founder, the time of the handover is kept too. It is a service mark, and it is neither in the /mydata file nor in the app. Photos don’t go to Telegram, and we don’t forward them there.
  • Your likes, passes and matches, when you were last active, your choice of who sees when you’re online and its exceptions for matches, your consents with the versions of their texts, and whether we may message you in Telegram.
  • If you invite friends, we keep your invitation code, who came with it, when, and when the reward came. If your account was created by an invitation, we keep who invited you and when. We need this to give the reward once and no more than five times. The record of an invitation is deleted with the account of the invited person, and if the inviter’s account is deleted, only the date stays.
  • Notifications for you, for example about a like, a match, a new message or a decision on a photo. A notification holds its type, who it is from and which like, match, message or photo it is about, the outcome of a decision on a photo, the channel, for example the app or Telegram, when it was created, sent and read, the number of delivery attempts and the time of the next attempt. It holds no text.
  • Sessions. They hold only a random token and an expiry date, with no IP address and no device. A Mini App session lasts 12 hours and is never extended. On the website a session lasts 30 days and is extended when you come back.

We need this data to match people and to run the service. The legal basis is our contract with you, that is the Terms of Service. Under Armenian law this is consent that counts as given, because the data is needed for the contract you accept. This is Article 9, part 4, point 2 of the Law on Personal Data Protection. Wherever this text says “our contract with you”, it means this basis. For who you’re looking for, the basis is your consent, which you give by tapping “Start”.

Your consent to storing who you’re looking for lasts until you withdraw it or delete your account. Only our server sees this data and uses it for matching. It is stored in our Supabase database in Frankfurt and processed there by Vercel’s server functions. Other people and the team don’t see it directly, but matching shows you only to the people you’re looking for. We send it only in the /mydata file when you ask for it. You can withdraw the consent at any time by deleting your account with /delete or by writing to the controller through the contact in the “Who is responsible for your data” section. We then delete your account and everything linked to it.

Your birth time, weight, the text about you and answers to questions are optional. Your profile and matching can’t work without the rest.

Profile check

Before other people see your profile, we check its photos. We check that the photos show a person, that they aren’t an ad or someone else’s picture, that nothing is explicit and that the person looks adult. We also check that your name and bio hold no contact details, ads or rude words. An automatic check looks at the photos first, as described below. A person from the team decides everything unclear, and only the founder decides a suspicion that someone is under 18. You can also take a selfie check with a gesture that the app picks at random. It’s optional. The face on the selfie is then compared with your photos, and your profile gets the “Verified” badge. Who is on the team and what they see is in the “Service team” section.

While your profile photos are waiting for the check or need a fix, other people don’t see your profile. You have no feed and no matches during that time. The selfie doesn’t change this, your profile opens the same way without it. You see the result of the check in the app.

Every new photo also goes through the check before other people see it. While a photo is waiting for review, only you and the team see it. A rejected photo is also seen only by you and the team. You see it together with the reason, and it is deleted after 14 days. If a photo or a selfie looks like child sexual abuse, though, the account is frozen at once, and we report it to the INHOPE hotline and to the police. This applies to a photo that was already approved too. Such a photo is kept for the police. Nobody sees it in the service anymore, the team included, and it isn’t in the /mydata file. The selfie is still deleted after the decision. No automatic cleanup deletes a frozen account or its photos. Amazon Bedrock has its own automatic abuse protection. If it finds child sexual abuse in a picture, Amazon Web Services may learn of it too and report it as its rules and the law require.

A script checks every new photo. We send Amazon Web Services in Frankfurt only the picture itself, without the place it was taken or camera data. There’s no name, bio, city, birth date or id in it. Amazon Rekognition looks for explicit content, violence, hate symbols, faces and text and estimates age by eye. A language model in Amazon Bedrock looks at whether it’s a photo of a person. Drawings, memes and screenshots don’t count. Our server looks for phone numbers and links in the text on the picture and compares a hash of the photo with photos of other accounts. The script picks one of three. Approve, reject with a reason, or leave it to a person. The script may decide clear cases on its own, and a person from the team decides the rest. The script never decides on its own that you’re under 18. You see a rejection reason the same way as from a person, and under a reason the script gave you can tap “Ask for another review” once. A person then looks at the photo. The legal basis is our contract with you, the check keeps the feed to real adults.

The automatic check leaves the outcome, the reason code, the version of the rules and the numbers the script decided by, such as how sure it was that a photo is explicit or the age by eye. These are whole numbers without text. Neither we nor Amazon Web Services keep a copy of the photo, a face template or any other trace of it. The outcome is kept while the photo or the check record exists and is deleted with them. The /mydata file has the outcome, the reason and the time.

For each photo our server computes a short 64-bit hash. It shows that two photos are nearly the same, but the picture can’t be rebuilt from it. We compare it with photos of other accounts so one photo doesn’t appear in two profiles. The hash is kept with the photo and deleted with it.

The review page shows the selfie, all your photos, the gesture we asked for and where the picture came from, the camera or a file. It also shows your age in years, the attempt number and the reasons for earlier rejections. Your name and bio are there too, to check that they hold no contact details, ads or rude words. Your birth date, city, gender and who you’re looking for are not there. The reviewer may not save the selfie, forward it or take a screenshot of it.

The selfie is one image without location or camera data. It is stored encrypted in separate private storage at Supabase in Frankfurt. First the selfie is checked automatically through Amazon Web Services, as described below, and the reviewer sees it if the answer isn’t clear. If you tap “Let a person check it”, only the reviewer sees the selfie. Other people don’t get the selfie, and it doesn’t go to Telegram. We delete the selfie right after the decision. Without a decision, a sent selfie is deleted after 7 days, and one taken but not sent after 24 hours. If the storage didn’t answer at deletion, the hourly cleanup keeps trying until it erases the file. The service no longer gives such a file to anyone. Database backups don’t hold the images, so a deleted selfie can’t come back from them.

The selfie is checked automatically first. When you tap the selfie button, the selfie and up to three of your photos go to Amazon Web Services in Frankfurt. Amazon Rekognition compares the face on the selfie with the face on the photos, and a language model in Amazon Bedrock checks the gesture and that the camera took the shot. A photo of a screen doesn’t count. The badge usually shows up within a minute. If the answer isn’t clear, a person from the team looks at the selfie. Neither we nor Amazon Web Services keep face templates or face collections. We keep only the outcome and the similarity as a whole number in the check record. If you tap “Let a person check it” before the shot, the selfie goes nowhere else, and a person looks at it, usually within a day.

The legal basis for the selfie is your separate consent. You give it only if you choose the selfie check, by tapping “Get verified” at the end of sign-up or in your profile. The text above the button says who will see the photo and when it is deleted. Until you tap it, the camera doesn’t turn on. If you took a selfie and haven’t sent it yet, you can simply not send it, and it is deleted after 24 hours. Once it is sent, you can withdraw the consent until the decision by cancelling the badge request. The selfie is then deleted at once, and a new check asks for the consent again. After the decision the selfie is already gone, so there’s nothing left to withdraw. The consent covers one check and lasts until its decision. The selfie goes only to the reviewer from the team and to the services of the “Who else processes data” section. These are Supabase and Vercel, and with the automatic check Amazon Web Services too. The automatic check needs one more separate consent, to the automatic face comparison. You give it with the same tap of the selfie button, and the text above it says so. If you don’t want the comparison, tap “Let a person check it”, and then only the selfie consent is needed. You can withdraw it in your profile at any time. The saved comparison result is then deleted, and a person looks at your next selfies. A badge you already have stays. While the check runs you can cancel it, and then the selfie and the result are deleted and the consent ends.

The “Verified” badge only means that the face on the selfie matched your profile photos at the time of the check. At equal compatibility a profile with the badge comes earlier in the feed, and a profile without it is still seen by everyone it suits. We keep the time the badge was given. The badge goes away if none of the photos that were in your profile at the time of the check is left. Then you can take the check again. Without the badge you can start up to 20 new conversations a day, this protects against mass messaging.

Each check leaves a record without the image. It holds the attempt number, the gesture and a mark if it was swapped, where the picture came from, the camera or a file, when the gesture was given, the picture was taken, the profile was sent and the decision was made, the decision itself and the reasons for a rejection. It also notes what happened to our message in Telegram with the result and, if the check was handed to the founder, when that happened. The record is kept while the account exists and is part of the /mydata file. It is there to show that a person checked the profile, and for safety. If the reason was suspected child sexual abuse, we leave that reason out of the file. The time of a handover to the founder is a service mark. It is neither in the file nor in the app.

We are still confirming with a lawyer the legal basis for keeping this record. Once it is confirmed, this text will be updated.

If at the check or later you look under 18, the account is deleted at once with all its data, as with the /delete command. Only the founder decides this. If we may message you in Telegram, we send one message, without blame, about why the profile is closed and where to write if we got it wrong. For that the Telegram id is kept until it’s sent, no longer than 24 hours, then deleted. The exception is a photo or a selfie that looks like child sexual abuse. Then the account is frozen and the photo is kept for the police, as described above.

Service team

Profiles, photos and reports are handled by the service team. That is the founder and the helpers the founder gives access to. Each helper signs a confidentiality agreement before getting access. The team works in a separate admin panel.

The admin panel shows your name from the profile or its draft, your age in years and all your photos, including those waiting for review or rejected. It also shows where your check stands, whether access is closed and the profile paused, the dates of your account to the day, how many photos you have and how many reports there are about you, whether we may message you and your language.

Your birth date, gender, who you’re looking for and cities are not in the admin panel. The team sees your messages only through a report. A report from the chat, yours or about you, holds a copy of the last messages of the conversation, 50 at most. If someone complains about a recent conversation with you through the operator’s contact, only the founder may read it, also at most its last 50 messages. The team sees your bio at the profile check and in a report about you, because the check and a report may be about it. The selfie is visible only at the check, while it waits for a decision.

On the team, only the founder sees your Telegram id. In a person’s card the founder opens it with a separate button. The founder can also find an account by its Telegram id and sees the ids in the access list of the test version.

The team’s log records what the team does in the admin panel, together with the id of the account it concerns. For example, these are check decisions and decisions on photos, selfie views, opening the card of a person or a report, showing a Telegram id, handing a case to the founder and the decision on a report. It also covers every measure, among them freezing and closing access, granting and removing Zodiamor+, refunding Stars, granting and removing a team role, and signing in to and out of the admin panel. The entry about the founder deleting an account is written without the account id. A log entry holds the account id of the team member who acted, their role, the time, the action code, the numbers of the records and details as codes and numbers, for example the reasons for a rejection, the attempt number and a mark if the case was about that member. An automated freeze is written without a team member. A decision of the script is written with the version of the rules and the reason code, without the account or photo id. There are no names, photos, links or Telegram ids in the log. The log is there so that these actions of the team can be checked and a mistake or a misuse of access can be looked into. The legal basis is our contract with you. The Terms of Service say in “How we protect the service” that the team keeps this log and why. How long the log is kept is in the “How long data is kept” section.

If you are on the team, your role is kept in your account until it is removed, and the log writes your actions under your account id. Signing in to the admin panel is confirmed in our Telegram chat. A sign-in request is valid for 2 minutes and links the press in the chat to the browser window. The founder gets an alert about each sign-in, with no name or id. An admin session lasts up to 8 hours from sign-in and ends after an hour without actions. It holds only a hash of the token and times, with no IP address or device. In the browser the admin panel keeps only the session cookie, a sign-in cookie for 2 minutes and copies of photos in the normal cache for up to an hour. The role and the session are there so that only team members get into the admin panel. The legal basis is our contract with you, that is the Terms of Service and the confidentiality agreement every helper signs. The /mydata file shows the role, and /delete deletes it.

Reports and blocking

You can report a person and block them right away from the menu on their card or in your chat with them. A block works at once. You no longer see each other, and there are no notifications between you. If you had a match, the block ends it, and the conversation disappears for both of you. Lifting the block doesn’t bring the match back.

A report holds who reports whom, a reason from a list, a message of up to 500 characters if one was written, where the report came from, for example the feed, a match or the chat, the time, the urgency and the decision. It also notes whether the report froze the account, when it was handed to the founder if it was, whether we reported it to the police and whether we sent the outcome to the author and a message to the reported person. At the moment of the report it also stores a snapshot of the reported person’s profile. That is the name, the bio, the answers to profile questions, the age in years and the numbers of the photos with their status. If you add social media, their handles go into the snapshot too. The team sees them only in a report about you. The snapshot has no birth date, gender, who the person is looking for or cities, and the photos themselves aren’t copied. If the report comes from the chat, the snapshot also holds a copy of the last 50 messages of the conversation from both sides, with who wrote each one and when. For an edited message, the copy has the time of the edit and the earlier versions. The first version is kept in full, and of the later ones up to the four most recent are kept, each up to 500 characters long. A long version keeps its beginning and end with an ellipsis between them. If the copy comes out too large, long messages and their versions are shortened the same way, the first version too. Only after that are later versions dropped from the copy, and as a last resort whole messages too, the longest first. The text of a report and the snapshot never go into service logs or alerts.

The team handles reports. Only the founder sees the name of the person who reported. Everyone else on the team sees only whether that person’s profile passed the check, how old their account is, under a week, under a month or older, how many reports were sent from their account and how many of them were confirmed. On the team, only the founder sees which reports you send.

The reported person never learns from us who reported them, and the author isn’t in their /mydata file either. If there was no violation and the account wasn’t frozen, they don’t learn about the report at all. If a report froze the account, they see it at once, and we tell them the reason, as described in the “Zodiamor messages in Telegram” section. After the decision the author gets one message from us with the outcome, with no name and without the measure we took.

Only the block works at once. A report of the most urgent kind, for example about threats, violence or someone who may be under 18, also freezes the reported account automatically until the founder checks it. This happens only if the author’s profile passed the check and the author already liked or passed this card or has a match with this person. An author can trigger such a freeze at most once in 30 days. It doesn’t touch an account that is closed or already frozen. What happens next is in the “Closed access and freezing” section.

Your reports and blocks are in the /mydata file. For each of your reports it has the reason, your message, where the report came from, what stage it is at and the dates. The team’s marks on a report are not in the file, because they show which measure we took. These are the urgency, the decision and the measure, the account freeze, the handover to the founder and to the police, and the times of our messages in Telegram. The file also has no snapshot of anyone else’s profile and no copy of a conversation. It has no reports about you, so it can’t give away who sent them.

We are still confirming with a lawyer the legal basis for the text of a report, the profile snapshot and the copy of a conversation. Once it is confirmed, this text will be updated.

Closed access and freezing

If the community rules are broken, the team may close access to an account. Then nobody sees the profile, and all of the account’s sessions end. If a profile check is waiting for a decision at that moment, it is cancelled and the selfie is deleted. You can still sign in, but the app shows only the “Access closed” page with the reason, the controller’s contact and a hint on how to delete the account.

A freeze hides the profile too. It is set by a report of the most urgent kind, as described in the “Reports and blocking” section, or by a person from the team after a report. While the account is frozen, the app shows that it is restricted, along with the controller’s contact, and we tell the reason in Telegram. Only the founder can lift a freeze. A freeze because of a photo that looks like child sexual abuse is described in the “Profile check” section.

When access is closed or an account frozen, the profile keeps the reason code and the time of the measure. They are there so that the measure holds, so that you can see the reason and so that the period of a closed account can be counted. The legal basis is our contract with you, that is the Terms of Service and their community rules. When access is given back or the freeze lifted, the code and the time are erased. The /mydata file shows them. If the reason was suspected child sexual abuse, we leave that reason out of the file.

If the team removes a social media handle after a report, for that network we keep a mark saying so and its time. They are there so that we can show you the line “Handle removed by the team” in your profile. The legal basis is our contract with you, that is the Terms of Service and their community rules. The mark is erased when you save a new handle for that network or delete your account. The /mydata file shows it.

A closed account is kept for 12 months from the time of the measure and then deleted. Until then, the cleanup of accounts that didn’t pass the check doesn’t delete it either. You can delete it earlier with the /delete command. The mark of the closing stays on the list of closed accounts, see the next paragraph. A freeze has no period of its own yet. Until the founder lifts the freeze or closes access, no cleanup deletes a frozen account.

If access is closed for breaking the rules, we add your Telegram id to the list of closed accounts. The list keeps only a fingerprint of the id, computed with our secret key. Without the key the id cannot be read from the fingerprint. It also keeps a rough group of the reason, safety, content, fraud or other, and the date. There is no name, photo, text or account id in the list. The list exists so that a person whose access was closed cannot delete the account and sign up again right away. So the row stays after the account is deleted, with /delete too, and for now it has no end date. If such an id opens the Mini App, our Telegram chat or the sign-in on the website again, it sees that access is closed. If access is given back, we delete the row. You can appeal the measure through the operator’s contact. The basis is our contract with you, that is the terms of use and their community rules. We are still checking the period and the basis with a lawyer.

In serious cases the founder may delete an account for breaking the rules. The account is then deleted with all its data, as with the /delete command, and reports and the team’s log follow the periods in the “How long data is kept” section. A frozen account and an account with a photo kept for the police are never deleted this way. We don’t write about the deletion, because the mark of whether we may message you is deleted together with the account. You can challenge the deletion, but deleted data can’t be brought back.

You can challenge a measure through the controller’s contact in the first section. How this works is described in the Terms of Service.

We are still confirming with a lawyer whether these periods fit a closed account and how long a freeze may last. Once we have the answer, this text will be updated.

Chat

You can write to a person only after a match. The chat has text only, without photos, voice messages or files. The text is stored in our Supabase database in Frankfurt, in the European Union. It reaches Telegram only in the /mydata file you ask for, and that file holds only your own messages.

With each message we keep who sent it and when, and if it was edited or deleted, the time of that. We also keep the time of the last change you both see, that is an edit, a reaction or a deletion. For each of the two people we also keep a read mark, that is up to which message they have read the conversation and when.

When you read a message, the other person sees a second check mark under it. While a message waits for the check, it doesn’t count as read.

While a conversation is open, our server tells the other person’s screen at once that there is a new message, an edit, a reaction or a read mark, and the screen fetches it from us. While you write, the other person sees “typing”. These signals go through Supabase Realtime and carry no text and no name. We don’t keep them.

People you have a match with can see whether you’re online right now. While the app is open on your screen, they see “online”. When you’re not in the app, they see nothing, no mark and no time you were last online. The mark goes through Supabase Realtime, and we don’t keep it. Your status isn’t shown in the feed or in “Likes”. In “Settings” you choose who sees when you’re online, all your matches or nobody, and you can always or never show it to the matches you pick. This is free and works both ways. If you hide your status from someone, you don’t see their status or the second check mark under your messages, and they don’t see it under theirs. With Zodiamor+ you see the status and the second check mark of people who don’t hide them, even while you hide your status. While Zodiamor+ is open for free, anyone can do this. A hidden status still shows for about 30 seconds after you write to someone, read their message or type to them. Someone you block never sees that you’re online.

You can edit your own message at any time, and it gets an “edited” mark. Earlier versions are kept with the message and only reviewers see them, if someone complains about the conversation.

You can put one reaction from a set on a message and later change or remove it. You both see the reaction, and no notification tells of it. For a reaction we keep who put it, which one and when. You can also reply to a message, and a short quote of the original then shows above the reply. For a reply we keep which message it answers.

You can delete a message for yourself, and then it disappears only for you, while the other person sees it as before. For this we keep which message is hidden and when. You can delete your own message for both people at any time, and then it disappears for both of you at once. Its text and earlier versions are kept for 30 more days for review only. During these days the text and the time of deletion also stay in the sender’s /mydata file. If someone complains about the conversation within these days, the copy in the report also gets such a message with a deletion mark, and that copy lives by the report periods. After 30 days the message is erased completely.

The two of you see the conversation. The service team sees messages in two cases only. The first is a report from the chat. At the moment of such a report, it stores a copy of the last 50 messages of the conversation from both sides, with who wrote each one and when, and with the earlier versions of edited messages, as described in the “Reports and blocking” section. Every time the team views these messages, it is written to the team’s log. The second is a complaint about a recent conversation through the operator’s contact. Then only the founder may read it, at most its last 50 messages. No external AI model or other service reads the messages. Only our server and database from the “Who else processes data” section handle them.

Our server looks in a message for a link, a username from Telegram or another service, an email address, a phone number, a card number or a request for money. If the sender’s account was younger than 7 days when the message was sent, the receiver sees a calm hint under it. The hint stays on that message later too. The sender doesn’t see it. The server works the hint out each time it shows the message and stores it nowhere. For this the text doesn’t leave our server. Links in the chat can’t be clicked by anyone.

Until the other person answers, you can send at most 3 messages in a row. There is also a limit of 30 messages a minute and 600 a day. How such limits are counted is in the “Protection from abuse” section.

A conversation is kept while the match lasts. What happens to it after an unmatch, a block or an account deletion is in the “How long data is kept” section.

We tell you about new messages in Telegram only if you let us message you. How this works is in the “Zodiamor messages in Telegram” section.

The /mydata file has your own messages under each match with their earlier versions, your reactions, the messages you deleted for yourself and the time of your last read mark. Another person’s message that you reply to, react to or delete for yourself is named in the file only by whose it is and when it was sent. The other person’s messages aren’t in the file.

The legal basis for the chat is our contract with you, that is the Terms of Service and their community rules, as for the rest of the service. The basis for the copy of a conversation in a report is described in the “Reports and blocking” section.

Zodiamor+ payments

When you buy a Zodiamor+ pass, we keep the order. It holds your account, the pass, the payment method, the amount and currency, the state of the order, the payment id in Telegram and the time the order was made and paid.

From Telegram we keep a record of the payment. It holds the kind of record, its number, the amount, the currency, the order number and the payment id. We don’t write your name, username, language or Telegram’s order details to the database.

We also keep how long Zodiamor+ lasts. That is the start and end of the access, where it comes from, for example a pass or the Founder program, and the time and reason if the access is closed, for example after a refund.

Telegram collects no name, phone, email or address for us. Telegram runs the payment as a separate controller.

For a refund we take your Telegram id from the account and the payment id. Once a day we check our orders against our list of Stars in Telegram by payment id, amount and time only, and keep nothing from that list.

We need this to sell the pass, open Zodiamor+, return Stars and keep accounts. The basis is the contract with you.

Zodiamor messages in Telegram

If you press the consent button in our chat in Telegram, we save a subscription. It holds your Telegram id, language, where the subscription came from, meaning the page or link that opened our chat and its code, and the version and time of your consent. It also holds the time of a beta invitation, the time the message was sent and the number of delivery attempts, and after an opt-out its time and reason, meaning an opt-out in the chat itself or blocking the chat.

Until the button is pressed, we write nothing to a subscription.

The subscription lets us message you once when sign-in opens for you. There are no other messages on this subscription. The basis is your consent, and you can opt out with /stop.

Zodiamor sometimes writes in Telegram to everyone who uses it about what’s new in the app and about offers. That’s no more than once a week and only between 10:00 and 21:00 in your city. “News and offers” are on from the start, and you can turn them off at any time in “Settings” or by sending /stop to our chat in Telegram. For that we keep whether your news is on and the time of the last change, and for each mailing we keep for 8 days a mark of whether the message went to you. We don’t keep who opened a message, only the total number. The legal basis is our interest in telling the people who use Zodiamor about it. You can opt out at any time. Notifications about likes, matches and messages don’t depend on this.

If you have an account, it keeps a mark of whether we may send you notifications in Telegram. Any message you send to our chat sets it, and so do unblocking the chat and a permission to message you that Telegram passes to us, for example when you sign in on the website. Signing in to the Mini App sets it too, when the launch data says we may already message you. If you block our chat, the mark is removed.

If we may message you, we tell you about likes, star signals and matches, and about new messages too. For messages we write once per conversation, until you read it. The next such notification comes only once you read the conversation and a new message arrives in it. A notification about likes, star signals and matches only says what kind of event it is, without a name, photo, age, city or any text of a conversation. These notifications only come from real people. They come right away and with sound, at any hour.

When someone writes to you in the chat, a notification comes with the name from that person’s profile and the number of new messages. The text of the messages isn’t in it.

After a payment we tell you the day Zodiamor+ is open until, and after a refund that the Stars came back.

If we may message you in Telegram, we tell you the result of the profile check. That is one message per decision, and one more if the check expires without a decision. If a profile didn’t pass, the message names the reasons with the same text as the app. If the reasons include an explicit picture, violence or hate symbols, the message stays general, and the reasons are only in the app. Your name and photos aren’t in the message. It comes right away and with sound, at any hour. If the account is deleted because of age, one message comes, as described in the “Profile check” section. If the account is frozen because of a photo or selfie that looks like child sexual abuse, we don’t write.

We also tell you the decision on each new photo, whether it passed the check or not. The photo itself isn’t in the message. The message names the reason for a rejection with the same text as “Profile”. If the reason is an explicit picture, violence or hate symbols, the message stays general, and you see the reason only in “Profile”. This message also comes right away and with sound. We don’t write about a photo that looks like child sexual abuse.

If we may message you, we also tell you about measures. When access is closed, the account frozen, an approved photo removed or the bio cleared, we write the reason, which rule was broken, whether the decision was automated and how to challenge it. If you report someone, after the decision we send you the outcome with no name and no measure. These messages also come right away and with sound. The AI guide never writes them. In case of suspected child sexual abuse we write nothing, neither at once nor later. The app then shows only a text without a reason and the controller’s contact.

Star Dates and the shared compatibility page

These pages work without an account.

The server only turns the birth date you enter into a sign and a decan and doesn’t save it.

A link to share holds only the decan of the person sharing it, the page language and a random link code. It has no name and no birth date.

Statistics

To understand how the service works, we count numbers per day. For example, how many people signed up, how many likes and matches there were and how many people came back 1, 7 and 30 days after signing up. The team sees these numbers in the admin panel, with no people in them. We also count the decisions of the automatic check by outcome and reason, and how many of them matched a person’s decision. For each mailing we count how many people it went to and how many times its button opened the app. We also count how many times a day the news was turned on and off. There are no ids in these numbers.

The numbers hold no account id or Telegram id, network address, device, city, birth date, sign, decan, friend link code or who you’re looking for. They can be split only by traits from a short list, for example by market or by gender. The numbers never affect the price, the order of the feed or notifications.

We count the returns after 1, 7 and 30 days by the week of signing up, and only when that week has at least 5 accounts. On the “Numbers” screen of the admin panel any number from 1 to 4 shows as “fewer than 5”.

The website and the Mini App collect events, for example opening a page or pressing a button, and send them to our server without cookies and without ids. The server only adds them to the numbers of the day and keeps neither the network address nor the device. Telegram launch data never gets into the events. So that events can’t overload the server, their number is limited by network address. How that counter is kept is described in the “Protection from abuse” section.

The numbers are kept for 400 days in our database in Frankfurt. Besides the admin panel, they go only into a summary the founder gets in a service chat in Telegram. The /mydata file and the /delete command don’t touch them, because they hold no ids.

If we turn on Vercel Web Analytics on the public pages of the website, it will work without cookies. The page address will reach it without Telegram launch data and without the friend link code.

We are still confirming with a lawyer whether this counting needs your consent. Once we have the answer, this text will be updated.

Protection from abuse

To keep the service from being overloaded, we count requests by network address, Telegram id or account id. In the database a counter keeps only a hash of the address or id, made with a secret key. The address or id itself is never stored there.

If you have an account, the basis is our contract with you. The Terms of Service say in “How we protect the service” that we limit and count requests. For people without an account, for example on Star Dates, on the friend page or in our Telegram chat before signing up, we are still checking the basis with a lawyer. Once it is confirmed, this text will be updated.

Who else processes data

Data is processed by the services Zodiamor runs on.

  • Supabase, a US company, keeps the database, the photos and the encrypted selfies in the European Union, in Frankfurt.
  • Vercel, a US company, runs the website and the server. The server functions run in Frankfurt, and photos and selfies pass through them on their way to storage.
  • Amazon Web Services, a US company, checks photos and, with the automatic check, selfies in Frankfurt, in Amazon Rekognition and Amazon Bedrock. AWS doesn’t keep the pictures or results and doesn’t train on them, this is turned off by a policy of our account.
  • Cloudflare, a US company, will handle the site’s address once the service has its own domain.
  • Telegram is responsible for its own data as a separate controller and runs payments in Stars.

We use no email services and no captcha. We don’t sell data or pass it to ad networks. We don’t show your photos and bio outside Zodiamor or use them in ads. There is an exception. If the law requires it, we pass data to the police, a court or another public authority. This happens, for example, when someone’s life is under threat or child sexual abuse is suspected. In the second case we also report to the INHOPE hotline, as described in the “Profile check” section. We are still confirming with a lawyer what we have to pass on and in which cases. Once we have the answer, this text will be updated.

The controller works from Armenia, and the data is stored in the European Union, in Germany. We keep the database and the files at Supabase and the server functions of Vercel in Frankfurt. This is a transfer of data to another country under Article 27 of the Law on Personal Data Protection. Its basis is Article 27, part 2. As far as we know, Germany is on the list of countries where data protection is adequate. Supabase and Vercel are US companies, and under their data processing terms they may access the data from the US too. That access is needed to run the service, which is the basis of Article 27, part 1. Amazon Web Services is a US company too. We send photos and selfies only to its Frankfurt region, and access from the US is possible under its data processing terms. It’s the same basis of Article 27, part 1. Data goes to Telegram only when you use our chat in Telegram. These are our messages about your account, such as the check result and notifications if you let us write to you, and the /mydata file when you ask for it. The basis is our contract with you and your own request. Whether Germany is on the list and whether access from the US needs a permit from the Agency, we are still checking with a lawyer. Once we have the answer, this text will be updated.

Other people see your card in the feed, in “Likes” and in matches. It shows your approved photos, name, age, sign and decan, your city and the city where you’re looking if it’s a different one, a rough distance to your city, your height, interests, answers to profile questions, your bio, how compatible you are with them and the “Verified” badge if you took the selfie check. Your birth date and time, your gender and who you’re looking for are not on the card. On your profile page, people you have a match with see which signs Venus and Mars were in on the day you were born. Together with your age, sign and decan, these signs sometimes narrow your birthday down to a few days. Your actual birth date and time stay hidden from other people. Other people don’t see your selfie or photos that are waiting for review or were rejected. People you have a match with also see whether you’re online right now. How it works and how to hide it is in the section “Chat”. Your weight, if you add it, is seen only by people who open your whole profile. If you add social media, people who are shown your profile also see their icons, the same way as your bio. When you erase a handle, the icon disappears for everyone, but we can’t take back anything a person already opened. If your account is less than 7 days old, a calm hint sits under the social media icons, and everyone who is shown your profile sees that the account is new. The server works the hint out from the date the account was created each time it shows the profile, and stores it nowhere.

If you like someone or send them a star signal, they see your card in their “Likes” and whether it’s a like or a signal, until they answer. If they answer with a like, you have a match. If you send someone a star signal, they see the “Star signal” mark on your card in their feed and in “Today’s star picks”. A person never learns that you skipped them.

If “Likes” are blurred, you can open one person a day. We keep whom you open and when. The record is deleted when you answer the like or the person leaves “Likes”, and lives no longer than 30 days.

How long data is kept

  • Your account is kept until you delete it or the founder deletes it for breaking the rules. What happens to a closed or frozen account is described in the “Closed access and freezing” section. A social media handle is kept until you erase it or delete your account. The mark that the team removed a handle is kept until you save a new handle for that network or delete your account.
  • A profile draft that hasn’t changed for 30 days is deleted. Uploading a photo or a selfie counts as a change too. An account without a finished profile is deleted once three things are true. It was created more than 30 days ago, its draft hasn’t changed for 30 days or is already gone, and none of its sessions is still valid.
  • A photo is kept until you delete it or delete your account. You can delete your last approved photo only once a new one is approved. You can’t delete your only photo that isn’t rejected. Add another one first. A rejected photo is deleted after 14 days. This period doesn’t apply to the photos of a frozen account. Freezing is described in the “Profile check” and “Closed access and freezing” sections. A deleted photo disappears from the service at once, and its files are erased right away. If the storage didn’t answer, the hourly cleanup keeps trying until it erases them. A cached copy may still open through a link given out earlier, for up to an hour after the deletion.
  • A check record is kept while the account exists. How long the selfie lives is in the “Profile check” section. If a profile hasn’t passed the check, no check is open, none of the account’s sessions is valid and there has been no activity for 30 days, the account is deleted. This rule doesn’t apply to a frozen account, or to a closed account until its 12 months are over. The outcome of the automatic check lives as long as the photo or the check record.
  • Each entry of the team’s log is kept for at least 12 months, and the database doesn’t let it be deleted earlier. There is no cleanup of old entries yet, so they live longer. We are still confirming with a lawyer how long to keep them after 12 months. The id of the account an action concerns stays in the log after the account is deleted. It is a random number with no name or Telegram id. The id of the team member who acted is erased from the log together with their account.
  • The message of a report and the profile snapshot with the copy of a conversation are erased 90 days after the decision, and the codes of the report stay. A report without a violation is kept for 6 months after the decision, a report with a measure for 12 months, an open one until the decision. No cleanup deletes a report we passed to the police, and we are still confirming its period with a lawyer. If one of the two people deletes their account, the report stays without their id, and the snapshot lives by the same periods. A block is kept until it is lifted and while both accounts exist.
  • A conversation is kept while the match lasts. The earlier versions of an edited message are erased together with it. A message deleted for both people is erased 30 days after the deletion together with its earlier versions. Reactions and marks of deletion for yourself are erased together with the message. After an unmatch or a block it disappears for both people at once, and its text and read marks are erased 30 days later. These 30 days leave a trace for a complaint about a recent conversation through the operator’s contact. Only the founder may read such a conversation, only on such a complaint, and at most its last 50 messages. If a conversation has no new message for 12 months, its messages are erased and the match stays. When either of the two deletes their account, the match and the whole conversation are erased for both at once. If the account of one of the two is frozen, no cleanup erases their conversation until the decision, like the rest of that account’s data. The copy of a conversation in a report lives by the periods of the report.
  • Orders and payment records are kept for accounting. After the account is deleted, the order stays without the account and the payment record is cleared. The payment id stays in the order, and with it Telegram can show in its Stars history who paid. How long to keep orders after a deletion we are still checking with a lawyer. After the account is deleted we can return Stars only on request through /paysupport from the same Telegram account.
  • A row of the test version’s access list is kept until it is removed or its end date passes, and for at most 30 days if there is no account. If an id is also still written in the Vercel settings, it stays there until the founder removes it.
  • A team role is kept until it is removed, an admin session for up to 8 hours, and an expired session is deleted within an hour. The cleanup erases a sign-in request to the admin panel about a day after it ends.
  • An expired session is deleted within an hour.
  • A notification in the app is kept until you read it and for 90 days after that. Notifications about likes and star signals count as read when you open “Likes”, and a notification about a new message when you read the conversation. The app has no list of the other notifications yet, so they are kept until your account is deleted. The same goes for a notification about a message if the conversation disappears before you read it. A notification outside the app, for example in Telegram, waits to be sent and is kept for 30 days once sent. If it can’t be delivered or is no longer true, for example the photo was deleted or the message already read, it is deleted.
  • A subscription in our Telegram chat is kept until the launch message, for at most 12 months from your consent. After the message it is kept for 30 more days, and after you opt out for 7 days. If the message can’t be delivered after 5 tries, the subscription is deleted 30 days later.
  • After you delete your account with /delete or the “Delete profile” button, we keep proof of your consents for 3 years. For each consent in the profile setup, for the selfie and for the subscription in our Telegram chat it holds only the type of consent, the version of the text, the time of the consent and of its withdrawal, and a hash of your Telegram id computed with a secret key. It holds neither the id itself, nor a name, nor any other data, and without the key it can’t lead to a person. Under Armenian law the controller must prove a consent, so this record is needed if a consent is disputed. The basis is this duty of the law, Article 9, part 8. We are still checking the 3-year period with a lawyer.
  • Rate limit counters and the keys of repeated requests live up to 24 hours, and the counters of the shared cards up to 30 days.
  • The daily statistics numbers are kept for 400 days.

Your rights

You can find out what data we have, correct it, delete it, restrict its processing, get it as a JSON file and object to its processing.

If the script rejected a photo, you can ask for a person to look at the decision. There’s an “Ask for another review” button under the reason for that.

You can withdraw a consent at any time. Processing before the withdrawal stays lawful.

When this text changes, the app shows a sheet with links to the new text. You can go on only after you tap “I accept”. We record which version you accept and when.

You can complain to the Personal Data Protection Agency of Armenia or to the supervisory authority of your country.

Requests go to the controller’s contact from the first section. Armenian law sets the time to answer.

How to get and delete your data

Sending /stop to our chat in Telegram cancels your subscription right away. Its data is deleted after 7 days.

Sending /mydata to our chat in Telegram gets you a file with your data there. It leaves out what belongs to other people or protects them, for example other people’s messages and reports about you. It also leaves out service records, for example the keys of repeated requests, the hashes of the counters and the time a check or a photo was handed to the founder. The file goes through Telegram and stays in the chat until you delete it. You can get it once a day. Photos are described in the file without the images themselves, and you can see your photos in the app. The selfie isn’t in the file.

The /delete command deletes your account and subscription right away, together with your photos, selfie, check records and blocks. This can’t be undone. Your matches and every conversation in them are erased for both people. The row of the test version’s access list goes together with the account. If your Telegram id is also written in the Vercel settings, /delete doesn’t remove it from there. The founder does that by hand at your request. You can write to the founder through the contact in the “Who is responsible for your data” section. Reports you are part of stay without your id, and the profile snapshot in a report about you, the copy of the conversation from both sides in a report you filed from the chat and the service team’s log live by the periods of the “How long data is kept” section. The proof of your consents also stays, without your id, and its period is in the “How long data is kept” section too.

The “Delete profile” button in your profile deletes the account the same way. In rare cases, for example for a frozen account, the button won’t work, and the app suggests writing to support.

Telegram keeps our chat with you, and you can delete it there.

Cookies and the rest

On the website we set only the cookies we need. They remember your language and, after you sign in, your session. While you sign in with Telegram, they also remember for a few minutes that the sign-in started in this browser.

In the Mini App, while the tab is open, it keeps a mark that it was launched in Telegram. The mark also says whether you have Telegram Premium. It helps show the right ways to share, for example a link in a story, which only Telegram Premium has. Later the mark will help tell Mini App visits apart in statistics. After you sign in, the tab also keeps a session token together with a hash of the launch it was issued for. The token goes only to our server. When you sign out or open the Mini App again, the tab forgets it.

The feed sorts people by compatibility first. At equal compatibility, profiles with the “Verified” badge come earlier, then the more complete ones, and after that the order depends on what suits you both and on activity. This is no decision with legal effects. There are two kinds of automated decisions about you. The first is a freeze after a report of the most urgent kind, described in the “Reports and blocking” section. The founder checks it, and only the founder can lift it. The second is the decisions of the script on photos and, with the automatic selfie check, on the “Verified” badge. The script decides only clear cases, described in the “Profile check” section. You can hand a rejection of a photo by the script to a person with “Ask for another review”, and after “Let a person check it” a person always looks at the selfie.