Privacy Policy

Ropely ("we", "us") respects your privacy. This policy explains what we collect, why, and your choices.

1. Roles

Creators use the dashboard to manage communities. Members purchase passes and receive access. We process data on behalf of creators to operate the service.

2. Data we collect

• Account data: email address, display name, session tokens (magic-link auth for creators and members).
• Payment metadata: amounts, currency, provider references, pass status — not full card numbers (handled by Stripe, Paystack, etc.).
• Platform identifiers: Telegram user IDs, Discord IDs, WhatsApp handles — to grant and revoke access.
• Usage & logs: API requests, webhook delivery, error reports (e.g. Sentry), optional analytics (PostHog) if enabled.
• Creator secrets: API keys and WAHA tokens encrypted at rest when ENCRYPTION_KEY is configured.

3. What we do not do

• We do not custody creator or member funds.
• We do not sell personal data to advertisers.
• We do not read private Telegram/WhatsApp message content except automated moderation rules you configure.

4. How we use data

• Authenticate users and send transactional email (magic links, receipts, dunning).
• Process checkouts, activate passes, and automate access lifecycle.
• Prevent fraud, enforce sanctions screening, and secure the Platform.
• Improve reliability and support creators.

5. Processors & subprocessors

We use infrastructure and service providers (hosting, email, databases, payment processors, messaging APIs). Creators choose which payment rails and WhatsApp (WAHA) nodes to connect. Those providers have their own privacy policies.

6. Retention

We retain account and pass records while your account is active and as needed for legal, tax, and fraud prevention obligations. You may request deletion by contacting support; some records may be retained where required by law.

7. Your rights

Depending on your jurisdiction you may request access, correction, or deletion of personal data. Contact support@ropely.io. Members should also contact their community creator for pass-specific requests.

8. Security

We use encryption in transit (TLS), encrypted storage for sensitive creator credentials, and access controls on production systems. Report vulnerabilities to support@ropely.io — see our bug bounty policy.

9. International transfers

Data may be processed in countries where our infrastructure providers operate. We use appropriate safeguards for cross-border transfers where required.

10. Contact

Privacy questions: support@ropely.io