Amoura Privacy Policy

1. Introduction & Our Philosophy on Privacy

At Amoura Dating, we believe that creating meaningful dating connections requires mutual trust. Honesty and transparency are core to that trust. We have written this Privacy Policy in plain, accessible language so you can clearly understand how your personal information is handled when you use our website, web application, and matchmaking APIs.

Amoura is an adult dating and social connection platform designed to assist adult members in forming genuine personal and romantic connections. We do not operate as an escort service, sexual-services marketplace, or platform for commercial sexual encounters. We do not collect personal information arbitrarily, nor do we sell, rent, trade, or monetise your personal data with third-party advertisers or data brokers. Every piece of information we collect serves a direct operational purpose: helping you create a profile, discover compatible candidate matches, communicate safely, and protect our community from abuse.

2. Scope & Data Controller Information

This Privacy Policy applies to all registered members and visitors accessing Amoura Dating ("Amoura") through web browsers, desktop interfaces, mobile web clients, and associated application programming interfaces (APIs).

For the purposes of the UK General Data Protection Regulation (UK GDPR) and the Data Protection Act 2018 (DPA 2018), the statutory Data Controller is:

• Data Controller Entity: Amoura LTD
• Registered Address: London, United Kingdom
• Official Privacy Contact Email: privacy@reverse-proxy.co.uk
• Application Domain: www.reverse-proxy.co.uk

3. Information We Collect: Overview & Principles

To operate a matchmaking platform, we process three primary categories of personal data:

It goes without saying that we cannot help you develop meaningful connections without processing essential information about you, such as basic profile details and the types of people you would like to meet. We also collect usage data generated as you swipe and message, as well as verification data from social authentication providers like Google Sign-In when linked to an existing account.

1. Information Provided Directly by Users (e.g. registration details, profile attributes, photographs, direct messages, safety reports).
2. Information generated automatically when you use the Service (e.g. swipe interactions, match history, approximate distance calculations, technical IP metadata, session tokens).
3. Information received from authorized third parties (e.g. Google Sign-In identity verification for existing members).

4. Information Provided Directly by Users

When you create an account, complete your profile, or interact with other members, you directly supply personal data that enables us to establish your identity and render Discovery feeds.

5. Account & Registration Data Processing

During account setup, we collect essential authentication details:

Creating an account requires basic information necessary to verify your identity and protect against automated spam:

• Email Address: Used as your unique account key, for login verification, password resets, security notifications, and essential transactional messages.
• Password Security: We store passwords using industry-standard salted password hashing algorithms. Plaintext passwords are never logged or stored.
• Account Status & Onboarding State: We track your operational account status (`active`, `unverified`, `suspended`, `deleted`) and onboarding steps (`email_unverified`, `photos_required`, `profile_setup`, `active`).
• Verification Records: 6-digit email confirmation codes, magic link tokens, and verification timestamps.

6. Profile & Demographic Information Collected

To build your public dating card, you provide self-descriptive attributes:

Your public profile helps candidate matches get to know you before swiping:

• Basic Identity: Display name, date of birth (DOB), calculated age, gender (`man`, `woman`, etc.), and target gender preferences.
• Location & Residency: Primary city and country name for geographic candidate presentation.
• Biography & Prompts: Custom biography text and response prompts describing your background and lifestyle.
• Lifestyle Attributes: Job title, company or university, height in centimeters, relationship intentions (`long_term`, `short_term`, `friendship`), family plans (`wants_children`, `has_children`), interests list, languages spoken, star sign, and pet choices.

7. Photographs, Media Assets & Metadata

Visual presentation is vital for online dating. To complete your onboarding, you must upload a minimum of two authentic profile photographs (up to a maximum of 8 photos). In addition, when matched, users may exchange private photo and video media attachments within 1-on-1 direct message conversations:

Photographs and media assets are processed to render candidate Discovery cards and facilitate private communication:

• Image Files & WebP Processing: Uploaded profile images are downsampled, cropped, optimized, and saved as WebP binary files on our secure cloud storage infrastructure.
• Crop Parameters & Display Ordering: We record crop rectangle coordinates (normalized x, y, width, and height percentages), display sequence indices, primary photo badge indicators, and upload creation timestamps.
• Media Message Attachments: Photo files and video attachments (up to 15 MB) exchanged between mutual matches are stored in secure cloud storage and accessed via short-lived, time-limited secure URLs.

8. Direct Messages & Communication Records

When you achieve a mutual match with another user, private messaging is unlocked:

Direct chat messages and media attachments enable members to converse once mutual interest is established:

