跳到正文
Hub Nexus

数据处理协议

Hub Nexus 如何为企业处理其工作区中的个人数据,含欧盟和英国的数据传输条款。

关于 Hub Nexus

本协议仅有英文版本。

Last updated: October 15, 2026

This Data Processing Agreement ("DPA") is between HubNX, Inc. ("Hub Nexus", the Provider) and the Customer under the Hub Nexus Workspace Terms (the Agreement), as the Agreement defines it. It applies whenever Hub Nexus processes personal data for the Customer through a Hub Nexus workspace. The Customer accepts it, with the Agreement, when a workspace is created for it, when it starts or changes a workspace plan, or when it signs an Order Form that refers to it — no separate signature is needed. A Customer that wants a countersigned copy can ask at legal@hubnx.com.

The DPA has two parts: (1) this Cover Page, and (2) the Common Paper Data Processing Agreement Standard Terms, Version 1.1, which are incorporated by reference. If they disagree, the order is the one the Standard Terms set: the EEA SCCs or UK Addendum, then this DPA (this Cover Page over the Standard Terms), then the Agreement.


Cover Page

Agreementthe Hub Nexus Workspace Terms between the Customer and Hub Nexus, in the version the Customer accepted and as changed under their item 8
Approved SubprocessorsAmazon Web Services, Inc., 410 Terry Avenue North, Seattle, WA 98109, USA — runs the Service: application servers, databases, file storage, checks and conversions of uploaded files, backups, logs and outgoing email; United States (US West (Oregon), us-west-2). Files are also cached at AWS CloudFront edge locations around the world, near the person opening them; a cached copy opens only with a valid signed link. · Stripe, Inc., 354 Oyster Point Boulevard, South San Francisco, CA 94080, USA — payments for workspace plans and recognition budgets, and payouts of budgets to members' own Stripe accounts: the payer's name, email address and payment details (card details go to Stripe directly), the workspace's name on a budget payment, Hub Nexus's ids for the payer, the workspace and each member paid, the number of billed members, and amounts; United States. · Google LLC (Google Workspace), 1600 Amphitheatre Parkway, Mountain View, CA 94043, USA — Hub Nexus's own mailboxes: messages people send to Hub Nexus, including reports about a workspace page or comment (its title and an excerpt, the reason and the reporter's address) and feedback (the message, the page's address and the sender's address), and notices about email Hub Nexus sends (a bounced address); may be stored outside the United States. These are the Approved Subprocessors, as changed under Section 2.6; the current list, with each one's location and task, is also at hubnx.com/about/security. Hub Nexus will email the workspace's owner and administrators at least 30 days before it adds or replaces a Subprocessor, naming it, its location and its task; that email is the notice Section 2.6(a) of the Standard Terms and Clause 9 of the EEA SCCs require, and its 30 days replace the 10 business days in Sections 2.6(a) and 3.2(c)(ii) of the Standard Terms
Provider Security Contactsupport@hubnx.com — security reports, questionnaires and audit requests; questions and complaints about personal data: legal@hubnx.com, answered by the founder
Security Policyas defined in the Agreement; Annex II lists the measures Hub Nexus maintains at least
Service Provider RelationshipTo the extent the California Consumer Privacy Act, as amended, and its regulations ("CCPA") apply, Hub Nexus is the Customer's service provider. The Customer discloses personal information to Hub Nexus only for the limited and specified business purposes in Annex I(B) (Nature and Purpose of Processing). Hub Nexus will not: (a) sell or share it; (b) retain, use or disclose it for any purpose other than those business purposes, except as Changes to the Standard Terms, item 3 describes or as the CCPA otherwise permits; (c) retain, use or disclose it outside its direct business relationship with the Customer; or (d) combine it with personal information it receives from anyone else or collects from its own dealings with a person, except as needed to provide the Service to the Customer or as the CCPA permits. Hub Nexus will comply with the CCPA and give the personal information the level of privacy protection the CCPA requires of businesses; will help the Customer answer consumers' requests as Section 6 of the Standard Terms provides; and will notify the Customer if it determines that it can no longer meet its obligations under the CCPA. The Customer may take reasonable and appropriate steps to ensure Hub Nexus uses the personal information consistently with the Customer's CCPA obligations — through the information and audits in Section 5, as changed below — and, on notice, to stop and remediate any unauthorized use. Hub Nexus certifies that it understands these restrictions and will comply with them
Other US state privacy lawswhere a US state privacy law other than the CCPA applies, Hub Nexus is the Customer's processor under it, and this DPA's terms on instructions, confidentiality, assistance, deletion and return, information and audits, and Subprocessors are the contract that law requires
Governing Member StateEEA transfers: Ireland. UK transfers: England and Wales

