Effective and last updated: September 1, 2026
These measures are Accord’s Security Measures under the customer agreement and Data Processing Addendum. They apply to the current production version of Accord.
Where Accord runs
Accord is built on Atlassian Forge, the platform Atlassian provides for running apps inside Jira. Atlassian hosts the app and its stored review data. Accord does not operate a separate application server or database.
Atlassian provides Forge infrastructure security, tenant partitioning, encryption in transit and at rest, persistent-storage durability and backup, platform monitoring, and eligible data-residency controls. Provider remains responsible for Accord’s code, permissions, authorization rules, data choices, dependency management, releases, and incident response. Atlassian’s certifications cover Atlassian services within their stated scope; Accord is not separately certified under SOC 2 or ISO 27001.
What Accord stores
Accord keeps only the information needed to organize reviews:
- the identifying numbers Jira uses for tickets, projects, and accounts;
- your review plans and forms;
- who a review is assigned to and when it is due; and
- scores, reviewer notes, and the status of each review.
Accord does not store ticket descriptions, comments, attachments, customer messages, customer email addresses, or complete copies of tickets.
Access controls
Accord checks both the person’s role in Accord and their existing Jira access. Reviewers see work assigned to them. Support team members see only finished reviews of their own tickets. Live Jira ticket content is shown only when the person can already open the ticket in Jira. If that access is later removed, an authorized person may still see the stored QA record, but Accord does not show the restricted live Jira content.
- Atlassian authenticates users; Accord identifies them by Atlassian account ID, not email address.
- Every sensitive app request is authorized on the server. Hiding a page or button is not treated as authorization.
- Live Jira ticket content is requested in the current user’s Jira context. Accord does not use app authority to reveal content the user cannot browse.
- Draft scores and notes are limited to authorized reviewers and administrators. Agents can see only their own submitted results, never draft reviews.
- Submitted reviews are immutable. Corrections are made by voiding a review with a recorded reason rather than rewriting history.
Application safeguards
- No external app-data egress: Accord declares no remote backend, external database, analytics vendor, advertising service, AI provider, or customer-data logging destination.
- Data minimization: stored Jira data is limited to identifiers and review metadata needed for the workflow. Jira descriptions, comments, attachments, customer messages, and customer email addresses are not persisted.
- Input and output safety: IDs, roles, dates, Jira search rules, scores, and reviewer text are validated at server boundaries. User-controlled text is rendered as text, not raw HTML. Browser errors use stable codes and do not expose stack traces.
- Tenant separation: Forge storage is partitioned by app installation. Accord has no cross-customer data query or shared customer database.
- Software supply chain: releases are subject to TypeScript, automated test, lint, production dependency advisory, license, secret, source-policy, bundle, and Forge manifest checks. Production builds do not include source maps.
- Privacy lifecycle: Accord reports stored Atlassian account IDs to Atlassian’s privacy API and removes or de-identifies closed accounts as required.
Customer responsibilities
Customers must manage Jira accounts and permissions, promptly remove access that is no longer needed, limit Accord administrator and reviewer roles, review the app’s requested scopes, keep supported Atlassian and browser versions, avoid sensitive data in reviewer notes, and report suspected compromise promptly. Accord’s controls do not correct an overly broad Jira permission or an authorized user’s misuse.
Report a possible security problem
Email security@accordquality.com with:
- a short explanation of the problem and what it could affect;
- safe steps we can follow to see the problem;
- whether you believe anyone has already used the problem; and
- a safe way to contact you with questions.
Do not disrupt service, use denial-of-service or social-engineering techniques, access data that is not yours, retain personal data, or publicly disclose an unresolved issue. Stop testing and contact us if you encounter customer data. Provider will not pursue a claim against good-faith research that follows these rules, avoids harm, and gives Provider reasonable time to investigate and fix the issue, except where Provider is legally required to act.
What happens after you report it
We will acknowledge a report that appears genuine, preserve appropriate evidence, investigate scope and cause, contain the issue, coordinate with Atlassian where needed, remediate it, and keep the reporter informed when we need more information. Vulnerabilities will be handled within Atlassian’s required Marketplace remediation periods.
Where the Accord DPA or applicable law requires notice, Provider will notify an affected Customer without undue delay and, for a Security Incident covered by the DPA, within its 72-hour Specified Notice Period. An initial notice may contain the information then available and be supplemented as the investigation continues. Notice is not an admission of fault.
Changes
Provider may update these measures to reflect platform, product, risk, or legal changes, but will not materially reduce the overall level of security during a current paid Subscription Term unless necessary to address an urgent threat or required by law.