DatingNow — Privacy Policy

Last updated: October 4, 2026 Effective date: October 4, 2026

Still outstanding before publishing: this text has NOT been reviewed by a lawyer and is not tailored to Peruvian law (Ley 29733 de Proteccion de Datos Personales). The disclosures here must match the Data Safety form in Play Console exactly (see Appendix A) — a mismatch is a common cause of review rejection.

This policy explains what DatingNow collects, why, who it is shared with, and the control you keep. It covers the DatingNow mobile app on Android and iOS.

DatingNow is operated by SYSTEMAKE S.A.C. ("DatingNow", "we", "us"), registered at Cal. Cesar Vallejo Mza. 41 Lote 13, A.H. Municipal Chillon (frente a las Revisiones Tecnicas), Lima, Peru. For any privacy question, contact systemakesac@gmail.com.

1. You must be 18 or older

DatingNow is a dating service for adults. You may not create an account or use the app if you are under 18. During sign-up we ask for your date of birth and reject any date that would make you younger than 18. We do not knowingly collect data from minors; if we learn that an account belongs to someone under 18, we delete it and its data.

2. What we collect

We only collect what the app actually needs to work. Everything below is data you provide or that is generated by your use of the service.

2.1 Account and identity

We never receive or store your Google or Apple password. Sign-in is handled entirely by Google, Apple and Firebase Authentication.

A note on Sign in with Apple: if you choose "Hide My Email", Apple gives us a relay address instead of your real one. That is enough for us — we never see your real address.

2.2 Profile you publish

Your name, date of birth, gender, "About me" text, interests, and profile photos. Your date of birth is stored; your age — not the date itself — is what other users see.

2.3 Precise location

With your permission, we read your device's GPS coordinates and store them on your profile. Other users never receive them. Your device turns your position into a place name (neighbourhood and city) using your operating system's geocoding service and saves that name on your profile; that name is the only location other people see. No distance between you and other people is shown.

To obtain that place name, our servers round your coordinates to about 1 km and send the rounded coordinates to OpenStreetMap's Nominatim geocoding service, which returns the neighbourhood and city. We keep the resulting place name in a cache on our servers. Your coordinates are never sent to our AI provider (see §4).

Location is optional. Deny the permission and the app still works — your profile simply shows no place name, and profiles without a known location are shown rather than hidden.

2.4 Messages and interactions

• Message text, and the server-side time it was sent.
• Delivery and read state: whether a message reached the server, and the last time each participant opened the conversation (this is what powers the ✓ / ✓✓ marks and unread badges).
• A copy of the sender's profile is stored alongside each message — name, age, photos and other public profile fields — so conversations render correctly and instantly.
• Who you liked.

2.5 Device and purchase data

• A push notification token, so we can notify you about new messages.
• Records of in-app purchases (the product purchased and the store transaction identifier). Payment is processed by Google Play or Apple; we never see your card number or billing details.
• Your credit balance, and the fact that you viewed a profile — viewing profiles consumes credits.

2.6 What we do NOT collect

To be explicit, because it is unusual and it is verifiable in our app:

• No analytics or tracking SDK. We do not measure your behaviour across the app.
• No advertising identifier, no ad networks, no cross-app tracking.
• No access to your contacts, calendar, microphone, call logs or SMS inbox.
• We do not sell your personal data, and we do not share it for advertising.

We do use one diagnostic tool, and we would rather name it than have you find it: Firebase Crashlytics, which reports crashes and errors so we can fix them. It receives the crash itself, your device model and OS version, and your DatingNow account id — so we can tell whether a bug hit one person or everyone. It never receives your messages, your photos or your location.

3. How we use your data

1. To run your account — authenticate you, restore your profile, keep you signed in. 2. To show you people and show you to people — matching by gender preference, age range and distance, and rendering profiles. 3. To deliver messages and notifications, including push notifications about new messages. 4. To process purchases of credit packs and to meter credit consumption. 5. To keep the service safe — to act on reports you or others submit, and to enforce our terms.

We do not use your data to build advertising profiles, and we do not run automated decisions that have a legal effect on you.

4. Automated and AI-generated messages

Please read this section — it describes something you will experience in the app.

DatingNow uses a third-party AI service (OpenAI) in two ways. Both involve AI profiles, which are profiles operated by DatingNow and labelled as such in the app.

Conversations between people are never sent to the AI provider. Only conversations with an AI profile are.

• Conversation openers. We may send a message request from an AI profile to start a conversation (this feature is currently switched off). To write it, we send the recipient's first name, gender, interests and preferred app language, together with the AI profile's own name and gender.
• Automated replies, only in conversations with an AI profile. To write a reply, we send up to the 20 most recent messages of that conversation, the AI profile's own name, gender and bio, and the neighbourhood, city and country derived from your location — never your coordinates.

We never send the AI provider your photos, your email address, your phone number, or your exact location or coordinates.

