Freelove legal
Privacy Policy
How Freelove collects, uses and stores personal information in the iOS and Android apps and on the web, and how you can exercise your rights.
Last updated: 2026-09-13 · 2026-09-13.1
1. Who is responsible for your data?
Freelove is operated by Easynet Kft. (EasyNet Informatikai és Számítástechnikai Szolgáltató és Kereskedelmi Korlátolt Felelősségű Társaság). Company registration number: 01-09-682490. Correspondence address: 1139 Budapest, Petneházy utca 37–47., E. I. 1., Hungary. Email: support@freelove.hu. Telephone: +36 20 444 0365.
Easynet Kft. is the controller of the personal information described here. Send privacy questions, requests to exercise your rights and complaints to support@freelove.hu or the correspondence address above. Include enough information to identify your account, but never send a sign-in code or payment card details.
2. Scope and minimum age
This policy covers the current Freelove iOS and Android apps, www.freelove.hu, the associated account and customer support. It also covers profile information you make public. Available features can differ by platform, app version, region and membership.
Freelove is for adults aged 18 and over. Your birthday is used to check the minimum age, display your age and support age-related discovery. Minors may not register. If you suspect an underage account or a child-safety concern, use Report on the member’s profile or contact support@freelove.hu so we can investigate and take appropriate action.
3. Information we receive
We receive the information you enter during registration and profile editing, content you upload or send, and information you provide for verification or support. Required fields are marked in the relevant screen. Without information needed to create or verify an account, we cannot complete that step; optional fields can be left blank.
Using Freelove also creates technical and interaction records. Other members can provide information about you through messages, connection or album requests and reports. A sign-in or payment provider supplies information when you choose to use its service.
| Category | Examples and use |
|---|---|
| Account and access | Email or phone number, sign-in method, provider identifier when an available Apple/Google sign-in is used, member ID, sessions and necessary consent records. |
| Profile | Name or nickname, username, birthday, gender and identity, orientation, home city, interests, introduction, relationship intentions and further fields you choose. |
| Content and connections | Photos, albums and permissions, text, images, GIFs, voice and client-supported video messages, shared locations, profile visits, favourites, friends, Footprints, message requests and presence. |
| Device and use | IP address, device/installation and push identifiers, operating system, app version, language, timestamps, operational and security logs. iOS analytics is described separately. |
| Purchases and assistance | Membership entitlement, product, transaction and store receipt identifiers, renewal status; support messages, reports and necessary evidence. The store handles your full payment card details. |
4. Purposes and legal bases
We distinguish the purposes for which information is used. Accepting the Terms of Use or acknowledging this policy is not consent to every form of processing. A device permission also does not replace a legal basis. The requirements below do not mean that a missing consent has already been obtained; sections 5 and 10 explain the current limitations.
Our legitimate interests include protecting accounts and members, preventing fraud and abuse, keeping the service reliable and dealing with disputes. Such processing must be necessary and proportionate, taking your rights into account. You can object as explained in section 16.
| Purpose | Legal basis |
|---|---|
| Account, access, requested profile display, discovery, messaging and membership | Performance of a contract: GDPR Article 6(1)(b). Special category information also requires an Article 9 condition. |
| Preventing abuse, security, investigating failures and handling reports | Legitimate interests: Article 6(1)(f); Article 6(1)(c) where action is legally required. |
| Special category profile information and selfie verification | Explicit, purpose-specific consent: Article 6(1)(a) and, where relevant, Article 9(2)(a). |
| Non-essential analytics and optional cookies | Prior consent as required by applicable law: Article 6(1)(a). See section 10 for the current iOS implementation. |
| Accounting or other mandatory records and valid legal requests | Legal obligations: Article 6(1)(c). Legal claims may rely on legitimate interests and, where necessary, Article 9(2)(f). |
5. Sensitive profile information
Profile fields about sexual orientation, sex life, health, religion or ethnic origin may contain special category personal data. Such information can be used for the profile and discovery choices you request, and be visible according to the relevant settings. Making information visible does not remove its protection as personal data.
Processing these categories requires an applicable GDPR Article 9 condition, such as your explicit, purpose-specific consent. The current general registration checkbox records acceptance of the terms and acknowledgement of the privacy policy; it does not record a separate explicit consent to sensitive profile processing. This policy does not substitute for that separate choice.
You can edit or remove supported fields in your profile. For withdrawal, access or erasure of sensitive information, including retained copies, write to support@freelove.hu. Hiding a field changes visibility; it does not by itself delete the stored value. Withdrawal does not affect earlier lawful processing, and functions that depend on the information may become unavailable.
6. Who can see your profile and content?
Other members can see your profile and content within the applicable visibility and album settings. A public profile link can show a limited preview without sign-in. Your sign-in email, phone number, full birthday and verification recordings are not part of that anonymous preview.
Private albums use access permissions: you can approve, refuse or revoke access. Messages and locations you send are available to the recipient. Recipients may save or copy material they can access, so later deletion or revocation cannot retrieve copies they made outside Freelove.
Profile visits, Footprints, connection requests and presence can be visible to other members as the relevant feature describes. Blocking stops direct private messaging between the two accounts. Hiding and presence controls have their own scope and do not guarantee that every trace of previous interaction disappears.
7. Location, camera, microphone and notifications
Nearby discovery, distance calculation and map features can use your chosen city, an approximate location derived from your IP address, or device location obtained with permission. On the public website, IP-based country detection also chooses Hungarian for Hungary and English elsewhere. A language you select yourself takes precedence. A location you send in chat is shared with its recipient.
Camera and selected-photo access support uploads, supported QR scanning and selfie verification. Microphone access supports voice messages and recordings where offered. Notifications use device or installation identifiers and push tokens, and may display message or interaction information on your lock screen depending on your settings.
You can change location, camera, microphone and notification permissions in device or browser settings. The related function may then be limited. Revoking a device permission prevents future access through that permission; it does not automatically erase material you have already uploaded.
8. Photo moderation and selfie verification
Uploaded photos can be checked using Google Cloud Vision and human moderation. Images may be sent to Google for objectionable-content analysis and face detection. Detecting whether a face is present or where it appears is different from identifying a person.
Where selfie verification is offered, a separate consent screen explains the guided selfie photographs or short video, private copies of the main profile photo, and the comparison process. Authorised reviewers compare the material with the profile photo. The process does not use identity documents or create a facial-recognition template. A verification badge is a photo-comparison result, not a background check or a guarantee of identity or conduct.
Verification material can be used again when your main photo changes. The configured retention period is 730 days from the later of submission or the most recent decision. You can withdraw verification consent on its screen; this requests removal of the material and removes the verification status. Account deletion also requests erasure of verification material. The erasure process may keep a minimal decision record separately; you can ask support to confirm the status of your request.
9. Service providers and recipients
We use the providers below for the functions indicated. What a provider receives depends on your platform and the feature you use. Providers acting on our behalf process information for the service they supply; stores and sign-in providers can also act as independent controllers under their own privacy policies.
Authorised staff and service providers may access information as needed for support, security and moderation. We may disclose relevant information to competent authorities where legally required, or to advisers and other recipients where necessary to establish, exercise or defend legal claims. We do not grant other members unrestricted access to private account records.
| Provider | Information and purpose |
|---|---|
| Google Cloud; MongoDB Atlas | Servers, stored databases and operation of the service. |
| Google Firebase Cloud Messaging / Installations; Apple APNs | Installation and push identifiers, delivery data and notifications. Used by native apps; web push operates only when its configuration is enabled. |
| Google Maps / Places; Google Cloud Vision | Map and place requests and related technical data; content checks on submitted images. |
| Mailgun; Twilio | Recipient email or phone number, sign-in and service messages and delivery information. |
| GIPHY | GIF searches and selected GIF loading; search terms, content and network information. |
| Apple / Google stores and identity services | Information associated with the chosen sign-in method, purchases and membership receipts. |
| Google Firebase Analytics / GA4 in iOS | Usage events, installation/member identifiers and the information in section 10. |
10. Analytics and marketing
The current iOS app enables Google Firebase Analytics when the app starts. It can send app and screen events, sign-in method, purchase events and member or conversation identifiers associated with interactions. The signed-in member identifier can be linked to these events, so these are not anonymous statistics.
The iOS app currently has no separate in-app analytics-consent switch. The website’s cookie choices and the device’s notification permission do not switch off this measurement. Contact support@freelove.hu about access, objection or erasure concerning these records. Publishing this policy does not supply any prior consent required for optional analytics.
The current Android app uses Firebase Messaging and Installations without Firebase Analytics or Crashlytics. www.freelove.hu does not load Google Analytics or an advertising pixel. Technical and security logs needed to operate the service are separate from optional audience measurement.
Accepting the terms does not subscribe you to marketing or authorise cross-app advertising tracking. Any marketing consent required by law must be separate, and can be withdrawn without withdrawing from ordinary service messages needed for your account.
12. Retention periods
Retention depends on the purpose, the account or content deletion request, unresolved reports or claims, and applicable legal obligations. Closing an account and removing its active content are different from deleting every retained record. The specific current exception for closed accounts is explained in section 13.
The current service does not promise automatic deletion after six months or two years of inactivity. Do not rely on inactivity or uninstalling the app to erase your information. Use account deletion or send an erasure request.
| Information | Period or erasure condition |
|---|---|
| Active account, profile, albums and messages | Until you delete the account or the relevant content, subject to the retained records described below. |
| Selfie verification material | Withdrawal, account deletion or the configured 730-day period from the later of submission or the latest decision. Ask support to confirm erasure if needed. |
| Completed account-deletion request receipt | 30 days to recognise and safely confirm a retried request. Pending deletion recovery state remains until the request completes. |
| Reports, security records and legal claims | For resolution of the specific incident or claim and any required legal preservation period. The relevant matter and legal requirement determine the period. |
| Accounting records | Eight years where Hungarian accounting law requires Easynet Kft. to retain the document. This does not apply indiscriminately to profile or message content. |
| Operational logs and backup copies | Logs and backups can remain separately from active records. A uniform fixed expiry is not currently specified; contact support for the period and status applicable to your information. |
| Separate records of closed accounts | Currently retained without an automatic expiry. These identifiable records are described in section 13; you can request access or erasure. |
13. Information that remains after account deletion
When an ordinary member account is deleted, the active account is removed, but a separate administrative record is retained. It can contain the member identifier, username and display name, email, phone number, sign-in provider identifier, IP addresses, location, birthday, interests and account-activity dates. This record contains identifiable personal information; it is not an anonymous deletion receipt.
This separate record currently has no automatic expiry. Its purpose, legal basis and retention limit are being reviewed. We therefore cannot say that account deletion immediately erases all personal information, or that only the 30-day request receipt remains.
You can request a copy, restriction or erasure of retained information by writing to support@freelove.hu. We must assess the request under the applicable data-protection rules and explain any lawful reason for continued retention. Disclosure of this practice does not remove your rights or create a legal basis for otherwise unjustified retention.
14. Requesting deletion
You can initiate account deletion in the app’s account settings or at freelove.co.uk/fioktorles. The web flow verifies control of your account email using a code and does not require app sign-in or a paid subscription. If you cannot access that email or the deletion function, contact support@freelove.hu.
Deleting the account ends access to the active profile and initiates removal of its content and connections. The retained information described in sections 12 and 13 is separate. Copies already saved by another person outside Freelove cannot be recalled by deleting your account.
Uninstalling the app does not delete your account. Deleting your account does not cancel an App Store or Google Play subscription; cancel automatic renewal separately in the store account used for purchase.
15. International transfers and security
Some providers may process information outside the EEA, including in the United States. Transfers require a condition under GDPR Chapter V, such as an applicable adequacy decision or appropriate contractual safeguards with supplementary measures where needed. Contact us for information about the recipients and safeguards used.
Traffic is protected by HTTPS/TLS, access is permission-based and private media has separate access controls. Chat is not end-to-end encrypted: servers may access content to operate the service, investigate reports and take necessary legal action. This is not blanket permission to read private conversations arbitrarily.
16. Your rights and complaints
You may request access and a copy, correction, erasure, restriction and portability where the legal conditions apply. You may object to processing based on legitimate interests and withdraw consent. Send requests to support@freelove.hu; we may require proportionate identity verification to protect the account.
We normally respond within one month. Complex or multiple requests may require up to two additional months; we explain an extension within the first month. Exercising rights is normally free.
Discovery filters and ordering may use profile information, interests, settings and location. If you disagree with an automated check or restriction, ask support for human review.
You may complain to Hungary’s National Authority for Data Protection and Freedom of Information (NAIH), naih.hu/ugyfelszolgalat-kapcsolat, or the competent authority in your habitual place of residence, and seek a judicial remedy.
17. Changes to this notice
The date and version above identify this policy. It updates the description of the current apps and website; it does not retroactively obtain consent or change the legal basis of past processing. We will provide appropriate notice of material changes and obtain a separate choice where a new purpose requires consent.
The Hungarian and English versions describe the same practices. If you notice a discrepancy or need help understanding how a passage applies to your account, contact support@freelove.hu. The Terms of Use are available at freelove.co.uk/terms.