Your data, your control.

Realove is currently operated by Eugene Donin as an individual data controller, based in Ukraine. We'll register a formal company soon and update this section. For all privacy questions, contact [email protected].

If you're in the European Union, the United Kingdom, or California, you have additional rights described below. Wherever you are, you can write us with privacy questions and we'll respond within 30 days.

Account information

Email address and name, plus the authentication information needed for the sign-in method you choose. Realove uses passwordless sign-in and does not store a Realove account password. If you use Google or Apple, we receive the provider account identifier and verified email information they return. Apple may provide a privacy relay address when you choose Hide My Email. Any Apple authorization credential Realove needs to maintain or revoke the connection is encrypted at rest.

Profile information

Date of birth, age, gender, sexual orientation, location (city/country), languages you speak, relationship goals, profile photos, bio text, values, interests.

Venus matchmaker data

Birth date, birth time, birth city (if you give them — used for astrology and numerology), things you tell Venus in chat, screenshots you upload (up to 10), AI-generated insights about you (badge, mini-bio, growth notes), chat history with Venus.

Communication data

Messages you send to other users, photos shared in chat, who you matched with, who you blocked or reported.

Technical data

IP address, device type, browser type, operating system, what pages you visited, when you logged in. Used for security, debugging, and basic analytics.

Push notifications and app installation data

If you enable push notifications, Realove associates with your account a randomly generated, app-specific installation ID; an Expo push token; Android or iOS platform; app environment, version, and native build; selected language; notification permission and preferences; registration and last-seen timestamps; and delivery status.

The installation ID is specific to Realove. It is not an IMEI, hardware serial number, or advertising ID, and we do not use it to track you across apps.

We use this information only to deliver Realove notifications, synchronize unread badges, respect your settings, secure device registration, prevent duplicate or unauthorized delivery, invalidate unusable tokens, and troubleshoot delivery. Chat notifications may contain the sender's first name or a generic alert, but not the chat message text.

Realove stores the Expo push token. Expo Push Service routes notifications through the device's native Firebase Cloud Messaging (FCM) token on Android or Apple Push Notification service (APNs) token on iOS. Realove does not receive or store those native provider tokens. These providers receive technical routing information and the minimal notification payload required for delivery.

A device registration is disabled when revoked, when you sign out on that installation, or when the provider reports the token invalid, and it is removed during permanent account-deletion cleanup. A one-way hash of an invalid token may be retained only to prevent repeated delivery attempts; it cannot be used to send notifications.

You can change notification categories in Realove and withdraw system permission in your device settings. We do not sell push identifiers or use them for advertising or cross-app tracking.

Verification data

If you go through verification, we may collect a verification photo or ID. Used only to confirm identity, then minimized — we keep proof of verification, not the documents themselves where possible.

Sensitive categories

By using a dating service, you may share information about your sexual orientation, religious or political views, or health details. You're giving us explicit consent to process this for the purpose of matching you with compatible people. You can withdraw consent anytime by deleting your account.

We process your data for these reasons:

• To run the service. We need your profile data to show you to other users, to let Venus help you, to deliver messages between users. (Legal basis: contract.)
• To keep the community safe. We use behavior patterns to detect scams, fake profiles, and harassment. (Legal basis: legitimate interest.)
• To comply with the law. Sometimes governments require us to keep certain records, or to remove certain content. (Legal basis: legal obligation.)
• To improve Realove. We look at anonymized, aggregated patterns to fix bugs and design better features. (Legal basis: legitimate interest.)
• With your consent. For things like astrology readings or AI screenshot analysis — we ask you to explicitly opt in.

Other Realove users

People you match with or who can see your profile see your photos, bio, age, gender, location (city level), interests. They see your Venus badge and mini-bio only if you publish them — until you press "publish," they're private.

They never see: your email, your phone number, your full address, your birth time, your Venus chat history, your growth notes, your verification documents.

Service providers (data processors)

We use trusted companies to actually run the service. They process your data on our behalf, under contract, and can't use it for anything else:

• Railway — hosts our servers and database.
• Cloudinary — stores your photos and screenshots.
• OpenAI — Venus uses OpenAI's models to analyze your chat and screenshots. OpenAI is bound by their API terms not to use this data for training their models. API abuse-monitoring state may be retained for up to 30 days under OpenAI's API controls.
• Google — if you sign in with Google, Google handles that authentication step.
• Apple — if you sign in with Apple, Apple handles that authentication step and may provide a Private Email Relay address when you choose Hide My Email.
• Expo Push Service, Firebase Cloud Messaging (FCM), and Apple Push Notification service (APNs) — route the minimal token and notification payload needed to deliver mobile notifications.
• Resend — sends login codes and notification emails; related delivery records may be retained for up to 30 days.

