This notice explains what personal data Forlais Group Ltd collects through the Forlais website and the EvaEsi products, why we process it, who we give it to, how long we keep it and what rights you have. It is the main privacy notice for everyone who uses our websites, our platform, our mobile application, our developer platform and our support service. The regional schedules listed in section 3 sit underneath it and add whatever your local law requires.
What this notice covers
This notice covers the personal data Forlais Group Ltd processes as a controller. That means the personal data we decide the purposes and means of processing for.
It covers:
- the Forlais website and the EvaEsi marketing and documentation pages;
- the EvaEsi platform surfaces Chat, Index, Studio and Interests, and Verify across the platform;
- the EvaEsi mobile application, which carries Chat and Interests;
- the EvaEsi developer platform and the public API at
https://evaesi.dev/api/v1/; - accounts, sign in and account administration;
- billing and payment records;
- support requests and other correspondence with us;
- marketing and product communications.
There is no EvaEsi desktop application. If you are offered one, it is not ours.
What this notice does not cover
This notice is not the whole privacy estate. It does not cover:
- cookies and similar technologies, which are covered by the Cookie and Similar Technologies Policy (FOR-PUB-056) and the Cookie Preference Centre (FOR-PUB-057);
- retention and deletion timings, which are covered by the Data Retention and Deletion Notice (FOR-PUB-059);
- how we handle customer content for model training, which is covered by the Customer Content and Training Data Policy (FOR-PUB-060);
- international transfers in detail, which are covered by the International Data Transfer Notice (FOR-PUB-063);
- personal data we process on behalf of a business or enterprise customer under a contract. In that case the customer is the controller and its own privacy notice applies to its users. Our role and obligations are set out in the Enterprise Data Use Policy (FOR-PUB-061);
- personal data processed by third party services you reach through a link from our sites, which is covered by the Third-Party Links Notice (FOR-PUB-007);
- job applicants, who are covered by the Applicant Privacy Notice (FOR-PUB-071).
This notice is not legal advice and it does not form part of any contract. Your contract with us is in the EvaEsi Terms of Service (FOR-PUB-011) and the documents it refers to.
How this notice works with the regional schedules
We publish one privacy notice and a schedule for each territory that needs one. We do this so that the answer to a question is in one place and does not contradict itself.
| Schedule | When it applies to you |
|---|---|
| UK Privacy Schedule (FOR-PUB-038) | You are in the United Kingdom |
| EEA Privacy Schedule (FOR-PUB-039) | You are in the European Economic Area |
| United States Privacy Schedule (FOR-PUB-040) | You are in the United States |
| California Privacy Notice (FOR-PUB-041) | You are a California resident |
| Canada Privacy Schedule (FOR-PUB-045) | You are in Canada |
| Other territories | A schedule is published for each further territory we serve. The policy register lists them and is the authoritative list, because it changes as territories are added |
Our services are not offered in China or Hong Kong. A schedule for those territories exists (FOR-PUB-055) but is not in force, and it does not come into force until a separate market entry assessment for each has been completed and approved.
Three further notices apply only where United States state law makes them apply: the Do Not Sell or Share Notice (FOR-PUB-042), the Global Privacy Control Notice (FOR-PUB-043) and the Limit Use of Sensitive Personal Information Notice (FOR-PUB-044).
Who is responsible for your personal data
The controller is Forlais Group Ltd, company number 16835488, a private company limited by shares registered in England and Wales. Our registered office is 45 Albemarle Street, Mayfair, London, W1S 4JL, United Kingdom.
EvaEsi is a division and product name of Forlais Group Ltd. It is not a separate company. When you use an EvaEsi product, the controller is Forlais Group Ltd.
Write to us about anything in this notice at [email protected], or to the registered office marked for the attention of the Data Protection Lead.
We have appointed a Data Protection Officer. The role is independent, it has direct access to senior management, and it is responsible for the privacy programme across every territory we operate in rather than for one region of it. Write to the Data Protection Officer at [email protected], or at the registered office marked for their attention.
We are established in the United Kingdom and we have no subsidiary or branch elsewhere that acts as our principal establishment. Where a territory requires a local representative as well, we appoint one, and the schedule for that territory names the requirement.
Where your personal data comes from
| Source | What we get |
|---|---|
| From you directly | Account details, the content you submit to a surface, support messages, billing details and communication preferences |
| From your use of our products | Records of what you did, when, and from what device and connection, together with usage measured for billing |
| From other users | Your details when someone invites you to a shared Interests group or a Studio team workspace, and the content they contribute to a space you share with them |
| From an organisation | Where your account is provided by an employer or another organisation, the account and role information it gives us |
| From our payment providers | Stripe and Apple process payments for us. They tell us whether a payment succeeded or failed and give us the customer, subscription, entitlement, invoice, transaction status and payment reference information we need to run your account. Full card numbers never reach our servers and are never held on them |
We do not buy personal data from data brokers.
The personal data we process
| Category | Examples | Where it comes from |
|---|---|---|
| Account and identity | Name, email address, account identifier, plan, organisation membership and role | You, or the organisation that provides your account |
| Authentication and security | Sign in records, session records, password credentials held in a form we cannot read back, and security events on your account | Your use of our products |
| Content you submit | Chats, uploads, Index contents, Studio projects, and anything you type into a prompt | You |
| Model outputs | The responses our models produce for you, and the record that links them to your request | Generated by your use |
| Memory entries | Entries our products hold so that a later session can use earlier context | Generated by your use, and by you where you add or correct an entry |
| Shared and collaborative content | Content in a shared Interests group, and content, in project chat, presence and role information in a Studio team workspace | You and the other members of that space |
| Developer platform records | Project records, API key metadata such as the key name, its prefix and its creation and revocation times, the audit log of key operations, request logs, evidence bundles retrievable by request identifier, usage records, batch records and webhook endpoint configuration | Your use of the developer platform |
| Usage and billing | Usage measured in rungs, the plan allowance applied, project budget settings and the outcome of a budget check, invoices and payment records | Generated by your use |
| Device and connection | Internet protocol address, device and browser type, operating system, language, and the pages or routes you requested | Your use of our products |
| Support and correspondence | Your messages to us, our replies, and the account context needed to answer | You |
| Marketing and preferences | Subscription state, consent records and suppression list entries | You |
We never see the full value of an API key after you create it. Keys are issued for a single project, carry the prefix esi_dev_, are shown once at creation, and can be rotated or revoked at any time. Every key operation is written to the audit log.
Why we process personal data, and our lawful basis
The lawful bases named below are the ones we rely on under the UK GDPR. The EEA Privacy Schedule (FOR-PUB-039) names the equivalent articles of the General Data Protection Regulation. The schedules for territories outside the United Kingdom and the European Economic Area state the local equivalent.
| Purpose | Personal data used | Lawful basis |
|---|---|---|
| Giving you the products you asked for | Account and identity, content you submit, model outputs, memory entries, shared content | Performance of our contract with you |
| Generating model outputs | The content you submit and the context the surface supplies with it | Performance of our contract with you |
| Running accounts and keeping them secure | Authentication and security, device and connection | Performance of our contract with you, and our legitimate interest in protecting accounts against unauthorised access |
| Running the developer platform | Developer platform records, device and connection | Performance of our contract with you |
| Measuring usage, applying budgets and billing you | Usage and billing, account and identity | Performance of our contract with you, and compliance with tax and accounting law |
| Preventing abuse, fraud and misuse, and enforcing our terms | Usage and billing, device and connection, content brought to our attention, reports from users | Our legitimate interest in keeping the service safe and lawful, and compliance with our legal obligations |
| Answering your support requests | Support and correspondence, account and identity | Performance of our contract with you, and our legitimate interest in answering people who contact us |
| Telling you about changes, incidents and security matters | Account and identity | Performance of our contract with you, and compliance with our legal obligations |
| Sending marketing and product communications | Marketing and preferences, account and identity | Your consent, or our legitimate interest in telling an existing customer about similar products, in either case subject to regulation 22 of the Privacy and Electronic Communications Regulations 2003 |
| Meeting legal and regulatory obligations | Whatever the obligation requires | Compliance with our legal obligations |
| Establishing, exercising or defending legal claims | The records relevant to the claim | Our legitimate interest in defending our position, and the establishment of legal claims |
Where we rely on a legitimate interest, you may object. Section 18 explains how, and what happens then.
Where we rely on your consent, you may withdraw it at any time. Withdrawing consent does not make earlier processing unlawful.
Training and model improvement
Whether the content you submit is used to train or improve our models is the most important question in this notice, and it is answered in one place rather than in a form of words that could be read two ways.
We do not use the content you submit to train or improve our general models. That is the default and it applies to every kind of account and every surface: personal accounts, business and team accounts, enterprise accounts and traffic through the public API. You do not have to change a setting to get it.
There are three exceptions and no others:
- you hold a personal account and you opt into a clearly identified improvement programme. That is an affirmative choice you make yourself. It is never on by default and it is never bundled into accepting our terms;
- a business customer agrees in writing that specified content may be used. Nobody using that account can give that agreement in the organisation's place;
- an enterprise customer separately authorises in writing that something built specifically for it may inform general model development. Absent that, enterprise content is never used and anything adapted for an enterprise customer stays isolated from our general models.
The Customer Content and Training Data Policy (FOR-PUB-060) carries the full position, including how a choice is made and withdrawn and what withdrawing it does to content already used.
We give 90 days' notice before a change to that position takes effect, and a change never applies to content you provided before it took effect.
People at Forlais can read customer content, but only in named circumstances. Authorised personnel may read the minimum content necessary to answer a support request, to investigate a report of abuse, to diagnose a fault, to respond to a security incident, to meet a legal obligation, or to look at material you deliberately sent us as feedback. That access is reveal gated, role based, logged, attributable to a named person, time limited and confidential. Routine browsing of customer conversations is prohibited.
The Abuse Monitoring Notice (FOR-PUB-099) and the User Feedback and Model Improvement Notice (FOR-PUB-098) cover human access to content.
Memory entries
Our products hold memory entries so that later work can use earlier context. Memory entries are personal data where they describe you or someone else.
Every entry is visible to you, and each one shows what is held, where it came from and when it was recorded. You can correct an entry and the correction stands. You can remove or exclude any single entry, and you can delete all of your personal memory at once. An entry we inferred rather than one you told us is labelled as inferred and held as a proposal, and it does not persist until you approve it.
Personal memory, Studio project memory and Index memory are logically isolated. A workspace sees your personal layer and its own memory and cannot read a sibling project or a sibling Index unless you deliberately connect them. Every read and every write is authorised against the tenant, the project and the role before it happens.
A memory entry lasts until you correct it, remove it or switch memory off, or until the account closes. Your rights under section 18 apply to memory entries in the same way as to any other personal data we hold about you.
Special category and sensitive data
We do not ask you for special category data, meaning data revealing racial or ethnic origin, political opinions, religious or philosophical beliefs, trade union membership, genetic or biometric data used to identify a person, data concerning health, or data concerning a person's sex life or sexual orientation.
You must not put special category data into a chat, an upload, an Index entry or a Studio project unless you have a lawful reason to do so, and you must not put another person's special category data into our products at all.
We do not process special category data for any separate purpose of our own. We do not use it to profile you, to decide what you are shown, or to make any decision about your account. Where it reaches us inside content you submitted, we handle it as part of that content and it is subject to the same rights, retention and deletion as the rest of that content.
The Sensitive and Special-Category Data Notice (FOR-PUB-069) sets out the full position. United States state law defines sensitive personal information differently and more widely. The Limit Use of Sensitive Personal Information Notice (FOR-PUB-044) covers that definition and the control that goes with it.
Children and young people
You must be 18 or over to hold an account. People under 18 may not use our products, and they may not be added to an account an organisation administers.
Registration requires you to confirm your age. That is a self declaration and it is not highly effective age assurance, so we do not describe it as such. Where we receive reliable evidence that an account holder is under 18 we investigate it, and where it is right we suspend, verify and close the account. Where local law or the risk of a particular service requires stronger age assurance, we operate it.
The Age Eligibility Policy (FOR-PUB-067) carries the rule, and the Children and Young People Privacy Notice (FOR-PUB-066) covers what we do with a child's personal data if it reaches us.
If you believe we hold personal data about a child and we should not, write to [email protected] and we will look into it.
Automated decision making and profiling
Our models generate outputs automatically. That is what the product does. Generating an output is not a decision about you, and an output is not a judgement we have made about you. The Output Reliability Notice (FOR-PUB-086) explains what an output is and is not.
We do not use automated processing to make decisions about your credit, your employment, your insurance, your access to a service outside our own, or anything else that produces a legal effect on you.
Automated processing may be involved in enforcement against an account, for example suspension for suspected abuse. Automated systems also apply rate limits, reject invalid credentials, enforce hard budgets and temporarily restrict access for security reasons. None of those is a decision about you in the sense the law means. Where an account action is material and permanent, it carries a reason, an appeal route and human review.
Moderation operates across the collaborative and user to user surfaces, which are Interests and shared Studio workspaces. It runs with risk assessments, reporting routes, a complaints process, an appeal route and controls for illegal content. The Content Moderation Policy and the Enforcement Guidelines (FOR-PUB-126) set out how a decision is taken and how you challenge it.
this detail is not yet published
Where a decision about your account is taken by automated means alone and it significantly affects you, you have the right to ask for a person to look at it, to state your case, and to challenge the outcome. Use the routes in the Account Suspension and Termination Policy (FOR-PUB-028) and the Enforcement Guidelines (FOR-PUB-126).
Who we share personal data with
| Recipient | Why |
|---|---|
| Subprocessors | Suppliers who process personal data on our instructions so that we can run the products, covering infrastructure and hosting, authentication, email, monitoring, support, analytics, payments and encrypted storage. Each is bound by a written contract that limits them to our instructions. Every material provider is named in the Subprocessor List (FOR-PUB-064) with its service, purpose, data categories, hosting region and transfer mechanism. We give 30 days' notice before a new subprocessor begins processing, and you may object |
| Our payment providers | Stripe and Apple, to take payment and to detect payment fraud. See the Payment Processing Notice (FOR-PUB-026) |
| Other users you choose to share with | Members of a shared Interests group or a Studio team workspace see what you contribute to it, together with your presence and role in that space |
| Professional advisers | Lawyers, accountants and auditors, where they need the data to advise us and are bound by a duty of confidence |
| Authorities and law enforcement | Where we are legally required to disclose, or where disclosure is necessary to establish or defend a legal claim. Our approach is set out in the Law-Enforcement Data Request Guidelines (FOR-PUB-074) |
| A buyer or successor | If the business or part of it is sold or reorganised, to the buyer and its advisers, under confidentiality obligations |
this detail is not yet published The Public Sharing Policy (FOR-PUB-127) covers it.
We do not give your personal data to advertisers or to data brokers.
Selling and sharing under United States state law
Several United States states use the words sell and share in a wide sense that can catch disclosures made for no money.
Our position is that we do not sell personal data and we do not share it for cross context behavioural advertising.
this detail is not yet published
The Do Not Sell or Share Notice (FOR-PUB-042) carries the position and the opt out route.
Where your personal data is processed
Forlais Group Ltd is established in the United Kingdom. Our products are used worldwide, so personal data may be processed outside the country you are in.
Your account data, prompts, uploads, memory, Index contents and Studio project data are held in approved United Kingdom and European Economic Area regions. Operational logs and encrypted backups sit in approved regions too, and which ones is documented in our Data Location Register.
That is the primary position, and there is a limited exception to it. Some account, support, payment, security and service delivery data is processed in other approved regions by subprocessors we contract with, under recognised transfer safeguards. It is limited to what those functions need, and it does not extend to moving your prompts, uploads or project content out of the primary regions.
Where personal data leaves the United Kingdom or the European Economic Area, the transfer runs on a recognised mechanism: the EU Standard Contractual Clauses, the UK International Data Transfer Agreement, the UK Addendum, an adequacy decision, or the equivalent local mechanism where one applies. A transfer risk assessment is completed and recorded for each material restricted transfer route, and the clauses are accompanied by that assessment and by whatever supplementary safeguards it calls for.
The International Data Transfer Notice (FOR-PUB-063), the Subprocessor List (FOR-PUB-064) and the Data Location and Residency Page (FOR-PUB-065) carry this in full. The UK and EEA schedules state the transfer rules that apply to you.
How long we keep personal data
We keep personal data only for as long as we need it for the purpose we collected it for, or for as long as the law requires us to keep it. When neither applies, we delete it or make it permanently unidentifiable.
Most of what you create in the product is not on a timer at all. It is kept while you are using it and it goes when you remove it:
- chat conversations, until you or an administrator delete them or the account closes;
- Index contents and claims, until you or an administrator delete them;
- Studio project content, until the owner or an administrator deletes it;
- uploads, while they are attached to an active account, conversation, Index or Studio project;
- memory entries, until corrected, removed, switched off, or until the account closes;
- Verify history, until you delete it or the account closes;
- Interests content, while the post or the group exists.
The categories that do run on a fixed period are:
- API request content, 30 days, and evidence bundles retrievable by request identifier, 90 days;
- sign in and security logs, 12 months, longer only for a live incident or a legal hold;
- identifiable telemetry, 90 days, then deleted or reduced to aggregate figures;
- support correspondence, 2 years from closure of the issue;
- consent records, 6 years after the consent is withdrawn or expires;
- billing and accounting records, 7 years.
When you close your account, access is disabled promptly and we remove the data belonging to it from our live systems within 30 days of your request. Backups holding a copy expire within 90 days of the request, so 90 days is the outside figure for a copy surviving anywhere in our systems. A restore never resurrects deleted data, because we re-apply every deletion recorded since the backup was taken.
The Data Retention and Deletion Notice (FOR-PUB-059) carries the full table, including the categories not listed above and the criteria each period is set from.
Records we must keep by law, such as invoices and tax records, are kept for the statutory period regardless of any deletion request, and are then deleted.
How we protect personal data
The following controls are in place today.
- API keys are issued per project, are shown once at creation, and are stored in a form that cannot be reversed to recover the key. A key can be rotated or revoked at any time, and every key operation is written to the audit log.
- Sensitive developer platform actions require a signed in browser session rather than an API key. A leaked key cannot be used to redirect a customer event stream.
- Retrieval of evidence for a request checks the caller against the ownership record. A request for another account's record is answered as not found, so the response does not reveal whether the record exists.
- Traffic is encrypted, both between you and us and between our own services, including database and cache connections. Your data, your files, your credentials and your two factor secrets are protected with managed encryption at rest.
- Multi factor authentication and passkeys are available on your account. An enterprise customer can require them across its organisation. Our own staff, and anyone with privileged access, must use them.
- Administrative access, key operations, budget changes and sensitive reveals are attributable to a named person and recorded in a form designed to show tampering. Central security monitoring runs across the platform.
- We run central security monitoring, classify incidents, escalate to an on call rota, preserve evidence, take a legal and privacy assessment, work out who is affected, notify regulators where the law requires it and tell affected customers. Where an incident affects you, we tell you without undue delay and within the period the law or your contract sets.
No system is perfectly secure. If you think your account has been accessed by someone else, tell us at [email protected]. If you have found a security weakness in our products, use the Vulnerability Disclosure Policy (FOR-PUB-104). The Security Overview (FOR-PUB-102) describes our security posture in more detail.
Your rights and how to use them
The rights below are the ones the UK GDPR gives you. If you are in another territory, your schedule states the rights you have there, which may be wider or narrower.
| Right | What it lets you do |
|---|---|
| Access | Ask what personal data we hold about you and get a copy of it |
| Rectification | Have inaccurate personal data corrected, and incomplete data completed |
| Erasure | Ask us to delete personal data where we no longer need it, where you withdraw the consent we relied on, or where you object and we have no overriding ground to continue |
| Restriction | Ask us to stop using personal data while a dispute about its accuracy or our grounds is resolved |
| Portability | Get the personal data you gave us in a structured, commonly used, machine readable format, and have it sent to another controller where that is technically feasible |
| Objection | Object to processing we base on a legitimate interest, and object to direct marketing at any time. An objection to direct marketing is always honoured |
| Withdraw consent | Withdraw consent for anything we do on the basis of consent, at any time |
| Human review of an automated decision | Ask for a person to review a decision made about you by automated means alone that significantly affects you |
| Complain | Complain to a supervisory authority. Section 21 explains how |
To use a right, use the Privacy Rights Request Page (FOR-PUB-058) or write to [email protected]. Say which right you are using and give us enough detail to find your records.
We acknowledge a request within 5 working days and answer within one month. Where a request is complex, or where you have made several requests, we may extend that by up to two further months. If we extend, we tell you within the first month and say why.
We may ask you to confirm your identity before we act, and we will only ask for what we need to be satisfied. If we cannot identify you from the information you give us, we will say so rather than guess.
There is no charge. If a request is manifestly unfounded or excessive we may charge a reasonable fee for the administrative cost, or refuse it. If we refuse, we tell you why and how to challenge it.
Some rights have limits. We may keep personal data we are legally required to keep, and we may refuse a request where complying would disclose another person's personal data or would prejudice the establishment or defence of a legal claim. We tell you when a limit applies and which one.
You can export your account data, chats, uploads, Index contents, claims, evidence, Verify history, Studio projects and project files, memory, Interests, membership information and the usage records that relate to you. An authorised workspace administrator can do the same for the workspace they administer. Exports come in documented portable formats, which are JSON, CSV and ZIP depending on what is being exported. The Data Export and Portability Policy (FOR-PUB-062) covers it, and gives you 30 days from termination to take an export before access is withdrawn.
Cookies and similar technologies
We set cookies and use similar technologies on our websites and in our platform. What we set, why, and how to change your choices is in the Cookie and Similar Technologies Policy (FOR-PUB-056). You change your choices in the Cookie Preference Centre (FOR-PUB-057).
We do not set non essential cookies before you consent, as regulation 6 of the Privacy and Electronic Communications Regulations 2003 requires. Where you are in a territory that recognises a browser based opt out preference signal, the Global Privacy Control Notice (FOR-PUB-043) explains how we treat it.
Marketing
We send marketing only where we are allowed to. You can stop it at any time using the unsubscribe link in any marketing message, in your account settings, or by writing to [email protected]. We keep a suppression record so that an unsubscribe is not undone by a later import.
Service messages are different. We send those because we have to, for example to tell you about a change to these terms, a billing problem or a security incident. You cannot unsubscribe from service messages while you hold an account.
The Marketing Communications Privacy Notice (FOR-PUB-070) covers this in full.
Complaints
If you are unhappy with how we have handled your personal data, tell us first at [email protected]. We will look at it and reply.
You may also complain to a data protection authority. If you are in the United Kingdom, that is the Information Commissioner's Office. If you are elsewhere, your regional schedule names the authority for your territory. Complaining to us first is not a condition of complaining to an authority.
The Complaints Policy (FOR-PUB-029) covers complaints that are not about privacy.
How we change this notice
We update this notice when what we do with personal data changes, when a new product surface starts processing personal data, or when the law changes.
Every version carries a version number, a document date and an effective date. Superseded versions are kept in our policy register and are available on request.
A material change is one that changes what we do with your personal data, who we give it to, how long we keep it, or what rights you have. Where a change is material, we publish it 30 days before it takes effect and we tell account holders by email or by a notice in the product. A change to the position on customer content and model training carries 90 days' notice under section 8, and a new subprocessor carries 30 days' notice under section 13. A change that only corrects wording is published without separate notice.
How to contact us
| Subject | Address |
|---|---|
| Anything in this notice | [email protected] |
| Using one of your rights | The Privacy Rights Request Page (FOR-PUB-058), or [email protected] |
| A complaint about how we handled your personal data | [email protected] |
| Formal legal notices | Forlais Group Ltd, 45 Albemarle Street, Mayfair, London, W1S 4JL, United Kingdom, marked for the attention of the Company Secretary |
| A security weakness in our products | See the Vulnerability Disclosure Policy (FOR-PUB-104) |
An email to a general address is not service of a legal notice. The Contact and Legal Service Notice (FOR-PUB-005) sets out how to serve one.
About this document
| Property | Value |
|---|---|
| Reference | FOR-PUB-036 |
| Version | 0.3 |
| Effective date | 29 July 2026 |
| Applies to | Everyone whose personal data Forlais Group Ltd processes through its websites, its products, its developer platform, its support service and its accounts |
| Products | The Forlais website, the EvaEsi platform surfaces Chat, Index, Studio and Interests, Verify across the platform, the EvaEsi mobile application, the EvaEsi developer platform and API, and our account and support services |
| Territories | All territories where our websites and products are available, read together with the regional schedule for your territory |
Version history
| Version | Date | Change |
|---|---|---|
| 0.1 | 28 July 2026 | First controlled draft. Carries unresolved gaps against FOR-REG-002 entries C1, C2, C3 to C7, C9, D1 to D8, E5, E6, E10, E11, F10, G1, G2, G6, H4 and I3, and one entry the register does not yet hold on sale and sharing under United States state law. |
| 0.2 | 29 July 2026 | Production pass. Committed values written in from the decision schedule (FOR-REG-008): retention periods, the account deletion and backup timetable, the minimum age of 18 and the age assurance position, the 30 day subprocessor notice, the 90 day training change notice, the 30 day policy change notice, the 5 working day rights request acknowledgement and the 30 day export window. Draft commentary removed. Two internal cross references corrected. |
| 0.3 | 29 July 2026 | Answers pass. Confirmed operating position written in from FOR-REG-002 and FOR-REG-008. Sixteen of the nineteen confirmation gaps closed: the Data Protection Officer appointment, the payment providers and what card data reaches us, the training position with its personal, business and enterprise exceptions, human access to content and its conditions, memory visibility, correction, deletion, inferred entry approval and workspace isolation, moderation capability, the named subprocessor categories, hosting regions and the international processing exception, transfer mechanisms and transfer risk assessments, encryption, multi factor authentication and passkeys, logging and monitoring, incident detection and notification, and export scope and formats. Retention periods at section 16 corrected against the reissued schedule, which moved user controlled content off a fixed clock and reversed the API request content and evidence bundle periods. Three gaps remain: C10 on sale and sharing under United States state law, H4 on automated abuse detection, and I3 on public sharing. |
