CupidLane Privacy Policy

Last updated: September 16, 2026

Think of personal information as a piece of luggage. It has a platform of departure, a transfer in the middle, a room where it waits, and a day when it is handed back to its owner. This policy is that itinerary, written strictly in the order the information actually travels — from the first moment of collection to the final moment of erasure, with every stop along the way stating why it is made, how long it lasts and how the contents are guarded. CupidLane is published and operated by KHVISUALS LLC, which is also the legal entity. The itinerary takes effect the moment the app lands on your phone.

Journey 1 — Departure: the four categories that board here

One check comes before anything else, and it does not belong at the end of a document. CupidLane is not intended for minors, and no visitor below the age of 18 can complete registration — date of birth is a mandatory field, and an entry under that age is stopped at the instant of submission. That same check fixes the premise for everything that follows: with minors outside this journey, children's personal information is not something we collect on our own initiative.

Collection obeys a single measure: enough, and no more. Four categories are involved, each with its own source and its own destination, taken one at a time below.

Account information, handed over by you

During registration, sign-in and profile completion, the following enters the system:

  1. an email address, which serves as the sole credential for signing in;
  2. a nickname and an avatar;
  3. gender and date of birth, the latter used only to confirm that you have reached 18;
  4. your city, used for nearby recommendations and distance display;
  5. a short bio, interest tags, and any other profile detail you later add or amend.

An account can usually still be created without one of these items, but nearby recommendations and profile display will visibly drift, and other people will have trouble recognising you.

Device and technical information, logged automatically

So that the app runs steadily across very different handsets, and so that a crash or a stall can be reconstructed quickly, the system logs the following:

  1. an app-level anonymous device identifier such as Android ID;
  2. device model and manufacturer brand;
  3. OS version and security patch level;
  4. screen resolution and pixel density;
  5. system language and regional settings;
  6. the installed Google Play services version, together with the channel the app was installed from;
  7. the on-or-off state of developer options and root access.

Usage behaviour, left behind by your own actions

These records arise from taps and are not always noticed by the person producing them:

  1. how far each onboarding step was completed, and where abandonment occurred;
  2. how often a like signal was sent, withdrawn, or answered;
  3. how many gallery photos were uploaded, and the review outcome for each;
  4. the number and cumulative length of voice messages recorded;
  5. how frequently the nearby list was refreshed, and the radius that was set;
  6. session length per visit and the count of cold starts;
  7. how many times you were reported, and the conclusion reached in each case.

Such data serves two ends: reconstructing a problem as it happened, and deciding where the next version should spend its effort.

Payment information, of which only a receipt reaches us

When a membership benefit or a virtual gift is bought, charging, settlement and reconciliation are carried out entirely and independently by the official Google Play Billing channel. What arrives in our systems is confined to the necessary receipt: order number, transaction state, item purchased and amount. Card numbers, payment passwords and payment verification codes neither pass through our servers nor find any place to be stored there.

Journey 2 — Transfer: where each category is sent

Information is not tipped into a pool to be drawn on at will. Five purposes correspond to the four categories above:

  1. Running the service — registration, sign-in, profile display, nearby recommendations, like signals and voice messages all rest on this one;
  2. Improving the service — which step loses people and which build stutters can only be read from onboarding completion and fault logs, and release planning follows from that reading;
  3. Protection against abuse — bulk registration, automated volume inflation, account takeover and romance fraud are identified and blocked under this heading;
  4. Customer support — enquiries, appeals and reports you send are carried by this heading, with the conclusion returned along the same line;
  5. Legal compliance — duties set by applicable law and by regulators are discharged here, and lawful investigations are assisted on the same footing.

Should some category of information be needed for a scenario outside those five, your consent will be sought separately before the act takes place, rather than described afterwards in a sentence of notice.

Journey 3 — The fork: which information pauses in third-party hands

Selling, renting or otherwise trading your personal information is not among our options — it was not in the past, and it will not be added in the future.

To make the features work in practice, CupidLane integrates third-party SDKs / services, namely Cloudinary (storage and delivery of image and voice assets), SendGrid (transactional email delivery), Braze (push and in-app messaging), Snowplow (event analytics) and Mintegral (advertising and monetisation). Advertising, analytics and push messaging — three processing activities in total — are all carried out through the third-party SDKs / services listed above. Each party processes data only within the limit of its own function, and each is bound by its own privacy policy.

