Amio

Privacy Policy

v1 — 12 August 2026

Effective from 12 August 2026. This is the version your consent is recorded against in the app. When we change this policy the version string changes with it — see Changes to this policy.

The short version

Amio shows you what people near you are doing right now. To do that we need three things: your phone number (it is how you log in — Amio has no passwords and does not ask for your email), your photos, and a rough idea of where you are.

We do not keep your exact coordinates. Your location is converted into a map tile covering an area around you, and only that tile is saved. We only check your location while the app is open — there is no background tracking.

Your face photos are not public. Only you, an active match, and someone whose vibe you responded to can see them. Blocking someone overrides all of that. Chats disappear 48 hours after you match.

Delete your account and your profile, photos, vibes, matches and chats are erased permanently. We keep only safety records — reports, and blocks other people placed on you — because those belong to their safety, not yours.

We do not sell your data, we do not show you ads, and we do not run face recognition on your photos.

1. Who we are

Amio is a mobile dating application operated by Mihir Jain, sole proprietor, trading as Amio — a proprietorship registered in India under Udyam Registration Number UDYAM-KR-03-0736720.

In this policy, "Amio", "we", "us" and "our" mean that proprietorship — Mihir Jain trading as Amio. "You" and "your" mean the person using the app.

Under India's Digital Personal Data Protection Act, 2023 ("DPDP Act") we are the Data Fiduciary for your personal data — the entity that decides why and how your data is processed, and the entity responsible for complying with the Act. Under that Act you are the Data Principal.

2. Who this policy covers

This policy applies to everyone who uses the Amio mobile app, and to this website.

Amio is currently offered only in India. Registration requires an Indian mobile number (+91), and we do not currently market or offer the service anywhere else. If you use Amio while travelling outside India, your data continues to be handled as described here.

Language of this notice

The DPDP Act gives you the right to receive this notice in English or in any language listed in the Eighth Schedule to the Constitution of India. This policy is published in English. If you would rather have it explained in another Eighth Schedule language, write to mihir@amioonline.in and we will arrange it. We would rather do that than publish a translation we cannot keep current — a stale translation of a privacy policy is worse than none, because it is the version someone will rely on.

3. The data we collect

This is the complete list. If something is not in this section, we do not collect it.

Identity and account

Content and activity

Device and technical data

We do not use cookies, advertising identifiers, or third-party analytics or advertising SDKs in the Amio app. This website sets no cookies and runs no scripts.

Safety and moderation

Payments

If you buy something in the app, we record what you bought — the product, the subscription and the entitlements it grants you.

We never receive or store your card details. Payment information is entered directly into our payment gateway, or into the Apple App Store or Google Play, and is handled by them under their own privacy policies. We see only the result of the transaction.

Consent records

Every time you grant or withdraw a consent, we record it on our servers: which type of consent it was, the version of the document it applied to, whether it was granted or withdrawn, and when. This is how we can show what you agreed to and when. See Consent, and how to withdraw it for the full list of consent types.

4. Location data

Amio is a hyperlocal app: its entire purpose is to show you what is happening near you. Location is therefore the most sensitive data we handle, and this section describes exactly what happens.

When we collect it

We request your device's approximate location at two moments, and no others:

• when you open the feed, so we can show you vibes posted near you; and
• when you post a vibe, so it can be shown to people near you.

This is foreground-only. Amio does not request or use background location permission. When the app is closed or in the background, we are not collecting your location. There is no location history, no movement trail, and no way for us to reconstruct where you have been.

What is sent, and what is kept

Your device produces a latitude and longitude. That pair is transmitted to our servers over an encrypted connection, because the conversion happens on our side. On receipt, it is converted into a tile identifier — one cell in a fixed grid laid over the world, with boundaries set in advance — and only that identifier is written to our database. The raw coordinates are not stored.

This means that what we hold is "this user was in this tile", not "this user was at this address". Everyone inside the same tile is indistinguishable from everyone else inside it, and the tile boundaries are fixed in advance, so they cannot be drawn around you.

Your controls

You grant location access through your phone's operating system, and you can withdraw it at any time in your device settings, or by emailing us to withdraw the LOCATION consent. If you do, Amio's core features stop working — a feed of people near you cannot be produced without knowing roughly where you are — but you keep your account, and we stop collecting location immediately.

5. Photos

Profile photos

