Updated June 9, 2026
Privacy Policy (Français)
How Hoorly plans to collect, use, protect, retain, and disclose personal data for a gay dating and chat service.1. Data we process
Depending on the features you use, Hoorly may process account data, profile data, photos, messages, device data, approximate or precise location choices, safety reports, subscription records, support messages, and consent records.
Because Hoorly is a gay dating service, some profile choices or user interactions may reveal sensitive information such as sexual orientation. Sensitive profile fields should be optional and controlled by explicit consent.
2. Why we process data
We process data to create and secure accounts, show profiles, enable discovery and chat, review reports, moderate public content, provide support, process purchases, prevent abuse, comply with law, and improve the product.
We should not use sensitive profile data for unrelated advertising or third-party data enrichment without a clear legal basis and user-facing disclosure.
3. Legal bases
Core account, profile, discovery, and messaging features are generally processed to provide the service you request.
Safety, fraud prevention, abuse reporting, and moderation may rely on legitimate interests and legal obligations. Marketing, optional analytics, precise location, and sensitive optional profile fields should rely on consent where required.
4. Sensitive data and explicit consent
Optional fields that may reveal sexual orientation, sexual life, health, STI/HIV status, or similar sensitive information should require explicit consent and should be disabled or hidden by default where appropriate.
Users should be able to withdraw consent without losing access to the basic service, although withdrawing consent may disable the feature that depends on that data.
5. Location and visibility
Precise location should be off by default and used only when you choose nearby discovery features. Hoorly should provide settings to control distance display and profile visibility.
Where possible, Hoorly should minimize long-term storage of raw precise location data.
6. Service providers
Hoorly may use infrastructure, hosting, storage, CDN, security, analytics, support, email, push, and payment providers. Current expected providers may include Vercel, Cloudflare, Supabase, Apple App Store, and Google Play.
A public subprocessor list should describe each provider, purpose, region, and transfer safeguard before launch.
7. International transfers
Hoorly should prefer EEA-region processing where practical. If personal data is transferred outside the EEA, the transfer should rely on an adequacy decision, Standard Contractual Clauses, or another lawful safeguard.
Where required, Hoorly should document transfer impact assessments and use additional measures such as encryption, access controls, log minimization, and regional storage choices.
8. Retention
Hoorly should retain personal data only for as long as needed for the relevant purpose. Account content should generally be deleted or anonymized after account deletion, except for backups, safety records, legal holds, billing records, and abuse-prevention needs.
Suggested retention defaults include short-lived security logs, limited report retention, consent proof records, encrypted rolling backups, and legally required billing retention.
9. Security
Hoorly should use risk-appropriate technical and organizational measures, including access controls, encryption in transit, limited admin access, audit logs, backup protection, incident response, and regular security review.
No online service can be perfectly secure, but Hoorly should design privacy and safety into default settings.
10. Your rights
Depending on your location, you may have rights to access, correct, delete, restrict, object to processing, withdraw consent, export data, and complain to a supervisory authority.
Hoorly should provide self-service privacy controls in the app plus a support fallback for verified requests.