Skip to content
HIPS
  • Earn with your GPU
  • Pricing
  • Docs
Sign inJoin early access
⌘K

Get started

  1. 01Developer hub
  2. 02Quickstart
  3. 03Security
    1. AChoose a pool for your data
    2. BCoding agents and prompt injection
    3. CWhat a Community pool provider can see
    4. DWhat HIPS stores
    5. EKnowledge and RAG data
  4. 04Migrate to HIPS

Guides

  1. 05HIPS SDK
  2. 06Import and run your model
  3. 07Model and task guides
    1. ATask guides
    2. BLanguage (chat)
    3. CClassification
    4. DImage
    5. EVideo
    6. FAudio
    7. GDocument processing
  4. 08Batch jobs
  5. 09Prompt caching
  6. 10Code with HIPS
  7. 11Coding-tool setup
    1. AHIPS Code
    2. BClaude Code
    3. CCodex
    4. DOpenCode
    5. EKilo
    6. FPi
    7. GQwen Code
    8. HCrush
    9. ICline
    10. JPrime Agent
    11. KAider
    12. LGoose
    13. MHermes Agent
    14. NGrok Build
    15. ODeepSeek Harness
    16. POther coding tools and editor integrations
  8. 12Command line
    1. AInstall and update
    2. BSign in
    3. CStatus and models
    4. DCoding agents
  9. 13Console
    1. AAccount
    2. BWorkspaces
    3. CAPI keys
    4. DSettings
    5. EUsage
    6. FModels
    7. GPlayground
    8. HDeployments
  10. 14Billing
  11. 15Provider setup
    1. AWhen it works
    2. BCommands
    3. CSettings
    4. DProvider Console
    5. EEarnings
    6. FCrash reports
    7. GData centers
  12. 16Semantic routing
  13. 17Guardrails
  14. 18Knowledge

Reference

  1. 19API reference
    1. AAuthentication
    2. BChat completions
    3. CResponses
    4. DMessages
    5. ECount tokens
    6. FModels
    7. GPrices API
    8. HTasks
    9. IEmbeddings and rerank
    10. JImages
    11. KJobs
    12. LUploads
    13. MFiles
    14. NBatches
    15. OWebhooks
    16. PVector stores
    17. QDeployments
    18. RRequirements and headers
    19. SErrors
    20. TUsage
    21. UVersioning
  2. 20Operating guidance
    1. ALimits
    2. BErrors
    3. CRetries and billing outcomes
    4. DIdempotency
    5. EStreaming
    6. FData handling
    7. GCompatibility matrix
  3. 21Changelog
Sheet indexSecurity

Get started

  1. 01Developer hub
  2. 02Quickstart
  3. 03Security
    1. AChoose a pool for your data
    2. BCoding agents and prompt injection
    3. CWhat a Community pool provider can see
    4. DWhat HIPS stores
    5. EKnowledge and RAG data
  4. 04Migrate to HIPS

Guides

  1. 05HIPS SDK
  2. 06Import and run your model
  3. 07Model and task guides
    1. ATask guides
    2. BLanguage (chat)
    3. CClassification
    4. DImage
    5. EVideo
    6. FAudio
    7. GDocument processing
  4. 08Batch jobs
  5. 09Prompt caching
  6. 10Code with HIPS
  7. 11Coding-tool setup
    1. AHIPS Code
    2. BClaude Code
    3. CCodex
    4. DOpenCode
    5. EKilo
    6. FPi
    7. GQwen Code
    8. HCrush
    9. ICline
    10. JPrime Agent
    11. KAider
    12. LGoose
    13. MHermes Agent
    14. NGrok Build
    15. ODeepSeek Harness
    16. POther coding tools and editor integrations
  8. 12Command line
    1. AInstall and update
    2. BSign in
    3. CStatus and models
    4. DCoding agents
  9. 13Console
    1. AAccount
    2. BWorkspaces
    3. CAPI keys
    4. DSettings
    5. EUsage
    6. FModels
    7. GPlayground
    8. HDeployments
  10. 14Billing
  11. 15Provider setup
    1. AWhen it works
    2. BCommands
    3. CSettings
    4. DProvider Console
    5. EEarnings
    6. FCrash reports
    7. GData centers
  12. 16Semantic routing
  13. 17Guardrails
  14. 18Knowledge

Reference

  1. 19API reference
    1. AAuthentication
    2. BChat completions
    3. CResponses
    4. DMessages
    5. ECount tokens
    6. FModels
    7. GPrices API
    8. HTasks
    9. IEmbeddings and rerank
    10. JImages
    11. KJobs
    12. LUploads
    13. MFiles
    14. NBatches
    15. OWebhooks
    16. PVector stores
    17. QDeployments
    18. RRequirements and headers
    19. SErrors
    20. TUsage
    21. UVersioning
  2. 20Operating guidance
    1. ALimits
    2. BErrors
    3. CRetries and billing outcomes
    4. DIdempotency
    5. EStreaming
    6. FData handling
    7. GCompatibility matrix
  3. 21Changelog
03
  1. Docs/
  2. Security/
  3. What HIPS stores
(Detail D)
llms.txt

What HIPS stores

On this sheet7 sections
  1. Never kept
  2. The one temporary exception: the prompt cache
  3. What is kept: usage, not content
  4. What you choose to store
  5. In the Certified pool
  6. In the Community pool
  7. In one region

HIPS has a zero-tolerance policy on storing your data.

F

Never kept

  • 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.

The one temporary exception: the prompt cache

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.

What is kept: usage, not content

To bill you and to run the service, HIPS keeps usage records: the model, token counts, timings and result codes. They hold no content.

What you choose to store

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).

In the Certified pool

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.

In the Community pool

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 one region

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

  • Data handling
  • Prompt caching
Previous sheetWhat a Community pool provider can see
Next sheetKnowledge and RAG data
Sheet
03 of 21
Detail
D
Updated
2026-11-18
Sign in to the Console

On this sheet

  1. Never kept
  2. The one temporary exception: the prompt cache
  3. What is kept: usage, not content
  4. What you choose to store
  5. In the Certified pool
  6. In the Community pool
  7. In one region

Product

  • Inference
  • Models
  • Deploy your model
  • Always-on GPU capacity
  • How it works
  • Use cases
  • Pricing

Developer

  • Docs
  • Quickstart
  • Migrate to HIPS
  • HIPS SDK
  • Batch jobs
  • API reference

Provider

  • Earn with your GPU
  • Register GPU interest
  • Download for Mac
  • Download for Windows
  • Download for Linux

Resource

  • Security and Data
  • Resources
  • llms.txt

Compare

  • OpenRouter alternatives
  • Together AI alternatives
  • Groq alternatives
  • All comparisons

Company

  • About
  • Contact
  • Affiliate program
  • HIPS Payments

Legal

  • Legal
  • Consumer Health Data Privacy Policy
  • Report content
  • Cookie preferences

Support

  • Contact HIPS
  • Looking for payments support?

HIPS. AI inference for builders.

hips.com

Hyperscale Inference Processing Systems OÜ