
Riffle Data Processing Agreement
Riffle Resilience Inc
Effective Date: 4/12/2026
Updated Date: 11/11/2026
This Data Processing Addendum (“DPA”) applies to the applications listed in Annex 1 (the “Apps”), published on the Atlassian Marketplace by Riffle Resilience Inc. (“Riffle,” “we,” “us,” or “our”).
This DPA forms part of the agreement under which Riffle provides each App and applies without a separate signature. It is the “Riffle Data Processing Addendum” referred to in Section 16 of the Riffle Additional Terms for Atlassian Marketplace.
Customers whose procurement processes require a countersigned copy may request one using the contact information in Section 15.
The main provisions of this DPA apply to every App. The annexes form part of this DPA:
-
Annex 1: Details of the processing for each App.
-
Annex 2: Technical and organizational security measures.
-
Annex 3: Subprocessors and separate product analytics disclosures.
1. Definitions
For purposes of this DPA:
Agreement: The Bonterms Standard End User Agreement (for Marketplaces), together with the Riffle Additional Terms for Atlassian Marketplace, under which the Customer uses an App.
Additional Terms: The Riffle Additional Terms for Atlassian Marketplace.
Apps: The Riffle applications listed in Annex 1. Each application is an “App.”
Customer: The organization that installs and uses an App.
Personal Data, Controller, Processor, Data Subject, Processing, Personal Data Breach, and Supervisory Authority: These terms have the meanings given to them under the GDPR.
GDPR: Regulation (EU) 2016/679 and, where applicable, the UK GDPR.
CCPA: The California Consumer Privacy Act of 2018, as amended, and its implementing regulations.
Data Protection Laws: The GDPR, the CCPA, and any other data protection or privacy laws applicable to the processing of End User Data under this DPA.
End User Data: Personal Data that Riffle processes on the Customer’s behalf in connection with an App, as described in Annex 1.
Riffle Personnel: Riffle’s employees and authorized contractors acting under Riffle’s authority and bound by confidentiality obligations.
Subprocessor: Another processor engaged by Riffle to process End User Data.
2. Roles and Scope
2.1 Roles of the Parties
For End User Data, the Customer acts as the Controller and Riffle acts as a Processor operating on the Customer’s documented instructions.
Where the Customer acts as a Processor for another Controller, Riffle acts as the Customer’s Subprocessor. The Customer is responsible for ensuring that it is authorized to appoint Riffle and provide the instructions contemplated by this DPA.
Where the CCPA applies and the Customer acts as a “business,” Riffle acts as a “service provider.”
2.2 Customer Instructions
The Customer’s documented instructions consist of the Agreement, this DPA, and the Customer’s use and configuration of each App, as described in Annex 1.
Riffle will inform the Customer without undue delay if, in Riffle’s opinion, an instruction infringes Data Protection Laws.
2.3 Customer Responsibilities
The Customer is responsible for:
-
Establishing a lawful basis for Personal Data entered into or synchronized through an App;
-
Providing required notices to Data Subjects;
-
Ensuring that its instructions and use of the Apps comply with Data Protection Laws;
-
Managing its users, permissions, retention settings, and deletion instructions; and
-
Not submitting special categories of Personal Data or regulated data prohibited by Section 7 of the Additional Terms, unless expressly permitted under a separate written agreement establishing the necessary protections.
2.4 Processing Outside This DPA
This DPA does not govern Personal Data for which Riffle acts as an independent Controller, as described in the Riffle Privacy Policy.
Such information includes website and business contact information, sales and support correspondence, and the limited pseudonymous product usage analytics described in Annex 3.
End User Data accessed or processed to provide customer-authorized technical support remains subject to this DPA.
3. Details of the Processing
Annex 1 describes, for each App:
-
The subject matter, nature, and purpose of processing;
-
The duration of processing;
-
The Customer’s instructions;
-
The categories of Personal Data;
-
The categories of Data Subjects; and
-
Applicable export, retention, and deletion functions.
4. Riffle’s Obligations
Riffle will:
-
Process End User Data only on the Customer’s documented instructions, including instructions concerning international transfers, unless processing is required by applicable law. In that case, Riffle will inform the Customer of the legal requirement before processing unless the law prohibits such notice;
-
Not use End User Data for advertising, marketing, or purposes unrelated to providing, securing, and supporting the Apps;
-
Not use End User Data to train generative artificial intelligence models;
-
Ensure that every person authorized to process End User Data is bound by an appropriate duty of confidentiality;
-
Implement and maintain the technical and organizational measures described in Section 5 and Annex 2;
-
Engage Subprocessors only as described in Section 6;
-
Assist the Customer, taking into account the nature of the processing, through appropriate technical and organizational measures insofar as possible, in responding to Data Subject requests as described in Section 7;
-
Assist the Customer, taking into account the nature of the processing and the information available to Riffle, in meeting its obligations concerning security, breach notification, data protection impact assessments, and prior consultation with a Supervisory Authority;
-
Make available information reasonably necessary to demonstrate compliance with this DPA and allow for audits as described in Section 9; and
-
Delete or return End User Data at the end of the engagement as described in Section 11.
5. Security
Riffle implements and maintains the technical and organizational measures described in Annex 2.
These measures are designed to provide a level of security appropriate to the risk, taking into account the state of the art, implementation costs, and the nature, scope, context, and purposes of processing.
Riffle may update these measures over time, provided that the changes do not reduce the overall level of protection for End User Data.
6. Subprocessors
6.1 Authorized Subprocessors
The Customer grants Riffle general written authorization to use the Subprocessors listed in Annex 3.
6.2 Changes to Subprocessors
Riffle will provide at least 14 days’ advance notice of an intended addition or replacement of a Subprocessor by updating this page and announcing the change in the Atlassian Marketplace listing notes of each affected App.
The Customer may object on reasonable data protection grounds by contacting Riffle using the information in Section 15.
The parties will work in good faith to address the objection. If the objection cannot be resolved, the Customer may terminate its use of the affected App by uninstalling it.
6.3 Subprocessor Obligations
Riffle will enter into written arrangements with its Subprocessors imposing data protection obligations substantially equivalent to those applicable under this DPA.
Riffle remains responsible for its Subprocessors’ performance of those obligations to the extent required by Data Protection Laws.
7. Data Subject Requests
End User Data is maintained within the Customer’s Atlassian environment and the associated Forge-hosted App storage, and, where applicable, in the Customer’s connected systems.
The Customer may use the available tools described in Annex 1 to respond to requests for access, correction, export, and erasure.
Where a request cannot be fulfilled using those tools, Riffle will provide reasonable assistance without undue delay, taking into account the Customer’s applicable response deadlines.
If a Data Subject contacts Riffle directly about End User Data, Riffle will:
-
Refer the request to the Customer without undue delay; and
-
Not respond on the merits of the request except on the Customer’s documented instructions or where required by law.
8. Personal Data Breaches
8.1 Notification to the Customer
Riffle will notify the Customer without undue delay and, in any event, within 48 hours of becoming aware of a Personal Data Breach affecting End User Data.
Riffle will provide the information reasonably available to it, including:
-
The nature of the breach;
-
The categories and approximate number of Data Subjects concerned;
-
The categories and approximate number of Personal Data records concerned;
-
The likely consequences;
-
The measures taken or proposed to address the breach and mitigate its effects; and
-
A contact point for further information.
Where all information is not available at the time of the initial notice, Riffle will provide additional information in phases without undue further delay.
Notification will be sent to the administrator contact associated with the Customer’s installation or support relationship.
For incidents involving the Atlassian Forge platform, Riffle relies in part on information provided by Atlassian. This does not change Riffle’s notification obligations once Riffle becomes aware of a Personal Data Breach affecting End User Data.
8.2 Customer Responsibilities
The Customer remains responsible for assessing and fulfilling its obligations to notify the relevant Supervisory Authority and affected Data Subjects.
Riffle will provide reasonable assistance to the Customer in meeting those obligations.
9. Audits and Information
Riffle will make available information reasonably necessary to demonstrate compliance with this DPA.
Riffle will allow for and contribute to audits, including inspections, conducted by the Customer or an independent auditor appointed by the Customer.
Audits are subject to reasonable advance written notice, applicable confidentiality obligations, and reasonable measures to protect other customers’ information and the security of the Apps.
Ordinarily, audits may occur no more than once per year. This limitation does not apply following a Personal Data Breach, where a Supervisory Authority requires an audit, or where additional audits are necessary to comply with Data Protection Laws.
Riffle may provide an available, current third-party audit report, such as a SOC 2 Type II report, to address an audit request where that report is sufficient. Providing a report does not remove audit rights that must be preserved under Data Protection Laws.
Relevant evidence may include:
-
The Riffle Privacy Policy;
-
This DPA;
-
Each App’s Atlassian Marketplace Privacy and Security information;
-
Relevant App configuration and security documentation;
-
Each App’s manifest; and
-
Atlassian’s compliance information for its hosting platform, available through the Atlassian Trust Center.
Atlassian’s certifications and audit reports relate to Atlassian’s services and do not represent a separate certification or audit of Riffle.
10. International Transfers
Eligible Forge-hosted persistent storage follows the Customer’s supported Atlassian data residency settings.
Other processing locations are governed by Atlassian’s applicable platform arrangements. A storage residency setting does not guarantee that every processing activity occurs exclusively within that region.
Riffle does not maintain an independent copy of End User Data in Riffle-operated hosting systems. However, customer-authorized support access and processing by platform providers may involve international transfers. Customer-configured synchronization also involves exchanging data with the Customer’s ServiceNow instance.
Where processing under this DPA involves an international transfer requiring safeguards under Data Protection Laws, the applicable parties will establish the required transfer mechanism before that transfer occurs.
Such mechanisms may include an applicable adequacy decision or appropriate contractual safeguards, including the applicable EU Standard Contractual Clauses and, where required, a UK International Data Transfer Addendum or International Data Transfer Agreement.
Atlassian’s international processing as a Subprocessor is subject to its applicable Data Processing Addendum and transfer safeguards.
Those arrangements do not automatically replace any separate transfer safeguards required between the Customer and Riffle. Where additional safeguards are required, they must be established in the applicable contractual arrangements.
11. Deletion and Return of Data
11.1 Customer Choice and Export
At the end of the relevant services, Riffle will, at the Customer’s choice, return or delete End User Data and delete existing copies, unless applicable law requires continued storage.
Return may be provided through the export functions described in Annex 1. Where those functions do not adequately support the Customer’s request, Riffle will provide reasonable assistance.
Customers should complete required exports before uninstalling an App.
Riffle does not maintain an independent repository of End User Data outside the hosting arrangements described in this DPA.
11.2 Deletion During Use
The retention periods and deletion functions of each App are described in Annex 1.
Removing a user’s access does not necessarily delete that user’s Personal Data from records, attachments, history, or other content. The Customer must consider those records separately when responding to an erasure request.
11.3 Uninstalling an App
After uninstallation, Forge-hosted storage associated with the installation becomes subject to Atlassian’s platform retention and deletion lifecycle.
Atlassian currently documents a 28-day post-uninstallation retention period for Forge-hosted storage, during which recovery may be available through its supported recovery process.
Permanent deletion, including the handling of retained copies and backups, follows Atlassian’s applicable retention and disposal policies. These platform timelines are controlled by Atlassian rather than Riffle.
This DPA continues to protect End User Data retained during the applicable deletion period. Retained data will not be used for unrelated purposes.
Uninstalling an App does not itself delete records held separately in the Customer’s Jira Service Management Assets or ServiceNow systems.
11.4 Diagnostic Logs
Diagnostic logs expire under the applicable Forge platform retention schedule. To the extent those logs contain End User Data, they remain subject to this DPA.
11.5 Legally Required Retention
Where applicable law requires continued storage, Riffle will retain only the data required, protect it under this DPA, and limit further processing to the legally required purpose.
12. CCPA Service Provider Terms
To the extent the CCPA applies, the Customer discloses End User Data to Riffle only for the limited and specific business purposes described for each App in Annex 1.
Riffle will:
-
Not sell or share End User Data;
-
Not retain, use, or disclose End User Data for any purpose, including a commercial purpose, other than those specified business purposes, except as permitted by the CCPA;
-
Not retain, use, or disclose End User Data outside the direct business relationship with the Customer, except as permitted by the CCPA;
-
Not combine End User Data with Personal Data received from another source or collected through Riffle’s own interactions with individuals, except as permitted by the CCPA;
-
Comply with CCPA obligations applicable to service providers and provide the level of privacy protection required by the CCPA;
-
Notify the Customer if Riffle determines that it can no longer meet its obligations under the CCPA;
-
Assist the Customer in responding to consumer requests, as described in Section 7; and
-
Require any subcontractor processing End User Data to accept written terms meeting the CCPA’s requirements.
The Customer may take reasonable and appropriate steps to ensure that Riffle uses End User Data consistently with the Customer’s CCPA obligations, including the measures described in Section 9.
Upon notice, the Customer may also take reasonable and appropriate steps to stop and remediate unauthorized use of End User Data.
Riffle certifies that it understands and will comply with the restrictions in this Section.
13. Liability
Each party’s liability arising out of or related to this DPA is subject to the limitations and exclusions of liability in the Agreement, except to the extent prohibited by Data Protection Laws or inconsistent with applicable mandatory transfer safeguards.
Nothing in this DPA limits rights or liabilities that cannot lawfully be limited.
14. Term, Precedence, Governing Law, and Changes
14.1 Term
This DPA forms part of the Agreement governing the Customer’s use of each App.
For new installations, it applies when the Customer installs the App. For existing installations, this version applies in accordance with the Agreement’s applicable notice and change provisions.
This DPA remains in force for as long as Riffle processes End User Data on the Customer’s behalf, including any applicable retention and deletion period.
14.2 Precedence
If this DPA conflicts with the Agreement regarding the processing of Personal Data, this DPA prevails for that subject matter.
The annexes specify the processing arrangements for each App. An App-specific provision prevails for that App only to the extent it does not reduce the protections required by the main provisions of this DPA or Data Protection Laws.
Where applicable mandatory transfer clauses conflict with this DPA, those clauses prevail to the extent required by their terms.
14.3 Governing Law
This DPA is governed by the same governing law as the Agreement, except where Data Protection Laws or applicable mandatory transfer safeguards require otherwise.
14.4 Changes to This DPA
Riffle will post changes on this page and update the effective date, updated date, and version.
Material changes will be announced in the Atlassian Marketplace listing notes of each affected App and communicated through any additional notice mechanism required by the Agreement or Data Protection Laws.
Subprocessor changes remain subject to Section 6.2.
15. Contact Information
Riffle Resilience Inc.
Attention: Privacy and Data Protection
9 Bancroft Road
Andover, MA 01810
United States
Data protection inquiries, breach notifications, and requests for a countersigned DPA:
privacy@riffleresilience.com
Security reports, vulnerability reports, and application support:
support@riffleresilience.com
Website:
www.riffleresilience.com
Annex 1: Details of the Processing
Part A: Riffle Operational Resilience
Subject Matter and Nature
Storing, organizing, displaying, searching, exporting, and deleting operational resilience records created by the Customer’s users, including:
-
Value streams;
-
Assets and dependencies;
-
Impact analyses;
-
Recovery plans;
-
Restoration sequences;
-
Exercises; and
-
Incident events.
Processing also includes recording changes for the Customer’s audit trail, reading the Customer’s Jira users and, where enabled, Jira Service Management Assets objects, and answering questions or preparing drafts through Atlassian Rovo when requested by a user.
Purpose
Providing the App’s operational resilience and business continuity planning service, including securing the App and supporting the Customer’s use of it.
Duration
The period during which the App is installed on the Customer’s Atlassian site, together with the applicable retention and deletion periods described in Section 11.
Customer Instructions
Instructions are provided through the App’s use and configuration, including:
-
Content entered by users;
-
Roles assigned by program owners;
-
Retention periods and trash policies selected by program owners; and
-
Exports and deletions initiated by authorized users.
A “program owner” is a Customer user holding the administrator role within the App.
Categories of Personal Data
The App processes the following categories of Personal Data:
-
App users: Atlassian account ID, cached display name and avatar, App role, team memberships, and assignments. Atlassian user email addresses are not retained in the user list; they may be stored in contact lists or imported records.
-
Access requests: Requester’s account ID, cached name and avatar, and request message.
-
Plans, assessments, and other records: Account IDs of owners, approvers, and assignees; user-entered text; and contact lists containing names, email addresses, telephone numbers, and other contact details, including contacts outside the Customer’s organization.
-
Announcements, direct messages, and system notifications: Sender and recipient account IDs, cached names, and message content.
-
Change history and approval evidence: The identity of the person taking an action, the action and time, and values before and after a change, which may include user-entered text.
-
Attachments: User-uploaded files and the uploader’s account ID.
-
Usage events stored within the App: The feature used and the associated account ID.
-
Export and import records: The account ID of the user initiating a job, copies of rows replaced by an import, and mappings between people named in imported files and the Customer’s users, which may include names and email addresses.
-
Jira Service Management Assets search index: Object keys, labels, types, and owners copied into a search index where the Customer enables this feature.
Categories of Data Subjects
-
The Customer’s employees, contractors, and other individuals with an Atlassian account on the Customer’s site, including Jira administrators;
-
Individuals named in plans and assessments as contacts, whether inside or outside the Customer’s organization; and
-
Individuals referenced in Jira Service Management Assets records used by the App.
Special Categories of Personal Data
The App is not designed or intended to process special categories of Personal Data.
The Customer must not enter such data in text fields, messages, notes, or uploaded files except where expressly permitted under the separate written arrangements described in Section 2.3.
AI Features
The App’s assistant uses Atlassian Rovo.
When a user requests assistance, content needed to respond is processed through Atlassian’s AI services under the applicable Atlassian terms and data processing arrangements.
Riffle does not send End User Data to a separately contracted AI provider.
Data Subject Requests
Program owners can:
-
Export a person’s data;
-
Correct plan content and contact lists;
-
Remove a person from the App; and
-
Run the personal data cleanup function for a person who has been removed.
Following that cleanup, the App retains a marker containing the person’s Atlassian account ID without their name. Text authored by that person remains within the Customer’s records.
The retained account ID and authored content may still constitute Personal Data. This cleanup function therefore does not, by itself, erase every reference to the person.
The Customer must assess whether additional correction or deletion of records, attachments, contact lists, or other content is required. Riffle will provide assistance as described in Section 7.
Export
Program owners can export the App’s data in a machine-readable JSON format while the App remains available to the Customer.
Retention and Deletion
The following periods describe application-level retention and cleanup. Deletion from active application storage remains subject to the platform’s applicable backup and disposal lifecycle.
Change History and Audit Records
Retained for 365 days by default.
The Customer may configure retention from 30 to 3,650 days under Settings → History.
Removed Users
Retained for 365 days after removal by default, followed by the personal data cleanup described above.
The Customer may configure retention from 30 to 3,650 days under Settings → Personal data cleanup.
Decided Access Requests
Retained for 365 days after the decision by default. Pending requests remain until decided.
The Customer may configure retention from 30 to 3,650 days under Settings → Personal data cleanup.
Announcements
Announcements with an expiry date are retained for 365 days after expiry by default. Announcements without an expiry date remain until deleted.
The Customer may configure retention from 30 to 3,650 days under Settings → Personal data cleanup.
Direct Messages and System Notifications
Retained for 365 days after sending by default.
The Customer may configure retention from 30 to 3,650 days under Settings → Personal data cleanup.
Usage Events Stored Within the App
Retained for a fixed period of 90 days.
Derived counts that contain no Personal Data are retained.
Export Job Records
Retained for a fixed period of seven days.
Import Undo Copies
Retained for a fixed period of 14 days.
Import Mapping Records
Retained until App uninstallation, followed by the platform deletion lifecycle.
There is no configurable retention setting. Requests requiring earlier action are handled under Section 7.
Plans, Assessments, Contact Lists, Assignments, Attachments, and Approval Evidence
Retained until deleted by the Customer’s users, subject to any applicable trash policy.
The Customer manages these records through the App’s deletion functions.
Trashed Records
Retained until permanently deleted by a program owner. Automatic deletion is off by default.
The Customer may enable automatic deletion after 1 to 3,650 days under Settings → Trash policy.
Active Users, Roles, and Teams
Retained while the relevant membership remains active and managed by program owners.
Removed-user data then follows the removed-user retention process.
Cleanup Schedule
Cleanup of removed users, access requests, announcements, and messages begins seven days after installation and runs daily thereafter.
Part B: Riffle Data Sync for JSM Cloud (Integration for ServiceNow®)
Subject Matter and Nature
Synchronizing configuration item (“CI”) records from the Customer’s ServiceNow configuration management database (“CMDB”) into Jira Service Management Assets on the Customer’s Atlassian site.
This includes keeping selected records aligned, including deletions.
Purpose
Providing the App’s synchronization service to the Customer.
Duration
The period during which the App is installed on the Customer’s Atlassian site, together with the applicable retention and deletion periods described in Section 11.
Customer Instructions
Instructions are provided through the App’s configuration, including the ServiceNow tables, columns, filters, and synchronization schedules selected by the Customer’s administrators.
Categories of Personal Data
-
ServiceNow connection information supplied by the Customer, including the instance URL, integration account username, and password;
-
CMDB data selected for synchronization, which may include person-identifying fields such as owner, assigned user, support group, or contact email;
-
Synchronization configuration and bookkeeping information, including table selections, filters, record identifiers, watermarks, and sanitized error summaries; and
-
The Atlassian account ID of the administrator configuring the App, checked transiently to verify permissions.
Categories of Data Subjects
The Customer’s employees, contractors, and other individuals referenced in the CMDB records selected for synchronization.
Special Categories of Personal Data
The App is not intended to process special categories of Personal Data.
The Customer must not configure the App to synchronize such data except where expressly permitted under the separate written arrangements described in Section 2.3.
Data Subject Requests
Synchronized Personal Data resides in the Customer’s ServiceNow and Jira systems.
The Customer can use those systems to address requests for access, correction, export, and erasure. Relevant changes take effect in Assets on the next synchronization or reconciliation, in accordance with the Customer’s configuration.
Export
Synchronized records remain accessible through the Customer’s Jira Service Management Assets and ServiceNow systems. The Customer may use the export capabilities available in those systems.
Retention and Deletion
Synchronized data remains under the Customer’s control in its Jira site.
Deleting an import removes its configuration. If the Customer chooses to delete the import’s data, the App’s built-in teardown removes the objects and object types it created.
Following uninstallation, stored credentials and configuration become subject to Section 11.3.
Uninstalling the App does not itself delete synchronized records from the Customer’s Jira Service Management Assets or ServiceNow systems.
Annex 2: Technical and Organizational Measures
Part 1: Measures Applicable to Both Apps
Hosting
The Apps run on Atlassian’s Forge platform.
Riffle operates no separate servers, databases, or storage for End User Data, and End User Data is not transmitted to Riffle-operated hosting systems.
Separate product analytics processing is described in Annex 3.
Separation of Customers
Each Customer’s App data is maintained in Forge-hosted storage associated with that Customer’s installation.
Encryption
Connections use HTTPS with TLS 1.2 or above.
Atlassian encrypts data in Forge-hosted storage at rest and in transit.
Access by Riffle Personnel
Riffle Personnel do not routinely access customer-created application information.
Access is limited to customer-requested troubleshooting, customer-authorized support, or temporary access specifically approved by the Customer, subject to applicable legal obligations.
Internal Security Practices
Access to systems used to develop and support the Apps is:
-
Granted on a need-to-know basis;
-
Protected by multi-factor authentication; and
-
Reviewed periodically.
Secure Development
Changes to the Apps undergo code review, automated testing, and dependency vulnerability scanning before release.
The Apps are subject to Atlassian’s security requirements for Marketplace cloud applications.
Part 2: Riffle Operational Resilience
Storage
End User Data is stored in Forge SQL, Forge Key-Value Store, and Forge Object Store.
Network Restrictions
The App’s manifest permits external analytics traffic to the provider described in Annex 3.
Other external destinations are blocked by the platform’s applicable egress controls. Atlassian-managed services operate under the platform’s own arrangements.
Identity and Access
Users are identified through their Atlassian accounts.
Access within the App is role-based, using program owner and subject matter expert roles, with permissions checked on the server.
Subject matter experts can access only items assigned to them. Settings, exports, and permanent deletions are reserved for program owners.
Administrative Access
Initial setup and the emergency access page are restricted to Jira administrators.
Emergency access grants are recorded in an audit log.
Diagnostic Logging
Diagnostic logging is designed to minimize Personal Data.
Account IDs are replaced with keyed pseudonyms, and an automated test checks for log statements that would expose account IDs.
Pseudonymized information may remain Personal Data and is protected accordingly.
Pseudonymization
The key used to create pseudonyms is maintained as a Forge environment variable and is not written to logs or application storage.
Support Access
Support access to Customer data through the App requires the Customer to grant an appropriate role to a named person on the Customer’s Jira site.
Part 3: Riffle Data Sync for JSM Cloud
Credential Protection
ServiceNow credentials are maintained in Forge’s dedicated encrypted secret storage.
Credentials are not written to logs or returned through a user interface.
Network Restrictions
Outbound external network access is restricted by the App’s manifest to the Customer’s ServiceNow instance.
Other external hosts are blocked by the platform’s applicable egress controls.
Administrative Access
The App’s configuration interface is restricted to Jira administrators.
Permissions are verified on the server for every request.
Endpoint Security
The App’s two optional HTTP endpoints are protected by randomly generated, per-installation secrets.
Secrets are accepted only in request headers and compared using constant-time comparison.
Diagnostic Logging
Credentials are not logged, record identifiers are replaced with non-reversible fingerprints, and raw API response bodies are not logged.
Support Access
Access to an installation’s diagnostics is available only during a time-limited window granted by the Customer’s administrator.
Access is read-only and logged.
Annex 3: Subprocessors and Product Analytics
Part 1: Authorized Subprocessors
Subprocessor
Atlassian, including its applicable cloud hosting providers, principally Amazon Web Services, and providers used to deliver the relevant Atlassian services.
Applicable Apps
Both Riffle Operational Resilience and Riffle Data Sync for JSM Cloud.
Rovo functionality applies to Riffle Operational Resilience.
Role
Atlassian hosts App runtime, storage, and logs through Forge and provides the Rovo AI service under Atlassian’s applicable Data Processing Addendum and service terms.
Data Processed
Processing may involve all categories of End User Data described in Annex 1, as needed for the relevant service.
Processing Locations
Eligible Forge-hosted persistent storage follows the Customer’s supported Atlassian data residency settings.
Other platform processing, including runtime execution and Rovo, follows Atlassian’s applicable hosting, service, and data residency arrangements.
Other Providers and Customer Systems
Riffle has not directly appointed other Subprocessors for the processing covered by this DPA.
Atlassian’s use of its own providers is governed by its applicable contractual arrangements and subprocessor disclosures.
The Customer’s Jira site, Jira Service Management Assets environment, and ServiceNow instance are systems used under the Customer’s own contracts. Their use in that capacity does not itself constitute a separate appointment by Riffle.
This distinction does not alter Atlassian’s role as Riffle’s Subprocessor for the Forge and Rovo services described above.
Part 2: Product Usage Analytics
Applicable App and Provider
Riffle Operational Resilience sends limited pseudonymous product usage analytics to PostHog, Inc., which processes that information in the United States.
Riffle Data Sync for JSM Cloud does not send product usage analytics.
Processing Role
Riffle determines the purposes and means of the separate product analytics processing described here and acts as an independent Controller for that processing, as described in the Riffle Privacy Policy.
PostHog processes that information on Riffle’s behalf. For this separate processing, it is Riffle’s processor rather than a Subprocessor processing End User Data on the Customer’s behalf under this DPA.
This distinction does not mean that pseudonymous analytics is anonymous or exempt from Data Protection Laws.
Information Sent
Product analytics may include:
-
Feature and event names;
-
Counts and durations;
-
App version;
-
The user’s role within the App;
-
A hashed site identifier;
-
The Jira site hostname;
-
Forge environment identifiers;
-
A pseudonymous user identifier created using a keyed hash; and
-
Basic technical information added by the analytics library, such as browser and operating system type.
-
Information Not Sent
The analytics payload does not include:
-
Atlassian account IDs;
-
User names;
-
Email addresses; or
-
Content entered into the App by the Customer’s users.
The pseudonymous identifiers described above are distinct from raw Atlassian account IDs.
IP Addresses and Location
The App configures the analytics provider not to record IP addresses or location.
This setting does not imply that an IP address is never processed transiently to deliver a network request.
Customer Control
A Jira administrator can disable product analytics.
Privacy Information
The purposes, applicable rights, retention practices, and contact arrangements for this separate processing are described in the Riffle Privacy Policy.
.png)