Opt out of training: a census of 143 listings

No opt-out is needed: the contract bars 11x outright from training any AI or ML model on customer data, and the privacy policy repeats this for Google Workspace data.

Source retrieved 2026-09-23

The distributor states flatly that catalog data, buyer dialogues and cost formulas are never used for public LLM training, though it publishes no contractual term or setting behind that promise.

Source retrieved 2026-09-27

Zero data retention is contracted with every LLM provider by default, so customer data is processed in memory only and never used for model training.

Source retrieved 2026-10-03

The bridge never ships your code anywhere, so nothing leaves the machine through it, but whether your prompts train a model is governed by the Claude and Codex accounts it relays between.

Source retrieved 2026-10-03

The privacy policy promises no training of public models on private data without consent, but it covers information collected through the website and services and no separate client data processing agreement is published.

Source retrieved 2026-10-03

Nothing to opt out of: the vendor never receives a copy of your data, which stays in your own database.

Source retrieved 2026-09-02

No opt-out is needed because no training happens: models run at zero data retention under provider agreements, and 'no training on your data' is a checked row on all four plans including Starter.

Source retrieved 2026-09-23

The vendor states its telemetry never touches your code, prompts or keys, analytics are opt-in only, and one command disables collection permanently.

Source retrieved 2026-09-30

Aisera states as a blanket commitment, not a setting you must find, that it neither retains customer data nor trains other models on it; the TRAPS page repeats this for other customers' models.

Source retrieved 2026-09-24

No opt-out is needed because training is excluded by default: submitted text and generated packets are not stored, reused for training, or passed to a third-party provider.

Source retrieved 2026-09-10

Consumer terms say your interactions feed Google's model development unless you change a setting, and the enterprise path states corporate data is never used for training.

Source retrieved 2026-09-10

Uploaded lists and CRM records are contractually kept out of the sellable database unless you opt into the Chrome-extension contribution programme, but no clause anywhere states whether customer data trains Argorant's own models.

Source retrieved 2026-09-26

Identifiable data needs your prior express consent before it trains anything and Google mailbox data is carved out entirely, but de-identified and aggregated usage data is used for model training with no published opt-out control.

Source retrieved 2026-09-10

AudioCodes states it never retains or trains on customer data, though it notes that third-party speech and LLM providers you route to are governed by their own policies you must configure.

Source retrieved 2026-09-24

Paid plans exclude AI training on your data, but the Community terms grant Augment the right to train on Customer Code.

Source retrieved 2026-09-02

Training on your call and lead data is off by default and contractual rather than a setting - it requires your written opt-in, and the same commitment is repeated in the privacy policy.

Source retrieved 2026-09-11

A zero-retention policy is asserted for the chatbot line and covers the model providers they use, but the AI agent page makes no equivalent promise and the claim sits in a block that opens by naming a third-party product.

Source retrieved 2026-09-11

No outside model provider sees your calls and zero-retention processing exists for sensitive work, but no general training opt-out is published.

Source retrieved 2026-09-11

Exclusion from training is contractual and reserved for Team and Enterprise customers under an MSA or DPA; no self-serve toggle is documented for Free or Pro.

Source retrieved 2026-09-11

No opt-out is needed: the vendor states outright that it does not use conversation data or uploaded content for model training, and says the same of the provider side. Aggregated usage data is still used for product improvement.

Source retrieved 2026-09-02

The privacy policy makes no-training the default, conditioned on affirmative consent.

Opt-out is by request form for selected categories of content; Enterprise plans can additionally enable Zero Data Retention for TTS and STT inference.

Source retrieved 2026-09-02

Retained API data is not used for training without express permission, and the opt-in route is a named program an admin must join.

Source retrieved 2026-09-02

Commercial terms (Team, Enterprise, API, cloud providers) are no-training by default; Free, Pro and Max users toggle it in privacy settings.

Source retrieved 2026-09-02

Cline states it never trains on your code, and BYOK keeps requests out of its infrastructure entirely, but its privacy notice puts training on whichever model provider you choose and their opt-out.

Source retrieved 2026-09-12

