Privacy policy

1. Data we collect

• Account data: email address, display name, role, authentication records, signup path, initial creator link and campaign tags when present, and settings.
• Creator data: profile, social links, pricing, availability, approval status and Stripe connected-account status.
• Service data: requests, messages, ratings, reports, blocks, subscription status and notification preferences.
• Private media: voice notes, photos and VIP media stored in private storage and served through expiring signed links.
• Payment data: amounts, currency, status and Stripe object references. ReplyPass does not store full card or bank credentials.
• Technical and security data: IP-derived security signals, device/browser data, timestamps, logs, consent choices and rate-limit records.
• Measurement data described below, including cookieless Google page-view pings and optional consent-based analytics and advertising data.

2. Why we use it

• Contract: create accounts, route requests, provide messaging and media access, administer VIP, process payments and send service notices.
• Legitimate interests: secure the service, prevent abuse and fraud, support users, reconcile payments, improve reliability and enforce rules.
• Legal obligations: accounting, tax, identity/payment compliance, disputes, lawful requests and record preservation.
• Consent: analytics cookies, additional Google Analytics events, and optional Meta and X advertising/conversion measurement. Consent can be withdrawn through Cookie preferences.

3. Analytics, advertising and cookies

Essential storage keeps authentication, security and requested features working. Google Tag Manager manages the Google Analytics, Meta and X browser tags while preserving the separate consent choices described below. Google Analytics loads with Consent Mode v2 defaults denying analytics and advertising storage and sends cookieless page-view pings even when the banner is ignored or rejected. These pings can include technical signals such as browser information, referrer and timestamps; they are not unique visitor counts. Analytics cookies and additional analytics events require analytics consent. Meta and X Pixels and their consent-aware Conversions API measurement remain off until their respective advertising consent. The banner is shown to new visitors and offers separate choices. Each advertiser has a separate choice that can be rejected and is remembered in that browser for up to 180 days.

ReplyPass keeps daily aggregate counts of loaded creator-landing pages and successful creator-profile link copies. Landing counts store aggregate source and campaign tags from the URL, but not visitor identities, cookies, full URLs or click IDs; short-lived IP-derived security limits help protect the count from abuse. Campaign tags are kept in this browser tab for up to 24 hours so a completed signup can record its entry campaign. Link-copy counts are associated with the creator account, separated between the creator dashboard and public profile, without retaining the visitor identity or copied URL. These counts are not unique people. Measurement excludes message text, media, creator handles, internal payment references and arbitrary form contents. With Meta advertising consent, Meta may receive approved event data, page URL, campaign parameters, browser identifiers and a one-way hashed email for matching. With X advertising consent, X may receive page URL and campaign parameters through its Pixel, and a hashed email plus a pseudonymous conversion identifier when a creator completes registration. Google receives sanitized page groups and limited campaign tags (source, medium and campaign) in cookieless page-view pings; with analytics consent it can also use analytics cookies and receive approved funnel events. Arbitrary URL parameters and creator handles are omitted. Google, Meta and X act under their own privacy terms for data they receive.

4. Who receives data

• Supabase for authentication, database and private storage.
• Stripe for payments, fraud controls, subscriptions, identity/KYC and creator payouts.
• Vercel for hosting and delivery.
• Resend for transactional email.
• Upstash for shared rate limiting.
• Google Analytics for cookieless page-view pings, and for cookie-based analytics after consent; Meta and X only under their respective advertising consent.
• An error-monitoring provider after configuration, limited to sanitized operational metadata.
• Professional advisers, authorities or counterparties when lawfully required.

5. International transfers

Providers may process data outside your country. Where required, ReplyPass relies on an adequacy decision, approved contractual safeguards, or another lawful transfer mechanism. Provider locations and safeguards must be checked when contracts are finalized.

6. Retention

We keep account and service data while the account is active and for a limited period afterward. Private request media is retained only as long as needed to provide the purchase, handle disputes and meet safety or legal needs. Financial, tax, refund and dispute records may be retained for the legally required period. Security logs are kept for a shorter risk-based period. Consent records are retained to demonstrate the choice made.

A final retention schedule with exact periods will be approved before commercial launch. Data may be preserved longer for an active dispute, safety report or legal hold.

7. Your rights

Depending on applicable law, you may request access, correction, deletion, restriction, portability, or objection; withdraw consent without affecting earlier lawful processing; and complain to the CNIL or your local supervisory authority. We may need to verify identity and may retain data where a legal exception applies.

• Manage optional tracking through Cookie preferences.
• Manage account settings and request deletion from the account area.
• Send privacy requests to info@getreplypass.com.

8. Security and children

ReplyPass uses access controls, private storage, expiring media links, encrypted transport, webhook verification, rate limits and restricted administrative access. No system is completely secure; report suspected compromise promptly.

ReplyPass is for adults aged 18 or older. We do not knowingly offer accounts to children. Contact us if you believe a child supplied personal data.

9. Controller details and changes

The service is operated from France under the ReplyPass name. The operator’s registered legal name, postal address, registration number and, where applicable, VAT number and data-protection representative must be inserted before commercial launch.

We will publish material policy changes and give additional notice where required.