Security and data location
Where your data is stored, how it is protected, and who processes it
AboutLast updated: October 15, 2026
This page says where Hub Nexus keeps your data, how it is protected, and which companies process it for us. It covers the public site and private workspaces alike.
Where your data is stored
- Everything you write, upload or set up on Hub Nexus — pages and every version of them, comments, workspaces, their members and settings — is stored in Amazon Web Services' US West (Oregon) region, us-west-2, in the United States. What Stripe holds for payments, and the messages that reach our own mailboxes at Google, are kept by those companies (below).
- The application that serves it runs in the same region.
- We do not copy your data to other regions, apart from the cached copies near readers described below, and we do not yet offer hosting in another region.
How it reaches readers
- Pictures, video and other files are delivered through Amazon CloudFront, which keeps cached copies at locations near readers around the world; a cached copy opens only with a valid signed link. Files are served only through signed links that expire within 24 hours, and a link is made only for someone who can open a page that uses the file, or for the person uploading it. A workspace's files are stored apart from everyone else's: knowing a file's name opens nothing in a workspace. Profile pictures and the site's own guide pictures are public.
- Search over public pages is built from public pages only. A private workspace's pages are never part of it.
- The site's pages pass through Amazon CloudFront as well, where AWS WAF turns away scanners and floods of requests before they reach our servers. Pages are never cached there: each one is fetched afresh, encrypted from the reader's browser to the edge and from the edge to our servers.
How it is protected
- Your data is encrypted in transit (HTTPS) and at rest (AES-256). The email we send travels over TLS whenever the receiving server offers it.
- The database can be restored to any moment in the last 35 days, and earlier versions of files are kept for 30 days.
- A single operator runs the service and reaches the production systems through their own AWS role. Hub Nexus's site administrators can open a workspace's pages, to give support or act on a report, and the workspace's audit log records it.
- Workspaces keep an audit log of who did what, which their administrators can export. Organisations can connect their own sign-in (SAML or OpenID Connect) and provisioning (SCIM), and can require approvals to be signed.
Companies that process data for us
These companies process data on our behalf. Each is bound by its own security and privacy commitments. For workspaces they are the subprocessors in our Data Processing Agreement, which says what each one receives.
- Amazon Web Services, Inc. — hosting, databases, file storage, checks and conversions of uploaded files, backups, logs, content delivery and sending email (United States, with cached copies of files near readers worldwide).
- Stripe, Inc. — payments for supporting pages, workspace plans and recognition budgets, and payouts: the payer's name, email address and payment details, and the amounts. Card details go to Stripe and never reach our servers (United States).
- Google LLC, through Google Workspace — our own mailboxes: messages people send us, including reports and feedback, and notices about email we send (may be stored outside the United States).
Compliance
We keep a readiness pack for SOC 2 — our policies, a map of our controls and the evidence behind them — and share it with organisations evaluating Hub Nexus. Hub Nexus has not yet been audited against SOC 2 or ISO 27001.
Reporting a security problem
If you find a security problem, write to support@hubnx.com. Please give us a chance to fix it before telling anyone else, and do not access data that is not yours.