• Chat Message Content: Text message bodies and supported media attachments (photos and videos up to 15 MB) exchanged privately between matched profiles.
• Message Metadata: Sender user ID, receiver user ID, message creation timestamp, read status indicators, and thread identifiers.

9. Safety, Moderation, Blocking & Reports Data

To preserve platform safety and investigate policy violations, we collect moderation records:

Protecting community safety requires collecting investigation records when misconduct occurs:

• Block Records: Blocker user ID, blocked user ID, block creation timestamp.
• Safety Report Triage: Reporter ID, reported candidate ID, report category (harassment, fake profile, inappropriate photo, scam, commercial sexual solicitation/prostitution, underage concern, offline incident), descriptive text details, and investigation resolution state (`pending`, `investigating`, `resolved`).
• Moderation Case & Audit Logs: Internal safety notes, case priority ratings, assignment records, and audit logs of enforcement actions taken by authorized human moderators (warnings, photo removal, profile content resets, account suspensions, or terminations).

10. Automatically Collected Technical & Device Information

When you access Amoura, our application servers automatically log standard web metadata:

Our infrastructure logs technical connection data to render API endpoints securely:

• Network & Device Metadata: IP address, HTTP user-agent string, operating system version, browser family, and device classification.
• Security Identifiers: Cross-Site Request Forgery (CSRF) tokens, active session handles, and API rate-limiting activity counters.

11. Geographical Location & Distance Processing

To present local candidate matches, we process Geographical Location & Distance Processing details (latitude and longitude coordinates) associated with your profile city:

Matchmaking relies on proximity calculations to display nearby members:

• Distance Calculation: We execute Haversine spherical trigonometric formulas to calculate distance in miles or kilometers between candidates.
• No Continuous Tracking: We do NOT perform continuous real-time GPS tracking or record exact street addresses.

12. Discovery, Swiping & Match Activity Data

We log your interactive swiping activity to maintain your discovery queue state:

To generate candidate feeds and detect mutual matches, we process swiping actions:

• Swipes & Intentions: Target candidate ID, swipe direction (`pass`, `like`, `superlike`), and action timestamp.
• Rewind Counters: Consecutive rewind counters (capped at a maximum of 10 rewinds) and burst rate-limit trackers.
• Match Formations & Unmatches: Formed match records, mutual like detection timestamps, and unmatch execution events.

13. Session Data & Security Identifiers

We manage authenticated session state using secure session cookies (session identifiers), session creation timestamps, last activity times, security tokens, and client IP buckets stored in secure server-side caching storage.

14. Information Received from Third Parties: Overview

We limit third-party data collection strictly to essential authentication mechanisms, specifically optional Google Sign-In for existing members.

15. Google Sign-In & Single Sign-On (SSO) Disclosures

Amoura Dating ("Amoura") supports Google Sign-In & Single Sign-On (SSO) as an optional, secure authentication mechanism for registered members. In compliance with the Google API Services User Data Policy, including the Limited Use requirements, the following explicit disclosures describe how Google user data is accessed, used, stored, shared, protected, and deleted by our application:

15.1 Requested Google OAuth Scopes & Accessed Data

When you authenticate via Google Sign-In, Amoura requests access strictly to basic, non-sensitive Google OAuth 2.0 scopes:

• openid: Accessed to verify your unique account identity using the OpenID Connect standard.
• email: Accessed to retrieve your primary Google email address (`email`) and verification status (`email_verified`).
• profile: Accessed to retrieve your unique Google Subject ID (`sub`), display name, and avatar image URL.

We do NOT request, access, collect, or process sensitive Google user data, such as your Google Contacts, Google Drive files, Google Calendar events, Gmail message content, or continuous device location logs.

15.2 Specific Use of Google User Data

Google Account data obtained through Google Sign-In is processed strictly for the following limited operational purposes:

• Authentication & Account Linking: We match your verified Google email address against existing registered accounts in our secure database to authenticate your login session and link your unique Google Subject ID (`sub`) to your member profile.
• Session Security & Fraud Prevention: We verify Google signed ID tokens server-side to prevent identity spoofing, credential stuffing, and unauthorized account access.
• Service Notifications: We use your verified email address to deliver essential account security alerts and transactional notifications.

15.3 Strict Login-Only Policy

Google Sign-In is strictly an authentication shortcut for existing registered accounts. Google SSO CANNOT be used to create or auto-generate new member profiles. If an unregistered Google account attempts login, our application rejects the request with a clear user notification instructing the individual to complete our standard registration form first.

15.4 Server-Side Token Verification & Non-Storage of Passwords

