Documentation

Features

Privacy, Logging, and Data Collection

Making sure your data is safe.

When using AI through A4F, whether via the chat interface or the API, your prompts and responses go through multiple touchpoints. You have control over how your data is handled at each step.

This page is designed to give a practical overview of how your data is handled, stored, and used. More information is available in the privacy policy and terms of service.

Within A4F

A4F does not store your prompts or responses, unless you have explicitly opted in to prompt logging in your account settings. It's as simple as that.

A4F samples a small number of prompts for categorization to power our reporting and model ranking. If you are not opted in to prompt logging, any categorization of your prompts is stored completely anonymously and never associated with your account or user ID. The categorization is done by model and with a zero-data-retention policy.

A4F does store metadata (e.g. number of prompt and completion tokens, latency, etc) for each request. This is used to power our reporting and model ranking, and your activity feed.

Provider Policies

Training on Prompts

Each provider on A4F has its own data handling policies. We reflect those policies in structured data on each AI endpoint that we offer.

On your account settings page, you can set whether you would like to allow routing to providers that may train on your data (according to their own policies). There are separate settings for paid and free models.

Wherever possible, A4F works with providers to ensure that prompts will not be trained on, but there are exceptions. If you opt out of training in your account settings, A4F will not route to providers that train. This setting has no bearing on A4F's own policies and what we do with your prompts.

Data Retention & Logging

Providers also have their own data retention policies, often for compliance reasons. A4F does not have routing rules that change based on data retention policies of providers, but the retention policies as reflected in each provider's terms are shown below. Any user of A4F can ignore providers that don't meet their own data retention requirements.

The full terms of service for each provider are linked from the provider's page, and aggregated in the documentation.

ProviderData RetentionTrain on Prompts
AI21Unknown retention policy Does not train
AnthropicRetained for 30 days Does not train
Azure OpenAIZero retention Does not train
Google Vertex AIRetained for 30 days Does not train
OpenAIRetained for 30 days Does not train
Mistral AIRetained for 30 days Does not train
CohereRetained for 30 days May Train (May Train)
DeepInfraZero retention Does not train

This is a sample list. For a complete and up-to-date list, please refer to individual provider documentation or the A4F models page.

Was this page helpful?