Privacy

What Space Factory for Confluence stores, where, and for how long.

Last updated: 2026-11-05. Provider: Gold Standard Web.

The short version

• Your data stays in Atlassian’s Forge storage, inside Atlassian’s cloud.
• Nothing leaves Atlassian. The app has no servers of its own and makes no outside calls.
• We don’t store page content. We store ids, settings, page titles and the values people type into a template’s blanks.
• When someone closes their Atlassian account, the app erases their account id within about a week.
• Atlassian deletes everything when you uninstall.
• We (Gold Standard Web) can’t see your data.

What we store

• Templates: which space or page tree to copy, the blanks found in it, the naming rules, the roles, watch and restriction rules, and which groups may use it — and every saved version of each template.
• What reading a template found: the counts, the blanks, and the titles of any pages the app couldn’t read.
• Requests: who asked (an account id), the values they filled in, who decided and the reason they gave.
• Creations: how far each one has got, step by step, with the id of every page, label, restriction and watch made, so the creation can be undone.
• An activity log: who did what, by account id only.
• Page titles and space names: for each page a creation made, the title it had in the template and the title it ended up with, so the result screen can show what was renamed and undo knows what it made; and the new space’s name. These can hold whatever people typed into the blanks, such as a client’s name. The page bodies are never stored.
• Settings: which groups may make templates and approve requests, the limits, and whether undo may delete permanently.

We don’t store page content, email addresses or IP addresses, and we don’t track anybody.

The people we hold ids for

An account id is Atlassian’s random id for a person. The app holds the account ids of:

• the people who made or saved a template, and the people a template names as approvers;
• whoever asked for a space, and whoever approved or declined the request;
• whoever started a creation — also written inside the key the creation was sent under, which is how the app makes sure it never creates the same space twice;
• the people given a role on a new space;
• every member of the groups set to watch a new space: the creation keeps the list while it works, and a record that each one was set watching;
• the person a welcome page greets;
• the people chosen in a “person” blank;
• the person behind each entry in the activity log.

It also keeps two kinds of display name: the person chosen in a person blank, because that’s who gets @mentioned on the new pages, and the person who asked, for the built-in {requester} blank.

Every one of these ids is reported to Atlassian each week, and erased when the account is closed (see Closed accounts, below).

The values people type

What someone types into a blank — a client’s name, a project, a date — is your content. It is stored with the creation so you can see what was made and undo it. Your admin sets how long that is kept; after that it is cleared out.

What we read but don’t keep

To do its job the app reads, through Confluence’s own API: the pages of the space being copied and their content, who can see them, and space permissions. These are used while a creation runs and are not stored, beyond the ids, titles and counts above.

Group member lists are the one exception. When a template sets groups to watch the new space, the app reads who is in them and keeps those account ids with the creation while it sets each person watching, along with a record that it did.

Where it lives

In Atlassian’s Forge storage for your site, so it sits under Atlassian’s own security and data residency. There is nowhere else.

How long we keep it

A Confluence admin sets how long the record of every creation, finished or failed, is kept — 7 days to 10 years, 180 days by default. After that the values are cleared and the record is deleted. Requests that were decided or withdrawn before then are deleted too; a request still waiting is kept until someone decides it or the person takes it back. The spaces that were created are never touched by this.

Everything else lasts until you uninstall. On uninstall, Atlassian deletes the app’s storage.

What is left behind when you uninstall

Atlassian deletes the app’s own storage. Two things are not the app’s storage and do not go with it:

• The spaces and pages it created. They are your content and they stay — that is the point of the app, and uninstalling never deletes anyone’s work. Their roles, restrictions, labels and watchers stay too; they are the space’s own settings, which you can see and change in Confluence.
• A small record on each space the app created, called gsw.family.rules. It holds the space key, the run it came from, the groups set to watch, and the pages with edit rules (by id and title). A page only some groups may see is left out of it, so the record never shows anyone a page they couldn’t open. It is there so Restriction Rules — and Group Watch, once its update ships — can keep those rules up to date as people join and leave your groups, and it is deliberately left in place — if you still use those apps, removing it would stop them working on that space. It holds nothing a person who can already see the space could not already see. Deleting the space removes it; if you want it gone from a space you are keeping, email us.

Closed accounts

Each week the app tells Atlassian which account ids it holds, as Atlassian requires. If an account has been closed, the app erases that id and blanks any display name stored beside it.

Support emails

If you email hello@goldstandardweb.com, we keep that conversation to help you, and delete it on request.

Questions

Email hello@goldstandardweb.com.