1. Architectural Zero-Egress Commitment
SpecSync v3.0 is engineered from the ground up as a 100% Atlassian-hosted Forge application (nodejs22.x runtime). Our application manifest (manifest.yml) declares zero external egress permissions (permissions.external is completely empty).
Runs on Atlassian Guarantee: SyncForge Cloud Systems does not operate external application servers, external databases, or external analytics endpoints for SpecSync v3.0. All uploaded SAP PI/PO archives (
.tpz), SAP Cloud Integration packages (.iflw / .zip), Groovy scripts, OpenAPI contracts, WSDL files, and simulated XML/JSON payloads are processed ephemerally in memory inside your Atlassian Cloud tenant and never leave Atlassian's infrastructure.
2. Data Processed Within Your Atlassian Tenant
To deliver documentation generation, migration conversion, governance remediation, and breaking-drift alerts, SpecSync processes only the following customer-controlled artifacts inside Atlassian Forge:
| Data Category | Purpose of Processing | Storage Location & Retention |
|---|---|---|
Integration Packages (.iflw, .zip, .tpz, OpenAPI, WSDL) |
Parse adapter topology, convert PI/PO ICOs & UDFs, run governance audits, and build Confluence ADF specifications. | Processed ephemerally in Forge Lambda memory during invocation; raw files are never persisted externally. |
| Structural Baseline Fingerprints & Metadata | Compare v1 vs. v2 package revisions to detect breaking endpoint, security, or schema drift. | Stored exclusively in Atlassian Forge Encrypted App Storage (storage:app) partitioned by your Atlassian cloudId. |
| Webhook Signing Secret (Optional) | Verify HMAC-SHA256 signatures on incoming CI/CD webtrigger requests. |
Stored exclusively in your tenant's Forge Encrypted App Storage; never readable outside your tenant. |
| Evaluation Quota Counters | Track aggregate invocation counts on evaluation licenses per tenant cloudId. |
Stored locally inside Atlassian Forge App Storage; contains zero personal user names or email addresses. |
3. Personal Identifiable Information (PII) & Usage Tracking
- Zero PII Collection by Vendor: SpecSync v3.0 does not collect, transmit, sell, or store end-user names, email addresses, IP addresses, browser fingerprints, or customer payload contents on any SyncForge Cloud Systems infrastructure.
- Zero External Analytics or Tracking Pixels: Neither the Confluence Custom UI macro nor the Forge backend loads external scripts, fonts, tracking pixels, or third-party analytics SDKs.
- Billing & Licensing Metadata: Commercial subscription billing is managed directly by Atlassian via Paid via Atlassian. SyncForge Cloud Systems receives only standard Marketplace Partner license transaction summaries provided by Atlassian in accordance with the Atlassian Privacy Policy.
4. Subprocessors, Data Residency & GDPR Compliance
- Third-Party Subprocessors: None (Zero). All compute and storage are fulfilled exclusively by Atlassian Cloud (Atlassian Forge platform).
- Data Residency: Because SpecSync stores baseline state solely in Atlassian Forge App Storage and Confluence/Jira Cloud entities, data residency automatically follows Atlassian Forge's regional hosting controls configured for your Atlassian Cloud site.
- Data Deletion & Right to Erasure (GDPR Art. 17): Administrators may delete stored artifact baselines at any time or uninstall SpecSync from Atlassian Administration, which purges tenant Forge App Storage in accordance with Atlassian Forge platform lifecycle policies.
5. Privacy Inquiries & Data Protection Contact
For privacy questionnaires, DPA confirmations, or GDPR inquiries regarding SpecSync v3.0, contact SyncForge Cloud Systems at support@syncforgecloud.com.