| Excerpt | ||||
|---|---|---|---|---|
| ||||
This is our privacy policy for all our apps and websites. |
This is our privacy policy for all our apps and websites, as of October 2ndJune 26th, 20192023. By using our products:
You agree that your information may be used according to the following policy,
You agree that your information may be used according to the Security Policy,
You agree to the Terms of Use (for cloud products) or to the End-User License Agreement (for downloadable products),
You agree that Atlassian is not responsible for the privacy, security or integrity of Vendor-Collected End User Data.
...
What information we collect
We mostly gather information through support cases. We also receive information from Atlassian through licenses ("Atlassian-collected end-user data"), Jira support issues, and from Google Analytics which we use our websiteswebsite tracking tools such as Google Analytics, Fullview, or other session-recording tools.
We host data created by users in our Cloud apps.
We don't gather collect any data when apps are installed by the customers on their own server, with the exception of the "feedback job" in Play SQL Base, explained in the table below.
...
Atlassian is not responsible for the privacy, security or integrity of Vendor-Collected End User Data.
Mode | Product | Status | Framework | Atlassian-collected end-user data (1) | Vendor-collected end-user data (1) | |
|---|---|---|---|---|---|---|
Data containing PII(3) | Other collected data, in normal usage | |||||
Cloud | Requirement Yogi | Paid | Atlassian Connect using Atlassian's official ACSB. | The license subscription information | None | Application data(2) (the requirements, page IDs, page titles, Jira issues) |
Cloud | Requirement Yogi for Jira | Paid | The license subscription information | None | Application data(2) (the requirements text, page IDs, page titles, Jira issues) | |
Server / DC | Requirement Yogi | Paid | Atlassian P2 plugins | The license subscription information | None | None |
Server / DC | Requirement Yogi for Jira | Free | None | None | None | |
Server / DC | RY Testing & Compliance | Paid | The license subscription information | None | None | |
DC | RY-Comala integration | Paid | The license subscription information | None | None | |
Server / DC | PSEA - Play SQL Export Add-on | Free | None | None | None | |
Server / DC | SEO Manager | Free | None | None | None | |
Server / DC | Play SQL Base | Free | None | None since 3.1.2(4) | None | |
Server / DC | Play SQL Spreadsheets | Free | None | None since 3.1.2(4) | None | |
Server / DC | Play SQL Forms | Free | None | None | None | |
Server / DC | ReqIF extension for Requirement Yogi | Free | None | None | None | |
(1) As defined in Atlassian Marketplace Publisher Agreement, section §8.4: Generally the company name, country, address, technical email, licensing email, reseller details, license number, etc.
...
(4) There used to be a feedback job in Play SQL Base and Play SQL Spreadsheets. This feedback job was removed in version 3.1.2 (see the history of this page).
What other data is collected?
...
In the situation where the company or one product is sold to a new owner: We sign a mutual NDA before the negotiation. Upon ownership transfer, the new owner takes responsibility for respecting or updating the current licenses and privacy policy.
In the situation where someone illegally accesses our systems, we cannot provide control about your data,
In the situation where we are compelled by law to provide this information, we cannot provide control about your data.
Here is what we allow:
Information | Founder | Employees under confidentiality agreement | Contractors | Accountant |
|---|---|---|---|---|
Billing | Yes | No | No | Yes |
Application Data | Yes | Yes | Yes | No |
Web Analytics | Yes | Yes | No | No |
Support | Yes | Yes | No | No |
How we host and transfer data internationally
...
We try to delete data as early as possible, except for backups which we keep a little longer.
License information | License information is provided to us by Atlassian every time we need it. If Atlassian starts limiting the history, then we will store it for up to 2 years, mainly for accounting purposes. |
|---|---|
User-created data in our Cloud apps | We delete data from the active databases as soon as the addon is uninstalled. We keep a backup of customer data for up to 2 months. |
...
Subprocessors, where we keep information
...
, how it is transferred internationally
| Anchor | ||||
|---|---|---|---|---|
|
| Anchor | ||||
|---|---|---|---|---|
|
Our products are generally hosted by Amazon AWS and Digital Ocean, except our website which is managed by OVH, France. The computers we use to create software and access your information are located in France.
Type | Product | Where it is hosted | Link | Data Processing Addenum | Implementation date |
|---|---|---|---|---|---|
Data from Cloud products | Requirement Yogi | Amazon AWS |
| Pre-2022 | |
Web | Our website | OVH, France |
Mailing lists
All
Pre-2022 | |||||
Web | Cloudflare | USA | 2023 | ||
Web | Google Analytics 4 | Europe | Data is stored in Europe | 2023 | |
Web | Google Tag Manager Google Ads | Europe | 2023 | ||
Web | Fullview | Europe | Data is stored in Europe | 2023 | |
Support data | Slack | USA |
2019-01-29 MailChimp DPA.pdfSupport data | Jira and Confluence | Europe | - | - | - |
Mailing lists | Hubspot | USA | 2023 | ||
Mailing lists | Mailchimp | Not used anymore since 2023. | |||
Fastmail | Fastmail, Australia / USA. | ||||
Pre-2022 | |||||
Administrative documents | Encrypted backups of our administrative documents, invoices, work documents. | SpiderOak, USA | https://spideroak.support/hc/en-us/articles/360002173891-GDPR-and-SpiderOak | Pre-2022 | |
Desktop | Our computers, our company, etc. | Encrypted laptops, desktops and hard drives, | |||
Carried by our employees and consultants. | Pre- | ||
We plan to use Amazon Web Services in the future for several of those services.
2022 |
How to access and control your information
...
If any process is not automated or you do not know how to exercise your rights, you may exercise them by contacting Adrien Ragot at:
Requirement Yogi - Responsable GDPR 535 route des Lucioles Les Aqueducs B3 06560 Sophia Antipolis France |
How we update this policy
We may update this policy without notice, for the purposes of being more specific, reflecting a new practice or complying to legal requirements.
Change log:
October 17th, 2023: Added Fullview, Google Tag Manager, Google Analytics 4,
February 15th, 2022: Added Amazon AWS and Requirement Yogi Cloud, and removed cloud products which have been shut down. Added a specific section for Requirement Yogi Cloud.
October 2nd, 2019: Added SpiderOak for our backups; Reflected the removal of support-requests-through-the-app features.
January 29th, 2019: Rewrite, to comply with Atlassian's request for updated policies, to have one policy for all products, to be specific on the location of your data, and to reflect up-to-date information.
September 11th, 2015: Add sections "What data we have", "Who accesses the data", "How we keep our servers secure", "How you can opt out" - see page history.
November 11th, 2013: Rewrite, to go from generic statements to specific ones.
October 2nd, 2013: Original version.
...