1 Hosting & Cloud Architecture
InsightLog is built entirely upon Atlassian Forge, Atlassian's next-generation serverless application framework. Unlike legacy Atlassian Connect apps that require external third-party infrastructure (e.g. Heroku, AWS, or custom servers), InsightLog executes entirely within Atlassian's managed cloud infrastructure.
2 Data Storage & Tenant Isolation
Application configurations (such as holiday schemes, team setups,
custom report templates, and settings) are stored within Atlassian
Forge's native Key-Value Storage (storage:app).
- Strict Tenant Isolation: Every storage key is strictly partitioned by Atlassian at the tenant boundary. It is mathematically and architecturally impossible for one Jira instance to access or query keys belonging to another instance.
- Jira As Source of Truth: Actual worklog entries (issue keys, time spent, timestamps, and work categories) are written directly into native Jira worklogs using standard Atlassian APIs.
3 Data Encryption Standards
Encryption at Rest
All data stored in Forge Key-Value Storage and native Jira worklog fields is encrypted using industry-standard AES-256 encryption, managed directly by Atlassian KMS.
Encryption in Transit
All communication between the user's browser, Jira Cloud, and Forge serverless handlers is enforced over TLS 1.3 / HTTPS with modern cipher suites.
4 Authentication & Access Control
InsightLog leverages native Jira Cloud authentication and OAuth 2.0 user tokens.
-
User Context Execution (
api.asUser()): Worklog submissions and issue searches execute exclusively in the context of the currently authenticated Jira user. Users cannot view, log, or edit issues for which their Jira account does not have explicit permission. - Role-Based Access Control: Team settings and global configurations require Jira Administrator privileges. Regular team members can only inspect and manage their own timesheets.
5 Network Egress & Third-Party Integrations
Atlassian Forge enforces a strict declarative network egress policy
defined in manifest.yml. InsightLog does not maintain
unauthorized network connections or embed external tracking pixels.
AI Assistant Processing: When using the Gemini AI worklog parser, only the unstructured natural language prompt typed into the bar is transmitted to the declared API endpoint over encrypted TLS for entity extraction. No proprietary code repositories or customer Jira backlogs are ingested.
6 Privacy Policy & GDPR Compliance
InsightLog respects individual privacy and adheres strictly to European General Data Protection Regulation (GDPR) and global privacy benchmarks:
- Data Controller vs Data Processor: The customer organization is the Data Controller. InsightLog acts strictly as a software processor operating inside the customer's Jira tenant.
- Right to Erasure: Because all worklogs are stored natively in Jira, deleting worklogs or uninstalling the app permanently purges associated metadata from the Forge tenant.
- Zero Data Brokerage: We never sell, monetize, or share customer time tracking data with advertising networks or third parties.
7 Responsible Disclosure & Contact
We welcome reports from independent security researchers. If you discover a potential vulnerability in InsightLog, please submit your findings to our security team at:
We respond to all verified security inquiries within 24 business hours.