Get the weekly research letter
Companies change their terms quietly. We read every version and catch what actually changed. One email a week on the changes that matter and what they mean. No account.
The agreement authorizes Writer to aggregate and de-identify metadata derived from user activity, including usage data, trends, statistical data, performance information, and analytics, and to use that data for any purpose including developing other products and services. This is a distinct authorization from the model training exclusion, which applies only to user-submitted Materials.
This analysis describes what Writer's agreement states, permits, or reserves. It does not constitute a legal determination about enforceability. Regulatory applicability and practical outcomes may vary by jurisdiction, enforcement context, and individual circumstances. Read our methodology
This provision establishes a broad authorization for Writer to use de-identified, aggregated data derived from platform activity for any purpose, including product development. The scope of the defined term 'metadata' is broad and encompasses all data derived from user activity, not limited to technical log data.
Interpretive note: Whether de-identified metadata meets the legal threshold to fall outside personal data protections under GDPR or CCPA depends on technical de-identification standards not described in the document.
Under this clause, data derived from how users interact with Writer's platform, including usage patterns, trends, and performance analytics, may be aggregated, de-identified, and used for any purpose, including developing new products. This authorization operates separately from the provision stating that user-submitted Materials will not be used to train Writer's models.
Cross-platform context
See how other platforms handle Metadata Aggregation and Use and similar clauses.
Compare across platforms →Monitoring
Writer has changed this document before.
Receive same-day alerts, structured change summaries, and monitoring for up to 20 platforms.
"You acknowledge that we may aggregate and/or de-identify metadata related to your use of our Services and use such aggregated and de-identified data for any purpose, including to improve our Services, develop other products and services, and understand how our Services are being used. When we use the term 'metadata', we mean any data that is derived from your use of our Services, including, without limitation, any usage data, trends, statistical data, and performance information, analytics, or similar information regarding the operation of our Services.Excerpt from Writer's Terms of Service
REGULATORY LANDSCAPE: The metadata aggregation clause engages GDPR data minimization and purpose limitation principles if de-identification does not meet the standard required for data to fall outside the scope of personal data under EU law. The CCPA and CPRA may also be relevant depending on whether de-identified data meets California's legal definition. The European Data Protection Board and California Privacy Protection Agency are the primary enforcement authorities in their respective jurisdictions. GOVERNANCE EXPOSURE: Medium. The clause is explicit about the scope of metadata and the breadth of permitted uses, which provides disclosure clarity. However, the breadth of the defined term and the open-ended 'any purpose' authorization may require evaluation against data minimization obligations under GDPR and similar frameworks. Whether de-identification is technically sufficient under applicable law is not addressed in the agreement. JURISDICTION FLAGS: EU and EEA organizations should assess whether the metadata aggregation and use practices described in this clause comply with GDPR data minimization and purpose limitation requirements. California organizations should evaluate compliance with CPRA provisions governing de-identified data. Organizations in sectors with heightened data sensitivity, such as healthcare or financial services, should assess additional sector-specific obligations. CONTRACT AND VENDOR IMPLICATIONS: The distinction between the metadata clause and the model training exclusion is operationally significant for vendor due diligence. Procurement teams should ensure their vendor risk assessments accurately distinguish between these two provisions and do not treat the training exclusion as covering all derived data use. The Data Processing Agreement referenced in the Terms may provide additional detail relevant to organizational accounts. COMPLIANCE CONSIDERATIONS: Legal and compliance teams should assess whether the metadata clause requires disclosure in data processing records or privacy notices. Organizations subject to GDPR should verify that Writer's de-identification practices meet the applicable legal standard. Data mapping exercises should account for the distinction between Materials, which are excluded from training use, and metadata, which is subject to broader use permissions.
This provision establishes a broad authorization for Writer to use de-identified, aggregated data derived from platform activity for any purpose, including product development. The scope of the defined term 'metadata' is broad and encompasses all data derived from user activity, not limited to technical log data.
Under this clause, data derived from how users interact with Writer's platform, including usage patterns, trends, and performance analytics, may be aggregated, de-identified, and used for any purpose, including developing new products. This authorization operates separately from the provision stating that user-submitted Materials will not be used to train Writer's models.
No. ConductAtlas is an independent monitoring service. We are not affiliated with, endorsed by, or sponsored by Writer.