Changes to the Standard Terms

  1. Audits and security reports. Hub Nexus has not been audited by an independent third party and has no Report to give. Until it has one: (a) Section 5.2 (Security Reports) of the Standard Terms is replaced with this: on the Customer's written request, Hub Nexus will give the Customer, in confidence, its security readiness pack (policies, control map and latest evidence report), its record of the processing it carries out for the Customer, and a completed security questionnaire, and will tell the Customer when a Report becomes available. Section 5.3 (Security Due Diligence) applies unchanged. (b) Despite the sentence of Section 5.1 that limits how the Customer exercises its audit rights: if what Hub Nexus gives under Sections 5.2 and 5.3 does not reasonably show that it complies with this DPA, after a Security Incident, or when a supervisory authority asks, the Customer may audit Hub Nexus's compliance with this DPA itself or through an independent auditor who is bound to confidentiality and does not compete with Hub Nexus. The Customer gives at least 30 days' written notice (less after a Security Incident or at a supervisory authority's request), audits no more than once in any 12 months otherwise, and pays its own costs. The audit reviews documents, records and evidence from Hub Nexus's systems, with interviews, normally remotely; it does not extend to the facilities of Hub Nexus's Subprocessors, whose own audit reports Hub Nexus will help the Customer obtain.
  2. No AI on Customer Personal Data. Hub Nexus will not use Customer Personal Data to develop, train or improve any artificial intelligence or machine learning model, and will not give it to any generative AI or large language model service — including for support or debugging, and including the AI tools its personnel use to build and run the Service, which are not used on Customer Personal Data, and which the Service's own database client refuses a workspace's pages and settings in production. This item does not cover the spam, fraud and security screening that Approved Subprocessors apply, under their own terms, to email and payments.
  3. Return and deletion. Section 7 of the Standard Terms applies with these changes, and the words "impracticable or" in Section 7.2(a) do not apply. (a) Return. Hub Nexus returns Customer Personal Data with the Workspace Content, as item 4 of the Agreement's Changes to the Standard Terms provides; that is the return Section 7.2(a) of the Standard Terms and Clause 8.5 of the EEA SCCs refer to. (b) During the Agreement. Deleting a page, change, comment or file removes at once the records that name it; the stored text or file itself is erased with the workspace. (c) Deleting a workspace — by its owner, or by Hub Nexus on request or after the Agreement ends, as item 5 of the Agreement's Changes to the Standard Terms says — erases every page in every state with all its versions, changes, comments, votes and signatures; its stored texts and files; its members, groups, invitations, read links and page grants; its single sign-on and SCIM set-up and verified domains; notifications and reports about its pages; and its name. (d) What remains for a limited time. Database backups for up to 35 days and earlier versions of stored files for up to 30 days, kept encrypted and used only to recover the Service after a failure — anything a recovery brings back that had been deleted is deleted again; application logs that name people, for up to 30 days; and messages people sent Hub Nexus about the workspace (support, reports, feedback): the copies in the Service for up to 90 days, the emails in Hub Nexus's mailboxes until the Customer asks for them to be deleted. Copies cached at content-delivery edge locations are invalidated when the workspace is deleted. (e) What Hub Nexus keeps. The workspace's audit log, for 12 months after deletion, to answer the Customer's questions about the workspace — including who deleted it — and then erased; earlier, on the Customer's written request once it has its copy. It holds ids, actions and times, never page text or email addresses. Records of payments into and out of a recognition budget, as Hub Nexus's own financial records, for as long as tax and accounting law requires. A version published to the public site, which is public content (Agreement, Changes to the Standard Terms, item 3). People's own accounts, as item 4 says. (f) On request, Hub Nexus confirms in writing what it deleted and what it kept under (d) and (e).
  4. Roles, and what is Customer Personal Data. Customer Personal Data includes the personal data in Workspace Content; what the Service holds about people because of the Customer's workspaces — membership, roles, groups, invitations, page grants and read links, votes, signatures, notifications about workspace pages, and what the Customer's identity provider sends by single sign-on or SCIM; the workspaces' audit logs; and Usage Data that identifies a person, which Hub Nexus uses only to provide, secure and support the Service. Hub Nexus is a separate controller, under its Privacy Policy and not under this DPA, for each person's own Hub Nexus account once they have signed in — their sign-in address, name, picture and profile, and what they do on the public site — for its billing and payment records, and for any version a member publishes to the public site, from the moment it is published. An account Hub Nexus creates only because the Customer invited, shared a page with or provisioned an address is Customer Personal Data until that person signs in, and Hub Nexus deletes it if what created it — the invitation, the grant or the provisioning — ends before they do. Deleting a workspace does not delete the accounts of people who have signed in; each can delete their own at any time. Each account has a public profile page showing its name, picture and anything its owner adds to the profile.
  5. Hub Nexus's personnel and their access. Hub Nexus gives access to Customer Personal Data only to personnel who need it to run, secure and support the Service and who have committed in writing to keep it confidential. Its site administrators can open any workspace page, hide a page and remove a comment. They do so only to give support the Customer asked for, to act on a report of abuse or of a security problem, or where Applicable Laws require it, and the workspace's audit log records each administrator's first opening of the workspace each day and every comment removed, and every page hidden. Hub Nexus's operator administers the infrastructure through an AWS role; that access can reach all stored data and is recorded only in AWS's 90-day history of management actions.
  6. Security Incidents. Section 4 of the Standard Terms applies to every Security Incident as the Agreement defines it (Workspace Terms, Changes to the Standard Terms, item 6), with these additions. Hub Nexus sends its notice by email to the Customer's Notice Address, the workspace's owner and administrators, and any security contact the Customer names in writing — sooner than 72 hours where a law that applies to Hub Nexus requires it. The notice gives, as far as known at the time: what happened and when; the workspaces, kinds of data and approximate numbers of people and records affected; the likely consequences; what Hub Nexus has done and will do; what the Customer should do; and whom to contact. Hub Nexus will help the Customer notify supervisory authorities and the people affected.
  7. Helping with people's requests. Under Section 6.1 of the Standard Terms, Hub Nexus helps the Customer answer people who exercise their data protection rights. The workspace's administrators can themselves find, change and remove its pages, comments and members, and download its audit log. Within 30 days of the Customer's written request, Hub Nexus exports a person's content and activity in a workspace, and corrects or erases, as the Customer instructs and as far as item 3 allows, personal data the Service gives the Customer no way to change itself — in an earlier version of a page, for example — and confirms it in writing.
  8. Instructions. Where the GDPR or the UK GDPR applies, "Applicable Laws" in Sections 2.2 and 7 of the Standard Terms means the law of the European Union, an EEA member state or the United Kingdom; a demand made under any other law is handled under Section 6.1 of the Standard Terms and Clauses 14 and 15 of the EEA SCCs. Hub Nexus will tell the Customer at once if, in its opinion, an instruction breaks the GDPR or another data protection law.
  9. Objecting to a new Subprocessor. If the Customer objects to a new Subprocessor on reasonable data protection grounds within 30 days of the notice, and the parties cannot resolve the objection within 30 days after it, the Customer may end the Agreement by notice and receive a prorated refund of prepaid Fees.
  10. Swiss transfers. Where the Swiss Federal Act on Data Protection (FADP) governs a transfer, Section 3.4 of the Standard Terms applies with these additions: references to the GDPR anywhere in the EEA SCCs are to the FADP, to the extent the FADP governs the transfer; the Swiss Federal Data Protection and Information Commissioner is the competent supervisory authority for it; and "Member State" in Clause 18(c) of the EEA SCCs does not prevent data subjects in Switzerland from suing for their rights in Switzerland, where they habitually reside.
  11. Versions of this DPA. This DPA carries a version date. A new version applies to the Customer only as item 8 of the Agreement's Changes to the Standard Terms allows; it never changes the EEA SCCs or the UK Addendum and never lowers the protection of Customer Personal Data already received. Earlier versions stay available at hubnx.com/about/dpa.