When you authenticate with Google, our application receives a cryptographic OAuth ID token. Our backend verifies this token directly with Google's secure token verification service (https://oauth2.googleapis.com/tokeninfo). We do NOT receive, request, or store Google passwords, OAuth client secrets, or refresh tokens.

15.5 Google User Data Sharing, Disclosures & Third-Party Transfers

Amoura does NOT share, transfer, or disclose Google user data to third parties, except in the following strictly limited circumstances:

• Essential Infrastructure Processors: To encrypted cloud database hosting infrastructure necessary to store user profile records securely.
• Legal Obligations: Where mandated by valid statutory legal process, court orders, or enforceable governmental requests.

We do NOT transfer or disclose Google user data to third parties for targeted advertising, advertising networks, data brokers, information resellers, credit scoring, or AI/ML model training.

15.6 Security Controls for Google User Data

We implement robust technical and organizational security procedures to protect the confidentiality and integrity of Google user data:

• Encryption in Transit: All communications between your browser, our application servers, and Google OAuth endpoints are encrypted using Transport Layer Security (TLS 1.3 / SSL).
• Encryption at Rest: User database records and session identifiers are stored in secure server infrastructure with AES-256 encryption at rest.
• Strict Access Controls: Access to production database infrastructure is restricted to authorized systems with multi-factor authentication and role-based access controls.
• No Human Inspection: Employees and operators do NOT view, read, or inspect raw Google user data, except where explicitly required for fraud/security investigations or compliance with valid legal orders.

15.7 Google User Data Retention & Deletion Protocol

We retain Google user identifiers (`google_id` and linked email) strictly for the duration of your active account lifecycle:

• Retention Period: Google user account link records are retained as long as your Amoura account remains active.
• User-Initiated Deletion: You may request full deletion of your account and all associated Google user data at any time by navigating to Settings > Delete Account within the application, or by emailing our Privacy Team at privacy@reverse-proxy.co.uk.
• Data Purging Timeline: Upon receiving an account deletion request, your account record, profile data, and linked Google account identifiers are permanently deleted or anonymized within 30 days.

Google authentication processing is governed by Google's Privacy Policy (https://policies.google.com/privacy).

16. Customer Support & In-App Feedback Data

If you contact our support team at support@reverse-proxy.co.uk or submit safety feedback, we collect your email address, message body, attachments, and resolution notes to solve your request.

17. Lawful Bases for Processing Under UK GDPR

Under Article 6 and Article 9 of the UK GDPR, we process personal data strictly under valid statutory legal bases:

• Contractual Necessity (Art. 6(1)(b)): Necessary to register your profile, render Discovery decks, process swipes, establish matches, and deliver direct messages under our Terms.
• Explicit Consent (Art. 6(1)(a) & Art. 9(2)(a)): Applicable when you voluntarily disclose special category data (sexual orientation, relationship intentions, lifestyle attributes) or upload profile photos. You may withdraw consent at any time by editing or deleting profile fields.
• Legitimate Interests (Art. 6(1)(f)): Processing necessary to enforce rate limits, maintain system security, triage safety reports, prevent fraud/spam, and protect community safety.
• Legal Obligation (Art. 6(1)(c)): Compliance with statutory legal mandates, court orders, or retaining consent logs in `user_consents`.

18. Processing Purpose: Account Creation & Authentication

We process your email address, salted password hash, or Google ID token to authenticate your identity, generate CSRF security tokens, and maintain an active session.

19. Processing Purpose: Candidate Feeds & Discovery

We process your demographic choices, search preferences (min/max age, distance, target gender), and profile coordinates to filter and display candidate cards in Discovery feeds using Haversine distance formulas.

20. Processing Purpose: Matches & Real-Time Chat

We process swipe actions to detect mutual interest, create active match pairs, and transmit direct chat messages with real-time delivery status.

21. Processing Purpose: Safety, Moderation & Rate Limits

We enforce multi-layered safety and security controls to protect our community:

• Automated & Technology-Based Detection: Enforcing sliding-window rate limits (authentication attempts, swipe velocity, messaging frequency, rewind controls), media file format verification, and media size constraints (3 MB for profile photos, 15 MB for video messages) to identify potentially problematic activity, anomalous account behaviour, or automated spam.
• Safety Reports & Human Moderation: Where safety reports or system flags are generated, authorized human reviewers inspect reported profile information, photographs, media attachments, and report narratives within an internal moderation workspace to make proportionate enforcement decisions. Automated tools assist with triaging and prioritization, but user content is not universally pre-screened or manually previewed by a human prior to publication.
• Enforcement Action Records: Processing records to execute warnings, photo removals, profile text resets, account suspensions, or permanent terminations where policy breaches are identified.

22. Processing Purpose: Service Notifications & Emails

