Pulse runs entirely on Atlassian Forge: it has no server of its own, and your Confluence content stays in the Atlassian cloud. It changes a page only as the signed in person, after that person confirms the change. The AI features of the Advanced edition use Atlassian's Forge LLMs. The only data Pulse sends outside Atlassian is usage analytics (which Pulse pages, features and actions are used, marked with your site and the state of its subscription), sent to an analytics product on Atlassian's pre-approved allowlist.
Last updated: October 2026
Pulse keeps everything it stores in your site's own Forge database, hosted by Atlassian in your site's location. Scoring runs inside Forge, and AI features use Atlassian's Forge LLMs, never a third party AI provider.
Pulse can change a page in three ways only: Apply a fix, the label needs-review and a comment that mentions the page owner. Each is made as the signed in person, after one confirmed click, and shows in Confluence. Nothing Pulse runs by itself changes a page.
Lists, counts and reports are computed over the pages the person looking at them can open, checked with Confluence as that person. Nobody sees a total over pages they cannot open, an admin included.
Pulse stores people as keyed hashes, not account IDs, and never stores names, email addresses or pictures: each person's browser looks a name up as that person. Analytics are marked with your site and the state of its subscription, never with a person.
How Pulse accesses, processes, and stores data
Pulse's screens ask Confluence for pages as the person using them, so Confluence applies that person's permissions. The background index reads as the app, and shows nobody anything until Confluence has answered for those pages as that person.
Pulse counts what a score is made of (words, headings, links, images, placeholder text) and keeps the counts, titles and scores in Forge SQL. Page text is not stored.
Every list and number is counted for the person looking at it. A title is shown only for a page Confluence returned to that person in the last 10 minutes.
| Data Type | Location | Retention | Encrypted |
|---|---|---|---|
| Page index: titles, counts, scores; owners and editors as keyed hashes | Forge SQL (your site's location) | While the app is installed | ✅ By Atlassian |
| Rows about one person (settings, sessions, choices), under a keyed hash | Forge SQL | One minute to 180 days by kind | ✅ By Atlassian |
| A reader's optional note (up to 280 characters) | Forge SQL | 180 days while open, 30 days after closing | ✅ By Atlassian |
| Site and space policies, coach defaults, review intervals | Forge SQL | While installed, or until an admin resets them | ✅ By Atlassian |
| Pairs of pages on one topic | Forge SQL | While both pages exist; AI pairs 90 days | ✅ By Atlassian |
| Page text | - | - | Not stored |
| Names, email addresses, profile pictures | - | - | Not stored |
Atlassian deletes an installation's data 28 days after an uninstall. The privacy policy lists every kind of data and its retention.
Every service involved in running Pulse
| Service | Provider | Purpose | Data Location | Data Stored |
|---|---|---|---|---|
| Atlassian Forge | Atlassian | App runtime, Forge SQL database, and Forge LLMs for the AI features of the Advanced edition | Per customer's Atlassian data residency | The page index, settings and per person rows described above |
| PostHog | PostHog Inc. | Usage analytics, an analytics product on Atlassian's pre-approved allowlist, declared in the Forge manifest with end-user data out of scope | United States (SCCs) | Events with the site's cloud ID and fixed values; no content, titles, names or account IDs |
Pulse uses no other external services. Your Confluence content is processed only within Atlassian's platform, AI processing included.
Every permission explained
Four write permissions allow three changes, each made as the signed in person after they confirm it. They stay locked on a site until its admin approves them. One permission is reserved and unused. Pulse has no attachment access and never fetches web addresses from your pages.
Measures we implement to protect your data
How we handle security incidents and vulnerabilities
Report a security issue: support@bytera.tech, subject "Security Incident" or "Vulnerability Report"
Support Portal: Bytera Support
| Phase | Action | Timeline |
|---|---|---|
| Acknowledgment | Confirm receipt and assign severity level | Within 24 hours |
| Triage | Assess scope, impact, and affected systems | Within 48 hours |
| Containment | Isolate affected components; disable features if necessary | Immediate upon confirmation |
| Remediation | Develop and deploy a fix | Based on severity |
| Notification | Notify affected customers with details and remediation steps | Within 72 hours of confirmation |
| Post-Mortem | Document root cause, lessons learned, and preventive measures | Within 2 weeks |
| Severity | Description | Target Resolution |
|---|---|---|
| Critical | Active exploitation, data breach, or complete service compromise | Within 24 hours |
| High | Vulnerability with significant impact potential but no active exploitation | Within 72 hours |
| Medium | Vulnerability with limited impact or requiring specific conditions | Within 1 week |
| Low | Minor issue with minimal security impact | Next scheduled release |
Our severity timelines align with the Atlassian Security Bug Fix Policy for Marketplace Partners.
We respond to critical and high-severity (T1) support requests within 24 hours, 5 business days per week, in Europe/Berlin (Central European Time). Channels: our support portal and support@bytera.tech.
Regulatory and platform compliance
Bytera follows data minimization and purpose limitation principles. Pulse stores people as keyed hashes and never stores names, emails or profile data, and the only outbound data is usage events without personal data to an analytics product on Atlassian's pre-approved allowlist.
Pulse adheres to the Atlassian Marketplace Partner requirements for security and privacy and the Security Bug Fix Policy, and takes part in the Marketplace Security Bug Bounty.
By building on Forge, Pulse inherits Atlassian's SOC 2 Type II certified infrastructure controls and benefits from their security-first platform architecture.
Pulse reads pages to count what a score is made of and keeps the counts, titles and scores, not the text. The one text a person types that Pulse keeps is the optional note of "This looks wrong", up to 280 characters.
In three ways only: Apply a fix (replace a placeholder, or remove links to pages in the trash), the label needs-review, and a comment that mentions the page owner. Each is made as the signed in person, after they confirm it, and shows in Confluence. Pulse never changes a page by itself and archives nothing. On a site that updated from an earlier version, the changes stay locked until an admin approves Pulse's new permissions.
No. Scoring runs in the Forge runtime, and the AI features of the Advanced edition use Atlassian's Forge LLMs inside the platform. The only outbound connection is usage events, with no content, titles, names or account IDs, to an analytics product on Atlassian's pre-approved allowlist.
Only on the Advanced edition, for the similar meaning check, on Atlassian's Forge LLMs. Pulse sends titles, never page text, and nothing goes to a third party AI provider. The Standard edition never calls a model.
Pulse stores people as keyed hashes (HMAC SHA-256 with a secret per installation), not account IDs, and never stores names, email addresses or profile pictures: each person's browser looks a name up as that person. Analytics carry the site's cloud ID and fixed values, never an account ID. The privacy policy lists the few exceptions.
Pulse is built so they cannot. Every list, count and report is computed for the person looking at it, over pages Confluence lets that person open, and a title is shown only for a page Confluence returned to that person in the last 10 minutes.
Yes. Pulse keeps its data in your site's Forge database, stores people as keyed hashes and no profile data, and sends only usage events without personal data outside Atlassian. Users can request data access, correction, or deletion at any time.
Pulse keeps nothing after an uninstall. Atlassian's Forge storage keeps the installation's data for 28 days, so that a reinstall can be linked to it, and then deletes it. Bytera has no copy.
Please contact us immediately at support@bytera.tech with the subject line "Security Concern". We respond within 24 hours.
We're committed to transparency. If you have any questions about our security practices, data handling, or need additional information for your security review, please don't hesitate to contact us.