Privacy Policy

Effective date: October 23, 2026

Draft — pending legal review.

The Policy describes what personal data of Users Siamora processes, for what purposes, on what legal basis and for how long, who it is shared with and what rights the User has. Data is used only to run the Service, keep it safe and communicate with the User; there are no ads, no tracking and no sale of data.

1. General provisions

1.1. This Privacy Policy (hereinafter the "Policy") governs how the personal data that the User provides when using the Siamora mobile application and the siamora.net website (hereinafter together the "Service") is processed and protected.

1.2. The personal data operator is Siamora (hereinafter the "Administration"). It is the Administration that decides what data the Service collects and why.

1.3. By creating an account and using the Service, the User confirms that they have read the Policy. If the User does not accept its terms, they must stop using the Service. Consent to the processing of location and biometric data is requested separately, in the app, before such processing begins.

1.4. The User can reach the Administration at any time at support@siamora.net.

2. Summary

• The Service collects what is needed to run a dating app: the User's profile, likes and chats. Nothing more.
• No ads, no advertising partners, no tracking across other apps or websites. The Administration never sells or rents Users' data.
• Selfie verification is optional. The selfie is deleted immediately after the face comparison; only the result is kept.
• Location is used to place the User on the grid and to show how far away other people are. Others see only the city and an approximate distance in whole kilometres, never the exact location.
• Chats are encrypted on the Administration's servers, but they are not end-to-end encrypted. The Administration can technically read them, and does so only to handle reports and lawful requests.
• The User can delete their account at any time directly in the app (Settings → Delete account); the profile, photos and chats are deleted right away, except copies attached to a report (see clause 9.4).

3. What data the Service collects

3.1. Account

The email address and a hashed password, or the Apple ID if the User uses Sign in with Apple (the Service receives the identifier and the email address Apple passes on, which may be a private relay address). Session and refresh tokens are also stored so that the User stays signed in.

3.2. Profile

Nickname, date of birth, gender and who the User is looking for, and photos. Optional: relationship goal, a short bio, height and weight, education, whether the User has children, attitude to alcohol and smoking, languages and interests. Every optional field can be left empty and filled in or cleared later. The User's gender and who they are looking for decide whose profiles the User sees and who sees theirs; they are not shown on the profile (see section 6). If the User sets feed filters (age, distance, interests and so on), they are stored with the account and applied to the User's grid. Nobody else sees them.

3.3. Location

If the User allows the location permission, the app sends the device location and the Service stores the precise coordinates. They are used to sort the grid by distance and to show how far away someone is. The User's current city and country of origin are part of the profile other people see.

The User's coordinates are never shown to other users. The distance they see is rounded to whole kilometres and is calculated from an area of about 1 km around the User, not from their exact position, so it cannot be used to pinpoint where they are. If the User would rather not share their location, they can deny or withdraw the location permission in the device settings. The app still works, but distances and nearby results become much less useful.

3.4. Verification selfie

A selfie taken with the device camera, only if the User chooses to verify their profile (see section 4).

3.5. Activity

Likes and passes (a pass hides that profile for 7 days), matches, blocks, and the time of last activity.

3.6. Messages

The text, photos and heart reactions the User sends in chats, including the fact that a message was edited or deleted.

3.7. Reports

When the User reports someone: the reason chosen, the comment, and the message or profile reported. At that moment the Service also saves a copy of the reported profile (its text and photos) and of up to 50 messages of the conversation, so that a moderator can check the report even if something is changed or deleted later.

3.8. Device and technical data

The push notification token, so that notifications can be delivered. If the app crashes, the Service receives a crash report that contains an internal user id, the device model, the operating system and the app version — never messages, email address or photos. The servers also keep standard technical logs needed to run and secure the Service.

3.9. What the Service does not ask for

The Service does not ask for passport details, identity documents, a phone number or payment details.

4. Biometric data (selfie verification)

4.1. Verification is optional and always starts on the User's initiative.

4.2. Before the check, the app explains it on a separate screen and asks for explicit consent; the moment the consent is given is recorded. Only then does the camera open, and the selfie together with the main profile photo is sent to Amazon Web Services (the Rekognition face comparison service, in the EU — Frankfurt, Germany) to check whether the faces match. AWS acts as the Administration's processor: it works on the Administration's instructions and does not use the User's images for its own purposes.

4.3. A face template made from a selfie is biometric data, therefore:

