Privacy
Data partners
Parinay uses trusted service providers to run account access, hosting, communication, support, safety, and payments. Contact support@example.com or support@example.com with privacy questions.
| Category | Service provider | Typical role | Notes |
|---|---|---|---|
| Application hosting and managed backend | Supabase Active | Hosted Postgres, authentication, storage, and server-side APIs for the standalone app. account identifiers, profile data, photos, audit events | Counsel should publish the production project region and legal entity in the final privacy pack. |
| Transactional SMS and OTP delivery | MSG91 Conditional | Delivers one-time passcodes and other phone-based notifications when configured. phone number, OTP delivery metadata | India DLT registration and template approvals may be required before production use. |
| Transactional email delivery | Resend Conditional | Delivers transactional emails such as recovery acknowledgements and other account communications when configured. email address, message content, delivery metadata | Recovery request acknowledgement and support intake notifications use this vendor seam when configured. |
| Site delivery, CDN, and edge protection | Deployment host edge network Active | Serves the Next.js app, caches static assets, terminates requests, and provides edge protection. request metadata, IP address, asset delivery logs, cache diagnostics | This entry covers the deployment host's edge network, static caching, and DDoS-facing delivery layer. |
| Logs, metrics, and traces | Managed observability vendor Conditional | Receives structured application and service telemetry when managed observability is configured. request metadata, error payloads, service traces, diagnostic identifiers | Structured logs are already emitted in a vendor-neutral format so a managed provider can be attached later. |
| Maps, place autocomplete, and reverse geocoding | Managed maps vendor Conditional | Would resolve place suggestions, map picks, and reverse geocode current-device coordinates once a production maps provider is approved. typed place queries, approximate coordinates, map interaction metadata | The current standalone build uses an internal supported-place lookup first and keeps the managed vendor path optional until rollout. |
| Member communication infrastructure | Managed chat / RTC vendor Conditional | Can power member messaging, audio, and video rooms when the managed vendor configuration is enabled. member identifiers, message metadata, call session metadata | The standalone build now has provider seams and guarded room-join flow, but production chat or RTC traffic stays off until vendor credentials and policy review are complete. |
| Trust and safety automation | Managed moderation vendor Conditional | Can receive report, risk, and moderation queue cases when trust and safety automation is enabled. profile content, reported content, moderation outcomes | Parinay now has internal case creation plus optional vendor dispatch so managed moderation can be attached without reworking member-facing report flows. |
| Membership payments and billing | Managed payment gateway Conditional | Processes paid memberships, renewals, payment method tokenization, receipts, and dispute references when a production gateway is enabled. billing profile, masked payment method metadata, invoice totals, payment event identifiers | The standalone repo now keeps billing history, invoice snapshots, and entitlement enforcement in-app while leaving raw payment handling to a future managed gateway. |
| Sponsored placements and ad serving | Managed ad server Conditional | Can deliver sponsor creatives, line items, and campaign reporting once a production ad stack such as Google Ad Manager or an equivalent vendor is connected. placement metadata, campaign identifiers, impression and click events, limited audience segments when consent is on | The standalone build now has first-party sponsor slots, promoted-profile disclosures, and internal impression/click reporting so a managed ad server can be added later without redesigning member-facing surfaces. |