Last updated 3 November 2026

Security

This page summarises the measures we take to protect customer data, for those responsible for assessing Six Weeks Out as a supplier.

1.Hosting and encryption

The application and its database are hosted by Railway in its EU West region, in Amsterdam. Data is encrypted in transit using TLS and at rest on the database storage.

Point-in-time recovery is enabled on the production database, allowing it to be restored to any moment within its retention period. Backups are held within Railway only.

2.Authentication

The service does not use passwords. Users sign in by requesting a link sent to their work email address. Each link may be used once and expires after fifteen minutes. A link is consumed only when the user confirms on the page it opens, so that email security scanners which follow links cannot use it.

Sessions are held in a signed cookie that cannot be read by scripts in the page and that expires after thirty days. The sign-in form does not disclose whether an account exists for a given address, and requests are rate-limited per address and per domain.

Access is available only to people invited by a customer and to people with an address at an email domain the customer has registered. Public email domains cannot be registered.

3.Separation of customer data

Every request is checked against the organisation to which the signed-in user belongs, and each user belongs to a single organisation. Permissions within an organisation, such as approving work, managing the team or deleting a campaign, are enforced on the server.

We carry out periodic security reviews of the service.

4.Support access

Our administrators may access a customer account in order to provide support. Such access is read-only unless expressly changed, lasts no longer than twelve hours, and is recorded on every occasion, including the administrator, the account viewed, the time and the pages opened. The contents of those pages are not recorded. The record is available to the customer on request.

5.Sub-processors

Our sub-processors are listed in our privacy policy, and no other party receives customer data. The artificial intelligence features send only the information each task requires, to providers whose terms do not permit them to train their models on it.

6.Development and change management

Every change is subject to automated type checks and tests before deployment, and is deployed to staging before it reaches production. We monitor security advisories for our dependencies and apply patches as they are released. Credentials are held in the hosting platform rather than in source code, and the source code is held in a private repository.

7.Certifications

We do not currently hold ISO 27001 or SOC 2 certification, and we have not yet commissioned an independent penetration test. If either is a requirement of your procurement process, please contact us to discuss it.

8.Reporting a vulnerability

Please report any security vulnerability to [email protected]. We will acknowledge reports within two working days, keep you informed of progress, and credit you if you wish. Please do not access data that is not your own, or take any action that could degrade the service for other customers. We will not take action against good-faith research carried out within these limits.

Back to the main page

Six Weeks Out Ltd, registered in England and Wales no. 16460224. © 2026 Six Weeks Out Ltd. All rights reserved.