Data Processing Addendum

Last updated: October 9, 2026

This addendum sets out how we process personal data on your behalf when your organization uses DocLamp. It forms part of the End User Terms and applies automatically, with no signature needed.

On this page
  1. Who it binds and how it applies
  2. What we process, and how
  3. Your instructions
  4. Confidentiality
  5. Security
  6. Sub-processors
  7. Data location and transfers
  8. Requests from individuals
  9. Personal data breaches
  10. Deletion at the end
  11. Information and audits
  12. Liability, duration and governing law
  13. Annex 1: Details of the processing
  14. Annex 2: Security measures
  15. Annex 3: Sub-processors

Who it binds and how it applies

This addendum is between Brainsower Solutions, registered in France under SIRET 989 706 544 00016, Metz, France (“we”, “us”, the processor), and the organization that installs DocLamp (“you”, the controller).

  • It applies whenever the app processes Customer Personal Data on your behalf, from installation until that data is deleted.
  • “Customer Personal Data” means personal data contained in the Confluence content the app reads or stores for you, such as a name in a page title or an excerpt.
  • “Data Protection Law” means the EU General Data Protection Regulation (GDPR) and the national laws that complete it, and, where they apply to you, the UK GDPR and the Swiss Federal Act on Data Protection. Other terms, such as controller, processor and personal data breach, have their GDPR meaning.
  • If this addendum and the End User Terms differ on the processing of personal data, this addendum prevails.

If your organization needs a signed copy, write to contact@doclamp.com.

What we process, and how

The app reads the Confluence spaces your site admins choose, computes its analysis and keeps the results for you. Annex 1 describes this processing in detail.

All of it happens inside Atlassian Cloud. The app runs on Atlassian Forge, declares no outside network destination, and keeps its results in Forge hosted storage. We, the publisher, have no access to your Confluence content or to the results stored for you: only the app's code can reach them.

The personal data we receive ourselves, such as licensing contacts, app logs and the support emails you send us, is not covered by this addendum. We process it as a controller, as our Privacy Policy explains.

Your instructions

We process Customer Personal Data only on your documented instructions, unless the law requires otherwise. In that case we tell you first, unless the law forbids it.

Your instructions are the End User Terms, this addendum, and what your users do in the app: the spaces they choose or exclude, the analyses they run, the reports they publish and the data they erase.

We will tell you if we believe an instruction breaks Data Protection Law.

You remain responsible for the lawfulness of your Confluence content and for choosing which spaces the app may read.

Confidentiality

Anyone working for us on DocLamp is bound by a duty of confidentiality. In any case, the design of the app keeps Customer Personal Data out of our reach.

Security

We apply the technical and organizational measures listed in Annex 2. We may improve them over time, but never lower the overall level of protection.

Sub-processors

You authorize us to use the sub-processor listed in Annex 3: Atlassian, which hosts the app.

  • Atlassian processes data for Forge apps under its Forge Data Processing Addendum and the Standard Contractual Clauses, which impose data protection obligations at least as strict as this addendum.
  • We will announce any new sub-processor at least 30 days in advance, on this page and in the app's release notes on the Marketplace.
  • You may object on reasonable data protection grounds by writing to us. If we cannot meet your concern, you may end your subscription, and we will refund through Atlassian the unused part of any prepaid period.
  • We remain responsible to you for our sub-processors' obligations, as the GDPR requires.

Data location and transfers

We are established in France, in the European Union.

Forge keeps the app's storage in the same location as your Confluence site's data, including when your site uses data residency. We transfer no Customer Personal Data ourselves.

Where Atlassian processes data outside the European Economic Area to provide Forge, the Standard Contractual Clauses between Atlassian and us apply.

Requests from individuals

Your organization answers requests from the people whose data appears in your content, and the app gives you direct control:

  • edit or delete a page, and its title and excerpts leave the results at the next analysis;
  • restrict a page's view, and the app no longer reads it;
  • exclude a space, and the data kept for it is erased;
  • erase every stored result for a space, at any time, with “Erase this space's data”.

If someone sends us a request about your data, we forward it to you without undue delay and do not answer it ourselves unless you ask us to.

We also help you with data protection impact assessments and consultations with a supervisory authority, by giving you the information we hold about the processing.

Personal data breaches

We will notify you without undue delay, and where possible within 48 hours, after becoming aware of a personal data breach affecting Customer Personal Data.

  • Our notice goes to the technical and billing contacts Atlassian gives us for your licence. Please keep them up to date.
  • It describes what happened, the data and people likely concerned, the likely consequences and the measures taken or proposed, as far as we know them. We complete it as we learn more.
  • If a breach happens in Atlassian's infrastructure, we pass on what Atlassian tells us.

