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 a Community pool provider can see
(Detail C)
llms.txt

What a Community pool provider can see

On this sheet7 sections
  1. A request in the Community pool, step by step
  2. What a provider never learns
  3. What protects the Community pool
  4. What cannot be guaranteed
  5. What HIPS redacts before a request reaches a provider's GPU
  6. What runs in the Community pool
  7. When to use it

The Community pool runs on independent owners' GPUs, for a lower price.

A request in the Community pool, step by step

  1. 01

    Your app sends the request to HIPS, encrypted in transit.

  2. 02

    HIPS holds back who you are: your account, your workspace, your API key, your email address, your network address and your billing never go to the provider.

  3. 03

    Before the request reaches a GPU a provider owns, HIPS recognizes and redacts API keys, tokens, private keys and the values of environment variables in its text, and applies your guardrails if you set any.

  4. 04

    The job travels to the provider's machine over mutual TLS.

  5. 05

    The GPU reads the request to answer it. This is the point where the machine's owner could in theory view or alter the content.

  6. 06

    The answer returns the same way. HIPS's software on that machine keeps nothing after the job, apart from a prompt cache where one is kept, and HIPS does not store, log or train on the request or the answer.

What a provider never learns

  • Who you are. A request reaches a provider's GPU without your account, your workspace, your API key, your email address, your network address or anything about your billing.
  • Who else is using HIPS, or what other customers send.

Every request in the Community pool is anonymous in this sense: the provider cannot tie it to you.

What protects the Community pool

  • Thousands of GPUs: very reliable, because there are thousands of GPUs that can process your request.
  • Thousands of tests: HIPS runs thousands of different tests on the Community pool's GPUs.
  • Encryption: your requests are encrypted on every connection, and each provider's machine connects to HIPS over mutual TLS.
  • Attestation: models are signed by HIPS and verified before they load, and the engines HIPS ships to a provider's machine are checked against their build attestations before HIPS publishes them.
  • Nothing kept: HIPS's software on that machine keeps nothing after the job is done, apart from a prompt cache where one is kept (Prompt caching).

All of it is there to make sure a provider cannot access your data and cannot inject anything.

What cannot be guaranteed

A GPU has to read a request to answer it. On a machine that its owner controls, the owner could in theory view the content of a request and its answer while the GPU processes it, and could alter either. The provider agreement forbids keeping, using or changing your data. Still, in the Community pool none of it can be guaranteed: the GPUs are out in the wild, as with anything on the internet.

Recommended

For sensitive or personal data, use the Certified pool: it is the pool HIPS can fully certify. If you are unsure, choose the Certified pool.

What HIPS redacts before a request reaches a provider's GPU

  • API keys, tokens and private keys, and credentials carried in a URL or as a Bearer token.
  • The values of environment variables in their usual forms, such as the lines of a .env file, and values named password, secret, token or key.

This redaction reads the text of a request: messages, tool calls and their results, embedding and rerank inputs, and task and image prompts. Images, audio and uploaded files are not read or changed. A secret in a format HIPS does not recognize may not be found, so treat the redaction as a safety net and keep secrets out of what you send to the Community pool.

Your own Guardrails can mask more before any model sees it: email addresses, phone numbers, names and other customer information. What their checks read is on Choose a pool for your data.

What runs in the Community pool

Today the Community pool serves chat on open-weight language models, listed in GET /v1/models and on Models. As HIPS serves other kinds of models, such as image generation, text-to-speech, speech-to-text, classifiers and ONNX models, the Community pool is the low-cost place for them too, when what you send is not sensitive. Coding agents and requests with tool calls do not run there, and HIPS does not offer coding-agent models there. Read Coding agents and prompt injection.

When to use it

When you just need GPUs and nothing you send is sensitive: a chat that is for fun and holds no personal data, product descriptions, labeling content that is public anyway, or a project where you want low-cost inference and accept that the data runs on consumer GPUs. If you are a business and you send any sensitive data at all, such as personal data (PII), use the Certified pool. Read Choose a pool for your data.

Related sheets

  • Data handling
  • Guardrails
Previous sheetCoding agents and prompt injection
Next sheetWhat HIPS stores
Sheet
03 of 21
Detail
C
Updated
2026-11-18
Sign in to the Console

On this sheet

  1. A request in the Community pool, step by step
  2. What a provider never learns
  3. What protects the Community pool
  4. What cannot be guaranteed
  5. What HIPS redacts before a request reaches a provider's GPU
  6. What runs in the Community pool
  7. When to use it

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Ü