Data Processing Agreement
This page is the Cover Page of the data processing agreement (DPA) between Nordika Apps and each customer of SOP Training & Attestation for Confluence. It incorporates the Common Paper DPA Standard Terms, Version 1.1.
How this DPA applies
- The agreement it supplements. The App is offered on the Atlassian Marketplace under the Bonterms Standard End User Agreement (Version 1.0). This DPA applies when the App's Provider-Specific Terms identify it under Section 3.3 (DPA) of that agreement.
- Acceptance. Customer accepts this DPA together with the Agreement when it first enters into an Order for the App. No signature is needed. This DPA also applies, on the same terms, while Customer uses the App's free tier or a trial.
- Standard Terms. This Cover Page incorporates by reference the Common Paper DPA Standard Terms, Version 1.1 (the "Standard Terms"), with the single change described below. Capitalized terms that are not defined on this page have the meanings given in the Standard Terms.
- Signed copy. If Customer needs a signed copy of this DPA, write to support@nordikaapps.com.
Key terms
| Term | Value |
|---|---|
| Provider | Er Navas Maldonado, an individual in Mexico, doing business as Nordika Apps. Notice address: support@nordikaapps.com. |
| Customer | The organization that enters into an Order for the App (the party placing the Order under the Agreement). |
| Agreement | The Bonterms Standard End User Agreement (Version 1.0), with the App's Provider-Specific Terms, between Provider and Customer, entered into through the Atlassian Marketplace. |
| Service | As described in the Agreement: SOP Training & Attestation for Confluence (the "App"), an app for Confluence Cloud that runs on Atlassian Forge, and its support. |
| Approved Subprocessors | The subprocessors listed under Approved Subprocessors (Annex III). |
| Provider Security Contact | support@nordikaapps.com |
| Security Policy | The technical and organizational measures in Annex II. Provider has no third-party certification (such as ISO/IEC 27001 or SOC 2) and no third-party audit report. |
| Governing Member State | Ireland |
Change to the Standard Terms
Section 5.2 (Security Reports) of the Standard Terms says that Provider is regularly audited by independent third-party auditors. That is not the case: Provider has no Report. Section 5.2 is therefore replaced with the following text, which prevails over the Standard Terms:
"5.2 Security Reports. Provider is not audited by independent third-party auditors and has no Report. Customer may verify Provider's compliance through the information described in Section 5.1 and the responses described in Section 5.3. In addition, once a year, or after a Security Incident, Customer may audit Provider's compliance with this DPA by examining Provider's relevant documents and records, either itself or through an independent auditor bound by confidentiality, at Customer's cost and with 30 days' written notice. If Provider obtains a Report, Provider will notify Customer and update the Cover Page, and from then on Provider will give Customer, upon written request and on a confidential basis, a summary copy of its then-current Report."
This change does not limit any right of Customer or of data subjects under the EEA SCCs or the UK Addendum. Nothing else in the Standard Terms is changed.
Approved Subprocessors (Annex III)
| Subprocessor | Location | Processing tasks |
|---|---|---|
| Atlassian Pty Ltd (ABN 53 102 443 916), under the Forge Terms and the Forge Data Processing Addendum | Australia (company). Stored data follows the data residency of Customer's Confluence site: the location Customer has pinned, or, if none is pinned, locations chosen by Atlassian. Forge aims to run the App's functions in the same location as the site, but may sometimes run them elsewhere. | Running the App on Atlassian Forge: compute, storage in Forge SQL, queues and logs. |
| Namecheap, Inc., under its Data Processing Addendum | United States | Hosting the support mailbox, support@nordikaapps.com. This applies only to personal data that Customer chooses to include in a support message. |
- Atlassian's own sub-processors are listed at atlassian.com/legal/sub-processors, where Customer can also subscribe to Atlassian's notices. Changes among Atlassian's own sub-processors follow Atlassian's notice period, which is at least 14 days; Provider will forward each such notice to Customer within 2 business days of receiving it.
- Changes to the subprocessors in the table above are published on this page and sent to Customer at least 10 business days in advance, as Section 2.6 of the Standard Terms requires.
- Where notices go. Provider sends notices under this DPA to the customer contact email that Atlassian makes available to Provider for Customer's license, or to another address that Customer gives by writing to support@nordikaapps.com. If no address is available, for example while Customer uses the free tier, notices of subprocessor changes are published on this page, and Security Incident notices are sent through any other means available to Provider, including through Atlassian.
- No other services. Provider does not share Customer Personal Data with any other service, including AI tools.
Annex I: details of the processing
A. List of parties
| Party | Details |
|---|---|
| Data exporter | Customer, as named in its Order. Contact: as described in "Where notices go" above. Activities: use of the App on Customer's Confluence Cloud site. Role: controller (Module Two) or, where Customer processes the data on behalf of another controller, processor (Module Three). Signature and date: given by entering into the Order, as described in "How this DPA applies". |
| Data importer | Er Navas Maldonado, doing business as Nordika Apps, Mexico. Full postal address on request to support@nordikaapps.com. Contact: support@nordikaapps.com. Activities: providing and supporting the App. Role: processor (Module Two) or subprocessor (Module Three). Signature and date: given by publishing this Cover Page and identifying it in the App's Provider-Specific Terms. |
B. Description of the processing
| Item | Description |
|---|---|
| Subject matter | The training records that the App keeps for Customer in Customer's Confluence Cloud site, and support for the App. |
| Categories of Data Subjects | Customer's Users (employees, contractors and other people Customer allows to use its Confluence site) who publish training revisions, answer quizzes or attest; and members of the Confluence groups that Customer chooses as an audience, even if they never open the App. |
| Categories of Personal Data |
|
| Special Category Data | None. |
| Special Category Data Restrictions or Safeguards | Not applicable. The App is not designed to process special category data. Under Section 7.2 of the Agreement, Customer will not submit Sensitive Data, and quiz text should not contain personal data. |
| Frequency of Transfer | Continuous, while the App is installed on Customer's site. |
| Nature and Purpose of Processing | Providing the App to Customer: storing and showing training records; checking with Confluence, as the person, whether they may publish a revision or open a report; reading a page to compute its fingerprint when someone attests (the content is not kept); keeping a cache of audience group membership to show who is pending and who is overdue; looking up names for reports and CSV exports; reporting stored account IDs to Atlassian and erasing the records of closed accounts; keeping a log of actions; and answering support requests. |
| Duration of Processing | While the App is installed under the Agreement. After the App is uninstalled, Atlassian keeps its data for 28 days and then deletes it. The group membership cache is deleted once it is more than 7 days old, unless a refresh is under way. The records of a closed Atlassian account are erased after Atlassian reports the closure to the App. Support messages are kept for as long as needed to handle the request and any follow-up. |
| Transfers to subprocessors | Same subject matter, nature and duration as above, limited to the tasks listed under Approved Subprocessors. |
C. Competent supervisory authority
The supervisory authority determined under Clause 13 of the EEA SCCs. For transfers under the UK Addendum, the Information Commissioner's Office.
Annex II: technical and organizational measures
Platform and data location
- The App runs entirely on Atlassian Forge. Provider operates no servers, databases or other infrastructure of its own.
- The App's manifest declares no external domains, no Forge Remote and no web triggers, so the App cannot send data outside Atlassian.
- Records are stored in Forge SQL, which follows the data residency of Customer's Confluence site.
- Security of the hosting infrastructure is provided by Atlassian under the Forge Data Processing Addendum, including encryption in transit with TLS 1.2 or later. Atlassian makes its SOC 2 Type II report and ISO/IEC 27001 certificate available to Forge developers; those are Atlassian's, not Provider's.
Data minimization
- The App stores Atlassian account IDs, not names or email addresses.
- Page content is read only to compute its SHA-256 fingerprint and is not stored.
- Names are looked up from Confluence when a report is shown or exported.
Access control
- Publishing a revision and opening a report require permission to edit the page. The App checks it with Confluence as the person making the request.
- The list of reports shows only pages the person can view.
- The account and page of every quiz attempt and attestation come from Forge's invocation context, never from the browser, so a person can attest only for themselves.
- Correct quiz answers are kept on the server and are never sent to the browser.
- The App has no administrative interface for Provider and no function that sends records to Provider.
Input and output safety
- All input is validated on the server before it is stored. Database statements use bound parameters; the only values written into the statement text are validated whole numbers for LIMIT and OFFSET.
- Reports write Confluence-provided text as plain text, never as HTML.
- In CSV exports, a cell that starts with
=,+,-or@is prefixed with an apostrophe to prevent formula injection. - Validation, the handling of quiz answers and the CSV prefix are covered by automated tests.
Logs
- The App logs only counts, API quota status and error descriptions. Every error is logged by the App itself after its message is stripped of quoted values and shortened, so that the logs do not carry account IDs or page content; the App does not pass original errors to Forge. The logs are kept by Atlassian.
Personal data lifecycle
- Every week, the App sends the account IDs it stores to Atlassian's personal data reporting API (up to 2,700 accounts per weekly run, starting with those checked longest ago) and erases all records of the accounts that Atlassian reports as closed.
- Account IDs that no longer appear in any record are removed from the App's account list every hour.
- The group membership cache is refreshed at most once a day, when a report is opened, and is deleted once it is more than 7 days old, unless a refresh is under way.
- When the App is uninstalled, Atlassian keeps its data for 28 days and then deletes it.
- The App has no function yet for erasing one person's records while their Atlassian account stays active. If Customer needs this, Customer writes to support@nordikaapps.com from, or with confirmation by, its license contact, and Provider erases them within 30 days.
Availability
- The App limits its own Confluence API use per site and per hour, so that one customer cannot exhaust the quota that Confluence shares among all of the App's customers. Group membership refreshes use only part of that limit, so that the rest stays available for opening reports and publishing revisions, and they continue in the next hour when their part runs out.
Vulnerability management
- Dependencies are pinned with a lock file and scanned with npm audit before every production deployment and on the first day of every month.
- The code is checked with static analysis (eslint-plugin-security).
- The App holds no secrets or credentials. The token used to deploy it is rotated every 90 days and revoked at once if the device that holds it is lost or stolen.
People, incidents and records
- Provider is a one-person business, with no employees or contractors who access Customer Personal Data.
- Provider will notify Customer of a Security Incident without undue delay and no later than 72 hours after becoming aware of it (Section 4 of the Standard Terms). Atlassian notifies Provider of security incidents on its platform under the Forge Data Processing Addendum.
- Provider keeps records of its compliance with this DPA for 3 years after the DPA ends.
- Questionnaires and requests for information are answered in writing, through the Provider Security Contact.
Help with data subject requests
- Access and portability: for each procedure, reports and CSV exports show who attested, when, the page version and the quiz score. Quiz attempts and the log of actions are not exported by the App; on Customer's written request, confirmed by its license contact, Provider provides all records of one person within 30 days.
- Erasure: as described under "Personal data lifecycle".
- Requests sent to Provider: Provider passes them to Customer and does not answer them without Customer's consent (Section 6.1 of the Standard Terms).
About the Standard Terms
The Standard Terms are the Common Paper Data Processing Agreement, Version 1.1 (released May 9, 2025), published by Common Paper at commonpaper.com/standards/data-processing-agreement/1.1 under the Creative Commons Attribution 4.0 International license (CC BY 4.0). This Cover Page fills in their variables and changes Section 5.2 as stated above. Common Paper is not a party to this DPA and has not reviewed or endorsed it.
Versions
1.0 · 28 October 2026 · First version.