English privacy notice
1. Who is responsible
The Red Thread is operated by Emirati author Abdulla Ahmed Al Mansoori in the United Arab Emirates. For the optional website measurement described below, The Red Thread determines why and how page-view data is shared and therefore acts as the controller for that processing.
To exercise a privacy right or ask a privacy question, use the protected privacy-request form. It sends the minimum information needed directly to The Red Thread without publishing a personal email address or phone number.
2. What the site does without optional measurement
You may read all six bilingual literary works without allowing Meta measurement. The site uses a strictly necessary privacy-choice record so it can remember whether you accepted or rejected the optional category and which notice revision you saw. Rejecting optional measurement does not restrict the library, reader, language controls, or free access.
Privacy-request processing
The protected privacy-request form collects a request type, reply email, preferred language, acknowledgement, and any optional details you choose to provide. The Red Thread uses this information only to receive, verify where necessary, manage, and respond to the request. The email and optional details are encrypted in private storage outside the public website and are not sent to Meta or another external advertising service.
The request application does not store raw network addresses or user-agent strings. Hosting and security infrastructure may process temporary connection metadata under provider controls to deliver and protect the route. The form body and reply email are sent only in the protected request body and are not placed in the page URL.
Private request content is retained only while needed to manage the request. By 365 days, any request still pending or under review is flagged for an owner retention review; this is a configurable operational deadline, not a statutory period, and an unresolved request is not deleted automatically solely because of its age. On resolution or closure, the live reply email, optional details, and request-level matching values are erased immediately. Non-reversible anti-abuse rate-limit buckets derived from the reply address or request source may remain for up to two days, without the raw email address or network address. A minimal record without the request content—opaque reference, request type, language, acknowledgement version, timestamps, status, and action audit—is retained for up to 180 further days before purge. A one-way erasure record may then remain for up to 365 days to demonstrate deletion without restoring the private content.
Access-restricted private recovery copies containing encrypted request fields may retain an earlier copy of request content for up to 30 days solely for disaster recovery. They expire automatically and are not used for analytics or marketing. Although the live reply email and optional details are erased immediately when a request is resolved or closed, a recovery copy created before that transition may persist until its 30-day expiry. Any data restored from a recovery copy must immediately re-enter the same retention and erasure process.
3. Optional Meta Pixel measurement
If you actively allow measurement, the site may use Meta Pixel to send one PageView event for the current document. The purpose is to measure entry into the literary house, attribute eligible visits, understand aggregate audience response, and improve relevant promotion. The books remain free; this release does not measure reading progress, purchases, checkout, payment, shipping, or sales.
| Data or event | Purpose | Boundary |
|---|---|---|
| PageView with page type and language | Measure entry into the literary house and the language context of the current page | One event per document after consent; no reading-progress event is authorised |
| Current page context | Attribution and aggregate audience measurement | May include the current URL or path, page title, and origin-level referring context where supplied. Measurement remains disabled when the current URL or referring URL contains an unapproved or potentially personal query value or fragment. |
| Browser/device identifiers | Event matching, attribution, and aggregate measurement | May include IP address, user agent, Meta browser ID (`_fbp`), and eligible Meta click ID (`_fbc`) |
4. What is never authorised for Meta measurement
The integration is not authorised to send reader reflections, enquiry text, names, email addresses, phone numbers, payment data, government identifiers, or information that reveals or infers health, financial circumstances, religion, political or philosophical opinion, psychological condition, sexual life, family circumstances, or a legal dispute. Personal data must not be placed in tracking URLs or event names.
5. Recipients and processing locations
Meta
Meta receives the optional PageView event for matching, measurement, attribution, audience creation, advertising optimisation, and uses described in its applicable terms. Processing may occur outside the UAE under Meta’s applicable data-processing and transfer terms.
6. Consent and control
Optional Meta measurement is off until you select “Allow measurement.” You may choose “Continue without measurement,” configure the category, or withdraw later through the persistent Privacy choices control. Withdrawal stops future optional transmission; a page reload may be used to remove an already loaded measurement script and clear accessible first-party Meta identifiers.
If you are under 13, do not allow optional Meta measurement. If local law requires parental or guardian authorisation, continue without measurement unless that authorisation has been obtained.
7. Retention
The first-party privacy-choice record contains a consent identifier, choice and change timestamps, accepted categories and services, interface language, notice revision, and expiry. It is configured for 90 days after rejection and 180 days after acceptance, subject to revision or deletion through your browser. Meta retains information under its applicable terms, privacy policy, and account controls. The Red Thread will not keep information longer than necessary for the stated purpose and applicable obligations.
8. Your rights
Subject to applicable law, you may request access, correction, deletion, restriction or cessation of processing, withdrawal of consent, portability, and information about recipients and cross-border processing. Identity may be verified before a request is fulfilled. Withdrawal does not invalidate processing that occurred lawfully before withdrawal.
Submit a protected privacy request. Please do not include identity documents or sensitive information in the form. If verification is necessary, it will be requested separately.
9. Security and accountability
The Red Thread applies data minimisation, a single standard event name, restricted parameters, encrypted transport, and pre-production testing. Optional measurement is refused when the current URL or referring URL contains an unapproved or potentially personal query value or fragment, and must remain disabled if the consent manager, dataset identity, or public privacy notice is not healthy.
10. Changes
Material changes to the optional measurement purpose, recipients, data types, or notice will increase the consent revision and prompt you to choose again.