Data handling
Policy
HIPS never trains on, retains or logs your prompt data. For anyone, on any plan: no prompt, file, result or response is used to train any model, and none is kept or written to a log. This includes requests processed by customer-owned models.
HIPS holds content only where you ask it to, to deliver what you asked for (batch files for thirty (30) days, task results for seven (7) days, uploads for twenty-four (24) hours, and Knowledge documents, files kept for later use and agents' own definitions and kept disks until you delete them, or thirty (30) days after their storage goes unpaid), keeps a prompt cache only in the GPU memory of its own servers, and on a provider's computer only in the engine's memory once it has given notice of it, re-runs a result to verify it only in memory, leaves it on a provider's computer only in the engine's memory until it is overwritten, and otherwise keeps content only where the law requires (Common Clauses Section 3.14).
The Common Clauses define what this covers: Prompt Data means all the content of a Request and of its response, whatever the interface, the Plan or the pool: Request Data; Batch Files; files uploaded to the Services; the results of task Requests and of jobs; documents added to a Workspace for the Services to search (Knowledge), and the passages the Services find in them; the inputs and the results of tools that HIPS runs for a Request; and anything kept for an agent. The Console will show this before you send work.
Policy
Customer-owned model weights will never be used to train other models on any plan.
A customer model is imported from a model hub, never uploaded, and it is weight files only: no customer code runs anywhere. The import pins the revision, fetches only the files an engine reads, re-saves what passes its checks, copies it once into encrypted HIPS storage in the workspace's storage region, where its deployments run, and signs it with a HIPS key. Workers and devices load only that signed copy, never the hub. Import and run your model has the whole path.
A hub token for a private or gated repository is read-only, kept encrypted under a cloud key, shown by its last four characters, used only in the import job and never sent to a data-center worker, its RunPod pod or a device; it is deleted when you delete it. Access tokens has the rules.
| What | The gateway |
|---|---|
| Request bodies, prompts, inputs | Never stored. Read, validated, relayed to the worker, forgotten. Logged as sizes and counts, never as content. |
| Responses, outputs | Never stored, except a task or job result on the job record until expires_at, so a client can retrieve it. |
| Uploads | Never pass through the gateway (a presigned PUT). Stored encrypted in the HIPS account under the upload's retention. |
The user field | Discarded. |
| The usage record | Operational metadata only: ids, timestamps, units, cost, outcome. No prompt, no input, no output. |
- What
- Request bodies, prompts, inputs
- The gateway
- Never stored. Read, validated, relayed to the worker, forgotten. Logged as sizes and counts, never as content.
- What
- Responses, outputs
- The gateway
- Never stored, except a task or job result on the job record until
expires_at, so a client can retrieve it.
- What
- Uploads
- The gateway
- Never pass through the gateway (a presigned PUT). Stored encrypted in the HIPS account under the upload's retention.
- What
- The
userfield - The gateway
- Discarded.
- What
- The usage record
- The gateway
- Operational metadata only: ids, timestamps, units, cost, outcome. No prompt, no input, no output.
A request that names a router is read first by a decision service run outside HIPS: a masked excerpt of at most 4,096 bytes, the newest user message's text and then the system text, with every email address, phone number, Social Security number, card number, IBAN, IP address and secret replaced by a typed placeholder, for the one call. It is never stored, logged or sent to a model's server, and the usage record keeps the router, the preference and how it chose, never the task or the difficulty (Semantic routing).
A content moderation guardrail holds a matched value and a redacted original in the gateway's memory for the request alone: never stored, logged, returned or sent to a model's server, so a GPU receives only the redacted text. A check the decision service judges sends it only the parts the guardrail scans, after the patterns' redaction, for the one call (Guardrails), and a request that requires a region sends it nothing (A request that requires a region).
In the community pool a job runs on a device that its owner controls physically. The provider app handles weights and inputs in memory and removes them after the job, and the software is signed; but a person with physical control of a machine can in principle read its memory, and HIPS cannot verify from outside that they did not. HIPS discloses this before a customer selects the pool. In the certified pool a job runs on data-center supply operated by an approved provider, with published execution protections and access conditions per provider Not decided yet.
Encryption in transit and at rest is part of the platform requirements. It protects data during transfer and storage, but does not by itself prevent a GPU operator from accessing weights or request data during execution. We will publish the execution protections and access conditions for each pool before customers deploy workloads to it.
Cross-pool fallback is off by default and requires explicit enablement. It never relaxes a region or data-use rule. Customer-owned models run in the certified pool only at launch.
A region is a requirement of a request, available on the Business plan only. What a region requirement covers (processing, logs, storage, backups, retries, verification samples, operations access, sub-processors) is open Not decided yet, and it is not offered until specified. The rule that holds regardless: no request silently crosses a required boundary. If no eligible supply exists in the required region, the gateway answers 503 overloaded_error with Retry-After, never a result from elsewhere.
Related sheets
- Sheet
- 19 of 20
- Detail
- F
- Updated
- 2026-11-16