← Dealkeep

Dealkeep for Jira: Privacy Policy

Effective date: October 1, 2026 Publisher: Great Work LLC, 651 N Broad St Suite 206, Middletown, DE 19709, USA Contact: hello@greatwork.company

This policy explains what information the Dealkeep app for Jira Cloud (the "App") processes, where it is kept, and your rights. It covers only the App, not Atlassian's products, which are governed by Atlassian's own privacy policy.

1. Summary

  • The App runs entirely on Atlassian's Forge platform ("Runs on Atlassian"). It has no servers of its own and sends no data to Great Work or to any third party.
  • Companies, contacts, deals, activity, issue links and settings are stored in your site's Forge SQL database, hosted by Atlassian. Linked issues carry a small dealkeep issue property so they can be searched with JQL.
  • CSV imports are read in your browser and sent only to your site's App; CSV exports are built in the browser and saved to the user's device.
  • Great Work LLC cannot see your customers, contacts or deals.

2. What the App processes

DataWhyWhere it lives
Companies: name, web domain, website, industry, phone, address, owner (Atlassian account id), tags, notes, created and updated timesThe CRM recordsForge SQL, until deleted or uninstall
Contacts: first and last name, email, phone, job title, company, owner, tags, notesThe CRM recordsForge SQL, until deleted or uninstall
Deals: name, value, currency, pipeline, stage, status, expected close date, lost reason, company, contact, owner, notes, stage and close timesPipeline, forecastForge SQL, until deleted or uninstall
Activity: notes, calls, meetings, emails and tasks users write (text, date, due date, assignee, author), and history entries the App writes (stage changes, merges, links)Timeline and tasksForge SQL, until the record is deleted or uninstall
Issue links: issue id and key, linked company, deal or contact, who linked it and whenLinked work, JQLForge SQL; plus the dealkeep issue property (company names, deal names, stage names, contact emails, open deal value) on the linked issue until unlinked or the issue is deleted
Settings: viewer and editor group names, currency, extra excluded email domains, pipelines and stagesTo run the AppForge SQL
Issue keys, summaries, status, type, assignee name, project, updated date, reporter email (if Jira shows it to the user) read to show linked work and suggest a companyLinked work, suggestionsIn the browser and in memory during the request
CSV files users importTo create or update recordsIn memory during the import
Your account id, groups and Jira admin permissionTo decide what you may see and changeIn memory only

The contact details your users enter are personal data about your customers. Your organization decides what to record and is the controller of that data; the App only stores it in your site.

The App does not read issue descriptions, comments, attachments, mailboxes or calendars, and it does not collect IP addresses, passwords, API tokens, payment card details or analytics. It sets no cookies and loads no third-party scripts or fonts.

3. Where data is stored

All App data is stored by Atlassian, in Forge SQL for your site and in issue properties on your Jira issues. Atlassian is the hosting provider and acts as a subprocessor under Atlassian's terms. Great Work LLC uses no other subprocessors. Data residency follows what Atlassian offers for Forge SQL and Jira (UNVERIFIED at time of writing: confirm Forge SQL's residency coverage on Atlassian's current Forge data residency page before stating it in the listing).

4. Who can see what

  • Your Jira admins choose which groups can see records and which can edit them (default: everyone with access to the App can see and edit). Jira admins always can.
  • Linked Jira issues are listed only to people who can browse them in Jira. Anyone who can see an issue can see its dealkeep issue property (company, deal and stage names, contact emails, open deal value) through Jira's REST API and JQL.
  • Great Work LLC: no access. If you open a support request, we see only what you send us.
  • Atlassian: as the platform operator, under Atlassian's privacy policy.

5. Retention and deletion

Records stay until a user deletes them. Deleting a company, contact or deal deletes its activity and issue links and updates the issue property; contacts and deals of a deleted company are kept without a company. Uninstalling the App removes its Forge SQL data according to Atlassian's Forge data deletion process. Export everything to CSV first if you need a copy.

To answer a request from one of your contacts (for example a GDPR erasure request), search for them in Dealkeep, export what you hold, and delete the contact.

6. Support requests

If you contact support through our help desk or by email, we process what you send (name, email, message, attachments) only to answer you, keep it up to 24 months, and delete it sooner on request. Please do not send customer records unless you need to.

7. Your rights

Depending on where you live (for example EU/UK GDPR or US state privacy laws), you may have the right to access, correct, delete or port personal data and to object to processing. For data in your Jira site, your organization (the Atlassian customer) is the controller and Atlassian processes it on your behalf. For support data, Great Work LLC is the controller: email hello@greatwork.company. We respond within 30 days.

8. Security

The App uses only Atlassian-hosted compute and storage, reads Jira as the signed-in person (the issue property is written as the App after the person's browse access is checked), re-checks every permission on the server, and keeps no secrets of its own. Report vulnerabilities to hello@greatwork.company.

9. Children

The App is a business tool and is not directed to children under 16.

10. Changes

We will post changes here and update the effective date. Material changes will also be announced in the App's Marketplace release notes.

11. Contact

Great Work LLC, 651 N Broad St Suite 206, Middletown, DE 19709, USA. hello@greatwork.company