• the selfie is deleted from storage immediately after the comparison, whether it succeeds or not;
• only the outcome (verified or not verified), the date of the check and the date of consent are kept;
• if the User changes their main profile photo, the verification is reset and the User can verify again;
• consent can be withdrawn by writing to support@siamora.net or by deleting the account; the verification check mark is then removed from the profile.

4.4. Face recognition is not used for anything else: the Administration does not use it to identify the User elsewhere, to search for the User in other photos or for advertising.

5. Purposes and legal bases of processing

5.1. The Service uses data only for the purposes listed in the table.

5.2. Where processing is based on consent, the consent can be withdrawn at any time. Withdrawing consent does not affect the lawfulness of processing carried out before it was withdrawn.

6. What other users see

6.1. Other users of the app see the User's profile — and of it, only what the User filled in and what is worked out from it:

• nickname and age (not the date of birth);
• current city and an approximate distance in whole kilometres;
• photos and the "About" text;
• the kind of relationship the User is looking for (dating, friendship or a relationship);
• height and weight, education, whether the User has children, and attitude to alcohol and smoking;
• zodiac sign, worked out from the date of birth — it can be hidden in the profile;
• country of origin, languages and interests;
• the verification check mark, if there is one.

6.2. A field left empty or answered "Rather not say" is not shown. The User's gender and who they are looking for are not shown to other users: they are used only to decide whose profiles appear in each other's grid. Because that works both ways, someone who finds the User's profile in their grid can guess that the User might be interested in someone like them. Other users never see the User's date of birth or coordinates. The zodiac sign narrows the birthday down to about a month; if the User would rather not share that, they can hide it.

6.3. Everything the User puts into their profile becomes available to other people using Siamora. The User should fill in only what they are comfortable with others knowing: anything visible in the app can be copied or screenshotted.

6.4. The grid is ordered using distance and recent activity, so being active makes the User more visible. Messages are visible only to the person the User is chatting with.

7. Sharing data with third parties

7.1. The Administration does not sell or rent personal data, and has no advertising partners. Data is shared only with the following processors and recipients:

• Amazon Web Services — the Rekognition face comparison used for verification, in the EU (Frankfurt, Germany). AWS receives only the selfie and the main profile photo, only for the check; photos and chat images are not stored with AWS.
• Google Firebase Cloud Messaging — delivery of push notifications (the push token and the notification content).
• Sentry — crash reporting, containing only an internal user id plus device, OS and app version.
• Apple — if the User uses Sign in with Apple, Apple handles the sign-in and passes on the identifier and email the User agreed to share.
• Email provider — to send account emails (email address confirmation and password reset), and to receive and answer support messages and reports.
• Hosting provider — servers that run the Service and hold the database and the storage for photos and chat images.

7.2. Each of these recipients may use the data only to provide their service to the Administration, and must protect it at least as well as the Policy provides.

7.3. In addition, data may be disclosed:

• to public authorities — when the law requires it;
• to a buyer or successor if the Service is sold or merged — the Administration will give notice in advance, and the Policy continues to apply until the User is told otherwise;
• to anyone else — only with the User's consent.

8. International transfers

8.1. The Service's servers, which also store photos and chat images, are located outside Thailand and the European Union. If the User uses the Service from Thailand or from any other country, their data is transferred there.

8.2. Some processors work in other countries: Sentry in the European Union; Amazon Web Services in the European Union (Frankfurt, Germany), only for the face comparison during selfie verification; Google (Firebase Cloud Messaging) and Apple in the United States and other countries where they run their services. Not all of these countries are recognised by Thailand as providing an adequate level of personal data protection: their laws may protect data less than the law of the User's own country, and their authorities may be able to request access to it.

8.3. Data is transferred to these countries only as far as it is necessary to provide the Service under the public offer — the exception for performing a contract in Section 28 of the Thai PDPA. For users in the EU/EEA and the UK, the corresponding GDPR rules apply.

8.4. The Administration may later move the storage of photos and chat images to a cloud provider in another country. Before that happens, the Policy will be updated and the User will be notified in advance, as described in section 15.

9. How long data is kept

9.1. While the account exists — the profile, activity and chats are kept so that the Service works.

