Data Processing Agreement.
The terms on which HIPS processes personal data on behalf of a business customer when it answers that customer's Requests, as Article 28 of the GDPR requires.
- Version
- 1.0
- Last updated
- In effect from
- 2026-10-27
- Length
- 19 sections12 defined terms
- Questions
- hello@hips.comSection 15
This Data Processing Agreement (the DPA) is between HIPS Payment Group Limited (HIPS, we, us or our) and the Buyer that holds a Workspace and is a Business User (the Customer, you or your). HIPS engages its Affiliate Hyperscale Inference Processing Systems OÜ, which operates the Services for HIPS (the Operating Company, Common Clauses Section 3.1), as a Sub-processor (Annex 3). When your Workspace sends Requests, imports a Customer Model or stores files with the Services, HIPS processes on your behalf the personal data those contain. This DPA is the contract that Article 28 of the GDPR, and the corresponding provisions of the UK GDPR and the FADP where they apply, require for that processing. It forms part of the Terms of Service (the Terms) and of your Agreement with HIPS, without a separate signature. Capitalized terms are defined in Section 2, in Terms Section 2 and in Common Clauses Section 2.
Important: what this DPA covers, and what it does not
HIPS processes your personal data as your processor only to answer your Requests, run your Customer Models and keep the files you store, as your settings instruct (Sections 3 and 4). Two things are outside this DPA. First, HIPS's own purposes as a controller (Section 14): on the Free/PAYG Plan and the lower paid Plan, "request inputs and generated outputs may be used for training", and HIPS then uses them as an independent controller, not as your processor; on the higher paid Plan, Training is off unless an Owner or admin turns it on. Second, HIPS's own records, such as usage metadata, billing and security records. In the Personal Pool, the owner of the Device that runs a Request can in principle access the model and the Request Data while it runs, and in the Approved Pool so can the data-center operator; you may exclude the Personal Pool by requiring the Approved Pool (Section 7.4). HIPS's liability under this DPA is limited as the Common Clauses provide for your population (Section 15.1).
The commitments in brief
- Your instructions only. HIPS processes your personal data only to provide the Services to you, as your Agreement, your Workspace settings and your Requests instruct.
- Nothing kept by default. A Request's content is processed to answer it and is not stored, except as Batch Files, uploaded task inputs, the request bodies of asynchronous jobs, the results of task Requests and jobs, the answers kept for an idempotency key and the other cases this DPA lists, each for the period of Annex 1.
- Batch Files for thirty days. The input, output and error files of a Batch are deleted thirty (30) days after they are uploaded or produced (an input file still used by an open Batch, when that Batch ends), sooner if you set a shorter period or delete them, and they are never copied into backups.
- Prompt caches stay in your Workspace, for a limited time. Caches are automatic, isolated per Workspace and held in memory, never on disk. HIPS promises you no lifetime, but makes each cache unreadable within the longest period of Annex 1, and at once when you delete the Workspace, your Agreement ends or you ask, and then erases it from the worker's memory within the further period of Annex 1. Personal Devices run with their cross-request cache off.
- Who processes it. Sub-processors are named in Annex 3, beginning with the Operating Company. Providers in the Personal Pool are authorized as a category, bound by the Provider Agreement, listed in the Console by a pseudonymous identifier and their country, and never learn who you are; a Device takes your Requests only in a Device Country, and never in a restricted country. HIPS records which Provider ran each Request and shows your Owner and admins, at any time in the Console, who processed your data. You may exclude the Personal Pool at any time.
- Notice and objection. HIPS tells you at least thirty (30) days before it adds or replaces a named sub-processor, and before each new Provider receives your data if you subscribe to those notices, and you may object.
- Stored in Ireland, processed in three regions. HIPS keeps the data it stores for you in Ireland, except content stored for a Request that requires a region, which rests in that region, and processes Requests in its regional processing locations in Ireland, the United States and Japan, and on data-center capacity and Devices reached from them. On ai.hips.com, a Request is first decrypted, in memory only, at the Amazon CloudFront edge location nearest the client, in any country. A Request without a region requirement may be processed in any region. A region requirement, once offered, keeps processing and stored content in its region, and that region's own address keeps the connection there too. Transfers rest on adequacy decisions where they cover the recipient, and otherwise on the Standard Contractual Clauses (Section 9).
- Breaches, deletion and audits. HIPS tells you of a breach without undue delay and within forty-eight (48) hours of becoming aware of it, deletes your data when its period ends, and shows its compliance by documentation first.
- HIPS's own purposes are separate. Training where your Plan allows it, billing, fraud prevention and security are HIPS's own purposes as a controller, described in Section 14 and in the Privacy Notice.
01About this DPA
What this DPA is. This DPA sets out the terms on which HIPS processes Customer Personal Data as your processor, or as your sub-processor where you are a processor for another controller. It is the contract that Article 28(3) of the GDPR requires, and, where the UK GDPR or the FADP applies to the processing, the contract those laws require. Annex 4 (Section 19) adds the terms that the laws of Japan, the Republic of Korea, Singapore, Taiwan and Australia ask of a contract with a person to whom personal data is entrusted, for a Customer to which one of those laws applies.
Who it applies to. This DPA applies to every Customer: every Buyer that is a Business User, whatever its Country, including a US User who is a Business User. It is stated to apply to the Customer, and Common Clauses Section 1.4 therefore does not exclude US Users from it. It does not apply to a Buyer that is a Consumer, whose Request Data HIPS processes as a controller under the Privacy Notice (Terms Section 22.2).
Part of the Terms of Service. This DPA forms part of the Terms of Service and of your Agreement with HIPS. You accept it when you accept the Terms of Service as a Business User, or when you declare that you act as a Business User, without a separate signature. HIPS records the version of this DPA with your acceptance (Common Clauses Section 17.7). A change to this DPA is a change to the Terms of Service and follows Common Clauses Section 9.
Order of precedence. For the processing of Customer Personal Data that HIPS carries out on your behalf as a processor, this DPA prevails over the other documents of your Agreement, except an agreement signed by you and HIPS (Common Clauses Section 17.3). Where the Standard Contractual Clauses apply under Section 9, they prevail over this DPA. This DPA does not depart from Common Clauses Sections 4 to 6, which govern liability under it (Section 15.1), or from Common Clauses Sections 12 to 15, which govern Disputes about it, except as the Standard Contractual Clauses require for a Dispute arising from them.
Prelaunch. On the date this DPA was last updated, the Services are prelaunch and HIPS processes no Customer Personal Data. A part of this DPA that concerns a feature applies only once HIPS releases that feature (Terms Section 1.6). Training jobs and their datasets are not Customer Personal Data under this DPA until HIPS amends it under Section 15.5 before they open.
02Definitions and interpretation
Further definitions. The terms defined in Common Clauses Section 2.1 and Terms Section 2 have the same meanings in this DPA, including Account, Agreement, Applicable Law, Approved Pool, Approved Provider, Business User, Buyer, Consumer, Country, Customer Model, Device, Dispute, Durable Medium, EEA, GDPR, Input, Legal Information Page, Member, Operating Company, Output, Personal Pool, Plan, Provider, Provider Agreement, Purchased Credits, Restricted Jurisdiction, Request, Request Data, Track, US User, Workspace, Always-On Capacity, API Key, Authorized Tool, Batch, Batch File, Batch Line, Completion Window, Hub Token, Owner, Prefix Ledger, Request-Data Policy and Training; a prompt cache is the state that Terms Section 9.9 describes. Assignment, Attempt, Engine, Provider Country, Sandbox and Test Assignment have the meanings that the Provider Agreement gives them, and Device Country the meaning that Section 7.3 gives it. "Controller", "processor", "personal data", "processing", "data subject" and "supervisory authority" have the meanings that Applicable Data Protection Law gives them. In addition:
- Applicable Data Protection Law
- means the GDPR, the UK GDPR, the FADP, the laws of the Member States of the European Union and of the EEA that implement or supplement the GDPR, including the Data Protection Acts 1988 to 2018 of Ireland and the Estonian Personal Data Protection Act, and any other data protection law that applies to the processing of Customer Personal Data under this DPA.
- Customer
- has the meaning given in the opening paragraph of this DPA.
- Customer Personal Data
- means the personal data that HIPS processes on your behalf in providing the Services to your Workspaces, which Annex 1 describes: personal data in Request Data, including Batch Files, uploaded task inputs, the request bodies of asynchronous jobs, the results of task Requests and jobs and the answers kept for an idempotency key, in the metadata and file names you attach to Batches, Batch Files and uploads, in prompt caches, in Customer Models and in Hub Tokens. It does not include HIPS Controller Data.
- FADP
- means the Swiss Federal Act on Data Protection of 25 September 2020 and its ordinances.
- HIPS Controller Data
- means the personal data that HIPS processes for its own purposes as a controller, as Section 14 and the Privacy Notice describe, including the Training copies HIPS makes where your Plan allows Training.
- Personal Data Breach
- means a breach of security leading to the accidental or unlawful destruction, loss, alteration, unauthorized disclosure of, or access to, Customer Personal Data while HIPS or a Sub-processor processes it.
- Standard Contractual Clauses or SCCs
- means the standard contractual clauses for the transfer of personal data to third countries set out in the Annex to Commission Implementing Decision (EU) 2021/914 of 4 June 2021.
- Sub-processor
- means a processor that HIPS engages to process Customer Personal Data, including the Operating Company and each other sub-processor named in Annex 3, each Approved Provider and each Provider.
- Swiss Amendments
- means the adaptations of the SCCs set out in Section 9.6.
- UK Addendum
- means the International Data Transfer Addendum to the EU Commission Standard Contractual Clauses issued by the Information Commissioner under section 119A(1) of the Data Protection Act 2018, version B1.0, as it may be revised.
- UK GDPR
- means the GDPR as it forms part of the law of the United Kingdom, as defined in section 3(10) of the Data Protection Act 2018.
- Workspace Settings
- means the settings of a Workspace and its API Keys, made in the Console or through the API: the pool, region and fallback requirements of API Keys and Requests, the Request-Data Policy where the Plan lets it be changed, the expiry you set for Batch Files, and the deletion of Batch Files, uploads, results, Customer Models, Hub Tokens and Workspaces.
Interpretation. Common Clauses Section 2.2 applies to this DPA. A reference to an Article of the GDPR includes, where the UK GDPR or the FADP applies, the corresponding provision of that law.
03Roles and scope
Your role and HIPS's role. You are the controller of Customer Personal Data, and HIPS processes it as your processor. If you process Customer Personal Data as a processor for another controller, HIPS is your sub-processor, and:
- (a)you warrant that your controller has authorized your instructions to HIPS, the engagement of HIPS and of the Sub-processors this DPA authorizes, the transfers of Section 9, and the disclosure from which HIPS derives the Prefix Ledger (Section 14.2);
- (b)you are HIPS's only point of contact: HIPS deals with your controller only through you, unless Applicable Data Protection Law requires otherwise, and you pass on to your controller every notice and every piece of information HIPS gives you under this DPA;
- (c)your controller exercises any right it has against HIPS, including an audit right, only through you and under the conditions of this DPA; and
- (d)where the Plan of a Workspace allows Training, you warrant that your controller has authorized in writing the disclosure to HIPS for Training that Section 14.3 describes; without that authorization you shall not send your controller's personal data from a Workspace whose Request-Data Policy allows Training.
What HIPS processes on your behalf. HIPS processes Customer Personal Data only to provide the Services to your Workspaces: to receive your Requests and Batches at HIPS's regional processing locations, route them, forward them between those locations as Section 9.1 provides, and answer them in the Personal Pool or the Approved Pool, to keep prompt caches for your Workspace, to place Requests and Batch Lines on a worker that holds a prompt cache of their Workspace and to group Batch Lines that begin with the same content, using hashes of blocks of the tokens of their Inputs and the entries of the Prefix Ledger for the same Workspace (Terms Sections 6.24 and 9.9(c)), to store and return Batch Files, uploaded task inputs, the request bodies of asynchronous jobs, the results of task Requests and jobs and the answers kept for an idempotency key, to import, check, re-save, sign, store, profile and run your Customer Models, to keep your Hub Tokens and use them for your imports, to verify the work of Providers, to screen Request Data in memory, before any of it is made available to HIPS for Training, so that Requests revealing special categories of personal data, personal data relating to criminal convictions or offenses or personal data concerning a child, or that the filters cannot assess, are not made available, and to mask the identifiers and secrets that Section 14.3(f) lists, to keep content for debugging when you ask for it in writing, and to delete all of it. Annex 1 sets out the particulars of the processing.
What this DPA does not cover. This DPA does not govern HIPS Controller Data, which HIPS processes for its own purposes as Section 14 and the Privacy Notice describe: among it, the personal data of your Members and of your billing contacts, usage metadata, billing, tax and ledger records, identity verification records, the record that HIPS derives from Request Data and keeps for the purposes of its own that Section 14.2 states (the Prefix Ledger, as Terms Section 2.2 defines it: the record HIPS keeps of pseudonymized hashes of blocks of the tokens of the Inputs of Requests to language models served by data-center workers whose prompt cache is on, keyed for each cache scope as Terms Section 13.7 states, with the worker that served each Request and the time, used only as Terms Section 13.7 describes; for your Workspaces the cache scope is the Workspace, and the Prefix Ledger holds no prompt text; Section 14.2, Annex 1 and Privacy Notice Section 6.12), and the Training copies HIPS makes where your Plan allows Training. HIPS's use of the Prefix Ledger to place Requests and Batch Lines on workers and to group Batch Lines, which Terms Section 13.7 also lists, is processing on your behalf, which this DPA governs (Section 3.2). The prompt caches themselves are Customer Personal Data, which this DPA governs: HIPS keeps them only in the memory of data-center workers, never on disk, uses them only for Requests of the same Workspace, makes each of them unreadable no later than the longest life that Annex 1 states, and erases each of them within the further period that Annex 1 states (Terms Section 9.9(g)).
HIPS does not read your content. HIPS does not inspect Request Data to find out whether it contains personal data, or what kind, except as Terms Section 13.8 allows, and except the automated screening of Section 14.3(f), which keeps nothing of what it screens out. HIPS relies on you to decide what you send, under which Plan, Workspace Settings and pool requirements (Section 4.5).
04Your instructions
Your documented instructions. You instruct HIPS to process Customer Personal Data to provide the Services as your Agreement describes them. Your documented instructions are:
- (a)your Agreement, including this DPA and Annex 1;
- (b)your Workspace Settings;
- (c)each Request, Batch, upload, import and deletion that your Members, your API Keys or your Authorized Tools make through the Console or the API; and
- (d)any further instruction that you give HIPS in writing and that HIPS accepts in writing under Section 4.3.
Processing only on instructions. HIPS processes Customer Personal Data only on your documented instructions, including as regards transfers to a third country, unless Union or Member State law to which HIPS is subject requires it to process otherwise. In that case HIPS tells you of that legal requirement before the processing, unless that law prohibits it on important grounds of public interest.
Further instructions. An Owner or admin of the Workspace may give HIPS a further instruction in writing. HIPS follows it if it is consistent with your Agreement and the Services as HIPS provides them to every Customer. HIPS may decline an instruction that would require it to change the Services, its Sub-processors or its measures for you alone, or that it cannot follow without disproportionate effort, and it tells you why. If HIPS declines an instruction that Applicable Data Protection Law requires you to give, you may stop the processing concerned and terminate your Agreement under Common Clauses Section 9.4, with the refunds that Section provides.
Instructions that infringe the law. HIPS tells you at once if, in its opinion, an instruction infringes Applicable Data Protection Law, and it may suspend the processing concerned until you confirm or change the instruction. HIPS has no duty to review your instructions for lawfulness beyond this.
Your responsibilities. As the controller, you are responsible for the lawfulness of the processing you instruct. In particular, you represent, warrant and undertake that:
- (a)you have, and will keep, a lawful basis for each processing you instruct, including the processing in the pools and countries your Workspace Settings allow, the disclosure that Section 14.3 describes where your Plan allows Training, and the disclosure from which HIPS derives the Prefix Ledger (Section 14.2), and, where you are a processor, your controller's authorization of those disclosures, in writing for Training (Section 3.1(a) and (d));
- (b)you have given, and will give, the data subjects concerned the information that Applicable Data Protection Law requires, including that their personal data may be processed by Providers in the Personal Pool, and the Request-Data Policy of your Plan;
- (c)you do not send, in Request Data or in a Customer Model, the categories of personal data that Terms Section 13.12 excludes, except as HIPS agrees in a signed document;
- (d)you have chosen the Plan, the pools, the region and fallback requirements, the address to which you send Requests (Section 9.1(d)) and the expiry of Batch Files that are appropriate for your data, after considering the conditions of each pool that Terms Section 17 and Annex 2 describe; and
- (e)your instructions comply with Applicable Data Protection Law.
05Confidentiality
HIPS's personnel. HIPS ensures that every person it authorizes to process Customer Personal Data is bound by a duty of confidentiality, by contract or by law. HIPS's personnel work from metadata first and reach Customer Personal Data only for a purpose, with an authorization and a record, as Annex 2 describes.
Sub-processors. HIPS binds every Sub-processor to confidentiality, including every Provider under Provider Agreement Sections 6.6 and 8.4.
Requests from authorities. If a public authority asks HIPS for Customer Personal Data, HIPS refers the authority to you where it can, discloses only what the law compels, and tells you of the request unless the law prohibits it. Where a request appears to HIPS to exceed what the law allows, HIPS uses the legal remedies reasonably available to it. HIPS treats a request of a public authority that concerns the Prefix Ledger, or that asks HIPS to establish whether a Workspace sent a given content, as a request for Customer Personal Data under this Section. Provider Agreement Section 8.14 imposes the same duty on Providers.
06Security
HIPS's measures. HIPS implements and maintains the technical and organizational measures set out in Annex 2, which are designed to ensure a level of security appropriate to the risk, as Article 32 of the GDPR requires.
Your assessment. You have reviewed Annex 2, the conditions of each pool in Terms Section 17 and the protections HIPS publishes for each pool, and you agree that, together with the Workspace Settings you choose, they provide a level of security appropriate to the risks of the processing you instruct.
Important: what the security measures do not prevent
What the measures do not prevent. "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." In the Personal Pool, the owner of a Device has physical control of it and can in principle access the model and the Request Data while a Request runs; the Provider Agreement forbids it and HIPS's verification detects dishonest Outputs, but not silent copying. In the Approved Pool, the data-center operator administers the host. HIPS makes no claim of confidential computing for either pool.
Updates to the measures. HIPS may update the measures of Annex 2, provided that an update does not materially lower the overall level of security of Customer Personal Data. HIPS publishes the current measures and tells you on a Durable Medium of an update that materially changes them.
Your own security. You are responsible for the security of your Accounts, your API Keys, your Authorized Tools, your systems and your Workspace Settings, and for the measures you apply before Customer Personal Data reaches the Services (Terms Section 5).
07Sub-processors
General written authorization. You give HIPS a general written authorization to engage, as Sub-processors:
Conditions for every Sub-processor. HIPS engages a Sub-processor only by a written contract that imposes on it the same data protection obligations as this DPA imposes on HIPS, in particular sufficient guarantees to implement appropriate technical and organizational measures, as far as they concern the processing that the Sub-processor performs. HIPS remains responsible to you for the performance of each Sub-processor's obligations as Article 28(4) of the GDPR and Common Clauses Section 3.8 provide.
Providers as a category. Providers are natural persons and organizations that supply GPU Time to HIPS from their own Devices under the Provider Agreement and whose Country is a Provider Country (Provider Agreement Section 3.3): the United States, the United Kingdom, a state of the EEA, Switzerland, Canada, Japan, Singapore, the Republic of Korea, Taiwan or Australia, each from the date the Console lists it as open. A Provider's Devices may be located in any country other than a Restricted Jurisdiction, but a Device processes Customer Personal Data only while it is located in a Device Country: a state of the EEA, a country for which an adequacy decision of the European Commission is in force, or a country that HIPS has opened after the assessment of Section 9.3, as the Legal Information Page lists them. HIPS takes the country of each Device from the network address of each of its connections, and the Provider never reports it. HIPS assigns no Request to a Device that it locates in a Restricted Jurisdiction, and no Request of yours to a Device that connects through a virtual private network, a proxy or another anonymizing network, or whose location HIPS cannot confirm, until HIPS has confirmed its location (Common Clauses Section 7.6); where the Device's operating system allows it, the Provider App may reach HIPS outside a virtual private network so that HIPS can confirm it. When a Device first connects from a country that is not yet a Device Country, HIPS assesses that country under Section 9.3 and opens it as a Device Country where the assessment allows, adding it to the Legal Information Page; until then, the Device takes only Test Assignments, which carry no Customer Personal Data. HIPS authorizes Providers individually, by enrollment, identity verification and the checks of each Device, and does not name them in Annex 3, because their number changes continually. HIPS makes their identities readily available to you at all times: the Console shows the Owner and admins of each Workspace whose requirements allow the Personal Pool, under the duty of confidentiality of Common Clauses Section 3.8 and the prohibition of Terms Section 17.9, the name, Provider Country and contact address of every Provider on the Workspace's list and of every Provider whose Device processed its Customer Personal Data, with the period in which it did, from the record that HIPS keeps of the Provider and the Device that ran each Request and Batch Line of your Workspaces for thirteen (13) months; you may download that information as a file; and HIPS gives it to you within five (5) business days of a written request if the Console cannot.
Excluding the Personal Pool. You may at any time exclude Providers from the processing of your Customer Personal Data, for all of your Workspace or for any API Key or Request, by requiring the Approved Pool in your Workspace Settings with cross-pool fallback off. That exclusion is how you object to Providers as a category, and it is always available to you without a reason. No Customer Model runs in the Personal Pool at launch (Terms Section 15.8).
Notice of a new or replaced sub-processor. HIPS tells you of any intended addition or replacement of a sub-processor named in Annex 3, or of an Approved Provider, at least thirty (30) days before the new sub-processor processes Customer Personal Data, by a notice to the Owner and admins of your Workspaces on a Durable Medium and by updating the list on the Legal Information Page. HIPS gives the same notice of a change to the description of Providers as a category that widens it, such as a new Provider Country or the opening of the Personal Pool to Customer Models. HIPS gives this notice, to the Owner and admins of every Workspace that exists when it takes effect, before a Request of that Workspace runs on a Device in a country that HIPS opens as a Device Country, naming that country; you may object under Section 7.6 or exclude the Personal Pool under Section 7.4. The Provider Country shown for each Provider in the list below is the Provider's own Country, which may differ from where its Devices are located. HIPS gives this notice of its regional processing locations in the United States and Japan, of Amazon Web Services and RunPod at those locations (Annex 3), and of Japan, Singapore, the Republic of Korea, Taiwan and Australia as Provider Countries, to the Owner and admins of every Workspace that exists when they are added, before a Request of that Workspace is processed at those locations or on a Device in those countries. HIPS keeps in the Console, for each Workspace whose requirements allow the Personal Pool, a current list of the Providers that may receive its Requests, each with a stable pseudonymous identifier and its Provider Country, and notifies the Owner and admins who subscribe of each Provider added before that Provider receives Customer Personal Data; you object to any of them by excluding the Personal Pool under Section 7.4, which applies to every Request accepted after you set it.
Your objection. You may object to a change under Section 7.5, in writing, before the end of the notice period, on reasonable grounds relating to the protection of Customer Personal Data. HIPS and you then discuss the objection in good faith, and HIPS may offer a way to avoid the change for your Customer Personal Data, such as a pool or region requirement. If the objection is not resolved before the change takes effect, you may, as your only remedy for the change, terminate your Agreement, or stop using the part of the Services the change concerns, by notice before the change takes effect; HIPS then refunds your unused Purchased Credits and the unused part of any prepaid Plan fee, as Common Clauses Section 9.4 provides. An objection does not oblige HIPS to forgo the change.
Urgent replacement. Where HIPS must replace a sub-processor sooner than Section 7.5 allows, because the sub-processor has failed, has stopped its service or presents a risk to the security of Customer Personal Data, HIPS may do so at once and tells you as soon as it can. Section 7.6 then applies from that notice.
08Providers in the Personal Pool
The flow-down. Provider Agreement Section 8 is the contract between HIPS and each Provider that Article 28(4) of the GDPR requires. It imposes on every Provider, wherever located, the data protection obligations of this DPA as far as they concern the processing a Device performs. In particular, each Provider:
- (a)processes Request Data only on HIPS's documented instructions, which are the Provider Agreement and each Assignment, including the Engine settings that HIPS sets, and nothing else (Provider Agreement Section 8.3);
- (b)keeps Request Data confidential and lets nobody access it (Provider Agreement Sections 6.6 and 8.4);
- (c)keeps in place every protection of the Provider App and the Sandbox, and never turns on a cache, learning or recall feature of an Engine that HIPS has turned off (Provider Agreement Sections 6.5, 6.7, 6.12 and 8.5);
- (d)engages no other processor and passes no Assignment to another machine or person (Provider Agreement Section 8.6);
- (e)tells HIPS without undue delay of any actual or suspected personal data breach (Provider Agreement Section 8.7);
- (f)assists HIPS as Articles 28(3)(e) and (f) of the GDPR require (Provider Agreement Section 8.8);
- (g)keeps no Request Data after an Attempt ends (Provider Agreement Section 8.9);
- (h)makes information available and contributes to audits, which HIPS carries out by remote means (Provider Agreement Section 8.10);
- (i)is bound by the Standard Contractual Clauses where its Device is outside the EEA, the United Kingdom and Switzerland, whether or not an adequacy decision also covers it (Provider Agreement Section 8.11; Section 9.3); and
- (j)tells HIPS of any request by a public authority for Request Data (Provider Agreement Section 8.14).
What a Device holds. A Device processes Request Data in memory only, inside the Sandbox, subject to what the operating system of the Device writes to swap or hibernation, as Annex 2 states, for one Attempt at a time, and the Provider App releases and overwrites what it held when the Attempt ends. At launch every Engine on a Device runs with its cross-request cache off and with every feature that records, learns from or recalls Request Data across Attempts turned off, so no prompt cache of your Workspace exists on any Device. A Device never learns your identity, your Workspace's name, your API Keys or your prices (Provider Agreement Section 4.10).
Customer Models. No Customer Model runs on a Device at launch. If HIPS later opens the Personal Pool to Customer Models, it does so only for Customer Models in ONNX format, only for a deployment you opt into after being told that the Device owner's machine holds the weights, only on Devices whose owner has turned on the per-device switch, and only in memory and in the Sandbox (Provider Agreement Section 7; Terms Section 15.8), and it gives you notice under Section 7.5 before it does.
Verification of Providers. HIPS verifies the conformity of Providers' work with the methods described in Provider Agreement Section 22.2, including test Assignments, timing envelopes, memory probes, the sampling of completed work against the Approved Pool and software integrity checks. Those methods detect dishonest results; they do not detect silent copying (Section 6.3). HIPS enforces the Provider Agreement, including by suspension, removal and the measures of the Provider Agreement for Fraud, and tells you of a breach that affects your Customer Personal Data as Section 11 provides.
What you accept. You accept that a Device's owner has physical control of it, that the protections of this Section 8 are technical measures and contractual duties that make deliberate access a breach of the Provider Agreement but not technically impossible, and that you may exclude the Personal Pool at any time (Section 7.4).
Approved Providers. Each Approved Provider processes Customer Personal Data under a commercial agreement with HIPS that meets Section 7.2, on HIPS's worker images and behind the worker contract that Annex 2 describes. HIPS publishes the execution protections and access conditions of each Approved Provider on the Legal Information Page before you deploy workloads to it, and the criteria under which it approved it. HIPS uses RunPod's Secure Cloud only, never its Community Cloud, for any workload that receives Customer Personal Data or a Customer Model.
09International transfers
Where HIPS processes Customer Personal Data. HIPS hosts the Services with Amazon Web Services and keeps the Customer Personal Data it stores for your Agreement in Ireland (region eu-west-1), except content stored for a Request that requires a region, such as its uploads, the files of its Batch, its asynchronous results and the copy of a Customer Model deployed in that region, which rests in that region's storage; content stored for a Request without a region requirement rests in Ireland, and no Workspace setting stores it elsewhere. HIPS processes Requests in its regional processing locations in Ireland (eu-west-1), the United States (us-east-2, Ohio) and Japan (ap-northeast-1, Tokyo), and on the data-center capacity of the Approved Pool and the Devices of the Personal Pool reached from them:
- (a)the regions are "eu", the EEA (the 27 member states of the European Union, Iceland, Liechtenstein and Norway); "us", the United States (its fifty states and the District of Columbia); and "jp", Japan;
- (b)a Request sent to ai.hips.com passes through the Amazon CloudFront edge location nearest the client, which decrypts it in memory only (point (d) and Annex 2), and reaches the nearest regional processing location; without a region requirement, it may be processed there or, where that location has no eligible capacity, forwarded to another region's location and processed there, and it may run on data-center capacity in the EEA, the United States or Japan or on a Device in a Device Country (Section 7.3);
- (c)region selection is an intended feature of the higher paid Plan, offered for a region only once HIPS enforces it there (Terms Section 6.8); where a region requirement applies, the processing of the Request, every retry and fallback, and the content stored for it stay in the region, and no Request, retry or fallback crosses it; a region requirement does not cover HIPS Controller Data, such as account data and billing records, which HIPS keeps in Ireland, the operational logs, metrics and error and crash reports of the Services, which carry no Customer Personal Data, access by HIPS personnel to stored content under Annex 2, which takes place from the European Union, or the decryption on ai.hips.com that point (d) describes;
- (d)on eu.ai.hips.com, us.ai.hips.com and jp.ai.hips.com, encryption ends only inside the regional processing location of that region, no edge network is in between, and a Request there that requires another region is refused; a Request that requires a region and is sent to ai.hips.com may first reach a location outside its region, which decrypts it in memory only, stores nothing of its content, forwards it to its region and relays the response; that decryption is processing of Customer Personal Data in the country of that location, with Amazon Web Services, which HIPS treats as a transfer to that country with the safeguards of Section 9.7; and on ai.hips.com every Request is first decrypted, in memory only and with no response cached, at the Amazon CloudFront edge location nearest the client, in any country where CloudFront operates, which HIPS treats as a transfer by Amazon Web Services to that country with the safeguards of Section 9.7; a region requirement covers neither; a Customer that needs the connection itself kept inside a region therefore sends its Requests to that region's address; and
- (e)each regional processing location holds Request Data only in memory while it routes the Request, forwards it and relays its result, and keeps in its own region the stores that Annex 1 lists.
Your authorization. You authorize the transfers of Customer Personal Data to the Sub-processors and the countries that Annex 3 and Section 7.3 describe, the Devices of Providers in the Device Countries of Section 7.3 among them, made with the safeguards of this Section 9. HIPS makes no other transfer of Customer Personal Data to a third country except on your documented instructions or where Union or Member State law requires it.
Providers outside the EEA. Where a Device is located outside the EEA, the United Kingdom and Switzerland, the SCCs apply between HIPS, as data exporter, and the Provider, as data importer, as Provider Agreement Section 8.11 incorporates them, whether or not an adequacy decision also covers the Provider, with the choices in the table below. HIPS assigns no Request or Batch Line of a Customer to such a Device unless those SCCs bind its Provider and HIPS has assessed the laws and practices of the country where the Device is located, as Clause 14 of the SCCs requires, and documented that assessment, and HIPS concludes the SCCs by the Provider's recorded acceptance of the Provider Agreement, which is the Provider's signature of Annex I. When a Device first connects from a country that is not yet a Device Country, HIPS makes and documents that assessment for that country, and opens it as a Device Country (Section 7.3) only where the assessment shows that the SCCs, with any supplementary measures it identifies, give the Customer Personal Data processed there a level of protection essentially equivalent to that guaranteed within the EEA; until then, no Request or Batch Line of a Customer runs on a Device there.
| Item | Choice |
|---|---|
| Module | Module Three (processor to processor) for Customer Personal Data; Module Two (controller to processor) for personal data of which HIPS is the controller |
| Clause 7 (docking clause) | Not included |
| Clause 9 (use of sub-processors) | Option 1, specific prior authorization, with no sub-processor authorized (Provider Agreement Section 8.6) |
| Clause 11 (redress) | The optional wording is not included |
| Clause 13 (supervision) | The Data Protection Commission (Ireland) |
| Clause 17 (governing law) | Option 1: the law of Estonia |
| Clause 18 (choice of forum) | The courts of Estonia, without prejudice to Clause 18(c) |
| Annex I | Annex 1 of this DPA and Provider Agreement Section 8.2 |
| Annex II | Annex 2 of this DPA as it applies to Devices, and Provider Agreement Sections 5 to 8 |
| Annex III | Not applicable: no sub-processor is authorized |
The law of Estonia, which recognizes contracts for the benefit of third persons, governs these Clauses because Clause 17 requires the law of a Member State that allows third-party beneficiary rights.
Countries with an adequacy decision. Where a Device or a Sub-processor is located in a country for which an adequacy decision of the European Commission applies and covers it, HIPS relies on that decision. These include the United Kingdom and Switzerland and, for the recipients each decision covers: Canada; Japan, under Implementing Decision (EU) 2019/419, for personal information handling business operators in Japan subject to the Act on the Protection of Personal Information as complemented by the Supplementary Rules; the Republic of Korea, under Implementing Decision (EU) 2022/254, for entities in the Republic of Korea subject to the Personal Information Protection Act; and the United States, under Implementing Decision (EU) 2023/1795, for organizations certified under the EU-U.S. Data Privacy Framework, on which HIPS relies only together with the SCCs where the recipient's terms offer them. For a Provider, the SCCs of Section 9.3 apply in addition to any adequacy decision.
The UK GDPR. Where the UK GDPR applies to a transfer of Customer Personal Data to a country or a recipient for which no regulations under Article 45A of the UK GDPR approve the transfer, the SCCs apply as amended by the UK Addendum (version B1.0 issued by the Information Commissioner), whose Table 1 names the parties as Annex I.A of the SCCs names them and starts on the date the SCCs first apply between them, whose Table 2 selects the Modules and clauses that this Section 9 and Provider Agreement Section 8.11 select, whose Table 3 is completed by Annexes 1 to 3 of this DPA and Provider Agreement Section 8.2, and in whose Table 4 neither party may end the UK Addendum when it changes; and HIPS makes the transfer only where, acting reasonably and proportionately, it considers that the data protection test of Article 46 of the UK GDPR is met. This applies, among others, to Customer Personal Data subject to the UK GDPR that HIPS processes in its regional processing locations in the United States and Japan, except that in the United States HIPS relies on the certification of Amazon Web Services, Inc. under the UK Extension to the EU-U.S. Data Privacy Framework, and in Japan on the regulations of the United Kingdom that approve transfers to Japan, which cover private-sector businesses subject to the Act on the Protection of Personal Information.
The FADP. Where the FADP applies to a transfer of Customer Personal Data to a country that the Swiss Federal Council has not recognized as providing adequate protection, the SCCs apply with the following adaptations (the Swiss Amendments): references to the GDPR are to the FADP as far as the transfer is subject to it; the Swiss Federal Data Protection and Information Commissioner is the competent supervisory authority under Clause 13 for such a transfer; the term "Member State" in Clause 18(c) does not prevent a data subject in Switzerland from bringing proceedings in their place of habitual residence; and the SCCs protect the personal data of legal persons only where the FADP does. This applies, among others, to Customer Personal Data subject to the FADP that HIPS processes in its regional processing locations in the United States and Japan, except that in the United States HIPS relies on the certification of Amazon Web Services, Inc. under the Swiss-U.S. Data Privacy Framework, which the Swiss Federal Council recognized from 15 September 2024. In Japan, which the Swiss Federal Council has not recognized, HIPS processes Customer Personal Data subject to the FADP only for a Workspace that requires the region "jp", on that Customer's instruction, with the SCCs of Section 9.3 and the Swiss Amendments for any Device there, and a Request of a Workspace whose Country is Switzerland is not forwarded there for want of supply. A Customer that needs its Requests kept away from Amazon CloudFront edge locations in countries that the Swiss Federal Council has not recognized sends them to eu.ai.hips.com, which no edge network fronts (Section 9.1(d)).
Sub-processors. Annex 3 states the safeguard on which HIPS relies for each sub-processor that processes Customer Personal Data outside the EEA or that is established in a third country, such as the SCCs or the recipient's certification under the EU-U.S. Data Privacy Framework. For Amazon Web Services in the United States, HIPS relies on the certification of Amazon Web Services, Inc. under the EU-U.S. Data Privacy Framework and on the SCCs of its data processing terms should that framework cease to cover it; for Amazon Web Services in Japan, on the adequacy decision for Japan, the Amazon Web Services company that processes the data there being subject to the Act on the Protection of Personal Information, with the safeguards for the United States for any access from there; for Amazon CloudFront's edge locations, on the certification of Amazon Web Services, Inc. under the EU-U.S. Data Privacy Framework in the United States and on the SCCs of its data processing terms in any other country without an adequacy decision; and for RunPod's data centers in the United States and Japan, on the SCCs (Module Three) of its data processing agreement with Runpod Inc., which is not certified under that framework, with a transfer impact assessment, and in Japan also on the adequacy decision where it covers RunPod's processing there. The Operating Company operates the Services from Estonia, and the Sub-processors it engages for HIPS, with their locations and safeguards, are those of Annex 3.
Customers outside the EEA. Where you are established in a third country without an adequacy decision, HIPS's return of Customer Personal Data to you is a transfer by HIPS, as a processor subject to the GDPR, to a controller in a third country, and Module Four (processor to controller) of the SCCs applies between HIPS, as data exporter, and you, as data importer, with the law and the courts of Estonia under Clauses 17 and 18, and the UK Addendum or the Swiss Amendments where Sections 9.5 and 9.6 apply. HIPS returns to you only Customer Personal Data that it received from you or produced from it to answer your Requests, and does not combine it with personal data that HIPS collected in the European Union; the clauses of Module Four that apply only to such a combination therefore do not apply, unless HIPS combines them, in which case they apply.
If a safeguard fails. If a safeguard on which a transfer relies is invalidated or no longer suffices, HIPS may stop assigning Requests that carry Customer Personal Data to Devices in the countries concerned, or stop the transfer to the Sub-processor concerned, and it tells you which alternative it applies. If no lawful alternative exists for a Sub-processor in Annex 3, Section 7.6 applies as if HIPS had given notice of its replacement.
Your own transfer rules. Where you are established in Japan, the Republic of Korea, Singapore, Taiwan or Australia, or the law of one of them otherwise governs Customer Personal Data, that law may set its own rules on providing personal data to a recipient outside the country. For those rules:
- (a)HIPS processes Customer Personal Data in Ireland, the United States and Japan, at Amazon CloudFront edge locations for Requests to ai.hips.com, and on Devices in the Device Countries, as Section 9.1, Section 7.3 and Annex 3 state, and you may exclude the Personal Pool (Section 7.4) and, where region selection is offered to you, keep processing and stored content in one region (Section 9.1(c));
- (b)HIPS processes Customer Personal Data under this DPA wherever it processes it, applies to that processing the GDPR, which binds HIPS as a company established in the European Union, and binds its Sub-processors and Providers to the same obligations (Sections 7.2 and 8.1 and the SCCs of Section 9.3);
- (c)HIPS gives you, on request, the information about its processing locations, Sub-processors, Provider Countries and measures that you need for the notices and consents your law requires of you, such as under Article 28 of Japan's Act on the Protection of Personal Information, Article 28-8 of the Republic of Korea's Personal Information Protection Act, section 26 of Singapore's Personal Data Protection Act 2012 and Australian Privacy Principle 8, and assists you with them as Section 10 provides; and
- (d)Annex 4 (Section 19) sets out the further terms, information and assistance HIPS gives for each of those laws.
10Assistance
Requests from data subjects. Taking into account the nature of the processing, HIPS assists you by appropriate technical and organizational measures, as far as possible, in responding to requests from data subjects to exercise their rights:
- (a)HIPS forwards to you, without undue delay, any request it receives from a data subject about Customer Personal Data that it can identify as yours, and does not respond to it itself, except to tell the data subject to contact you, unless Applicable Data Protection Law requires otherwise;
- (b)the Console and the API let you delete Batch Files, uploads, results, Customer Models, Hub Tokens and Workspaces yourself, and set a shorter expiry for Batch Files; and
- (c)because HIPS does not store Request Data by default (Terms Section 13.7), HIPS may hold no copy of the personal data a request concerns, and it tells you so.
A request that concerns HIPS Controller Data, including a Training copy, an objection to Training, or a request or objection about the Prefix Ledger, HIPS handles itself as a controller, as Section 14 and the Privacy Notice describe (Privacy Notice Section 11.6), and does not forward it to you.
Impact assessments and prior consultation. Taking into account the nature of the processing and the information available to it, HIPS assists you with your data protection impact assessments and prior consultations with a supervisory authority under Articles 35 and 36 of the GDPR, by giving you the information on the Services, the pools, Annex 2 and its Sub-processors that HIPS publishes or reasonably holds.
Security and breaches. HIPS assists you in meeting your obligations under Articles 32 to 34 of the GDPR by the measures of Annex 2 and by notifying you under Section 11.
Costs. HIPS gives the assistance of this Section 10 that consists of its self-service tools, the information it publishes and the forwarding of requests without charge. HIPS may charge its reasonable and proportionate costs for further assistance that you ask for, at rates it tells you in writing before it gives that assistance, and never at a level that would deter you from asking for assistance that Article 28(3)(e) or (f) of the GDPR requires. HIPS charges nothing for its notices and information under Section 11, or where the need for the assistance results from HIPS's breach of this DPA.
11Personal Data Breaches
Notice to you. HIPS notifies you without undue delay after becoming aware of a Personal Data Breach, and in any case within forty-eight (48) hours, by a notice to the Owner and admins of the Workspaces concerned on a Durable Medium. Where HIPS cannot then give all the information of Section 11.2, its first notice says what it knows and the rest follows in phases. For a Customer in Japan, this notice is also the notice by which an entrusted person informs the business that entrusted it under Article 26(1) of the Act on the Protection of Personal Information.
Contents. The notice describes, as far as HIPS then knows them, the nature of the Personal Data Breach, including the categories and approximate number of data subjects and of records concerned, the likely consequences, the measures HIPS has taken or proposes to take to address it and to mitigate its possible adverse effects, and a contact point at HIPS. Where HIPS cannot give all of this at once, it gives it in phases without undue further delay.
HIPS's measures. HIPS takes reasonable steps to contain, investigate and remedy each Personal Data Breach, records it as an incident, and keeps you informed of material developments. Where a Personal Data Breach occurs at a Provider or another Sub-processor, HIPS acts on the Sub-processor's notice as this Section 11 requires.
Your notifications. You are responsible for any notification of a Personal Data Breach to a supervisory authority and to data subjects that Applicable Data Protection Law requires of you as the controller. HIPS makes no such notification for you unless you and HIPS agree it in writing or the law requires it, and except that HIPS notifies, as a controller, a breach that concerns HIPS Controller Data.
No admission. A notice under this Section 11 is not an admission of fault or liability by HIPS.
Isolation faults. Where HIPS finds that a prompt cache of one Workspace may have been read for a Request of another, including where a worker reports a cache hit that the Prefix Ledger cannot support, HIPS handles it as a Personal Data Breach under this Section 11, containing, investigating and recording it, until it establishes that no Customer Personal Data reached another Workspace (Annex 2). HIPS gives the notice of Section 11.1 for it once it has not established that within twenty-four (24) hours after the fault is detected, and the notice says that the fault is still under investigation. A fault that HIPS establishes within that period let no Customer Personal Data reach another Workspace is recorded as an incident, and HIPS tells you of it on request. Sections 13.2 and 13.3(e) apply to an isolation fault only once HIPS has established that Customer Personal Data reached another Workspace.
12Deletion and return
During your Agreement. HIPS keeps Customer Personal Data only for the periods in Annex 1, deletes it when a period ends, and follows your Workspace Settings where they set a shorter period. Request Data is not stored after a Request is answered, except as Annex 1 lists.
Batch Files. HIPS keeps each Batch File for thirty (30) days after it is uploaded or produced and then deletes it, except that an input file still used by an open Batch when its thirty (30) days end is deleted when that Batch ends, or sooner at the end of a shorter period that you set for it or when you delete it (Terms Section 6.22). Batch Files are held only in object storage that is not included in HIPS's backups, and deleting a Batch File removes every stored version of it, so no copy of the file remains in the Services after its deletion, except a Training copy made from its content, which the last sentence of this Section governs. A Batch Line that has not finished when the Completion Window of its Batch closes expires and is not run further (Terms Section 6.18). The expiry or deletion of a Batch File does not delete a Training copy made from it, which Section 14.3 and Terms Section 13.11 govern.
Customer Models and Hub Tokens. When you delete a Customer Model or a version, HIPS deletes its copy within seven (7) days, except that while a security incident or a notice under Terms Section 15.10 that concerns the version is open, HIPS keeps the copy for that purpose only, tells you, and deletes it when the matter ends (Terms Section 15.11). HIPS deletes a Hub Token at once when you delete it, and when you delete the Workspace that holds it.
At the end of your Agreement. Before your Agreement ends, and while a deleted Workspace can still be restored (Terms Section 14.2), you may retrieve through the Services the results, output files and other Customer Personal Data that the Services return to you; doing so is your choice of return under Article 28(3)(g) of the GDPR. If HIPS suspends or closes a Workspace or ends your Agreement, for cause or otherwise, HIPS keeps the Batch output and error files and the results of task Requests and jobs that are still within their periods available through a time-limited download link that HIPS sends, on request, to the Owner or to your billing contact, or through a key that HIPS issues for that purpose and that can only retrieve those files, for thirty (30) days after the closure or end, the period for which a deleted Workspace can be restored (Terms Section 14.2), or until their periods end if sooner, unless Applicable Law or a competent authority forbids it, and except a file or result that HIPS has reasonable grounds to believe is illegal content, which HIPS does not make available and keeps only as Terms Section 13.8 allows. When your Agreement ends, HIPS makes the prompt caches of your Workspaces unreadable at once and erases them within the period that Annex 1 states, and deletes the remaining Customer Personal Data as each Workspace is purged and within the periods of Annex 1, unless Union or Member State law requires HIPS to keep it, in which case HIPS keeps it only for that purpose and protects it under this DPA. If the only Owner of one of your Workspaces deletes their Account, HIPS chooses no Owner for you and follows Terms Section 4.7(a): where that Owner is you yourself, as a sole proprietor, the Workspace is deleted with the Account unless you first make another Member its Owner; otherwise HIPS does not delete the Workspace with that Account. If you named a Member as the Workspace's successor Owner beforehand, in the Workspace's settings, HIPS makes that Member its Owner. Otherwise HIPS keeps the Workspace running without an Owner, with its Credits and its Customer Personal Data, for thirty (30) days, which is not a measure under Terms Section 24, so that Terms Sections 6.25 and 24.4 do not apply to it: Requests through the Workspace's API Keys and through the Authorized Tools of its other Members, its deployments and its open Batches keep running against its Credits, its admins and Billing Members keep their roles, only the actions that only an Owner may take are unavailable, and HIPS releases, without charge from then on, any Always-On Capacity that a Billing Member asks it to release; and HIPS tells you so at once on a Durable Medium, at the email addresses of the Workspace's remaining Billing Members and at any billing contact address you gave HIPS, with the date on which the Workspace will be deleted. During that time you may name in writing, with evidence of your authority, a Member or another person as its Owner, who becomes its Owner once they hold an Account and have passed identity verification. If you name none in that time, HIPS deletes the Workspace with the effects that Terms Section 4.7(a) states, and you keep the right this Section gives you: if you ask in writing, with evidence of your authority, while the deleted Workspace can still be restored (Terms Section 14.2), HIPS restores it and makes the person you name its Owner.
Customer Models: deletion as your choice, and return. No part of the Services returns the weights of a Customer Model to anyone, your Workspace included (Terms Section 15.7), except as this Section provides. You hold the source of each Customer Model at the model hub from which you imported it, at the revision HIPS records with each version, so you choose, by accepting this DPA, that HIPS delete its copy, when you delete the model or version and at the end of your Agreement, under Section 12.3, rather than return it. You may change that choice for a Customer Model before its copy is deleted, by telling HIPS in writing that you no longer hold its source: HIPS then makes the files of its copy, as it re-saved them, available once to an Owner of the Workspace that imported it, through a link that expires seven (7) days after it is sent and whose use HIPS records, and deletes its copy afterwards, unless the license the import recorded forbids you to hold that copy, in which case HIPS deletes it and tells you why.
Backups. Deleted Customer Personal Data may remain in HIPS's encrypted backups until they expire (seven (7) days for encrypted database backups, and one (1) day for earlier versions of stored objects), except Batch Files, which are never in backups (Section 12.2). HIPS never restores a backup into service without first removing what was deleted before it, and protects backups under this DPA until they expire.
Confirmation. On your written request, HIPS confirms in writing that it has deleted the Customer Personal Data of a Workspace whose deletion is complete, including its prompt caches, once the period that Annex 1 states for erasing them has passed.
13Information and audits
Information. HIPS makes available to you the information necessary to demonstrate compliance with Article 28 of the GDPR and this DPA: this DPA and its Annexes, the list of sub-processors, the protections HIPS publishes for each pool, and answers to your reasonable written questions about the processing. HIPS holds no security certification and no independent audit report on the date of this DPA. If it obtains one, such as an ISO/IEC 27001 certificate or a SOC 2 report, it makes it, or a summary of it, available to you on request under a duty of confidentiality, and you may rely on it under Section 13.2.
Documentation first. You exercise your audit right first by reviewing the information of Section 13.1. You or an auditor you mandate may carry out an audit, including an inspection, of HIPS only where that information does not reasonably demonstrate HIPS's compliance, where a supervisory authority requires it, or after a Personal Data Breach that concerns your Customer Personal Data.
Conditions of an audit. An audit under Section 13.2:
- (a)is requested in writing, with its scope, at least thirty (30) days in advance, except where a supervisory authority requires a shorter time;
- (b)is carried out during normal business hours at the place audited, without unreasonable disruption of HIPS's operations, and by remote means where they suffice;
- (c)is carried out by you or by an independent auditor who is not a competitor of HIPS and is bound by a duty of confidentiality to HIPS;
- (d)does not give access to the data of other customers, to the identity of Providers except as Section 7.3 provides, to the parameters of HIPS's verification methods, or to information whose disclosure would compromise the security of the Services;
- (e)takes place no more than once in any twelve (12) months, except where a supervisory authority requires it or after a Personal Data Breach that concerns your Customer Personal Data; and
- (f)is at your cost, and you reimburse HIPS's reasonable costs of an inspection, unless the audit shows that HIPS has materially breached this DPA.
Sub-processors. HIPS audits its Sub-processors under its contracts with them. HIPS verifies Providers by remote means, including the methods of Provider Agreement Section 22.2 and the reports of the Provider App, and asks for an inspection of a Device on a Provider's premises only where a supervisory authority, or an audit under Section 13.2 that remote means cannot satisfy, requires it (Provider Agreement Section 8.10). You have no right to audit a Provider or an Approved Provider directly. Where Section 13.2 would allow you to audit HIPS, HIPS audits the Sub-processor concerned on your instruction, to the extent its contract with HIPS and, where they apply, Clause 8.9 of the SCCs allow, and gives you the results subject to Section 13.3(d); Sections 13.3(a), (e) and (f) apply to that audit. HIPS also gives you the relevant results of its own audits on request, subject to their confidentiality.
Findings. HIPS remedies, within a reasonable time, any material non-compliance with this DPA that an audit shows.
14HIPS's own purposes as a controller
Separate from this DPA. HIPS processes some personal data for its own purposes, as a controller and not as your processor. This DPA does not govern that processing. The Privacy Notice describes it, and HIPS is responsible for it as a controller under Applicable Data Protection Law.
HIPS's purposes. HIPS's own purposes are the following, each stated separately:
| Purpose | What HIPS processes | Where it is described |
|---|---|---|
| Accounts, Workspaces and Members | The personal data of your Members, Owners, billing contacts and the people who use your Authorized Tools | Privacy Notice |
| Billing, the ledger and tax | Usage metadata, charges, payments, receipts, invoices and the records accounting and tax law require | Terms Sections 9 to 11 and 13.7; Privacy Notice |
| Fraud and abuse prevention, and the Acceptable Use Policy | Usage metadata, rate signals, reports and the automated classification of the Inputs and Outputs of the models that Acceptable Use Policy Section 11.10 covers; the content of a flagged Request only where Applicable Law requires HIPS to preserve or report it, and otherwise no content of a flagged Request (Terms Section 13.8(d)) | Terms Section 13.8(d); Acceptable Use Policy Section 11; Privacy Notice |
| Reports, notices and evidence | The content and records concerned, and the information needed to identify the Workspace or person concerned, where HIPS reports illegal content, suspected child sexual abuse material or a suspected criminal offense to a competent authority or to an organization that the law recognizes for receiving such reports, decides a notice under Acceptable Use Policy Section 14, gives a payment processor or a card network the evidence of a disputed payment, tells a model hub or a rights holder of a breach that concerns its model or its rights, disclosing no more than shows the breach, or preserves content that it has reasonable grounds to believe is illegal or that it needs to establish, exercise or defend a legal claim, for as long as that purpose needs | Terms Sections 13.8 and 21; Acceptable Use Policy Sections 5.2, 12.9, 12.11 and 14; Privacy Notice |
| Security of the Services | Logs, metrics and error reports, which carry no Request Data, and incident records | Annex 2; Privacy Notice |
| Verifying Cached Input Tokens before HIPS bills them, keeping prompt caches apart by detecting and investigating a fault in keeping Workspaces apart, and answering a binding order of a competent authority | The Prefix Ledger: for each Request to a language model served by a data-center worker whose prompt cache is on, pseudonymized hashes of blocks of the prompt's tokens, keyed for each Workspace, with the worker that served it and the time. It holds no prompt text, but it is pseudonymized data derived from Request Data: HIPS cannot read a prompt from it but could check whether a Workspace sent a known text. As a controller, HIPS uses it only to verify Cached Input Tokens before it bills them (Terms Section 9.10), to detect and investigate a fault in keeping Workspaces apart (Section 11.6), and to answer a binding order of a competent authority, which HIPS handles only as Section 5.3 provides. HIPS's use of the same entries to place Requests and Batch Lines on a worker that holds a prompt cache of their Workspace, and to group Batch Lines that begin with the same content, is processing on your behalf, as your processor, which this DPA governs (Section 3.2 and Annex 1); HIPS uses the Prefix Ledger for no other purpose (Terms Section 13.7). HIPS handles a data subject's request or objection about the Prefix Ledger itself, as a controller (Section 10.1). HIPS derives the Prefix Ledger as a controller, for the purposes of this row, from Request Data that you disclose to it for that purpose; Section 4.5(a) applies to that disclosure as it applies to Training, and you may stop it by turning a Workspace's prompt cache off on data-center workers (the switch "Prompt caching on data-center workers" in the Workspace's settings in the Console), after which HIPS records no Prefix Ledger and charges no Cached Input Token for that Workspace; until that setting is available in the Console, HIPS turns the prompt cache of a Workspace off on data-center workers, with the same effect, without undue delay after an Owner or admin of the Workspace asks it to in writing | Annex 1; Terms Section 13.7; Privacy Notice Section 6.12 |
| Legal obligations | What sanctions, tax and other laws, or an order of a competent authority, require HIPS to keep or disclose | Terms Section 13.8(f); Privacy Notice |
| Training, only where your Plan allows it | Copies of Request Data made under Section 14.3, kept for no longer than twenty-four (24) months after HIPS accepted the Request, stored and used for Training only in the EEA and never on a Device, and used only to develop, fine-tune and evaluate machine learning models that HIPS itself operates and offers through the Services. HIPS does not sell, license, publish or otherwise disclose training copies, datasets made from them, or the weights of a model trained on them, to any third party, except where Applicable Law or a binding order of a court or competent authority requires it, including a request of the AI Office or a market surveillance authority under Regulation (EU) 2024/1689, which HIPS handles as Section 5.3 provides, and except to a successor that takes over the Services under Privacy Notice Section 9.5(f) and is bound by this provision; a service provider that processes them only on HIPS's behalf and under its instructions is not a third party for this purpose. A model that HIPS trains on Request Data runs only on data-center capacity of the Approved Pool located in the EEA or in a country, territory or sector for which an adequacy decision of the European Commission under Article 45 of Regulation (EU) 2016/679 is in force, and never on a Device of the Personal Pool, and is offered only to Buyers whose Country is in the EEA or in a country, territory or sector for which an adequacy decision of the European Commission under Article 45 of Regulation (EU) 2016/679 is in force and covers that Buyer, which, for a Buyer in Japan or the Republic of Korea, HIPS establishes from the Buyer's confirmation in the Console that it is subject to the law the decision names and does not use the model for a purpose the decision excludes (so never a Buyer in the United States that is not certified under the EU-U.S. Data Privacy Framework, or a Buyer in Canada that the Personal Information Protection and Electronic Documents Act does not cover). HIPS treats every model it trains on Request Data as containing personal data, and does not host or offer such a model anywhere else or to any other Buyer. HIPS runs its automated filters over the Request Data of a Request, its Input and its Output, in memory, before it writes any training copy of it, writes no training copy of a Request whose Input or Output the filters identify as revealing special categories of personal data, data on criminal convictions or offenses, or data concerning a child, or that they cannot assess, and masks direct identifiers and secrets in the Input and the Output before it writes the copy (Section 14.3(f)) | Terms Sections 2 and 13; Privacy Notice Sections 6.6 and 6.10 |
| Improving and reporting on the Services | Usage metadata, and statistics derived from it that do not identify you | Terms Section 20.6 |
Training. Training follows the Request-Data Policy of your Workspace's Plan, as the Terms of Service state it: on the Free/PAYG Plan and the lower paid Plan, "request inputs and generated outputs may be used for training"; on the higher paid Plan, Training is off by default, and an Owner or admin may turn it on (Terms Section 13.1). The policy in force when HIPS accepts a Request applies to it, including to every line of a Batch, whose content follows the same rule as a live Request on the same Plan. Where your Plan allows Training:
- (a)you instruct HIPS to make the Request Data of your Workspace available to HIPS for Training, and HIPS makes its Training copies as an independent controller, not as your processor (Terms Section 22.5; Common Clauses Section 17.3(b));
- (b)you warrant that you have a legal basis for that disclosure and have informed the data subjects concerned, including of their right to object under Terms Section 13.2, and, where you are a processor, that your controller has authorized that disclosure (Sections 3.1(d) and 4.5);
- (c)HIPS uses Training copies only for the purpose that Section 14.2 states, developing, fine-tuning and evaluating machine learning models that HIPS itself operates and offers through the Services, and discloses no training copy, dataset made from one, or weights of a model trained on one, to any third party, except where Applicable Law or a binding order of a court or competent authority requires it, including a request of the AI Office or a market surveillance authority under Regulation (EU) 2024/1689, which HIPS handles as Section 5.3 provides, and except to a successor that takes over the Services under Privacy Notice Section 9.5(f) and is bound by this provision, a service provider that processes them only on HIPS's behalf and under its instructions not being a third party for this purpose; a model that HIPS trains on Request Data runs only on data-center capacity of the Approved Pool located in the EEA or in a country, territory or sector for which an adequacy decision of the European Commission under Article 45 of Regulation (EU) 2016/679 is in force, and never on a Device of the Personal Pool, and is offered only to Buyers whose Country is in the EEA or in a country, territory or sector for which an adequacy decision of the European Commission under Article 45 of Regulation (EU) 2016/679 is in force and covers that Buyer, which, for a Buyer in Japan or the Republic of Korea, HIPS establishes from the Buyer's confirmation in the Console that it is subject to the law the decision names and does not use the model for a purpose the decision excludes (so never a Buyer in the United States that is not certified under the EU-U.S. Data Privacy Framework, or a Buyer in Canada that the Personal Information Protection and Electronic Documents Act does not cover); HIPS treats every model it trains on Request Data as containing personal data, and does not host or offer such a model anywhere else or to any other Buyer; HIPS relies for that purpose on its legitimate interests, under Article 6(1)(f) of the GDPR, with the balancing test and the safeguards that the Privacy Notice describes (Privacy Notice Sections 2.4 and 6.10), which HIPS recorded before it wrote the first training copy; HIPS makes its Training copies as an independent controller and not as your processor, and any wider purpose, or any disclosure of Training copies, datasets or trained models to another recipient, would be a change under Terms Section 13.13, with its own assessment and notice, and would apply only to Request Data HIPS accepts after it takes effect;
- (d)HIPS honors the objection of any natural person to the use for Training of Request Data that concerns them, and your request to exclude your Workspace's contributions, as Terms Sections 13.2 and 13.11 provide. Where a natural person's objection concerns Request Data in a dataset that HIPS has already used, HIPS, within three (3) months after it records the objection, retrains without it, or stops offering, every model trained on that dataset; until it has done so, it applies to that model, from no later than one (1) month after it records the objection, measures that prevent it from outputting the personal data concerned; and it tells the person which it did. The same applies where HIPS learns that a training copy already used held data that item (f) excludes;
- (e)HIPS never uses the weights of a Customer Model to train other models, on any Plan (Terms Section 13.6); and
- (f)HIPS runs its automated filters over the Request Data of a Request, its Input and its Output, in memory, before it writes any training copy of it. It writes no training copy of a Request whose Input or Output the filters identify as revealing racial or ethnic origin, political opinions, religious or philosophical beliefs, trade union membership, genetic or biometric data, health, sex life or sexual orientation, or criminal convictions or offenses, or as concerning a child, or that the filters cannot assess, and it masks names, contact details, identification numbers, payment card data and authentication secrets in the Input and the Output before it writes the copy. The filters keep nothing of what they screen out, and HIPS never relies on its legitimate interests to train on a special category of personal data, on personal data relating to criminal convictions or offenses, or on personal data concerning a child (Terms Section 13.2; Privacy Notice Section 6.6). The screening and the masking are part of the processing HIPS carries out on your behalf, on your instruction (Section 3.2 and Annex 1), before any Request Data is made available to HIPS for Training; HIPS tests the filters as Privacy Notice Section 6.6 describes. The filters do not change your obligations under Section 4.5(c).
No sale and no advertising. HIPS does not sell Customer Personal Data, does not use it for advertising, and does not combine it with other data to profile the people it concerns.
15Liability, term and general terms
Liability. Each party's liability arising out of or in connection with this DPA is subject to Common Clauses Sections 4 to 6, including the limits that Common Clauses Section 5 sets for your population, as part of your Agreement. Liability under this DPA and under the rest of your Agreement counts once against those limits. Nothing in this DPA limits either party's liability to a data subject under Article 82 of the GDPR, or any liability that Common Clauses Section 5.1 excludes from the limits.
Recourse between the parties. Where one party has paid compensation to a data subject for damage for which the other party is responsible under Article 82 of the GDPR, it may claim back from the other party the part of the compensation corresponding to the other party's share of responsibility, as Article 82(5) of the GDPR provides.
Fines. Each party bears the administrative fines that a supervisory authority imposes on it. A party may recover a fine from the other only where Applicable Law allows a fine to be indemnified (Common Clauses Section 2.1, "Losses").
Term. This DPA applies for as long as HIPS processes Customer Personal Data, and survives the end of your Agreement until HIPS has deleted it under Section 12.
Changes. HIPS changes this DPA as Common Clauses Section 9 provides. HIPS may also change it with effect from the date the law requires, where Applicable Data Protection Law, a decision of a supervisory authority or court, or a new version of the SCCs or the UK Addendum requires it. No change reduces the protection of Customer Personal Data under this DPA, except as the law requires.
Disputes. A Dispute about this DPA is resolved on the Track that applies to you under Common Clauses Sections 12 to 15. A dispute arising from the SCCs where Section 9.8 makes you a party to them is resolved as their Clauses 17 and 18 provide.
United States privacy laws. Where the California Consumer Privacy Act or a comparable state law applies to your processing, HIPS processes Customer Personal Data as your service provider or processor, for the specific business purposes that Section 3.2 lists, which are the only purposes for which you disclose it to HIPS; HIPS does not sell or share it, does not retain, use or disclose it for any other purpose, any other commercial purpose or outside the direct business relationship with you, and does not combine it with personal information from another source, except as those laws and Cal. Code Regs. tit. 11, section 7050(a), permit; HIPS complies with those laws and gives Customer Personal Data the same level of privacy protection they require of you; you may take reasonable and appropriate steps, including the audits of Section 13, to ensure that HIPS uses it consistently with your obligations, and, on notice, to stop and remediate any unauthorized use; HIPS helps you answer consumers' requests as Section 10 provides; and HIPS tells you if it determines that it can no longer meet those laws. HIPS uses the Prefix Ledger, which it derives from Customer Personal Data, only to verify and bill the Cached Input Tokens of your own Requests, to detect and investigate a fault in keeping Workspaces apart and to answer a binding order of a competent authority, which are uses that section 7050(a)(1), (4) and (5) permit, so that deriving it does not take HIPS outside its role as your service provider. On a Plan whose Request-Data Policy allows Training, HIPS receives Request Data for Training as a third party and not as your service provider: HIPS uses it only for Training as Terms Section 2.2 defines it; complies with those laws for it and gives it the same level of privacy protection; honors a consumer's opt-out of sale or sharing that you forward to it by excluding that consumer's data under Terms Section 13.11; lets you take reasonable and appropriate steps to ensure, and on notice to stop and remediate, its use; and tells you if it can no longer meet those laws. You are responsible for the notice and opt-out those laws require for that disclosure, and you shall not send from such a Workspace the personal information of a consumer who has opted out of its sale or sharing.
Severability. Common Clauses Section 16 applies. Each Section, clause and lettered item of this DPA is a separate provision.
Contact. You reach HIPS about this DPA as follows.
- Questions about this DPA, data subject requests and audit requests
- hello@hips.com
- Security issues
- security@hips.com, also published in /.well-known/security.txt on hips.com
- Legal notices
- the address in Common Clauses Section 10.3
- The current list of sub-processors
- the Legal Information Page
16Annex 1: Particulars of the processing
The particulars. The processing that HIPS carries out on your behalf is as the table below describes.
| Item | Description |
|---|---|
| Controller | The Customer, or, where the Customer is a processor, its controller (Section 3.1) |
| Processor | HIPS, which engages the Operating Company and the other Sub-processors of Annex 3 |
| Subject matter | Providing the Services to the Customer's Workspaces: inference on catalog models and Customer Models, Batches, asynchronous jobs, uploads, the import and storage of Customer Models, and Always-On Capacity |
| Duration | For the term of the Customer's Agreement, and afterwards until deletion under Section 12 |
| Nature | Receipt at the Amazon CloudFront edge location in front of ai.hips.com and at HIPS's regional processing locations, transmission, routing and forwarding between those locations (Section 9.1), inference in the memory of a data-center worker or a Device, prompt caching in the memory of a data-center worker, never on disk, the placement of Requests and Batch Lines on a worker that holds a prompt cache of their Workspace and the grouping of Batch Lines that begin with the same content, using hashes of blocks of the tokens of their Inputs and the entries of the Prefix Ledger for the same Workspace (Section 3.2), storage of Batch Files, uploads, the request bodies of asynchronous jobs, results, the answers kept for an idempotency key and Customer Models, verification of Providers' work, the screening and masking of Request Data in memory before any of it is made available to HIPS for Training (Section 14.3(f)), the import, checking, re-saving and signing of Customer Models, return to the Customer and deletion |
| Purpose | Providing the Services to the Customer as its Agreement describes them, on its documented instructions |
| Categories of data subjects | The persons whom the Customer's Request Data, Batch Files and Customer Models concern, as the Customer decides, such as its end users, customers, employees and the persons named in its content; and the holder of a Hub Token's hub account |
| Categories of personal data | Any personal data that the Customer includes in Inputs, uploads, Batch Files and the metadata and file names it attaches to them, that Outputs contain, that is embedded in the weights of a Customer Model, or that a Hub Token identifies |
| Special categories | None, unless HIPS agrees otherwise in a signed document (Terms Section 13.12); the Customer does not send special categories of personal data in Requests that may be served from the Personal Pool or from a Workspace whose policy allows Training |
| Frequency | Continuous, as the Customer sends Requests and Batches |
| Sub-processors | Annex 3 and Providers as a category (Section 7) |
| Locations | Ireland, the United States and Japan; Amazon CloudFront edge locations in any country, for Requests to ai.hips.com; and Devices in the Device Countries (Section 7.3); as Section 9.1, Section 16.2 and Annex 3 state |
Retention. HIPS keeps each kind of Customer Personal Data as the table below states.
| Customer Personal Data | Where it is held | How long |
|---|---|---|
| Inputs and Outputs of a Request | In memory at the Amazon CloudFront edge location that receives a Request to ai.hips.com, at the regional processing location that receives the Request, at any location to which it is forwarded (Section 9.1), and on the data-center worker or Device that serves it | For the processing of the Request; not stored afterwards, except in the rows below |
| Prompt caches | In memory on the data-center worker that served the Workspace's earlier Request, in that worker's region; never on disk; never on a Device at launch | No lifetime promised for your benefit, and evicted as the engine needs its memory; HIPS makes every prompt cache of a Workspace unreadable no later than twenty-four (24) hours after it was made, by changing the value that keeps the Workspace's caches apart, and at once when the Workspace is deleted, when your Agreement ends or when you ask; no Request can then read the old cache, and the engine discards it as it needs the memory, and in any case HIPS clears the prompt cache of that worker in full no later than twenty-four (24) hours after it became unreadable (Terms Section 9.9(g)); never shared with another Workspace |
| Batch Files | HIPS object storage in Ireland (eu-west-1) or, for a Batch that requires a region, in that region's storage (Section 9.1), encrypted | Thirty (30) days, or until the end of an open Batch that still uses an input file, or less as Section 12.2 provides; never in backups |
| Uploaded task inputs | HIPS storage in Ireland (eu-west-1) or, for a Request that requires a region, in that region's storage, encrypted | Twenty-four (24) hours after upload, or less where you delete them |
| Results of task Requests and jobs | HIPS storage in Ireland (eu-west-1) or, for a Request that requires a region, in that region's storage, encrypted | Seven (7) days after the task or job completes, or less where you delete them |
| Request bodies of asynchronous jobs | HIPS storage in Ireland (eu-west-1) or, for a Request that requires a region, in that region's storage, encrypted | From acceptance until the job ends, then deleted |
| Answers kept for an idempotency key | HIPS storage in Ireland (eu-west-1) or, for a Request that requires a region, in that region's storage, encrypted | Only a completed answer, for twenty-four (24) hours after it is produced, so that a retry with the same key returns it without running or charging the Request again, then deleted |
| Batch metadata and file names | HIPS's database in Ireland (eu-west-1), encrypted, and its encrypted backups | For the period of the request log, thirteen (13) months from the Request, then deleted; backups as Section 12.6 provides |
| Verification samples | HIPS storage in the Workspace's storage location, encrypted, for the comparison, and the reference device that HIPS itself operates, or the worker of the Approved Pool, that runs it again, within the Request's region requirement | Deleted when the comparison completes, and in any case within seventy-two (72) hours of the Request; no content of a Workspace whose policy is training off is sampled |
| Content held for debugging at the Customer's written request | HIPS storage in Ireland (eu-west-1) or, for a Request that requires a region, in that region's storage (Section 9.1), encrypted | The period the Customer names in its request, then deleted |
| Customer Model copies | HIPS storage in the region of the Workspace's storage location, encrypted, and a copy in the region of a deployment that requires another region | Until the Customer deletes the model or version, then as Section 12.3 provides |
| Hub Tokens | HIPS's database in Ireland (eu-west-1), under envelope encryption | Until the Customer deletes them or the Workspace |
| Backups of the above | In the region of what they back up, encrypted: Ireland (eu-west-1) for the database and the storage there, and each region's storage keeps its own object versions in that region, never replicated to another | Until the backup expires (Section 12.6); Batch Files are never in backups |
| The Prefix Ledger, which is HIPS Controller Data (Section 14.2) and is listed here for your information | The operational store of the regional processing location at which the worker that served the Request is homed, in that worker's region, which holds no prompt text | HIPS records the Prefix Ledger only for Requests served by data-center workers whose prompt cache is on, and never for a Workspace whose prompt cache is turned off under Terms Section 9.9(a). It deletes each record no later than the maximum lifetime of a prompt cache in the row above after the Request it records, and sooner only once the engine of the worker it names has restarted or once the caches of the Workspace have been made unreadable, never while the cache the record stands for can still be read, so that no Cached Input Token is charged at the input rate because its record was deleted first; except that records that concern an isolation fault under investigation (Section 11.6) are kept apart from the rest, and only until the investigation ends (Terms Section 14.1; Privacy Notice Section 6.12(d)) |
17Annex 2: Technical and organizational measures
The measures. HIPS applies the following measures to Customer Personal Data, subject to Section 6.4.
| Area | Measures |
|---|---|
| Hosts and edges | The API is served at ai.hips.com, which reaches the nearest of HIPS's regional processing locations, and at the regional addresses eu.ai.hips.com, us.ai.hips.com and jp.ai.hips.com, each of which reaches only its region's location; the Console at console.hips.com; and the device link at providers.hips.com, for the enrollment of Devices and the renewal of their certificates, and at the hosts under providers.hips.com of the regional processing locations, to which Devices connect for their work; each over TLS. On ai.hips.com, TLS ends first at the Amazon CloudFront edge location nearest the client, in any country where CloudFront operates, which holds the Request in memory only, caches no response of the API, records no Request Data in its logs, and passes the Request over TLS to the regional processing location it serves, which decrypts it again; on a regional address, and on the device link, no edge location is in between and TLS ends only inside the region, for the device link at the coordinator of the regional processing location the Device connects to; HIPS treats the decryption at an edge location, and at an entry outside a Request's region, as a transfer to that country with the safeguards of Section 9.7. The paths on which Stripe, Bynn and Amazon SES notify HIPS of events, and the device sign-in, are answered in Ireland on eu.ai.hips.com, to which ai.hips.com relays them. Buyers and Devices never connect to each other: every Request reaches a Device through HIPS's regional processing locations, and no Device learns a Buyer's network address, nor a Buyer a Device's. The website is at hips.com, and www.hips.com answers every request with a permanent redirect to hips.com before any cookie is set, except a request for the script address of a service worker that an earlier website used, which it answers with a script that unregisters itself and a Clear-Site-Data header limited to storage and cache. The Console's session cookie is host-only on console.hips.com, no cookie of the Services is set for the wider hips.com domain, and each host asks for consent to its own cookies. Every cookie HIPS sets carries the __Host- prefix, which a browser accepts only over HTTPS, for one host and with no Domain attribute, so that no other host under hips.com can set a cookie under one of its names. Browsers may also send HIPS's hosts cookies that another host under hips.com set for the whole hips.com domain, or that an earlier website at hips.com or www.hips.com set; HIPS's edge removes from each request every cookie whose name does not carry the __Host- prefix or is not listed in Privacy Notice Section 13.3 for the host that receives it, before the request reaches HIPS's applications; the edge records no cookie name or value in its logs; and HIPS does not store, use or pass on any cookie it removes |
| Encryption in transit | TLS on every connection: from your clients to the API and the Console; from the gateway to data-center workers over gRPC with TLS on HIPS's private certificate authority and a worker key per pool, never in plaintext; between HIPS's own services, within and between its regional processing locations, over mutual TLS; from each Device to HIPS over mutual TLS 1.3 with a short-lived Device certificate whose key stays in the Device's keystore |
| Encryption at rest | Customer Model copies, Batch Files, uploads, the request bodies and results of jobs and the answers kept for an idempotency key in object storage encrypted with keys of the cloud key service; the database, the cache and the backups encrypted at rest; Hub Tokens under envelope encryption with a dedicated key that HIPS's platform role cannot use to decrypt them |
| Content not stored by default | A request log holds operational metadata, not stored prompts and outputs. Request and response bodies on error, and tokens themselves, are not stored. Logs, metrics and error reports carry no Request Data and are kept in HIPS's own observability stack |
| Access by HIPS personnel | Metadata first. Access to Request Data or Customer Model weights only for a closed list of purposes (an abuse review, the Customer's written debugging request, a security incident, a legal obligation), with the approval of a second administrator, time-boxed, and recorded in an audit log; a short, reviewed list of administrators; infrastructure access through roles with session logging. Verification comparisons run without human access |
| Isolation of the Services | The Services run in their own namespaces, on their own nodes, with their own database, cache, keys, roles and logs, separated by network policies from every other workload in the same cloud account, including those of HIPS Payments, a business that HIPS does not carry on and whose systems and personnel have no access to Customer Personal Data; anyone who administers that shared infrastructure for HIPS does so only on HIPS's instructions and under a duty of confidentiality; HIPS itself holds that cloud account, under the data processing terms of Amazon Web Services (Annex 3) |
| Prompt caches | Automatic; isolated per Workspace by a value that the gateway derives for each Workspace and model version and sends to the engine, which the Customer cannot set; narrowed further by the Customer's prompt cache key; held in the memory of data-center workers, never on disk; every cache of a Workspace made unreadable within the longest life of Annex 1 by changing that value, and at once when the Workspace is deleted, the Agreement ends or the Customer asks, and the prompt cache of the worker cleared in full within the further period of Annex 1 after it became unreadable; a reported cache hit is billed only where the Prefix Ledger, which keeps pseudonymized hashes of blocks of the tokens of prompts for each Workspace and never prompt text, shows that it belongs to the same Workspace, and a count that the Prefix Ledger cannot support is an isolation fault, handled as a Personal Data Breach under Section 11 until HIPS establishes that no Customer Personal Data reached another Workspace, and notified as Section 11.6 provides. At launch, Devices run with every cross-request cache off |
| Batches | Batch Files are a stored class of their own, held only in object storage that is not backed up, deleted with every stored version, and kept no longer than Section 12.2 allows; lines run in the Approved Pool or the Personal Pool under the same pool, region and fallback requirements as live Requests |
| Customer Models | Weight files only; no code of the Customer runs anywhere. Pickle-based files, repository code, custom operators and external data outside the model are refused at import. Each import runs as an isolated job on HIPS infrastructure, each step in a fresh sandbox with its own network policy; the files are re-saved, signed with a HIPS key held in the cloud key service, and stored once under an opaque key that names no customer; workers verify the signature before loading; no route returns the weights |
| Hub Tokens | Read-only tokens only; shown by their last four characters, never returned, never logged; opened only by the import runner for a credential check or an import's fetch step, every opening matched against the cluster's audit log; never sent to a data-center worker or a Device |
| The Approved Pool | HIPS's worker images behind HIPS's worker contract; engines run with remote code off and no custom operator; the account credential of the Approved Provider held only by the platform; data centers of RunPod's Secure Cloud, never its Community Cloud, in the EEA, the United States and Japan, each reached from the regional processing location of its region and listed by identifier and country on the Legal Information Page; published protections per Approved Provider on the same page |
| The Personal Pool | Identity verification of every Provider; the Provider App's Sandbox (a separate process with no network access and no file access outside its model cache, which the app can stop at any time); Request Data in memory only, never written to disk by the Provider App or its Engines, released and overwritten after each Attempt, the operating system of a Device being able to move memory to its swap or page file, or to a hibernation file when its owner puts it to sleep, which the Provider App limits where the operating system allows it, for example by locking memory, and which the Device's owner controls; one Assignment at a time; no inbound port; signed software and engines from HIPS's own mirror, verified before they run; every Engine cache and learning feature off at launch; the country of each Device taken from the network address of each of its connections, from a database HIPS holds, so that no address is sent elsewhere; Requests only on Devices located in a Device Country, none on a Device located in a Restricted Jurisdiction, and none of yours on a Device that connects through an anonymizing network or whose location HIPS cannot confirm; and, for a Request that requires a region, location checks: the country of each connection's address, the address on no known anonymizing network, and the round trips that HIPS's regional processing locations measure to the Device, never the Device's own report; each Device connected to one regional processing location, the nearest it measures, which HIPS may change; verification of results (Provider Agreement Section 22.2) |
| Region | The platform and the Customer Personal Data stored for the Agreement in Ireland (eu-west-1), except content stored for a Request that requires a region; regional processing locations in Ireland (eu-west-1), the United States (us-east-2) and Japan (ap-northeast-1); three regions, "eu" (the EEA), "us" and "jp", a requirement covering the processing of a Request, its retries and fallback and the content stored for it, never HIPS Controller Data; the Approved Pool in data centers in the EEA, the United States and Japan; pool, region and fallback requirements enforced by the scheduler on every attempt, retry and fallback, and at the entry, where a Request that requires another region is forwarded to it in memory only on ai.hips.com, and refused on a regional address (Section 9.1) |
| Resilience and backups | Encrypted backups kept in the same region; deleted data never restored into service |
| Incidents and vulnerabilities | A security contact and a security.txt file; incidents recorded and tracked; fixes for confirmed vulnerabilities in the gateway, the coordinator and the Provider App released ahead of other work; dependency advisories checked in continuous integration |
| Deletion | Object deletion removes every stored version of an object; a lifecycle rule expires noncurrent versions; scheduled deletion enforces the periods of Annex 1 |
18Annex 3: Sub-processors
The list. HIPS engages the following sub-processors for Customer Personal Data. HIPS publishes the current list on the Legal Information Page and changes it as Section 7 provides.
| Sub-processor | What it does for HIPS | Customer Personal Data | Location | Transfer safeguard |
|---|---|---|---|---|
| Hyperscale Inference Processing Systems OÜ (Estonia), the Operating Company, HIPS's Affiliate | Operates the Services for HIPS: the gateways, the scheduler, the Console, the Provider App's services, support, security and trust and safety operations; engages the sub-processors below for HIPS | All Customer Personal Data that HIPS processes | Estonia (operations and administration); the data itself is stored and processed where the rows below state | None needed (EEA) |
| Amazon Web Services: Amazon Web Services EMEA SARL (Luxembourg), the contracting party, and Amazon Web Services, Inc. (United States), the parties to the data processing terms of Amazon Web Services | Hosting of the Services, the database, the cache, object storage, keys and secrets; email delivery; HIPS's regional processing locations; the content delivery network in front of ai.hips.com, the Console and the website (Amazon CloudFront) | All Customer Personal Data that HIPS stores; Request Data in transit and in memory at each regional processing location; Request Data in memory at the Amazon CloudFront edge location that a Request to ai.hips.com, or a playground request through console.hips.com, reaches; content stored for a Request that requires a region, in that region | Ireland (eu-west-1), for the Services' storage and the regional processing location there; the United States (us-east-2, Ohio) and Japan (ap-northeast-1, Tokyo), for HIPS's regional processing locations there; Amazon CloudFront's edge locations in any country where CloudFront operates, which end TLS for ai.hips.com and the Console, including the playground, and which HIPS cannot restrict to the EEA | In Ireland, none needed; in the United States, the EU-U.S. Data Privacy Framework, under which Amazon Web Services, Inc. is certified, and the SCCs of the data processing terms of Amazon Web Services should it cease to cover the transfer; in Japan, the adequacy decision for Japan (Implementing Decision (EU) 2019/419); at a CloudFront edge location in another country without an adequacy decision, the SCCs of the data processing terms of Amazon Web Services |
| RunPod: Runpod Inc. (United States), the first Approved Provider | GPU capacity of the Approved Pool, from its Secure Cloud only | Request Data, prompt caches, verification samples and Customer Models while a Request, a Batch Line or a deployment runs | Data centers of RunPod's Secure Cloud in the EEA, the United States and Japan, listed by identifier and country on the Legal Information Page; a data center in another country is added only with the notice of Section 7.5 | In the EEA, none needed; in the United States and Japan, the SCCs (Module Three) of RunPod's data processing agreement, with a transfer impact assessment, RunPod not being certified under the EU-U.S. Data Privacy Framework, and in Japan also the adequacy decision for Japan where it covers RunPod's processing there |
| Providers, as a category (Section 7.3) | GPU Time of the Personal Pool | Request Data of Requests and Batch Lines to catalog models while they run; no Customer Model at launch | The Device Countries of Section 7.3, as HIPS takes each Device's country from each connection, and never a Restricted Jurisdiction; each Provider's own Country one of the Provider Countries the Console lists: states of the EEA, the United Kingdom, Switzerland, Canada, the United States, Japan, Singapore, the Republic of Korea, Taiwan and Australia | Sections 9.3 to 9.6: none needed in the EEA; otherwise the SCCs, which bind every Provider whose Device is outside the EEA, the United Kingdom and Switzerland, together with any adequacy decision that covers it, after HIPS's assessment of the country under Clause 14; for a Provider established in the EEA whose Device is outside it, Provider Agreement Section 8 with the duties of Clauses 14 and 15 |
Recipients that are not sub-processors. HIPS's other service providers named in the Privacy Notice, such as its payment processor (Stripe), its identity verification provider (Bynn) and its error-reporting service (Rollbar), process HIPS Controller Data, as HIPS's processors or, for the purposes Stripe decides itself, as an independent controller, and receive no Customer Personal Data. The model hubs from which you import Customer Models are your own sources: you hold your account and your repositories there under the hub's own terms; HIPS reaches a hub only on your instruction, to fetch the files you name, with your Hub Token where one is needed, and sends it no Customer Personal Data beyond the request for those files and that Hub Token. HIPS does not engage a hub to process Customer Personal Data on its behalf, so a hub is not a sub-processor.
19Annex 4: Country terms
Scope. This Annex applies to Customer Personal Data to which the law of Japan, the Republic of Korea, Singapore, Taiwan or Australia applies, in addition to the rest of this DPA, which it does not reduce.
All five. HIPS processes Customer Personal Data only for the purpose and within the scope of Annex 1; implements the measures of Annex 2; engages Sub-processors only as Section 7 allows, which is your consent to that engagement; notifies you of a Personal Data Breach as Section 11 provides, with the information you need for the report and notices your law requires; deletes or returns Customer Personal Data as Section 12 provides; gives you the information and audits of Section 13, which are your means to supervise HIPS's handling; and is liable to you for a breach of these obligations as Section 15 provides.
Japan. This DPA is your contract of entrustment with HIPS under Article 25 of the Act on the Protection of Personal Information. HIPS is established in the European Union, which the Personal Information Protection Commission has designated under Article 28 of that Act. If you rely instead on a recipient that maintains a system meeting the Commission's standards, HIPS maintains the measures of this DPA as that system, tells you without delay of any obstacle to them, including a law of a country where it processes Customer Personal Data, and gives you once a year, and on request, the information on its measures and on the countries where it processes Customer Personal Data that you need for Article 28(3) of that Act.
The Republic of Korea. This DPA is the document of entrustment of Article 26(1) of the Personal Information Protection Act and states the matters of Article 28(1) of its Enforcement Decree: the purpose and scope of the entrusted work (Annex 1), the restrictions on re-entrustment (Section 7), the safety measures including access restriction (Annex 2), the supervision of the management status of Customer Personal Data (Section 13), and liability for damages (Section 15). HIPS processes Customer Personal Data outside the Republic of Korea in the countries of Sections 7.3 and 9.1, and gives you the items of Article 28-8(2) of that Act that you must disclose or notify; the protective measures of Article 29-10 of the Enforcement Decree are those of Annex 2, Section 10 (complaints and requests) and Section 15.6 (disputes).
Singapore. HIPS processes Customer Personal Data as your data intermediary and protects it to a standard comparable to that of the Personal Data Protection Act 2012. Customer Personal Data may be transferred to and processed in the countries named in Section 9.1, in Annex 3 and in the Device Countries of Section 7.3 as the Legal Information Page lists them, and in no other.
Taiwan. HIPS handles Customer Personal Data within the scope, categories, purpose and period of Annex 1, applies the measures of Annex 2, engages further commissioned parties only as Section 7 allows, notifies you of a breach and the remedial measures as Section 11 provides, follows your instructions on any matter Section 4 reserves to you, and returns or deletes Customer Personal Data at the end as Section 12 provides; HIPS stops a transfer to a country that the competent authority restricts under Article 21 of the Personal Data Protection Act.
Australia. HIPS handles Customer Personal Data in accordance with the Australian Privacy Principles, as if bound by them, except Principle 1, and only on your instructions, so that you keep effective control of it; it binds its Sub-processors and Providers to the same handling (Sections 7.2 and 8.1).