S
Simpleasyty
Help Center — No data egress
GETTING STARTED
IntroductionInstall the appQuick startRuns on Atlassian
SIMPLE TABLE
PasteAttachmentsFile uploadJoin tablesPage PropertiesConfluence ContentJira Issues
TABLE WITH BODY
Native Confluence tables
DATA STORAGE
Data residencyNo data egressSave table data
REUSE TABLES
Table Excerpt / Include
DISPLAY
SearchFiltersSortingGroupingRow numbersFull screen modeDownload tableConfidential labelRovo
COLUMNS
ReorderingRename headingHideIncognito modeText appearanceColumn colorsData typeGrouping aggregationFooter aggregationCalculated columnExpression functionsNested JSON fieldsDelete column
PIVOT TABLES
Overview
FORMATTING
Layout & spacingTable colorsTable heightPagination

No Data Egress

Simple Tables is implemented on Atlassian Forge. In standard table workflows, table content is processed and retained within Atlassian’s Confluence and Forge services; Simpleasyty does not operate an external application backend for that content.

DATA STORAGE

This establishes a defined and reviewable data boundary. Confluence permissions, data residency, and retention controls continue to govern the table content throughout its lifecycle.

Why it matters

For information security, privacy, and procurement reviews, a defined data flow is essential. Creating, displaying, filtering, and updating a table do not require a separate Simpleasyty service or an external data platform. Forge denies undeclared external connections by default, so any permitted external destination is visible in the app manifest and subject to review.

CORE GUARANTEES

How it works

The core product is designed around these boundaries, so teams can work with table data in Confluence with clear, documented safeguards.

Processing stays in Atlassian

Table content is read from and written back to Confluence, including macro configuration, native tables, and page attachments selected as a data source.

No external data flow

The core table service runs on Atlassian Forge and uses Atlassian APIs and platform storage, rather than a Simpleasyty-hosted processing or storage backend.

Explicit domain controls

Forge requires each external destination to be declared in the app manifest, providing an auditable record of the permitted boundary.

Data retained within Atlassian

The following content is not transmitted to an external service as part of the standard table workflow:

  • Table values, headers, calculated results, filters, and display settings.
  • Contents of CSV, JSON, and Excel files attached to or uploaded for a Confluence page.
  • Native Confluence table content, including the rich content that Simple Table with Body reads from the page.

Editor-configured external sources

A URL-based table source is governed separately. Where an editor explicitly configures a URL, Simple Tables reads data from that selected system. The source system’s location, access controls, and retention policy remain applicable. This is an intentional, editor-configured connection; it is not a transfer of Confluence table content to a Simpleasyty service.

Evidence for enterprise review

Atlassian’s Runs on Atlassian program assesses whether a Forge app uses Atlassian-hosted compute and storage, supports aligned data residency, and controls external egress. Administrators can review the app permissions in Marketplace, while the app team can run Forge’s eligibility check for each deployed version.

Review Atlassian’s Runs on Atlassian requirements

READY FOR YOUR FIRST TABLE?

Make your Confluence data genuinely useful.

Install Simple Tables and build your first interactive table directly inside Confluence.

View on Atlassian Marketplace