Legal review required — not legal advice. This document is not final, legally reviewed or confirmation of UK GDPR compliance. Items marked "REQUIRED BEFORE PUBLICATION" must be resolved by the operator, and the whole text reviewed, before public publication. The preparation date is not publication approval.

Privacy notice

Prepared 10 November 2026 — review required · Version 5

This notice describes the current early-interest waitlist only. It does not cover future marriage profiles, matchmaking or Wali Support. Those services will require a separate assessment and updated information before they become available.

Who we are

RevertsMatrimony is a UK-first marriage platform in development, welcoming all adult Muslims serious about marriage, whether born Muslim or reverts/converts. The voluntary waitlist is open to adults aged 18 or over; marriage introductions, AI guidance and Wali Support are not live.

Operator: AMT Vision trading as RevertsMatrimony.com, a sole trader. This designation does not identify a limited company or establish the individual's personal legal name. The individual sole trader is the legal data controller: [REQUIRED BEFORE PUBLICATION: supply the owner's full personal legal name for controller disclosure]. Address supplied by the owner: Maitland House, 1 Warrior Square, SS1 2JN, United Kingdom.

The operator states that it is exempt from the ICO data protection fee. This concerns the fee only and does not exempt the operator from UK GDPR obligations. No exemption certificate or rationale is asserted here. [REQUIRED BEFORE PUBLICATION: document the supporting ICO fee-exemption assessment].

Contact for any privacy question or request: info@revertsmatrimony.com.

What we collect and where it comes from

Your email address, provided by you, is required so we can maintain the waitlist and contact you about early access and launch when those notices begin.
Your self-declaration that you are 18 or over, provided by you, is required. It is not full age verification. Without an email and this declaration we cannot accept a registration.
Your UK region or "Outside UK", provided by you, is optional. Leaving it blank does not prevent registration.
We record whether you chose the separate, optional promotional-updates checkbox. It is unticked by default; declining marketing does not prevent registration or requested launch updates.
The system generates a record identifier, signup date and time, a source label identifying the prelaunch landing page, and the privacy-notice version associated with the registration. Email addresses are trimmed and normalised to lowercase for duplicate handling.
Abuse protection: the server processes your connection (IP) address to generate a hashed connection key and records an attempt identifier and time to limit repeated submissions. The waitlist tables do not store your raw IP address. A hashed key is not treated as proof that data is anonymous. Hosting or delivery services may process connection information separately; their logging and retention arrangements require confirmation.
Anti-bot checks also process a hidden form field and, when supplied, the form-start time. These are checked before a signup is stored and are not fields in the signup record.

We do not ask for your name, phone number, explicit religious affiliation, gender, marital history or whether you have a wali at this stage. Information comes from your submission and technical information generated while processing it, not from a purchased contact list.

Possible sensitive inferences

The site does not ask for religion or infer religious beliefs for profiling. However, joining a Muslim marriage platform may reveal religious faith through context. Whether this constitutes special-category processing under UK GDPR requires a fact-specific legal assessment; having no religious field or separate religious-consent checkbox does not settle that question. [REQUIRED BEFORE PUBLICATION: complete the Article 9 legal assessment before launch and document an applicable condition if required, including associated UK law requirements]. No Article 9 condition has been established, and this notice does not assert that explicit consent is either necessary or unnecessary.

Purposes and lawful bases — assessment pending

Maintain your requested waitlist registration and send early-access or launch updates when available. [REQUIRED BEFORE PUBLICATION: validate and document the Article 6 lawful basis for requested waitlist registration and launch/early-access communications].
Send broader promotional updates only if you select the separate marketing option. That choice is intended as consent and can be withdrawn; [REQUIRED BEFORE PUBLICATION: verify the consent wording, records, withdrawal process and applicable UK GDPR/PECR requirements before marketing starts].
Use optional region information in aggregate to plan a UK-first rollout. [REQUIRED BEFORE PUBLICATION: validate and document the Article 6 lawful basis for regional launch planning].
Protect the waitlist from fraud, spam and repeated submissions using validation and anti-bot checks. [REQUIRED BEFORE PUBLICATION: validate and document the Article 6 lawful basis for abuse prevention].
Send separate internal copies of a genuinely new signup to the business inbox and an operator-controlled account with a third-party mail service, through third-party email delivery. [REQUIRED BEFORE PUBLICATION: validate and document the Article 6 lawful basis and necessity of internal signup notifications].

Overall lawful-basis assessment: [REQUIRED BEFORE PUBLICATION: validated Article 6 assessment for each purpose]. If legitimate interests is proposed for any purpose, [REQUIRED BEFORE PUBLICATION: complete a legitimate interests assessment (LIA) and explain the specific interests, necessity, balancing and right to object]. This notice does not select legitimate interests or any other basis on the operator's behalf.

