Security

DocLamp is built so that your content never has to leave Atlassian Cloud. This page is for the people who review an app before it is installed: security teams, site admins and procurement.

Last updated: October 8, 2026

On this page
  1. How DocLamp is built
  2. Runs on Atlassian
  3. Permissions the app asks for
  4. Who sees what
  5. What is stored, and for how long
  6. What we, the publisher, receive
  7. Reporting a vulnerability
  8. Documents

How DocLamp is built

DocLamp is a Confluence Cloud app built on Atlassian Forge, Atlassian's own app platform. Its code runs on Atlassian's compute, its results live in Forge hosted storage, and it declares no outside network destination.

Atlassian Cloud

Your Confluence siteOnly the spaces you chose

reads pages

DocLampRuns on Atlassian Forge

keeps results in

Forge hosted storageSame location as your site's data

No outside destination

Anywhere else, including usYour pages and results never get here
We only receive app logs with counts and durations, which a site admin can turn off, and the licensing contacts Atlassian shares with app publishers.
  • There is no DocLamp server outside Atlassian. Nothing the app reads or computes can be sent elsewhere.
  • The analysis applies fixed rules. It calls no AI service, inside or outside Atlassian.
  • Forge keeps the app's storage in the same location as your site's data, including when your site uses data residency, and encrypts it at rest.

Runs on Atlassian

Atlassian's Runs on Atlassian program identifies apps that use only Atlassian-hosted compute and storage, follow your site's data residency and send no data outside Atlassian. DocLamp is built to meet those requirements. Atlassian checks each app automatically and shows the badge on its Marketplace listing.

Permissions the app asks for

DocLamp asks for six permissions, the fewest its features need. Your site admin sees the same list when installing it.

PermissionWhy DocLamp needs it
read:page:confluenceRead the pages of the spaces you chose: text, headings, titles and links.
read:content-details:confluenceRead page details, such as when a page last changed, to keep the index of links between pages up to date. It also tells DocLamp whether the person using it is a site admin.
read:space:confluenceList the spaces and their names, and the labels used in a space.
search:confluenceCount the pages that carry each label through Confluence search, instead of reading every page again.
storage:appKeep the analysis results in Forge hosted storage, inside Atlassian Cloud.
write:page:confluenceCreate a report page when someone asks for one. Existing pages are never changed.

Who sees what

  • Only site admins choose which spaces DocLamp analyzes. Space admins can exclude their own space at any time.
  • Results are shown only to people who can see the space. Confluence confirms it at each request.
  • Background analyses can be requested only by space admins.
  • Restricted pages never appear anywhere in the app or its reports, since the app cannot read them.
  • A published report is an ordinary Confluence page: whoever can see the space can read it, including the page titles and excerpts it quotes.

What is stored, and for how long

For each analyzed space, DocLamp keeps its latest analysis, its first score, daily, monthly and yearly histories, and the pages that have an issue, with their title, link and an excerpt of at most 160 characters. It stores nothing about who uses it: no names, email addresses, IP addresses, cookies or trackers.

  • Each analysis replaces the previous one. Daily snapshots are kept for the 24 most recent days analyzed, monthly scores for 24 months, and the first score and one score per year for as long as the app is installed.
  • Every score kept can be exported as a CSV file from the app's overview, at any time.
  • A space admin can erase every stored result for a space from the app, at any time. Excluding a space erases its data too.
  • Uninstalling the app erases everything it stored within 28 days.

The Privacy Policy lists every piece of data in detail.

What we, the publisher, receive

We cannot read your pages or the results stored for your site. We receive:

  • app logs, which Atlassian shares with us by default: counts, durations and memory use, never page titles or content. An error message may include a space key. A site admin can stop this sharing in Atlassian Administration, under Apps, Connected apps, DocLamp, Details, Logs access;
  • the licensing information Atlassian gives app publishers;
  • the support requests you choose to send us.

Reporting a vulnerability

If you think you have found a security issue in DocLamp or on this website, write to us with “Security” in the subject line. Tell us what you found and how to reproduce it. We aim to reply within 24 hours and will keep you informed until it is fixed.

Email uscontact@doclamp.com

The same contact is published in security.txt.

Documents