Legal

FindLove Cookie Policy

Websites: https://www.findlove.lk and https://match.findlove.lk

Mobile app: FindLove for Android and iOS

FindLove uses cookies and similar browser storage to keep its websites working, protect accounts, and support requested features and preferences. This Cookie Policy explains these technologies and the controls available to you. It also explains local storage and notification choices in the FindLove native Android and iOS app; broader personal-information processing is covered by our Privacy Policy. We no longer load Google Analytics or use persistent referral-tracking cookies, and do not display an optional analytics-cookie prompt.

FindLove does not display advertising, operate advertising or remarketing pixels, sell cookie-derived information, or use marketing-site analytics to track private matchmaking activity. This Cookie Policy supplements our Privacy Policy and Terms and Conditions.

01

Who operates FindLove

FindLove is currently operated by Mohamed Ziyan Junaideen, an individual based in Sri Lanka. You can contact us about cookies and privacy at legal@findlove.lk.

02

What cookies and similar technologies are

A cookie is a small piece of information a website asks your browser to store. Cookies can recognise a sign-in session, protect a form from abuse, or remember a requested preference. Some last only for a browsing session; others remain until expiry or removal.

Websites can also use local storage, session storage, and similar browser technologies for related functions. In this policy, references to cookies generally include those technologies when they perform a comparable role. First-party cookies are set in connection with FindLove's websites; third-party technologies are provided by services such as Google or Cloudflare.

03

How the FindLove websites differ

  • www.findlove.lk is our public information and marketing website. It uses essential site and security technologies. We count public page requests on our server without analytics cookies or visitor identifiers.
  • match.findlove.lk is our account-based matchmaking website. It uses sign-in, security, and requested feature storage. Private profiles, messages, matches, and member browsing are outside public website reporting.
  • vendors.findlove.lk, events.findlove.lk, marketplace.findlove.lk, and authenticated dashboards do not participate in public website request counts.
  • Cloudflare Turnstile protects registration and contact forms against automated abuse.

No member profile is publicly browsable without an account. Access to matchmaking does not depend on optional website tracking. Cookies required for sign-in and security must remain available for those functions to work.

04

Strictly necessary cookies and storage

Necessary cookies or comparable storage are used only for functions that support operation, security, or a service you request. Depending on the page and browser, these functions include:

  • Keeping you signed in and maintaining an authenticated session.
  • Protecting forms and requests against forgery, abuse, and automated submissions.
  • Remembering requested display and interface preferences.
  • Supporting account security and features you actively use.

We do not use necessary cookies to send advertising or sell information. Blocking them may prevent sign-in, form submission, or other requested features from working.

Google sign-in and temporary signup storage

Choosing Continue with Google redirects you to Google for authentication. Google may use its own cookies for account selection, sign-in, and security under its cookie information and Privacy Policy. These Google-domain cookies are controlled by Google and your browser settings. This requested sign-in function is separate from public website statistics.

FindLove uses its first-party _core_key session cookie for the resulting account session and, for a new member who has not finished signup, the Google account identifier, email, name, and issue time. It is shared across FindLove subdomains, is not readable by page scripts, is not sent with requests that other websites make in the background, and is sent only over HTTPS in production. The cookie is signed against tampering but its contents are not encrypted. It is a browser-session cookie with no fixed persistent expiry set by FindLove; browser session-restore settings may retain it.

The pending Google signup is accepted for at most 30 minutes, after which you must restart Google sign-in. That validity limit does not itself erase the cookie's data: pending details can remain until the session is cleared or replaced, including on successful sign-in or logout, or until you remove the cookie in browser settings.

The signed state value sent through the redirect is valid for 10 minutes and is carried in the sign-in URL rather than a separate cookie. The Google authorization code and temporary access token are used to fetch sign-in details and are not stored in FindLove's session cookie. No Google access, refresh, or ID token is persisted by FindLove. Deleting cookies or signing out does not remove the account's Google identity link from our database; retention and account deletion are explained in our Privacy Policy.

05

Aggregate public website statistics

We increment daily totals for successful page requests by visitors who are not signed in on www.findlove.lk. Totals are grouped by fixed page categories and broad source categories, such as Google, ChatGPT, direct, internal, or other. Article and location paths are grouped by route, without retaining slugs or location values. Unrecognised sources become other. We do not store raw referrer URLs, campaign values, IP addresses, browser details, account identifiers, individual request timestamps, or event histories in these statistics. No analytics cookie, local-storage identifier, fingerprint, or third-party analytics script is used.

Counts include reloads and automated requests. They are not unique-visitor or session counts and do not include moving between pages without a full page load. Signed-in requests, account and sign-in routes, token-bearing URLs, other hosts, and unsuccessful responses are excluded. Sources are classified for the current request only; they are not remembered across visits or attached to registrations. Aggregate totals have no automatic expiry. Ordinary infrastructure and security logs remain separate and are described in our Privacy Policy.

06

Cloudflare Turnstile and error monitoring

We use Cloudflare Turnstile to identify potentially automated or abusive requests on registration and contact forms. It can process technical browser and security signals when a protected form is used. Depending on the configuration, security technologies may use cookies or similar mechanisms. Cloudflare Turnstile may use a cf_clearance cookie if its optional pre-clearance feature is enabled; the presence of that cookie is not assumed for every visit or setup. We use Turnstile for form security, not advertising.

We also use Sentry for software error monitoring. Error reports can include technical browser, device, or request information when a problem occurs. Sentry is not our marketing analytics system, and we do not use its diagnostic information for advertising. Error monitoring does not necessarily require a Sentry cookie; whether any related browser storage is present depends on the deployed configuration and features. See our Privacy Policy for more information about diagnostic data and service providers.

07

Your privacy controls

There is no analytics-cookie consent prompt because we no longer use analytics cookies. Our aggregate counter respects browser requests carrying Global Privacy Control (Sec-GPC: 1) or Do Not Track (DNT: 1); enable a supported browser privacy control to exclude those requests. Contact legal@findlove.lk about other privacy requests.

When old tracking cookies are present, FindLove sends expiry instructions for accessible _ga*, _findlove_referrals, _findlove_cookie_preferences, and _findlove_consent_receipt cookies. Browser settings can remove any remaining copies. An earlier refusal excludes the request carrying that old preference while the cookie is retired. Existing account-linked consent evidence and referral history remain historical records; no new website choices or referral histories are linked to accounts. Account deletion removes those account-linked records. Removing cookies does not erase information already sent to Google.

09

Providers and international processing

The relevant providers are FindLove, Cloudflare Turnstile for form security, Sentry for diagnostics, and Google for requested sign-in. App notifications use Expo Push Service, Google Firebase Cloud Messaging (Android), or Apple Push Notification service (iOS). Browser notifications use the browser's push service. These providers process relevant identifiers and payloads, including optional previews, and may process information internationally as described in our Privacy Policy. Public website aggregate counts stay in FindLove's database. Google Analytics data collected before we retired that integration remains subject to Google's retention and deletion arrangements; removing our integration does not automatically erase it.

We do not authorise advertising networks or data brokers to use FindLove cookies for their own marketing. For additional information about information processing, access, deletion, and international transfers, read the FindLove Privacy Policy.

11

Contact us

Operator: Mohamed Ziyan Junaideen

Privacy email: legal@findlove.lk

Websites: https://www.findlove.lk and https://match.findlove.lk

You may contact us to ask about a cookie, request further details about our current cookie settings, or exercise a privacy right under applicable law.

Questions about this policy?

Write to a person on our team. We read every message.