No opt-out is needed because customer code is never used for training by CodeRabbit or its providers; separately, retention of learnings and model-output logging can be switched off.

Source retrieved 2026-09-15

Business, Enterprise and API-key usage are not trained on by default; the same matrix marks Plus and Pro unavailable.

Source retrieved 2026-09-02

AI runs through OpenRouter providers and the terms reserve use of AI processing and anonymised data for product improvement; no customer-facing training opt-out is published.

Source retrieved 2026-09-05

The DPA bars use of customer personal data beyond delivering the service, but there is no published model-training opt-out, and de-identified derivatives of your data become Crescendo's property.

Source retrieved 2026-09-12

Framework telemetry excludes prompts and agent data by default and is disabled with one environment variable, but no page states whether platform execution data trains vendor models.

Source retrieved 2026-09-13

Privacy Mode is available on every plan, settable by the user or enforced by a team admin, and is on by default for Enterprise; it does not cover BYOK requests.

Source retrieved 2026-09-02

Stronger than an opt-out: zero-day retention is enforced with every AI provider by default, so conversation data is not stored or trained on.

Source retrieved 2026-09-14

Opt-out is a per-request query parameter, mip_opt_out=true, and Deepgram states that only data contractually included in the Model Improvement Partnership Program is used for training; opted-out request data is retained only long enough to serve the request.

Source retrieved 2026-09-02

Training is on by default and the opt-out is paid-plans-only; opting out also enables Zero Data Retention with the model providers.

Source retrieved 2026-09-02

Opt-out lives in Data Controls and is available only on paid plans (admin-only on Teams), after which Zero Data Retention is enabled with model providers; Enterprise needs written consent to train.

Source retrieved 2026-09-03

Nothing to opt out of: the vendor states it does not train models and contractually bars its model sub-processors from training on your data.

Source retrieved 2026-09-02

The security page states customer data is never used for model training and that third-party providers retain nothing, so there is no opt-out to find because training is excluded by default.

Source retrieved 2026-10-01

Any account can switch off model training in Terms and privacy, Data use; Enterprise data is excluded by default, and third-party LLM providers are contractually barred from training on it.

Source retrieved 2026-09-02

Only Enterprise is promised no training on your data by default; no opt-out control is documented for Basic, Plus, Pro or Scale, though uploaded PDFs are stated to stay private to the account.

Source retrieved 2026-09-14

Zero Data Retention is a Business and Enterprise plan feature; Factory says it routes traffic directly to providers and stores no prompts, and never indexes your repository.

Source retrieved 2026-09-02

Fine-tuning on your anonymised data can be switched off at any time with deletion inside 30 days, and workspaces with a BAA or hosted in the EU or AU are excluded automatically.

Source retrieved 2026-09-18

No opt-out is needed because the contractual default is no training on customer data, backed by zero data retention agreements; the exception is the optional Claude Fable 5 model, which retains data for 30 days for safety work.

Source retrieved 2026-09-14

Nothing to opt out of: no training on prompts or responses by default. Preview and Trusted Tester data sharing is opt-in and used for product improvement, not training.

Source retrieved 2026-09-02

Group plans are opted out of model training automatically with no-training terms bound onto subprocessors, but no equivalent blanket statement covers Free, Plus or Pro accounts.

Source retrieved 2026-09-15

Business and Enterprise data is never used for training; individual subscribers are opted in by default and switch it off in Copilot settings without losing features.

Source retrieved 2026-09-02

Zero LLM data retention is in the seat fee, and the Universal Model Key is stated not to train on your data.

Source retrieved 2026-09-02

ADK's own usage telemetry is off until you switch it on and explicitly excludes source files, prompts and credentials, but the site says nothing about what the model provider you route to may do with your data.

Source retrieved 2026-09-15

goose's own telemetry is opt-in and explicitly excludes your code and conversations, but whether your prompts train a model is decided by the LLM provider you point it at, which the vendor says has its own retention policy.

Source retrieved 2026-09-16

Nothing reaches a GPT Researcher service to train on; only the providers you pick see your queries, and a local model plus SearXNG removes even that.

Source retrieved 2026-09-16

