Global App, local compliance.

Whiteboards data residency gives you control over where your “in-scope” data is hosted.
We serve Whiteboards from the Google Cloud Platform. Depending on the deployment option you use, your data can be stored in one of the provided locations.

Deployments & Locations

Whiteboards for Jira and Confluence Cloud

Whiteboards for Jira and Confluence DC & Server &

product data: EU - Belgium,
attachments: EU Multi-regional

product data: EU - Belgium,
attachments: EU Multi-regional

product data: US - Iowa,
attachments: US Multi-regional

product data: US - Iowa,
attachments: US Multi-regional

product data: APAC - Singapore,
attachments: ASIA Multi-regional

*List of multiple data centers in certain regions are available here.




We always strive for the highest standards to help your organization stay safe and compliant.For us, data residency is key so whenever your business is you can be sure your data is with you.We give organizations more control over their data by ensuring their user-generated content is stored within the selected location.

In-scope And Out-of-Scope Data

The table below in-scope product data types and out-of-scope product data.

In-scope Product Data

Out-of-scope Product Data

  • All your custom templates, your board data, cards, lines, attachments, text, diagrams, images and all other objects you add to the board.

  • All your integrations configurations (GitHub, Jira, Confluence).

  • Backups of all the above.

  • Logs, audit product, and operational : Logs used for operational maintenance and diagnostic purposes as well as logs generated by changes related to content and configuration.

  • License data : Data provided for licensing purposes

  • Atlassian Marketplace App integration : Atlassian Connect provided configuration

  • Data in transit : Data being processed, but not stored by Whiteboards services

  • Cached content : Content stored in a non-specified region for up to 30 days with the purpose of content migration to a nominated location, or temporary storage of transactional content, such as emails, until delivery has been confirmed or abandoned.

  • Product analytics : Events collected by Whiteboards for in-product user experience optimisation and performance.

  • User analytics: Events collected by Whiteboards to help understand experiences based on user interactions.

  • User Account Data: because our users are global and can be a member of a multiple whiteboard organisations, we store the following user account data globally:

For all deployment options (Whiteboards for Jira, Whiteboards for Confluence,

  • access tokens

For only

  • First Name

  • Last Name

  • User survey data (questions asked during the signup process, for example: your role, preferred use, etc.)

  • No labels

This page has no comments.