Data residency
Simple Tables keeps its table content with your Confluence content. It does not use a separate Simpleasyty database for the core table workflow.
Where table data lives
The storage location follows the table source.
On the Confluence page
For pasted or imported data that is saved inline, the table data and its settings are stored with the macro on that page.
In the native table
For Simple Table with Body, the Confluence table on the page remains the source that editors work with.
As a page attachment
For larger datasets, or when you choose to save one, Simple Tables keeps the table data as an attachment on the same Confluence page.
What happens when a page is deleted?
Macro content and page attachments follow the lifecycle of their Confluence page. When a page is deleted, its Simple Tables content and attachments are removed with it. Any recovery period is governed by your Confluence recycle bin and retention settings.
What data residency means here
Simple Tables does not select a separate region or operate a separate store for your table content. The residency and retention controls for your Confluence site apply to the page content and attachments used by Simple Tables.
If you use a URL-based data source, that source system has its own data location and retention policies.
For a security or vendor review
Read the published details on no data egress, Runs on Atlassian, and platform architecture.
Want to try it in your site? InstallSimple Tables for Confluence from the Atlassian Marketplace.