Zero-data-retention agreements with major model providers are the default rather than a setting, and open models are explicitly excluded from training; a 30-day-retention model group must be chosen deliberately.

Source retrieved 2026-09-30

No opt-out is needed because the default is no training: content, recordings, transcripts and cloned voice models are stated never to train shared or third-party models, and the terms repeat it.

Source retrieved 2026-09-10

The vendor states local evaluation uploads nothing and cloud sync carries only redacted summaries, but publishes no explicit model-training clause.

Source retrieved 2026-09-29

The vendor states customer data grounds answers only for that customer and never trains anyone else's models, and generative AI can be switched off or kept on private in-house models entirely.

Source retrieved 2026-09-24

No-training is contractual and applies by default rather than being a toggle you must find, and Google-derived data is additionally bound by Limited Use.

Source retrieved 2026-09-14

Juggler has no cloud and no account, so nothing reaches the vendor; whether your code trains a model is settled entirely by the provider whose key or subscription you connect, and Juggler publishes no policy of its own on it.

Source retrieved 2026-09-17

There is nothing to opt out of: the vendor says training never happens on customer data, internally or at its model providers, and repeats the commitment in its privacy policy.

Source retrieved 2026-09-17

Training on your code is off unless you switch it on, the exclusion is ticked on every tier including free, and the commitment is contractually extended to model subcontractors.

Source retrieved 2026-09-18

Call data is used to improve the vendor's AI algorithms in anonymised form under legitimate interest, and the policy offers a GDPR right to object rather than a product setting; no dashboard toggle or contractual opt-out is documented.

Source retrieved 2026-09-26

Kilo states it never trains on your code and does not retain prompts for its own purposes; local models keep code on the machine.

Source retrieved 2026-09-02

No opt-out is needed because the vendor states it never trains models on customer traces, prompts or outputs; Engine's analysis still runs through LangChain-managed inference.

Source retrieved 2026-09-18

Anonymous usage telemetry is on by default and switched off with one variable, but the vendor makes no statement about training models on your data either way.

Source retrieved 2026-09-03

Nothing to opt out of: the vendor states it does not train on customer data. Separately, setting LANGSMITH_TRACING=false keeps agent data on your own machine entirely.

Source retrieved 2026-09-02

Hosted messages may train future models; running your own model backend or local state means nothing is collected.

Source retrieved 2026-09-02

Training exclusion is the default rather than a setting to find: Lindy states neither it nor its model providers train on customer data, and repeats the claim in its docs and pricing FAQ.

Source retrieved 2026-09-19

Nothing to opt out of: zero retention is the default on every plan, LiveKit logs no prompts, audio or completions, and voice-clone samples are opted out of provider training on your behalf.

Source retrieved 2026-09-02

Nothing is used for training by default, and do_not_cache=True skips the 48-hour cache entirely.

Source retrieved 2026-09-02

Non-training rests on the hosted default routing to Azure OpenAI inside Microsoft's boundary rather than on a customer-facing toggle; self-hosting or your own Azure resource is the stronger route.

Source retrieved 2026-09-09

The Trust Center states contracts bar every third-party model provider from training on your data, but the Team FAQ frames that prohibition around Team and Enterprise customers and the help centre lists Data Training Opt-Out as a Team feature.

Source retrieved 2026-09-19

Contractual no-training default on customer inputs and outputs, for Mastra's and model providers' models, with training only on express opt-in.

Source retrieved 2026-09-02

No opt-out is needed because the vendor states customer data is never used to train or fine-tune foundational models and is not aggregated for model improvement; sensitive data is also redacted before any external model call.

Source retrieved 2026-09-25

Microsoft makes no training claim for the framework and instead pushes the question to whichever model or tool provider you configure, telling you to review their retention and privacy terms first.

Source retrieved 2026-09-19

No opt-out is needed: the vendor states user data is never shared with model providers for training, and the guarantee is ticked on every plan including Free.

Source retrieved 2026-09-20

You consent before conversation data goes to OpenAI and can withdraw that consent, but withdrawing disables the AI features, and the policy claims a right to use de-identified data commercially with no separate training opt-out.

Source retrieved 2026-10-03

The vendor states customer data is never used to train its global generative models, so there is nothing for a buyer to opt out of.

