1. Zero External Vendor Server Architecture
Asana Project Table & Filter for Confluence by SyncGrid Solutions runs 100% natively on Atlassian Forge serverless infrastructure. SyncGrid Solutions operates zero external backend servers, databases, or logging endpoints. Customer Confluence content, Asana tasks, and OAuth tokens never transit through or reside on vendor-owned infrastructure.
2. Data Processed & Stored
- OAuth 2.0 Credentials: Managed, encrypted at rest, and refreshed exclusively by Atlassian's native Forge External Authentication vault (
providers.auth). Users may revoke access at any time via Atlassian Connected Apps (id.atlassian.com/manage-profile/apps) or Asana Account Settings. - Macro Configuration Metadata: Only non-personal macro bindings (Asana Workspace GID, Project GID, and project title) are stored inside Atlassian's encrypted Forge Key-Value Store (
@forge/kvs) within your Confluence tenant boundary. - Task Content: Fetched transiently in real time over TLS 1.2+/1.3 directly between Atlassian Forge and
https://app.asana.comstrictly to render the Confluence page view. Task descriptions, titles, and assignees are never persisted in storage.
3. Sub-Processors
Because the application operates exclusively inside Atlassian Forge and communicates directly with Asana's official API, no third-party vendor sub-processors exist beyond Atlassian Pty Ltd (host platform) and Asana, Inc. (customer-authorized data source).
4. Data Retention, Deletion & Privacy Contact
Uninstalling the app from Confluence automatically purges app storage within Atlassian's Forge retention lifecycle, or administrators may request immediate assistance via support@syncgridsolutions.com. SyncGrid Solutions is established in the Republic of Cyprus (European Union) and complies with GDPR Articles 15–22 and 28.