Law enforcement (rarely)

We share data with police or government only when we're legally required — for example, in response to a court order or search warrant. We push back on overly broad requests when we can. Child-safety reports are reviewed. Confirmed CSAM is reported, as applicable, to NCMEC or the relevant regional authority in accordance with law.

We never sell your data

Not to advertisers, not to data brokers, not to anyone. This is core to what Realove is.

Your data is stored on servers in the European Union (Railway data centers). Cloudinary stores images on global infrastructure. OpenAI processes data in the United States.

For users outside the EU/US — your data may be transferred to these regions. We use Standard Contractual Clauses approved by the European Commission to protect data transferred outside the EU.

You can start permanent deletion yourself in the Realove app or authenticated web settings. Support is available only as a fallback if you cannot access the account.

Deletion is permanent. Your account cannot be restored.

What will be deleted

• Your profile will disappear from discovery and matches, and you will be signed out.
• Your personal data, photos, and message content will be deleted or anonymized.
• The account cannot be restored. To use Realove again, you will need to create a new account.

Data and media cleanup. Cloudinary media cleanup is scheduled immediately and retried until successful. It normally completes within 30 days, but temporary provider outages can take longer.

Providers and backups. For Railway volume-backup schedules that are enabled, isolated copies may remain: daily for up to 6 days, weekly for up to 1 month, and monthly for up to 3 months; PITR may retain data for about 4 weeks if enabled. Railway service logs depend on plan: 7 days on Trial/Hobby, 30 days on Pro, or up to 90 days on Enterprise. OpenAI API monitoring state may remain up to 30 days and Resend records up to 30 days. Deletion/support correspondence in the configured mailbox and its provider logs is retained for no more than 90 days after the request is completed, unless a documented legal hold requires longer. These copies do not return to the active service and cannot restore the account.

Railway volume backup copies may remain isolated for the schedules actually enabled: daily backups for up to 6 days, weekly backups for up to 1 month, and monthly backups for up to 3 months. Point-in-time recovery may retain data for about 4 weeks if PITR is enabled. Railway service logs are retained by plan: 7 days on Trial/Hobby, 30 days on Pro, or up to 90 days on Enterprise. These copies are not returned to the active service and cannot restore a deleted account; their retention does not delay active-service deletion.

You have the right to:

• Access your data — ask us what we have on you.
• Correct it if it's wrong.
• Delete it (permanently delete your account in Settings, or ask us to delete specific things).
• Export it — get a copy in a portable format.
• Restrict processing — tell us to stop using your data for some purpose.
• Object to processing where we're relying on legitimate interest.
• Withdraw consent at any time where consent was the legal basis.
• Complain to your local data protection authority. In the EU, you can find yours at edpb.europa.eu.

To exercise any of these rights, email [email protected]. We respond within 30 days, usually faster.

We use essential cookies — to keep you logged in, to remember your language preference, to bind an Apple sign-in attempt to the browser that started it, and to prevent fraud. Apple flow cookies are HttpOnly, short-lived, and deleted after use. These essential cookies don't need consent.

We don't use advertising cookies. We don't use Facebook Pixel, Google Ads tracking, or any third-party ad networks. We may use basic analytics (like Plausible or self-hosted PostHog) to count page views in aggregate, but not to track individuals.

Venus uses AI to analyze your chat messages, profile data, and screenshots to generate insights about you (badge, mini-bio, growth notes, compatibility hints).

This is not fully automated decision-making in the GDPR sense — Venus suggests, you decide. You always control what gets published to your profile.

We don't use AI to make legally significant decisions about you (like denying you access to the service based on AI scoring).

Realove is strictly for adults 18+. We don't knowingly collect data from anyone under 18. If we find out we have data from a minor, we delete it immediately and close the account.

If you're a parent and think your child has signed up, email us at [email protected] and we'll handle it immediately.

We take security seriously. Specifically:

• All data in transit is encrypted (HTTPS/TLS).
• Realove uses passwordless authentication; sensitive Apple authorization credentials are encrypted at rest.
• Database access is restricted to our small team.
• We monitor for unauthorized access and respond quickly to threats.

That said, no system is 100% secure. If something happens, we'll tell you within 72 hours of discovering it, as required by law.

We may update this policy. When we make significant changes (especially to what data we collect or who we share it with), we'll email you and update the "last updated" date at the top.

For any privacy question, request, or complaint:

[email protected]

We read every message and respond within 30 days — usually within a few days.