Annex I(A) — List of Parties

Data exporterData importer
Namethe Customer, as named in its Order Form, billing details or acceptanceHubNX, Inc. (Hub Nexus)
Addressthe address in the Customer's Order Form or billing details, or given on requestgiven on request; notices by email to legal@hubnx.com
Contactthe workspace's owner, and any data protection officer or EU or UK representative the Customer names in writingthe founder, responsible for data protection — legal@hubnx.com
Activitiessee Annex I(B)see Annex I(B)
Signature and dateaccepted electronically on the Order Dateaccepted electronically on the Order Date
RoleController (or Processor, where the Customer processes the data for someone else)Processor (or Subprocessor)

Annex I(B) — Description of Transfer and Processing



ServiceHub Nexus Workspaces
Categories of Data Subjectsthe Customer's owner, administrators, members and guests, including people it has invited who have not joined and people its identity provider provisions; people outside the Customer it shares a page with by name, and people who open its read links (anonymous to Hub Nexus); members paid from a recognition budget; people named or shown in Workspace Content, including in pictures and recordings
Categories of Personal Datanames and sign-in email addresses, and profile pictures as the workspace shows them; what the Customer's identity provider sends (single sign-on subject and email; SCIM user name, external id and names); roles, groups, invitations, page grants and read links; Workspace Content and any personal data in it — pages and every version, comments and review reasons, files, including recordings of voice and image; review records — votes, approvals and signatures (name as signed, meaning, time and method); activity — the actions the audit log records (as ids, never page text or addresses), sign-ins through single sign-on, notifications, and likes and follows on workspace pages; for members paid from a recognition budget, their Stripe payout account and the amounts; for requests made while signed out, the IP address, kept only as a rate-limit counter for about two hours; ids and, in some error messages, an email address in application logs, kept 30 days
Special Category Datanone intended: the Customer agrees not to submit special categories of personal data (Article 9 GDPR; Agreement, Changes to the Standard Terms, item 7) or data about criminal convictions and offences (Article 10 GDPR). The Service cannot detect such data; if any is submitted, the measures in Annex II apply to it
Frequency of Transfercontinuous, while the Customer uses the Service
Nature and Purpose of Processingto provide the Service the Customer uses, as instructed in Section 2.2 (Processing Instructions) of the Standard Terms: receiving data as members write, upload and are provisioned; storing and organizing it, with versions and backups; checking every upload, making smaller copies of pictures and converting Office files to PDF; controlling access to it and encrypting it; delivering it only to the people the Customer's members choose — members and guests, people a page is shared with by name, holders of a read link, the Customer's identity provider through single sign-on and SCIM, and the public site for versions a member publishes — and in the Service's emails to them (invitations, notifications, sign-in and signing codes, whose subjects can carry workspace names and page titles); limiting request rates and preventing abuse; billing, and paying out recognition budgets; support, and acting on reports about workspace content (Changes to the Standard Terms, item 5); returning it (export); and erasing it (item 3)
Retentionfor the Agreement, then as Changes to the Standard Terms, item 3 sets out
Duration of Processingfor as long as needed to perform the processing instructed in Sections 2.2(a)–(d) of the Standard Terms, or as required by applicable law

