Last Updated: September 16, 2026
This policy governs one relationship between two subjects: what we do, and what you may require of us. The nine sections follow that order, each opening with our own action and its limit, then closing with the judgment you are entitled to draw from it. Nothing important is deferred to the final paragraph. NearLove is developed and operated by Gm Sadiuzzaman, and this policy takes effect for you at the moment the app is installed on your device.
This policy applies to the NearLove client, the web version, and every feature attached to them — nearby recommendations, likes and matching, direct messages, voice calls, the feed, and virtual gifts are all inside its reach. Information created, submitted or retained through any of those entry points is handled under this policy. Third-party pages embedded within the app answer to their own privacy rules, and we identify them where they appear.
The age premise comes first, because everything that follows rests on it. NearLove provides social services to adults, and the registration threshold is 18. No one under 18 may register, sign in, or use any feature. This app is not intended for minors, and we do not collect children's personal information on our own initiative.
Four principles constrain our handling: a stated purpose, the smallest possible scope, notice before the act, and consent that can be withdrawn. Any processing that falls outside what this policy describes begins only after your separate consent has been obtained.
Information arrives from four directions: what you hand over, what the system logs automatically, what your actions leave behind, and what the payment channel reports back. Each is set out below.
The following enters our system when you register, sign in and complete your profile:
So that the app runs on wildly different hardware, and so that a stall or a crash can be traced quickly, the system logs the following:
These records are produced alongside every tap, and you may not notice each one:
When membership benefits or virtual gifts are purchased, charging, settlement and reconciliation are performed entirely and independently by the official Google Play Billing channel. What arrives in our systems is confined to the order number, transaction state, item purchased and amount. Card numbers, payment passwords and verification codes neither pass through our servers nor find anywhere to be stored.
There are five uses, each mapped to the categories above, with no opportunistic repurposing:
Should a category of information be needed for a scenario outside those five, your consent will be sought separately before the act occurs, rather than announced afterwards in a line of notice.
We do not sell, rent or otherwise trade your personal information. To make the features work in practice, NearLove integrates the following third-party SDKs / services:
Advertising, analytics and push messaging — three processing activities in total — are carried out entirely through the third-party SDKs / services listed above; we build no equivalent capability of our own. Each provider processes data only within the limit of its own function and is bound by its own privacy policy, and we review its data-processing terms before integration.
Apart from the third-party SDKs / services, information leaves our systems only in the following cases:
Custody is split across four layers, so that no single layer bears the whole weight: TLS/SSL encryption runs throughout transmission; sensitive fields are written to disk under AES-256 with keys held separately; internal access is divided by role (RBAC), so that what any one employee can reach is compressed to the minimum their own work requires; and every read is logged, with those logs inspected on a rolling cycle and access that looks wrong triggering an alert without delay.
Three further arrangements sit alongside those layers: security assessments and penetration tests are each run at least once a year; personal information protection training for all staff is held on a recurring schedule; and a dedicated contingency plan covers data security incidents, proceeding in the order of containment, damage limitation and notification once triggered.
Retention is capped by what is necessary to achieve the purpose of the service. Approximate ranges are set out for guidance: account details last as long as the account does; device and technical information is generally kept across the most recent few release cycles for fault reconstruction; usage records are archived by statistical period, with anything beyond it aggregated; payment receipts are held for the statutory periods required by tax, accounting and audit rules. When a period ends, or when the law no longer requires retention, the data concerned is deleted, anonymised or de-identified.
The five rights below may be exercised through the in-app settings or by writing to the support mailbox, without any manual approval step:
Beyond those five, questions, objections and complaints about how information is handled are received in the same way. Once identity is verified, a reply follows within a reasonable period.
NearLove is open only to adults aged 18 and over and is not offered to minors. We do not collect children's personal information on our own initiative.
If an incorrect date of birth, a fraudulent registration or some other event we failed to anticipate causes a minor's information to enter the system despite all this, then once the situation is confirmed we delete the information and restrict the associated account from further use of this app, while also checking whether the same device or installation channel has been used to bypass verification at scale. The complete arrangement for child protection is set out in the NearLove Child Safety Standards, which parents, guardians and regulators may all consult.
Features are adjusted, the service model shifts, and legislation or regulatory expectations move on; whenever any of this happens, this policy is revised to match. A revised version is announced in two places at once — inside the app and on the official website — and the date carried at the head of the document is brought up to date alongside it. An amendment bearing on your substantial interests is notified before it takes effect, by pop-up, by in-app message, or by another means that is hard to miss; where the change genuinely warrants it, fresh consent is requested from you.
For questions, comments or complaints about this policy, about how information is handled, or about exercising your rights, you can reach us through the channels below:
App Name: NearLove
Developer Name: Gm Sadiuzzaman
Registered Address: 6045 Teesdale Ave, North Hollywood - 91606-4422, United States (US)
Support Email: service@nearlove-chat.com