FindLove Privacy Policy
Websites: https://www.findlove.lk and https://match.findlove.lk
Mobile app: FindLove for Android and iOS
FindLove is a free service for adults who want to meet other people, particularly those interested in meaningful relationships and marriage. This Privacy Policy explains what personal information we collect, how we use it, who can see it, when we share it with service providers, and how you can manage or delete it. We do not sell or rent members' personal information, use matchmaking profiles for advertising, or use personal information for unrelated commercial purposes.
Please read this policy before creating an account, submitting verification documents, or choosing which profile information to reveal. Your choices about profile visibility are important because other registered members may be able to view and retain information you make available to them.
Last updated · 26 October 2026 Version 2026-10-26
Who is responsible for your information
FindLove is currently operated by Mohamed Ziyan Junaideen, an individual based in Sri Lanka (FindLove, we, our, or us). We are responsible for determining how the personal information described in this policy is used. Our contact email for privacy requests is legal@findlove.lk. If the service later moves to a registered business, we will notify members of the change and update this notice as required by law.
This policy covers the public informational website at www.findlove.lk, the account-based matchmaking website at match.findlove.lk, and the FindLove native Android and iOS app and its account API. Their data practices differ in important ways, particularly regarding website statistics, app storage, and notification delivery.
Our approach to personal information
We use personal information to register members, provide profiles and matching features, enable conversations, conduct requested checks, maintain accounts, keep the service secure, send operational communications, investigate reports, and comply with applicable law. We do not serve advertisements inside FindLove, sell personal information to data brokers, or give profile or messaging information to advertisers for targeting.
We use selected technology providers to host and protect the service and deliver its features. Those companies process relevant information on our behalf or in connection with their own technical services, subject to their applicable contracts and privacy terms. Use of such a provider is not a sale of member data. Public website statistics are described separately in Cookies and statistics on our websites.
Information you provide when registering
To create and operate an account, FindLove requires an email address and the following basic profile information: name, date of birth or information used to calculate age, gender, country, relationship intent (marriage-minded, serious dating, or either), and the gender of people you wish to meet. We verify email addresses before the account is used. These fields are needed for eligibility, member discovery, and matching features.
You may also provide a telephone number. We do not currently use SMS verification. We generally contact you through your account or email and may use a telephone number you provided for an important administrative matter if ordinary in-app or email contact has not been answered. We do not use telephone numbers for telemarketing.
Google sign-in
If you choose Continue with Google on a supported FindLove website, we redirect you to Google to authenticate. We request the openid, email, and profile permissions to receive your Google account identifier, email address, whether Google has verified that email, name, and profile-picture URL where available. These permissions do not give FindLove access to your Gmail messages, contacts, calendar, or Drive files, and we do not receive your Google password.
We use the Google account identifier to recognise you on later sign-ins. When first linking an identity, we require a Google-verified email and link it to an existing FindLove account with the same email, or use it to create an account after the applicable signup steps. We can use the Google name to prefill signup or initialise an account name. For a linked identity we store:
- The provider name, your Google identifier, the provider email, and whether Google has verified it.
- A link to your FindLove account, with creation and update times.
- The name and picture URL received when linking or refreshing the identity. The picture URL is not automatically imported as a matchmaking photograph.
A new member's unfinished signup retains only the Google identifier, email, and name, with a time limit as described in our Cookie Policy; once signup completes, the identity record initially holds those details and the verified-email status. Later Google sign-ins refresh the stored provider email, status, and profile data; they do not automatically replace your FindLove account email or edited profile details.
FindLove uses a Google access token temporarily to retrieve these sign-in details. We do not persist Google access tokens, refresh tokens, or ID tokens. Google sign-in is a requested account-access feature, separate from public website statistics. It does not enable tracking. Google receives the sign-in request and technical connection information and processes authentication under its own Privacy Policy. See Providers who process data, International access and transfers, and How long we retain information, and our Cookie Policy for session storage.
Optional profile information
Members can add information about themselves in independently controlled sections, including About, Education, Work History, Background and Values, and What You Are Seeking. The information may include photographs, religion, religious observance, family background and values, marital status, education, occupation, location, lifestyle details, interests, relationship expectations, and preferred characteristics of a potential partner. Apart from the required fields in Information you provide when registering, these details are optional and can be edited or removed. FindLove does not currently collect ethnicity as a separate profile field, although members may voluntarily mention it in free-text answers.
We process profile information to display it according to your permissions, help you discover and evaluate possible matches, and make the matching service work. We do not use sensitive profile characteristics to target commercial advertisements. Information you put in free-text fields or photographs may reveal additional details about you, so please consider carefully what you provide.
Device location and distance discovery
Sharing your device's location is optional. In the Android and iOS app, we request foreground location permission when you choose Share approximate location or Update to where I am now. With permission, that action reads the device's current latitude and longitude and sends a rounded position to FindLove for your profile. Granting permission alone does not share or refresh a position. We do not continuously track your location or collect it in the background, and you can browse without sharing it. On the matchmaking website, Use my current location or Update from this browser requests a position through your browser's location permission; you then choose whether to save it after viewing the approximate map preview.
The app and website round latitude and longitude to two decimal places before sending them, and the server applies the same rounding before storage. This is roughly kilometre-level precision, varying with latitude and the accuracy of the device reading; it is not an exact address or a guarantee of anonymity. This device-supplied position is separate from the country, city, or other location details you enter in your profile and from approximate location derived from an IP address for technical or security purposes.
We use the latest saved position to support distance filters, nearby discovery, and proximity ordering of profiles and daily introductions. You are the only member who can see your saved coordinates. Other members do not receive your coordinates, position history, or a numerical distance to you, including through friend or match access. However, appearing in distance-filtered or proximity-ordered results can reveal approximate proximity. Authorised FindLove administrators can access saved locations for account support, administration, and safety. Our hosting provider processes stored positions as part of hosting the Service. Website map previews load tiles from OpenStreetMap, which receives your IP address and requests identifying the approximate area displayed; the native app's location control does not load this map preview.
Each save records the rounded position, the profile it belongs to, and the time saved. A new save replaces the position used for discovery but keeps earlier saves as position history. There is no automatic time-based expiry: the latest position and earlier history remain until cleared or the profile or account is deleted. Signing out, uninstalling the app, pausing a profile, choosing Any distance, or revoking location permission does not delete an already saved position or its history. A saved position can continue to be used for proximity features without another device reading.
In the app's Discover distance control, Clear saved location removes your profile's current position and all its position history from the active database. Remove location on the website does the same. Clearing stops use of that saved position for distance discovery and ordering, while leaving manually entered profile-location fields unchanged. You can clear a saved position without granting location permission. Deleting the profile or account also removes the saved position and history. Previously saved positions can remain in database backups until backup rotation, as described in How long we retain information. Revoking permission in your device or browser settings prevents future device readings but does not perform this deletion; use the clear or remove control as well if you want an already saved location removed.
Who can see your profile
Member profiles are available only to signed-in members who are permitted to view them. A visitor without an account cannot browse member profiles, and we do not intentionally make member profiles available to public search engines. A member you have blocked should not be able to view your profile through their blocked account.
FindLove offers separate visibility controls for About, Education, Work History, Background and Values, and What You Are Seeking. Each photo has its own visibility control. Depending on the control you choose, an item may be visible to:
- Members only: all registered and signed-in FindLove members who are permitted to view your profile, excluding members you have blocked. This setting does not make your information available to visitors who are not signed in or to public search engines.
- Anyone Verified: signed-in members whose accounts have the relevant verification status.
- Matches and Friends: the accepted relationships supported by the matching or friendship feature.
- Hidden: not displayed to other members through ordinary profile views.
For new profiles, About, Education, Work History, and Background and Values start with Members only visibility. What You Are Seeking starts Hidden. Existing profiles keep their saved section audiences; changing the defaults does not change an existing member's settings. Review the audience beside each section before saving and change it whenever you wish. The About audience controls your biography; basic discovery details, such as your display name and age, remain available to eligible signed-in members. Family background and social links have additional friends-only restrictions. Each photo has its own visibility setting and should be reviewed before it is revealed. You can also use Pause My Profile to stop ordinary profile discovery temporarily, subject to any conversations or information you have already shared.
Changing a visibility setting limits future access through the Service but cannot erase screenshots, copied details, messages, or photographs another person has already retained. We do not guarantee that every member will respect a request to keep information confidential.
Sensitive information and consent
Some information used by a dating service can be especially sensitive. Religion, religious observance, family background, lifestyle answers, and gender or partner preferences may reveal beliefs or sexual orientation. We use these details for the matching and member-display functions and internal reporting described here, subject to applicable legal conditions. The Background and Values answers listed below are optional and are used only if you choose to provide them. We do not use them for advertising, sale, or unrelated profiling. We do not currently collect ethnicity as a separate profile field.
Where applicable law requires a separate basis or explicit consent for collecting, displaying, or using particularly sensitive data, we request it through the relevant controls rather than relying solely on your acceptance of our Terms and Conditions. Optional sensitive fields can be removed from your profile.
Background and Values answers are optional and separate from the section's audience. If you provide them, we store them, use them for compatibility and discovery, display them to your chosen audience subject to additional field restrictions, and include them in internal demographic reporting. This applies to religion, religious observance, marital status, children, family background, values, diet, alcohol use, and smoking status (the covered answers). We do not analyse free-text family-background answers for demographic reports. This does not cover required profile details or free text in other sections.
In the Background and Values section on the website and in the app, you can choose Remove previously saved answers. This clears all of the covered answers. It stops future use of those answers for matching, member display, and demographic reporting without closing your account. Deleted answers may remain in database backups until those copies are removed through backup rotation, but are no longer used for those purposes.
Hiding and removing answers are different choices. Selecting Hidden prevents other members from viewing the section through ordinary profile views, but does not itself erase answers or stop their other permitted use. Select Remove previously saved answers to remove the covered Background and Values answers and stop their future use, or remove other optional fields through the relevant profile controls.
What You Are Seeking can remain Hidden while its preferences support discovery and daily introductions. Removing Background and Values answers does not erase your age or other required profile details, or stop permitted reporting that does not use the removed answers. Daily introductions already selected before removal are not recomputed; removal stops future use of covered answers rather than undoing earlier selections.
If you withdraw an optional consent, we will stop the affected processing and erase or restrict the relevant data where required, subject to lawful retention obligations. Withdrawal does not undo processing already carried out lawfully or remove copies another member has independently retained. Some core information, such as the age and partner-gender details needed to run the account, cannot simply be removed while preserving all matchmaking functionality; you can ask us about your options or delete the account. We will not treat accepting this Privacy Policy as blanket consent for all sensitive uses.
Internal demographic and service reporting
We use account, profile, and service-use records to calculate internal statistics about our membership and how FindLove is used. Reports include age bands and median age, gender, broad and profile-entered location, languages, relationship intentions and partner preferences (including sought age ranges and gender), profile completion, activity, sign-in methods, and counts of interactions. They help us understand membership coverage, engagement, and opportunities to improve onboarding and matching features. Covered Background and Values answers you provide contribute to these reports, even when the section is Hidden, until you remove them. We do not analyse private message contents, biographies, family-background prose, or seeking notes for these reports.
Reports are restricted to authorised administrators and show grouped figures rather than member names, email addresses, exact dates of birth, or individual message contents. Small groups and combinations of characteristics can still identify someone indirectly; grouped reporting is not a guarantee of anonymity. Profile reports count profiles, while account reports count accounts; their populations and reporting periods can differ. Reports reflect records available when calculated, rather than an immutable history of everyone who has ever registered. Deleting records or removing covered answers affects subsequent calculations. We do not retain a separate demographic-report snapshot through this feature. This reporting is separate from aggregate public website request counts.
Photographs and private sharing
You may store profile photographs with visibility controls set individually for each image. Private photographs may be revealed to a selected member during a conversation using photographs already held in your account. The messaging feature does not currently allow you to attach newly uploaded photographs to a chat message.
When you choose to reveal a photo, the intended recipient can view it through FindLove under the applicable feature. They may still screenshot, copy, or photograph what they see. We prohibit unauthorised redistribution through our Terms, but we cannot technically guarantee that a recipient will not retain a copy. Deleting or hiding a photo removes or restricts it within our Service, subject to normal deletion processing and applicable retention exceptions.
Messages, matches, and reports
We store private messages in FindLove's own database on our application servers, together with information needed to deliver conversations, manage matches and friendships, apply blocks, and support reports. We do not use the contents of private conversations for advertising or train an AI moderation service on them. FindLove does not currently use AI moderation.
Private messages are not guaranteed to be end-to-end encrypted or inaccessible to authorised FindLove personnel. When a report or serious safety issue is raised, we may review relevant messages and reasonably necessary conversation context, account records, photographs, and report details to investigate harassment, impersonation, fraud, or other suspected violations. We limit this access to legitimate investigations, security matters, or lawful requests; we do not promise that every conversation will be proactively read or monitored.
When an account is deleted, its private conversations are deleted from active messaging for both participants, subject to limited records lawfully needed to investigate abuse, preserve evidence, or respond to legal obligations. Members may have retained their own copies outside the Service. Reports and moderation records linked to deleted profiles are removed. Before deletion, an authorised administrator may approve a limited report snapshot or specifically selected supporting text for an investigation involving an existing account, with a recorded necessity, case reference, approver, and future expiry. This does not preserve the entire account or conversation, and does not prevent an administrator from fulfilling a reviewed account-deletion request.
Ordinary selected case evidence expires 365 days after the later of recorded case resolution or deletion of the subject account. Either event updates the expiry of evidence that is still preserved; it does not restore anything already released or expired. Until either event has been recorded, an open investigation has an administrator-selected expiry within 365 days of its latest necessity review. Continued preservation requires an explicit review with a current reason and dated expiry; an open case is not an indefinite hold. Case resolution can be recorded after account deletion. We release evidence sooner when it is no longer necessary. Resubmitting the same resolution or reviewing a resolved case does not restart its ordinary retention clock.
A specific documented legal obligation can justify a longer, explicitly dated exception. Those legal expiries are not automatically extended by account deletion or case resolution. Evidence and preservation controls are restricted to administrators, and expired evidence is hidden from that view and automatically erased by the scheduled expiry process. A limited audit records approvals, reviews, resolution, deletion events and early release, with reasons, actors and dates but without a separate copy of the selected evidence. After early release, that audit remains only until the evidence's approved expiry; the audit is also erased on that schedule. Ordinary resolved source reports are erased 365 days after their recorded resolution, or sooner when a linked profile or account is deleted. Erasing an old report does not undo a profile or account ban.
Identity and education verification
Verification is optional. You may upload a Sri Lankan national identity card, passport, or other relevant identity document, and educational certificates or comparable records to request identity or qualification verification. We review the submitted evidence and may accept or reject the request.
We collect the uploaded evidence, its file information, your selected document category, and any note you submit. The evidence itself may contain document numbers and other personal information. The verification request also records the account and relevant profile or qualification, the submitted profile name and date of birth or qualification details, request instructions and additional metadata, submission history, decisions, reasons for rejection or revocation, and the people and times involved in creating and reviewing the request.
Authorised administrators may record a more specific document type, issuing authority, document number, issue and expiry dates, and private review notes. Recording a document number is optional; members do not need to enter one separately to submit evidence. These private administrator-recorded details are excluded from member-facing pages, API responses, and notifications. You can see your own submission history, notes, and decision reasons. Other members can see the relevant verification status through the applicable profile features, but cannot view your verification documents or private review records.
Each uploaded document file is queued for deletion from active DigitalOcean Spaces storage immediately after its review is approved or rejected, including rejected files that are later replaced. Ordinary download and preview access ends immediately at that decision. Deletion is handled by a background job that retries automatically after a failure, and normally follows within seconds, although processing or technical failures can cause a delay. A resubmission is new evidence kept for its own review; it does not extend retention of earlier uploads.
Where a specific lawful preservation requirement applies, authorised administrators may document a hold on only the necessary files. Those files remain excluded from ordinary downloads after the decision. Holds have a recorded expiry, defaulting to no more than 12 months from approval; deletion resumes when the hold expires or is released. Only a specific documented legal requirement can justify a longer dated preservation extension. We do not back up verification uploads or retain versioned or archived copies of those files, including uploads stored under older storage paths. Restoring a database backup does not restore deleted document files.
Deleting an uploaded file does not delete the verification history or recorded document details, including any document number and notes. We retain these records in our database for the verification function while the account exists; there is currently no automatic time-based deletion of that history. Verification metadata and recorded document numbers are stored as ordinary database fields, without application-level field encryption.
When account deletion succeeds, the linked verification requests and recorded document details are deleted from the active database. All remaining verification uploads, including unreviewed submissions, are queued for deletion when the account is removed.
Separate upload-cleanup and lawful-preservation records can remain after that, including document and request references, deletion status and times, and any preservation reasons and administrator audit history. These records exist only to complete deletion and manage necessary preservation. Completed cleanup audit records expire after 12 months. Outstanding references remain only to complete deletion or a dated preservation hold, and a queued cleanup retains the storage reference until the file is deleted. These records have no separate document-number field, although free-text preservation reasons may contain personal information. Contact legal@findlove.lk for requests to correct or remove retained verification information. Database backups may still contain verification metadata and previously deleted document details until those backup copies are removed through rotation, as described in How long we retain information.
Verification is a limited document review. It is not a criminal history check, a guarantee that every profile claim is true, or a certification of another member's character or safety. Our Terms and Conditions explain the meaning of verification badges.
Technical security and diagnostic information
When you use FindLove, our systems may record IP addresses, approximate location derived from an IP address, login events, browser and device characteristics, request metadata, timestamps, authentication and session identifiers, security events, and error reports. This information is needed to deliver pages, protect accounts, investigate abuse, prevent unauthorised access, and diagnose failures. These records are not used to build advertising profiles.
We use Sentry for application error monitoring. When a request to our servers fails, the report can include browser and device details sent with the request, the page or API path, and the submitted parameters after passwords, tokens, and other filtered fields are removed. When the Android or iOS app crashes or reports an error, it sends the error details, device model, operating system, app version, and recent screens and network requests; the app does not send screenshots, screen recordings, console output, or an IP address as user information. We aim to avoid sending message contents, identity documents, passwords, or unnecessary sensitive profile fields in such reports. Sentry is set not to store IP addresses.
We use Cloudflare Turnstile on registration and contact forms to identify automated or abusive submissions; it processes browser and security signals necessary to provide that protection.
We restrict verification uploads to authenticated access by the account owner and authorised administrators during review. Private document details and preservation controls are restricted to administrators in the Service. Private file storage and these access controls do not provide application-level encryption of verification metadata or document numbers. No online system is completely secure, and we cannot promise absolute protection against every incident. If a data breach occurs, we will assess whether notification to affected persons or authorities is required by applicable law.
Emails and optional notifications
We use Amazon Simple Email Service (Amazon SES) to send account confirmation, welcome messages, password resets, important security information, policy-change notices, and other essential service communications.
Weekly summary email
We also send an optional weekly summary email. It is on unless you turn it off, and it is sent on Sunday morning in the time zone saved in your account settings, only when there is something new. It states how many of your conversations have unread messages, how many friend requests are waiting for you, and how many members viewed your profile during the past week. It does not include other members' names, photos, or message text, and it does not identify who viewed your profile.
To prepare it, we use your account email address, first name, and time zone, the message, friend-request, and profile-view records described in this policy, and a record of when the last summary period ended. You can turn it off under Weekly summary in Notification settings on the websites or in the app, or through the unsubscribe link in any summary; turning it back on requires signing in. Turning it off does not stop essential service emails or change your app and browser notification settings.
App and browser notifications
Optional notifications in the Android and iOS app and supported browsers announce new messages, received and accepted friend requests, and mutual matches. They require you to turn them on for that app installation or browser and grant the necessary system permission. The app does not request notification permission at launch. You can enable it from the Messages inbox or Profile → Notification settings. Permission alone does not opt a newly signed-in account into notifications. Notification permission is separate from acceptance of this policy. We do not use contact information for advertising campaigns or unrelated promotional mailings.
For app notifications, we store:
- A randomly generated installation identifier and an Expo push token.
- The Android or iOS platform, the registering account and API-session references, a registration version number, and registration timestamps.
The app keeps the installation identifier and a session-bound notification choice in secure device storage, plus a local installation marker to prevent restored storage from silently restoring consent. The installation identifier can survive sign-out and, on some devices, reinstall; it is not an advertising identifier. API sessions separately hold a session name, hashed authentication credentials, expiry and revocation information, and timestamps. These records let us route alerts to the right account, refresh tokens, apply choices, and stop new submissions when a session ends. Ordinary request and security metadata are described in Technical security and diagnostic information.
The app registers with Expo using the native Apple or Google push token, an Expo installation identifier distinct from FindLove's installation identifier, app and project identifiers, platform, and development or production delivery information. Expo and the platform services also process connection information needed for registration and delivery. FindLove sends notifications through the Expo Push Service, which relays them to Google Firebase Cloud Messaging (FCM) for Android or Apple Push Notification service (APNs) for iOS. They process the delivery tokens and notification payload, including the event type and profile, conversation, or connection identifiers needed to open the relevant screen. These identifiers are not authentication credentials.
Names and message previews are off by default. Generic alerts still reveal that you use FindLove and the kind of event. If you enable Show names and message text, app notifications can include the other member's profile name and, for messages, up to 150 characters of message text. Expo and Google or Apple then process that preview content as part of delivery; people who can see your device or notification display may also see it, subject to system settings. Browser push payloads remain generic; with previews enabled, the browser retrieves preview content from FindLove only through an eligible signed-in session.
Notification controls and sign-out
Notification settings in the app and on the websites share account-wide switches for messages, friend requests, matches, and previews, plus a message switch for your profile. Message alerts require both the account and profile switch. Turning off one app installation removes its registration without changing the other devices' choices; browser controls separately disable that browser. You can also deny or revoke permission in system settings and adjust Android notification channels and lock-screen presentation there. The app checks permission again when it runs or returns to the foreground and removes its server registration if permission has been revoked; restoring permission can resume an existing app opt-in. If turning notifications on or off fails, the app asks you to try again rather than reporting success.
Successful app sign-out revokes the API session and removes its push registrations before clearing local credentials and notification consent. If you are offline or a temporary failure occurs, sign-out can be retried; do not assume it succeeded until the app confirms it. Remote session revocation, password change or reset, and account deletion also remove the affected app registrations. Signing into another account requires a new notification opt-in. Uninstalling the app does not immediately notify FindLove: we remove an invalid registration when the delivery service reports it, and expired sessions are excluded from new submissions. Already submitted or delivered notifications, including previews, cannot be recalled by signing out, turning notifications off, or deleting an account.
Availability depends on the installed build, device, permissions, network, and service configuration. Notifications can be delayed, duplicated, suppressed, or lost; provider acceptance or handoff is not proof of display or reading. Reading a conversation during the short message delay can suppress its alert. Operating-system restrictions, including Android force-stop, can prevent delivery until the app is opened again. Check FindLove for current messages and matches rather than relying on push as a guaranteed or urgent communication channel. Push registration and outcome retention are described in How long we retain information.
Why we use data and applicable legal grounds
The reasons for processing depend on the information and law that applies. Account details, profile preferences, messages, matches, and essential notifications are generally needed to provide requested features and administer accounts. The optional weekly summary keeps you informed of activity on your account, and you can turn it off at any time. Security records, fraud prevention, report handling, and diagnostics support safety, legitimate operation, and applicable legal obligations. Covered Background and Values answers are optional and are used only if you choose to provide them, subject to applicable legal conditions. Aggregate public request totals help us understand and improve the public website without maintaining visitor records.
We consider proportionality and use only data reasonably relevant to each purpose. Where the law provides rights to object, withdraw consent, restrict use, or obtain an explanation, we will assess requests under the legal rules applicable to that user. The precise legal basis for a particular use may differ depending on the jurisdiction; contact legal@findlove.lk for a more specific explanation.
Providers who process data
We do not sell personal information. We use the following external services for specific functions:
- DigitalOcean: virtual private server hosting for the FindLove application and its database, and DigitalOcean Spaces object storage for photographs and verification uploads.
- OpenStreetMap: map tiles for website map previews, including requests identifying the approximate area displayed and the visitor's IP address.
- Amazon SES: delivery of essential service emails and the optional weekly summary.
- Expo Push Service: app push-token registration and notification relay, including delivery identifiers, payloads, and any previews you enable.
- Google Firebase Cloud Messaging (Android) and Apple Push Notification service (iOS): native device registration and notification delivery, including platform delivery identifiers and payloads relayed through Expo. Browser push services, which depend on the browser, can include Google, Apple, Mozilla, or Microsoft; they receive delivery endpoints and encrypted browser payloads.
- Sentry: software error monitoring and diagnostic reporting.
- Cloudflare Turnstile: protection of registration and contact forms from bots and abuse.
- Google sign-in: authentication and identity details when you choose this sign-in method, including the account-linking information described in Information you provide when registering. Google also processes the sign-in request and technical connection information under its own privacy terms; this is separate from notification delivery.
These providers receive the information technically necessary for their respective functions under applicable contractual and operational safeguards. We may disclose limited information to professional advisers, authorities, or other recipients where legally required or reasonably necessary to address serious safety incidents or enforce legal rights, subject to applicable law. We do not provide profile information to external matchmaking brokers, list vendors, or advertising data exchanges.
International access and transfers
FindLove is operated from Sri Lanka and is intended for members in Sri Lanka and internationally. Our DigitalOcean application server, database, and Spaces object storage use DigitalOcean's SGP1 (Singapore) region. Other providers may process service data in additional countries according to their systems and agreements. In particular, Expo and Google or Apple process app registration and notification data through their delivery infrastructure; that processing is not confined to our Singapore server or to Sri Lanka. This includes names and message excerpts if you enable previews. Browser delivery services may similarly process technical delivery data internationally. Sentry stores error reports in the United States. A person in another country can also see information you make available through the profile's selected visibility settings.
Where personal information is transferred across borders, we will apply safeguards required by applicable law, which may include appropriate provider agreements, contractual protections, and other measures. We will make further information available about relevant transfer arrangements where the law requires it. Choosing to disclose a profile field to members worldwide is separate from the transfer of information to our infrastructure providers.
Google sign-in also involves Google's international authentication infrastructure. Our copy of the linked identity and provider profile is stored in our Singapore-hosted database. Google's processing of the sign-in request, connection information, and its own account and security records may occur in other countries under the international-processing arrangements in Google's Privacy Policy; it is not confined to Sri Lanka or our Singapore server. We do not send your matchmaking profile or messages to Google as part of sign-in.
How long we retain information
We retain account details, profile information, matches, stored photographs, and messages while an account is active and the information is needed for the Service, unless you delete particular material sooner. Verification document files are queued for deletion after each approval or rejection, subject to the specific lawful preservation holds described above, and are not backed up. Verification history and recorded document details, including optional document numbers and free-text notes, remain separately from the files as described in Identity and education verification. Open reviews have no automatic age limit while the account exists. Verification history is removed with the account. Completed verification cleanup audits expire after 12 months, and preservation holds have dated expiry as described in that section.
Saved device positions and their history have no automatic expiry. They remain until you clear them or delete the relevant profile or account, with backup handling as described below. Updating a position retains earlier saves; revoking device or browser permission does not delete them. Device location and distance discovery explains these location controls and their effect on discovery.
Google identity links and stored provider profile data have no automatic age-based expiry while the FindLove account exists. They are refreshed on later Google sign-ins and deleted from our active database with the account. Signing out, deleting only a matchmaking profile, or removing the connection in your Google Account does not erase FindLove's stored identity record. You can manage the Google-side connection in your Google Account settings; use our account-deletion process to remove the FindLove account and its identity link. Removing the FindLove account does not delete your Google Account, its connection settings, or Google's independently held records. Existing backups follow the separate rotation described below.
App push registrations remain until removed or replaced as described in Emails and optional notifications; they have no separate automatic age-based deletion period. Session expiry stops their use for new submissions without itself guaranteeing immediate deletion. Local notification-choice and installation values remain until cleared or replaced by the app or device; sign-out clears notification consent but retains the installation identifier. Browser subscriptions remain until removed, replaced, their session is deleted, or the provider reports an invalid endpoint; expired browser sessions are excluded from new submissions.
For app delivery reliability, we separately retain a record of each notification attempt: event references, recipient account, profile, and device or session identifiers, a fingerprint of the push token (not the token itself), the registration version, submission and receipt times, attempt counts, the outcome and a reason code, and Expo delivery ticket identifiers. These outcome records contain neither message text nor plaintext push tokens. Completed, failed, cancelled, or unknown outcomes are automatically deleted 30 days after their last outcome update; active work and unresolved tickets remain until resolved or expired, then enter that period. Deleting the recipient account or profile removes its outcome records immediately. Removing a device registration or session alone leaves this limited outcome history until expiry. Independently held provider registration and delivery records follow the relevant provider's retention arrangements; removing a FindLove registration does not itself delete those records. Expo states that notification content is kept only in memory and queues as needed for handoff to Google or Apple. This does not mean all provider identifiers, receipts, or device-held notifications are erased at handoff.
After account deletion, we remove the member's account, profile, saved positions and position history, photographs, matches, preferences, and private messages from active service records for both sides of affected conversations, subject to limited lawful exceptions. The deletion process may be asynchronous. Database backups rotate separately from active records and can contain previously deleted information, including verification metadata and recorded document details. Every database backup, including snapshots taken before updates to the Service, is deleted within 30 days of being made, so deleted information leaves our backups within 30 days of its deletion. Backups are not used as an ordinary way to restore deleted member content.
Account-linked sessions, sign-in records, push registrations, consent receipts, verification history, reports, and moderation records are deleted with the account. Account deletion does not automatically create a preservation exception. After deletion, the following remain for the periods stated:
- Explicitly approved case evidence and its limited preservation audit, under the restricted, dated exceptions in Messages, matches, and reports.
- Operational deletion references, until cleanup succeeds, and completed verification cleanup audits, which expire after 12 months.
- Server logs recording requests, sign-in and security events, which are deleted within 30 days.
- Error reports already sent to Sentry, which Sentry deletes 30 days after receipt under our current plan. Account deletion does not remove reports already sent.
- Provider records outside the active account database, which follow their separately applicable retention arrangements. Account deletion does not selectively erase existing backups or independently held provider records.
- Daily aggregate public website totals, which have no automatic expiry and are separate from account records.
- Google Analytics data collected before we retired that integration, which follows the property's retention and deletion arrangements.
Access, correction, deletion, and other rights
You can update or remove many optional profile details and photographs through your account settings, change section and photo visibility, pause discovery, block members, disable weekly summaries, and delete your account. In Background and Values, the Remove previously saved answers control clears the covered answers while leaving your account active. You can contact legal@findlove.lk to request access to the information we hold, correction of inaccurate information, deletion, restriction or objection to particular processing, and a copy of applicable information where relevant law provides that right.
You may also ask to withdraw consent for processing based on consent. Hiding a field is not the same as withdrawing consent or deleting the underlying value. We may need to confirm your identity before acting on a request, particularly where another person's private information or the security of an account could be affected. We will respond within the time required by applicable law and explain any valid reason why we cannot fully carry out a request.
Where a data protection regulator has jurisdiction, you may have a right to complain to that regulator. Contact us first if you would like to give us an opportunity to resolve your concern.
Account deletion and remaining records
Choose Delete account in website account settings, on the app's Profile screen, or under Legal and support, or start on the website without installing the app. Request a code sent to your registered email, enter the code, and explicitly confirm permanent deletion. The server then automatically removes your account and every owned profile, including paused, banned, or archived profiles; no administrator approval or new identity-document upload is required. Our account deletion page explains each step, the time limits, and the retained records in detail. In summary:
- The deletion route works without accepting updated policies, and for banned accounts without restoring sign-in access.
- A code allows five attempts and expires 15 minutes after the request; email requests are rate limited. Receiving a code alone does not delete data, and you can cancel before confirmation.
- The result acknowledges active-record deletion and explains outstanding file cleanup. An offline or server error is not confirmation of success. Retrying a successful confirmation with the same valid code returns the same result.
- A deletion request temporarily holds the registered email, account reference, protected code, and attempt count. Completion clears the email and account reference, and the remaining retry receipt expires at the original 15-minute deadline. Expired requests and receipts are automatically removed.
- If you cannot access your registered email or need help, legal@findlove.lk remains an optional fallback for proportionate verification and administrator fulfilment.
We acknowledge requests promptly and complete deletion within 30 days of confirming account ownership; if something prevents that, we tell you why and when we expect to finish. Once the account is removed, FindLove stops ordinary profile discovery and removes the account's active content as described in How long we retain information, including your messages from the matchmaking system for both correspondents. File deletion runs through background jobs that retry after a technical failure. Only the limited approved exceptions and cleanup records described above remain. Browser and app sessions and saved push registrations are revoked with account removal. Google sign-in links are removed; FindLove does not hold a persistent Google access or refresh token. Already delivered emails and notifications cannot be recalled. Providers may retain independently required security or technical records as described in that section.
We cannot delete information already independently copied by another member, sent to an external address at your request, or otherwise stored outside our control. We also cannot immediately remove data from existing database backups; previously deleted database information may remain until those copies are removed through backup rotation. We do not keep archived copies of verification document images as part of that backup process.
Deleting your profile removes its details, saved position and position history, stored photographs, associated verification requests, reports, and conversations for both participants, while keeping your account. Pausing only stops ordinary discovery and keeps the profile data. Removing Background and Values answers clears them without deleting the account.
Users under 18
FindLove is for adults aged 18 and older. We do not knowingly permit people under 18 to register or participate in matchmaking or messaging. If we discover a minor has registered or submitted information, we may suspend access, investigate as appropriate, and delete the account and information as required by law. Please report the profile using the Child safety reason, or notify legal@findlove.lk, if you have reason to believe an underage account exists. Our Child Safety Standards explain how we prevent and respond to child sexual abuse and exploitation.
Changes to this Privacy Policy
We may update this policy as our features, service providers, privacy controls, or legal requirements change. The date at the beginning identifies the current version. For material changes, we will send an essential service email explaining the changes before they apply, unless urgent legal or safety reasons require earlier action. From the effective date, the website and app will ask you to review and expressly acknowledge the updated policy before continuing to use protected member features. Our public policies, support, and account-deletion request instructions remain accessible without that acknowledgement.
Policy acknowledgement is separate from permission for optional sensitive-data processing or analytics; where renewed consent is required, we will obtain it before the new processing occurs. Changes to mobile notification providers, notification payloads, or analytics on the matchmaking service require an appropriate review and policy update.
Contact us
Operator: Mohamed Ziyan Junaideen
Privacy email: legal@findlove.lk
Websites: https://www.findlove.lk and https://match.findlove.lk
For urgent physical danger or suspected criminal activity, contact the relevant local emergency service or law enforcement authority; a privacy email is not an emergency reporting mechanism.
Questions about this policy?
Write to a person on our team. We read every message.
We can't find the internet
Attempting to reconnect
Something went wrong!
Attempting to reconnect