No launch or promotional emails are being sent yet, and no automatic confirmation email is sent to you when you join. The current signup process attempts separate internal notifications to both operator-controlled inboxes only after a new signup is stored; duplicate registrations do not trigger them. Failure or suppression of one copy does not prevent the other attempt or undo a saved signup. Delivery and inbox ownership have not been independently verified. Each copy contains only your email, optional region, marketing choice and signup time, used to reconcile the notification with the registration; it does not include the age declaration, source label or religious profiling.

Access, recipients and processors

Signup and abuse-prevention records are held using hosting and database services. Internal signup notifications pass through third-party email delivery to operator-controlled email inboxes: a business inbox and, separately, an account with a third-party mail service. Their mailbox providers process those copies. The public website does not provide a signup list; its public database access cannot read or write the waitlist tables. The operator and people authorised to manage the service can have access through administrative systems or the internal notification inboxes.

We do not sell waitlist data. [REQUIRED BEFORE PUBLICATION: confirm hosting/database, email-delivery and recipient-mailbox providers, contractual processor roles, subprocessors and authorised recipient/access arrangements]. The exact provider entities, service contracts and data regions have not been confirmed in this notice; no UK-only hosting or other unverified security assurance is made.

The current site's conversion code places limited interaction events, including whether a region or marketing option was selected, in the page's in-memory event list; it does not pass your email or load an external analytics or advertising tracker. Provider-level operational logging and any other processing outside that code remain subject to verification.

International transfers — confirmation required

[REQUIRED BEFORE PUBLICATION: confirm storage and processing locations, remote access and transfers outside the UK for every hosting, database, delivery and mailbox provider; identify applicable adequacy decisions or other safeguards and how to obtain a copy]. We cannot yet state that information stays in the UK or that a particular transfer safeguard is in place. Ask info@revertsmatrimony.com for details; the operator must complete this disclosure before publication.

Retention policy — automation pending

Owner-confirmed policy: Retain waitlist records until 12 months after the platform launches, subject to an earlier valid deletion request. You can request deletion at info@revertsmatrimony.com. Platform launch date: not set. No launch date has been invented or used to delete records.

Retention automation is pending. The current system does not automatically enforce the post-launch deadline; deletion becomes automatic only after a verified scheduled purge is implemented and the actual launch date is set. Earlier valid deletion requests require an operator-managed process. [REQUIRED BEFORE PUBLICATION: implement and verify scheduled post-launch deletion and the manual deletion-request process, including notification copies and backups].

If launch does not occur, the operator will periodically review whether retaining the waitlist remains necessary and record a decision to continue for a justified, time-limited period or delete it. This is not a promise of indefinite retention. [REQUIRED BEFORE PUBLICATION: set the prelaunch review interval, responsible person and decision deadline, and institute the reviews].

Abuse-protection cleanup is opportunistic: when a new submission passes the initial validation and anti-bot checks, the server attempts to remove records older than 24 hours. It is not a scheduled 24-hour deletion guarantee. Records may remain longer if no eligible submission occurs or cleanup fails.

[REQUIRED BEFORE PUBLICATION: confirm retention and deletion for internal notification emails, consent evidence, provider logs and backups, including how deletion requests reach those copies]. The rate-limit threshold does not define the retention of signup or email records.

Your rights

Depending on the processing and applicable legal conditions, you can request access, correction, deletion, restriction and data portability. You can object to processing based on legitimate interests if that basis is adopted, and object to direct marketing at any time. You can withdraw any consent you have given without affecting the lawfulness of processing before withdrawal. Declining or withdrawing broader marketing does not itself cancel requested launch notices; you can separately ask to leave the waitlist and stop those notices.

For any of these requests, contact info@revertsmatrimony.com, preferably from your registered email so we can match the record. We may need proportionate information to verify your identity. We will respond without undue delay and normally within one month; where the law permits an extension we will explain it. [REQUIRED BEFORE PUBLICATION: confirm the rights-handling process and responsibility, including email copies and any lawful retention exceptions].

You can complain to the Information Commissioner's Office (ICO) at ico.org.uk.

Automated checks, not marriage decisions

The waitlist uses automated validation, hidden-field and timing checks, and connection-based limits that may reject a submission or ask you to retry. It does not create marriage profiles, rank matches or make automated marriage-related decisions. If a check prevents registration, contact info@revertsmatrimony.com. This statement describes the waitlist, not an unverified claim about every provider's processing.

Review status and notice changes

This is version 5. New signup records identify the current notice; existing records keep the notice version recorded when they joined, and duplicate requests do not overwrite it. The preparation date does not mean existing members saw this version or that it is legally approved.

[REQUIRED BEFORE PUBLICATION: complete legal review, confirm the final notice date and version, and decide how existing waitlist members will receive material changes]. Final notice date: [REQUIRED BEFORE PUBLICATION: date after review]. This notice must be completed before publication and reassessed before additional services or processing begin.