You may add up to six photos to your profile, and you need at least three to finish signing up. Once your account exists you can delete photos down to a minimum of two.

Photos are held in object storage and delivered through a content delivery network. Every photo link we issue is signed for one viewer and expires after 15 minutes, so a link cannot be forwarded, shared, or kept working after the fact.

Vibe photos

The optional photo attached to a vibe is a separate thing from your profile photos. It carries no user identifier, and it is visible to everyone nearby who can see the vibe. Treat it as public to your immediate area: do not put anything in it — a face, a house number, a vehicle plate, a workplace — that you would not want a stranger nearby to see.

Automated checks on photos

Photos you upload are checked automatically for content that breaks the rules in our Terms of Service. This is content moderation, not identification — the check looks at what is in the picture. It does not recognise, match or remember who is in it, as the next section explains.

We do not process biometric data

Amio does not perform face recognition, face matching, face-geometry extraction, photo verification, or any other biometric processing on your photos. We do not compare your photos against each other, against an identity document, or against any database. We do not hold a face template for you, because we never create one.

We are stating this explicitly because biometric information is classified as sensitive personal data under the SPDI Rules, and because several other dating apps do carry out exactly this kind of processing. If that ever changes for Amio, it will require a new version of this policy and a fresh, separate consent from you — it will not be slipped in under an existing one.

6. How we use your data

We use your data for the purposes listed below and for nothing else. We do not sell your personal data. We do not share it with advertisers. We do not use it to build advertising profiles, and Amio shows no third-party ads.

Improving your matches

Amio learns from what you do in the app so that the people and vibes you are shown fit you better than distance alone would manage. What that means concretely: which vibes you opened or responded to, which you passed over, and whether a match turned into a conversation.

Three limits on this, and they are the point of writing it down:

• We do not read your conversations to do it. Chat messages are never used for matching. Whether a conversation happened is a signal; what was said in it is not.
• It lives and dies with your account. These signals are kept while your account is open and erased when you delete it. Nothing about you is carried into a permanent archive, and nothing is kept to study after you leave.
• It is used to serve you, not to profile you for anyone else. The result is your feed and your suggestions. It is not sold, not shared with advertisers, and not used to build a profile of you for any third party.

You can withdraw PERSONALISATION at any time by emailing mihir@amioonline.in. If you do, we erase the signals we hold for it and your feed goes back to being decided by tile, age range and gender alone. Nothing else about your account changes.

Automated processing

Two things in Amio happen automatically rather than by human judgement:

• Content moderation. Vibe text, comments and bios are checked automatically against our rules. Content can be blocked or removed by this check without a person seeing it first. If your content is removed and you think that is wrong, you can raise it through grievance redressal and a person will look at it.
• Your feed. Which vibes you see is decided automatically, based on your tile, your age-range preference, gender, and who you have blocked.

Neither of these produces a legal effect or a decision about you outside the app.

7. Consent, and how to withdraw it

Under the DPDP Act, your consent must be free, specific, informed, unconditional and unambiguous, and must be given by a clear affirmative action. It also has to be as easy to withdraw as it was to give. We record each consent separately rather than asking you to accept everything at once.

The consents we record

Each consent is recorded against the version of the document it applied to — the string at the top of this page. That is how we can tell which wording you actually agreed to, even after the document has been updated.

Withdrawing consent

You can withdraw any consent at any time by emailing mihir@amioonline.in. You do not have to explain why, and we act on it without asking you to justify it.

Withdrawal does not make past processing unlawful — it stops future processing. When you withdraw a consent we stop the processing that relied on it within a reasonable time, and erase the data that no longer has a purpose, unless a law requires us to keep it.

Be aware of what withdrawal means in practice: withdrawing PHONE_NUMBER, PROFILE_DATA or DATA_PROCESSING removes the basis on which your account exists, and we will treat it as a request to delete your account. Withdrawing LOCATION disables the hyperlocal features but keeps your account. Withdrawing MARKETING affects nothing except marketing messages.

8. Who we share data with

We share personal data only with the service providers that make the app work, and only to the extent each needs. Each is bound by contract to process the data only on our instructions.

Other users

Some of your data is shown to other people using Amio — that is the point of the app. What is visible to whom is set out in Photos and summarised here: your name, age, gender, bio and onboarding tags appear on your profile card to people you can match with; your vibes appear to people nearby; your profile photos follow the restricted visibility rule. Your mobile number is never shown to another user.

