Diagrams.now — Privacy Policy & Terms of Use
How Diagrams.now handles your data, and the terms governing its use as a Confluence Cloud Forge app.
Last updated: October 2026 · Applies to: Diagrams.now (Forge app for Confluence Cloud) · Votazz Global Privacy Policy & Terms
Privacy Policy
Diagrams.now is a Confluence Cloud macro built on Atlassian Forge. All app code, compute, and customer data run inside Atlassian’s hosted Cloud platform with no external egress. Diagrams.now is “Runs on Atlassian” eligible. The manifest declares no external network permissions and no remote endpoints. It contains one web trigger that exists only for development testing: in production it always returns a fixed “development-only” 403 response and can never return customer data.
Permissions (Atlassian scopes declared in the Forge manifest):
| Scope | Purpose |
|---|---|
storage:app | App-level key-value storage (Forge KVS) for diagram persistence |
read:page:confluence | Read Confluence page context the macro is embedded in |
read:attachment:confluence | Load diagram XML and SVG previews stored as page attachments |
read:content-details:confluence | Read page metadata (page id, space id) used to scope storage |
read:user:confluence | Verify whether the current viewer has Confluence admin permission (license gating) |
read:space:confluence | Read the macro’s containing space to scope diagram libraries |
read:content.property:confluence | Declared for the app’s Confluence content property modules (searchable diagram metadata). The app currently keeps its diagram search index in Forge storage instead (see below) |
write:attachment:confluence | Save the diagram XML and SVG preview as page attachments (disaster-recovery copy), and save unpublished edits as a temporary draft attachment |
write:content.property:confluence | Declared together with read:content.property:confluence for the same content property modules |
delete:attachment:confluence | Remove the app’s own temporary draft attachment after you Publish or Discard a diagram |
Diagrams.now does not request any read scope on user profile data beyond the admin-permission check above. It never modifies your Jira issues or Confluence pages outside of saving its own diagram artefacts.
What we store (Atlassian-managed Forge KVS + Confluence page attachments):
| Storage | Stores | Retention |
|---|---|---|
Forge KVS — diagram chunks | Diagram XML chunks keyed by pageId + localId (Confluence page identifier + macro instance identifier). Primary persistence for fast load. | While installed (not removed automatically when the page is deleted; see Data deletion) |
Forge KVS — macroConfig | Pointer record keyed by localId: attachment id, attachment filename, version number, last update timestamp. No user fields accepted by the schema allowlist. | While installed |
Forge KVS — modal scope tokens | Short-lived security tokens with localId, pageId, issued/consumed timestamps. Used to validate iframe parent-child boundaries when opening the editor in a modal. | Single-use, consumed within minutes; unused tokens are removed by a daily cleanup |
Confluence attachment — XML | Compressed drawio-compatible mxfile envelope of the diagram. Filename diagramly-*.xml, page-scoped under Confluence’s attachment lifecycle. | Page lifecycle; deleted with the page or via attachment removal |
Confluence attachment — SVG preview | Rendered SVG snapshot of the diagram for inline preview. Filename diagramly-*.svg, page-scoped. | Page lifecycle |
Confluence attachment — draft | Unpublished edits of a diagram, so they survive closing the editor. Filename diagramly-*.draft.xml, page-scoped. | Removed when you Publish or Discard; otherwise page lifecycle |
Forge KVS — diagram search index | Text labels from the diagram, plus the page id, page title, space key and name, and page URL, so that diagram.now Search can find diagrams without calling Confluence search. | While installed |
Forge KVS — AI usage records | One record per AI operation: your Atlassian accountId, the operation type and its quota weight, AI token counts, model name, the site’s technical identifier, and a timestamp. See AI features below. | Deleted automatically after 45 days |
Forge KVS — AI usage counters | Daily and monthly AI usage totals per site, and daily totals per accountId. | Deleted automatically after 45 days (the site-wide trial counter, which contains no personal data, is kept while installed) |
Forge KVS — AI working data | Intermediate state and the generated result of an AI request. | Deleted automatically after 1 hour |
Note on filename prefix: the literal prefix diagramly- on the attachment filenames is an internal artefact of the app’s development codename and is preserved for storage compatibility. It does not represent any other product or any third-party processor.
Diagram content (user-authored): Diagrams may contain text labels, notes, and shape annotations that you type while editing. This content is your responsibility and is stored alongside the diagram XML in the locations above. Diagrams.now indexes the text labels of your diagrams in its own Forge storage so that diagram.now Search can find them. When you use the AI features, your request is processed as described under “AI features” below. Diagram content never leaves Atlassian Cloud and is persisted only to the Atlassian-hosted storage listed.
What we do NOT store:
- accountId-keyed records, except AI usage records — apart from the AI usage records and counters described under “AI features” (deleted after 45 days), no Diagrams.now record uses an Atlassian account identifier as a key or stored value. Diagram records are scoped by Confluence resource identifiers (page id, space id, macro instance id).
- Email addresses, display names, profile pictures — never read or persisted by the app.
- Telemetry or analytics — no Mixpanel, PostHog, Google Analytics, Segment, Amplitude, or Sentry integration. Zero outbound calls to any third-party service.
- Cross-tenant data — each Atlassian site’s installation is isolated by Forge.
- Payment information — handled by the Atlassian Marketplace.
Real-time collaboration: When two or more users edit the same diagram concurrently, Diagrams.now publishes ephemeral cursor and selection presence updates over the Atlassian-managed real-time channel. These updates carry the originating user’s accountId so the UI can attribute the cursor to a person; the channel is peer-to-peer within your tenant and the presence payload is not persisted to KVS, attachments, or any backend store. When the editor closes, the presence stream ends and no audit record remains.
AI features: The AI diagram features (generation and AI editing) use Atlassian-hosted Claude models through Atlassian Forge LLMs. Your prompt, and any page text included as context, are processed inside Atlassian’s platform; Diagrams.now makes no calls to external AI providers and Votazz does not receive this content.
To enforce fair-use limits, prevent abuse and monitor aggregate cost, Diagrams.now records one usage record per AI operation. Each record contains your Atlassian account ID, the operation type (generation or edit) and its quota weight, the number of AI model tokens used, the model name, a timestamp, and the technical identifier of your Confluence site. Daily usage totals per account are kept alongside. This data is stored only in Atlassian Forge hosted storage inside your site’s app installation, is not shared with any third party, is not used for any other purpose, and is deleted automatically after 45 days.
Confluence administrators can see aggregated AI usage for their site, including the five most active users for the current month, on the app’s admin page in Confluence settings. Names are looked up in the administrator’s browser at view time and are not stored by the app.
Permission check: When loading the editor we ask Confluence whether the current viewer has admin permission. The query passes accountId to Confluence’s /rest/api/user endpoint and reads back a boolean (admin yes/no). The accountId value is used in the request only and is not written to KVS, attachments, logs, or any external service.
Where data lives: Atlassian-managed Forge KVS and Confluence Cloud attachments, region-pinned to your Atlassian site’s region — Atlassian’s choice based on your tenancy. Customers in the EEA may be served from EU regions per Atlassian’s tenancy assignment. Forge hosted storage supports Atlassian data residency, so the app’s stored data follows your site’s data residency location. There is no data egress from Atlassian Cloud to Votazz-operated infrastructure or any third party. See Atlassian’s Forge tenant data isolation documentation for the platform isolation model.
Encryption: All data Diagrams.now writes is encrypted at rest by the Atlassian Forge platform (Forge KVS) and Confluence Cloud (page attachments), and is transmitted exclusively over TLS 1.2 or higher. Diagrams.now itself does not run any independent storage or network transport — encryption is provided end-to-end by Atlassian’s hosted platform.
Compliance & certifications: Because Diagrams.now runs entirely on the Atlassian Forge platform, customer data inherits Atlassian’s compliance posture (SOC 2, ISO 27001, GDPR, and others as published by Atlassian). For Votazz-level certifications, security controls, and breach-notification commitments, see the Votazz Trust Center.
Subprocessors: None outside Atlassian. AI features run on Atlassian-hosted models through Forge LLMs. Diagrams.now does not transmit data to external analytics, monitoring, AI providers, or any other third-party service. All compute and storage stay inside Atlassian Cloud.
Data deletion: When a Confluence page hosting a Diagrams.now macro is deleted, Confluence removes the diagram attachments with the page. The app’s own records for that diagram in Forge storage (diagram data, pointer record and search entry) remain in your site’s app installation until the app is uninstalled; email support@votazz.co to have them erased sooner. AI usage records are deleted automatically after 45 days. When you uninstall Diagrams.now, the Atlassian Forge platform automatically places your tenant’s KVS data in soft-delete for 30 days, after which it is permanently purged; Confluence attachments remain on your pages under your workspace’s ownership. While the app is installed, you may email support@votazz.co to request immediate erasure of any specific diagram or all diagrams associated with your account.
GDPR Article 28 status: for the purposes of GDPR Article 28, you are the controller of the data processed by Diagrams.now, Atlassian is your processor, and Votazz acts as a sub-processor. This covers the data that already resides in your Confluence Cloud tenant, the diagram content you author (shape labels, notes, annotations), and the AI usage records described above. Votazz processes this data only to provide the app’s functionality. The Data Processing Agreement in the global policy governs this relationship.
Your rights: The GDPR and CCPA rights described in the global Votazz Privacy Policy apply to data processed by Diagrams.now. The only records Diagrams.now keys by your Atlassian account ID are the AI usage records, which are deleted automatically after 45 days. To have them, or any diagram data held in the app’s storage, erased sooner under GDPR Article 17, email support@votazz.co and we will delete them. After uninstall, the platform 30-day soft-delete behavior described above applies to KVS storage.
Security & Vulnerability Disclosure
Reporting vulnerabilities: If you discover a security issue in Diagrams.now, please email security@votazz.co or submit via the Atlassian Marketplace “Security and privacy support” channel. We acknowledge reports within 1 business day and use CVSS v3.1 to score severity.
Patch SLAs (aligned with Atlassian Marketplace Security Bug Fix Policy):
- Critical (CVSS 9.0+): patch within 7 days
- High (CVSS 7.0–8.9): patch within 30 days
- Medium (CVSS 4.0–6.9): patch within 90 days
- Low (CVSS < 4.0): addressed in the next regular release
Responsible disclosure: We request a 90-day private disclosure window before public publication. Researchers acting in good faith are credited (with consent) in our release notes.
Authentication & access controls: Code is deployed only via the Atlassian Forge Developer Console by authorised Votazz engineers. Multi-factor authentication is enforced on all Votazz developer accounts.
Dependency management: Production dependencies are continuously monitored via the Atlassian Forge Dependency Scanner and npm audit. Diagrams.now ships with zero high- or critical-severity production-dependency vulnerabilities at release.
Logging & monitoring: Application logs are retained by the Atlassian Forge platform for 30 days and reviewed for scope-permission failures and runtime errors. Logs stay inside the Atlassian Forge platform. They contain no customer diagram content and no raw Atlassian account IDs; AI usage log lines carry only a one-way hash of the account ID.
Terms of Use
1. Acceptance of Terms
By installing or using Diagrams.now from the Atlassian Marketplace, you agree to be bound by these Terms of Use and the Atlassian Marketplace End User License Agreement. If you do not agree, please uninstall the app and discontinue use.
2. License
Diagrams.now is licensed per user tier as published on its Atlassian Marketplace listing. Use of the app is subject to the Atlassian Marketplace End User License Agreement. Votazz grants you a non-exclusive, non-transferable, revocable license to use Diagrams.now for the duration of an active Marketplace subscription, including the free trial period.
3. Support & Maintenance
Active Diagrams.now subscriptions include email support and ongoing updates delivered automatically via Atlassian Marketplace. Support hours are Monday – Friday, 9am – 5pm AEST/AEDT. Reach support at support@votazz.co.
4. Refunds
All Diagrams.now purchases are subject to the Atlassian Marketplace refund policy. New paid subscriptions include a 30-day money-back guarantee. Refund requests are processed by Atlassian; contact support@votazz.co for assistance.
5. Acceptable Use
You agree not to use Diagrams.now for any unlawful purpose, to violate any third-party rights, to attempt to gain unauthorized access to any systems or networks, or to reverse-engineer, decompile, or otherwise extract the app’s underlying source code beyond what is permitted by applicable law.
6. Limitation of Liability
Diagrams.now is provided “as is” without warranty of any kind. Votazz is not liable for any indirect, incidental, special, consequential, or punitive damages arising from the use of, or inability to use, Diagrams.now — including loss of data, loss of business, or interruption of service. Our total aggregate liability for any claim relating to Diagrams.now shall not exceed the amount paid by you for the app in the 12 months preceding the claim.
7. Termination
You may terminate use of Diagrams.now at any time by uninstalling the app from your Atlassian site. Upon uninstall, your tenant’s KVS data is placed in 30-day soft-delete by the Forge platform, after which it is permanently purged; Confluence attachments saved by the app remain on your pages under your workspace’s ownership. Votazz may suspend or terminate access for violation of these Terms or the Atlassian Marketplace EULA.
8. Contact
For questions about these Terms or the app, contact us at support@votazz.co.
For shared sections — cookies, retention rules, your rights under GDPR & CCPA, jurisdiction, contact, and the Data Processing Agreement (DPA) — see the Votazz Global Privacy Policy & Terms of Use.