Ayma Privacy Policy

The company behind Ayma (referred to as "Ayma", "we", or "us") is the controller of the personal data described in this policy.

• We collect what you give us (sign-in details, profile, photos, messages, voice), what Ayma derives (facial and physique analyses, a web-search summary of your name, match scores), and basic device and usage data.
• We use it to run the service, suggest matches, keep users safe, meet legal duties, and improve the product.
• We share it only with the service providers that run Ayma's infrastructure and AI (Google Firebase, Google Gemini / Vertex AI, LiveKit), with other users to the extent your profile and messages expose it, and with authorities where the law requires.
• We do not sell your personal data and we do not use it for third-party advertising.
• You can access, export, correct, and delete your data from within the app.

We do not ask for government ID, and we do not run identity or background checks on anyone.

Connecting a Google account (optional)

If you choose to connect a Google account, Ayma requests your explicit consent through Google's own OAuth screen for narrow, read-only access: Gmail message metadata (subject/sender) for a bounded recent window of messages, plus the plain-text body content of a small number of those messages (after skipping senders on an exclude list that starts with major banks, payment processors, and government/tax domains, and which we can extend at any time), and Google Calendar event titles and attendee counts (never attendee identities or descriptions). Ayma reads a bounded, recent window only — never your full history — via one sync pass at connect time and periodically afterward while connected. (Google Photos was previously part of this feature, in a counts-only form; it has since been removed — Google no longer allows third-party apps this kind of access to an existing photo library. You can still share photos with Ayma directly, as described elsewhere in this policy.)

What is pulled is held in memory only, run once through Ayma's AI to distill a short set of facts about you, and then discarded; the raw Gmail/Calendar content is never written to our database. The distilled facts are added to your private working memory (the "wiki") described elsewhere in this policy, default private to you, not shown on your public profile.

You can disconnect at any time from Profile settings, which revokes Ayma's access with Google immediately (a real token-revocation call to Google, not just a local deletion) and deletes the stored access token. Facts already distilled remain in your notes unless you edit or delete them, the same as anything else Ayma has learned about you from conversation.

Where GDPR-style law applies, the legal bases are noted in plain terms.

• To provide the service you asked for — create and store your profile, run chat and voice, deliver messages, keep your credit balance. Basis: performance of our contract with you.
• To run the automatic analysis of your photos and name, keep the results in Ayma's working memory, and surface them into your profile when you ask. This is core functionality and cannot be switched off while you use Ayma. Basis: performance of our contract; and our legitimate interest in providing an AI matchmaking product. Where local law treats photo-derived analysis as sensitive data, we rely on your explicit consent, given when you create an account and add photos, and you can withdraw it by deleting your account.
• To learn real facts about you from a connected Google account, if you choose to connect one, and distill them into your working memory. Basis: your explicit consent, given through Google's OAuth consent screen when you connect; withdrawable at any time by disconnecting, which also revokes the token with Google.
• To suggest matches and rank compatibility. Basis: performance of our contract; legitimate interest in making the product work well.
• For safety and integrity — review reports, investigate abuse, enforce the Terms, prevent fraud, and protect users. Basis: legitimate interest in protecting users and the service; compliance with legal obligations.
• To improve the product — fix bugs, understand which features are used, improve model prompts and quality. We use your content for this in aggregated or limited ways and do not use it to train third-party foundation models (see "AI providers" below). Basis: legitimate interest in improving Ayma.
• To meet legal obligations — respond to lawful requests, keep records we are required to keep, handle disputes. Basis: legal obligation; establishment or defence of legal claims.
• To send you notifications you have enabled. Basis: consent (device permission); legitimate interest for essential service messages.

Service providers (subprocessors)

We use a small number of providers to run Ayma. They process your data only to provide their service to us, under contract.

AI providers and training

We instruct our AI providers to process your content only to return results to Ayma, not to train their own general-purpose models on it. Ayma itself does not sell your content or license it to others for advertising or model training.

Other users

Other users see what your public profile shows and the messages you choose to send them. They do not see your private wiki notes, your raw facial/physique analyses, your voice transcripts, or your web-search summary unless you have deliberately added that content to your public profile or a message.

Legal, safety, and business transfers

We may disclose data if we reasonably believe it is required by law or legal process, or necessary to prevent serious harm to someone. If Ayma is involved in a merger, acquisition, or sale of assets, data may transfer as part of that transaction, subject to this policy.

No sale of personal data

We do not sell your personal data, and we do not "share" it for cross-context behavioural advertising as those terms are used under US state privacy laws.

Ayma is a mobile app, not a website, so it does not use advertising cookies.

• Firebase SDKs run inside the app for authentication, data sync, storage, crash reporting, and push notifications.
• We use product analytics limited to how the app is used (feature usage, performance, crashes). We do not use third-party advertising or tracking SDKs, and we do not build advertising profiles.
• Standard mobile identifiers (such as a push token and an app-instance ID) are used to deliver notifications and basic analytics.

Ayma and its providers are based in, or operate from, the United States and other countries. Your data may be processed outside the country where you live, including in the United States. Where the law requires it, we use appropriate safeguards for these transfers, such as the European Commission's Standard Contractual Clauses (or the UK equivalent) with our providers.

• We keep your account data for as long as your account is active.
• When you delete your account, we remove your profile, photos, messages, voice transcripts, and derived analyses from our active systems.
• Deletion has a short recovery window during which the account can be restored. After that window it is permanent.
• Backups are kept on a rolling basis and age out automatically, so a copy may remain in backups for a limited period after deletion.
• We may keep specific records longer where we must for legal, tax, security, or dispute-resolution reasons (a "legal hold"), and only for as long as that purpose lasts.

• Data in transit is encrypted with TLS; stored data sits in Google's managed infrastructure with encryption at rest.
• Access to production data is limited to staff who need it and is authenticated.
• Firestore and Storage security rules restrict each user's data to that user and the people they interact with.
• No system is perfectly secure. If a breach affects you, we will notify you and the relevant authorities as required by law.

Depending on where you live, you may have some or all of these rights:

• Access and portability — get a copy of your data.
• Correction — fix inaccurate profile information.
• Deletion — delete your account and associated data.
• Restriction and objection — ask us to limit or stop certain processing.
• Withdraw consent — where we rely on consent, withdraw it (for the core photo/name analysis, this means deleting your account, because the analysis is essential to the service).
• Non-discrimination — we will not penalise you for using these rights.

How to use them: most rights are self-service in the app — edit your profile to correct it, use the export option to get a copy, and use account deletion to erase it. For anything else, contact us through the in-app feedback tool. We may need to verify your identity (for example that you control the account's phone number or sign-in). We respond within the time the law allows.

If you are in the EEA or UK, you also have the right to complain to your local data protection authority. If you are in California or another US state with a privacy law, you may use an authorised agent to make a request on your behalf.

Ayma is only for adults aged 18 and over. We do not knowingly collect personal data from anyone under 18. If we learn that a user is under 18, we close the account and delete the data. If you believe a minor is using Ayma, report it through the in-app feedback tool.

We may update this Privacy Policy as Ayma changes or the law changes. We update the "Last updated" date above, and for material changes we give notice in the app. If you keep using Ayma after a change takes effect, that means you accept the updated policy.

For any privacy question or request, use the in-app feedback tool (Profile, then "Send feedback").