Last updated 3 November 2026
Privacy policy
This policy explains what personal data we hold, with whom it is shared, how long it is kept, and the respective responsibilities of Six Weeks Out and its customers under data protection law.
1.Who we are
Six Weeks Out is marketing planning software for the UK hospitality sector, operated by Six Weeks Out Ltd. Questions about this policy or about your personal data should be sent to [email protected].
This policy describes how we handle personal data. Where we process personal data on behalf of a customer, the contractual terms governing that processing are set out in our data processing agreement.
2.Our role: processor and controller
Under the UK GDPR, responsibility for personal data depends on whether an organisation acts as a controller or as a processor. We act in both capacities, in relation to different data.
Our customer is the controller of the personal data entered into the service, including details of its staff and their roles, the tasks assigned to them, campaigns, audit answers and the contents of free-text fields. The customer determines what data is entered and for what purpose. We process that data on the customer’s instructions, solely in order to provide the service.
We are the controller of the records we keep to operate our business: details of our customers, the contact details of the person who registered, records of acceptance of our terms, billing records, support correspondence, and the technical logs used to monitor the service.
3.The data we hold
Account and access data: name, email address, job title, the roles held and the sites to which they relate, and the time of last sign-in. Because sign-in is by emailed link, we also hold short-lived sign-in tokens.
Data generated through use of the service: tasks and their assignees, approvals, comments, recorded absences, campaign plans, audit answers and associated notes.
Publicly available business information: when a restaurant is set up, we retrieve information it has published, such as its address, opening hours and description, so that it does not need to be entered manually. This is information about a business rather than about an individual.
Support access records: when one of our administrators accesses a customer account to provide support, we record which administrator, whose view was used, when, and which pages were opened. We record the pages visited, not their contents.
We do not request special category data within the meaning of Article 9 of the UK GDPR, such as information about health, religious beliefs or trade union membership. Absences may be recorded without a reason being given. Free-text fields will accept any input, and customers should ensure that special category data is not entered into them.
4.Purposes and lawful basis
We process customer content on the customer’s instructions in order to provide the service, under our contract with the customer. The data processing agreement is the contract between controller and processor required by Article 28 of the UK GDPR.
We process our own business records on the basis of our contract with the customer and of our legitimate interests in operating, securing and improving the service. We do not sell personal data, and we do not use it to target advertising at individuals.
5.Product improvement
We use information about how the service is used, such as achievable lead times and the tactics customers remove, to improve the planning it provides, including to develop and train our own machine learning and artificial intelligence models.
We use only aggregated, anonymised and non-personal information for this purpose. Customer data is aggregated and anonymised under the authorisation given in our data processing agreement, and is never used for this purpose in a form that identifies a customer, a member of its staff or any other individual. Information that has been anonymised is no longer personal data. We do not train models on customer content itself, meaning the text of plans, comments or audit answers.
A customer may opt out of the use of its information for model training at any time by emailing [email protected]. The opt-out applies to information derived after we receive it.
6.Artificial intelligence
Certain features send customer content to a third-party artificial intelligence model provider, named in the list of sub-processors below: for example, to generate campaign plans, summarise audits, draft the weekly digest and retrieve a restaurant’s public details. Only the information needed for the task is sent, which may include text entered by users.
We use such providers only on terms that do not permit them to use customer content to train their models. All output is a draft for review by a person and is not acted upon automatically. No decision about any individual is made solely by automated means.
7.Sponsored offers
The service may display sponsored offers from suppliers whose goods or services relate to the work in a customer’s plans. We select offers using information about the customer’s business, such as the location of its sites and the type and timing of upcoming work, and not on the basis of information about individual members of staff. Offers are selected on our own systems, without advertising cookies or tracking technologies.
We do not share customer data with suppliers. A supplier learns of a customer only if a user chooses to contact it, or asks us to pass their details on. We report to suppliers only the number of times their offers have been shown and selected. A customer may ask us to stop showing offers by emailing [email protected].
8.Sub-processors
We use sub-processors to host the service, provide its artificial intelligence features and deliver email. Our current sub-processors are:
| Who | What they do with it | Where |
|---|---|---|
| Railway | Runs the application and hosts the database. Holds everything, encrypted at rest. | EU (Amsterdam) |
| Anthropic | The Claude models behind the AI features, including the web search that looks up a restaurant's public details. | US |
| Resend | Sends sign-in links and welcome emails. Receives a name and an email address. | EU |
| Cloudflare | Serves the domain and routes traffic to the website and the service, protecting both from attack. | Global edge |
| Our own email and the demo booking page. Receives what you type when booking a demo. | US / EU |
We may change our sub-processors from time to time. Where a sub-processor is located outside the UK or the European Economic Area, transfers are made under the UK International Data Transfer Addendum, Standard Contractual Clauses or another lawful transfer mechanism. Before a new sub-processor begins processing customer data we will update this list and notify customers, as set out in the data processing agreement.
9.Cookies
We use one cookie to keep users signed in. It is set at sign-in, contains a signed token and no other information, and expires after thirty days or on signing out. Our administrators receive a second cookie, valid for twelve hours, while accessing a customer account to provide support; it links that session to its access record. Neither cookie can be read by scripts running in the page.
Cloudflare, which routes traffic to our website and to the service, may set a cookie to distinguish people from automated traffic; it does not identify individuals. As these cookies are strictly necessary to provide the service, consent is not required for them under the Privacy and Electronic Communications Regulations.
We do not currently use analytics or advertising cookies. If we introduce cookies that are not strictly necessary, we will update this policy beforehand and will not set them without your consent where the law requires it.
10.Retention
Customer content is retained for as long as the customer’s account remains open. When an account is closed, we will provide a copy of the data on request and then delete it within 90 days, except where retention is required for tax or legal purposes. Copies held in database backups are deleted when those backups expire in accordance with their retention period.
Sign-in tokens expire within minutes of issue. Support access records are retained for two years, so that questions about access to an account can be answered after the event. Our records of customers, including registration details, acceptance of our terms and invoices, are retained for as long as required by tax law or for the establishment or defence of legal claims.
11.Your rights
You have the right to request a copy of your personal data, to have it corrected or erased, to object to its processing and to request that its processing be restricted. If you are a member of a customer’s staff, your employer is the controller and requests should be made to them in the first instance; we will assist them in responding.
If you have a concern about how we have handled your personal data, please contact us and we will seek to resolve it. You also have the right to complain to the Information Commissioner’s Office at ico.org.uk.
12.Security
Sign-in is by emailed link rather than by password, so no user passwords are stored. Data is encrypted in transit and at rest. Administrator access to customer accounts is read-only by default and is recorded on every occasion. Further information, including how to report a security concern, is set out on our security page.
13.Changes to this policy
We will update this policy as the service changes. The date at the head of this page shows when it was last revised. We will notify customers directly of any change that materially affects them.
Six Weeks Out Ltd, registered in England and Wales no. 16460224. © 2026 Six Weeks Out Ltd. All rights reserved.