Deletion at the end

When you uninstall the app, Atlassian keeps its storage for 28 days, then deletes it. Within that window it can be restored only with your consent.

  • Before uninstalling, you can export every score kept as a CSV file, and erase any space's data from the app.
  • We keep no copy of Customer Personal Data.
  • Report pages published by the app are ordinary pages of your Confluence site. They stay under your control; you can delete them like any page.

Information and audits

We make available the information needed to show that we meet our obligations under this addendum:

  • this addendum, our Privacy Policy and our Security page;
  • the privacy and security answers on DocLamp's Marketplace listing;
  • written answers to your reasonable security questionnaires, within 30 days.

If that information is not enough, or a supervisory authority requires it, you may carry out an audit, once a year at most:

  • with at least 30 days' written notice, at your own cost;
  • yourself, or through an independent auditor bound by confidentiality;
  • without access to other customers' data or to Atlassian's systems.

Atlassian's infrastructure is covered by Atlassian's own certifications and reports, available from its Trust Center.

Liability, duration and governing law

  • The limits of liability in the End User Terms apply to this addendum, to the extent Data Protection Law allows.
  • This addendum lasts as long as we process Customer Personal Data for you, until it is deleted after you uninstall the app.
  • We may update it, for example when the law changes or for a new sub-processor as described above. The current version is always at doclamp.com/dpa, with its date, and we announce a significant change at least 30 days before it takes effect.
  • It is governed by French law. The courts of Metz, France, have exclusive jurisdiction, unless Data Protection Law requires otherwise.

Annex 1: Details of the processing

Subject matterAnalysis of the Confluence content your site admins choose, to score how ready it is for Rovo and show what to fix.
NatureAutomated reading of pages with the app's own account, applying fixed rules, storing the results, showing them in the app and on space home pages, and publishing report pages when a user asks for one.
PurposeComputing, showing and tracking the analysis for you. No other purpose: no AI service, no model training, no advertising, no profiling.
DurationWhile the app is installed, then 28 days until Atlassian deletes its storage.
Data subjectsPeople whose personal data appears in the analyzed content, such as page authors, colleagues, customers or partners named in pages.
Personal dataRead: whatever personal data appears in the titles, text and links of analyzed pages. Stored: titles and links of pages that have an issue, excerpts of up to 160 characters, and page identifiers. The app stores no names, email addresses or other details about the people who use it.
Special categoriesNone intended. The app does not look for them, but an excerpt could quote one if your pages contain it. You decide which spaces the app reads.
RetentionThe latest analysis, up to 24 daily snapshots, one score per month for up to 24 months, and the first score and one score per year while the app is installed, per space. Details in the Privacy Policy.
LocationForge hosted storage, in the same location as your Confluence site's data.

Annex 2: Security measures

  • Inside Atlassian Cloud. The app runs only on Atlassian Forge compute and storage and declares no outside network destination.
  • Encryption. Forge encrypts the app's storage at rest, and Atlassian encrypts traffic in transit.
  • No access for the publisher. We cannot read your Confluence content or the stored results; only the app's code can reach the storage.
  • Least access to content. The app reads nothing until a site admin chooses spaces, never reads a space left out of that choice, never reads personal spaces, and never reads pages with view restrictions, since those exclude the app's account.
  • Access control. At each request, Confluence confirms, as the person asking, that they can see the space before any result is shown. Only site admins choose the analyzed spaces, and only space admins can erase a space's data or request a background analysis.
  • Data minimization. Pages are never copied whole. Stored excerpts are 160 characters at most. Long-term history keeps scores, dates and page counts, with no titles or text.
  • Logs. The app logs counts, durations and memory use, never page titles or content. A site admin can stop log sharing with us in Atlassian Administration.
  • Minimal permissions. The app asks for six Confluence and storage permissions, each explained on our Security page. It holds no passwords, tokens or other secrets.
  • Secure development. We check the app's dependencies for known vulnerabilities and do not release a version with a known critical or high one. Authorization checks have automated tests, run again whenever the code that enforces them changes.
  • Vulnerability handling. Security reports go to contact@doclamp.com, as published in security.txt, and are handled as a priority.

Annex 3: Sub-processors

Sub-processorServiceLocationSafeguards
Atlassian Pty Ltd (ABN 53 102 443 916), Sydney, AustraliaHosting of the app on Atlassian Forge: compute, storage and loggingThe location of your Confluence site's dataForge Data Processing Addendum and Standard Contractual Clauses

Atlassian relies on its own sub-processors, such as cloud hosting providers, listed on Atlassian's sub-processor page.

Contact: contact@doclamp.com, Brainsower Solutions, Metz, France.