---
title: "Privacy"
description: "What this service records, what it never records, and the governing policy"
canonical: "https://inference.boundless.network/privacy"
last-updated: "2018-10-20T01:46:40.000Z"
---

# Privacy at Boundless

What this service records, what it never records, and the policy that governs both.


This page summarises how Boundless handles the data you send it. It is a summary, not the agreement: the binding documents are the [Inference Services Customer Terms](/terms) — Section 3 covers data — and the [Boundless Networks privacy policy](https://boundless.network/privacy-policy), which is the company-wide policy for every Boundless product. Where this page and those documents differ, those documents govern.

## Zero data retention

Your prompts and your outputs are never stored, and never used to train a model. Request and response bodies are not written to a log or a database by this service.

That is the whole of the claim, and it is deliberately narrow: it is about the content of your requests. It is not a claim that no record of the request exists, because billing needs one.

## What is recorded

For each request the service keeps what is needed to bill it and to let you check the bill:

- The model that served it
- Input, cached-input and output token counts
- A timestamp
- The computed cost
- The API key and team the request was billed to

This is exactly what the [usage page](/usage) shows you, and it is enough to recompute any charge from the [rate card](/docs/pricing) yourself. Nothing in that list contains the text of a prompt or a completion.

Billing records are retained for 90 days, then deleted automatically.

## Account data

Signing in creates an account record: your email address, your name if you provide one, your team membership and role, and your API key names. Authentication is handled by a third-party identity provider; payment, where card payment is enabled, is handled by Stripe, and card numbers never reach this service.

## Third-party infrastructure

Models run on compute operated by third parties. [Section 3 of the terms](/terms) sets out the limits on what can be promised about infrastructure that is not ours — read it if zero retention is a compliance requirement on your side rather than a preference, and write to us if you need those limits in writing for a specific deployment.

## Questions, and requests about your data

Email [support@boundless.network](mailto:support@boundless.network) for anything on this page, including access, correction and deletion requests. See [Contact](/contact).