Zero data retention
Merki does not retain the content of your requests. This is the default for every tier.
What ZDR covers
- Prompts. Not stored after the request is served.
- Completions. Not stored after the response is returned.
- Files and media sent with a request. Not stored after the request is served.
The one exception: caching
Caching is what makes inference fast on repeat work. To serve a cache hit, Merki has to keep the cached entry. Cache entries are the only part of your request data that is retained.
Cache entries are:
- Scoped to your account. They are not shared with other customers.
- Evicted after 24 hours or when superseded.
- Billed at 50% of the input rate on a hit. See Caching and Pricing.
What is not request data
Merki does keep operational records that are not request content:
- Account and billing records, including credit balances and usage counts.
- Age assurance and identity verification records, kept as required for the age-assured and identity-verified tiers.
- Logs and metrics, kept for reliability and abuse prevention.
These are listed, with their windows, in the retention matrix.