CouplesConnect Privacy Policy
Effective date: 1 November 2026.
1. Who operates CouplesConnect
CouplesConnect is operated by Pankaj Gupta ("CouplesConnect," "we," "us," or "our"). Our contact for privacy questions and requests is support@couplesconnect.site. Postal/legal address: H.No.477, New Sarai, Near Sain Chowk, Narnaul, Haryana, 123001. Grievance contact: Preeti Agrawal, agrawalpreeti1998@gmail.com.
CouplesConnect is a social service for adult couples to discover and arrange platonic small-group Plans. It is not a dating or matchmaking service. One account represents one couple.
2. Who may use the service
The service is intended for people aged 18 or older. Both partners represented by an account must be adults. Age bands are self-selected and are not identity or age verification. The service is not directed to children, and we do not knowingly invite minors to create accounts. Contact us if you believe a minor has provided personal data so we can assess and take appropriate action.
3. Information we process
Depending on how you use CouplesConnect, we process:
- Account and sign-in: email address, authentication and session records, and security events needed to authenticate you. Ordinary account sign-in uses a six-digit email code. A dedicated account for store review is also configured to sign in using a password. Never send a sign-in code, password, or access token to support.
- Couple profile: partner names, a shared self-selected age band, city, interests and optional introduction. The current app does not ask for dates of birth, separate partner ages, or profile photos, and has no public couple directory. Your login email is not shown as part of the contextual couple profile.
- Plans and participation: Plan title, activity, date/time, city/locality, capacity and notes; requests to join, introductions, approvals, cancellations, participation history and related chat text and timestamps. Eligible Plans and relevant profile information are shown to other users in discovery or shared Plan/participation contexts according to the feature used.
- Safety and moderation: reports, reasons, relevant Plan or message snapshots, blocks, moderation decisions and limited attendance/no-show claims. These claims are user statements and are not independently verified attendance, ratings, background checks or GPS evidence.
- Notifications and device data: in-app notification records, notification preference and, if you enable push, a device push token and delivery-status information. Push messages are generic and are not intended to include chat bodies or private profile details. A push may remain on a recipient's device after delivery.
- Service and diagnostic data: app/build information, technical error and stack metadata, monitoring check-in identifiers/status and service-operation data. We use aggregate daily product counts such as onboarding, Plan creation/completion, participation and chat opening. The aggregate table does not contain account identifiers, message text or profile descriptions.
We do not use precise GPS tracking, collect dates of birth, or offer in-app payments/ticketing in the current release. These statements describe the current product and must be updated before any such feature is introduced.
4. How we use information
We use the information above to authenticate accounts; operate profiles, discovery, Plans, participation and Plan chat; send requested account and Plan notifications; maintain reliability and security; investigate user reports; enforce our community rules; process deactivation and deletion; respond to privacy and support requests; and understand aggregate product usage. We will review any materially new purpose and update this policy and any required user choices before using information for it.
5. When information is shared
We share information only as needed to operate the service and the features you use:
- With other users: relevant couple-profile and Plan information, introductions, participation and Plan chat are available in the contexts described above. Do not put sensitive information in a profile, Plan or chat.
- With service providers: Supabase provides authentication, database, realtime and backend processing; Resend delivers authentication email; Expo/EAS supports app build/delivery and Expo push routing; Firebase Cloud Messaging delivers Android push; Cloudflare hosts the website and protected admin portal; Vercel is retained for fallback hosting; Sentry receives limited error and backend availability telemetry. Providers process data under their own terms and infrastructure. They may process technical connection and operational data.
- For safety, legal process or a business transfer: we may disclose limited information when reasonably necessary to address abuse or security, comply with a legally valid request, protect users or rights, or support a transfer/reorganization of the service. The scope and applicable law must be assessed for each request.
We do not sell account profile or chat data. No advertising use is part of the current product.
6. Processing and storage locations
Current account configuration and provider disclosures indicate: the Supabase database project is configured in Singapore; Cloudflare serves the website and admin portal through its global network; retained Vercel functions are configured in the United States; Resend sends authentication mail through Tokyo and publishes US storage for email data; Sentry storage is in the United States; and Expo/Google services may process push data in their infrastructure. A configured function or sending region does not establish that every network, log, backup or provider operation is confined to that region. We do not promise India-only processing or storage.
7. Retention
We keep information for as long as needed for the purposes above, then delete or de-identify it according to the relevant application schedule, subject to applicable law, security needs and specific legal holds.
When an account is deleted, ordinary profile data and authored content are promptly removed or anonymized as appropriate. Account authentication removal is performed by a secure background process and may not be instantaneous. Minimal shared Plan/participation history may remain without the deleted account's profile identifiers. Necessary private report, abuse, security and audit evidence may remain identifiable for up to 180 days after deletion and is then deleted or irreversibly anonymized through retention processing, unless a specific record is subject to a legal requirement or documented record-specific hold. A hold does not pause ordinary account deletion or create an indefinite account-wide exception.
Service providers have separate logs, backup and delivery retention. Resend publishes a standard 30-day retention period for email and logs on the applicable plan, with separate provider backup and account-termination periods. This is not a guarantee that every provider record is erased 30 days after account deletion. Expo push messages may remain queued while needed for delivery; when no message TTL is provided, Expo documents a default delivery lifetime of up to four weeks for undelivered notifications. Firebase may retain installation identifiers until deletion through its API and remove live/backup copies on a separate schedule. Removing an app-side token does not by itself establish deletion of a provider-side identifier. A message already delivered cannot be removed from another person's device by deleting your account. Provider terms and retention practices can change; we will update this disclosure when our verified arrangements change.
8. Your controls and requests
You can edit supported profile details, manage saved Plans and push preferences, report or block, deactivate your account temporarily, or request permanent deletion through the in-app controls. A web account-deletion request is available at couplesconnect.site/account-deletion. Deactivation is temporary and does not erase data. Reactivation does not restore cancelled Plans, withdrawn participation or ended chat access.
For privacy questions or access/correction/deletion requests, email support@couplesconnect.site. We may verify that you control the relevant account before acting. One account represents a couple; control of its shared login does not automatically authorize disclosure of the other partner's private reports, third-party content or reporter identity. We will scope requests to protect others' information. Do not email passwords, OTPs or access/refresh tokens. We will explain if information must be retained for a specific lawful reason.
For a grievance, contact Preeti Agrawal at agrawalpreeti1998@gmail.com. You may also contact support@couplesconnect.site for privacy, account or service requests.
9. Security
We use access controls, server-side authorization and database row-level security to limit access according to account ownership, Plan context and moderation permissions. Mobile JavaScript error reporting is configured to remove ordinary personal application content and retain generic error, stack and release/build metadata. Backend availability check-ins send a monitor/check-in identifier, status and environment without account identifiers, emails, chat content, queue contents or issue details. Native crash behavior and all provider-side technical data are not covered by that JavaScript configuration. No online service can guarantee absolute security.
10. Changes
We will publish the current version here and update the effective date when we make a material change. Where required, we will provide additional notice or choice before the change takes effect. The policy in force for your use is the version linked from the app and website.
11. Contact
Privacy, deletion, correction or safety request: support@couplesconnect.site
Postal/legal address: H.No.477, New Sarai, Near Sain Chowk, Narnaul, Haryana, 123001. Grievance contact: Preeti Agrawal, agrawalpreeti1998@gmail.com.