Advance notice of proposed Terms and Privacy changes

Proposal dated

PROPOSED CHANGES — NOT IN EFFECT

This is advance notice of the specific proposed changes below. The current Terms of Service and current Privacy Policy remain in effect. Their current content-license and account-deletion wording has not yet been replaced.

No effective date has been set. Under section 16 of the current Terms, these changes will not take effect sooner than 30 full 24-hour days after this notice is first displayed in the app. The proposal date is not an effective date and does not establish when that display began.

Nothing on this page activates a policy change automatically. A separate update will identify any effective date after the required notice period. Until then, the existing policies continue to apply.

1. Proposed replacement for Terms §5.2's general content-license paragraph

The second paragraph of section 5.2 currently grants rights for any purpose, including model training, that survive account termination. The proposed replacement limits that general license to operating the requested service. The first paragraph about ownership and the separate third paragraph about Marketplace listings are unchanged by this proposal.

You grant the Company a non-exclusive license to process, store, and display content you submit or create only as needed to deliver the service you request, including requested model and tool processing and displaying results to you or recipients you choose. This license does not grant rights to use submitted content for unrelated products or purposes. Meta Council does not use submitted content to train AI models.

2. Proposed replacement for Terms §14.1

The current section says account deletion removes data within 30 days. The proposed wording describes the limits of application cleanup and backup retention rather than promising a complete-erasure deadline.

You may request deletion of your account. Supported owner-linked application records are removed when account cleanup completes. Active work or failed external cleanup can prevent completion; a deletion request is not a guarantee that cleanup has succeeded. Backup copies and time-retained logs can remain after application cleanup. Backup rotation does not guarantee that all copies are deleted within 30 days, and individual customer records cannot be removed from a database backup archive. The Data Retention and Deletion Standard describes the mechanisms, dated verification and known limits; it does not guarantee a deadline for complete erasure.

Matching proposed replacement for Privacy Policy §6's account-data sentence

Account data is retained while your account is active. Supported owner-linked application records are removed when account deletion completes; active work or failed cleanup can prevent completion. Backup copies and time-retained logs can remain afterward, with no guaranteed complete-erasure deadline. See the Data Retention and Deletion Standard for dated verification and known limits.

Only the account-data sentence in Privacy Policy section 6 is proposed for replacement. The separate query-history and API-log statements, and all other policy clauses, are unchanged by this notice.

Read the Data Retention and Deletion Standard. Local backup scripts use an age threshold of seven days or keep the newest seven dumps, depending on the job. Failed backup or upload jobs can delay rotation. Provider metadata last recorded in that standard on 25 August 2026 showed offsite deletion eligibility at age 90 days and a seven-day soft-delete setting; those settings do not prove when every copy becomes unrecoverable. This notice does not claim a new inspection of those provider settings.

Current hosted and self-hosted processing

The hosted service uses Anthropic's Claude Haiku 4.5 by default through the Anthropic API, so query content is sent to Anthropic. Availability and platform usage limits can prevent a run; selecting another configured model can change which provider receives content.

Local inference is available when self-hosted and configured for it. Self-hosting alone does not make every operation local: enabled research tools, integrations, cloud models and fallback routing may still send relevant content to third parties.

Meta Council does not use submitted content to train AI models. Third-party processing is governed by the provider and plan used. Anthropic's commercial data policy states that API inputs and outputs are not used for training by default, while describing exceptions for submitted feedback or other permission. This is not a guarantee about every provider or configuration.

Current protected-health-information restriction

Do not submit protected health information (PHI/ePHI). Meta Council is not HIPAA-ready and does not currently offer a Business Associate Agreement (BAA). A model provider's own BAA offering does not establish a BAA with Meta Council or permission to submit PHI here.

Current Terms · Current Privacy Policy · Trust and Security · Back to Meta Council