Openwake · evidence pack

Atlassian

https://www.atlassian.com · record 703 · read 2026-10-22 · rules/v1 · generated 2026-10-23 04:14 UTC

Facts

Trains on customer data
yes
“To provide customer support: We use your information to resolve technical issues you encounter, to respond to your requests for assistance, to analyze crash information, and to repair and improve the Services, including for development, training, or fine-tuning of machine learning and artificial intelligence models.”
privacy policy · https://www.atlassian.com/legal/privacy-policy · confidence 0.55
Opt-out mechanism
* Where applicable under local law, you may have certain rights or choices with respect to your personal information, including to request information about our processing of information, to request a copy of your information, to object to our use of information, to request the deletion or restricti
“* Where applicable under local law, you may have certain rights or choices with respect to your personal information, including to request information about our processing of information, to request a copy of your information, to object to our use of information, to request the deletion or restriction of information, to request a disclosure of information in a portable format, or to opt out of certain disclosures of personal information and targeted advertising.”
privacy policy · https://www.atlassian.com/legal/privacy-policy · confidence 0.50
AI features
present
“We may use artificial intelligence in responding to your pricing, billing or licensing-related requests.”
privacy policy · https://www.atlassian.com/legal/privacy-policy · confidence 0.55
Model providers named
Google (Gemini / Vertex AI), OpenAI
“Google Vertex AI Applicable Cloud Products All Atlassian Cloud Products with enabled Atlassian Intelligence or Rovo”
subprocessors · https://www.atlassian.com/legal/sub-processors · confidence 0.60
Retention
not stated
No supporting text found in the documents read.
privacy policy · https://www.atlassian.com/legal/privacy-policy · confidence 0.20
Hosting regions
not stated
No supporting text found in the documents read.
privacy policy · https://www.atlassian.com/legal/privacy-policy · confidence 0.20
Subprocessor notice
not stated
No supporting text found in the documents read.
privacy policy · https://www.atlassian.com/legal/privacy-policy · confidence 0.20

Subprocessors (18)

NameCategoryLocationQuoted from
Amazon Web Serviceshyperscalerunstated
“Amazon Web Services, Inc. Applicable Cloud Products Atlas”
Loomotherunstated
“Loom Opsgenie Rovo”
Databricksotherunstated
“Databricks, Inc. Applicable Cloud Products Atlassian Guard (Access/Guard family)”
MongoDBotherunstated
“MongoDB, Inc. Applicable Cloud Products Jira Service Management Cloud (including Assets, JSM Chat/Assist, and JSM Operations)”
Salesforceotherunstated
“Salesforce, Inc. (Heroku) Applicable Cloud Products DX”
Herokuotherunstated
“Salesforce, Inc. (Heroku) Applicable Cloud Products DX”
Snowflakeotherunstated
“Snowflake, Inc. Applicable Cloud Products DX”
Mailgunotherunstated
“Mailgun Technologies, Inc. Applicable Cloud Products Jira Cloud (including Jira Software and Jira Work Management)”
Mailchimpotherunstated
“Mailchimp Applicable Cloud Products Loom”
Twiliootherunstated
“Twilio Inc. Applicable Cloud Products Bitbucket Cloud (including Bitbucket Pipelines)”
Cloudflareotherunstated
“Cloudflare, Ltd. Applicable Cloud Products Atlas”
Zendeskotherunstated
“Zendesk Applicable Cloud Products Loom”
Google (Gemini / Vertex AI)model providerunstated
“Google Vertex AI Applicable Cloud Products All Atlassian Cloud Products with enabled Atlassian Intelligence or Rovo”
OpenAImodel providerunstated
“OpenAI, L.L.C. Applicable Cloud Products All Atlassian Cloud Products with enabled Atlassian Intelligence, Loom AI, or Rovo”
Segmentotherunstated
“Twilio, Inc (Twilio-Segment) Applicable Cloud Products Loom”
CrowdStrikeotherUSA
“Crowdstrike Location of Processing USA”
OktaotherUSA
“Okta, Inc. Location of Processing USA”
TenableotherUSA
“Tenable Holdings, Inc. Location of Processing USA”

Sources read

DocumentURLReadContent hashLedger
dpahttps://www.atlassian.com/legal/data-processing-addendum2026-09-06d88e100664293c0a…seq 436
subprocessorshttps://www.atlassian.com/legal/sub-processors2026-10-1391f43c2df5bf8950…seq 53139
privacy_policyhttps://www.atlassian.com/legal/privacy-policy2026-10-223dd294c82295db11…seq 64163
Ledger proof for this record.
seq 64178 · key 2f898a895f05b7a0 · 2026-10-22T05:19:27.244Z
hash 64ba3e161b7c7d96cc6cba3acbb338a72e52c7516e5abee4799d6d16ddbc3bc0
prev 3d14339fd4eff75e9af5868e51fd8c651e3363205758105e8092a92c8281424a
payload d86adc1e902a1fe3fe91befd79c6c2d9812d74fbbc4806ac37da021af3051bcb
signature GMytULM6WCxl/w0AsnwJ9GbnvurPB+fp4umAZOTD57SEMmLVtC5q+F4BsXCu1QdShNIupzAFS4gHtTtYHhIJAA==
anchored 2026-10-22 at head seq 64204 68332ccffa8b4c79780bf1a01284351ca72309d4c1746ababe798f1ed346c99d
Fetch /v1/keys; for each ledger entry recompute sha256(prev_hash|kind|ref_id|payload_hash|created_at ISO) and verify the Ed25519 signature over that hash. Anchors are committed to git; compare the anchored head with the chain.