We use your email address to send essential transactional emails, including verification codes, password reset links, security alerts, and match notifications.

23. Processing Purpose: System Diagnostics & Uptime

We process web server logs, error traces, and system metrics stored in storage/logs/ to debug application errors, ensure server performance, and maintain uptime.

24. Processing Purpose: Legal Compliance & Audit Trails

We retain legal consent records in user consent database records and safety investigation records to demonstrate statutory compliance and defend against legal claims.

25. Public Profile Visibility & Shared Data

Your display name, age, city, bio, job, height, intentions, lifestyle tags, interests, languages, and profile photos are visible to candidates in Discovery. Your email address, exact location coordinates, verification credentials, and password hash are NEVER publicly visible.

26. Disclosures to Essential Service Processors

WE DO NOT SELL, RENT, OR TRADE YOUR PERSONAL DATA WITH ADVERTISERS OR DATA BROKERS.

We share personal information strictly with Disclosures to Essential Service Processors operating under binding Data Processing Agreements (DPAs):

27. How We Share Data: Cloud Infrastructure & Database Hosts

Our web application servers and database storage systems are hosted in secure, ISO-certified data centers located in the UK and European Economic Area (EEA).

28. How We Share Data: Caching Infrastructure & Session Storage

High-performance session state and rate-limiting counters are managed via secure caching systems protected by strict access controls.

29. How We Share Data: Transactional Email Relays

Verification emails, security codes, and password resets are dispatched through secure transactional email gateways and cloud relays.

30. How We Share Data: Disclosures to Law Enforcement

We may disclose user records to police, judicial, or regulatory authorities where required by statutory court order, subpoena, search warrant, or in emergency situations involving imminent physical danger, sexual exploitation, human trafficking, fraud, or child safety threats.

31. How We Share Data: Corporate Transactions & Restructuring

In the event of a merger, acquisition, or asset sale involving Amoura LTD, user data will be transferred as a business asset subject to identical privacy commitments.

32. Data Retention Framework

We maintain a comprehensive Data Retention Framework: We retain personal data only for as long as necessary to maintain your active account, deliver the Service, enforce safety moderation, and satisfy statutory record-keeping obligations.

If you stop using Amoura, you can delete your account via Account Settings. Following account closure, we delete your personal information as detailed in Section 33 below.

33. Account Deletion & Purging Protocol

When you delete your account via Account Settings, our Account Deletion & Purging Protocol executes: your records across account profiles, uploaded photos, interaction history, matches, and direct messages are immediately and permanently purged from our database systems, and your photo files are purged from storage.

34. Backup Systems & Residual Retention

Encrypted database backup snapshots are automatically rotated and purged on a rolling 30-day schedule.

35. Data Security & Encryption Standards

We enforce robust technical controls: strong salted password hashing, TLS transport encryption, prepared database statements against SQL injection, CSRF security tokens, and strict file permission controls.

36. User Rights Under UK & EU GDPR

Under UK GDPR, you possess statutory privacy rights: Right of Access (Subject Access Request), Right to Rectification, Right to Erasure ("Right to be Forgotten"), Right to Restrict Processing, Right to Data Portability, and Right to Object.

You can exercise these rights directly within account settings or by emailing our Privacy Team at privacy@reverse-proxy.co.uk.

37. California Privacy Rights (CCPA/CPRA)

California residents have California Privacy Rights (CCPA/CPRA) including the Right to Know, Delete, Correct, and Limit Use of Sensitive Personal Information. We do not sell or share personal information under California law.

38. Protection of Minors (Strict 18+)

Amoura enforces the Protection of Minors (Strict 18+) and is strictly restricted to adults aged 18 and older. We enforce date-of-birth age validation upon registration to prevent minors from accessing the Service. Any account identified as belonging to or operated on behalf of a minor under 18 years of age is immediately and permanently banned, and all associated personal data is permanently purged.

39. International Data Transfers & Safeguards

Primary servers are located in the UK/EEA. External transfers enforce International Data Transfer Agreements (IDTAs) or EU Standard Contractual Clauses (SCCs).

40. How to Exercise Privacy Rights & Contact Information

To exercise your privacy rights or submit a Subject Access Request, email our Data Protection Team at privacy@reverse-proxy.co.uk.

41. Supervisory Authority Complaints & DPO Contact Details

You have the right to lodge a complaint with the Information Commissioner's Office: Information Commissioner's Office (ICO), Wycliffe House, Water Lane, Wilmslow, Cheshire SK9 5AF. Website: https://ico.org.uk.

DPO Email: dpo@reverse-proxy.co.uk | Privacy Desk: privacy@reverse-proxy.co.uk