Data Handling and Privacy
E-SignSeal is built on Atlassian's Forge platform, which means all data your team generates — contract documents, signer identities, audit trails, and signed PDFs — is stored and processed entirely within Atlassian's infrastructure. No data is transmitted to Optimizory's servers or any third-party service.
E-SignSeal app info panel showing Forge platform badge and data residency indicator
Data storage architecture
E-SignSeal uses Forge Storage, Atlassian's built-in key-value and entity storage layer. Data written via Forge Storage is:
Hosted on Atlassian's cloud infrastructure in the same region as your Jira site
Subject to Atlassian's data residency controls and security certifications (SOC 2, ISO 27001, and others documented on the Atlassian Trust Center)
Not accessible to Optimizory or any party outside your Atlassian site
Forge Storage is the only persistence mechanism E-SignSeal uses. There are no external databases, no third-party file storage services, and no telemetry endpoints outside Atlassian's infrastructure.
What data E-SignSeal stores
Data type | Where it is stored | Who can access it |
|---|
Template content (contract text + field configuration) | Forge Storage | Template Managers, Workspace Admins |
Envelope metadata (title, signer list, settings, status) | Forge Storage | Senders (own), Workspace Admins (all) |
Contract document (resolved HTML) | Forge Storage | Contract participants + admins |
Audit trail events | Forge Storage | Contract participants + admins |
OTP codes (during active session) | Forge Storage (ephemeral, 5-min TTL) | Not exposed to any user |
Signed PDF | Jira issue attachment (via Atlassian API) | Jira issue access controls apply |
Signer identity (Jira user IDs) | Forge Storage + resolved via Jira API at read time | Contract participants + admins |
Signed PDF attachment
When a contract is completed, the sealed PDF is written to the linked Jira issue as an attachment using the standard Jira attachments API (write:jira-work scope). The PDF is subject to Jira's existing issue-level permissions:
Users with Browse Projects permission for the issue can view the attachment.
Users with Delete Attachments permission can delete it — but deleting the attachment from Jira does not affect the audit trail in E-SignSeal.
OTP code handling
One-time passcodes are:
Generated server-side using HMAC-SHA256 with a per-envelope secret key
Stored ephemerally in Forge Storage with a 5-minute TTL
Never exposed in API responses, logs, or notifications (only the 6-digit code is sent to the signer's email via Atlassian's notification infrastructure)
Invalidated immediately on verification or on expiry, whichever comes first
Data scopes used
E-SignSeal requests the minimum Jira OAuth scopes required to function:
Scope | Why it is needed |
|---|
storage:app
| Read and write envelope, template, and audit data in Forge Storage |
read:jira-work
| Read issue field values to resolve merge fields at send time |
write:jira-work
| Attach the sealed PDF to the linked Jira issue on completion |
read:jira-user
| Resolve Jira user display names and emails for signer lookup and OTP delivery |
manage:jira-configuration
| Read project-level configuration to populate the Projects settings tab |
E-SignSeal does not request write access to Jira issues beyond attachment creation. It does not modify issue fields, status, or comments.
Data retention
E-SignSeal data persists in Forge Storage for as long as your Jira site is active. There is no automatic data purge. If you uninstall E-SignSeal from your Jira site, Forge Storage is cleared according to Atlassian's Forge data lifecycle policy — currently, app data is deleted when the app is uninstalled.
Signed PDFs attached to Jira issues are not deleted when E-SignSeal is uninstalled; they remain as standard Jira attachments.
Your responsibilities
E-SignSeal provides the technical infrastructure for secure, Atlassian-native e-signature. You are responsible for:
Ensuring signers are valid parties to the agreements they sign
Complying with applicable e-signature laws in your jurisdiction (such as eIDAS in the EU, ESIGN and UETA in the US)
Retaining signed PDFs according to your organization's record-keeping policies
Next steps