Annex I(C) — Competent Supervisory Authority

The supervisory authority of the data exporter, as determined by Clause 13 of the EEA SCCs or the relevant provision of the UK Addendum.

Annex II — Technical and Organizational Measures

The measures Hub Nexus maintains at least, for all Customer Personal Data (the Agreement's Security Policy):

MeasureWhat Hub Nexus does
Encryption at restdatabases, stored files and backups encrypted with AES-256, with keys managed by AWS
Encryption in transitHTTPS with TLS 1.2 or later on hubnx.com and media.hubnx.com (TLS 1.0 and 1.1 refused); HSTS on the site; email sent over TLS whenever the receiving server supports it
Separation of customerseach workspace's texts and files are stored under that workspace's own prefix and signed only for people who can open the workspace
Access to Workspace Contentthe workspace's members and guests, the people it shares a page with by name, and anyone holding a read link it made (for 1, 7 or 30 days); every request that names a page, change, comment or collection checks that access first; files open only through signed links that expire within 24 hours; workspace pages never enter the public search, feeds or sitemap. Removing a person, by hand or through SCIM, ends their access on their next request, though a file link already signed works until it expires. Hub Nexus's personnel: Changes to the Standard Terms, item 5
Identification and authenticationa one-time code emailed for each sign-in, or the workspace's own single sign-on (OpenID Connect or SAML 2.0), which it can require for its verified domains; no passwords; SCIM provisioning and deprovisioning. A session lasts 30 days from the last visit and cannot yet be ended early, so turning a person off at the identity provider ends their access only once SCIM or an administrator removes them from the workspace. Approving with a signature takes a code emailed at that moment or a fresh sign-in through the workspace's single sign-on
Hub Nexus's own accessone person operates the Service; production is reached only through an AWS role; secrets are kept in AWS Systems Manager; the computer used to operate the Service locks its screen when idle and holds Workspace Content only while sending an export the Customer asked for, deleting it once received; personnel are bound in writing to confidentiality; the AI tools used to build and run the Service are not used on it, and the Service's own database client refuses them a workspace's pages and settings in production
Event loggingthe workspace's audit log records membership and roles, single sign-on and SCIM events, settings, groups and approvers, pages created and moved, every review step and signature, read links and page grants, budget and plan events, deletion, comments removed and pages hidden by Hub Nexus, and each Hub Nexus site administrator's first opening of the workspace each day. The Service only adds to it; administrators can read it and download it as CSV. It does not record reads, downloads, read-link visits or exports. A line that cannot be written is logged for the operator. Application errors are logged with ids and kept 30 days
Availability and recoverypoint-in-time recovery of the databases for 35 days; earlier versions of stored files kept 30 days; deletion protection on the tables; a restore rehearsed every quarter; one AWS region (us-west-2), with no copy in another
Testingunit tests, and an isolation check — 56 requests as outsiders, members, removed members and signed-out visitors against a development server — that the operator runs before releasing changes to workspace access (not yet enforced by the build); dependency vulnerability scans, with high-severity fixes within 30 days. No independent penetration test yet (Changes to the Standard Terms, item 1)
Development and test datadevelopment copies of the database leave out every workspace and every account that exists only through a workspace, and replace sign-in addresses
Data minimizationno analytics, advertising or tracking; no third-party code in readers' browsers; the audit log keeps ids, never names, addresses or content
Helping with people's requestsadministrators can find, change and remove pages, comments and members themselves and download the audit log; Hub Nexus helps with the rest as Section 6.1 of the Standard Terms and Changes to the Standard Terms, item 7 say
Retention, portability and erasureexport: the Agreement's Changes to the Standard Terms, item 4; retention and deletion: Changes to the Standard Terms, item 3
Subprocessorseach bound by its own data processing terms and reviewed yearly; each publishes independent audit reports
Accountabilityevery change to the Service is a commit, deployed from one history; a record of the processing carried out for customers is kept current; security problems can be reported to support@hubnx.com

Annex III — Subprocessors

The Approved Subprocessors listed on the Cover Page.


Common Paper Data Processing Agreement (Version 1.1) free to use under CC BY 4.0. The Standard Terms are © Common Paper, Inc. This Cover Page was written by HubNX, Inc. from the Common Paper Data Processing Agreement Cover Page and changes the Standard Terms as stated above; Common Paper does not endorse it.