Source retrieved 2026-09-20

Standard-tier models are contractually excluded from training, and the discounted contributor models that do train on your content are opt-in by model id and can be left behind by upgrading.

Source retrieved 2026-09-20

n8n states the context sent to its AI features is never used to train provider models and is deleted after 30 days; admins can also stop sending workflow data at all, and telemetry is opt-out.

Source retrieved 2026-09-02

No opt-out is needed: the vendor states its AI providers are used under API terms that exclude training on your content, and that it never sells your data.

Source retrieved 2026-09-29

The terms take call recordings and user content for model development unless you opt out of recording, so the control exists but is opt-out, is bundled with recording itself, and is qualified only by de-identification.

Source retrieved 2026-09-09

API data is excluded from model training by default; sharing is opt-in, and Zero Data Retention or Modified Abuse Monitoring can additionally remove content from the 30-day abuse-monitoring logs after approval.

Source retrieved 2026-09-02

No OpenClaw cloud sits in the path, so the vendor receives nothing to train on, but whichever model provider your gateway forwards to handles that data under its own policy.

Source retrieved 2026-09-21

Zen providers are zero-retention and non-training by default, but named free and contributor models explicitly use your data to improve models.

Source retrieved 2026-09-21

Running it locally or self-hosted keeps code out of vendor hands entirely, but the cloud privacy policy reserves model training on your content with no opt-out published.

Source retrieved 2026-09-21

Guaranteed on Enterprise Pro and Enterprise Max; the comparison row is blank for individual Pro, while the API is documented as zero-retention and never trained on.

Source retrieved 2026-09-02

The terms reserve the right to train on prompts and outputs and exempt only Pro members for as long as they stay on Pro; uploaded documents are always excluded, and there is no self-serve toggle.

Source retrieved 2026-09-09

The vendor states flatly that no model is trained on customer data, and its edge boundary is designed to keep identifying values from reaching a model at all.

Source retrieved 2026-10-03

Customer conversations reach Raven training only where the contract authorises it, and the privacy notice relies on consent where law requires; no self-serve opt-out control is documented.

Source retrieved 2026-09-02

No training-opt-out toggle is published, and none is needed for the library itself, which sends prompts straight to the provider you configure. Where Pydantic is in the path, the Gateway terms license your content only to operate the Gateway, and provider terms govern the provider leg.

Source retrieved 2026-09-02

No opt-out is needed because the default is already exclusion: the privacy policy states customer information is not used to develop or train generalised AI or ML models and is not stored by its AI providers.

Source retrieved 2026-09-22

Nothing to opt out of by default: the vendor states it does not train on customer data absent a specific partnership agreement, and metadata is excluded from training.

Source retrieved 2026-09-22

Content trains Replit's models by default; the opt-out switch is documented for Pro, while Enterprise content is excluded outright.

Source retrieved 2026-09-22

Per-agent data storage settings let you keep transcripts and recordings out of Retell entirely, but the privacy policy states collected information is used to train its models and publishes no separate training opt-out.

Source retrieved 2026-09-23

Zero-retention agreements with every model provider are the default and the site states customer data is never used to train generalised models - there is nothing to opt out of.

Source retrieved 2026-09-03

The vendor states flatly that client business data is not sent to train third-party public models, presenting it as a property of the MCP grounding architecture rather than a paid option.

Source retrieved 2026-09-28

There is nothing to opt out of: the Einstein Trust Layer applies zero retention by default, so prompts and responses are not stored by or used to train the third-party models.

Source retrieved 2026-09-03

The vendor states it does not train its own model on customer content, but that is a commitment rather than a switch, and prompts still reach Anthropic under Anthropic's terms.

Source retrieved 2026-09-25

The vendor trains nothing of its own on your data and routes EU-sensitive workspaces to Anthropic in code, but is explicit that its default Moonshot provider gives no equivalent guarantee.

Source retrieved 2026-10-03

Sierra states customer data is never used to train models at all, so there is no opt-out to negotiate per tier.

Source retrieved 2026-09-26

No customer-facing training opt-out switch; the vendor commits that Google-API data is never used for generalized model training, and self-hosting keeps data on your own infrastructure.

