Skip to main content
Hebno hosts your organisation’s data in one region, the EU or the US. You choose it once, when the workspace is created, so you can tell a client exactly where their material is stored.

Choose a region

The choice is the Data residency step in onboarding, which the person creating the workspace completes. Choose the region that matches your clients’ requirements: firms with EU clients or EU compliance obligations usually choose the EU.
  • The choice applies to the whole organisation.
  • It cannot be changed afterwards.
  • Every member of the organisation shares it.
Residency is fixed when the organisation is created. If you need a different region, create a new organisation in that region. Ask support before you do, so you know what moves and what does not.

What residency applies to

Residency applies to the data Hebno stores for your organisation:
  • Conversations, including the excerpts a reply used from connected systems.
  • Files members upload, and deliverables saved to projects.
  • The library, project instructions and organisation context.
  • Admin records, including logs and spend history.
Connection tokens are stored encrypted in the same region.

What residency does not apply to

Residency governs where Hebno stores your data. It does not move data that is in your other systems.
  • Files, mail and records in Microsoft 365, Google Workspace, your CRM or finance system remain where those systems store them. Hebno reads them live.
  • Files saved from Hebno to a linked folder, such as SharePoint or Google Drive, are stored by that service in its own region.
  • Model providers, database hosts and connected services act as subprocessors. The data processing agreement lists them and where they operate.

Documents to share with a client

Your signed agreement governs contractual terms. Use Data handling for what is stored and how it is deleted.

Common questions

Yes. Ask support to confirm it, or check your signed agreement.
Yes. Region is a property of the organisation, not of a member.
No. Model access is controlled in Models, not by region.

Next steps