9.2. When the account is deleted — in the app (Settings → Delete account), the account, profile, photos, chats and everything else the app stores about the User are deleted right away, except copies attached to a report (see clause 9.4); a request by email is carried out by the Administration within 15 days. Deletion removes the conversations for both sides: the people the User was chatting with lose those conversations entirely, not only the User's messages. Crash reports keep only an internal user id and expire with the crash-reporting provider's retention period; server logs are kept for a short time.

9.3. Verification selfie — not retained at all; it is deleted immediately after the comparison.

9.4. Reports — a report and the copies saved with it are kept for 12 months, even if the person who filed the report or the reported person deletes their account, and then deleted. Records of moderators’ actions on reports, including each time they view a report’s copies or search for a profile, are kept for the same 12 months and then deleted.

9.5. Data that must be kept by law — kept for as long as the law requires, and no longer.

10. Security

10.1. The Administration takes the following security measures:

• all traffic between the app and the servers is protected with TLS;
• chat messages are encrypted at rest with AES-256-GCM;
• photos and chat images are kept in private storage and delivered through short-lived links, not public URLs;
• passwords are stored only as a hash, never in a readable form;
• access to production data is limited to the few people who need it to run the Service.

10.2. Chats are not end-to-end encrypted. The Administration holds the keys, so it is technically able to read messages. This is done only when there is no other way: to review a report, to investigate abuse of the Service, or to answer a lawful request from an authority. Siamora chats should not be treated as a confidential channel.

10.3. Moderators read a conversation only from the copy saved with a report — only the conversation between the person who reported and the person reported, never other conversations — and every time a moderator opens that copy, this is recorded.

10.4. Transmitting data over the internet always carries risks, and nobody can guarantee absolute security. The Administration is not responsible for the disclosure of information that the User has shared with other users or third parties themselves.

11. The User's rights

11.1. Depending on the country where the User lives (Thailand's PDPA, the GDPR in the EU/EEA and the UK, and similar laws elsewhere), the User has the right to:

• access their personal data and get a copy of it;
• correct it — most profile data can be edited directly in the app;
• delete it — delete the account in the app (Settings → Delete account) or ask the Administration to do so; see the account deletion page;
• data portability — receive the data they provided in a machine-readable format;
• object to processing based on legitimate interests, and ask for processing to be restricted;
• withdraw consent for location or selfie verification at any time;
• complain to a supervisory authority: in Thailand, the Personal Data Protection Committee (PDPC); in the EU/EEA or the UK, the local data protection authority.

11.2. To exercise these rights, the User writes to support@siamora.net from the address linked to the account. The Administration replies within 15 days, or sooner where the law of the User's country sets a shorter deadline. The Administration may first need to confirm that the account belongs to the User.

12. Users in Thailand

12.1. If the User uses the Service in Thailand, the Thai Personal Data Protection Act B.E. 2562 (2019) (PDPA) applies to the processing of their data, even though the Administration is based outside Thailand.

• Sensitive data. The selfie for verification is biometric data. It is processed only with the User's explicit consent, given in the app before the camera opens.
• Transfers. Data is stored outside Thailand; see section 8 for why and on what basis.
• Rights are listed in section 11 and can be exercised by email.
• Complaints. A complaint can be made to the Office of the Personal Data Protection Committee (PDPC), pdpc.or.th.

13. Age requirement

13.1. The Service is for adults only: an account can be created from the age of 18. The Administration does not knowingly collect data from anyone under 18.

13.2. If it becomes known that an account belongs to a minor, the account is deleted together with its data. A profile that looks underage can be reported in the app (profile or chat → ⋯ → Report → "Underage") or by email to support@siamora.net.

14. This website

14.1. The siamora.net website sets no cookies, runs no analytics and loads no third-party trackers or fonts. Nothing a visitor does on the website is tied to their Siamora account.

14.2. If a visitor chooses a language in the switcher, that choice is stored only in their browser (localStorage) and is not sent anywhere.

14.3. The website host keeps standard server logs — IP address, time and requested page — for a short time, to keep the site running and protect it from attacks.

15. Changes to the Policy

15.1. The Administration may amend the Policy. The new version is published on this page with a new effective date.

15.2. For changes that materially affect the User — for example, if a company takes over the Service from the current operator, or if the storage of photos and chat images is moved to another country — the Administration also notifies the User before they take effect, by email or in the app.

15.3. Continuing to use the Service after the changes take effect means that the User accepts the new version of the Policy.

16. Contact

Siamora support@siamora.net

The Policy is effective from October 23, 2026.