This Privacy Policy applies to the Android app published on Google Play as "Nearby - Free Random chat" (package name com.securenearby.app), also referred to as SecureDateNearby ("we", "us", "our"), an adult social discovery app for nearby dating, messaging, file sharing, and encrypted audio/video calling.
Developer: Harsh, an individual developer operating under the domain securenearby.cc, listed on the Google Play Store as the publisher of this app.
Data Fiduciary: Harsh (trading as SecureDateNearby / Nearby - Free Random chat)
Grievance Officer: Harsh
Contact: [email protected]
Website: https://api.securenearby.cc
Primary jurisdiction: India
The Service is strictly for people aged 18 or older. We do not knowingly allow minors to use the app. If we learn that an account belongs to a person under 18, we delete and/or ban the account.
| Data type | What we process | Purpose | Typical retention |
|---|---|---|---|
| Pseudonymous identity | A user ID derived from your Ed25519 public key, plus public Ed25519, X25519, signed-prekey, and ML-KEM-768 public key material. | Account operation, request authentication, friend requests, encrypted session setup, exact-ID lookup, and routing. | Active account data is removed on account deletion or automatically after 30 days of inactivity (see Section 10). A minimal deletion/ban tombstone may be retained long-term so a deleted or banned account cannot recreate the same account on this server. |
| Google sign-in identity | Your Google account's email address and Google's stable per-app account identifier ("sub"), obtained by verifying a short-lived Google ID token when you sign in. We do not receive your Google password, contacts, Drive, or other Google data — only what a standard "Sign in with Google" grant provides (basic profile/email). | Identify which account is yours, let you sign in on a new or reinstalled device, and link an existing device-created account to your Google account. | Until account deletion or automatic 30-day inactivity deletion, at which point the Google-account link is removed and that Google account is free to be used to create a new, unrelated account. |
| Encrypted identity-key backup | An encrypted-at-rest backup (via Google Cloud KMS) of the private key material your device generated for your account (signing key, session-setup keys, and the keys used to encrypt your local database and friend/block backup). | So losing, resetting, or replacing your device does not permanently lock you out: signing in with the same Google account on any device restores this same key material. | Until account deletion or automatic 30-day inactivity deletion, at which point this backup is deleted along with the Google-account link (see Section 10). |
| Account-recovery audit log | Timestamp, IP address, and user-agent string recorded each time your encrypted key backup is successfully decrypted and returned after a verified Google sign-in. | Security auditing of this sensitive recovery capability, so unexpected or unauthorized recovery attempts can be identified. | Until account deletion or automatic 30-day inactivity deletion. |
| Public profile and compatibility fields | Display name, age, gender, bio, occupation, relationship goal, interests, favorite interests, profile prompts, anthem, values, lifestyle, personality sliders, relationship preferences, profile-completion/discoverability fields, visibility settings, distance-visibility setting, last-seen visibility setting, country label, and last-seen state. | Discovery, profile preview, compatibility percentage, filters, lucky matching, known-user lookup, and friend presence (including showing connections when you were last online, unless you hide it). | Current online presence expires after about 35 seconds. A recent-offline profile snapshot may remain discoverable for up to 24 hours. Lookup/bundle cache may remain for up to 30 days after activity. |
| Rounded location | Your device obtains a local location fix and rounds latitude/longitude to 0.01 degrees before sending it. Raw GPS coordinates are not intentionally sent to our server. Depending on latitude, Google Play may still classify this as precise location. | Nearby discovery, distance sorting/filtering, hidden-distance behavior, and recent-offline discovery. | Current presence about 35 seconds; recent-offline RAM/Redis snapshot up to 24 hours or until deletion/process cleanup. |
| Encrypted friend/block backup | An opaque AES-256-GCM ciphertext containing your in-app friends and blocked users, public keys, display names, timestamps, and relationship preferences. It does not contain your phone contacts or avatars. We cannot decrypt it. | Restore your in-app social graph after reinstall or device change. | Until account deletion or automatically after 30 days of inactivity (see Section 10); Redis cache may be refreshed with account activity. |
| Encrypted messages and service signals | Encrypted message envelopes and signed service signals, plus visible routing metadata: sender/receiver IDs, signal type, timestamps, message IDs, delivery/read/delete events, friend request/accept events, profile-photo preference updates, and WebRTC setup messages. | Message delivery, offline delivery, friend requests, receipts, delete-for-everyone, call setup, reconnection, and WebRTC setup. | Delivered signals are discarded after delivery. Undelivered call/WebRTC signals expire after about 15 minutes. Durable signals and sealed offline messages expire after up to 7 days. |
| Voice-note storage metadata and ciphertext | Cloudflare R2 object identifiers and encrypted voice-note objects. Voice notes are encrypted on your device before upload; the decryption key is sent only inside an end-to-end encrypted message. | Store-and-forward voice notes when the recipient is offline. | Normally deleted after successful download or account deletion attempts; bucket lifecycle removes remaining objects after up to 14 days. |
| Push notification data | FCM token, sender ID, sender display name, event type, message ID where applicable, call type, generic title/body text, collapse key, and recent push-delivery log entries. Message plaintext is not included. | Wake the app, show message/call notifications, support inline reply, and diagnose push reliability. | Token until deletion, invalidation, replacement, or automatic 30-day inactivity cleanup. Recent in-memory push log is capped. |
| Operational and security data | IP addresses, rate-limit records, request-error records, active chat-pair metadata, message counts, call type/outcome/route, transfer type/route/byte count, FCM registration state, dependency health checks, and admin-audit metadata. | Security, abuse prevention, reliability, rate limiting, diagnostics, and aggregate service operations. | Mostly bounded RAM/process lifetime or provider log retention. Active chat pairs expire after 24 hours of silence. Request/error/rate-limit logs are bounded. |
| Abuse reports | Reporter ID, reported user ID, selected reason, optional details up to 500 characters, reporter IP, timestamp, status, and related profile metadata available to moderators. When you use "Report" on a specific message or attachment, a short excerpt of that message's text (up to 1,000 characters) or the attachment's type is voluntarily included as evidence — we otherwise cannot see message content, since it is end-to-end encrypted. Message content is not automatically attached in any other case. | Safety review, enforcement, ban decisions, legal compliance, and child-safety response. | No automatic expiry currently; retained for moderation, enforcement, safety, and legal records, subject to applicable rights. |
| Block records | Blocker ID, blocked user's ID, an optional reason, and a timestamp. | Moderation visibility into blocking activity, so patterns of abuse are reviewable even though the block itself is enforced entirely on your device. | No automatic expiry currently; retained for moderation and safety records. |
| Device identifier (anti-abuse) | Your Android device's ANDROID_ID (a per-device identifier scoped to this app's signing key; it survives uninstall/reinstall but resets on factory reset), plus, on supported devices, a Play Integrity attestation token from Google confirming the app is unmodified and the device is not obviously compromised. | Anti-abuse signal only. Accounts are identified by your Google sign-in, not by device, so a device is no longer limited to one account — this data helps us spot device-level abuse patterns (e.g. automated mass account creation) without gating normal use. | Retained as an anti-abuse signal; not used for advertising, tracking across apps, or any purpose beyond abuse detection. |
| Data type | Where it lives |
|---|---|
| Private keys and local encryption keys | Generated on your device and stored there — Android uses SecureStorage backed by Android EncryptedSharedPreferences/Keystore where available; web builds use browser storage. A local fallback may be used if native secure storage is temporarily unavailable. An encrypted backup of this same key material is also held server-side so you can recover it after signing in with Google on a new device — see Section 3. |
| Message history, ratchet sessions, contacts, pending requests, avatars, file chunks, and file metadata | Stored in encrypted IndexedDB or native/local file storage on your device. The app may export non-key user data if you choose "Export my data first" before account deletion. |
| Theme, selected tab, call history, read-receipt state, notification settings, profile-photo sharing choice, large-file preference, and other local settings | Device-local storage. |
We do not sell personal data and do not use personal data for advertising.
| Service | Provider | Purpose | Data involved |
|---|---|---|---|
| Google Sign-In | Google LLC | Authenticate you and identify your account. | Google account email address and account ID (sub), obtained by verifying a Google-issued sign-in token. |
| Google Cloud Key Management Service (KMS) | Google LLC | Encrypts and decrypts the account key backup described in Section 3. | The encrypted key-backup ciphertext; Google performs the cryptographic operation, it does not otherwise store or use your data. |
| Firebase Cloud Messaging | Google LLC | Push notifications and app wakeups. | FCM token and notification metadata; no message plaintext. |
| Cloudflare | Cloudflare, Inc. | DDoS/TLS protection, optional TURN relay, and R2 encrypted voice-note object storage. | IP/request metadata, encrypted TURN packets when relay is used, encrypted voice-note objects, and object identifiers. |
| Railway and configured data services | Railway Corp. and configured infrastructure providers | Application hosting, server runtime, Redis/Postgres where configured. | Server traffic and operational data necessary to run the service. |
You do not have to delete your whole Nearby - Free Random chat (SecureDateNearby) account to have specific data removed. You can:
What is typically deleted on request: stored profile/compatibility fields, presence and location lookup snapshots, the encrypted friend/block backup, undelivered queued messages/signals, FCM push tokens, and voluntarily-submitted report details you authored.
What we keep, and for how long: the account itself remains active; the anti-abuse device/account binding described in Section 3 is not removed unless you delete your account; and moderation, safety, and legal records (such as reports about you, ban history, or provider/security logs) may be retained where required for safety, legal compliance, or dispute resolution, per the retention periods described elsewhere in this policy.
You can delete your account in Settings - Delete Account or contact [email protected].
Deletion removes your encrypted friend/block backup, encrypted key backup, Google-account link, account-recovery audit log, active presence, recent profile/location lookup data, queued encrypted messages/signals, FCM token, and active connection records from our application stores. The app also attempts to notify existing/pending contacts and delete outstanding encrypted voice-note objects you uploaded before wiping local signing keys. Removing the Google-account link also frees that Google account to be used to create a new, unrelated account afterward. A minimal tombstone is retained so the same deleted identity cannot simply be restored on this server. Reports, safety records, provider logs, and legal records may remain where required or appropriate.
Deletion wipes data from the device completing the deletion. Copies already delivered to another user's device are controlled by that user and are not removed by your account deletion.
Automatic deletion for inactivity: even if you never request deletion, an account that has been inactive for 30 days (no app activity that refreshes it, such as opening the app or syncing your encrypted friend/block backup) is automatically deleted and tombstoned by our server on the same terms as a manual deletion — you do not need to take any action for this to happen.
The Service is 18+. We do not knowingly collect data from minors. Child sexual abuse material (CSAM), child sexual abuse or exploitation (CSAE), grooming, sextortion, or sexualization of minors is prohibited and may be reported to relevant authorities. See our Child Safety Standards.
Where applicable, we process data based on consent, providing the service you request, security/legal obligations, and legitimate uses such as abuse prevention and reliability. Under applicable law, including India's Digital Personal Data Protection Act, 2023 where it applies, you may request information, correction, erasure, grievance redressal, and withdrawal of consent for optional permissions.
Contact [email protected]. We aim to acknowledge grievances within 48 hours and resolve them within 30 days.
We may update this policy as the app changes. Material updates will be shown in-app or on this page. If you do not agree, stop using the Service and delete your account.