Source retrieved 2026-09-03

Under AI Security sipgate states model training on customer data is contractually excluded and processing stays in Europe, but the sentence covers its own ChatGPT usage, not Flow's speech subprocessors specifically.

Source retrieved 2026-09-03

The licence you grant is limited to running and protecting the service, which excludes model training, but there is no explicit training statement or opt-out switch to point a buyer at.

Source retrieved 2026-10-03

Voiceprints are contractually never used beyond service delivery, but nothing states whether call transcripts or recordings train models.

Nothing to opt out of: the contract and the trust page both state customer content is never used to train models, with zero-retention terms at every provider.

Source retrieved 2026-09-15

No opt-out toggle is needed because the vendor states training is contractually excluded through DPAs with the model providers; its OpenAI and Anthropic DPAs are published.

Source retrieved 2026-09-09

A blanket contractual commitment not to train on customer input or output; published Marketplace templates are the one carve-out.

The DPA commits contractually to no training on customer payloads, binds AI sub-processors to the same, and says a product toggle cannot vary it.

Source retrieved 2026-10-03

A no-training promise is published for the veterinary receptionist offer only; the general terms describe data being used for service delivery and improvement without any model-training opt-out.

Source retrieved 2026-09-12

The opt-out is one TelEcho sets on your behalf rather than a switch you control, and it binds only where each model provider offers one; TelEcho separately promises not to train its own models on identifiable content.

Source retrieved 2026-09-16

An opt-out exists but training is the default: without notice, de-identified inputs and outputs may improve Telnyx and third-party models. The residency FAQ routes you to your account team to document it.

Source retrieved 2026-09-09

Agent data is off the training path by default: the Agent Builder row shows no fine-tuning of UiPath models and no training of third-party models, and product-improvement processing can be opted out contractually or by ticket, though that opt-out row is an em dash on Basic.

Source retrieved 2026-09-03

A no-training guarantee is stated for enterprise R&D data, covering model providers too, but the vendor makes no equivalent statement for Free, Pro or Team users.

Source retrieved 2026-09-26

Only Google Workspace data carries an explicit no-training guarantee; the self-service terms otherwise grant Unify a perpetual licence over customer data within service data, with no published opt-out.

Source retrieved 2026-09-27

The privacy policy reserves call content for model training and names no toggle; the $1,000/month ZDR add-on is the only documented way to stop it being kept at all.

Source retrieved 2026-09-03

Conversation-content collection is an explicit opt-in/opt-out toggle, telemetry is off by default, and the vendor states data is not used to train models either side.

Source retrieved 2026-09-27

The vendor states flatly that transcripts are not used to train models, so there is nothing to opt out of; the same assertion is repeated for calendar and appointment data.

Source retrieved 2026-09-22

Model training on customer voice, transcripts and end-user communications is disclaimed by default, and opting out of call recording also removes the aggregated de-identified service-improvement use; any wider training needs explicit opt-in.

Source retrieved 2026-09-03

The no-training commitment is scoped: it is stated firmly for Google Calendar data, while general product improvement runs on legitimate interests with opt-out controls rather than being off by default.

Source retrieved 2026-10-03

Vendor states customer data is never used for AI model training; it uses OpenAI's pre-trained models instead.

Source retrieved 2026-09-03

Zero Data Retention agreements with the contracted providers apply on every plan, including Free; admins on Business and Enterprise can additionally switch off the optional interaction-data sharing, which is already off by default there.

Source retrieved 2026-09-03

Nothing is retained or trained on unless you rate a response or opt into training collection; on Business both are off by default and members cannot opt in.

Source retrieved 2026-09-29

Training on customer code is refused outright rather than offered as a toggle, and code context is described as processed ephemerally unless persistence is switched on.

Source retrieved 2026-09-09

Third-party LLMs never train on customer data, but Zendesk does train its own generic cross-account classification models on Service Data and publishes no opt-out.

Source retrieved 2026-09-03

The vendor operates no service that could train on your code and keeps all state on your disk, but whether prompts train a model is decided by the provider you log in to, not by zot.

Source retrieved 2026-09-28