Beyond that, information changes hands only at the following points:

  1. you have given separate consent or express authorisation for one particular sharing;
  2. where necessary functions such as payment, push and statistics have to be delivered, information is handed to a commissioned partner in the smallest possible scope, and that partner bears confidentiality duties equal to our own;
  3. a judicial or regulatory authority lawfully demands disclosure, or applicable law directly so provides;
  4. sharing is genuinely indispensable to protecting someone's physical safety, the security of the platform, or a substantial public interest;
  5. a merger, acquisition, reorganisation or transfer of assets occurs, in which case information moves with the corresponding business, and the receiving party may not apply protection standards lower than this policy.

Journey 4 — The strongroom: after information is written to disk

Security is divided into four gates that connect to one another, so that no single gate carries the whole weight:

  1. In transit — TLS/SSL encryption is applied throughout transmission, leaving little room for interception or silent alteration;
  2. At rest — sensitive fields are stored under AES-256 encryption, with keys held separately and never mixed into the same place as business data;
  3. On access — permissions are split by role (RBAC), and the data any individual staff member can reach is compressed to the minimum needed for that person's own work;
  4. On audit — every read generates a log, logs are sampled on a fixed cycle, and anomalous access raises an alert at once.

Three further arrangements sit alongside the four gates: security assessments and penetration tests are each conducted at least once a year; personal information protection training is held for all staff on a regular schedule; and a dedicated contingency plan covers data security incidents, so that once triggered, containment, damage limitation and notification can all be completed within a short window.

Journey 5 — The stay: how long it lasts, and what happens at expiry

Retention follows one principle only: no longer than the period necessary to achieve the purpose of the service. To help you estimate, the approximate stay for several categories is set out below.

When the period ends, or when the law no longer requires retention, the data concerned is deleted, anonymised or de-identified. Where statute prescribes a longer term for a particular category, that category is kept for the statutory term and is likewise erased or anonymised once the term runs out.

Journey 6 — Return tickets: five you may use at any time

Control over information stays with you throughout. Five tickets may be used at any time, through the in-app settings or by writing to the support mailbox:

  1. Access — your account details and the processing records connected to them can be retrieved and checked at any time;
  2. Correction — where a record is wrong or incomplete, you may require us to correct, complete or update it;
  3. Erasure — you may require your personal information to be wiped; to leave entirely, start from the in-app path Settings → Account Management → Delete Account, or submit a request at the CupidLane account deletion page;
  4. Withdrawal of consent — consent given for a particular processing activity may be retracted at any time, without retroactive effect on processing already completed;
  5. A copy — a copy of your personal information is issued in a structured format, on request.

Beyond the five tickets, questions, objections and complaints about how personal information is handled are received in the same way. Once identity is verified, a reply follows within a reasonable period.

Journey 7 — The terminus: erasure, account closure, and the exception for minors

Luggage is eventually collected. Once a closure request is submitted, the winding-up runs in the following order.

One situation deserves separate treatment. CupidLane is not intended for minors, and children's personal information is not collected on our own initiative. If an incorrect date of birth, a fraudulent registration or some other event we failed to anticipate causes such information to enter the system anyway, then once confirmed, the information is deleted and the associated account is restricted from further use of this app. The complete arrangement for child protection is set out in the CupidLane Child Safety Standards, which parents, guardians and regulators may all consult.

Journey 8 — Route changes: when this itinerary is rewritten

Where product features shift, the service model changes, or new developments appear in legislation and regulatory expectations, this policy is amended accordingly. The new version is published in the in-app announcements area and on the official website, with the date at the top refreshed to match. Should an amendment touch your material interests, notice will be given before it takes effect by pop-up, in-app message or another means conspicuous enough to be noticed; where genuinely necessary, your consent will be sought afresh.

Journey 9 — The service desk: how to reach us

For questions, comments or complaints about this policy, about how personal information is handled, or about exercising your rights, you can reach us through the channels below:

App Name: CupidLane

Developer Name: KHVISUALS LLC

Legal Entity: KHVISUALS LLC

Registered Address: 19973 N 97TH Pl, Scottsdale, AZ 85255-6678, United States (US)

Support Email: service@cupidlane-chat.com