# Data processing addendum

For PageCheck and PageCycle, BrainGrid's Runs on Atlassian apps for Confluence. App data is processed and stored only on Atlassian's platform.

Effective November 9, 2026 · BrainGrid AI, Inc. · https://atlassian.braingrid.ai/dpa

## Agreement and scope
This Data Processing Addendum ("Addendum") forms part of the [terms of service](https://atlassian.braingrid.ai/terms) or other written agreement for PageCheck and PageCycle ("Agreement") between BrainGrid AI, Inc. ("BrainGrid") and the organization that owns the Atlassian site where an app is installed ("Customer"). The "Services" are PageCheck and PageCycle, the Runs on Atlassian apps for Confluence Cloud installed from the Atlassian Marketplace.

This Addendum applies when the Services process personal data on Customer's behalf ("Customer Personal Data"). It takes effect when Customer accepts the Agreement that incorporates it. A person accepting for Customer must have authority to bind Customer. A separately signed copy is available from [hello@braingrid.ai](mailto:hello@braingrid.ai).

This Addendum covers app data, including personal data in page text, comments and Atlassian account ids. It does not cover BrainGrid's development planning platform. Licensing contacts, support requests, business email and website request logs that BrainGrid handles for its own purposes are described in the [privacy policy](https://atlassian.braingrid.ai/privacy), rather than this Addendum. Customer should not send app content to BrainGrid when requesting help.

## Roles and applicable law
"Data Protection Laws" means the privacy and data protection laws that apply to the processing under this Addendum, including the EU General Data Protection Regulation ("GDPR"), the UK GDPR and Data Protection Act 2018, the Swiss Federal Act on Data Protection, and the California Consumer Privacy Act as amended ("CCPA"), where applicable. "Controller", "processor", "data subject", "personal data", "processing" and "personal data breach" have the meanings given by the GDPR or the corresponding applicable law.

Customer acts as controller, or as processor for a controller whose instructions Customer is authorized to give. BrainGrid acts as processor or sub-processor for Customer. Customer is responsible for the lawfulness of the data it places in Confluence, the notices and legal bases required to process it, and the instructions it gives through the Services.

## Customer's instructions
BrainGrid will process Customer Personal Data only to provide the Services under the Agreement, this Addendum and Customer's documented instructions. Those instructions include installing and configuring the apps, choosing enabled spaces, using their features and tools, setting retention periods and uninstalling them. The processing details are in Schedule 1 below.

BrainGrid will not process Customer Personal Data for advertising, sell it, or use it to train AI models. PageCheck uses its own model to run AI checks inside Atlassian; Customer's pages are inputs to those checks, not training data.

If a law requires processing beyond Customer's instructions, BrainGrid will tell Customer before that processing unless the law prohibits notice. BrainGrid will promptly tell Customer if, in its opinion, an instruction infringes Data Protection Laws, and may suspend that instruction while the parties resolve it.

## Hosting, access and confidentiality
The Services process and store Customer Personal Data only on Atlassian's platform, using Forge and Confluence. They have no external domains, remote back ends or external analytics services. BrainGrid does not receive or store Customer Personal Data outside Atlassian, and BrainGrid personnel have no access to Customer's app storage or page content through the Services.

Stored app data follows Customer's Confluence site's data residency location through Atlassian's Forge storage and Confluence. Atlassian hosts the apps' compute under its Forge platform arrangements. This Addendum does not promise that every computation takes place in the site's storage region.

Customer controls the users who can access its site and any exports or connections it authorizes, including Rovo, MCP clients and PageCycle's REST API. The Services enforce the requesting user's Confluence permissions. Customer is responsible for personal data it exports or asks an external client to receive.

BrainGrid will ensure that any person it authorizes to process Customer Personal Data is bound by confidentiality obligations or a statutory duty of confidentiality, and has access only as needed to perform the authorized work. This obligation does not grant BrainGrid personnel access to Customer's site or app storage.

## Security
Taking into account the nature, scope, context and purposes of processing and the risks to individuals, BrainGrid will maintain appropriate technical and organizational measures under Article 32 GDPR and other applicable Data Protection Laws. Schedule 2 describes the measures for the Services. BrainGrid will regularly assess those measures and will not materially reduce their overall protection during the Agreement.

Atlassian provides the hosting platform's physical security, encryption, tenant isolation and infrastructure operations. BrainGrid is responsible for the app code, permissions, dependencies and handling of data within that platform. BrainGrid does not claim that it holds Atlassian's certifications.

## Sub-processors
Customer authorizes Atlassian as the Services' only sub-processor, as described in Schedule 3. BrainGrid will bind its sub-processor to written data protection obligations that provide the protection required by this Addendum and Data Protection Laws, and remains responsible to Customer for the sub-processor's performance of those obligations.

BrainGrid will give Customer at least 30 days' prior written notice at Customer's Notice Address under the Agreement before adding or replacing a sub-processor. Customer may object on reasonable data protection grounds during that period. The parties will work in good faith to resolve the objection. If they cannot resolve it before the proposed change, Customer may terminate the affected Service and receive a refund of prepaid fees for the unused period, administered through the Atlassian Marketplace. BrainGrid will not use the proposed sub-processor for that Customer's data before the objection is resolved or the affected Service is terminated.

Adding processing or storage outside Atlassian would change the Services described here and requires an amendment to this Addendum and Customer's documented authorization before it begins.

## Assistance and individual rights
Taking into account the nature of processing, BrainGrid will assist Customer through appropriate technical and organizational measures, insofar as possible, to meet requests for access, correction, deletion, restriction, portability and objection. BrainGrid will promptly forward a request it receives about Customer Personal Data to Customer and will not answer it except on Customer's instructions or as the law requires.

App data lives in Customer's Atlassian site. Customer's site admins handle requests using Confluence and the apps' controls, with BrainGrid's assistance. Both apps report stored Atlassian account ids to Atlassian's personal data reporting API every week. When Atlassian reports an account as closed, PageCheck removes its account id, and PageCycle replaces its account id in app storage with a former user marker. These reports do not replace Customer's responsibility to handle other personal data in page text or comments.

BrainGrid will assist Customer with security obligations, breach notifications, data protection impact assessments and prior consultation with a supervisory authority, taking into account the nature of processing and the information available to BrainGrid. Contact [hello@braingrid.ai](mailto:hello@braingrid.ai) for assistance.

## Personal data breaches
BrainGrid will notify Customer at its Notice Address without undue delay after becoming aware of a personal data breach affecting Customer Personal Data. As information becomes available, the notice will describe the nature of the breach, the affected data and individuals, the likely consequences, the measures taken or proposed, and a contact for further information. BrainGrid may provide the information in stages and will cooperate with Customer to contain, investigate and address the breach.

Customer is responsible for notices to individuals and authorities unless the law requires BrainGrid to give them. A notification does not by itself admit fault or liability. Security reports go to [security@braingrid.ai](mailto:security@braingrid.ai), as the [vulnerability disclosure policy](https://atlassian.braingrid.ai/docs/security/disclosure) describes.

## Retention, return and deletion
Customer may retrieve data using the Services' available views and exports and Confluence's tools while the app remains installed. BrainGrid will assist Customer with return or deletion requests, including where those tools do not meet the request. Customer should request any needed return before uninstalling, because BrainGrid cannot read or recover app storage itself.

At the end of the Services, BrainGrid will, at Customer's choice, return or delete Customer Personal Data and delete existing copies, unless applicable law requires retention. Uninstalling an app initiates deletion of its Forge storage by Atlassian. Atlassian first makes that storage unavailable to the app and retains a recoverable copy for its platform retention period before final deletion; reinstalling alone does not restore that data. During that period the retained data remains protected under this Addendum and is processed only for recovery, security or legal obligations. BrainGrid will assist Customer with a request to Atlassian about recovery or final deletion, and provide available confirmation on request.

Data PageCycle writes to Confluence, such as page statuses, properties, comments and labels, and PageCheck's space settings property remain Customer's Confluence data after uninstall. Customer manages their retention and deletion through Confluence. Schedule 1 lists the apps' retention periods during use.

## International transfers
BrainGrid does not transfer Customer Personal Data to its own systems or to another provider outside Atlassian's hosting. Stored app data follows Customer's site's data residency location; Atlassian's platform processing is governed by the applicable Atlassian arrangements. A storage location alone does not determine whether Data Protection Laws treat an arrangement as an international transfer.

If processing under this Addendum requires a restricted transfer under EU, UK or Swiss law, the parties will put the required lawful transfer mechanism in place before that transfer, including applicable standard contractual clauses or a UK addendum where required. This Addendum does not itself incorporate standard contractual clauses. Neither party may treat it as authorization for an otherwise unlawful transfer.

## Information and audits
BrainGrid will make available the information necessary to demonstrate compliance with this Addendum and will allow and contribute to audits, including inspections, by Customer or an independent auditor Customer appoints, as Data Protection Laws require. The parties will coordinate reasonable notice, scope, timing and confidentiality to protect other customers and the security of the Services. These arrangements will not prevent an audit required by law or a supervisory authority.

BrainGrid will first provide available documentation and answers about its controls and Atlassian's platform. An audit does not grant access to another customer's data or a right to inspect Atlassian facilities beyond rights available under Atlassian's arrangements. If that information is insufficient, the parties will cooperate to meet the applicable legal requirement.

## California personal information
Where the CCPA applies, BrainGrid acts as Customer's service provider or contractor for the business purposes in Schedule 1. BrainGrid will not sell or share Customer Personal Data, retain, use or disclose it outside those purposes or the direct business relationship with Customer, or combine it with personal information from other sources except as the CCPA permits. BrainGrid will comply with the applicable CCPA obligations and provide the same level of privacy protection the CCPA requires.

Customer may take reasonable steps to check that BrainGrid uses the data consistently with those obligations, and to stop and remedy unauthorized use. BrainGrid will notify Customer if it can no longer meet those obligations. BrainGrid certifies that it understands and will comply with these restrictions.

## Precedence, duration and contact
This Addendum controls over the Agreement on the processing of Customer Personal Data. Mandatory Data Protection Laws and any applicable transfer clauses control where they require different terms. The Agreement's liability limits apply to this Addendum to the extent the law permits. This Addendum remains in effect for as long as Customer Personal Data is processed under it.

Changes follow the Agreement's notice and effective date provisions and must comply with Data Protection Laws. Requests for this Addendum, a signed copy or earlier versions go to BrainGrid AI, Inc., [hello@braingrid.ai](mailto:hello@braingrid.ai).

## Schedule 1: Processing details
| Item | Details |
|---|---|
| Subject matter and purpose | Providing PageCheck's AI checks and PageCycle's page workflows, review dates, automations and History for Customer's Confluence site |
| Nature and frequency | Reading, analyzing, organizing, storing, retrieving, displaying, updating, exporting at Customer's request and deleting app data as users, admins and scheduled app jobs use the Services |
| Duration | While Customer uses the Services, followed by return or deletion and Atlassian's platform retention period as described above |
| Data subjects | Customer's users, employees, contractors and other people whose personal data Customer includes in the pages and comments the apps process |
| Types of personal data | Atlassian account ids; personal data Customer includes in published page text, headings and move comments; page, space and version ids, timestamps, statuses, review dates, AI check results and operational records where linked to a person |
| Sensitive data | The Services do not require special categories of personal data. Customer controls page and comment content and must establish any additional legal basis and safeguards required for sensitive data it includes |
| Customer's rights and obligations | Customer determines purposes, lawful instructions, enabled spaces, authorized users and available retention settings, and may request information, assistance, return and deletion under this Addendum |

**PageCheck.** Only published pages in spaces a Confluence admin enables are checked. Page text and passages are processed by PageCheck's own model inside Atlassian. The newest two checked versions of each page retain their text and passages; deleting a page removes its stored text. Results and requester account ids remain until uninstall, with closed account ids removed through personal data reporting. The monthly active-user count is a sketch of small numbers, not a list of users; its random monthly key is deleted shortly after the month ends. PageCheck writes no page content or page properties.

**PageCycle.** The app stores space settings, workflows, review dates, page statuses, body fingerprints, History, pending moves, automation records and admin-confirmed tool changes in Forge SQL. A page body is read to compute its fingerprint and is not saved. History includes the account id of the person behind a move and any move comment. Space admins choose 30 days, 90 days, 1 year or 3 years of History, with 3 years as the default; older History is deleted weekly. Health problems and tool-change records are kept 30 days; automation run records are kept 90 days. Other app records remain while needed to provide the Services, until removed through the app's controls or uninstall.

## Schedule 2: Security measures
| Measure | How it applies |
|---|---|
| Hosting and egress controls | Runs on Atlassian: Atlassian-hosted compute and storage, no external domains, remote back ends or external analytics services |
| Encryption and isolation | Atlassian's Forge and Confluence platform encryption in transit and at rest, and storage isolated per installation |
| Access control | Confluence permissions enforced for the requesting user; app views, tools and exports limited to pages that user can view; settings changes limited to authorized admins |
| Data minimization | Only data needed for the documented features; no app content in operational logs; no use of Customer Personal Data for model training |
| Retention controls | PageCheck's two-version text retention and page-deletion handling; PageCycle's configurable History retention; weekly account reporting and closed-account handling |
| Secure development | Code review, permission and isolation tests, dependency checks, secret scanning and release gates; restricted access to code and developer accounts |
| Incident handling | Security contact, vulnerability disclosure policy, incident investigation and customer notification procedures |
| Availability and recovery | Atlassian operates the hosting platform and its recovery controls; BrainGrid maintains app source and release procedures and assists with platform recovery requests |

## Schedule 3: Authorized sub-processor
| Sub-processor | Service and data | Location |
|---|---|---|
| Atlassian | Forge app hosting, compute, SQL storage and personal data reporting, and Confluence data storage and APIs, for the Customer Personal Data in Schedule 1 | Stored app data follows Customer's Confluence site's data residency location; compute and platform operations follow Atlassian's Forge hosting arrangements |

Atlassian is the only sub-processor BrainGrid appoints for the Services. Atlassian's own infrastructure suppliers are governed by its platform arrangements. BrainGrid appoints no separate AI provider, database host or analytics provider for either app.
