Captured before automated identity checks (Oct 14, 2026): accurate as of its capture on Oct 2, 2026; our capture on Oct 15, 2026 found the same text, but its identity was not checked by them.
Get the weekly coverage letter
Companies change their terms without announcing it. We capture governance documents, compare each new version with the last, and publish what changed, with the source text behind it. One email a week on what we found and what we could not reach.
This page describes what the document states, permits, or reserves. It does not constitute a legal determination about enforceability. Regulatory applicability may vary by jurisdiction. Methodology
“All data, files, and other materials that customers make available to WRITER for using our platform, along with any inputs or generated outputs, are owned by that customer.”
“You can configure organization-wide data controls, including an automated data deletion schedule.”
“We encrypt data shared within our platform at rest and in transit, and provision data in an isolated production project.”
“We adhere to global privacy and data protection laws and maintain industry-recognized certifications to independently validate our security and privacy practices.”
“We also maintain certifications for HIPAA Type 1 and PCI compliance and adhere to our obligations under global privacy laws.”
“For a WRITER account with multiple teams, inputs and data from one team aren't used or accessible by another team, even within the same org.”
Writer's Trust Center sets out how Writer handles customer data: it encrypts everything, stores it only as long as you need it for the platform, and never uses your data or AI-generated outputs to train its models. All content you bring to Writer — and anything the platform generates — belongs to you. If your organization has multiple teams, each team's data is kept separate from all other teams.
This document establishes Writer's data governance commitments for its platform, including encryption of data at rest and in transit within an isolated production environment, a zero data retention approach under which data is stored only as long as needed for active platform use, and customer configuration of automated deletion schedules. Writer explicitly does not train its models on customer data, user inputs, or generated outputs, and all intellectual property in those materials remains with the customer. Internal access to user data is limited to job-function necessity and requires security approval, with team-level data isolation enforced even within shared organizational accounts. Writer holds HIPAA Type 1 and PCI compliance certifications and adheres to global privacy and data protection laws.
As a user, your data is encrypted in storage and in transit, kept only as long as your active platform use requires, and never used to train Writer's models. You own your inputs and all outputs the platform generates. Under applicable U.S. laws, you have the right to opt out of cookies Writer uses for targeted advertising purposes — that opt-out right is available to you directly.
Which mapped governance frameworks each document engages, tied to the specific provisions that engage them.
We withheld clauses we had published from this document. Each withholding is recorded in our correction log:
“You can configure organization-wide data controls, including an automated data deletion schedule.”
“All data, files, and other materials that customers make available to WRITER for using our platform, along with any inputs or generated outputs, are owned by that customer.”
“We encrypt data shared within our platform at rest and in transit, and provision data in an isolated production project.”
“We adhere to global privacy and data protection laws and maintain industry-recognized certifications to independently validate our security and privacy practices.”
“We also maintain certifications for HIPAA Type 1 and PCI compliance and adhere to our obligations under global privacy laws.”
“For a WRITER account with multiple teams, inputs and data from one team aren't used or accessible by another team, even within the same org.”
“Access to user data is restricted and only granted when required for job functions. Any access to user data requires security approval for access.”
“WRITER does not train its models on your data, nor does it train on user inputs or any outputs. You control how your data is used.”
“WRITER takes a zero data retention approach, storing data for only as long as is needed for you to build with our platform.”
“We maintain and implement various administrative, technical, physical, and organizational security measures to protect the data you share with us.”
“Agent requests to connected systems pass through a governed execution layer that validates identity, checks permissions, and records activity.”
“Under applicable U.S. laws, you have the right to opt out of cookies used for targeted advertising purposes.”
Every distinct legal provision identified in this document. Featured provisions appear above with analysis.
We have not recorded a change to this document since we began capturing it. Monitor includes alerts from a daily check, structured change summaries, and monitoring for up to 20 platforms.
Need provision-level monitoring and regulatory mapping? Insight includes governance timelines, drift analysis, and full provision tracking.
Cross-platform context
See how other platforms handle Customer-configurable automated data deletion schedule and similar clauses.
Compare across platforms →Governance Monitoring
Structured alerts for policy changes, governance events, and provision updates across 343 platforms.