ScenarioLoom
Your data, explained plainly

Privacy statement

Updated 7 November 2026

ScenarioLoom processes your schemas, settings and imported alerts on your device. This statement explains what the app uses, what it saves, and what you choose to share.

No uploadsfor generation or scoring
No accountfor Free generation
No analyticsor app telemetry

What the app processes

The browser reads the schema text and settings you enter, creates synthetic records, and prepares exports locally. In AML scoring, it also reads the alert file you select and compares those alerts with the generated answer key. Those inputs are not sent to a generation service or scoring API.

The app has no advertising, analytics, application telemetry or tracking cookies. The bundled CLI also processes its inputs locally.

Accounts, subscriptions and licences

Free generation does not require an account. On a copy connected to the account service, you can create an account with an email address and password. That service stores the email address, a salted password hash, account and subscription identifiers, payment-status records and session records. A necessary HttpOnly session cookie keeps you signed in; signing out invalidates that session. Passwords are not stored as plain text. Confirmation and password-reset emails are delivered by our email provider, Resend, which receives your email address and the message it delivers.

The online workspace checks your account plan through the same-origin account service. These requests contain no schema, setup, generated records or imported alert contents. Subscription checkout and management use Stripe when configured; Stripe receives billing/account details through its hosted pages and service. Payment-card details are not entered into ScenarioLoom. Placeholder billing configuration cannot take payments.

An offline licence contains an opaque account identifier, licence identifier, update entitlement date and the covered release identity. It contains no email address, schema or alert data. Offline generation does not require network checks. Operator contact, retention and commercial terms must be supplied before a public paid launch.

What stays in browser storage

ScenarioLoom saves your setup in local storage so you can return to it. Saved settings can include schema text, seed, anchor date, selected options and settings for modes you are not currently viewing. Local storage belongs to the browser profile and site address you use; different ports or browsers have separate saved settings.

Imported alert-file contents, generated datasets and score reports are kept in the app’s memory rather than saved in its local storage. Files you download are separate copies on your device and remain under your control.

How to remove saved settings

In your browser’s site settings, clear storage/site data for the address where you use ScenarioLoom. The compatibility storage key is schemaseed:v1. Clearing site data does not delete exported files or copies of links you have shared. Private browsing can limit persistence, depending on the browser.

What a share link contains

A complete share link contains the active mode’s setup, including the schema in schema mode. Other modes use their selected settings and a built-in example schema; inactive private schemas and unrelated mode settings are left out. Imported alerts, generated rows and score reports are not included.

The setup is encoded, not encrypted. Anyone with the complete link can read it. The URL fragment is not part of the HTTP request to the host, but it can still appear in browser history, clipboard tools, extensions or services through which you share the link. Share only a setup you intend to disclose.

Download setup creates a versioned file with the same active-mode scope. Treat a setup file as potentially sensitive when its schema or settings reveal private information.

Hosting and other software

When you open a hosted copy, your browser requests the app’s static files. The hosting provider may record normal web-request information, such as your IP address, requested paths and browser headers. ScenarioLoom does not control that provider’s logging.

Browser extensions, operating-system services, shared-device access and other applications are outside the app’s control. This statement describes the bundled app; a separately modified or hosted version may have different behavior.

Your exports and shared copies

You choose when to download or copy data, setup files, answer keys and reports. ScenarioLoom has no hosted storage or backup service for them. Review those files before importing them into another system, and apply your own storage and sharing controls.

For the processing model, offline options and local setup instructions, visit Run locally & data security. For tool capabilities and fixture limitations, see About & use cases.