Security policy
On Record Labs · Access Snapshot for Confluence · Updated 13 October 2026
Found something? Write to security@onrecordlabs.com. We confirm receipt within two business days and keep you informed until it is resolved.
We do not pay bounties. We will credit you by name if you want to be credited, and we will not take legal action over good-faith research that follows this page.
Who you are writing to
On Record Labs is an independent software studio in Brazil. At the time of writing it is one person. We say that here because it sets honest expectations: you will get a real answer from someone who can read the code, and you will not get a 24/7 incident desk.
What we commit to
| Stage | Commitment |
|---|---|
| Receipt confirmed | within two business days |
| First assessment | within five business days: whether we reproduce it, and how severe we think it is |
| Progress updates | at least every seven days until it is closed |
| Fix | as fast as severity warrants — we will tell you the target date rather than invent one here |
If a fix changes what the app does with data, the privacy policy changes with it, before the version ships.
What we ask of you
- Test against a site you own or administer. Never against another organisation's Confluence.
- Do not access, modify, export or retain data that is not yours. If you reach someone else's data by accident, stop, and tell us what you saw so we can assess the exposure.
- Give us a reasonable window to fix the issue before disclosing it publicly. Ninety days is our default; if the issue is being actively exploited, tell us and we will move faster.
- No denial of service, no spam, no social engineering of anyone.
What is in scope
- The app Access Snapshot for Confluence: its Forge functions, its resolver, and the Custom UI it serves.
- Its exported CSV and PDF files.
- This website,
onrecordlabs.com.
What is out of scope
| Not ours | Where it goes |
|---|---|
| Confluence, Forge, the Atlassian Marketplace, Atlassian accounts | Atlassian's own security team and bug bounty programme |
| Our email, DNS and hosting providers | Those providers' own disclosure channels |
| Reports produced only by automated scanners, with no demonstrated impact | We read them, but a scanner's opinion is not a finding |
| Missing hardening headers on static pages that hold no data and no session | Tell us anyway if you like — we will not treat it as urgent |
What the attack surface actually is
This section exists to save you time. The app is smaller than most, and knowing where it is small tells you where to look.
- No server of ours, anywhere. The app runs on Atlassian's own compute and storage, inside the customer's site. There is no backend we operate, no database we hold, no API of ours to reach.
- No outbound network access. The manifest declares no egress domain, so the app cannot make an external request even if its code tried to.
-
No write access to Confluence. Eight read scopes,
plus
storage:app, which writes only to the app's own storage inside Atlassian and grants no access to customer content. - Almost nothing is stored. One record per installation: counts, durations, gap category codes, and a sentence that names no one. No page titles, no group names, no user names, no page content.
- The report runs as the administrator who clicks it, so it cannot see anything that person cannot already see. There is no privileged service account to escalate to.
Each of those is verifiable in the repository's manifest and source, and each is also stated in the privacy policy. If one of them is ever not true, the interesting bug is probably right there.
Please do not attach a customer report to your email.
The exported CSV and PDF describe who can reach what inside a real site. If your finding needs one, send a redacted fragment or tell us which field matters, and we will ask for exactly what we need and nothing else.
No bounty, and why we say so plainly
We do not pay for reports. The product has no revenue yet, and advertising a bounty we cannot fund would waste your time and ours.
What we can offer: a fast, non-defensive answer from someone who reads the code, public credit if you want it, and a note in the release that fixes it. If that changes, this page changes with it.
Encryption
We do not publish a PGP key today. Mail to
security@onrecordlabs.com travels over TLS. If you need an
encrypted channel for a specific report, write and say so, and we will
agree on one before you send the details.