Privacy policy
This policy explains how Dceniac Labs ("we", "us") handles information in connection with our Atlassian Cloud apps distributed through the Atlassian Marketplace — Dceniac Markdown Writer for Jira and Spreadsheet & Table Field for Jira (each an "App", and together the "Apps") — and in connection with support requests you send us.
In short: our Apps run entirely on Atlassian's Forge platform ("Runs on Atlassian"). We operate no external application servers, databases, or analytics for the Apps. Your Jira content and custom field values are read and written only inside your Jira site, and we never receive them.
1. What the Apps access
Dceniac Markdown Writer for Jira
When a user opens Dceniac Markdown Writer for Jira on a Jira issue, the App accesses the following through Jira's own APIs, acting as that user and limited to what that user is allowed to see and change in Jira:
- The issue's description and comments, to load them into the editor and save the user's changes.
- Attachments on the issue, to show images, upload images the user adds, upload rendered Mermaid diagrams, and remove images the App uploaded that are no longer referenced.
- User names and avatars, to suggest people when the user types an @mention.
- The App's license status, provided by Atlassian, to check whether the subscription is active.
Dceniac Markdown Writer for Jira requests these Jira permissions (scopes): read:jira-work, write:jira-work and read:jira-user.
Spreadsheet & Table Field for Jira
When an administrator configures a table custom field or a user views or edits an issue or Jira Service Management portal request containing the field, the App accesses only:
- The custom field's contextual schema configuration (column definitions, validation rules, and default template rows) via Jira's app-owned field configuration API (
/rest/api/3/app/field/{fieldId}/context/configuration), so standard Jira users and Jira Service Management portal customers can render and validate the active table layout on screen. To avoid redundant API calls during concurrent renders, column schemas may be held in a transient 3-second tenant-scoped in-memory cache inside the isolated Forge runtime; no issue values or personal data are cached. - The custom field's table value on the current issue or service request, provided directly by Jira's custom field host bridge and saved back into the Jira custom field value.
- The App's license status, provided by Atlassian, to check whether the subscription is active.
Spreadsheet & Table Field for Jira requests only a single read-only Jira permission (scope): read:custom-field-contextual-configuration:jira.
2. What we store
Nothing outside your Jira site. Neither App uses external databases, Forge KVS/SQL persistent storage, cookies, tracking pixels, or analytics, and neither App sends data to any external service. Everything saved by the Apps — such as issue descriptions, comments, image attachments, custom field schemas, and structured table rows — is stored natively in your Jira Cloud site.
Unsaved drafts in your browser. So that closing the editor by accident loses nothing, Dceniac Markdown Writer for Jira keeps unsaved description and comment text in your own browser's local storage. Drafts are separated by Jira site, user account and issue, are never sent to us or any other service, and are deleted when you save, discard or dismiss them, or automatically after 14 days. You can also remove them at any time by clearing your browser's site data.
Atlassian hosts and processes your Jira data, and runs the Apps' code, under Atlassian's privacy policy. Atlassian may provide us with aggregated Marketplace information such as install counts, and billing contact details for licenses, under its Marketplace terms.
3. Support requests
If you email us, we receive your email address, your message and anything you attach. We use this only to answer you and fix problems with the Apps. We keep support emails for as long as needed to resolve the request and for our records, and we delete them on request. We don't sell or share them, except with service providers needed to route and host our email (Cloudflare and Google).
4. Your rights
Because we don't hold your Jira content, requests to access, correct or delete it should go to your Jira site administrator, who can manage it in Jira, or to Atlassian. For information we hold about you from support emails, contact us and we'll respond within 30 days.
5. Security
The Apps inherit the security of Atlassian's Forge platform and cannot access any Jira site where they are not installed. Dceniac Markdown Writer for Jira calls Jira APIs exclusively with the permissions of the signed-in user; Spreadsheet & Table Field for Jira reads only the contextual configuration of custom fields owned by the App while Jira enforces all issue and portal access controls. To report a security issue, see our security and incident response plan.
6. Children
The Apps are business tools and are not directed at children.
7. Changes
If we change this policy, we'll update the date at the top. If a change means an App starts handling data differently, for example by sending data outside Jira, we'll say so in the App's Marketplace listing and release notes before it takes effect.
8. Contact
Dceniac Labs, support@dceniac.com.