As a result, messages you receive from an AI profile are generated automatically rather than typed by a person.

What we commit to is that you are never charged anything on account of AI profiles:

• Messaging an AI profile is free. It never spends one of your daily message requests and never costs a credit.
• AI profiles do not count toward the credit meter in Discover. Browsing them costs you nothing, so they can never push you toward buying credits.

In other words, an AI profile cannot take a single credit from you, by any route. If you would like to know whether a particular profile is automated, write to us at the address in §13 and we will tell you.

If AI generation is unavailable, an opener may instead be chosen from a fixed set of pre-written greetings.

5. What other users can see

Other DatingNow users can see: your name, your age, your photos, your "About me" text, your interests, and the neighbourhood and city you are in. They cannot see your email address, your phone number or your date of birth.

About your coordinates: other people see only the neighbourhood and city you are in, never your coordinates, and no distance is shown. Your coordinates are not sent to other users' devices, including inside messages.

When you send a message, the person you are talking to receives a copy of your public profile fields along with it (see §2.4).

Discovery visibility: while your account exists, your profile can appear in other users' Discover feed. DatingNow does not offer a setting to stay signed in while hiding yourself from Discover — an earlier switch that appeared to do this was removed because it never actually took effect, and we would rather offer no control than one that does not work. The filters inside the app change who you see, not who sees you. To stop appearing altogether, delete your account (§10).

6. Who we share data with

We do not sell your personal data. We share it only with the service providers who operate our infrastructure, each acting on our instructions:

We may also disclose data when we are legally required to, or where it is necessary to protect the safety of our users or the public.

International transfers. These providers process data on servers outside your country, including in the United States. Where required by law, transfers rely on the European Commission's Standard Contractual Clauses or an equivalent safeguard.

7. Device permissions we ask for

Every one of these is optional and requested in context, not at launch. You can revoke any of them at any time in your device settings.

8. How long we keep data, and where

• Your profile is kept while your account exists.
• Your conversations and likes are kept while your account exists. Deleting a conversation on your device removes it for you; the other participant's copy is governed by their own use of the app.
• Your photos are kept until you delete them or delete your account.
• On your own device, your profile and your notification token are stored in the platform's protected storage — Android EncryptedSharedPreferences and the iOS Keychain — and are removed when you sign out or uninstall the app.

9. Your rights

You can:

• Access the personal data we hold about you.
• Correct your profile — most of it is editable directly in the app.
• Delete your account and your data (see §10).
• Withdraw permissions (location, camera, photos, notifications) in device settings.
• Object or restrict, and request a portable copy of your data, where the GDPR, UK GDPR, CCPA/CPRA or a comparable law applies to you.
• Complain to your local data protection authority.

To exercise any of these, write to systemakesac@gmail.com. We respond within 30 days. We will never charge you or degrade your service for making a request.

10. Deleting your account and your data

You can request deletion of your account and all associated data — profile, photos, messages, likes and preferences — at https://meetme-c9479.web.app/delete-account/ or by writing to systemakesac@gmail.com.

Once verified, we delete your data within 30 days, except where we must retain specific records to comply with a legal obligation (for example, transaction records required by tax law) or to resolve an active safety report. Backups are purged on a rolling 30-day cycle.

Google Play requirement — status: an app that lets users create an account must offer account deletion both inside the app and through a publicly reachable web page. Both exist: the in-app entry point is in My Profile, and the web form above is live. The step that remains is declaring that URL in Play Console → App content → Data safety.

11. How we protect your data

Traffic between the app and our servers is encrypted in transit (HTTPS/TLS). Data on your device is held in the platform's protected storage. Access to our production databases is restricted, and server-side rules govern which documents and files each signed-in account may read or write.

No system is perfectly secure. If a breach affects your personal data, we will notify you and the relevant authority as required by law.

12. Changes to this policy

If we change this policy materially, we will update the date at the top and notify you in the app before the change takes effect. Continuing to use DatingNow after that means you accept the updated policy.

13. Contact

SYSTEMAKE S.A.C. Cal. Cesar Vallejo Mza. 41 Lote 13, A.H. Municipal Chillon (frente a las Revisiones Tecnicas), Lima, Peru Privacy enquiries: systemakesac@gmail.com

Appendix A — Google Play Data Safety mapping

Fill the Play Console form to match this table. A mismatch between the form and this policy is one of the most common causes of a Play review rejection.

Declare also: data is encrypted in transit — yes; users can request data deletion — yes (https://meetme-c9479.web.app/delete-account/); data collection is not used for advertising or tracking; no data is sold.

Do declare Crash logs and Diagnostics. An earlier version of this appendix said the opposite; it was wrong. The app ships Firebase Crashlytics (and firebase-sessions), verified initializing in a release build. There is still no analytics SDK and no advertising ID — the merged release manifest carries no AD_ID permission — so the Advertising-ID declaration in Play Console is No.