Does Timestral 209M support zero data retention?

Yes. Timestral 209M is available with zero data retention on Opper through the Opper gateway.

Where is Timestral 209M hosted?

Timestral 209M runs on EU hosting routes through the Opper gateway, with contractually enforced residency on supported providers.

Is Timestral 209M trained on prompts and outputs?

No. Every hosting route for Timestral 209M is configured so customer prompts and outputs are not used to train models by default.

Is a GDPR DPA available for Timestral 209M?

Yes. A GDPR Data Processing Agreement is available on at least one route serving Timestral 209M. Contact hello@opper.ai to receive it.

Timestral 209M

by Mistral

Timestral 209M is the largest model in Mistral's Timestral family of time-series foundation models. Send a series' history (one or several variates, with optional past and known covariates) and a horizon, and it returns a median forecast with quantiles from 0.01 to 0.99 for every future step zero-shot, without fitting a model to your data first. Use it for demand, traffic, spend and capacity forecasts and for anomaly bands on metrics. Opper serves it in the EU (Stockholm) and bills per million time steps read and forecast.

Call Timestral 209M on Opper with the OpenAI SDK. Sign up without a credit card. Get started

Get your API key Try in chat Compare

Key info

Input

Output

Features

Context window

—

Max output

—

Input price

$0.05 /1M

Output price

$0.50 /1M

EU residency available
Zero data retention on pay-as-you-go
No training by default
GDPR DPA available

Available routes

Timestral 209M runs on 1 route through the Opper gateway. Compare residency, zero data retention and training posture at a glance, with full data-handling detail per route below. In the EU it is served by Opper (Sweden). See every Mistral model hosted in the EU.

Provider	Region	Zero data retention	Training	Input	Output	Cache read
Opper	EU		No	$0.05	$0.50	Input price

Live routes and prices as JSON: api.opper.ai/v3/models?q=opper%2Ftimestral-209m

Uptime and availability

Timestral 209M runs on a single route through the Opper gateway today, so its availability is that provider's availability.

100%route uptime, last 30 days

Single route, no failover target within this model.

Name a second model in the same request and the gateway tries it on retriable errors, so a busy hour never has to reach your users. Set up a fallback chain.

Measured over the last 30 days from each provider's official status feed via StatusGator. Refreshed hourly. See uptime for every provider Opper monitors.

Data handling per route

Each route hosting Timestral 209M has its own privacy posture, residency, and GDPR terms. Postures are maintained by Opper with a last-verification timestamp.

Opper — Sweden🇸🇪

Zero data retention: nothing is logged, held for abuse monitoring or used for training. No training on customer data. EU; DPA available.

Zero data retention: Yes. Nothing is logged, held for abuse monitoring or used for training.
Training: No training on customer data.
Logging: None
Abuse monitoring: No classifier
Caching: Not cached
GDPR DPA: DPA available
Transfer mechanism: Not applicable — data stays in EU

Get started

Call Timestral 209M through the Opper gateway with one API key. Opper is drop-in compatible with the OpenAI, Anthropic and Google AI SDKs.

Timestral 209M is a premium model on Opper. Sign up needs no credit card: you get an API key straight away and the free models work in the playground and the API. Add a card to use premium models, pay-as-you-go with no minimum.

Set it up with your agent

Copy this and paste it into a coding agent like Claude Code, Cursor or Codex and it'll wire up Opper for you.

Or call it directly

1import OpenAI from "openai";
2
3const client = new OpenAI({
4  apiKey: process.env.OPPER_API_KEY,
5  baseURL: "https://api.opper.ai/v3/compat",
6});
7
8const completion = await client.chat.completions.create({
9  model: "opper/timestral-209m",
10  messages: [{ role: "user", content: "Hello" }],
11});
12console.log(completion.choices[0].message.content);