Privacy foundation

FunnLov should collect only data needed to operate accounts, matching, safety, payments and verified-host services. Administrators may access account/profile/activity information for operations and moderation, subject to role controls.

What the product can retain

• Account identifiers, email/phone if supplied, signup and last-sign-in timestamps.
• Profile fields such as display name, age/date of birth, gender, country, language, interests, bio and profile photo.
• Wallet, purchase, host, payout, call-session and moderation metadata required to operate the service.
• Consent timestamps and safety/report records.

What is intentionally not available to administrators

• Readable passwords or authentication secrets.
• Private call video/audio recordings by default.
• Biometric face templates or facial-recognition profiles by default.
• Peer-to-peer live captions after the call ends.

Before public launch

• Publish a lawyer-reviewed privacy notice and terms with specific purposes and retention periods.
• Offer account deletion and data export.
• Maintain processor DPAs and an EU/EEA data-transfer review.
• Create a breach-response process and data-subject request workflow.
• Complete a DPIA before introducing biometric identification, call recording or other high-risk monitoring.