STORAGE & PRIVACY
Data residency
Simple Tables keeps core table content in Atlassian-hosted Confluence and Forge services. It does not use a Simpleasyty-operated external database for that content.
Where table data lives
Where the data lives depends on its source and the storage choice made when saving. Compare the four locations below.
- Inline page content
- Pasted or imported data saved inline, together with its table configuration, is retained with the macro on the relevant Confluence page.
- Native Confluence table
- For Simple Table with Body, the native Confluence table remains the source of record that editors manage on the page.
- Confluence page attachment
- For larger datasets, or when an editor elects to save one, the data is retained as an attachment on the same Confluence page.
- Atlassian Store (Forge)
- Static rows are saved in Forge storage; the macro keeps a reference to them.
Residency scope
Confluence page content and attachments follow your site’s data residency settings. Atlassian Store uses Forge hosted storage, which supports the host site’s data residency. Simple Tables does not offer an independent region selector.
Lifecycle, deletion, and recovery
Page content, native tables and attachments follow Confluence’s page lifecycle and recovery controls. Atlassian Store payloads are stored separately: deleting a page should not be treated as confirmation that its Forge data has been erased. Switching storage also leaves earlier page versions, attachments and exported copies unchanged.
External sources
For a URL-based data source, the source system remains responsible for its own data location, access controls, and retention policy.