Law enforcement and legal requirements

We may disclose personal data where we are required to by law, by a court, or by a competent authority acting under lawful powers, and where we believe in good faith that it is necessary to prevent serious harm to someone. We will not disclose more than the request requires.

If the business changes hands

If Amio is merged, acquired, or its assets are sold, personal data may transfer to the new owner. We will tell you before that happens, and the new owner will be bound by this policy until you are given notice of a new one.

Transfers outside India

Some of your data is processed outside India, and we would rather say so plainly than bury it.

Your account data is stored in India. Your profile, photos, vibes, matches and the records behind them sit on infrastructure in India, and the code that logs you in is delivered by an Indian SMS provider. None of that leaves the country.

Two features send text to an AI service outside India. When a match opens we generate suggested opening lines, and we check written content against our rules automatically. To do both we send the relevant text — the vibe you or your match wrote, the onboarding answers you have in common, the other person's first name, and the bio, vibe or comment text being checked — to an AI provider whose service is hosted in the United States. There is no Indian region for it. We do not send your photos, your phone number, your location, or your chat messages.

Purchases made through the Apple App Store or Google Play are the exception we do not control. Those transactions are handled by Apple or Google under their own terms and privacy policies, on their own infrastructure, and we never receive your payment details — see Payments.

Section 16 of the DPDP Act permits transfer to any country the Central Government has not restricted by notification. At the date of this policy, no country has been restricted, and the transfer described above is lawful on that basis. We re-check the notified list before publishing each version of this policy, and if a country we rely on is ever restricted we will move the processing or stop it.

9. How long we keep your data

10. Deleting your account

You can delete your account in the app's settings, or by emailing mihir@amioonline.in. If you use the in-app route we do not require you to email us, explain yourself, or speak to anyone first.

What is permanently erased

Deletion is real deletion, not deactivation. The following are erased and cannot be recovered:

• your profile — name, date of birth, gender, bio, onboarding answers, age preferences;
• all of your photos, both profile photos and vibe photos;
• all of your vibes, and your responses and comments;
• all of your matches;
• the personalisation signals built from what you responded to and skipped;
• all of your conversations;
• your device push tokens.

Your session token is revoked immediately, so every device you were signed in on is logged out at once.

[TODO: Confirm three things technically. (1) That chat documents are actually deleted, not just hidden, after the 48-hour expiry — the DPDP Act requires us to cause our processors to erase. (2) That object versioning, backups and replication do not retain deleted photos past the stated period. (3) That content delivery caches are invalidated or expire, so an already-issued signed URL cannot outlive deletion.]

What we keep, and why

Three things deliberately survive deletion. We would rather explain them than quietly omit them.

• Blocks other people placed on you. If someone blocked you, that record is part of their safety, not yours. Deleting your account does not clear it, because otherwise deleting and re-registering would be a way to undo other people's blocks.
• Moderation reports, both those you filed and those filed about you, along with their outcomes. An open or recently closed case must not vanish because one party left. These are kept for the period given in section 9.
• An anonymous account husk. The account row itself survives, with your mobile number replaced by a meaningless tombstone value of the form deleted-<random-id>. It holds no personal data — no number, no name, no photos, nothing that identifies you. It exists so that the time of deletion is recorded, and so that a future signup cannot accidentally collide with the old record.

We will also keep anything a law specifically requires us to keep — for example, records of payments you made — for as long as that law requires and no longer.

11. Your rights

As a Data Principal under the DPDP Act you have the following rights. All of them are free of charge.

How quickly we respond

We acknowledge every request within 24 hours and aim to complete it within 15 days, and in any event within 30 days of receiving it. If a request is complex and will take longer, we will tell you why and give you a date.

We may need to verify that a request really comes from you before acting on it, particularly for access and erasure. We will do this using your registered mobile number.

Your responsibilities

The DPDP Act also places some duties on you. In plain terms: do not impersonate anyone when registering, do not file a complaint or grievance you know to be false, and do not give us false particulars. Amio is a dating app — accurate information about who you are is a safety matter for everyone else, not just a legal formality.

12. Grievance redressal

If you have a question or a complaint about how we handle your personal data, contact our Grievance Officer. This is a named individual, published here as Indian law requires.

