Draft status
This Privacy Policy is not legal advice and is not ready to publish as an app-store policy. It must be reconciled with the actual submitted build, SDKs, backend vendors, launch geography, controlled-beta age/access flow, moderation process, deletion process, and store data-safety disclosures.
1. What the app is
meltup is an adults-only, personality-first dating app. Users may present with a pseudonymous handle and profile signal, but accounts remain accountable to the platform for safety, moderation, fraud prevention, and eligibility enforcement.
2. Information we expect to collect
| Category | Examples | Purpose |
|---|---|---|
| Account information | Email, auth provider identifiers, internal user IDs | Authentication, account management, fraud prevention, support |
| Profile and signal content | Handle, prompts, interests, personality signal, preferences | Profile creation, discovery, compatibility, safety review |
| Interaction data | Pulse actions, matches, chat metadata, reveal requests, blocks | Core app functionality, abuse prevention, product reliability |
| User content | Messages, reports, optional reveal media if enabled | Messaging, consent-based reveal, moderation, evidence review |
| Verification status | 18+ self-attestation for the controlled beta, provider status after beta, timestamp, eligibility metadata | Eligibility and safety gating. A verification provider is expected after beta; raw verification artifacts should not be stored unless a vendor flow requires it. |
| Diagnostics and operations | Crash logs, error events, limited analytics if configured | Reliability, safety, abuse prevention, beta support |
3. How information is used
- Provide authentication, access gating, discovery, matching, chat, reveal, report, block, support, and deletion features.
- Protect users and the service from harassment, scams, impersonation, exploitation, spam, and other abuse.
- Review reports and preserve safety evidence when needed, even if ordinary chats are time-limited.
- Maintain security, debug issues, improve beta reliability, and satisfy store-review obligations.
4. Sharing and vendors
The expected beta vendor stack includes Supabase for authentication/database, Cloudflare for Workers, Pages, and storage, Expo/EAS for builds, and a manual-review moderation process. Crash/error, analytics, push, payment, and post-beta verification vendors remain TBD and must be added before publication if used.
5. Retention
Ordinary chat is intended to be time-limited. Reported content, moderation records, security logs, support records, audit events, and deletion records may be kept longer when needed for safety, abuse prevention, legal compliance, or dispute handling. Exact windows must be approved before publication.
6. Account deletion
Users must be able to request deletion in the app and through an external deletion route. Deletion should hide the profile, stop discovery/match/chat/reveal access, revoke sessions where supported, and remove or redact eligible data. Limited safety, audit, support, and backup records may remain for approved retention windows.
7. User choices
- Edit profile and signal content where the app supports it.
- Block or report another user.
- Decline or avoid reveal.
- Request account deletion.
- Contact support or abuse inboxes once final contacts are published.
8. Contact
Final public support, abuse, privacy, deletion, child-safety, and legal contact details are TBD. Do not use this page for store submission until real monitored contacts are approved for publication.