Privacy notice.
How we use personal information when you visit and use Scenario.
Effective 27 September 2026, updated 3 October 2026. Scenario is the contact for questions and requests about this notice: [email protected].
Where this applies
This notice covers Scenario’s website, accounts and workspaces. When you connect a supported provider, add business context or ask Scenario a question, the information involved may contain personal data about you, your staff or customers. You should only provide information you are entitled to use.
What we collect
When you sign up, we receive your name, email address and, for email sign-in, a protected password hash. If you use Google or GitHub, we receive the information needed to sign you in, such as a provider identifier, email and profile image. We keep sessions, verification and security records, including IP address, browser or device details and rate-limit records.
In a workspace, we process information you enter or upload, connected account data, derived metrics, scenarios, questions, responses and service usage. Connected Stripe data may include customer, invoice, subscription and payment records relevant to the analysis. For a paid plan, we keep Stripe customer and subscription identifiers, the plan, payment status and cancellation setting. Stripe processes the payment details; Scenario does not receive full card numbers. During setup you can also tell us your business’s website and how you found Scenario; both are optional. If you arrived through a tagged link (for example one ending ?ref=reddit), we keep that tag with your workspace so we know which posts bring people in. We use these answers to understand who Scenario is for and to improve it, and they are deleted with your workspace. If you import a bank statement, we read the file to work out monthly totals by kind of spending and keep only those totals; the file and its transactions are not stored. If you switch on a public page in Settings, the figures you choose (your business name, and if you tick them, monthly revenue and customer count) are shown to anyone with the link until you switch it off. If you email us, we receive your message and contact details. Site visits also generate technical requests and server logs.
Why we use it
We use account information, workspace content and necessary cookies to provide sign-in, connections, analysis, answers and service messages. Where we act as controller, the lawful basis is performance of our agreement or steps you request before entering one. We use technical and security records to prevent abuse and maintain the service under our legitimate interest in a secure, reliable service. We use correspondence to respond to you under that same interest or, where relevant, to take steps you request before a contract.
Where your workspace contains other people’s data, your business may be the controller and Scenario may process it on your behalf. Contact us if you need to discuss a data processing agreement before providing such data.
Website analytics
We measure visits to our public website (not the signed-in app) with Scenario Analytics, our own cookieless analytics. For each page view we record the page address, the site that linked to it and any campaign tags, the country and, where available, the town or city, with the town’s position kept only to about 10 km (worked out by Cloudflare from your IP address, which we do not store), the type of device, the browser and operating system family, and how quickly the page loaded. To count visitors without cookies, we use a keyed hash of your IP address and browser details that changes every day and cannot be turned back into either. Nothing is stored on your device. We use this only to understand how the website is used and to improve it, and we keep it for 24 months. To leave yourself out, open any page of the site with ?scenario_ignore=1 at the end of the address; this saves a note in your browser that the analytics reads and respects.
Workspaces can also use Scenario Analytics on their own websites. There, we process the same limited information on the workspace’s behalf, only to provide their reports: we do not sell it, use it for advertising or combine it across websites. The website owner is responsible for telling their visitors about it.
If you use the chat on our website, we keep the conversation (what you and our team write, and when) so our team can read it and reply. An AI assistant answers first and its replies are labelled as AI; to write them, the conversation is sent to our AI provider (see “Who receives information”). A random key saved in your browser lets the chat carry on when you come back; clearing your browser data removes it. We keep chats until you ask us to delete them.
Businesses can also put this chat on their own websites. There, we process the chat on the business’s behalf, only to provide it to them: the business is responsible for telling its visitors, and requests about those chats go to the business. If a workspace invites you to its team, we keep your email address with the invitation and send you one email with a link to join (and again only if they resend it); an invitation that isn’t accepted stops working after 7 days. A business can ask for your name and email before its chat starts; they are kept with the chat so its team can reply, and the AI that writes replies does not see them. If the business turns on its team-only checks, we use them to look you up in the business’s own Stripe account, to check a one-way fingerprint of your email (never the address itself) against a public spam list (StopForumSpam), and to ask our AI provider whether the name looks genuine and whether the messages look like trolling. A business can also ask you to confirm your Discord account: its own bot sends you a message to answer. Once you have confirmed it, you can choose “Remember me on this device”: your browser keeps a random key for that business, so next time the chat can greet you and skip the checks. It lasts 30 days from when you last used it, and “Not you?” deletes it. We don’t recognise people by their IP address or device fingerprint. A business can also let the chat look up your own account in its own systems (for example your plan or recent activity), once you have confirmed who you are; only the business’s system and your confirmed account identifier are involved, and what comes back is filtered so the assistant sees only what it needs about you. These checks are shown only to the business’s team, are kept with the chat, and never decide anything on their own. Team members can add a photo, which is shown to customers in the chat.
How long we keep it
Sessions expire after seven days unless renewed through use. Verification and reset links expire sooner. We keep account and workspace records while your account is open. On closure, you can request removal of account and workspace information, subject to records we need for security, legal or dispute reasons. Disconnecting a provider stops future access; it does not by itself erase information already imported. Website analytics records are deleted after 24 months, and straight away when a workspace removes its site. Contact us about deletion of that information.
Your choices
You can ask to access, correct or erase your personal information, restrict its use, object to use based on legitimate interests, or receive information you supplied in a portable form where the law applies. Email us to exercise a right. We may need to verify your identity and may have a lawful reason to keep some records.
You can complain to the Information Commissioner’s Office in the UK. We would welcome the chance to address your concern first.
Changes to this notice
We will update this notice when the service or its providers change materially. The date above shows when it was last updated.