We will acknowledge your grievance within 24 hours and resolve it within 15 days, and in any case no later than 30 days from the date we receive it. When we resolve it we will tell you what we decided and why.

Escalating to the Data Protection Board of India

If we do not answer you, or you are not satisfied with our answer, you may complain to the Data Protection Board of India, the authority established under the Digital Personal Data Protection Act, 2023.

The Act requires you to exhaust our grievance process first — so please contact our Grievance Officer before approaching the Board, and keep our reply, or the date you wrote to us if there was none.

Proceedings before the Board are conducted online. A complaint must be made within two years of the date you became aware of the breach, and the Board is required to complete its inquiry within six months, which it may extend by recording its reasons. If you are not satisfied with the Board's decision, section 29 of the Act lets you appeal to the Telecom Disputes Settlement and Appellate Tribunal within 60 days.

[TODO: Link the Board's own filing portal here once it is published. As at the date of this policy the Board has not published a live complaint portal, so no address is given rather than an address that does not work. Check before each published version — do not paraphrase the procedure once it exists, link the official source.]

13. How we protect your data

The measures we take include:

• all traffic between the app and our servers is encrypted in transit, with the server's certificate chain pinned in the app so a forged certificate is rejected;
• your session token is stored in the iOS Keychain or Android Keystore, the operating system's hardware-backed credential store, and never in ordinary app storage;
• photo links are signed per viewer and expire after 15 minutes, so a leaked link is useless almost immediately;
• we store a tile rather than coordinates, so a database breach cannot reveal anyone's exact location;
• access to production data is restricted to staff who need it;
• automated moderation runs on user-generated text.

[TODO: Add encryption at rest, access logging and review, penetration testing cadence, and whether ISO/IEC 27001 certification is held or planned. ISO 27001 is the standard named in the SPDI Rules as evidence of "reasonable security practices" and is the safest thing to be able to point to.]

No system is perfectly secure, and we will not pretend otherwise. If a personal data breach occurs, we are required to notify both the Data Protection Board of India and every affected user, and we will do so.

14. Children and users under 18

Amio is only for people aged 18 and over. Under the DPDP Act, anyone under 18 is a child, and India sets that threshold at 18 with no lower option.

We ask for your date of birth at signup and block registration by anyone under 18. We do not knowingly collect personal data from children. The Act separately prohibits — absolutely, regardless of any consent — behavioural tracking of children and targeted advertising directed at them. Amio does neither of those things for any user.

If you believe someone under 18 is using Amio, report the profile in the app or contact our Grievance Officer. When we confirm it, we delete the account and its data rather than merely suspending it.

15. Sensitive personal data

The DPDP Act treats all personal data alike. The older SPDI Rules, which remain in force until 13 May 2027, single out certain categories as sensitive personal data or information — including passwords, financial information, health information, medical records, biometric information, and sexual orientation.

Amio does not ask for your sexual orientation, and there is no field for it. But we do record your gender, and we do record who you respond to. In a dating context, that combination can imply orientation even though we never asked. We treat it accordingly:

• it is used only to build your feed and your matches, never for anything else;
• it is never shared with any third party for any purpose other than hosting the service;
• it is erased when you delete your account, along with the rest of your profile.

Amio holds no passwords (there are none), no biometric data (see section 5), no health or medical information, and no financial information — payment details go directly to the payment gateway.

16. Changes to this policy

We will change this policy when what we do with your data changes. When we do:

• The version string changes. The badge at the top of this page — currently v1 — 12 August 2026 — is incremented, with a new effective date. Your consent is recorded against this exact string, so we can always tell which version you agreed to.
• We tell you before it takes effect. For any change that materially affects your rights or what we do with your data, we will notify you in the app and by push notification at least 14 days in advance, with a plain-language summary of what changed.
• We ask again where consent is needed. If the change involves a new purpose or a new category of data, we ask for fresh consent against the new version rather than assuming your old consent carries over. You can decline and keep using Amio for everything the change does not affect.
• Small corrections — fixing a typo, clarifying wording without changing meaning, updating a contact address — are made without notice, but the version and date still change.

Because your consent is recorded against a version of this policy, you are entitled to read the version you actually agreed to. Write to mihir@amioonline.in with the version string shown in the app and we will send you that text. We keep every published version for this reason.

17. How to contact us

Back to top ↑