What HIPS stores
HIPS has a zero-tolerance policy on storing your data.
- Not stored: no prompt or answer is kept, whatever it holds: messages, source code, documents, images, tool calls and their results, beyond what you choose to store below.
- Not logged: logs hold sizes and counts, never content.
- Not trained on: nothing you send or receive is used to train any model.
This holds on every plan, in both pools.
Certifications
HIPS is PCI DSS Level 1, ISO/IEC 27001 and SOC 2 certified.
A prompt cache, where one is kept, is held apart for each workspace: a workspace's prompt prefix is kept only in the memory of the engine on the GPU that ran the request, HIPS's software never writes it to a disk, a database or a log, and it is reused only by the same workspace. A cache nobody has used for 30 minutes is dropped, and no lifetime is promised. Read Prompt caching.
To bill you and to run the service, HIPS keeps usage records: the model, token counts, timings and result codes. They hold no content.
Some features exist to hold your data:
- Batch files: a batch's input file is deleted once the batch ends, within about five minutes, unless another open batch reads it. Output and error files are kept 30 days and then deleted, sooner when you set a shorter expiry or delete them (Batch jobs).
- Task and job results: a task or job result is kept on the job record until
expires_at, so a client can retrieve it (Data handling). - Uploads: stored encrypted in the HIPS account under the upload's retention (Data handling).
- Knowledge documents: the store, the chunks and the search run on the platform in the European Union (Ireland). Removing a document from a base removes its text, chunks and vectors at once; the File stays until you delete it (Knowledge).
Every facility in the Certified pool is certified by HIPS's compliance team to store none of your data. The prompt cache is the only state allowed, and it is temporary.
HIPS's software on a provider's machine keeps nothing after the job is done, apart from a prompt cache where one is kept. What an owner could do on a machine they control is the part that cannot be guaranteed (What a Community pool provider can see).
In either pool, you can keep a request to one region, for example only the EU or only the US. Knowledge is the exception: a knowledge base is stored and searched in the European Union (Ireland), whatever region its requests are kept to.
Related sheets
- Sheet
- 03 of 21
- Detail
- D
- Updated
- 2026-11-18