🛡️ Atlassian Forge
🔒 HTTPS/TLS
🇪🇺 GDPR Compliant

XPress — Security Policy

A comprehensive overview of how we protect your data, handle security incidents, manage vulnerabilities, and the security controls we have in place for XPress.

Last updated: April 2026

🏗️

Built on Atlassian Forge

XPress runs entirely within Atlassian's secure Forge platform — a sandboxed, multi-tenant environment with enterprise-grade security controls. Your data stays within the Atlassian cloud ecosystem.

🔐

Zero Personal Data Storage

We do not collect, store, or process any personal user data. XPress accesses Confluence content only when you initiate an action, and only through official Atlassian APIs.

🎯

Least Privilege

We follow the principle of least privilege — XPress only requests the minimum API scopes necessary for its functionality. No unnecessary data access.

🔄

No Third-Party Tracking

We do not use any third-party analytics, advertising, or tracking services within XPress. Your usage data is never shared with external parties.

Data Handling

How XPress accesses, processes, and stores data

Data Flow

1

Content Access

When you initiate an export, XPress reads your Confluence pages through official Atlassian APIs within the Forge sandbox.

2

Document Rendering

Document layout and styling are processed by our secure, cloud-hosted rendering service over encrypted HTTPS. The service processes data in-memory only and immediately discards all content — zero data retention.

3

Document Storage

Generated documents are stored within Forge SQL (Atlassian's cloud infrastructure). All content reading and storage remains within the Atlassian environment.

Data Storage Summary

Data Type Location Retention Encrypted
Generated documents Forge SQL (Atlassian cloud) Until deleted by user or app uninstalled ✅ At rest & in transit
App configuration Forge App Storage Until app uninstalled ✅ At rest & in transit
Personal user data Not collected

Subprocessors

Third-party services involved in data processing

Service Provider Purpose Data Location Data Stored
Atlassian Forge Atlassian App runtime, SQL database, storage, queues Per customer's Atlassian data residency App config, generated PDFs
Cloud Rendering Service Amazon Web Services Document rendering engine United States None — zero data retention

We do not use any other third-party services for data processing, analytics, or tracking within XPress.

App Permissions

Every permission explained

read:page:confluence
Read pages for export
read:confluence-content.all
Access page body content for PDF generation
read:confluence-space.summary
Display space list for content selection
read:attachment:confluence
Include images and files in exported PDFs
read:hierarchical-content:confluence
Navigate page tree for bulk exports
search:confluence
Enable content search within the app
write:confluence-file
Save generated PDFs as Confluence attachments
storage:app
Store app configuration and generated PDFs

Security Controls

Measures we implement to protect your data

🔑 Access Control

  • Principle of least privilege: Only minimum API scopes required for document export
  • User-initiated only: Content accessed only when user triggers an export
  • Confluence permissions: Respects native permission model — users export only what they can view
  • No admin access: App does not require Confluence admin privileges

🔒 Data Protection

  • Encryption in transit: HTTPS/TLS for all communication
  • Encryption at rest: Forge SQL and App Storage encrypted by Atlassian
  • Zero retention on render service: In-memory processing only
  • No personal data: Only Atlassian Account ID from app context

🏗️ Infrastructure

  • Forge sandbox: Isolated per-tenant execution environment
  • Cloud rendering: Private networking, no public access to rendering infrastructure
  • Ephemeral containers: Rebuilt from verified base images
  • No direct database: Render service has zero persistent storage

📊 Monitoring & Development

  • Infrastructure monitoring: Continuous health and performance tracking
  • Error tracking: Metadata only — no customer content in logs
  • Version control: Private repos with branch protection and required reviews
  • CI/CD pipeline: Automated build, test, and deployment

Incident Response

How we handle security incidents and vulnerabilities

Report a security issue: admin@bytera.tech — Subject: "Security Incident" or "Vulnerability Report"
Support Portal: Bytera Support

Response Process

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 Classification

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.

Vulnerability Management

Proactive and reactive security measures

Proactive Measures

  • Dependency scanning: Regular audits and updates for all third-party dependencies to address known CVEs
  • Code review: All changes undergo peer review with security-focused assessment for sensitive changes
  • Forge updates: Prompt adoption of new platform versions with security improvements
  • Minimal dependencies: Reduced attack surface through minimal external dependency footprint

Remediation Process

  1. Assessment: Evaluate applicability and real-world exploitability
  2. Classification: Assign severity level based on impact and likelihood
  3. Remediation: Develop, test, and deploy a fix within defined timelines
  4. Verification: Confirm fix resolves the issue without regressions
  5. Disclosure: Clear communication for customer-impacting vulnerabilities

Responsible Disclosure

We support responsible disclosure. If you discover a vulnerability, report it to admin@bytera.tech before public disclosure. Allow reasonable time for investigation and patching. We will acknowledge your contribution (with your permission) once resolved.

Compliance

Regulatory and platform compliance

🇪🇺

GDPR

Bytera operates as a data processor. We follow data minimization, purpose limitation, and respect data subject rights. Our rendering sub-processor (AWS) maintains GDPR compliance through Standard Contractual Clauses (SCCs).

🏪

Atlassian Marketplace

XPress adheres to all Atlassian Marketplace Partner requirements for security, privacy, and the Security Bug Fix Policy.

☁️

Forge Security

By building on Forge, XPress inherits Atlassian's SOC 2 Type II certified infrastructure controls and benefits from their security-first platform architecture.

Frequently Asked Questions

Does XPress store my Confluence content?

No. XPress accesses your content only during the export process. Generated documents are stored within Forge SQL (Atlassian's infrastructure), but the original page content is never permanently copied or stored outside of Confluence.

Does any data leave the Atlassian cloud?

During the export process, document layout and styling data is processed by our secure, cloud-hosted rendering service over encrypted HTTPS. This service operates as a stateless engine — it processes data in-memory only and immediately discards all content upon completion. The generated document is returned to Forge and no data is retained.

Do you collect personal data?

No. We do not collect, store, or process any personal user data. We only access the Atlassian Account ID provided in the app context to process your request. No user profiles, emails, or personal information is stored.

Where is data hosted?

App data is hosted within Atlassian's Forge infrastructure, subject to your organization's Atlassian data residency settings. Our rendering service is hosted on secure cloud infrastructure in the United States.

Are you GDPR compliant?

Yes. We follow GDPR principles including data minimization, purpose limitation, and respect for data subject rights. Since we don't store personal data, the compliance surface is minimal. Users can request data access, correction, or deletion at any time by contacting us.

What happens when I uninstall XPress?

When XPress is uninstalled, all app-related data (configuration, generated documents in Forge SQL) is automatically removed by the Atlassian Forge platform. No residual data remains.

How do I report a security concern?

Please contact us immediately at admin@bytera.tech with the subject line "Security Concern". We take all security reports seriously and will respond within 24 hours.

Related Documents

Have a security question?

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.