Nordika Apps

Data Processing Agreement

Nordika Apps · SOP Training & Attestation for Confluence · Cover Page version 1.0 · Last updated: 28 October 2026

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

Key terms

TermValue
ProviderEr Navas Maldonado, an individual in Mexico, doing business as Nordika Apps. Notice address: support@nordikaapps.com.
CustomerThe organization that enters into an Order for the App (the party placing the Order under the Agreement).
AgreementThe 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.
ServiceAs 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 SubprocessorsThe subprocessors listed under Approved Subprocessors (Annex III).
Provider Security Contactsupport@nordikaapps.com
Security PolicyThe 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 StateIreland

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)

SubprocessorLocationProcessing tasks
Atlassian Pty Ltd (ABN 53 102 443 916), under the Forge Terms and the Forge Data Processing AddendumAustralia (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 AddendumUnited StatesHosting the support mailbox, support@nordikaapps.com. This applies only to personal data that Customer chooses to include in a support message.

Annex I: details of the processing

A. List of parties

PartyDetails
Data exporterCustomer, 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 importerEr 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

ItemDescription
Subject matterThe training records that the App keeps for Customer in Customer's Confluence Cloud site, and support for the App.
Categories of Data SubjectsCustomer'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
  • Atlassian account IDs.
  • Dates and times of publishing, quiz attempts and attestations.
  • Quiz attempt numbers, scores and pass results.
  • For each record, the page ID, revision number, page version and a SHA-256 fingerprint of the page content.
  • Membership of audience groups (account IDs per group), kept as a cache.
  • A log of actions (publishing a revision, attesting) with the account ID and time.
  • Names, which are looked up from Confluence when a report is shown or exported and are not stored by the App.
  • Support messages that Customer sends to Provider.
The App does not store names, email addresses or page content. It also stores the IDs and names of the audience groups, and the quiz questions and answer options that Customer's editors write, as written.
Special Category DataNone.
Special Category Data Restrictions or SafeguardsNot 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 TransferContinuous, while the App is installed on Customer's site.
Nature and Purpose of ProcessingProviding 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 ProcessingWhile 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 subprocessorsSame 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

Data minimization

Access control

Input and output safety

Logs

Personal data lifecycle

Availability

Vulnerability management

People, incidents and records

Help with data subject requests

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.