Privacy

What Scenario Book for Jira stores, where, and for how long. Provider: Gold Standard Web LLC, 7530 39th Ave, Kenosha, WI 53142.

The short version

• Your scenarios stay in your Atlassian site: in Atlassian's Forge storage for the app, and in your own Jira.
• Nothing leaves Atlassian. The app has no outside servers and makes no outside calls.
• About people, the app keeps Atlassian account ids only, never names or email addresses.

What we store

Your scenarios, in full. The feature files your team writes are your content, and storing them is what the app is for. Scenario Book keeps:

• each feature file, and its last 50 versions;
• an index of each file's scenarios: name, tags, line numbers, and which stories they belong to;
• for each sync key, the last version of each file Jira and your repository agreed on, so it can tell who changed what. It is removed when the key is revoked or the file is deleted;
• while a conflict is open, the three versions of that scenario: Jira's, the repository's, and the last agreed one;
• test results: status, the name of the failing step, and an error message cut to 1 KB;
• a record of each import, so it can be undone.

Treat scenario text like any other text in Jira. Test scenarios often contain realistic-looking test data. Scenario Book can't tell real data from made-up data and stores what you write. Please don't put real personal, health or payment data in scenarios.

About people: the Atlassian account id of whoever last saved a file or setting, made a version, deleted a file, created a sync key, resolved a conflict or started an import.

Sync keys are stored only as a one-way hash. We can't show a key again, and neither can anyone else.

What we copy into your Jira

• On each story with scenarios: a small property with counts only (scenarios, passed, failed, not run, last run date), so JQL can find them. It stays on the story after you uninstall; it holds no scenario text.
• Only while a project admin has pipeline sync on: a copy of the project's feature files, in Jira project properties, so your pipeline can read them. Anyone who can browse the project can read these. Turning sync off takes them back, and so does uninstalling.

What we read but don't keep

Story statuses, fix versions and issue types, to filter scenarios by them. They are read from Jira each time and not stored.

Where it lives

In Atlassian's Forge storage for your site, and in your own Jira. Forge is Atlassian's app platform, so the data is held under Atlassian's own security and data residency. The app is Runs on Atlassian: no servers of its own, nothing sent outside Atlassian.

Who can see it

People in your site, according to their Jira permissions: anyone who can browse a project can read its scenarios; only people who can edit a story can change, delete or restore its scenarios. We can't read your stored data. If you contact support, we only see what you send us.

How long it is kept

• Feature files: until you delete them. A deleted file is kept 30 days so it can be restored, then removed with its versions, conflicts and sync records.
• Versions: the last 50 of each file.
• Test runs: the last 50 per project, or the number a project admin sets (1 to 1,000).
• Import files: a working copy is kept while the import runs, and removed when it finishes or fails, or after 7 days at most.
• On uninstall: the app removes the copies it published to your projects, and Atlassian deletes the app's storage 28 days after the uninstall. If you reinstall within 21 days, you can ask Atlassian to reconnect the old data. After 28 days it is gone.
• If your license lapses, your scenarios stay, and reading and export keep working until you uninstall. Housekeeping continues: deleted files are still removed after 30 days.

Each week the app tells Atlassian which account ids it holds, as Atlassian requires. If an account has been closed, the app replaces that id wherever it appears, and then checks that none is left; a run that leaves one behind fails rather than reporting success.

Your role and ours

You decide what goes into your site and your scenarios. The data stays in your own Atlassian site, and Gold Standard Web has no access to it, so we don't act as a processor of it.

Support emails

If you email hello@goldstandardweb.com, we keep that conversation to help you, and delete it on request. Please don't send us scenario files that contain anything sensitive.

Questions

Email hello@goldstandardweb.com.

Last updated: November 6, 2026.