Skip to content
HIPS
  • Earn with your GPU
  • Pricing
  • Docs
Sign inJoin early access
  1. Legal
  2. /
  3. Terms of Service

Terms of Service.

The agreement between HIPS and everyone who buys inference from HIPS, whether a business or a consumer.

SupersededSuperseded on 2026-11-16 by version 1.1. The version in force

About this document
Entity
HIPS Payment Group Limited
Status
Superseded on 2026-11-16 by version 1.1
Applies to
Buyers (businesses and consumers), Workspace Members, and the people and tools that use a Workspace's credentials
Acceptance
Accepted at Account creation, and by every Member who joins a Workspace, together with the version of the Common Clauses these Terms incorporate; HIPS records both versions with the acceptance and the separate confirmation of Section 1.5.
Incorporates
Common Clauses (version 1.0), Acceptable Use Policy, Data Processing Agreement (Business Users, including US Users who are Business Users)
Version
1.0
Last updated
2026-10-27
In effect from
2026-10-27
Length
30 sections18 defined terms
Questions
legal@hips.comSection 30
Contents0% read
  1. The commitments in brief
  2. 1About these Terms
  3. 2Definitions
  4. 3Who may buy
  5. 4Identity verification and Accounts
  6. 5Sign-in, API Keys and your tools
  7. 6The Services
  8. 7Plans
  9. 8Credits
  10. 9Prices and charges
  11. 10Payment
  12. 11Taxes
  13. 12Refunds and payment disputes
  14. 13Request data
  15. 14Retention and deletion
  16. 15Customer Models
  17. 16Outputs
  18. 17Where computation happens
  19. 18Availability and support
  20. 19Acceptable use
  21. 20Intellectual property and licenses
  22. 21Confidentiality
  23. 22Privacy and data protection
  24. 23Third-party services and model licenses
  25. 24Suspension and closure
  26. 25Liability, disclaimers and indemnities
  27. 26Business Users outside the United States
  28. 27Consumers
  29. 28United States
  30. 29Changes, notices and general terms
  31. 30Contact
Contents30 sections
  1. The commitments in brief
  2. 1About these Terms
  3. 2Definitions
  4. 3Who may buy
  5. 4Identity verification and Accounts
  6. 5Sign-in, API Keys and your tools
  7. 6The Services
  8. 7Plans
  9. 8Credits
  10. 9Prices and charges
  11. 10Payment
  12. 11Taxes
  13. 12Refunds and payment disputes
  14. 13Request data
  15. 14Retention and deletion
  16. 15Customer Models
  17. 16Outputs
  18. 17Where computation happens
  19. 18Availability and support
  20. 19Acceptable use
  21. 20Intellectual property and licenses
  22. 21Confidentiality
  23. 22Privacy and data protection
  24. 23Third-party services and model licenses
  25. 24Suspension and closure
  26. 25Liability, disclaimers and indemnities
  27. 26Business Users outside the United States
  28. 27Consumers
  29. 28United States
  30. 29Changes, notices and general terms
  31. 30Contact

These Terms of Service (the Terms) are an agreement between HIPS Payment Group Limited, a company incorporated in Ireland (HIPS, we, us or our), and the person who accepts them or the organization on whose behalf that person accepts them (you or your). HIPS is building a centrally managed AI inference marketplace on a distributed GPU network. It connects people buying inference with independently supplied GPU time. HIPS sells that inference to you in its own name, and these Terms govern how you buy and use it. They incorporate the HIPS Common Clauses, which every HIPS agreement shares. Hyperscale Inference Processing Systems OÜ, of Estonia, operates the Services for HIPS and is not a party to these Terms (Common Clauses Section 3.1). Capitalized terms are defined in Section 2.

Important: please read before you accept

How a dispute with HIPS is resolved depends on who you are. If you are a business outside the United States, Irish law governs, disputes go to confidential arbitration in Tallinn, Estonia, and you may bring claims only individually (Section 26). If you are in the United States, disputes go to binding individual arbitration, you and HIPS waive class actions and jury trials, and you may opt out of arbitration within thirty (30) days (Section 28). If you are a consumer outside the United States, you keep the courts of your home country and the mandatory protection of the law where you live (Section 27). Identity verification always includes a face check, which you complete, as you choose and without giving a reason, either by the automated face check, which needs your explicit consent, or by a face check by a person on a video call that is never recorded; if you refuse both, you cannot verify, and so you receive no Credits, cannot buy, cannot run Requests for a Workspace you own or as a Member, and cannot earn (Sections 4.8 and 4.9). On the Free/PAYG Plan and the lower paid Plan, Inputs and Outputs may be used for Training: a business cannot turn this off on those Plans, a consumer may object at any time with one switch and keep the Plan (in the United States, Training on a consumer's Request Data is off unless the consumer turns it on), and any natural person may object to the use for Training of Request Data that concerns them (Section 13.2). If you turn on machine payments, an agent that uses your Workspace's API Key can pay HIPS by card for the Workspace within the limits you set, and you are responsible for those payments as your own (Section 10.11). The owner of a Device in the Personal Pool, and the operator of hardware in the Approved Pool, can in principle access the model and the Request Data while a Request runs, and the operator also while a prompt cache holds it (Sections 9.9 and 17). A Batch has no promised completion time, and its lines that have not finished when its Completion Window closes expire without charge (Sections 6.17 and 6.18). Purchased Credits expire twelve (12) months after purchase, and Included Credits at the end of the billing period for which they are granted (Section 8.5). Prices change: the price of a Request is the one HIPS publishes when it accepts the Request (Section 9.2). A disputed card payment blocks the Credits it bought, and HIPS may freeze the whole Workspace where it suspects fraud or, in the United States, on any dispute (Section 12.4); HIPS may suspend or close a Workspace at once on the grounds in Section 24.2. HIPS's liability is limited within the law of your group (Section 25). HIPS asks you to confirm these points separately before you accept (Section 1.5).

The commitments in brief

  • Nothing is live yet. The Services are prelaunch, and Accounts are created by invitation only.
  • HIPS is your seller. HIPS Payment Group Limited, an Irish company that trades as HIPS, sells you inference in its own name, and you pay HIPS and nobody else. HIPS buys GPU time for its own account and never acts as anyone's agent. Its Estonian affiliate, Hyperscale Inference Processing Systems OÜ, operates the Services for HIPS and is not a party to these Terms.
  • Every person verifies, face check included. Identity verification always includes a face check: the automated face check, done only with your explicit consent, or a face check by a person on a video call that is never recorded, as you choose. An unverified person receives no Credits, cannot buy, cannot use a Workspace of their own or as a Member, and cannot earn.
  • Your Plan sets the request-data policy. On Free/PAYG and the lower paid plan, request inputs and generated outputs may be used for training. If you are a consumer, HIPS tells you so, and of your right to object, separately from any other information and before your first request, and you can object at any time with one switch and keep your plan; if you are a consumer in the United States, training is off unless you turn it on. On the higher paid plan, request-data training is off by default. The policy is shown before every request and never changes for a request already accepted.
  • Plans and prices. Free/PAYG has no plan fee; the paid plans are monthly subscriptions whose fee and included credits the price list states. Prices move: a request is charged at the price published when HIPS accepts it, and the price history HIPS publishes is information only.
  • Where requests run. HIPS keeps account data in Ireland and processes requests in Ireland, the United States and Japan. A request without a region requirement may run in any of them; on ai.hips.com the connection first ends at the content delivery network's point of presence nearest you, while a regional address keeps the connection itself inside your region.
  • Batches cost half, with no completion time. A Batch costs fifty percent (50%) less than on-demand, at rates fixed when HIPS accepts it. HIPS promises no completion time: lines unfinished when your window closes expire and are not charged, and every finished line is delivered. Credits held for a Batch do not expire while it holds them.
  • Prompt caching is automatic. Writing a cache is free, and HIPS charges the cached-input rate only for cache reads it can verify. Caches are kept apart for each Workspace, held only in memory, and made unreadable no later than twenty-four (24) hours after they are made, and at once when you ask.
  • Your model weights are not training data. Customer-owned model weights will never be used to train other models on any plan, and no part of the Services returns them to anyone.
  • Customer models run no code. A customer model is weight files imported from a model hub and run by HIPS's own engines, under your warranty that you may run it commercially.
  • Credits are prepaid use, not money. Purchased Credits expire twelve (12) months after purchase, and the included credits of a paid plan at the end of their billing period. If HIPS ends these Terms without cause, it refunds your unused Purchased Credits. A Consumer may ask for a refund of Purchased Credits that expired or remained unused (Section 27.12).
  • Card payments, no crypto. HIPS takes payments by card, including the card payments that an agent using your Workspace's API Key makes once you turn machine payments on, accepts no crypto-asset payment, and never offers MTO in any form. HIPS never encourages or advises anyone to acquire, hold, sell or trade MTO or any other crypto-asset, which carry extreme risk, including the total loss of their value (Common Clauses Section 3.12).
  • No uptime commitment. HIPS makes no availability, latency or support-response commitment unless it agrees one in a signed document.
  • Closure with reasons. HIPS closes a Workspace at once only for a stated cause, with a short statement of reasons; otherwise it gives thirty (30) days' notice and refunds unused Purchased Credits. In the United States, HIPS may also end these Terms at any time (Section 28.4).
  • Consumers keep their rights. Consumers keep the right of withdrawal, the remedies for services that are not in conformity, and their home courts.
Read with
  • 07Common Clauses
  • 03Acceptable Use Policy
  • 04Data Processing Agreement
Before section 1
  1. Important: please read before you accept
  2. The commitments in brief
Copy link

01About these Terms

1.1

The parties. These Terms are between you and HIPS, which Section 3.1 of the Common Clauses identifies. HIPS is the only party you contract with for the Services. HIPS sells the Services to you in its own name and for its own account, and it is the merchant of record for every payment you make for them (Common Clauses Section 3.3). Hyperscale Inference Processing Systems OÜ, the Operating Company, operates the Services for HIPS, as HIPS's subcontractor and, for personal data, its processor; it is not a party to these Terms, sells you nothing, receives no payment from you and has no authority to make any promise for HIPS, and HIPS is responsible to you for what the Operating Company does in performing these Terms as for its own acts, subject to Common Clauses Sections 4 and 5 (Common Clauses Section 3.1).

1.2

Who these Terms are for. These Terms govern the use of the Services as a Buyer: through a Workspace, by its Owner and its Members, with its API Keys and with the tools its Members authorize. They do not govern the supply of GPU Time to HIPS, which the Provider Agreement governs under its own acceptance. A person who is both a Buyer and a Provider has two Agreements with HIPS, each accepted separately (Common Clauses Section 1.2).

1.3

The documents of your Agreement. Your Agreement with HIPS as a Buyer consists of:

  1. (a)these Terms;
  2. (b)the HIPS Common Clauses, version 1.0, published at /legal/common-clauses, which these Terms incorporate by reference, word for word, and which form part of these Terms as if they were written out in them;
  3. (c)the Acceptable Use Policy;
  4. (d)if you are a Business User, including a US User who is a Business User, the DPA published at /legal/dpa, for the personal data HIPS processes on your behalf; and
  5. (e)any Additional Terms you accept, such as the terms of a promotion.

The Privacy Notice explains how HIPS handles personal data as a controller, including the personal data in the Inputs and Customer Models of Consumers. It is information, not a term of your Agreement. Where a clause of these Terms takes a period, a list or a description from the Privacy Notice, it takes it as the Privacy Notice states it from time to time; a change to the Privacy Notice that reduces your rights under such a clause is a change to these Terms, made only as Common Clauses Section 9 provides.

1.4

How the documents relate. Common Clauses Section 17.3 sets the order of precedence between the documents. On the subjects the Common Clauses cover, they prevail over these Terms, except where a clause of these Terms names the Common Clause it departs from and states the departure (Common Clauses Section 1.3). These Terms depart from the Common Clauses only in the following places, each stated in the clause concerned or, for item (f), in the DPA:

  1. (a)Section 8.6 departs from Common Clauses Section 3.7 by allowing HIPS, if you are also a Provider, to apply the unused Purchased Credits of a Workspace of which you are the Buyer to a debit balance under the Provider Agreement;
  2. (b)Section 10.10(a) departs from Common Clauses Section 17.4 by making final a charge that a Business User, including a US User who is a Business User, does not question within the period it states;
  3. (c)Section 12.2(a) supplements Common Clauses Section 5 by stating HIPS's entire liability for a charge for work not performed;
  4. (d)Section 24.6(a), (c) and (e) depart from Common Clauses Section 3.7 by applying or forfeiting Purchased Credits otherwise than as payment for the Services;
  5. (e)Section 6.21 departs from Common Clauses Section 3.7 by extending the expiry of Purchased Credits held for a Batch;
  6. (f)DPA Sections 1.4, 9.8 and 15.6 depart from Common Clauses Sections 12 to 15 for a dispute arising from the Standard Contractual Clauses, which the law and the courts of Estonia govern as Clauses 17 and 18 of those clauses require;
  7. (g)Section 25.3 supplements Common Clauses Section 5.9 by placing your liability for a breach of Section 19.2 outside the limits of Common Clauses Sections 5.3 to 5.8; and
  8. (h)Section 8.8 departs from Common Clauses Section 3.7 by allowing HIPS to apply the unused Purchased Credits of another Workspace of the same Buyer to a negative balance.

Where these Terms quote a Common Clause, the quotation is for your convenience, and the Common Clause governs.

1.5

How you accept. You accept these Terms when you create an Account, and each Member accepts them when joining a Workspace. Before you accept, HIPS shows you the full text, which you can print and save, with a summary beside it of the clauses that most affect your rights: your dispute Track, the disclaimers and limits of liability, the Request-Data Policy of your Plan and, if you are a Consumer, your right to object to Training, the two methods of the face check and what refusing both means, the access described in Section 17, the absence of a completion time for Batches, the expiry of Purchased Credits and the consequences of a payment dispute. HIPS asks you to confirm those clauses by a separate action, and it records your acceptance, your confirmation and the versions of these Terms and of the Common Clauses you accepted (Common Clauses Sections 1.6 and 17.7). If you are a Consumer, HIPS also asks you, by a separate action before you accept, to agree that HIPS gives you the information before the contract, the documents of your Agreement and its communications in English, and records that agreement (Common Clauses Section 18.1). HIPS may ask you to accept these Terms again before you add Credits, subscribe to a Plan, turn Machine Payments on, create an API Key or import a model.

1.6

Prelaunch status. On the date these Terms were last updated, the Services are prelaunch and none of them is available. HIPS plans to release them in stages: first the early-access website, then Accounts and Workspaces, the API, Customer Models, and paid access. A clause that concerns a feature applies only once HIPS releases that feature. A feature these Terms or the HIPS website describe as intended, such as region selection, single sign-on or stable prices, is not available until HIPS releases it, and its terms are set when it is released.

1.7

What these Terms do not cover. Use of the HIPS website at hips.com, with or without an Account (www.hips.com redirects there, Section 6.14), is governed by the HIPS Website Terms of Use, published at https://hips.com/legal/website-terms. Payment services offered under the HIPS Payments name are provided by legal entities other than HIPS and the Operating Company, under their own terms, which they publish at the address that the Legal Information Page gives (Common Clauses Section 3.2(h)), on hosts that are not part of the Services (Section 6.14). Despite the word in its name, HIPS carries on no payment business: it holds no authorization as a payment institution, an electronic money institution or a crypto-asset service provider, receives payments only as the seller of its own Services, makes payments only of its own debts, and carries on no part of the HIPS Payments business. Those payment services are not part of the Services, and an account with HIPS Payments is not an Account (Common Clauses Section 3.10). Operators of data-center capacity supply the Approved Pool under separate agreements with HIPS. The Affiliate Program is governed as Section 1.8 provides.

1.8

The Affiliate Program. HIPS's referral program, shown on the HIPS website as the Affiliate program and in the Console as Refer and earn (the Affiliate Program, as Common Clauses Section 2.1 defines it), is governed only by the Affiliate Program Agreement, a separate agreement that a person accepts, apart from these Terms, to take part as a Program Partner. HIPS publishes the Affiliate Program Agreement and its Program Figures at hips.com/affiliates and in Refer and earn when, and only if, it opens the Affiliate Program. HIPS opens the Affiliate Program only if and when it decides to. Each of the following is a separate provision:

  1. (a)the Affiliate Program is not part of the Services, and the Affiliate Program Agreement is not part of your Agreement under these Terms;
  2. (b)a Commission or any other reward of a Program Partner is not Credits, a Fee, a refund or Earnings; it is owed, if at all, only under the Affiliate Program Agreement, these Terms give no right to it, and no Credits of any Workspace can be used to pay it or turned into it;
  3. (c)a Program Partner is not HIPS's agent, employee or representative, and has no authority to make any statement, promise or offer for HIPS, including about the Services, prices, discounts, or MTO or any other Crypto-Asset (Common Clauses Section 3.12); HIPS is not bound by anything a Program Partner says or publishes, and your Agreement alone governs what you buy (Common Clauses Section 17); and
  4. (d)if you are referred, the only benefit these Terms give you is the Referral Discount of Section 8.10, on the conditions stated there.
Section 01
  1. 1.1The parties
  2. 1.2Who these Terms are for
  3. 1.3The documents of your Agreement
  4. 1.4How the documents relate
  5. 1.5How you accept
  6. 1.6Prelaunch status
  7. 1.7What these Terms do not cover
  8. 1.8The Affiliate Program
Copy link

02Definitions

2.1

Common definitions. The capitalized terms defined in Section 2.1 of the Common Clauses have the same meanings in these Terms. They include Acceptable Use Policy, Account, Additional Terms, Affiliate Program, Affiliate Program Agreement, Agreement, API, Applicable Law, Approved Pool, Approved Provider, Batch, Batch File, Batch Line, Batch Rates, Business User, Buyer, Completion Window, Console, Consumer, Country, Credits, Crypto-Asset, Customer Model, Device, Dispute, DPA, Durable Medium, Earnings, EU Consumer, Export Control Laws, Fees, HIPS Payments, Input, Legal Information Page, Member, MTO, Operating Company, Output, Personal Pool, Plan, Privacy Notice, Program Partner, Provider, Provider Agreement, Provider App, Purchased Credits, Request, Request Data, Restricted Jurisdiction, Sanctioned Person, Sanctions Laws, Services, Track, US User, USDC and Workspace. These Terms do not define any of them again; Sections 6.15 to 6.25 set out the terms of Batches. Commission, Commission Period, Referral, Referral Code and Referral Link have the meanings given in Affiliate Program Agreement Section 2.1. Invitation Code has the meaning given in Acceptable Use Policy Section 2.1. Netting Account has the meaning given in Provider Agreement Section 2.1.

2.2

Further definitions. In these Terms, the following capitalized terms have the meanings below.

Always-On Capacity
means GPU capacity from the Approved Pool allocated to a Workspace by the hour, which is charged while allocated, including between Requests.
API Key
means a secret credential HIPS issues to a Workspace to authenticate Requests sent to the API from servers, or from the devices of the persons to whom Section 5.2 allows you to give it.
Authorized Tool
means an application or tool, such as the `hi` command-line tool or HIPS Code, that a person authorizes through the Console's device sign-in to act as that person (Section 5.3).
Billing Member
means the Owner of a Workspace, or a Member in the role of admin or billing, when acting on the Workspace's payments.
Cached Input Token
means an input token that HIPS charges at a cached-input rate under Section 9.10.
Catalog Model
means a model in HIPS's curated catalog.
Early Access
means the HIPS early-access list, through which people register interest in the Services before any invitation is sent.
Free Allowance
means the monthly free Credits that Section 7.5 describes, if HIPS grants them.
Hub Token
means an access token for a model hub that you store in a Workspace under Section 15.6.
Included Credits
means the Credits included with a paid Plan for a billing period.
Machine Payment
means a card payment for a Workspace that an agent sending Requests with an API Key of that Workspace makes through Stripe's Machine Payments Protocol with a Shared Payment Token, as Section 10.11 describes.
Owner
means the one Member of a Workspace who holds the role of owner.
Prefix Ledger
means 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 Section 13.7 states, with the worker that served each Request and the time, used only as Section 13.7 describes.
Price List
means the prices, Plan fees, Included Credits, limits and other commercial terms that HIPS publishes in the Console and on its pricing page, as they apply when you buy or when HIPS accepts a Request; the history of each rate and the time of the last price update that HIPS publishes beside them are information only, and not part of the Price List (Section 9.2).
Promotional Credits
means Credits that HIPS grants without payment, for a promotion, as a Referral Discount, or as a goodwill or corrective credit, other than the Free Allowance and Included Credits.
Referral Discount
means the discount on a first top-up described in Section 8.10.
Request-Data Policy
means the rule, set by the Plan of a Workspace and, for a Consumer, by any objection under Section 13.2(b), on whether its Request Data may be used for Training (Section 13).
Training
means using Request Data 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 in the way DPA Section 5.3 provides for a request of a public authority, 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 HIPS establishes, for a Buyer in Japan or the Republic of Korea, 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, and, for a Buyer in the United States, from its confirmation in the Console that it is certified under the EU-U.S. Data Privacy Framework, which HIPS checks against the Framework's list before it offers the model (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 uses training copies, datasets made from them and models trained on them for no other purpose, and discloses them to no other recipient; any change would be a change of the Request-Data Policy under Section 13.13, with its own assessment, and would apply only to Request Data HIPS accepts after it takes effect.
2.3

"You" and the Buyer. Where a clause concerns a Workspace, its Credits, its payments or its charges, "you" means the Buyer that holds the Workspace. Where a clause concerns a person's own conduct, "you" also means each Member and each other person who has accepted these Terms.

2.4

Interpretation. Common Clauses Section 2.2 governs the interpretation of these Terms. In a quotation from the Common Clauses, a reference to a Section is to a Section of the Common Clauses.

Section 02
  1. 2.1Common definitions
  2. 2.2Further definitions
  3. 2.3"You" and the Buyer
  4. 2.4Interpretation
Copy link

03Who may buy

3.1

Invitation only. Public self-serve sign-up is not open, and HIPS has no obligation to contract with anyone. Until HIPS announces otherwise, an Account can be created only with an Invitation Code that HIPS issues to an approved Early Access registration, or with an invitation from a Workspace to the exact email address invited, which admits that person to that Workspace only. A person admitted by a Workspace invitation cannot create a Workspace of their own until HIPS approves an Early Access registration for them. HIPS decides whom to invite, and whether to accept an Account or a Workspace, before any contract with that person exists.

3.2

Early Access creates no rights. A registration for Early Access creates no Account, no Workspace, no credential and no place in a queue. Joining the list does not guarantee an invitation, a launch date, a free-credit amount or a price. Registering for Early Access does not accept these Terms; the early-access privacy notice shown on the registration forms governs the data you give when you register.

3.3

Businesses and Consumers. HIPS sells the Services to Business Users and to Consumers, each on the terms that apply to them. When you create a Workspace, you declare whether you act as a Business User or as a Consumer. A Business User gives HIPS its organization or trade name, its Country and, where it has them, its registration number and its VAT or other tax identification number. Common Clauses Section 12.3 applies to that declaration: you shall make it truthfully and keep it current, HIPS relies on it, and if you give HIPS the impression that you act for the purposes of your trade, business, craft or profession, HIPS treats you as a Business User. The status of a Workspace is the status of the Buyer that holds it.

3.4

Where HIPS sells to Consumers. HIPS sells to Consumers on the same terms in every state of the European Economic Area (the Member States of the European Union, Iceland, Liechtenstein and Norway), as Regulation (EU) 2018/302 requires, and in the United States. In every other country, HIPS sells only to Business Users, does not accept a declaration of Consumer status, and opens a Workspace only after it has validated a VAT or business registration number. HIPS does not contract with a person who resides in Quebec, Canada, or with an organization whose head office, or the establishment through which it would deal with HIPS, is in Quebec, until it publishes French versions of the documents (Common Clauses Section 18.4). In Japan, Singapore, the Republic of Korea, Taiwan and Australia, HIPS sells only to Business Users, and the number it validates is: in Japan, a corporate number or, for a natural person who declares that they carry on a business as a merchant and use the Workspace only for that business, a qualified invoice issuer registration number; in the Republic of Korea, a business registration number; in Taiwan, a unified business number; in Singapore, a GST registration number; and in Australia, an Australian Business Number (ABN), together with your statement that you are registered for GST. HIPS validates each number against the register that the tax administration of the issuing country keeps, before it opens the Workspace and again from time to time, and keeps the result. HIPS sells to no Consumer in Japan, Singapore, the Republic of Korea, Taiwan or Australia. Credits of a Workspace whose Buyer's Country is Japan may be used only in transactions that are commercial transactions for that Buyer.

3.5

Age and capacity. You may accept these Terms and use the Services only if you are at least eighteen (18) years old, have reached the age of majority where you live, and have the legal capacity to enter into a binding contract. Identity verification confirms, from the date of birth in your identity document, that you are at least eighteen (18), and HIPS refuses the verification of anyone younger and keeps only that result, never the date of birth (Section 4.2). You shall not let anyone who does not meet these conditions use the Services through your Workspace or your credentials.

3.6

Sanctions and restricted countries. You may not accept these Terms or use the Services if you are a Sanctioned Person, if you are located, organized or ordinarily resident in a Restricted Jurisdiction, if you are the Government of Russia or a legal person, entity or body established in Russia, if you are the Republic of Belarus, its Government or one of its public bodies, corporations or agencies, or if you act for or on behalf of, or at the direction of, any of them. Common Clauses Section 7 applies to you and to every use of the Services, and you give the representations of Common Clauses Section 7.2 each time you use the Services or make a payment.

3.7

Earlier closure. You may not accept these Terms if HIPS has closed an Account, a Workspace or a provider account of yours, or of the verified person you are, for cause under Section 24.2 or under the Provider Agreement, unless HIPS agrees otherwise in writing.

3.8

Organizations and authority. If you accept these Terms for an organization, you represent and warrant that you have the authority to bind it, and "you" means that organization. If you did not have that authority, you are bound by these Terms yourself, as a Business User. The organization is responsible for the acts and omissions of its Members, of the people who use its API Keys and of the tools its Members authorize, as for its own.

3.9

Members. A Member uses the Services on behalf of the Buyer that holds the Workspace. Each Member shall comply with these Terms and the Acceptable Use Policy in that use and is responsible to HIPS for their own breach. The Buyer, not a Member personally, pays the charges of the Workspace and gives the representations, warranties and indemnities that these Terms ask of a Buyer, unless the Member is also the Buyer. The Owner decides whom to invite and remove and which role each Member holds.

Section 03
  1. 3.1Invitation only
  2. 3.2Early Access creates no rights
  3. 3.3Businesses and Consumers
  4. 3.4Where HIPS sells to Consumers
  5. 3.5Age and capacity
  6. 3.6Sanctions and restricted countries
  7. 3.7Earlier closure
  8. 3.8Organizations and authority
  9. 3.9Members
Copy link

04Identity verification and Accounts

4.1

Verification of every person. A person may use the Services through an Account, as the Owner or a Member of a Workspace, only after they have passed identity verification through HIPS's identity verification provider, named in the Privacy Notice, and, for the face check by a person, a person at HIPS (Section 4.8); a person who uses the Services only through a Business User's API Key under Sections 4.10 and 5.2 need not pass it, and uses them as that Business User, which is responsible for them as for itself (Section 3.8). The checks include an identity document; a face check, which is part of every verification and which you complete, as you choose, either by the automated face check, for which HIPS asks your explicit consent, or by the face check by a person (Sections 4.8 and 4.9); a check that you are at least eighteen (18) years old (Section 3.5); and screening against sanctions lists. HIPS screens against no list of politically exposed persons and no list of criminal convictions or offenses. A Workspace receives no Credits of any kind, and HIPS accepts no Request for it, until its Owner has passed. An invited Workspace exists and shows the Console before then, but it holds no Credits and runs no Request.

4.2

What HIPS keeps. HIPS keeps a verification reference, its status, the time of the decision, the verification provider's case identifier, your consent to the face check, with its time, the version of the consent text shown to you and any refusal or withdrawal, in one record that covers both methods of the face check and does not show which you used (Section 4.8; Privacy Notice Section 7.6), the issuing country of your identity document, which the verification provider reports and which never decides your Country (Common Clauses Section 2.1), the result of the check that you are at least eighteen (18) years old, but never your date of birth, and HIPS's identifier of you as a natural person: a keyed hash of the issuing country, the type and the number of your identity document and your date of birth, and, where that document carries a personal identification number that its issuing country assigns for life, a second keyed hash of that country and that number (except the numbers that Privacy Notice Section 3.7(e) excludes). HIPS computes each keyed hash with a secret key that only HIPS holds, from the result that its identity verification provider returns, at the moment it receives that result; it stores the keyed hashes, discards the particulars at once, and never derives an identifier from images of your face or any other biometric data. Without that key, none of the particulars can be read from a keyed hash. HIPS recognizes the same person across two identity documents only where both carry the same personal identification number; otherwise it relies on your obligation not to verify with a second document (Acceptable Use Policy Section 8.1). For persons whose Country is the Republic of Korea, Singapore or Japan, Privacy Notice Section 3.7(e) states which identity documents are accepted and from which number the keyed hash is derived; HIPS never derives it from a resident registration number, an NRIC or other national identification number of Singapore, or an Individual Number of Japan. HIPS uses that identifier, on the basis of its legitimate interest in preventing fraud, only to keep one verified identity per person (Section 4.5), to recognize a person whose Account, Workspace, provider account or participation in the Affiliate Program HIPS closed for cause (Sections 3.7 and 24.5; Affiliate Program Agreement Section 19.12), and, after a deletion, to confirm who may change where HIPS pays what it owes (Section 4.7(d)). Because it is not derived from biometric data, HIPS keeps it whether or not your consent to the face check stands, and withdrawing that consent does not delete it: while your Account exists; after your Account is deleted, for three (3) years after the deletion, the period of Privacy Notice Section 7.6, and, beyond it, while an amount remains owed to you (Section 4.7(f)); and after a closure for cause, for five (5) years after the closure (Section 24.5). HIPS does not keep document images, document numbers or dates of birth (other than within a keyed hash, from which they cannot be read without HIPS's key), face images or biometric data; those stay with the verification provider, as the Privacy Notice describes, except the documents a person sends for a check by a person at HIPS under Section 4.7(d), which HIPS deletes as that item provides.

4.3

Re-verification and outcomes. HIPS may ask you to verify again after a risk event, such as a payment dispute, a change in a sanctions list, a sign of account takeover or a suspension, or where it has another reasonable ground to doubt that a verification remains accurate; it does not ask you to verify again on a fixed schedule. A sanctions match holds onboarding until a person at HIPS has reviewed it, and is handled under Common Clauses Section 7.7. If your verification fails or is not completed, you may start it again as often as you wish, after a wait that grows with each attempt that reached HIPS's identity verification provider: one (1) hour after the first, twenty-four (24) hours after the second and seven (7) days after each later one; at any time you may instead use the face check by a person or ask for a review. A failure because of a sanctions match, a duplicate identity or an earlier closure for cause is never retried automatically and is reviewed by a person at HIPS. You may ask for a review of any refusal by a person at HIPS who has the authority to change it, within thirty (30) days of the notice of the refusal, by the route that notice gives; you may state your point of view, and HIPS tells you its decision, with reasons, on a Durable Medium within ten (10) business days. The parts of the Services that verification gates stay closed to you until you pass. HIPS does not close your Account because you have not passed verification; but an Account that has never passed verification and has had no sign-in for twenty-four (24) months, and a Workspace whose Owner has not passed verification within twelve (12) months of its creation and in which no Member has signed in during that time, are deleted after HIPS gives the Owner, or you, thirty (30) days' notice.

4.4

Verification of organizations. Before HIPS opens the higher paid Plan to a Workspace held by an organization, and whenever it has reasonable grounds to doubt the information given under Section 3.3, HIPS verifies the organization as Provider Agreement Section 3.7 describes: its existence and status in the register of its country, the persons entitled to represent it and the authority of the person acting, and the natural persons who own twenty-five percent (25%) or more of it or otherwise control it, and it screens them against sanctions lists. Otherwise HIPS verifies the Owner as a natural person, validates the VAT or registration number it is given (Sections 3.3 and 3.4), screens the organization's name against sanctions lists, relies on the business information given under Section 3.3, and makes no statement about the identity of the organization. HIPS may ask for documents that show an organization's existence, its registration, its tax status or the authority of the person acting for it.

4.5

One person, one identity. One verified identity belongs to one natural person. You shall not create or use more than one identity, or use the identity of another person, to obtain additional Free Allowances or other benefits, to evade a limit, a suspension or a closure, or for any other purpose. HIPS may link the Accounts and Workspaces that resolve to the same verified person. A linked Account receives no additional Free Allowance, and where the ground for a measure under Section 24 concerns the person, HIPS may apply the measure to every Account of that person and to every Workspace of which that person is the Buyer. A Workspace held by another Buyer is not linked to a person because they are a Member of it; a measure concerning that person affects that Workspace only by suspending their membership.

4.6

Accurate information. You shall give accurate, complete and current information when you create an Account or a Workspace, verify your identity, declare your status, set up billing and give tax information, and you shall correct it promptly when it changes. HIPS relies on it. If you are a Business User or a US User, Common Clauses Section 6.1(f) applies to a false or incomplete declaration of your status, Country, tax status or VAT number.

4.7

Deleting your Account. You may delete your Account at any time. HIPS never refuses or delays the deletion because Earnings, Commissions or any other amount are pending, held, payable or owed, whether by you or by HIPS, or because you are the only Owner of a Workspace. Deletion revokes your sessions and the authorizations of your Authorized Tools and ends your Workspace memberships. Each of the following is a separate provision:

  1. (a)Workspaces you alone own. Before it deletes your Account, the Console shows you each Workspace of which you are the only active Owner, with what then happens to it, and you may first make another Member its Owner. A Workspace of which you are still the only active Owner when your Account is deleted is deleted with it, with the effects of Section 14.2: its unused Credits end when it is purged, except as Sections 12.1 and 27.12 provide. If you are a Consumer, before you confirm the deletion, the Console shows the unused Purchased Credits of each Workspace that is deleted with your Account and lets you ask for their refund under Section 27.12 in the same step; if you do not, you may still ask within the period of Section 27.12 by writing from the email address of your Account, and HIPS keeps the ledger records and that address that the refund needs until that period ends (item (f)). If the Buyer of that Workspace is a Business User other than you yourself, HIPS does not delete it with your Account. If the Business User named a Member as the Workspace's successor Owner beforehand, in the Workspace's settings, HIPS makes that Member its Owner and tells the Workspace's other Members. Otherwise HIPS keeps the Workspace running without an Owner, despite Section 6.3, with its Credits and data, for thirty (30) days. This is not a measure under Section 24, and 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 and are charged to the Business User, 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. HIPS tells the Business User so at once on a Durable Medium, at the email addresses of the Workspace's remaining Billing Members and at any billing contact address the Business User gave HIPS, with the date on which the Workspace will be deleted. During that time the Business User may name, by writing to HIPS with evidence of its authority, a Member or another person, who becomes its Owner once they hold an Account and have passed identity verification; HIPS chooses no Owner itself. If the Business User names none in that time, HIPS deletes the Workspace with the effects of Section 14.2, except that, when the Workspace is purged, HIPS refunds its unused Purchased Credits and the unused part of any prepaid Plan fee, as Section 24.7 provides (Section 12.1(g)); and while the Workspace can be restored, the Business User may still ask HIPS in writing, with evidence of its authority, to restore it and make the person it names its Owner (DPA Section 12.4). If you are yourself the Business User, as a sole proprietor, the Workspace is deleted with your Account unless you first make another Member its Owner.
  2. (b)Earnings. If you are a Provider, deleting your Account closes your provider account and ends the Provider Agreement. HIPS settles the GPU Time your Devices supplied before then, and pays every amount settled as payable, as that Agreement provides for its end (Provider Agreement Section 17.10), to the payout account that HIPS keeps connected for that purpose until it has paid. Earnings are lost only where the Provider Agreement provides that they do not accrue or are forfeited, and an amount that cannot be paid remains owed as Provider Agreement Section 10.13 provides.
  3. (c)Commissions. If you are a Program Partner, deleting your Account ends the Affiliate Program Agreement, and HIPS pays your Commissions as that Agreement provides for its end (Affiliate Program Agreement Sections 19.9 and 19.11). A Commission is lost only where that Agreement provides that it lapses, is reversed or is forfeited. If you are a Consumer, including a US User who is a Consumer, ending that Agreement by deleting your Account does not by itself make your Commissions lapse: your Referrals still pending when it ends that qualify, and pass the checks, within the period that their Commission Periods would otherwise have run count toward eligibility, although they earn no Commission of their own after it ends, as Affiliate Program Agreement Section 19.11(c) provides.
  4. (d)What HIPS owes you. An amount of Earnings or Commissions that has become payable remains an amount in US dollars that HIPS owes you, as its own debt, until it is paid, subject to the payout conditions and the rights of set-off of the Agreement under which it is owed; HIPS holds no money or Crypto-Asset for you meanwhile (Common Clauses Sections 3.5, 3.6, 3.11 and 3.13). After the deletion, HIPS pays it only in money, to a payout account in your own name, as Provider Agreement Section 17.8(a) and Affiliate Program Agreement Section 19.9(a) provide, and never in a Crypto-Asset (Common Clauses Section 3.11). After the deletion, HIPS also lets you complete or update the payout details and tax information that a payment needs, and connect or reconnect a payout account, through a link it sends, without restoring your Account, on your request and whenever a payout condition is not met. HIPS sends that link, and its notices about what it owes you, only to the email address of your Account as it was when you deleted it, unless you have given HIPS another address as this item allows. HIPS accepts another address for its notices, a change of the legal name in your payout details, or a payout account other than the one connected when you deleted your Account only after HIPS has confirmed that the person asking is the person whose identity was verified for your Account: by a new identity verification, the face check included (Section 4.8), in which the identifier of a natural person that HIPS kept (Section 4.2) matches; or, where HIPS kept none, the identifier does not match, or that person declines a new face check, after a person at HIPS has checked other evidence that HIPS reasonably asks for, such as an identity document and, for a change of name, a document that shows the old and the new name, without any face check; or, for an organization whose representative has changed, after HIPS has verified the new representative and their authority to act for it (by a register extract or a power of attorney, as Provider Agreement Section 3.8 describes). The identifier changes when an identity document is renewed or replaced, so a mismatch alone is not a sign of takeover. Where the identifier does not match, HIPS offers the check of other evidence by a person at HIPS, including the earlier and the new identity document, and holds the payout under Provider Agreement Section 11.1(d) or Affiliate Program Agreement Section 11.1(d), within the time limits of their Section 11.3, only where that check also fails to confirm that the person asking is the person whose identity was verified for your Account. Whatever the route, HIPS first tells the email address of your Account as it was when you deleted it, and the holder of the payout account connected then, of the change asked for, and the change takes effect no earlier than fourteen (14) days after that notice unless that holder confirms it sooner. HIPS accepts a change of legal name only on a document that it confirms with the register or authority that issued it; it asks for a document that shows the old and the new name, accepts it with every other detail redacted that this confirmation does not need, and never asks why the name changed; and it deletes the documents a person sends for a check under this item within seven (7) days after the later of its decision and the end of the waiting period, unless it needs them to establish, exercise or defend a legal claim about the change, keeping only the decision, its time, who made it and the kinds of document checked (Privacy Notice Sections 3.1 and 11.5). Where it accepts a change under this item, HIPS pays only in money to a payout account in your own name, which, where you are a natural person, is held in the name of the person so confirmed. HIPS never refuses payment of an amount it owes only because a person declines a new face check or because the identifier does not match, and never delays it for either reason beyond the time that the check of the other evidence reasonably takes, and in any case no longer than ten (10) business days; the notice and the waiting period of this item apply whatever the route. HIPS reminds you of any amount it still owes you, at the email address of this item, at least three (3) times: within thirty (30) days after the first payment date on which it could not be paid, at least once in each later calendar year, and for the last time no later than ninety (90) days before the limitation period of that Agreement ends (Provider Agreement Section 17.8(f); Affiliate Program Agreement Section 19.9(g)).
  5. (e)What you owe HIPS. Deleting your Account does not release any amount you owe HIPS, which becomes due as Section 24.8 provides, and does not end a measure HIPS has taken, or an investigation it has begun, under Section 24.2.
  6. (f)What HIPS keeps. After the deletion, HIPS keeps only the records that a legal obligation requires it to keep, or that it needs to pay what it owes you, to make a refund you may still ask for under Section 27.12, to recover what you owe it, to keep one verified identity per person, or to establish, exercise or defend a legal claim: the verification reference, status and decision time; the identifier of a natural person of Section 4.2, for the periods that Section states and whether or not your consent to the face check stands, together with whether its holder received a Free Allowance or a Referral Discount, only to keep one verified identity per person (Section 4.5), so that a later Account of the same person receives no second Free Allowance or Referral Discount, to confirm who may change your payout details under item (d) while an amount remains owed to you, and, after a closure for cause, to recognize the same person (Section 24.5); the ledger, settlement, payout and tax records; if you are a Consumer, the email address of your Account and the ledger records that a refund under Section 27.12 needs, until the period of that Section ends (item (a)); and the record Section 24.5 describes after a closure for cause. HIPS keeps each for the periods in Section 14 and in the Privacy Notice, and it deletes the rest.
4.8

The face check. A face check is part of every identity verification, for every person, whether a Buyer, a Member, a Provider or a Program Partner. You choose, without giving a reason, between two methods, which have the same effect and give the same access, Credits and benefits:

  1. (a)the automated face check, also called the liveness check, which captures images of your face while you verify, checks that they come from a live person and compares them, by an automated biometric comparison made only between them and the photograph in your identity document, to confirm your identity, and for which HIPS asks your explicit consent; or
  2. (b)the face check by a person, in which a person at HIPS sees you live on a video call that is never recorded, checks that you are present and compares you with the photograph in the identity document you show, with no automated processing of your face and no biometric data.

HIPS keeps no record of which method you used. HIPS plans to add verification through a European Digital Identity Wallet once such wallets are available to it, which states a present plan and not a promise; until then, these two methods are the only routes of the face check. HIPS makes a face check part of every verification, for a Buyer as for a Provider or a Program Partner, because the person who verifies may receive benefits that HIPS grants once per person (such as a Free Allowance, if HIPS grants one, on the first Workspace that person owns, a Referral Discount and promotions), pays by card under HIPS's own merchant account, and sends Requests to the personal Devices of Providers, and because a check of an identity document alone cannot show that the person verifying is present and is the person whom the document shows. For a Member who is neither the Owner nor a Billing Member, HIPS makes it part of verification because such a Member acts in the Workspace through an Account of their own, with the powers their role gives (such as, depending on the role, creating or revoking API Keys, authorizing tools that act in the Workspace, and reading its data and usage), which a person who only uses an API Key given to them under Section 5.2 does not hold. You ask for the face check by a person on the face check screen, before any check or after an automated face check that did not succeed, in the Console or the Provider App, without giving a reason. A person at HIPS carries it out on a video call that is never recorded; if HIPS later has its identity verification provider carry it out, it does so on the same terms, never recorded and with no automated processing of your face, and HIPS tells you before the call who will carry it out. Before the call, HIPS tells you who will see you, what that person checks and that the call is not recorded, and asks you to agree to it by a separate action. HIPS does not ask you why you choose it, or to state or prove a disability or any other reason, keeps no reason you give, and requires its identity verification provider to keep none. HIPS keeps one record of your consent to the face check, with its time and the version of the consent text shown to you, which describes both methods; it keeps no record of which method you used, and of the face check by a person it keeps only the outcome of the verification (Section 4.2). HIPS uses the automated face check to confirm that the person who verifies is a live person, present while verifying, and not a photograph, a recording or a synthetic image, and that they are the person whom the identity document shows; it does not use it to search for your face among other people's verifications: HIPS's identity verification provider compares your face only with the photograph in your identity document, keeps no face template after the decision, and, under its contract with HIPS, runs no face search and no comparison with any other collection of faces for HIPS, and uses no data of HIPS's verifications for any purpose of its own. HIPS's identity verification provider performs the automated face check as part of HIPS's verification, and HIPS keeps only the records in Section 4.2. Before the automated face check, HIPS tells you that it is automated, what is collected, for what purpose and for how long, and asks for your explicit consent by a separate action, apart from your acceptance of these Terms, which it records. Whatever your Country and wherever you are, that consent is also your written release for the collection of a biometric identifier, given before the check, and HIPS gives every person, before the check, the notices, and asks for the consents, that the biometric privacy and consumer health data laws of the states of the United States require, including the Washington My Health My Data Act (RCW 19.373) and Nevada Senate Bill 370, as Privacy Notice Section 3.7 describes. HIPS publishes the schedule on which the scan is retained and destroyed, under which HIPS's identity verification provider destroys it as Privacy Notice Section 3.7(c) provides, at the latest thirty (30) days after the decision on your verification unless a review of that decision or a legal claim about it is pending, and then when it is resolved. For persons in Canada, Privacy Notice Section 14.3 also applies.

4.9

Important: if you refuse both face checks

If you refuse both face checks. You decide whether to consent to the automated face check, and refusing it is never a breach of these Terms: you may verify through the face check by a person instead (Section 4.8). If you refuse both methods, you cannot pass identity verification, and so, for as long as you have not passed:

  1. (a)no Workspace you own receives Credits of any kind, the Free Allowance included (Sections 4.1 and 7.5), and you cannot buy Credits or subscribe to a paid Plan;
  2. (b)HIPS runs no Request for a Workspace you own, and you may not use the Services as a Member of any Workspace (Section 4.1), although a Business User may let you use an API Key of its Workspace on its behalf (Section 4.10);
  3. (c)none of your Devices becomes eligible for work and you cannot earn anything under the Provider Agreement; and
  4. (d)HIPS issues you no Referral Link or Referral Code and attributes no Referral to you, so you cannot take part in the Affiliate Program (Affiliate Program Agreement Sections 3.6 and 4.1).

You may start verification again at any time and choose either method then. You may withdraw your consent to the automated face check at any time; withdrawing it does not undo a verification already completed, but where HIPS asks you to verify again under Section 4.3, a face check, by either method, is part of that verification, and this Section 4.9 applies if you refuse both. Declining a new face check never stops HIPS from paying, to the payout account already connected in your name, Earnings for work performed before HIPS asked you to verify again, at the latest when the time limits for holding them under the Provider Agreement end, and Commissions that had become payable under the Affiliate Program Agreement before HIPS asked, which declining never by itself delays (Affiliate Program Agreement Section 3.6), subject to the reversals, forfeitures and set-off that those Agreements provide (Provider Agreement Sections 9.6, 12 and 13; Affiliate Program Agreement Sections 9, 12 and 13); Section 4.7(d) governs a change of payout details after a deletion.

4.10

People who work for a Business User. If you are a Business User, you shall not require any employee, worker or contractor to become a Member, or to consent to the automated face check, as a condition of their employment or engagement, and you shall not cause any detriment to a person who refuses or withdraws that consent; a person who does not consent may verify through the face check by a person or decline to be a Member. A person who declines both methods of the face check, or does not want to become a Member, may use the Services for you through an API Key of your Workspace under Section 5.2, including from the devices they work on, without becoming a Member. This route exists so that nobody is required to consent as a condition of their work; it gives that person no Workspace, Credits or Free Allowance of their own. HIPS tells you only whether a Member has passed verification, never which method of the face check they used or whether they refused or withdrew consent to the automated face check.

Section 04
  1. 4.1Verification of every person
  2. 4.2What HIPS keeps
  3. 4.3Re-verification and outcomes
  4. 4.4Verification of organizations
  5. 4.5One person, one identity
  6. 4.6Accurate information
  7. 4.7Deleting your Account
  8. 4.8The face check
  9. 4.9If you refuse both face checks
  10. 4.10People who work for a Business User
Copy link

05Sign-in, API Keys and your tools

5.1

Sign-in. You sign in with a one-time link sent by email, with Google, or with a passkey. You shall keep your sign-in methods secure, shall not share your Account, and shall tell HIPS without delay, through the security contact on the Legal Information Page, if you believe that your Account, an API Key or an Authorized Tool has been compromised. Your Account is separate from any account with HIPS Payments.

5.2

API Keys. HIPS issues API Keys to a Workspace as its credential for calling the API and the SDKs from servers and, for the persons to whom this Section allows you to give an API Key, from the devices they use for your work, and for nothing else. API Keys are confidential. You shall keep them secret; shall not publish them in source code or embed them in an application that runs in a browser or that you distribute to your customers or other users; shall not give them to anyone other than a Member, an employee, worker or contractor of yours who acts on your instructions and whom you bind to keep them confidential, or a service provider of yours that is bound to keep them confidential, and such a person uses the API Key on your behalf and need not be a Member; and shall revoke at once any API Key you suspect has been exposed. HIPS may revoke or restrict an API Key that it has reasonable grounds to believe has been exposed or misused, and it tells you when it does.

5.3

Tools that sign in as you. A person's tools, such as the `hi` command-line tool, the Provider App and HIPS Code, do not use API Keys. They sign in as the person, through the device authorization flow approved at console.hips.com/device. When you approve a tool there, you see its name, the scopes it asks for and the network address it connects from, and you choose the Workspace it acts in. The tool then acts as you, only within the scopes you approved and, for inference, in the Workspace you chose, and its usage is charged to that Workspace. HIPS records each authorization. You can see every authorization on your Account page and revoke any of them at any time. You shall approve a code only if you started the sign-in yourself, on a device you control.

5.4

Responsibility for your credentials. Every Request made with an API Key of your Workspace, and every action of an Authorized Tool you approved, is treated as yours.

  1. (a)Business Users, including US Users who are Business Users. You are responsible for every such Request and action and pay its charges, whether or not you authorized it, except to the extent it results from HIPS's breach of these Terms, and except a Request or action made after the credential was revoked, or more than twenty-four (24) hours after you told HIPS under Section 5.1 that the credential was compromised, whichever is earlier. The same applies to a Machine Payment made with such a credential (Section 10.11).
  2. (b)Consumers, including US Users who are Consumers. You pay the charges of a Request made with your credentials without your authority only to the extent it results from your failure to keep your credentials secure as this Section 5 requires, and never for a Request made after you told HIPS under Section 5.1 that the credential was compromised.
5.5

Security measures. Where HIPS has reasonable grounds to believe that a credential has been compromised or misused, HIPS may require you to change a sign-in method, revoke sessions, API Keys or authorizations, or pause a Workspace under Section 24.

Section 05
  1. 5.1Sign-in
  2. 5.2API Keys
  3. 5.3Tools that sign in as you
  4. 5.4Responsibility for your credentials
  5. 5.5Security measures
Copy link

06The Services

6.1

Your right to use the Services. Subject to these Terms and to your Plan, HIPS grants you, for as long as your Agreement lasts, a non-exclusive, non-transferable right, without the right to sublicense, to use the API and the Console to run inference for your own purposes, including in applications and services you offer to your own users. The right ends when your Agreement ends.

6.2

What the Services comprise. The Services available to Buyers comprise:

  1. (a)usage-based inference on Catalog Models, through an OpenAI-compatible API for language models and through the HIPS task API and SDK for other model types;
  2. (b)inference on Customer Models under Section 15;
  3. (c)Always-On Capacity;
  4. (d)the Console and its playground; and
  5. (e)Batches under Sections 6.15 to 6.25.

Each of these is available only once HIPS releases it (Section 1.6).

6.3

Workspaces. You use the Services through a Workspace. Each Workspace has exactly one Owner and may have Members in the roles of admin, developer and billing. Credits, API Keys, Customer Models, usage and the Request-Data Policy belong to the Workspace.

6.4

Pools and lanes. Requests run in one of two pools, the Personal Pool and the Approved Pool, as Section 17 describes. The shared lane is usage-based. Always-On Capacity is charged by the hour and comes from the Approved Pool only. A Request does not move to another pool unless you have enabled cross-pool fallback, which is off by default and never overrides a region rule or the Request-Data Policy.

6.5

Models and versions. HIPS does not silently substitute one model for another. A pinned model identifier is answered only by that version. A model identifier without a version (an alias) is answered by the version HIPS's catalog names as current for it, and each response names the pinned identifier that answered. HIPS may move an alias to a newer version of the same model by a scheduled change that it shows on the model's page before it takes effect; that is not a substitution of one model for another, and the version the alias leaves stays callable by its pinned identifier until its retirement date under Section 6.6. If you need one version, send its pinned identifier. A Request with a parameter the model does not support is rejected; the parameter is not silently dropped.

6.6

Retirement of Catalog Models. HIPS may retire a Catalog Model or a version with at least thirty (30) days' notice, given by email to the Owner and admins of every Workspace that called it in the ninety (90) days before the notice, and shown in the catalog with the retirement date. A pinned identifier stays callable until its retirement date, and deployments on it stop on that date. HIPS may retire a model with shorter notice, or at once, where the model's license, a rights holder's notice under Section 15.10, Applicable Law or a security risk requires it, and it tells you as soon as it can.

6.7

Limits. Each Plan carries limits, such as requests and tokens per minute, concurrency and allocations, which the Price List states for each Plan and the Console shows for each Workspace, and Batches carry the limits of Section 6.16. HIPS may also apply temporary limits to protect the Services, other Buyers or Providers, or under Section 24.

6.8

Regions. HIPS keeps your Account data and its billing records in Ireland, in the European Union, and holds in each of its regional processing locations only the copies of them that the location needs to serve Requests, such as the hashes of API Keys. It processes Requests in its regional processing locations in Ireland, in the United States (Ohio) and in Japan (Tokyo), and on the data-center capacity and the Devices that it reaches from them (Section 17.6). Each of the following is a separate provision:

  1. (a)a Request sent to ai.hips.com enters the regional processing location nearest to it, and a Request without a region requirement may be processed in any region and forwarded from one regional processing location to another;
  2. (b)the regions are `eu`, which covers the European Economic Area (the 27 Member States of the European Union, Iceland, Liechtenstein and Norway), `us`, which covers the United States (its fifty states and the District of Columbia), and `jp`, which covers Japan; HIPS accepts each as a region requirement only once it enforces that requirement; and supply serves a region requirement only where it is located in that region, so that the supply in the United Kingdom, Switzerland and Canada, and in every other country outside the EEA, the United States and Japan, serves only Requests without a region requirement;
  3. (c)a region requirement covers the processing of the Request at the regional processing location that serves it and at any regional processing location to which it is forwarded, on the data-center worker or Device of every attempt, retry and fallback and in any verification of it; the prompt caches and the Prefix Ledger records made from it; and the content that HIPS stores for it, with the backups of that content. It does not cover your Account data or HIPS's billing and usage records, which HIPS keeps in Ireland; the operational logs, metrics and error and crash reports of the Services, which carry no Request Data and reach HIPS's systems in Ireland or its error-reporting service; access by HIPS personnel to stored content under Section 13.9, which takes place from the European Union; or, on ai.hips.com, the decryption that items (e) and (h) describe;
  4. (d)eu.ai.hips.com, us.ai.hips.com and jp.ai.hips.com are the regional addresses of the API: each carries the region requirement of its region, ends the encrypted connection only inside that region, and refuses a Request whose region requirement names another region;
  5. (e)a Request with a region requirement that is sent to ai.hips.com and enters a regional processing location outside its region is decrypted there, in memory only and never stored there, and forwarded to a regional processing location of its region; that decryption is processing of the personal data in the Request, with Amazon Web Services, in the country of that location, which HIPS treats as a transfer to that country with the safeguards that the Privacy Notice and the DPA state; a Buyer that needs the connection itself kept inside its region therefore sends its Requests to that region's regional address, as HIPS recommends;
  6. (f)region selection is available only on the higher paid Plan, and for each region only from the date HIPS states in its documentation that it enforces that region; until then a Request that names that region is refused;
  7. (g)where a region requirement applies, no Request silently crosses it: if no eligible supply in the region is available, the Request fails rather than running elsewhere; and
  8. (h)on ai.hips.com, the encrypted connection first ends at the point of presence of Amazon CloudFront, HIPS's content delivery network, that is nearest to the client, which may be in any country where CloudFront operates; it holds the Request in memory only, caches no response and passes the Request to a regional processing location over an encrypted connection; that decryption is processing by Amazon Web Services in the country of the point of presence, which HIPS treats as a transfer to that country with the safeguards that the Privacy Notice and the DPA state, and which a region requirement does not cover; the regional addresses of item (d) pass through no point of presence, so a Workspace that needs the connection itself kept inside its region uses that region's address.
6.9

Capacity is not reserved. A capacity snapshot is not a reservation. Allocation is not model readiness. Stable pricing is not a capacity guarantee. Supply in the Personal Pool depends on independently owned Devices and is not continuously available capacity merely because Devices are online at a given moment.

6.10

No machine access. The Services provide inference and allocations of GPU capacity that serve your models. They do not give you access to any machine, virtual machine, operating system or shell.

6.11

HIPS may refuse a Request. HIPS may refuse, stop or decline to retry a Request that exceeds a limit, exceeds the available Credits, breaches the Acceptable Use Policy or Sanctions Laws, is flagged by the safety measures of Acceptable Use Policy Section 11.10, or cannot be served under its requirements. A refused Request is never charged.

6.12

Changes to the Services. HIPS may change, add or remove features, models, pools, Plans and payment methods, for a reason listed in Common Clauses Section 9.1. HIPS gives notice under Common Clauses Section 9.2 of a change that materially reduces a Service you pay for, and if you do not accept it, you may terminate under Common Clauses Section 9.4 with the refunds it provides. Section 27.8 adds rules for Consumers.

6.13

Beta features. A feature HIPS labels as beta, preview or early access is governed by Common Clauses Section 4.8 and may be subject to Additional Terms.

6.14

Where the Services are. Each of the following is a separate provision:

  1. (a)under hips.com, HIPS provides the Services only on these hosts: ai.hips.com, for the API (inference, the task API and the batch interface at https://ai.hips.com/v1, and the device sign-in that the tools of Section 5.3 use, which HIPS answers in the European Union at eu.ai.hips.com and ai.hips.com relays); eu.ai.hips.com, us.ai.hips.com and jp.ai.hips.com, the regional addresses of the API (Section 6.8); console.hips.com, for the Console, including the page console.hips.com/device on which you approve the sign-in of a tool; providers.hips.com and the hosts under it of HIPS's regional processing locations, for the endpoints to which the Provider App connects, which the Provider Agreement governs; and weights.ai.hips.com, from which Devices and HIPS's data-center workers download the Provider App's updates, the engines and the catalog models that HIPS signs. HIPS may open further interfaces on ai.hips.com, such as one for managing a Workspace, and each becomes part of the Services only when HIPS releases it (Section 1.6);
  2. (b)the HIPS website and its documentation are at hips.com; they describe the Services and lead into the Console, and Section 1.7 governs their use. 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. www.hips.com sets no cookie and asks for no choice of its own;
  3. (c)every other host under hips.com, including every host that HIPS Payments uses, is not part of the Services and is not governed by these Terms (Common Clauses Section 3.10);
  4. (d)you shall send API Keys, and the access tokens of Authorized Tools, only to ai.hips.com or a regional address of the API (Section 6.8), except that the Provider App sends its access token to providers.hips.com to enroll a Device and to renew the Device's certificate, as the Provider Agreement provides. A page on any other host that asks for your HIPS sign-in, an API Key or a payment for the Services is not a page of the Services: HIPS takes card payments for the Services only on its payment processor's pages that the Console opens (Section 10.4) and through Machine Payments on ai.hips.com (Section 10.11), and HIPS's automated emails about the Services come from noreply@hips.com;
  5. (e)each cookie HIPS sets belongs to the one host that sets it and is never sent to another host, and HIPS never sets a cookie for the whole hips.com domain, so no host of HIPS Payments receives one; 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; ai.hips.com and providers.hips.com set no cookies. Browsers may also send to hips.com, www.hips.com, console.hips.com and ai.hips.com 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. The HIPS website reads from your browser's storage only the entries that the Privacy Notice lists, never reads or uses storage, caches or service workers that an earlier website at hips.com or www.hips.com left in your browser, and removes them: hips.com answers every request for the script address of a service worker that an earlier website used with a script that unregisters itself, and sends a Clear-Site-Data header limited to storage and cache, never cookies, on its first response to a browser that does not yet hold the cookie that records only that this was done (Privacy Notice Section 13.3), and www.hips.com answers that script address as item (b) provides. HIPS stops sending that header and setting that cookie twelve (12) months after hips.com began to serve the HIPS website, on the date that the Legal Information Page states, and keeps answering the script address of an earlier service worker as this item and item (b) provide. Until an earlier service worker is unregistered, your browser may still run it for requests to that host, and HIPS uses nothing that it holds or sends;
  6. (f)the HIPS website and the Console each ask you once for your consent to their own cookies, apart from each other: a choice you make on hips.com does not apply on console.hips.com, and the reverse; and
  7. (g)a Referral Code you arrive with reaches the Console only in a parameter of the link that the HIPS website builds into the Console, which the Console keeps only where you consent to its own referral cookie and otherwise drops, or with your Early Access registration, and never in a cookie shared between hosts. If you have not yet answered the Console's cookie banner when the parameter arrives, the Console holds the value only in the open page, not in a cookie or in browser storage, shows the banner, and sets its referral cookie only if your answer allows it; otherwise it drops the value. HIPS removes the `ref` parameter that carries a Referral Code from the server and edge records of www.hips.com, the HIPS website (including its redirect from hips.com/console to the Console) and the Console.

The Privacy Notice describes the cookies of each host.

6.15

Batches. You may submit Requests to run together and asynchronously as a Batch, through the batch interface of the API: you upload an input file in which each line is one Request, create the Batch with a Completion Window, and retrieve its results in an output file and an error file. Every line of one input file is for the same model, and each line calls one of the routes that HIPS's documentation lists for Batches. Each Batch Line is a Request, and every provision of these Terms and of the Acceptable Use Policy on Requests applies to it, except as Sections 6.15 to 6.25 provide. HIPS accepts a Batch when it creates it in answer to your request, after checking the input file, its model, the route and the Completion Window; it then validates the Batch, checking each line and counting its input tokens, before any line runs. HIPS may refuse a Batch, or any line of it, on a ground in Section 6.11, other than that it exceeds the available Credits, or on a ground in Section 6.16, and a refused line is never charged; a Batch whose maximum charge the available Credits cannot carry is not refused but ends as failed for insufficient Credits under Section 6.21.

6.16

Batch limits. Batches are subject to the limits HIPS publishes in its documentation and the Price List, including the number of lines and the size of an input file, the number of embedding inputs in a Batch, the number of Batches a Workspace may create in an hour and have open at once, and the input tokens a Workspace may have waiting in Batches for each model, which the Price List states for each Plan. HIPS may change these limits under Section 6.12.

6.17

Important: Batches have no completion time, and unfinished lines expire

The Completion Window, and no completion time. You choose the Completion Window when you create a Batch: twenty-four (24) hours unless you choose another, or any whole number of hours or days from twenty-four (24) hours to seven (7) days. HIPS runs the lines of a Batch when capacity is free, after the interactive Requests it serves, in the order and on the supply it decides within the Batch's requirements (Section 6.24). HIPS does not promise when a Batch or any line of it will finish, or that any line will finish within the Completion Window: the Completion Window is the time after which unfinished lines expire, not an estimate of the time a Batch will take or a commitment to finish it. A longer Completion Window gives a Batch more time and does not change its price (Section 6.20).

6.18

Lines that expire. When the Completion Window of a Batch closes, every line of it that has not finished expires. HIPS delivers every finished line in the output file and charges it, and reports each expired line in the error file as expired. An expired line is not charged, and its hold is released (Section 6.21); you may submit it again, in a new Batch or as a Request, at the rates that apply then. The time a Batch takes within its Completion Window, and the expiry of its unfinished lines, are characteristics of Batches that form part of the description of the Services (Common Clauses Section 4.1); they are not a failure to perform the Services, and HIPS owes nothing for them beyond not charging the expired lines. If you are a Consumer, HIPS asks you to accept these characteristics expressly under Section 27.3(e), and Common Clauses Section 4.4 applies.

6.19

Canceling a Batch. You may cancel a Batch at any time before it ends. HIPS then starts no further line of it. A line that is already running when the cancellation takes effect may finish. Every line that finishes is delivered in the output file and charged; every other line is not run and not charged, and HIPS releases its hold (Section 6.21).

6.20

The batch price. HIPS charges each finished Batch Line at the Batch Rates: the on-demand rates of the Price List for the same model, pool and unit, reduced by fifty percent (50%). The reduction applies to every rate a Batch Line uses, including input, Cached Input Tokens (Section 9.10), output and every task unit, and it is the same for every Completion Window. HIPS shows the Batch Rates before you submit a Batch. The Batch Rates in effect when HIPS accepts a Batch, for each pool in which the Batch's requirements allow its lines to run, bind for every line of that Batch until the Batch ends, whatever later change is made to the Price List (Section 9.8), and each line is charged at the Batch Rate of the pool that ran it, but never at more than the lowest Batch Rate among the pools in which the Batch's requirements allow its lines to run. HIPS offers Batches only for the models that its catalog lists as available for Batches, always at the full reduction of this Section.

6.21

The held maximum. When HIPS has validated a Batch, and before any line of it runs, HIPS holds against the Credits of the Workspace the most that the Batch can cost: the input of every line, charged as input that is not cached, and the most output or other units each line can be charged (the limit the line sets or, if it sets none, the model's limit), each at the highest Batch Rate that Section 6.20 allows HIPS to charge for the line. If the Credits available in the Workspace cannot carry that maximum charge, the Batch ends as failed for insufficient Credits, and nothing is held or charged. Held Credits remain the Workspace's Credits, but they cannot be used for anything else while they are held, and they do not count as available Credits for Section 8.4. As each line finishes, HIPS charges it against the Credits held for the Batch, in the order of Section 8.3, and releases the rest of that line's hold; as each line expires, is canceled or is refused, HIPS releases its hold without charge; and when the Batch ends, HIPS releases whatever remains held. Credits held for a Batch do not expire while they are held: where held Credits reach their expiry date before the Batch ends, any part of them not charged when the Batch ends expires thirty (30) days after the Batch ends (Section 8.5). This extension departs from Common Clauses Section 3.7, as Common Clauses Section 1.3 allows.

6.22

Batch Files: retention and deletion. HIPS stores the input file you upload for a Batch, and the output file and error file it produces, to run the Batch and deliver its results. HIPS keeps each Batch File for thirty (30) days after it is uploaded or produced and then deletes it, except as this Section provides for the input file of an open Batch, unless it deletes it sooner:

  1. (a)at the end of a shorter period that you set for the file when you upload it or create the Batch; or
  2. (b)when you delete it.

The content of a Batch follows the Request-Data Policy of the Workspace as the content of any other Request does (Section 13). Deleting a Batch File, or its expiry, does not delete a training copy made from it under Section 13.8(a), which Section 13.11 governs, or content HIPS keeps under Section 13.8(d), (f) or (g). HIPS does not delete the input file of an open Batch because its thirty (30) days have ended: where the thirty (30) days of an input file end before a Batch that uses it ends, HIPS deletes the file when that Batch ends. If you delete the input file of an open Batch, or a shorter period you set for it ends while the Batch is open, HIPS may cancel the Batch with the effects of Section 6.19. HIPS keeps no Batch File for you beyond this Section, except as Section 13.8(g) provides, and you are responsible for downloading the results you need before they are deleted (Section 14.3).

6.23

When a Batch ends. A Batch ends when each of its lines has finished, expired, failed, been refused or been canceled, or when it ends as failed under Section 6.21. HIPS then makes its output file and error file available through the API and the Console, and tells you that the Batch has ended by email and, where you have registered an endpoint for the Workspace, by a webhook that HIPS signs so that you can check that it comes from HIPS. You shall check that signature before you act on a webhook. A notice that is late or does not arrive does not change the Batch, its results or its charges, and the status of the Batch that the API reports governs. How a line that fails is charged is governed by Section 9.5.

6.24

How Batch Lines run. Batch Lines run on the same supply, and under the same rules, as other Requests. The pool, region and fallback requirements of a Batch apply to every line and every retry of it (Section 6.4); a Batch Line may run in the Personal Pool or the Approved Pool as those requirements allow, under the conditions Section 17 describes; and a Batch Line for a Customer Model runs only where Section 15.8 allows. HIPS gives interactive Requests priority over Batch Lines, may pause a Batch between lines to serve them, and may group lines that begin with the same content and run them in order on one worker. Section 13.4 applies to a Batch as to a single Request: the Request-Data Policy in force when HIPS accepts the Batch applies to all its lines, subject to a Consumer's objection under Section 13.2(b).

6.25

Batches of a paused or closed Workspace. If HIPS pauses, suspends, freezes or closes a Workspace under Section 12.4 or Section 24, or your Agreement ends, HIPS may cancel the open Batches of the Workspace, with the effects of Section 6.19. A pause of a Workspace only because its available balance has reached zero (Section 8.4) does not cancel a Batch whose maximum charge is held under Section 6.21.

Section 06
  1. 6.1Your right to use the Services
  2. 6.2What the Services comprise
  3. 6.3Workspaces
  4. 6.4Pools and lanes
  5. 6.5Models and versions
  6. 6.6Retirement of Catalog Models
  7. 6.7Limits
  8. 6.8Regions
  9. 6.9Capacity is not reserved
  10. 6.10No machine access
  11. 6.11HIPS may refuse a Request
  12. 6.12Changes to the Services
  13. 6.13Beta features
  14. 6.14Where the Services are
  15. 6.15Batches
  16. 6.16Batch limits
  17. 6.17The Completion Window, and no completion time
  18. 6.18Lines that expire
  19. 6.19Canceling a Batch
  20. 6.20The batch price
  21. 6.21The held maximum
  22. 6.22Batch Files: retention and deletion
  23. 6.23When a Batch ends
  24. 6.24How Batch Lines run
  25. 6.25Batches of a paused or closed Workspace
Copy link

07Plans

7.1

The Plans. HIPS offers three Plans, once it releases paid access (Section 1.6), called in these Terms the Free/PAYG Plan, the lower paid Plan and the higher paid Plan, each under the public name that the Price List gives it. At launch, the Price List sets their fees as follows: the Free/PAYG Plan has no Plan fee; the lower paid Plan costs twenty United States dollars (US$20) a month and includes twenty-five United States dollars (US$25) of Included Credits each month; and the higher paid Plan costs two hundred United States dollars (US$200) a month and includes two hundred fifty United States dollars (US$250) of Included Credits each month. The Price List governs these amounts; HIPS may change them, and a change applies to an existing subscription only as Sections 7.2 and 7.3 provide. As HIPS describes the Plans:

  1. (a)Free/PAYG: no Plan fee and no Included Credits; you pay for your usage with Purchased Credits, which you top up by card, or by a Machine Payment (Section 10.11), in every country where HIPS sells, and no Plan, top-up of Credits or other part of the Services is ever payable in a Crypto-Asset (Common Clauses Section 3.11(i));
  2. (b)lower paid Plan: "A monthly subscription with included credits, intended better rates, and higher limits." "Region selection is not included."; and
  3. (c)higher paid Plan: "A monthly subscription with included credits and additional organization features." "Request-data training is off by default. Region selection and SSO are intended features."
7.2

The Plan terms. The fee, Included Credits, rates, limits and reset dates of each Plan are those of the Price List when you subscribe, read with this Section 7. HIPS grants the Included Credits of a paid Plan for each billing period, once the Plan fee for that period is paid; they are used at the rates of the Price List and expire at the end of the billing period for which they are granted, with no rollover, and that expiry does not affect your Purchased Credits (Section 8.5). HIPS changes the fee, the Included Credits or the limits of a paid Plan for an existing subscription only from a renewal after the notice of Section 7.3. HIPS sells no paid Plan before it publishes its terms, and it makes the region selection and single sign-on of the higher paid Plan available before it sells that Plan with them.

7.3

Subscriptions and renewal. A paid Plan is a monthly subscription. It renews automatically at the end of each period, and HIPS charges the Plan fee to the card saved for the subscription, until you cancel. If a renewal payment fails, HIPS's payment processor retries it up to eight (8) times within fourteen (14) days after the renewal date, no Included Credits are granted for the period until it is paid, and the subscription lapses after the final failure. HIPS gives at least thirty (30) days' notice on a Durable Medium before a change to the fee of your paid Plan applies. The change applies only from the first renewal after the notice period ends, and you may cancel before that renewal.

7.4

Cancellation and changes of Plan. You may cancel a paid Plan at any time in the Console, effective at the end of the current period. Your Purchased Credits stay in the Workspace, and the Included Credits of the period expire at its end. An upgrade takes effect at once: HIPS charges the difference between the two Plan fees for the rest of the current period, in proportion to the time left, and grants the Included Credits of the new Plan in the same proportion. A downgrade takes effect at the end of the current period. A Workspace cannot downgrade while it holds Always-On Capacity or a region requirement that the new Plan does not carry. Except as Section 12.1 provides, a Plan fee paid for a period is not refunded when you cancel during that period.

7.5

The Free Allowance. HIPS grants no Free Allowance at launch. If HIPS grants a Free Allowance, the Price List states it, with its amount, its reset date and whether unused amounts roll over, the Console shows them before the allowance is granted, and the rest of this Section applies to it. Each verified person receives one monthly Free Allowance, attached to the first Workspace that person owns, on the Plans the Price List names: one person, one allowance, however many Workspaces the person creates. It is granted only after the person passes identity verification. The Free Allowance is a benefit of the Plan, not a payment and not a balance you own; it carries no VAT and is never refunded. Wherever HIPS presents the Free Allowance, on its website, in the Console, in its emails and in its advertising, it states clearly beside it, at the outset, that the allowance is granted only to a person who has passed identity verification, which always includes a face check, by the automated face check with explicit consent or by the face check by a person (Sections 4.8 and 4.9), that each person receives one allowance, and that on the Free/PAYG Plan Inputs and Outputs may be used for Training, for a Consumer on the basis of HIPS's legitimate interest unless they object with one switch (a right HIPS presents separately from any other information), which keeps the Free Allowance, and, for a Consumer in the United States, only if the Consumer turns Training on (Sections 13.1 and 13.2).

7.6

No Crypto-Asset benefits. HIPS offers no benefit for holding MTO or any other Crypto-Asset, and connects no wallet (Common Clauses Section 3.11(a)). HIPS does not issue, sell or offer MTO or any other Crypto-Asset (Common Clauses Section 3.11(d)). HIPS does not encourage, invite, recommend or advise you to acquire, hold, sell or trade MTO or any other Crypto-Asset, for any reason; HIPS makes no statement or promise about the value, price, liquidity, availability or future of MTO; and nothing in the Services is an offer of MTO or investment, financial, legal or tax advice (Common Clauses Section 3.12).

Important: MTO and every other crypto-asset carry extreme risk

Common Clauses Section 3.12 provides, with items (b) to (d) of its list run together: "(b) whether you acquire, hold, sell or trade MTO or any other Crypto-Asset is your own decision alone, made at your own risk; (c) Crypto-Assets carry extreme risk, including the total loss of their value, sharp and sudden changes in their price, being unable to sell them, and technical, regulatory and counterparty risks, such as the failure of a blockchain network, a wallet, an issuer or a service provider, the loss of access to a wallet, and changes in the law that applies to them; (d) before you acquire, hold, sell or trade a Crypto-Asset, you should take advice from your own independent financial, legal and tax advisors"

7.7

Lapse of a paid Plan. A lapse never changes the Request-Data Policy of a Workspace silently. When the higher paid Plan lapses, the Workspace keeps its policies and is paused for inference until its Owner either acknowledges the Request-Data Policy of the Free/PAYG Plan or pays. When the lower paid Plan lapses, no policy changes; the Workspace loses the limits and rates of that Plan.

Section 07
  1. 7.1The Plans
  2. 7.2The Plan terms
  3. 7.3Subscriptions and renewal
  4. 7.4Cancellation and changes of Plan
  5. 7.5The Free Allowance
  6. 7.6No Crypto-Asset benefits
  7. 7.7Lapse of a paid Plan
Copy link

08Credits

8.1

What Credits are. Credits are a balance in United States dollars that a Workspace holds as a prepayment for the Services. They are different from model usage units and different from MTO. Common Clauses Section 3.7 governs their nature: they are not money, electronic money, a deposit, a Crypto-Asset, a security, property or currency; they can be used only to pay HIPS for the Services; they earn no interest; and they are not redeemable for cash except where the Agreement or Applicable Law requires a refund.

Important: Purchased Credits expire

Common Clauses Section 3.7 provides: "Purchased Credits expire twelve (12) months after the date on which they are purchased." Section 8.5 sets out when the other kinds of Credits expire and how HIPS reminds you before Purchased Credits expire, and Section 6.21 extends the expiry of Credits held for a Batch.

8.2

Kinds of Credits. A Workspace may hold the Free Allowance, Included Credits, Purchased Credits and Promotional Credits. Each grant is recorded as a separate lot with its own amount and expiry date, and the Console shows the balance of each kind with each lot's expiry.

8.3

Order of use. HIPS charges usage against the lot with the soonest expiry first and, between lots with the same expiry, the lot granted first. In this way the Free Allowance and Included Credits are generally used before Purchased Credits.

8.4

Using Credits. HIPS charges each Request, each hour of Always-On Capacity and every other charged Service against Credits at the price that applies under Section 9. HIPS refuses a Request whose estimated charge exceeds the Credits available in the Workspace. HIPS may reserve the estimated maximum charge of a Request when it accepts it, and it releases the unused part when the Request completes; for a Batch, HIPS holds its maximum charge as Section 6.21 provides. When the balance of a Workspace reaches zero, HIPS pauses the Workspace and, after a warning period of one (1) hour, which starts when HIPS tells the Owner and the Billing Members that the balance has reached zero, stops its Always-On Capacity; the Always-On Capacity is charged until it stops.

8.5

Expiry. Purchased Credits expire twelve (12) months after the date on which they are purchased. Credits of every kind that are held for a Batch when they would expire expire only as Section 6.21 provides. Included Credits expire at the end of the billing period for which they are granted, with no rollover, and a Free Allowance, if HIPS grants one, at its monthly reset, unless the Price List provides for its rollover; the expiry of Included Credits does not affect Purchased Credits. Promotional Credits expire on the date stated when they are granted. HIPS tells the Owner and the Billing Members on a Durable Medium at least thirty (30) days before Purchased Credits expire, and when they expire. Expired Credits cannot be used, and neither they nor the tax charged when they were bought are refunded, except as Section 27.12 provides for Consumers. A change to these Terms does not shorten the expiry of Credits bought before it (Common Clauses Section 9.6(c)).

8.6

No transfer and no cash. Credits belong to the Workspace that holds them. They cannot be transferred to another Workspace or person, sold, pledged, or used to pay anyone but HIPS, including a Provider. For the purposes of Common Clauses Section 3.7, these Terms allow no transfer of Credits. Credits are not redeemable for cash, except that HIPS refunds Purchased Credits where these Terms (Sections 9.8, 12.1, 24.6, 24.7, 27.6, 27.8, 27.12 and 28.4), Common Clauses Sections 7.10, 8.5 and 9.4, or Applicable Law require it. If you are also a Provider, HIPS may apply the unused Purchased Credits of a Workspace of which you are the Buyer to a debit balance of your Netting Account under the Provider Agreement, as Provider Agreement Section 13.3(b) provides; this departs from Common Clauses Section 3.7, as Common Clauses Section 1.3 allows.

8.7

Promotional Credits. HIPS grants Promotional Credits at its discretion and on the conditions it states when it grants them; unless those conditions say otherwise, one grant of a promotion is available per verified person. Promotional Credits are never refunded. HIPS may withdraw unused Promotional Credits that were obtained in breach of these Terms or of the promotion's conditions, through more than one identity, or with a payment that was later reversed or refunded. Section 8.10 governs the Referral Discount.

8.8

Negative balance. If charges, a refund or a reversed payment take the balance of a Workspace below zero, the amount below zero is a debt you owe HIPS, due when HIPS gives you notice of it. HIPS deducts it from the next Credits added to the Workspace and may ask you to pay it within fourteen (14) days of its notice.

  1. (a)Business Users, including US Users who are Business Users. After that notice, HIPS may charge the debt to a card saved to the Workspace.
  2. (b)Consumers, including US Users who are Consumers. HIPS charges a saved card for the debt only with your authorization for that charge.

If the Buyer of the Workspace holds another Workspace, HIPS may, if the debt is not paid within the period of its notice, apply the unused Purchased Credits of that other Workspace to the debt; if you are a Consumer, only with your authorization for that application. This departs from Common Clauses Section 3.7, as Common Clauses Section 1.3 allows. If you are also a Provider, HIPS may also recover the debt as the Provider Agreement provides. Section 10.9 applies to an amount not paid when due.

8.9

Blocked Credits. While a payment for a Workspace is disputed (Section 12.4), and while HIPS investigates under Section 24.2 a payment it has reasonable grounds to suspect is fraudulent, HIPS may block the use of the Credits that payment bought; a freeze under Section 12.4 blocks the use of all the Workspace's Credits. Blocked Credits are not lost: HIPS releases them when the ground ends, or applies them under Section 12.5 or Section 24.6.

8.10

The Referral Discount. While the Affiliate Program is open, a Workspace that is the subject of a Referral, or whose first top-up uses a Program Partner's Referral Code, may receive a discount on its first top-up, on the conditions HIPS shows before you pay, including the amount of the discount and the minimum top-up to which it applies, as the Affiliate Program Agreement states them: a discount of ten United States dollars (USD 10) on a first top-up of at least fifty United States dollars (USD 50) before the discount (Affiliate Program Agreement Section 24.1). Each of the following is a separate provision:

  1. (a)you pay the price of the top-up less the Referral Discount and receive Credits for the full amount of the top-up: the part you paid as Purchased Credits, and the Referral Discount as Promotional Credits;
  2. (b)only a Workspace that has never paid HIPS can receive a Referral Discount, and only one Referral Discount is available for each verified person and for each payment card; none is available to a person who is already a Member of a Workspace that has paid HIPS, or for a top-up of a Workspace of which the Program Partner concerned is a Member;
  3. (c)if the payment for that top-up is refunded, disputed or reversed, in whole or in part, HIPS removes the Credits it covers in proportion, taking them first from the Promotional Credits of the Referral Discount, and Sections 8.8, 12.1 and 12.5 apply to the rest;
  4. (d)a Referral Discount is never paid in cash, and HIPS may withdraw it under Section 8.7, and refuse or reverse it where the Referral breaches the Acceptable Use Policy or the Affiliate Program Agreement, including a Referral of yourself or of a person acting with you; and
  5. (e)if you are referred, the Program Partner sees your Referral in the Console only within totals: for each role (Buyer or Provider), the number of its Referrals that are pending, qualified, not qualified and reversed, and its Commissions as totals for each role and period, combined across periods so that each total covers at least five (5) of its Referrals, or any larger number that the Affiliate Program Agreement states. Until a role has at least that number of Referrals, Refer and earn shows for it only the number of its Referrals, with no count by state and no Commission total, and the statements of the Program Partner's payouts show only the total of each payout across all roles. Refer and earn also shows the Program Partner whether it is eligible and, once it has at least that number of Referrals across all roles, how many of its Referrals that have qualified count toward its eligibility. It never sees your Referral listed on its own, or its dates, its state or its amounts. Each payout pays Commissions from at least that number of Referrals, so it does not show what one Referral earned, except a last payout when the Program Partner leaves the Affiliate Program or it closes, a payout of an amount that has waited the longest period the Affiliate Program Agreement allows, and a payout that follows the end of a hold, a dispute or a complaint (Affiliate Program Agreement Sections 5.8, 10.3, 11.5, 13.4, 18.6 and 19.11(a)); such a payout to a Program Partner with few Referrals can show approximately what one Referral earned, and so, from the Commission rate, roughly what you paid HIPS or HIPS paid you. Where HIPS must identify your Referral to the Program Partner in a statement of reasons, a notice of forfeiture or a Dispute, HIPS does so only by a reference that HIPS assigns and, where the reason lies in your payments, refunds, payment disputes or Earnings, only with the reason category "a condition of the Program was not met" (Affiliate Program Agreement Section 5.8). A change in those totals can show a Program Partner who knows you that you have made a first qualifying top-up. HIPS never tells the Program Partner your name, your email address, your Workspace, your provider account or your Devices, or what you paid or were paid, except where Applicable Law requires it. If you object to the processing of your data for the Affiliate Program, or have it erased, HIPS stops attributing amounts to your Referral from then on (Affiliate Program Agreement Section 5.9); this does not affect a Referral Discount you have already received. Privacy Notice Section 3.8 describes this processing.
Section 08
  1. 8.1What Credits are
  2. 8.2Kinds of Credits
  3. 8.3Order of use
  4. 8.4Using Credits
  5. 8.5Expiry
  6. 8.6No transfer and no cash
  7. 8.7Promotional Credits
  8. 8.8Negative balance
  9. 8.9Blocked Credits
  10. 8.10The Referral Discount
Copy link

09Prices and charges

9.1

Prices. These Terms set no prices, except the reduction for Batches in Section 6.20; the Plan fees that Section 7.1 states are those of the Price List at launch. The price of a Request is the rate of the Price List, or the stable price, that applies to it under Section 9.2 or Section 9.3, and the price of a Batch Line is the Batch Rate that binds under Section 6.20. HIPS shows the current rates in the Console and on its pricing page before you send a Request.

9.2

Market pricing. Market pricing reflects changing supply and demand, and the rates of the Price List can rise as well as fall, at any time. Unless a Batch Rate (Section 6.20), a stable price (Section 9.3) or an explicit quote under this Section applies, the price of a Request is the rate of the Price List published when HIPS accepts the Request, and it binds for that Request and every retry of it; a rate published after HIPS accepts a Request never applies to it. HIPS publishes on its pricing page when its prices were last updated and a history of each rate, for information only: neither is an offer, a quote or a promise of any future price, and a past rate gives no right to be charged it. An explicit quote that HIPS shows before work, such as the quote for an allocation of Always-On Capacity, states the period for which it is valid and binds if HIPS accepts the work within that period; HIPS refuses work that refers to an expired quote, and the work must be quoted again.

9.3

Stable prices. "A stable-price option will give customers another way to plan their spend." A stable price fixes a rate for a stated period, workload, model, pool and region. It is a price commitment, not a capacity commitment. A stable rate changes only at the boundary of a period. Before you buy a stable price, HIPS states its period, the workload it covers, who may buy it and the notice HIPS gives of a change of its rate for a later period, and none of these changes during a period you have bought.

9.4

Billing units. Usage is measured in the unit of each model type, such as tokens, classifications, images, seconds, minutes or characters, and Always-On Capacity is measured in hours. Input tokens are measured as Cached Input Tokens (Section 9.10) and as input tokens that are not cached. A streamed response that completes is charged for the tokens delivered; how a canceled or interrupted stream is charged is set under Section 9.5.

9.5

Retries, interruptions and cancellations. HIPS may retry an attempt on other eligible supply within the rules of Section 6.4. Each of the following is a separate provision:

  1. (a)HIPS charges a Request once, for the Output it delivers, at the price bound under Section 9.2 or 9.3, however many attempts it took;
  2. (b)an attempt that is retried, rejected, interrupted, fails or times out is never charged to you;
  3. (c)a Request that ends without a completed Output is not charged, except as item (d) provides;
  4. (d)a streamed Request that you cancel, or from which your client disconnects, after Output has begun to be delivered, is charged for the units delivered; a Request that HIPS cannot complete is not charged;
  5. (e)a Request that you send again is a new Request with its own price; and
  6. (f)what HIPS pays a Provider for an attempt is never charged to you.
9.6

Always-On Capacity. The hourly charge covers allocated capacity, including time between Requests. It runs from the moment the allocation is granted, through loading and idle time, until a stop takes effect. The Console shows this before you confirm an allocation. If the supplier of the capacity interrupts the allocation, the charge stops. HIPS charges nothing for the Requests an allocation serves in addition to the hourly charge, unless the Price List states such a charge and the Console shows it before you confirm the allocation.

9.7

Customer Model charges. HIPS charges nothing for importing a Customer Model or for keeping HIPS's copy of it until HIPS publishes terms for those charges, and those terms apply only after notice under Common Clauses Section 9.2.

9.8

Price changes. HIPS may change the rates of the Price List for Requests it accepts after the change. A change does not affect a Request already accepted, the Batch Rates of a Batch already accepted (Section 6.20), a quote within its validity, a stable price within its period, or a Plan fee before the renewal Section 7.3 describes. Credits are a balance in US dollars, so a change of rates changes what a balance buys. For a Catalog Model whose rates the Price List publishes, the rate is the published rate of its model, pool and unit, which changes only when HIPS publishes a new rate; for other work, the Price List describes how market rates are set, including the inputs that move them and any ceiling that applies. If you are a Consumer and the rates for a model you used in the previous ninety (90) days rise by more than twenty percent (20%) within thirty (30) days, HIPS tells you on a Durable Medium, and you may, within thirty (30) days after that notice, have your unused Purchased Credits refunded under Section 12.1.

9.9

Prompt caching. The engines that run Requests may keep in memory the state they computed for the beginning of an Input after the Request ends, and use it again for a later Request whose Input begins with the same content (a prompt cache); on a data-center worker a prompt cache is held only in the memory of the worker's GPUs and host, and never on its disk. Each of the following is a separate provision:

  1. (a)prompt caching is automatic: you do not need to turn it on, and HIPS charges nothing for making a cache. You may turn it off for a Workspace in the Console, with the switch "Prompt caching on data-center workers" in the Workspace's settings, which an Owner or admin may use, and HIPS then keeps no prompt cache and records no Prefix Ledger for that Workspace, and charges it no Cached Input Token. 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 its Owner or an admin asks it to in writing at the privacy contact address in Section 30, as DPA Section 14.2 provides for a Business User;
  2. (b)HIPS keeps prompt caches apart for each Workspace: a cache made from the Requests of one Workspace is never used for a Request of another Workspace. In a Workspace held by a Consumer, HIPS also keeps apart by default the caches of each Member, with the Authorized Tools that act as them, and of each API Key, and the Owner may let them share one with the switch "Members and keys share one prompt cache" in the Workspace's settings, which is off by default. Otherwise, within a Workspace, a Request may use a cache made from any other Request of the same Workspace, whichever Member, API Key or Authorized Tool sent it, unless you narrow it with a cache key in your Requests, so a Member could tell from the speed of an answer whether another Request of the same Workspace began with the same text; you can prevent this by setting a separate cache key for each Member, API Key or Authorized Tool. HIPS sets the value that keeps Workspaces apart itself, and refuses a Request that tries to set it;
  3. (c)HIPS uses a prompt cache only to answer later Requests of the same Workspace, and may prefer to send a Request to a worker that holds a cache of its Workspace, but never against the Request's requirements (Section 6.4);
  4. (d)HIPS promises no lifetime for a prompt cache, within the maximum of item (g), no use of a cache for any Request and no saving: whether a Request uses a cache depends on where it runs, on load and on what the engine still holds;
  5. (e)at launch, Devices in the Personal Pool run with their prompt cache between Requests turned off. HIPS turns on a prompt cache on Devices only in memory, never on disk, and only after it has published the change in the protections of the Personal Pool (Section 17.5) and given notice of it under Common Clauses Section 9.2;
  6. (f)Section 17 applies to the state held in a prompt cache as it applies to Request Data; and
  7. (g)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 (item (b)), 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.
9.10

Cached Input Tokens. An input token that HIPS charges as read from a prompt cache is a Cached Input Token, and is charged at the cached-input rate of the model, which the Price List sets for each model, pool and pricing mode. Each of the following is a separate provision:

  1. (a)HIPS charges an input token as a Cached Input Token only where it can verify that the token was read from a prompt cache made from Requests of the same Workspace, and charges every other input token at the input rate. HIPS never deletes a Prefix Ledger record while the cache it stands for can still be read;
  2. (b)where the Price List sets no cached-input rate for a model in a pool, every input token is charged at the input rate; and because Devices run with their prompt cache off at launch (Section 9.9(e)), no Request served in the Personal Pool is charged a Cached Input Token at launch;
  3. (c)in a Batch, Cached Input Tokens are charged at the cached-input rate reduced as Section 6.20 provides, so that the two reductions multiply; and
  4. (d)Cached Input Tokens count toward the token limits of your Plan, and the usage record of each Request shows them apart from the other input tokens.
Section 09
  1. 9.1Prices
  2. 9.2Market pricing
  3. 9.3Stable prices
  4. 9.4Billing units
  5. 9.5Retries, interruptions and cancellations
  6. 9.6Always-On Capacity
  7. 9.7Customer Model charges
  8. 9.8Price changes
  9. 9.9Prompt caching
  10. 9.10Cached Input Tokens
Copy link

10Payment

10.1

You pay HIPS. HIPS is the merchant of record for every payment for the Services (Common Clauses Section 3.3). HIPS trades as HIPS, and your card statement shows HIPS as the merchant for every payment you make to it. You pay HIPS and only HIPS. No part of your payment is paid to or for a Provider, and HIPS does not collect or hold money for anyone (Common Clauses Sections 3.4 and 3.5).

10.2

Payment methods by Country. The payment methods available to a Workspace depend on the Country of the Buyer, as the table below shows.

TablePayment methods by Country
Country of the BuyerPayment methods
The United StatesCard, including Machine Payments (Section 10.11), on every Plan, including top-ups on the Free/PAYG Plan; never MTO in any form, and no other Crypto-Asset
Every other country where HIPS sellsCard, including Machine Payments (Section 10.11), on every Plan, including top-ups on the Free/PAYG Plan; no Crypto-Asset
A Restricted JurisdictionNone
10.3

Whose Country decides. A Buyer's Country is determined as Common Clauses Section 2.1 defines it. A payment method is offered for a Workspace only where it is available both in the Country of the Buyer and in the Country of the Billing Member who pays. If your Country changes, the methods of your new Country apply from your next payment, and a period you have already paid runs to its end.

10.4

Card payments. Card payments and card subscriptions are processed by Stripe. HIPS does not receive or store your full card number. You authorize HIPS, through Stripe, to charge the card you use for each payment you approve, for each renewal of a subscription you started, for automatic reload once you turn it on, for each Machine Payment made under Section 10.11, and as Section 8.8 provides. HIPS or its payment processor may require additional authentication of a payment, and may refuse a payment it has reasonable grounds to suspect is unauthorized or fraudulent.

10.5

No Crypto-Asset payments. HIPS accepts no payment in MTO, USDC or any other Crypto-Asset, in any country, and never holds a Crypto-Asset for you or for anyone else (Common Clauses Section 3.11). HIPS offers a Crypto-Asset payment only after amending these Terms and the Common Clauses under Common Clauses Section 9. Common Clauses Section 3.12 applies: HIPS does not encourage, invite, recommend or advise you to acquire, hold, sell or trade MTO or any other Crypto-Asset.

10.6

Automatic reload. Automatic reload of Credits is off by default and turns on only by your choice; a saved card alone never turns it on. Once you turn it on, HIPS charges your saved card under the settings you choose without further action from you. HIPS turns automatic reload off after repeated failed charges and during a freeze under Section 12.4.

10.7

Changing or ending a payment method or benefit. HIPS may change, suspend or end any payment method, Machine Payments included, for everyone or in a country, for a reason listed in Common Clauses Section 9.1, with notice under Common Clauses Section 9.2, or with immediate effect where Applicable Law, a competent authority, a card network or a payment processor requires it; if you are a Consumer, Section 27.8 also applies. Credits already granted are not affected.

10.8

Receipts, invoices and records. HIPS issues a receipt for every payment, which you can download, and an invoice where Section 11.9 requires one. Invoiced billing with later payment is not offered at launch. HIPS keeps an append-only ledger of Credits and charges: a correction is made by a new entry, never by editing an earlier one. Common Clauses Section 17.4 governs the effect of HIPS's records.

10.9

Late payment. An amount you owe HIPS that is not paid when due bears late interest at the rate Applicable Law provides. If you are a Business User, HIPS may also claim the compensation for recovery costs that Applicable Law provides. HIPS may take measures under Section 24.2 for an amount not paid when due.

  1. (a)Business Users, including US Users who are Business Users. You shall also pay HIPS's reasonable costs of collecting an amount unpaid when due, including the fees of a collection agency and reasonable lawyers' fees, to the extent Applicable Law allows.
10.10

Questions about a charge. If you believe a charge is wrong, tell HIPS within sixty (60) days after the receipt or the usage record that shows it. HIPS reviews it, tells you the outcome and corrects any error by a ledger entry.

  1. (a)Business Users, including US Users who are Business Users. A charge you do not question within that period is final, except for an error that results from HIPS's fraud, intentional breach or gross negligence. This Section 10.10(a) departs from Common Clauses Section 17.4, as Common Clauses Section 1.3 allows.
  2. (b)Consumers, including US Users who are Consumers. The period is a request to help HIPS correct errors quickly; it does not limit any right Applicable Law gives you.
10.11

Machine payments. Once HIPS releases this feature (Section 1.6), an agent, such as an AI agent or another program, that sends Requests with an API Key of your Workspace may pay HIPS for the Workspace by a Machine Payment: through Stripe's Machine Payments Protocol, with a card through a Shared Payment Token, when a Request asks for payment or as a top-up. Each of the following is a separate provision:

  1. (a)When they are available. Machine Payments are off by default. They are available only for a Workspace whose Owner has passed identity verification and whose Owner or an admin has turned them on in the Console and set the amount a payment request asks for and the largest top-up an agent may make, neither below the smallest card payment that Stripe accepts through a Shared Payment Token (fifty United States cents (US$0.50) on 2026-10-26), which the Price List states, and both within the top-up limits of the Price List. Every Machine Payment is made with a valid API Key of the Workspace and under the Workspace's settings, policies and limits; HIPS accepts no Machine Payment without an API Key and no anonymous Machine Payment.
  2. (b)Your standing acceptance. When the Owner or an admin turns Machine Payments on, they accept for the Buyer this Section 10.11 for every Machine Payment made while Machine Payments stay on, and HIPS records that acceptance with its time, the person who gave it and the version of the text shown to them. Machine Payments stay on until the Owner or an admin turns them off, which takes effect for every Machine Payment that HIPS has not yet confirmed.
  3. (c)The agent acts for you. An agent that makes a Machine Payment acts for the Buyer, never for HIPS. The Buyer authorizes every Machine Payment made with the credentials of its Workspace and within its settings, and is responsible and liable for it as for a payment it made itself, as Section 5.4 provides for Requests, subject, if you are a Consumer, to Section 5.4(b); HIPS may rely on a Machine Payment made with a valid API Key of the Workspace and within the Workspace's settings as authorized by the Buyer. HIPS is not responsible for the instructions, errors, purchases or spending of an agent within the settings and limits of the Workspace, which the Buyer sets and controls.
  4. (d)The card. A Shared Payment Token may carry a card of a person other than the Buyer only with that person's authority. The Buyer warrants that every card that an agent of its Workspace uses through a Shared Payment Token is used with the authority of its holder. If the Buyer is a Business User, it indemnifies HIPS against every loss, cost, reversed payment, fee and Claim that arises because a card was used without that authority (Common Clauses Section 6.1); if the Buyer is a Consumer, Common Clauses Section 6.3 applies to that loss instead.
  5. (e)What a Machine Payment buys. A Machine Payment buys Purchased Credits for the Workspace for the amount paid, as a card top-up does, and is never a charge for a single Request. Every Request, the one whose payment request led to the Machine Payment included, is charged from the Workspace's Credits at its price under Section 9. The Purchased Credits a Machine Payment buys expire, and are refunded, as other Purchased Credits are (Sections 8.5 and 12.1).
  6. (f)Receipts and tax. HIPS issues a receipt for each Machine Payment, which the Billing Members of the Workspace can download, and charges and states the tax under Section 11 on the amount fixed before the payment, by the Country and status of the Buyer that holds the Workspace.
  7. (g)Consumers. If you are a Consumer, turning Machine Payments on is also your express request that HIPS make the Credits of each Machine Payment available at once, and your acknowledgment that you lose your right of withdrawal from the contract for those Credits once they have all been used, as Section 27.6 provides for a purchase of Purchased Credits; HIPS confirms that request and that acknowledgment on a Durable Medium when you turn Machine Payments on and with the receipt of each Machine Payment.
  8. (h)Refunds and disputes. Refunds, a Consumer's withdrawal and payment disputes of a Machine Payment are handled as for any card payment for Purchased Credits (Sections 12 and 27), and Section 12.4 applies to a disputed Machine Payment. HIPS may refuse, hold or reverse a Machine Payment that it has reasonable grounds to suspect is unauthorized or fraudulent, and may turn Machine Payments off for a Workspace under Section 24.2.
  9. (i)No stablecoins. HIPS accepts no Machine Payment in a Crypto-Asset, including through the stablecoin rails of the Machine Payments Protocol or of x402, and Section 10.5 applies.

Stripe processes Machine Payments under its own terms (Section 23.1), and HIPS receives the payment on its own Stripe account as the merchant of record (Section 10.1).

Section 10
  1. 10.1You pay HIPS
  2. 10.2Payment methods by Country
  3. 10.3Whose Country decides
  4. 10.4Card payments
  5. 10.5No Crypto-Asset payments
  6. 10.6Automatic reload
  7. 10.7Changing or ending a payment method or benefit
  8. 10.8Receipts, invoices and records
  9. 10.9Late payment
  10. 10.10Questions about a charge
  11. 10.11Machine payments
Copy link

11Taxes

11.1

Prices and taxes.

  1. (a)Business Users and US Users. Prices, Plan fees and top-up amounts are exclusive of value added tax, sales tax and similar taxes, whichever payment method you use, and HIPS adds the taxes it must charge at checkout.
  2. (b)Consumers. Where Applicable Law requires prices to be shown to you inclusive of taxes, as it does for EU Consumers, the prices HIPS shows you include the value added tax and the other taxes HIPS must charge, and the total shown at checkout is what you pay.
11.2

When tax is charged. HIPS charges value added tax and similar taxes on Purchased Credits and Plan fees when you pay for them, not when you use the Services. The Free Allowance and Promotional Credits carry no tax. Tax charged on Credits that later expire or are forfeited is not refunded, except as Section 27.12 provides for Consumers.

11.3

Business Users in the European Union. If you are a Business User established in a Member State of the European Union other than Ireland and you give HIPS your VAT identification number, HIPS checks its validity, together with the name and address associated with it, before it treats you as a taxable person. Once it has done so, HIPS charges no value added tax on your purchases, and its invoices state "Reverse charge applies": you account for the tax in your Member State. If you are a Business User established in Ireland, HIPS charges Irish value added tax at the rate in force. Until you have given HIPS a VAT identification number that HIPS has validated, HIPS treats you as a person who is not a taxable person for value added tax and charges the value added tax of your Member State, and it does not recalculate the tax on earlier payments except where Applicable Law requires. By giving HIPS a VAT identification number, you confirm that you buy the Services for the purposes of your business.

11.4

Your location. HIPS determines where you are established or live, for tax purposes, from your billing address, the network location of the device you use and the other evidence that Applicable Law allows. You shall give HIPS your true billing address and shall not disguise your location (Common Clauses Section 7.6).

11.5

Consumers in the European Union. If you are a Consumer whose Country is a Member State of the European Union, HIPS charges the value added tax of the Member State where you live, at that Member State's rate. HIPS is registered in Ireland for the Union One Stop Shop and has opted, under section 35A(4) of the Value-Added Tax Consolidation Act 2010, to tax its supplies to Consumers in other Member States in the Member State where each Consumer lives from its first such supply. If you live in Ireland, HIPS charges Irish value added tax. If you are a Consumer whose Country is Iceland, Liechtenstein or Norway, HIPS charges the value added tax of that state where its law requires HIPS to collect it.

11.6

Outside the European Union. If you are a Business User in the United Kingdom, in a state of the EEA that is not a Member State of the European Union, or in another country whose law applies a reverse charge to the Services, you account for the tax that applies to them where that law requires. HIPS charges any other tax that the law of your country requires it to collect, including United States sales and use tax where HIPS is required to collect it (Section 28.7). If you claim an exemption, you shall give HIPS a valid exemption certificate or equivalent document before you pay. In addition:

  1. (a)Japan. The Services are business-to-business electronic services (事業者向け電気通信利用役務の提供), which HIPS supplies in Japan only to Business Users (Section 3.4). 日本の消費税は役務の提供を受けた貴社が納税することとなります。日本の消費税のリバースチャージ方式の対象取引です。 Japanese consumption tax on the Services is payable by you, the Business User that receives them, under the reverse charge mechanism, as a specified taxable purchase, and HIPS charges you none. HIPS shows you this notice before you buy, in these Terms, on the Price List and at checkout;
  2. (b)Singapore and Australia. HIPS sells in Singapore only to Business Users registered for goods and services tax (GST), on the GST registration number they give HIPS, and in Australia only to Business Users that give HIPS their Australian Business Number (ABN) and state that they are registered for GST, in each case validated under Section 3.4. HIPS charges no GST on those purchases, and you account for any GST that the law of your country requires of you on them. You shall tell HIPS at once if your registration for GST ends, and HIPS may then suspend purchases for the Workspace under Section 11.8. HIPS relies on the number, the statement and the validation in deciding that no GST is due from it; if any of them is wrong, you shall pay HIPS, on its demand, any GST, interest and penalty that a tax authority assesses on HIPS for your purchases, with HIPS's reasonable costs of dealing with the assessment; and
  3. (c)The Republic of Korea and Taiwan. HIPS supplies the Services in the Republic of Korea only for the taxable or tax-exempt business of a person registered under Article 8 of the Value-Added Tax Act, Article 168(1) of the Income Tax Act or Article 111(1) of the Corporate Tax Act of the Republic of Korea, and in Taiwan only to business entities identified by a unified business number, in each case validated under Section 3.4. HIPS charges you no value added tax or business tax on those purchases, and you account for any tax that the law of your country requires of you as the purchaser, including in Taiwan under Article 36 of the Value-added and Non-value-added Business Tax Act.
11.7

Withholding: Business Users and US Users. If Applicable Law requires you to withhold tax from a payment to HIPS, you shall increase the payment so that HIPS receives the amount it would have received without the withholding, and give HIPS the receipt for the tax withheld.

11.8

Tax declarations: Business Users and US Users. You represent and warrant that the tax status, Country and VAT or tax identification number you give HIPS are accurate. If a tax authority assesses on HIPS a tax that HIPS did not charge you because your declaration was false, incomplete or out of date, HIPS may charge you that tax, and Common Clauses Section 6.1(f) applies to the tax, interest and penalties. If tax information HIPS needs to charge tax correctly is missing or invalid, HIPS may, after telling you and giving you a reasonable time to correct it, suspend purchases for the Workspace under Section 24.2(f) until it is corrected. If a tax authority assesses on HIPS a sales, use or similar tax on a sale to you that HIPS was required to collect from you and did not collect, HIPS may charge you that tax, within the period in which the authority may assess it, but not interest or penalties caused only by HIPS's own error.

11.9

Invoices. HIPS issues an invoice where tax law requires one, in United States dollars, with the taxable amount, the value added tax and the total also stated in euros, converted at the latest selling rate recorded by the Central Bank of Ireland or the European Central Bank when the tax becomes due, or by another method that the Revenue Commissioners have agreed with HIPS. HIPS issues invoices electronically and, where Applicable Law requires a structured electronic invoice, in that form. If you are a Consumer, HIPS gives you a receipt for each payment.

Section 11
  1. 11.1Prices and taxes
  2. 11.2When tax is charged
  3. 11.3Business Users in the European Union
  4. 11.4Your location
  5. 11.5Consumers in the European Union
  6. 11.6Outside the European Union
  7. 11.7Withholding: Business Users and US Users
  8. 11.8Tax declarations: Business Users and US Users
  9. 11.9Invoices
Copy link

12Refunds and payment disputes

12.1

When HIPS refunds. Payments for Purchased Credits and Plan fees are not refunded, except:

  1. (a)when a Consumer withdraws under Section 27.4;
  2. (b)when HIPS terminates without cause under Section 24.7, or at will under Section 28.4 other than for a ground in Section 24.2;
  3. (c)when you terminate because of a change under Common Clauses Section 9.4, because of a transfer under Common Clauses Section 11.3, or because of a change to the Services under Section 27.8;
  4. (d)when either party terminates for a prolonged force majeure event under Common Clauses Section 8.5, or HIPS ends your Agreement under Common Clauses Section 7.10;
  5. (e)on a closure for cause, to the extent Section 24.6 provides;
  6. (f)when a Consumer asks for a refund under Section 9.8 or Section 27.12;
  7. (g)when HIPS deletes a Workspace under Section 4.7(a) because its Business User named no Owner, once the Workspace is purged; and
  8. (h)where Applicable Law requires a refund.

A refund of Purchased Credits is the price you paid for the unused Purchased Credits, with the tax charged on that price. HIPS makes a refund to the payment method used for the payment and removes the Credits it covers, which may take the balance below zero under Section 8.8.

12.2

Charges for work not performed. If HIPS charges you for a Request or for Always-On Capacity that the Services did not perform as these Terms describe, HIPS credits the charge back to the Workspace as Credits when you raise it under Section 10.10.

  1. (a)Business Users and US Users. Subject to Common Clauses Section 5.1, that credit is HIPS's entire liability, and your only remedy, for the charge and the failure to perform the work charged. This Section 12.2(a) supplements Common Clauses Section 5, as Common Clauses Section 1.3 allows.
  2. (b)Consumers. The credit does not limit the remedies Applicable Law gives you when the Services are not in conformity (Common Clauses Section 4.4).
12.3

Contact HIPS first. If you question a card payment, contact HIPS before you dispute it with your card issuer, so that HIPS can resolve it.

  1. (a)Business Users, including US Users who are Business Users. You shall raise the question with HIPS and give HIPS fifteen (15) days to resolve it before you dispute the payment.
  2. (b)Consumers, including US Users who are Consumers. HIPS asks you to do so, but it is not a condition of any right you have.

Nothing in these Terms limits a right that the rules of your card network or Applicable Law give you to dispute a payment.

12.4

Important: what a payment dispute does to the Workspace

Payment disputes. If a card payment for a Workspace is disputed with the card issuer (an inquiry by the card issuer alone is not a dispute), HIPS may block the Credits that payment bought and refuse new purchases for the Workspace while the dispute is open. HIPS may also freeze the Workspace, with the effects below, if it has reasonable grounds to suspect fraud under Section 24.2(a) or, if you are a US User, whenever a payment for the Workspace is disputed:

  1. (a)its API Keys and the access tokens of Authorized Tools are refused for that Workspace;
  2. (b)the Console becomes read-only for the Workspace, except for its receipts;
  3. (c)its Always-On Capacity is stopped and its open checkout sessions are canceled;
  4. (d)its Credits are blocked, automatic reload and Machine Payments are turned off, and Credits added later do not lift the freeze;
  5. (e)its Owner and admins cannot create another Workspace while the freeze stands; and
  6. (f)if the Buyer that holds it is also a Provider, that Buyer's payouts may be held, up to the disputed amount and the fees the dispute may cost HIPS, as Provider Agreement Sections 11.1(c) and 11.2 provide.

HIPS lifts a measure under this Section 12.4, or takes a measure under Section 24.2, within ten (10) business days after the card issuer's final decision, and it lifts at once a measure that rests only on the dispute if the card issuer decides the dispute in your favor. Section 12.5(a) still applies to a payment that is reversed.

12.5

Consequences of a dispute. Each of the following is a separate provision:

  1. (a)if the disputed payment is reversed, HIPS removes the Credits that payment bought, including any part already used, which may take the balance below zero under Section 8.8;
  2. (b)if you are a Business User, including a US User who is a Business User, you shall reimburse HIPS for the dispute fees and the fees for declined or disputed transactions that its payment processor charges it, unless the dispute is decided in your favor because HIPS was at fault;
  3. (c)a payment that is reversed and that you do not pay again within the time HIPS gives you in its notice is an amount unpaid when due for the purposes of Section 24.2(d);
  4. (d)if you are a Business User, including a US User who is a Business User, a dispute of a payment that you did not first raise with HIPS as Section 12.3(a) requires, and that the card issuer decides in HIPS's favor, is a material breach of these Terms for the purposes of Section 24.2(b); a dispute that the card issuer decides in your favor is never a breach of these Terms; and
  5. (e)HIPS may give its payment processor and the card network the evidence of your purchase and use, including the acceptance records, receipts and usage metadata of the Workspace.
12.6

Crypto-Asset payments. HIPS accepts no Crypto-Asset payment (Section 10.5), so no refund, chargeback or dispute of one arises under these Terms, and HIPS makes no refund in a Crypto-Asset.

Section 12
  1. 12.1When HIPS refunds
  2. 12.2Charges for work not performed
  3. 12.3Contact HIPS first
  4. 12.4Payment disputes
  5. 12.5Consequences of a dispute
  6. 12.6Crypto-Asset payments
Copy link

13Request data

13.1

The policy follows the Plan. The Request-Data Policy of a Workspace depends on its Plan and, where the Buyer is a Consumer, on whether the Consumer has objected under Section 13.2(b), as the table below shows. It applies to Catalog Models and Customer Models, and to single Requests and Batches, alike.

TableRequest-Data Policy by Plan
PlanRequest-Data PolicyBusiness Users: can it be changed?Consumers: can it be changed?
Free/PAYG PlanInputs and Outputs may be used for TrainingNoYes: you may object at any time with one switch, and keep the Plan; in the United States, Training is off unless you turn it on (Section 13.2(b))
Lower paid PlanInputs and Outputs may be used for TrainingNoYes: you may object at any time with one switch, and keep the Plan; in the United States, Training is off unless you turn it on (Section 13.2(b))
Higher paid PlanTraining on Request Data is off by defaultYes: an Owner or admin may turn it on (Section 13.3)Yes: an Owner or admin may turn it on (Section 13.3)
13.2

Important: Training on the Free/PAYG Plan and the lower paid Plan

Training on the Free/PAYG Plan and the lower paid Plan. "On Free/PAYG and the lower paid plan, request inputs and generated outputs may be used for training. This includes requests processed by customer-owned models." How this applies depends on who you are:

  1. (a)Business Users, including US Users who are Business Users. The policy is the rule of your Plan and cannot be turned off on those Plans. On those Plans, the use of Request Data for Training as this Section 13 and Section 20.4 describe is part of what you give HIPS in exchange for the Services and is reflected in the price of the Plan; the higher paid Plan, on which Training is off by default (Section 13.3), is the Plan HIPS offers for Request Data you do not want used for Training. You may ask HIPS to exclude the contributions your Workspace has already made, as Section 13.11 provides, but not to stop Training on later Requests. If you do not want Request Data used for Training, do not send it from a Workspace on the Free/PAYG Plan or the lower paid Plan; on the higher paid Plan, Training is off by default (Section 13.3).
  2. (b)Consumers, including US Users who are Consumers. Except as the last sentence of this item provides for Consumers in the United States, HIPS uses your Request Data for Training on the basis of its legitimate interest in developing, fine-tuning and evaluating the models it operates and offers through the Services (Article 6(1)(f) of Regulation (EU) 2016/679, where that Regulation applies), which HIPS has weighed against your interests, rights and freedoms, and with the safeguards the Privacy Notice describes (HIPS recorded that assessment, made by the three steps that the European Data Protection Board recalls in its Opinion 28/2024, before it wrote the first training copy, reviews it at least every twelve (12) months and before any change in how it trains, and gives a summary of it on request, as Privacy Notice Section 6.10 describes). HIPS brings your right to object explicitly to your attention, clearly and separately from any other information, at the latest in its first communication with you after you create your Account, and in any case before your first Request. You may object at any time, without giving a reason, with one switch in the Console, and you keep your Plan, with any Free Allowance, its rates and its limits. From the moment HIPS records your objection, HIPS makes no training copy of the Request Data of the Workspaces you hold as a Consumer, and it excludes your earlier contributions as Section 13.11 describes. You may withdraw your objection with the same switch, and it then applies only to Requests HIPS accepts afterwards. HIPS does not rely on your acceptance of these Terms, or on your acceptance under Section 27.3, as consent to Training. If your Country is the United States, Training is off for the Workspaces you hold as a Consumer unless you turn it on: HIPS screens your Request Data for Training, and makes a training copy of it, only for Requests HIPS accepts after you have given in the Console a consent that is your own clear affirmative act, separate from your acceptance of these Terms and from every other choice, never preselected and never obtained through a design that impairs your choice, and that names Training and that screening, the categories of consumer health data the screening may process, its purpose and the specific ways HIPS uses that data for it, the categories of service providers that process it for HIPS, and how to withdraw it, as the Washington My Health My Data Act (RCW 19.373) and Nevada Senate Bill 370 require of a consent to collect consumer health data. HIPS shares none of that data with third parties for Training and sells none of it, keeps a record of your consent and of its withdrawal, and leaving Training off changes nothing in your Plan, its rates or its limits. You may withdraw your consent at any time with the same switch; HIPS then makes no training copy of the Requests it accepts afterwards and excludes your earlier contributions as Section 13.11 describes. The Consumer Health Data Privacy Policy on the Legal Information Page covers your Request Data.

Whatever your Plan or population, HIPS never relies on its legitimate interest 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. 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 (Privacy Notice Section 6.10(g)); for a Consumer, the screening of special categories of personal data about the Consumer rests on the explicit consent of Section 13.12(b), and for a Business User it is part of the processing HIPS carries out on the Business User's behalf under the DPA, on its instruction, before any of its Request Data is made available to HIPS for Training (DPA Section 14.3(f)). Every natural person may also object at any time to the use for Training of Request Data that concerns them, and HIPS then excludes it under Section 13.11; objecting does not affect anyone's access to a Plan.

13.3

Training off on the higher paid Plan. On the higher paid Plan, Training on Request Data is off by default. An Owner or admin may turn it on. The change is recorded in the Workspace's audit log, is shown before any further Request, and applies only to Requests HIPS accepts after the change. A lapse of the Plan never changes the setting (Section 7.7).

13.4

The policy is shown and fixed per Request. HIPS shows the applicable policy before you send work, including in the playground, in the API Key settings and on model pages, and the API returns it with the list of models. A Request cannot override the policy. The policy in force when HIPS accepts a Request is recorded with it and applies to every retry of that Request, and the policy in force when HIPS accepts a Batch applies to every line of it (Section 6.24), except that a Consumer's objection under Section 13.2(b) applies from the moment HIPS records it, including to the lines of an accepted Batch that have not yet run.

13.5

Training off is not zero retention. Under a training-off policy, and after a Consumer objects under Section 13.2(b), no copy of the content is made for Training. "Turning training off is not, by itself, a promise of zero retention": the content may still be processed and kept as Sections 13.8 and 14 describe, including in Batch Files (Section 6.22), and held in a prompt cache (Section 9.9).

13.6

Your model weights. "Customer-owned model weights will never be used to train other models on any plan." That commitment applies to the weights themselves. It does not change the policy for Inputs and Outputs in this Section 13.

13.7

What HIPS stores by default. "A request log defaults to operational metadata, not stored prompts and outputs." For each Request, HIPS stores the usage metadata it needs to operate, bill and secure the Services, such as the Request identifier, API Key or Authorized Tool, Workspace, model, pool, lane, pricing mode, quote, region, units, rate, cost, outcome, latency and timestamps, error types and codes, and token and unit counts. By default, HIPS does not store the prompts, messages or Outputs of Requests to language models, request or response bodies on error, or the tokens themselves. The result of a task Request or a job, the request body of an asynchronous job, the Inputs you upload for a task and Batch Files are stored as Section 13.8(b) provides. The playground keeps no conversation on HIPS's servers; a playground run of a model that is not a language model is a task Request, and its result, and any file you upload for it, are stored as Section 13.8(b) provides. A prompt cache holds in the memory of a worker, never on its disk, the state an engine computed from an Input, for no promised time and never beyond the maximum of Section 9.9(g), and is used only as Section 9.9 describes. HIPS also keeps the Prefix Ledger, which Privacy Notice Section 6.12 describes. For each Request to a language model served by a data-center worker whose prompt cache is on, and never for a Workspace whose prompt cache is turned off under Section 9.9(a), in the Console or on a written request, it records pseudonymized hashes of blocks of the tokens of the Input, keyed for each cache scope: the Workspace and, in a Workspace held by a Consumer, each Member and each API Key unless the Owner lets them share one (Section 9.9(b)), with the worker that served the Request and the time. It holds no text of an Input or an Output, and HIPS cannot read an Input from it; but because its hashes are derived from Request Data, they are pseudonymized personal data wherever the Input contains personal data, and HIPS could use them to check whether a Workspace sent a known text. HIPS uses the Prefix Ledger only to verify Cached Input Tokens (Section 9.10), to keep prompt caches apart (Section 9.9(b)), to send a Request to a worker that holds a prompt cache of its Workspace (Section 9.9(c)), to group Batch Lines that begin with the same content (Section 6.24), to investigate a fault in keeping Workspaces, or the Members of a Consumer's Workspace, apart, and to answer a binding order of a competent authority, which HIPS handles, for every Buyer, as DPA Section 5.3 provides for an authority's request for the personal data HIPS processes for a Business User, telling the Buyer unless the law forbids it, and deletes each hash as Section 14.1 provides. HIPS treats a worker's count of cached input tokens above the Prefix Ledger's for that scope as a fault in keeping Workspaces, or the Members of a Consumer's Workspace, apart, and charges only the lower count (Section 9.10(a)).

13.8

Exceptions. HIPS keeps Request content only:

  1. (a)as training copies, where the Workspace's policy allows Training;
  2. (b)as the result of a task Request or a job, which the API returns until it expires or you delete it, including the answer HIPS keeps so that a Request repeated with the same idempotency key receives it again without being run or charged a second time; as the request body of an asynchronous job, until the job ends; as uploaded task Inputs; and as Batch Files; each for the periods in Section 14;
  3. (c)as verification samples, when HIPS compares a sampled job from the Personal Pool against another run of it on a reference device that HIPS itself operates or in the Approved Pool, within the Request's region requirement, for the comparison only, deleted when it completes and in any case no later than seventy-two (72) hours after the Request; HIPS samples no content of a Request from a Workspace whose policy is training off;
  4. (d)where Applicable Law requires HIPS to preserve or report the content of a Request that the safeguards of Acceptable Use Policy Section 11.10 flag, for that purpose and only as long as that law requires; otherwise HIPS keeps no content of a flagged Request, only the record that it refused the Request or withheld its Output, with the category and the time;
  5. (e)for debugging, when you ask in writing and name the API Key and the period, for a limited time and with every access recorded;
  6. (f)where Applicable Law or a competent authority requires; and
  7. (g)where HIPS has reasonable grounds to believe that the content is illegal content or concerns a breach of the Acceptable Use Policy, a security incident, a Notice or a Dispute, or needs it to establish, exercise or defend a legal claim or to answer a request of a competent authority, for as long as that purpose needs; HIPS then keeps that content apart from other data, suspends its deletion under Sections 6.22, 14.1, 14.2 and 15.11 for that content only, gives access to it only as Section 13.9 provides, tells you of the preservation unless Section 24.3 or Applicable Law allows it to wait, and deletes it when the purpose ends.
13.9

Who may access content. HIPS troubleshoots from metadata first. Apart from the automated processing that answers Requests, runs Batches, returns the results of task Requests, jobs and Batches, and prepares training copies under Section 13.8(a) and (b), a person at HIPS may access Request content only for a purpose in Section 13.8(d) to (g), including to decide a Notice about content stored at your request, for a security incident, or for a request about the Prefix Ledger under Privacy Notice Section 11.6, with an authorization approved by a second administrator and a record of every access. Training copies are accessible only to the members of HIPS's personnel who prepare and evaluate datasets and models and who handle objections and reports, named on a list HIPS reviews at least every six (6) months and bound by duties of confidentiality, and only after the filters and the masking of Section 13.2 have run; each access to an individual training copy is recorded. A comparison under Section 13.8(c) runs automatically, without human access. Apart from HIPS's automated import checks and profiling, nobody at HIPS opens Customer Model weights except where Applicable Law requires, at your written request, or for a security incident or an abuse case that concerns the model, with the same authorization and record.

13.10

Training terms to be set. "Retention, deletion, and any other permitted uses will be set out in the service terms before production access." They are as follows. HIPS keeps a training copy, and every dataset made from it, for no longer than twenty-four (24) months after it accepted the Request it copies, and then deletes it; afterwards it keeps only the record of which Workspaces a dataset drew on, without content, for as long as a model trained on that dataset is offered. HIPS waits at least thirty (30) days after it writes a training copy before it first uses it in Training, so that an objection or an exclusion request made in that time removes it before it is used. HIPS uses training copies only for Training, as Section 2.2 defines it, and runs Training only in the EEA, never on a Device. Section 13.2(b) states the legal basis for Training on the Request Data of Consumers, and Common Clauses Section 17.3(b) the basis for the Request Data of Business Users.

13.11

Exclusion from Training. You may ask HIPS to exclude the contributions your Workspace has made from Training. HIPS then excludes them from every dataset not yet used and removes them from retained copies; a dataset already used records the Workspaces it drew on. HIPS does the same for a Workspace it pauses or closes for fraud, abuse or sanctions, for a Consumer who objects under Section 13.2(b), for a Consumer as Section 27.7 provides, and, for the Request Data that concerns them, for any natural person who objects under the last paragraph of Section 13.2. An exclusion request covers contributions made before it. Except for a Consumer's objection under Section 13.2(b), it does not change the Request-Data Policy of the Workspace's Plan for later Requests. A Workspace held by a Business User, including a US User who is a Business User, on the Free/PAYG Plan or the lower paid Plan may make an exclusion request once in each calendar quarter; this does not limit any natural person's objection under the last paragraph of Section 13.2, or an exclusion HIPS makes on its own initiative. Where an objection under Section 13.2(b) or under the last paragraph of Section 13.2 concerns Request Data in a dataset that HIPS has already used, HIPS, within three (3) months after it records the objection, retrains without that Request Data, or stops offering, every model trained on that dataset, since HIPS treats every such model as containing personal data (Section 2.2); until it has done so, and from no later than one (1) month after it records the objection, it applies to that model measures that prevent it from outputting the personal data concerned; and it tells the person who objected which it did. The same applies where HIPS learns that a training copy already used held data that the last paragraph of Section 13.2 excludes.

13.12

Your responsibilities for Inputs. You represent and warrant that you have all rights, consents and legal bases needed to submit each Input and to allow its processing under these Terms and your Workspace's policy, including its use for Training where the policy allows it. If you are a Business User, you are the controller of any personal data in your Inputs, and you are responsible for informing the people it concerns, including of your Plan's Request-Data Policy. Special categories of personal data under Article 9 of Regulation (EU) 2016/679, personal data relating to criminal convictions and offenses, personal data of children, payment card data and authentication secrets are governed as follows:

  1. (a)Business Users, including US Users who are Business Users. Unless HIPS agrees otherwise in a signed document, you shall not include such data in Inputs sent from a Workspace whose policy allows Training, or in Requests that may be served from the Personal Pool. If your Workspace's policy allows Training, you shall not send from it the personal data of anyone whom you have not informed that you disclose it to HIPS for Training and of their right to object under the last paragraph of Section 13.2, and for whose disclosure you do not have a legal basis.
  2. (b)Consumers, including US Users who are Consumers. Include personal data of other people in your Inputs only where you are entitled to share it. HIPS asks you not to include such data in Inputs sent from a Workspace whose policy allows Training, or in Requests that may be served from the Personal Pool. HIPS does not rely on its legitimate interest to train on such data, and its automated filters screen the Input and the Output of every Request for it before a training copy is written and mask names, contact details, identification numbers, payment card data and authentication secrets in them, as the last paragraph of Section 13.2 and Privacy Notice Sections 6.6, 6.8 and 6.10(g) describe. Automated filters can miss some content, so do not rely on them: if HIPS learns that a training copy holds such data, it deletes the copy and excludes it from every dataset not yet used, and Section 13.11 provides what HIPS does about a dataset already used. Before your first Request, HIPS asks you, separately from these Terms and from every other choice, whether you give your explicit consent, under Article 9(2)(a) of Regulation (EU) 2016/679, to HIPS processing the special categories of personal data about you that you choose to include in your Inputs, only to answer your Requests and to keep that data out of training copies by the screening of the last paragraph of Section 13.2. The consent is optional. Refusing it, or withdrawing it at any time in the Console as easily as you gave it, does not affect your Plan, its price, its limits or your access to the Services. If you have not given it, do not include such data about yourself in your Inputs. The consent does not cover such data about anyone else.
13.13

Changes to a Plan's policy. A change to the Request-Data Policy of a Plan is always a change of which HIPS gives notice under Common Clauses Section 9.2. It applies only to Requests HIPS accepts after it takes effect and never to Request Data accepted under an earlier policy (Common Clauses Section 9.6(b)). HIPS shows the new policy in the Console before it applies.

Section 13
  1. 13.1The policy follows the Plan
  2. 13.2Training on the Free/PAYG Plan and the lower paid Plan
  3. 13.3Training off on the higher paid Plan
  4. 13.4The policy is shown and fixed per Request
  5. 13.5Training off is not zero retention
  6. 13.6Your model weights
  7. 13.7What HIPS stores by default
  8. 13.8Exceptions
  9. 13.9Who may access content
  10. 13.10Training terms to be set
  11. 13.11Exclusion from Training
  12. 13.12Your responsibilities for Inputs
  13. 13.13Changes to a Plan's policy
Copy link

14Retention and deletion

14.1

Retention. HIPS keeps data from the Services for the periods in the table below. The Privacy Notice describes the retention of personal data in more detail.

TableWhat HIPS keeps and for how long
DataRetention
Usage metadata of RequestsThirteen (13) months from the Request; then deleted, or reduced to the charge, the quote, the units and the rate version, which are kept with the billing records, and to counts that identify no person
Inputs and OutputsNot stored, except under Section 13.8
Training copies, where the policy allows TrainingUp to twenty-four (24) months from the Request, and less where Section 13.11 requires their removal; afterwards only the record of which Workspaces a dataset drew on, without content, while a model trained on it is offered (Section 13.10)
Results of task Requests and jobsSeven (7) days after the result is produced, or less where you delete them; then deleted
Answers kept for an idempotency keyOnly a completed answer, for twenty-four (24) hours after it is produced; then deleted
Request bodies of asynchronous jobsFrom acceptance until the job ends; then deleted
Uploaded task InputsTwenty-four (24) hours after upload, or less where you delete them; then deleted
Batch input filesThirty (30) days after upload, or until the end of an open Batch that uses the file if that is later, or less where you set a shorter period for the file or delete it; then deleted (Section 6.22)
Batch output and error filesThirty (30) days after HIPS produces them, or less where you set a shorter period for the file or delete it; then deleted (Section 6.22)
Verification samplesDeleted 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 (Section 13.8(c))
Content preserved under Section 13.8(g)For as long as the purpose of that item needs; then deleted
Prompt cachesOnly in the memory of the worker that ran the Request, never on its disk, for no promised time; unreadable at most twenty-four (24) hours after the cache was made, and at once when the Workspace is deleted, the Agreement ends or you ask, and cleared from the worker's memory in full at most twenty-four (24) hours after it became unreadable (Section 9.9(g)); none on Devices at launch (Section 9.9(e))
Prefix LedgerHIPS 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 Section 9.9(a). It deletes each record no later than the maximum lifetime of a prompt cache under Section 9.9(g) 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 (Section 9.10(a)). Records that concern a fault that HIPS is investigating in keeping Workspaces, or the Members of a Consumer's Workspace, apart are kept apart from the rest, and only until the investigation ends (Section 13.7; Privacy Notice Section 6.12(d))
HIPS's copy of Customer Model weightsUntil you delete the model or version, then deleted within seven (7) days, earlier versions of the stored objects within one (1) day, subject to Section 15.11
Hub TokensUntil you delete them, and at once when the Workspace is deleted
Billing, ledger and receipt recordsSeven (7) years from the end of the financial year in which the transaction was recorded, which covers the six (6) years from the date of the transaction that Irish VAT law requires (section 84 of the Value-Added Tax Consolidation Act 2010), or any longer period that Applicable Law requires (Privacy Notice Section 7.7), and ten (10) years from the end of the year of the supply for the records of supplies HIPS declares under the Union One Stop Shop (Article 369k of Council Directive 2006/112/EC)
Identity verification record, including the identifier of a natural person of Section 4.2 and whether its holder received a Free Allowance or a Referral DiscountWhile the Account exists and for three (3) years after the deletion of the Account (Privacy Notice Section 7.6), and the identifier also while an amount remains owed to the person (Section 4.7(f)); after a closure for cause, the identifier and the record of the closure for five (5) years after the closure (Section 24.5); the identifier is never derived from biometric data and is kept whether or not the consent to the face check stands (Section 4.2)
Documents a person sends for a check by a person at HIPS after a deletionDeleted within seven (7) days after the later of HIPS's decision and the end of the waiting period of Section 4.7(d), unless HIPS needs them to establish, exercise or defend a legal claim about the change; HIPS keeps only the decision, its time, who made it and the kinds of document checked (Section 4.7(d))
14.2

Deleting a Workspace. The Owner may delete a Workspace. Deletion revokes its API Keys, stops its deployments, cancels its open Batches with the effects of Section 6.19, releases its Always-On Capacity, which ends those charges, and deletes its Hub Tokens at once. The Workspace can be restored for thirty (30) days; after that it is purged. Usage, ledger, receipt and audit records are kept as Section 14.1 describes. When the Workspace is purged, HIPS deletes the stored copies of its Customer Models within the deletion period for weights in Section 14.1, and deletes at once any of its Batch Files not already deleted. Deleting a Workspace is not a refund event: its unused Credits end when it is purged, except as Section 12.1 provides.

14.3

Results you need. You are responsible for keeping your own copies of the Outputs and results you need, including the output files of your Batches, which HIPS deletes as Section 6.22 provides. HIPS is not a storage service and does not keep Request content for you beyond Section 13.8.

Section 14
  1. 14.1Retention
  2. 14.2Deleting a Workspace
  3. 14.3Results you need
Copy link

15Customer Models

15.1

Import from a model hub. A Customer Model is imported from a model hub, never uploaded. HIPS supports Hugging Face model repositories, public, gated and private (a Space is an application, not a model source). HIPS adds another model hub only once its import passes the same checks, and lists every hub it supports, with the rules that apply to imports from it, on the import screen of the Console. You name the repository and a revision, and the import pins the exact commit or the hub's version identifier.

15.2

Weights only; no code runs. A Customer Model consists of weight files only, run by HIPS's own inference engines. No code you supply runs anywhere. HIPS refuses at import, among other things, pickle-based weight files (such as `.bin`, `.pt`, `.pth`, `.ckpt` and `.pkl` files, and any file whose content is a pickle, whatever its name), repository code that the model would need to run, custom operators outside the standard domains of the engine release HIPS uses, and external data that points outside the model's own files. A language model's chat template is data, checked at import.

15.3

HIPS's copy. Each import checks the pinned files with HIPS's engines, re-saves the files it accepts, records the hub's license on the version, signs the files with a HIPS key, and copies them once into HIPS storage, encrypted, in the region of your Workspace's storage location. Workers and Devices load only that signed copy, never the hub's files. Each import that HIPS accepts creates a new version of the Customer Model; a refused or failed import creates none.

15.4

Your warranty of rights and licenses. At every import, you represent and warrant that:

  1. (a)you have the right to run the model, at the pinned revision, commercially as a hosted inference service for your purposes, under its license and every other term that binds it, including the terms of a gated repository, which your hub account has accepted;
  2. (b)you legitimately hold any Hub Token you give HIPS and may let HIPS use it to fetch the repository;
  3. (c)HIPS's import, copying, re-saving, signing, profiling and running of the model under these Terms do not infringe or misappropriate the rights of any third party or breach any license or Applicable Law;
  4. (d)the model contains no personal data that you are not entitled to have processed under these Terms; and
  5. (e)the model is not designed or intended to generate content that the Acceptable Use Policy or Article 5 of Regulation (EU) 2024/1689 prohibits.

The Member who imports confirms this warranty by an attestation, which HIPS records with the Member and the version of the attestation text. The license the hub states is its owner's declaration, which HIPS records but cannot verify. HIPS imports a model only under a license on the list of licenses it accepts for paid hosted inference, and refuses any other, a model with no stated license or an unrecognized one included, except your own model: a repository owned by the hub account your Hub Token signs in as, whose base models are all under accepted licenses, which HIPS imports on your attestation. The accepted licenses are those the import screen of the Console lists at the time of the import; a license joins that list only after HIPS has reviewed its conditions for paid hosted inference, and HIPS refuses a model whose license does not allow it to be run as this Section provides. A model under the llama4 license, or a multimodal model under the llama3.2 license (one whose model card shows image input), including a model derived from one, is never part of HIPS's catalog, and HIPS imports it only as a Customer Model of a Buyer that is established and domiciled outside the European Union and that, in addition to the warranty above, represents and warrants at the import that it holds Meta's license for that model in its own name and is neither a natural person domiciled in the European Union nor a company with its principal place of business in the European Union; HIPS runs such a model only in its regional processing locations outside the European Union, never in the `eu` region and never for a Buyer established or domiciled in the European Union, refuses a Request for it that requires the `eu` region, and may refuse its import, and stop its deployments and delete it at any time, where HIPS has reason to doubt that warranty or Meta or another rights holder objects. A Llama 3.2 model that takes text input only passes for every Buyer. The attestation is the text of Acceptable Use Policy Section 7.2, in the version the import screen shows.

15.5

License compliance. You shall comply with the license and use restrictions of each Customer Model, including its attribution, notice and acceptable-use terms, in your use of the model and of its Outputs, and you shall pass on to your own users the restrictions its license requires you to pass on. HIPS's acceptance of an import does not mean that the model is safe, lawful, licensed or fit for any purpose.

15.6

Hub Tokens. To import from a private or gated repository, you may store an access token for the hub in the Workspace. For Hugging Face, HIPS asks for a fine-grained, read-only token scoped to the repository, and it refuses a token that the hub reports as able to write. HIPS encrypts the Hub Token, shows only its last four characters, never returns it after creation, never logs it, uses it only for the import, and never sends it to a worker, a data-center host or a Device. HIPS deletes it when you delete it, and at once when the Workspace is deleted. HIPS cannot revoke a token at its hub, so you should revoke it there when you no longer need it.

15.7

No training and no return of weights. HIPS never uses Customer Model weights to train other models (Section 13.6). No part of the Services returns the weights to anyone, your own Workspace included, and HIPS's copy never goes back to a hub.

15.8

Where Customer Models run. At launch, Customer Models run in the Approved Pool only, and a Customer Model that is a language model runs in the Approved Pool only in every phase. HIPS may later allow Customer Models in ONNX format, and no other, in the Personal Pool, and only for a deployment you opt into after being told plainly that the Device owner's machine holds the weights, with the model run in a sandbox on the Device, with Providers bound as processors under the Provider Agreement, and with verification sampling running. HIPS opens the Personal Pool to Customer Models, if it does, only by announcing it in the Console and publishing a version of these Terms that provides for it.

15.9

HIPS may refuse, suspend or remove a Customer Model. HIPS may refuse an import, stop the deployments of a Customer Model or version, or delete HIPS's copy of it, if HIPS has reasonable grounds to believe that:

  1. (a)the import or the use of the model breaches Section 15.4 or the model's license;
  2. (b)the model is designed or likely to generate content that the Acceptable Use Policy or Article 5 of Regulation (EU) 2024/1689 prohibits, including realistic intimate imagery of an identifiable person without that person's consent and child sexual abuse material, and does not have reasonable safeguards that reliably prevent it;
  3. (c)a notice under Section 15.10 is well founded;
  4. (d)the model creates a security risk for the Services, for Providers or for other Buyers; or
  5. (e)Applicable Law or a competent authority requires it.

HIPS tells you of the measure and its ground under Section 24.3, and you may ask for its review there.

15.10

Notices about Customer Models. Anyone may notify HIPS that a Customer Model or other content stored at your request infringes its rights, breaches a license or is illegal content, through the notice form or the abuse contact address that Acceptable Use Policy Section 14.2 names, which together are HIPS's notice mechanism under Article 16 of Regulation (EU) 2022/2065. HIPS decides on each notice as Acceptable Use Policy Section 14.4 provides, and gives you a statement of reasons for any measure it takes on the ground that information you provided is illegal content or breaches these Terms or the Acceptable Use Policy, as Acceptable Use Policy Section 13 and Article 17 of that Regulation provide. While HIPS reviews a notice, it may stop the deployments concerned, delete HIPS's copy once it has preserved the evidence it needs, delete the related Hub Token, and pause the Workspace under Section 24. A notice of claimed infringement of a copyright under the law of the United States, and a counter-notice, go to HIPS's agent designated under 17 U.S.C. 512(c)(2), whom Acceptable Use Policy Section 14.10 names, and follow that Section. HIPS terminates, in appropriate circumstances, the Workspaces and Accounts of repeat infringers.

15.11

Deletion. Stopping a deployment does not delete HIPS's copy. When you delete a Customer Model or a version, HIPS deletes its copy within the deletion period for weights in Section 14.1. While a security incident or a notice under Section 15.10 that concerns a deleted version is open, HIPS keeps that version's copy for that purpose only, tells you, and deletes it when the matter ends.

15.12

Your responsibility for your models. You are responsible for your Customer Models and for their Outputs. Common Clauses Sections 5.10(b) and 6.1(a) apply to them if you are a Business User or a US User.

Section 15
  1. 15.1Import from a model hub
  2. 15.2Weights only; no code runs
  3. 15.3HIPS's copy
  4. 15.4Your warranty of rights and licenses
  5. 15.5License compliance
  6. 15.6Hub Tokens
  7. 15.7No training and no return of weights
  8. 15.8Where Customer Models run
  9. 15.9HIPS may refuse, suspend or remove a Customer Model
  10. 15.10Notices about Customer Models
  11. 15.11Deletion
  12. 15.12Your responsibility for your models
Copy link

16Outputs

16.1

Ownership of Outputs. As between you and HIPS, and to the extent Applicable Law allows, you own your Outputs, and HIPS assigns to you any right it has in them. This is subject to the license of the model that produced them, to HIPS's licenses under Section 20 and to your Workspace's Request-Data Policy.

16.2

Nature of Outputs. Outputs are generated by machine learning models and may be inaccurate, incomplete, offensive or not unique, and other users may receive similar Outputs. HIPS does not review Outputs for accuracy or suitability before they are returned; it applies the safety measures of Acceptable Use Policy Section 11.10 to the models that section names.

16.3

Your responsibility. You are responsible for evaluating Outputs before you rely on them, for how you and your users use them, and for using human review where accuracy matters. Common Clauses Sections 4.6 and 4.7 apply.

16.4

Model licenses. The license of a Catalog Model or a Customer Model may restrict how its Outputs may be used. You shall comply with those restrictions to the extent they apply to you.

16.5

Marking and disclosure. HIPS may mark Outputs as artificially generated, in a machine-readable format or otherwise, where it decides to or Applicable Law requires it, and you shall not remove or alter such marking except where Applicable Law allows. Outputs may carry the marks that Acceptable Use Policy Section 6.2 describes, and Acceptable Use Policy Section 6.3 forbids removing them. You shall make the disclosures that Article 50 of Regulation (EU) 2024/1689 and other Applicable Law require of you, including that image, audio or video content you publish is a deep fake, or that text you publish to inform the public on matters of public interest was artificially generated or manipulated.

16.6

Regulated use. If you use the Services for a workload that sector rules govern, such as health, financial, legal or employment decisions, the workload runs under your own obligations under those rules, and HIPS does not take them on (Common Clauses Section 4.7).

Section 16
  1. 16.1Ownership of Outputs
  2. 16.2Nature of Outputs
  3. 16.3Your responsibility
  4. 16.4Model licenses
  5. 16.5Marking and disclosure
  6. 16.6Regulated use
Copy link

17Where computation happens

17.1

Two pools. The Personal Pool consists of idle GPU time on the personal Devices of independent Providers. The Approved Pool consists of data-center capacity from Approved Providers, which HIPS approves under the criteria it publishes on the Legal Information Page.

17.2

Encryption. Encryption in transit and at rest is part of the platform requirements. It protects data during transfer and storage, but it does not by itself prevent a GPU operator from accessing weights or Request Data during execution.

17.3

Important: access in the Personal Pool and the Approved Pool

The Personal Pool. In the Personal Pool, the owner of the Device that runs a Request can in principle access the model and the Request Data while the Request runs. The Provider App keeps content in memory only and never writes it to disk itself, although the operating system of a Device may move memory to its swap or hibernation file, which the Provider App limits where it can; the Provider Agreement forbids Providers to read, copy or keep it, but the owner has physical control of the machine. Verification sampling detects dishonest Outputs; it does not detect silent copying. HIPS takes the country of each Device from the network address of each of its connections, as Provider Agreement Section 3.3 describes: HIPS reads the country of each connection's network address, checks that the address is on no known anonymizing network, and may compare the round trips that its regional processing locations measure to the Device, never the Device's own report of them. A Device takes Requests 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 transfer assessment the DPA describes, at launch the United States, Singapore, Taiwan and Australia, as the Legal Information Page lists them; elsewhere a Device takes only work that carries no Request Data. When a Device first connects from a country that is not yet a Device Country, HIPS assesses that country for transfers of Request Data and opens it as a Device Country where the assessment allows; until then, the Device takes only test work, which carries no Request Data. HIPS sends no Request, Request Data, model or update to a Device located in a Restricted Jurisdiction, and a Device whose location HIPS cannot confirm, or that connects through an anonymizing network, takes no Request until its location is confirmed; where the Device's operating system allows it, the Provider App may reach HIPS outside a virtual private network so that HIPS can confirm that location.

17.4

The Approved Pool. In the Approved Pool, the Approved Provider runs the hardware. A data-center operator administers the host and could access GPU memory, the container's file system and the storage holding the weights, and, where a prompt cache holds the state an engine computed from an Input (Section 9.9), that state until the engine discards it or HIPS clears it under Section 9.9(g). The protections and access conditions of each Approved Provider are published on the Legal Information Page before customers deploy workloads to it (Section 17.5).

17.5

Published protections. HIPS publishes the execution protections and access conditions of each pool before customers deploy workloads to it. HIPS does not claim confidential computing for either pool and does not promise complete confidentiality.

17.6

Location of processing. Without a region requirement (Section 6.8), a Request may be processed in any of HIPS's regional processing locations and may run on data-center capacity in the EEA, the United States or Japan, in the data centers of each Approved Provider that the Legal Information Page lists by country, or on Devices located in a Device Country, including a country that HIPS opens as one after a Device first connects from it (Section 17.3), of Providers whose own Country is a Provider Country: the United States, the United Kingdom, a state of the EEA, Switzerland, Canada, Japan, Singapore, the Republic of Korea, Taiwan or Australia, each once the Provider program opens there (Provider Agreement Section 3.3). The Privacy Notice and the DPA describe the resulting transfers of personal data.

17.7

Your choice of data. You are responsible for deciding, before you send Requests, whether the conditions of each pool described in this Section 17 are acceptable for your data, and for setting the pool, region and fallback requirements of your API Keys and Requests accordingly.

17.8

HIPS's responsibility for its supply. HIPS engages Providers and Approved Providers as its subcontractors to perform the Services, and it is responsible to you for their performance of the obligations HIPS owes you under these Terms and the DPA as for its own, subject to Common Clauses Sections 4 and 5 (Common Clauses Section 3.8). Sections 17.3 to 17.5 describe the conditions of each pool so that you can choose between them under Section 17.7; this does not release HIPS from those obligations. You have no contract with, and no claim against, a Provider or an Approved Provider under these Terms, and they have none against you.

17.9

No contact with Providers. HIPS does not disclose the identity of Providers to Buyers or of Buyers to Providers, except where Applicable Law requires it. This does not prevent HIPS from making available to you as controller, under a duty of confidentiality, the identity of the Providers on your Workspace's list and of each Provider that processed your personal data, as DPA Section 7.3 provides, or from disclosing it to a supervisory authority, where Article 28 of Regulation (EU) 2016/679 requires it. You shall not try to identify, contact or contract with a Provider through or because of the Services. Requests never pass directly between your systems and a Device: each Request and its result pass through HIPS's own regional processing locations, no Buyer learns the network address of a Device, and no Provider learns the network address of a Buyer.

Section 17
  1. 17.1Two pools
  2. 17.2Encryption
  3. 17.3The Personal Pool
  4. 17.4The Approved Pool
  5. 17.5Published protections
  6. 17.6Location of processing
  7. 17.7Your choice of data
  8. 17.8HIPS's responsibility for its supply
  9. 17.9No contact with Providers
Copy link

18Availability and support

18.1

No service level. HIPS makes no commitment on uptime, latency, throughput, capacity or support response times unless HIPS agrees to one in a signed document. HIPS publishes a service commitment only when its operating and contractual basis exists.

18.2

Interruptions. The Services may be unavailable from time to time for maintenance, updates, failures of supply or reasons beyond HIPS's control. HIPS may suspend all or part of the Services for maintenance or to address a security risk, and it gives notice in advance where it reasonably can.

18.3

Support. HIPS provides support through the channels listed on the Legal Information Page. No response time is promised.

18.4

Remedies. Section 12.2 sets out what HIPS does when it charged for work not performed. If you are a Consumer, you keep the remedies Applicable Law gives you when the Services are not in conformity (Common Clauses Section 4.4).

Section 18
  1. 18.1No service level
  2. 18.2Interruptions
  3. 18.3Support
  4. 18.4Remedies
Copy link

19Acceptable use

19.1

The Acceptable Use Policy. You shall use the Services only as the Acceptable Use Policy allows. It sets out the prohibited inputs, outputs, workloads and models, the model-license obligations you carry, and what HIPS inspects and when.

19.2

Prohibited conduct. Without limiting the Acceptable Use Policy, you shall not:

  1. (a)use the Services in breach of Applicable Law or of the rights of others;
  2. (b)sell or otherwise give access to your Account, a Workspace, an API Key or an Authorized Tool to anyone who is not a Member of the Workspace, except an API Key as Section 5.2 allows;
  3. (c)resell or offer to third parties access to the API, to a model as such, or to GPU capacity, as a standalone inference, model-hosting or computing service, without HIPS's prior written consent; building and offering your own applications and services that use the Services is allowed;
  4. (d)create or use more than one identity or Account to multiply Free Allowances, promotions or Referral Discounts, or to evade a limit, a suspension or a closure;
  5. (e)import a model you do not have the right to run, or use a Hub Token you do not legitimately hold;
  6. (f)probe, scan or test the vulnerability of the Services, or circumvent their security, limits, metering, pool, region or Request-Data Policy requirements, except as HIPS authorizes in writing;
  7. (g)interfere with, disrupt or overload the Services or the Devices of Providers, including by sending Inputs designed to crash, take over or extract data from an engine or a Device;
  8. (h)reverse engineer the Services, except as Applicable Law expressly permits;
  9. (i)try to identify or contact Providers, to direct work to Devices that you or a person linked to you controls, or otherwise to turn Credits, Free Allowances, promotions or Referral Discounts into Earnings or into rewards under the Affiliate Program;
  10. (j)give a Sanctioned Person, the Government of Russia or an entity established in Russia, or the Republic of Belarus, its Government or its public bodies, corporations or agencies, access to the Services or to their results, or take part in circumventing Common Clauses Section 7;
  11. (k)generate or manipulate material that Article 5 of Regulation (EU) 2024/1689 prohibits, including realistic intimate imagery of an identifiable person without that person's consent and child sexual abuse material; or
  12. (l)help or allow anyone else to do any of these.
19.3

Detection and reports. HIPS detects abuse from metadata, rate signals and reports, as the Acceptable Use Policy describes, and not by reading Request content except as Section 13.8 allows. You may report abuse through the abuse contact on the Legal Information Page. The Acceptable Use Policy describes how HIPS handles notices, gives statements of reasons and reviews its decisions for content stored at your request, such as Customer Models, Batch Files, the results of task Requests and jobs and uploaded task Inputs.

19.4

Consequences. A breach of this Section 19 or of the Acceptable Use Policy may lead to the measures of Section 24, and Common Clauses Section 5.9(e) and Section 25.3 apply to your liability for it.

Section 19
  1. 19.1The Acceptable Use Policy
  2. 19.2Prohibited conduct
  3. 19.3Detection and reports
  4. 19.4Consequences
Copy link

20Intellectual property and licenses

20.1

HIPS's rights. HIPS and its licensors own all rights in the Services, the Console, the API, the SDKs, the documentation and the HIPS brand. No right passes to you except the rights these Terms grant expressly. The open-source inference engines and components the Services use are provided under their own licenses, and nothing in these Terms limits the rights those licenses give you in them.

20.2

Your content. As between you and HIPS, you keep all rights in your Inputs, your Outputs (Section 16.1) and your Customer Models.

20.3

License to operate the Services. You grant HIPS a worldwide, non-exclusive, royalty-free license to host, copy, transmit, check, re-save, sign, profile, cache and otherwise process your Inputs, Outputs and Customer Models as needed to provide, secure, verify, support and bill the Services, to enforce these Terms and the Acceptable Use Policy, and to comply with Applicable Law, for as long as you use them and for the periods in Section 14 and Section 13.8(g). HIPS may extend this license to Providers, Approved Providers and its service providers only as needed to run your Requests and to provide the Services.

20.4

License for Training. Where the Request Data of your Workspace may be used for Training under Section 13, you also grant HIPS a worldwide, non-exclusive, royalty-free license to use that Request Data for Training as Section 13 describes; the license may be transferred only to a successor under Privacy Notice Section 9.5(f), and sublicensed only to service providers that process the Request Data on HIPS's behalf:

  1. (a)Business Users, including US Users who are Business Users. The license is perpetual and irrevocable for the Request Data of every Request HIPS accepts while your Workspace's policy allows Training, subject only to exclusion under Section 13.11 and to an objection by a natural person under the last paragraph of Section 13.2.
  2. (b)Consumers, including US Users who are Consumers. The license covers the Request Data of the Requests HIPS accepts while you have not objected under Section 13.2(b). It ends for Request Data not yet used for Training when you object, when HIPS excludes that Request Data under Section 13.11, or when your Agreement ends (and, if Section 27 applies to you, as Section 27.7 describes), and it continues after that only for Request Data already aggregated into a trained model or a dataset already used, which cannot be separated from it without disproportionate effort, subject to Section 13.11.

This license concerns HIPS's rights in the content. HIPS's use of personal data for Training rests on the legal basis that Section 13.2 and the Privacy Notice state, not on this license. An exclusion, an objection or the end of your Agreement does not require HIPS to withdraw or retrain a model already trained on Request Data, except as Section 13.11 provides or Applicable Law requires.

20.5

Feedback. If you give HIPS suggestions or feedback about the Services, HIPS may use them without restriction or payment.

20.6

Usage metadata. HIPS may use usage metadata to operate, bill, secure and improve the Services, and may publish statistics derived from it that do not identify you.

Section 20
  1. 20.1HIPS's rights
  2. 20.2Your content
  3. 20.3License to operate the Services
  4. 20.4License for Training
  5. 20.5Feedback
  6. 20.6Usage metadata
Copy link

21Confidentiality

21.1

Confidential Information. Non-public information that one party discloses to the other in connection with these Terms and that is marked confidential, or should reasonably be understood to be confidential, is Confidential Information. Your Inputs, Customer Models, Hub Tokens and API Keys are your Confidential Information. HIPS's non-public pricing, security information, verification methods and the identities of Providers and Buyers are HIPS's Confidential Information.

21.2

Obligations. The receiving party shall use Confidential Information only to perform or exercise its rights under these Terms, shall protect it with at least reasonable care, and shall disclose it only to its personnel, contractors and advisers who need it and are bound by duties of confidentiality at least as protective.

21.3

Exceptions. Section 21.2 does not apply to information that is or becomes public without a breach of these Terms, that the receiving party already knew or developed independently, or that it received lawfully from a third party without a duty of confidentiality.

21.4

Required disclosure. A party may disclose Confidential Information where Applicable Law or a competent authority requires it, after telling the other party where it lawfully can.

21.5

Request Data. Nothing in this Section 21 limits HIPS's use of Request Data as Sections 13 and 20 permit, or a disclosure under Section 21.7.

21.6

Processing in the pools. For Request Data and Customer Models processed in the Personal Pool or the Approved Pool, HIPS meets Section 21.2 by applying the protections described in Section 17 and published for each pool, and by binding Providers and Approved Providers to confidentiality. The access that Sections 17.3 and 17.4 describe is not a breach of this Section 21.

21.7

Reports and evidence. Section 21.2 does not prevent HIPS from using or disclosing your Confidential Information, including Inputs, Outputs, Batch Files, uploaded task Inputs and Customer Models, to the extent reasonably necessary:

  1. (a)to report illegal content, suspected child sexual abuse material or a suspected criminal offense to a competent authority, or to an organization that Applicable Law recognizes for receiving such reports, as Acceptable Use Policy Sections 5.2 and 12.9 provide;
  2. (b)to decide a Notice and inform the Notifier under Acceptable Use Policy Section 14, without disclosing your identity except as that Section allows;
  3. (c)to give a payment processor or a card network the evidence of Section 12.5(e);
  4. (d)to tell a model hub or a rights holder of a breach that concerns its model or its rights, as Acceptable Use Policy Section 12.9 allows, disclosing no more of your Inputs, Outputs or Customer Models than shows the breach; or
  5. (e)to establish, exercise or defend a legal claim, under a duty of confidentiality where the forum allows.

For personal data that HIPS processes on behalf of a Business User, HIPS does so only as the DPA provides.

Section 21
  1. 21.1Confidential Information
  2. 21.2Obligations
  3. 21.3Exceptions
  4. 21.4Required disclosure
  5. 21.5Request Data
  6. 21.6Processing in the pools
  7. 21.7Reports and evidence
Copy link

22Privacy and data protection

22.1

Privacy Notice. The Privacy Notice explains how HIPS collects and uses personal data about you as a controller, including Account, verification, billing and usage data. HIPS is the controller of that personal data, and the Operating Company processes it only for HIPS, as HIPS's processor (Privacy Notice Section 2.7). HIPS's lead supervisory authority is the Data Protection Commission of Ireland.

22.2

The DPA. If you are a Business User, including a US User who is a Business User, and your Inputs or Customer Models contain personal data, you are the controller of that data, and HIPS processes it on your behalf to answer your Requests. The DPA forms part of your Agreement and applies, without a separate signature, whenever HIPS processes personal data on your behalf. You accept it when you accept these Terms, and HIPS records its version with your acceptance. HIPS engages the Operating Company, which operates the Services for HIPS, as a sub-processor (DPA Annex 3). If you are a Consumer, HIPS processes the personal data in your Inputs and Customer Models as the controller (Privacy Notice Section 2.3), as the Privacy Notice describes, and the DPA does not apply to you.

22.3

Processing in the pools. Approved Providers, and Providers in the Personal Pool, process content on HIPS's behalf when they run Requests. For Business Users, including US Users who are Business Users, the DPA describes them, as categories of sub-processors, and the terms that bind them; for Consumers, the Privacy Notice does. If you are a Business User, including a US User who is a Business User, you may object to Providers in the Personal Pool as sub-processors by restricting your API Keys and Requests to the Approved Pool (Section 17.7).

22.4

Identity verification. HIPS's identity verification provider processes your identity document and the automated face check; a person at HIPS runs the face check by a person (Section 4.8). HIPS keeps only the records in Section 4.2, and Sections 4.8 and 4.9 apply to the face check.

22.5

Training. For Training, HIPS acts as an independent controller of the training copies it makes, not as your processor, and the DPA does not apply to them.

  1. (a)Business Users, including US Users who are Business Users. If your Workspace's policy allows Training, you instruct HIPS to make the Request Data of your Workspace available to HIPS for Training, and you warrant that you have a legal basis for that disclosure and have informed the people the data concerns, including of their right to object under the last paragraph of Section 13.2. HIPS relies on its legitimate interests, as Common Clauses Section 17.3(b) states. HIPS applies to that Request Data the same safeguards as to the Request Data of Consumers (the last paragraph of Section 13.2, and Sections 13.10 and 13.11), and, because it cannot identify or reach the people your Inputs concern, it informs them of that Training by publishing the Privacy Notice, as Article 14(5)(b) of Regulation (EU) 2016/679 provides.
  2. (b)Consumers, including US Users who are Consumers. HIPS is the controller of your Request Data, and it uses that Request Data for Training on the basis of its legitimate interest, unless you object, or, if your Country is the United States, only on your consent, as Section 13.2(b) and the Privacy Notice describe.
Section 22
  1. 22.1Privacy Notice
  2. 22.2The DPA
  3. 22.3Processing in the pools
  4. 22.4Identity verification
  5. 22.5Training
Copy link

23Third-party services and model licenses

23.1

Third-party services. Parts of the Services rely on third parties that act under their own terms, including Stripe for card payments, Machine Payments included, HIPS's identity verification provider, Google for sign-in if you choose it, and the model hubs from which you import. HIPS is not responsible for third-party services it does not control (Common Clauses Section 5.10(f) for Business Users and US Users), and your use of them may be subject to their terms.

23.2

Model licenses. Each Catalog Model and each Customer Model is made available under its own license, which may restrict how the model and its Outputs may be used, and you shall comply with it to the extent it applies to you. In particular:

  1. (a)for a model under a Llama community license, the model's page links to a copy of that license agreement and to Meta's Acceptable Use Policy for that version, which forms part of that license, and you shall comply with that policy;
  2. (b)for a model under the Gemma Terms of Use, the use restrictions of Section 3.2 of those terms, including the Gemma Prohibited Use Policy, are an enforceable term of these Terms, you shall comply with them, the model's page links to a copy of the Gemma Terms of Use, and Google may restrict the use of Gemma, remotely or otherwise, as those terms provide; and
  3. (c)for any model, you shall respect the attribution, notices and restrictions its page states.

You shall bind your End Users to these restrictions, and tell them that they apply, as Acceptable Use Policy Section 1.7 requires. Where the licensor of a model requires HIPS to restrict or end its use, HIPS may do so under Section 6.6.

23.3

Model hubs. HIPS contacts a model hub only on your instruction and sends it no customer data beyond the request for the files.

23.4

Blockchain networks. The Services use no blockchain network and involve no Crypto-Asset (Section 10.5). HIPS is not responsible for any blockchain network or Crypto-Asset, or for their operation, delays, forks, changes or fees.

Section 23
  1. 23.1Third-party services
  2. 23.2Model licenses
  3. 23.3Model hubs
  4. 23.4Blockchain networks
Copy link

24Suspension and closure

24.1

Your right to leave. You may stop using the Services at any time, and you may terminate these Terms at any time by deleting your Workspaces (Section 14.2) and your Account (Section 4.7). When you terminate for convenience, HIPS refunds nothing, except as Section 12.1 provides.

24.2

Important: when HIPS may act at once

Immediate measures for cause. HIPS may, with immediate effect and without prior notice, limit, pause, suspend or close your Account, any Workspace, any API Key or Authorized Tool, or any Customer Model or deployment, in whole or in part, if HIPS has reasonable grounds to believe or suspect that:

  1. (a)you, or anyone using your Account or your Workspace's credentials, has committed or attempted fraud, including payment fraud, the use of a payment method without authority, identity misuse, the use of more than one identity, or abuse of the Free Allowance, a promotion, a Referral Discount or the Affiliate Program;
  2. (b)you have committed a material breach of these Terms or the Acceptable Use Policy, including a breach of Section 19.2 or Section 12.5(d);
  3. (c)your use creates a security risk, or a risk of liability for HIPS, its Buyers or its Providers;
  4. (d)a payment for a Workspace is disputed, to the extent Section 12.4 allows a measure for it, or an amount you owe HIPS, including a reversed payment you have not paid again, is unpaid when due;
  5. (e)Sanctions Laws or Export Control Laws apply to you or to your use (Common Clauses Section 7.7);
  6. (f)your identity, status, tax or payment information is missing, false, unverified or inconsistent, and you have not corrected it within the time HIPS gave you in a notice;
  7. (g)your Inputs, Customer Models or other content stored at your request are illegal content or incompatible with the Acceptable Use Policy; or
  8. (h)Applicable Law, a competent authority, a card network or a payment processor requires it.

HIPS chooses a measure that is proportionate to the ground. It closes an Account or a Workspace under this Section only where the ground is serious: fraud HIPS has established after review, a serious or repeated breach, an amount unpaid after notice, the application of Sanctions Laws, or a requirement of Applicable Law or a competent authority.

24.3

Statement of reasons and review. HIPS tells you of each measure under Section 24.2 and the ground it relies on, in a short statement of reasons on a Durable Medium, when the measure takes effect. Where the measure rests on content you provided, the statement also says how you can seek redress. Where the measure rests on the ground that information you provided is illegal content or incompatible with these Terms or the Acceptable Use Policy, HIPS gives the statement at the latest when the measure takes effect, as Article 17 of Regulation (EU) 2022/2065 requires and Acceptable Use Policy Section 13.2 describes, unless the measure gives effect to an order under Article 9 of that Regulation. For a measure on any other ground, HIPS may delay the statement where Applicable Law prohibits it, or where telling you would prejudice the prevention or investigation of fraud, a security incident or the application of Sanctions Laws, and it then tells you when that reason ceases. You may ask HIPS to review the measure by replying to the statement or through the contact on the Legal Information Page; a person at HIPS with authority to change the measure reviews it and tells you the outcome. This review does not limit your rights under Common Clauses Sections 12 to 15 or under data protection law.

24.4

Effects of a pause or suspension. While a Workspace is paused, running jobs finish, queued asynchronous jobs are canceled, and its open Batches are treated as Section 6.25 provides. Its Always-On Capacity keeps being charged unless you stop it, which you can do in the Console while the Workspace is paused; if HIPS lifts the pause because the ground was not established, HIPS credits back the Always-On charges incurred during the pause. While a pause for fraud, a breach of the Acceptable Use Policy, a security risk or sanctions stands, the Owner and admins of the Workspace, and every user that verification links to the same person, cannot create another Workspace or invite Members. A suspension of a verified person blocks sign-in to every Account of that person, and the Provider Agreement governs the effect on any Devices and Earnings of that person. A measure that concerns a verified person affects a Workspace held by another Buyer only by suspending that person's membership in it (Section 4.5).

24.5

Closure for cause. When HIPS closes a Workspace under Section 24.2, its API Keys are revoked, its deployments stop, its Always-On Capacity is released and the Workspace is deleted. HIPS restores it, on a request by its Owner made within thirty (30) days after the closure, where HIPS reverses the closure on review under Section 24.3, where a court, an arbitral tribunal or an out-of-court dispute resolution body decides that it was not justified, or where its only ground was an amount unpaid or information missing that has since been paid or provided. HIPS never restores: (a) content that is illegal content, or that Applicable Law or a competent authority requires HIPS to remove, disable or keep from you; (b) anything that Sanctions Laws or Export Control Laws prohibit HIPS from making available to you; or (c) a Workspace closed for fraud that HIPS established after review, unless that finding is reversed. Whether or not it can be restored, HIPS keeps the Batch output and error files and the results of task Requests and jobs of the Workspace that are still within their periods under Sections 6.22 and 14.1 available to you, through a time-limited download link that HIPS sends, on request, to the Owner or, for a Business User, to its 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 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 Section 13.8(g) provides; for a Business User, this is the return that DPA Section 12.4 provides. HIPS makes the prompt caches of the Workspace unreadable at once and clears them within the period of Section 9.9(g). HIPS records the closure with the verification reference and the identifier of a natural person of Section 4.2 of each verified person on whom the ground for the closure rests (for an organization, of its representative, with its registration number), whether or not that person's consent to the face check stands, for five (5) years after the closure, so that a later invitation, Account, Workspace or verification of the same person can be recognized and refused (Section 3.7).

24.6

Credits and prepaid fees on closure for cause. On a closure under Section 24.2, each of the following is a separate provision:

  1. (a)HIPS first applies the unused Purchased Credits of the closed Workspace, and the unused part of a prepaid Plan fee, to the amounts you owe HIPS under your Agreement;
  2. (b)the Free Allowance, Included Credits and Promotional Credits of the closed Workspace end on closure;
  3. (c)Business Users and US Users. If the closure is for fraud that HIPS has established after review, the remainder after (a) and (e) is forfeited to HIPS as the agreed measure of the loss that such fraud causes HIPS beyond the documented amounts of (e) and that cannot be documented item by item, such as the monitoring and review of the Services against further use of the same methods, the effect of the fraud on HIPS's standing with its payment providers and card networks, and the value of Services that the fraud obtained and that HIPS cannot trace; you and HIPS agree that the forfeiture is a genuine pre-estimate of that loss, made when the Agreement is concluded, and not a sum payable to punish or to deter a breach. HIPS tells you of the forfeiture and its basis on a Durable Medium within a reasonable time after its review ends. You may dispute it under Common Clauses Sections 12 to 15, and HIPS refunds any part of it that a court or arbitral tribunal finds HIPS may not keep. HIPS may claim damage only to the extent that it exceeds the total of the amounts applied under (a) and (e) and forfeited under this (c);
  4. (d)in every other case, HIPS refunds the remainder after (a) and (e) under Section 12.1; and
  5. (e)Business Users and US Users. Before (c) or (d) applies, HIPS also applies the remainder after (a) to its documented losses and costs caused by the ground for the closure, such as reversed payments, payment processor fees and fines, amounts HIPS credited or refunded to others, and the reasonable cost of investigating; HIPS tells you of each amount and its basis on a Durable Medium, and an amount you dispute within thirty (30) days of that notice is held and not applied until the Dispute is resolved, when HIPS applies or refunds it as the outcome requires.

If you are a Consumer, (a) applies only to the amounts you owe HIPS and to the compensation for damage that Applicable Law allows HIPS to claim from you (Common Clauses Section 6.3), and (c) and (e) do not apply to you. Section 24.6(a), (c) and (e) depart from Common Clauses Section 3.7, as Common Clauses Section 1.3 allows, by applying or forfeiting Purchased Credits otherwise than as payment for the Services.

24.7

Termination without cause. Either party may terminate these Terms at any time and for any reason. You do so under Section 24.1. HIPS does so by notice to you on a Durable Medium, and the termination takes effect thirty (30) days after HIPS sends the notice. Until then you may keep using the Services under these Terms. When the termination takes effect, HIPS refunds your unused Purchased Credits and the unused part of any prepaid Plan fee. If you are also a Provider, the Provider Agreement governs your Earnings. Section 28.4 adds a right for HIPS in respect of US Users.

24.8

Effect of termination. When these Terms end for any reason, your access to the Services ends, your API Keys and the authorizations of your Authorized Tools are revoked, your deployments stop, your open Batches are canceled with the effects of Section 6.19, your Always-On Capacity is released, and HIPS makes the prompt caches of your Workspaces unreadable at once and clears them within the period of Section 9.9(g); every amount you owe HIPS becomes due; your Credits are treated as Sections 12.1, 24.6 and 24.7 provide; the Batch output and error files and the results of task Requests and jobs still within their periods stay available to you for thirty (30) days, as Section 24.5 and, for a Business User, DPA Section 12.4 provide; and HIPS keeps and deletes data as Section 14 and DPA Section 12.4 describe. Common Clauses Section 19 and Section 29.10 govern which provisions survive.

24.9

Reporting. HIPS may report conduct to the competent authorities where it has a duty to do so or Applicable Law allows it (Section 21.7).

24.10

Switching to another provider. HIPS provides the Services as a data processing service under Chapter VI of Regulation (EU) 2023/2854, and this Section sets out your rights to switch. Each of the following is a separate provision:

  1. (a)you may at any time ask HIPS, in the Console or by notice to the legal contact address in Section 30, to switch to a data processing service of another provider or to your own ICT infrastructure, naming that provider where there is one, or to erase your exportable data; HIPS starts the switching process within fourteen (14) days after your request;
  2. (b)the transitional period is thirty (30) days from that start, unless HIPS tells you within fourteen (14) working days of your request, with its reasons, that this is technically unfeasible and names an alternative period of no more than seven (7) months; you may extend the transitional period once by notice before it ends; during it your Agreement continues, and HIPS gives you and the persons you authorize reasonable assistance, acts with due care to keep the Services running, tells you of the risks it knows to their continuity, and keeps your data secure;
  3. (c)your exportable data are your Batch Files, the results of task Requests and jobs and your uploaded task Inputs that are still within their periods under Section 14, your usage records, receipts and invoices, the settings of your Workspaces, API Keys (without their secrets) and deployments, and, for each Customer Model, the model hub repository and pinned revision from which it was imported; they do not include the weights of a Customer Model, which you hold at the model hub, HIPS's prices, verification methods, the Prefix Ledger, training copies that HIPS holds as a controller (Section 22.5) or any other data of the internal functioning of the Services that HIPS's register lists as a trade secret of HIPS;
  4. (d)you may retrieve your exportable data through the API and the Console, in the formats that HIPS's register lists, for at least thirty (30) days after the transitional period ends;
  5. (e)when that retrieval period ends and the switching process is complete, or when you asked only for erasure, HIPS erases the exportable data you generated or that relate to you directly, except what Section 14.1 or Applicable Law requires it to keep, your Agreement ends, and HIPS tells you so on a Durable Medium;
  6. (f)HIPS charges nothing for switching; and
  7. (g)HIPS publishes on the Legal Information Page the information that Articles 26 and 28 of Regulation (EU) 2023/2854 require, including the register of the data structures and formats of the exportable data, the jurisdiction to which its ICT infrastructure is subject, and its measures against international governmental access to non-personal data held in the Union that would conflict with Union or Member State law.
Section 24
  1. 24.1Your right to leave
  2. 24.2Immediate measures for cause
  3. 24.3Statement of reasons and review
  4. 24.4Effects of a pause or suspension
  5. 24.5Closure for cause
  6. 24.6Credits and prepaid fees on closure for cause
  7. 24.7Termination without cause
  8. 24.8Effect of termination
  9. 24.9Reporting
  10. 24.10Switching to another provider
Copy link

25Liability, disclaimers and indemnities

25.1

The Common Clauses govern. The disclaimers of Common Clauses Section 4, the limitation of liability of Common Clauses Section 5 and the indemnities of Common Clauses Section 6 apply to these Terms, each for the population it names. This Section 25 quotes the parts you most need to read and adds the points specific to Buyers.

Important: liability that is never limited

Common Clauses Section 5.1 provides, with its list run together: "Nothing in the Agreement excludes or limits either party's liability for: (a) death or personal injury caused by its negligence or the negligence of its personnel; (b) fraud or fraudulent misrepresentation; (c) intentional breach of the Agreement or willful misconduct; (d) gross negligence, as Section 5.2 provides; (e) liability under the law implementing Directive (EU) 2024/2853 on liability for defective products, or under any other product liability law that does not permit it to be excluded or limited, including for damage to your property or the destruction or corruption of your data caused by a defect in the Provider App; or (f) any other liability that Applicable Law does not permit to be excluded or limited. Sections 5.3 to 5.13 are subject to this Section 5.1."

Important: the limit of liability for Business Users

Common Clauses Section 5.6 provides, with its list run together: "Each party's total aggregate liability to the other arising out of or in connection with an Agreement, for all claims together, whether in contract, tort (including negligence), breach of statutory duty or otherwise, is limited to the greater of: (a) for a claim arising from your use of the Services as a Buyer, the total Fees you paid HIPS in the twelve (12) months before the first event giving rise to liability, and, for a claim arising under the Provider Agreement, the greater of the total Earnings HIPS paid you and the total Earnings HIPS settled as payable for you in those twelve (12) months, and, for a claim arising under the Affiliate Program Agreement, the total commissions HIPS paid you under it in those twelve (12) months; and (b) one hundred United States dollars (US$100), whatever the capacity in which the claim arises. Where a claim arises in more than one capacity, the greatest of the amounts in (a) for those capacities applies."

25.2

The limits for each population.

  1. (a)Business Users. Common Clauses Sections 4.2, 5.3, 5.6, 5.10, 5.12 and 5.13 apply to you.
  2. (b)US Users. Common Clauses Sections 4.3, 5.4, 5.7, 5.10, 5.12 and 5.13 apply to you; Section 28.6 quotes the limit of liability.
  3. (c)Consumers. Common Clauses Sections 4.4, 5.5, 5.8 and 5.11 apply to you, and you keep the remedies Applicable Law gives you when the Services are not in conformity.
25.3

Amounts outside the limits. The limits do not reduce HIPS's obligation to make the refunds these Terms promise, and they do not reduce your obligation to pay Fees, charges, taxes, a negative balance and the other amounts you owe HIPS, or your liability for a breach of Section 19, of the Acceptable Use Policy or of Common Clauses Section 7 (Common Clauses Section 5.9).

25.4

Charged work. Section 12.2 sets out HIPS's remedy for a charge for work not performed.

25.5

Your indemnity. If you are a Business User or a US User, you defend and indemnify the HIPS Indemnified Persons under Common Clauses Section 6.1, including against Claims arising from your Inputs, your Customer Models, your Outputs and their use, the applications you build with the Services, your breach of these Terms or the Acceptable Use Policy, and a false declaration of your status, Country, tax status or VAT number. If you are a Consumer, Common Clauses Section 6.3 applies to you instead.

25.6

HIPS's indemnity. If you are a Business User or a US User, HIPS defends you against intellectual property Claims concerning the HIPS Software under Common Clauses Section 6.4, which states HIPS's entire liability for such Claims.

Section 25
  1. 25.1The Common Clauses govern
  2. 25.2The limits for each population
  3. 25.3Amounts outside the limits
  4. 25.4Charged work
  5. 25.5Your indemnity
  6. 25.6HIPS's indemnity
Copy link

26Business Users outside the United States

26.1

Who this Section applies to. This Section 26 applies to you if you are a Business User whose Country is not the United States.

26.2

Important for Business Users: arbitration in Tallinn, individual claims only

Disputes. Every Dispute is resolved on the Business Track of Common Clauses Section 13. Its central provisions read:

Common Clauses Section 13.2: "The Agreement, and every Dispute, including a non-contractual claim, are governed by the laws of Ireland, excluding its rules on the conflict of laws and excluding the United Nations Convention on Contracts for the International Sale of Goods." Common Clauses Section 13.3: "Any dispute, controversy or claim arising out of or in connection with the Agreement, including its breach, termination or validity, and every other Dispute, shall be finally settled by the Arbitration Court of the Estonian Chamber of Commerce and Industry in accordance with its rules on expedited procedure. If those rules do not allow the expedited procedure for a Dispute, it is finally settled by that Arbitration Court in accordance with its rules of arbitration in force when the request for arbitration is filed." Common Clauses Section 13.4: "The seat of arbitration is Tallinn, Estonia. The language of the arbitral proceedings is English. The tribunal consists of a sole arbitrator. The arbitration, its existence, the submissions, the evidence and the award are confidential, except to the extent that disclosure is needed to enforce or challenge an award, to comply with Applicable Law, or to obtain professional advice under a duty of confidentiality." Common Clauses Section 13.5: "Each party may bring claims against the other only in its individual capacity, and not as a claimant in, or a member of, any class, collective, consolidated or representative proceeding. The tribunal may not consolidate the claims of more than one claimant against HIPS, may not join a person who is not a party to the Agreement, and may not award relief to anyone other than the individual claimant."

Common Clauses Sections 12.7 (notice of dispute and informal resolution), 13.6 (interim relief in court), 13.7 (claims for sums due, which may go to the courts of Ireland or of the debtor's State), 13.8 (small claims, which may go to the courts of Ireland), 13.9 (time limit for claims), 13.10 (award) and 13.11 (if the restriction to individual claims fails) also apply.

26.3

No consumer protections. Section 27 does not apply to you. You have no right of withdrawal, and the disclaimers of Common Clauses Section 4.2 apply, subject to Section 26.7. You confirm that you accept these Terms, and use each Workspace you hold, for the purposes of your trade, business, craft or profession.

26.4

Information before the contract. Common Clauses Section 17.7 applies: you and HIPS agree that HIPS need not give you the information on the technical steps of concluding the contract, the filing of the contract, the correction of input errors and the languages offered that Applicable Law otherwise requires before an order is placed.

26.5

Records. HIPS's records of Requests, usage, charges and Credits are the basis of charges and prevail unless you show that they are wrong (Common Clauses Section 17.4).

26.6

Correcting your status. If HIPS has reasonable grounds to believe that a Workspace declared as held by a Business User is used for purposes outside a trade, business, craft or profession, HIPS may ask you to correct the declaration under Section 3.3, and if you do not, it may take a measure under Section 24.2(f).

26.7

Business Users in Australia, the Republic of Korea and Taiwan. If your Country is Australia: (a) where you acquire the Services as a consumer within the meaning of the Australian Consumer Law, which may include a business that acquires them for not more than the amount that law sets, the Services come with guarantees that cannot be excluded under that law; (b) nothing in these Terms or in the Common Clauses, including Section 25, Section 26.3 and Common Clauses Sections 4 and 5, excludes, restricts or modifies those guarantees or any other right or remedy under the Australian Consumer Law, or under any other law of Australia, that cannot lawfully be excluded, restricted or modified; and (c) where the Services are not of a kind ordinarily acquired for personal, domestic or household use or consumption, HIPS's liability for a failure to comply with such a guarantee is limited, to the extent section 64A of the Australian Consumer Law allows, to supplying the Services again or paying the cost of having them supplied again, as HIPS chooses. If your Country is the Republic of Korea or Taiwan, nothing in these Terms excludes or restricts a right that the Act on the Regulation of Terms and Conditions of the Republic of Korea or Article 247-1 of the Civil Code of Taiwan, to the extent it applies to your Agreement, does not allow a standard term to exclude or restrict. Common Clauses Section 13.12 applies to your Disputes.

Section 26
  1. 26.1Who this Section applies to
  2. 26.2Disputes
  3. 26.3No consumer protections
  4. 26.4Information before the contract
  5. 26.5Records
  6. 26.6Correcting your status
  7. 26.7Business Users in Australia, the Republic of Korea and Taiwan
Copy link

27Consumers

27.1

Who this Section applies to. This Section 27 applies to you if you are a Consumer whose Country is not the United States. If you are a Consumer in the United States, Section 28 applies to you instead, together with the rights the law of your state gives you. Sections 27.4 to 27.6 apply to EU Consumers, and to other Consumers to the extent the law of their Country gives them a right of withdrawal from a contract for digital services.

27.2

Your statutory rights. Nothing in your Agreement excludes or limits the rights that the mandatory consumer law of your Country gives you. HIPS supplies the Services in conformity with your Agreement and with Applicable Law, and you have the remedies Applicable Law gives you when they are not in conformity (Common Clauses Section 4.4). Information HIPS gave you before you accepted, which Applicable Law makes part of the contract, is part of it (Common Clauses Section 17.2(b)).

27.3

Characteristics you accept expressly. Before you accept these Terms, HIPS tells you specifically, and asks you to accept expressly and separately, the following characteristics of the Services, which form part of their description (Common Clauses Sections 4.1 and 4.4):

  1. (a)on the Free/PAYG Plan and the lower paid Plan, HIPS uses your Inputs and Outputs for Training unless you object with the switch of Section 13.2(b), and objecting keeps your Plan;
  2. (b)the owner of a Device in the Personal Pool, and the operator of hardware in the Approved Pool, can in principle access the model and the Request Data while a Request runs, and the operator also while a prompt cache holds it (Sections 9.9, 17.3 and 17.4);
  3. (c)no service level applies, and capacity is not reserved (Sections 6.9 and 18.1);
  4. (d)Purchased Credits expire twelve (12) months after purchase (Section 8.5), and Section 27.12 applies to their refund; and
  5. (e)a Batch has no promised completion time, its lines that have not finished when its Completion Window closes expire without charge, and a prompt cache has no promised lifetime and promises no saving (Sections 6.17, 6.18 and 9.9).

Your acceptance under this Section 27.3 concerns the description of the Services. It is not consent under Regulation (EU) 2016/679: HIPS's legal basis for using your personal data for Training is its legitimate interest, as Section 13.2(b) states, and you may object at any time.

27.4

Important for Consumers: your right of withdrawal

Your right of withdrawal. You may withdraw from a contract with HIPS for the Services, without giving any reason, within fourteen (14) days after the day on which the contract is concluded. For this purpose:

  1. (a)your acceptance of these Terms concludes the contract under which you use the Free/PAYG Plan;
  2. (b)each purchase of Purchased Credits is a separate contract, concluded when HIPS confirms your payment; and
  3. (c)each subscription to a paid Plan is a contract concluded when HIPS confirms your first payment for it; a renewal of the same subscription is not a new contract.
27.5

How to withdraw. To withdraw, you tell HIPS of your decision before the withdrawal period ends, by the withdrawal button in the Console, marked "Withdraw from the contract", which stays available to you throughout the withdrawal period and asks you to enter or confirm your name, the contract you withdraw from and the email address to which HIPS sends its confirmation, and which you send by a button marked "I confirm the withdrawal", as Article 11a of Directive 2011/83/EU on consumer rights requires; by an unequivocal statement sent to the legal contact address in Section 30; or with the model withdrawal form that HIPS publishes on the Legal Information Page, which you may use but need not. It is enough that you send your statement before the period ends. HIPS confirms receipt of your withdrawal on a Durable Medium without delay, stating what you sent and the date and time you sent it. For each contract, HIPS sends you within a reasonable time after it is concluded, and at the latest before performance begins, a confirmation on a Durable Medium containing the information on your right of withdrawal and the model withdrawal form, and, where Section 27.6 applies, your request and acknowledgment.

27.6

If you want to start at once. HIPS performs a contract for Purchased Credits or for a paid Plan during the withdrawal period only if you ask it to, expressly, before you pay. For automatic reload and for Machine Payments, you make that request, and give the acknowledgment of item (a), when you turn them on, for every purchase made while they stay on (Sections 10.6 and 10.11(g)). Each of the following is a separate provision:

  1. (a)when you ask, you also acknowledge that, if you withdraw, you pay HIPS an amount proportionate to what HIPS supplied until you told it of your withdrawal, and that you lose your right of withdrawal from a contract once HIPS has fully performed it, which for a purchase of Purchased Credits is when all the Credits of that purchase have been used; HIPS confirms your request and your acknowledgment on a Durable Medium;
  2. (b)if you withdraw after such a request, HIPS calculates the proportionate amount on the price agreed, in proportion to what HIPS supplied (the Credits of that contract you used and the part of the Plan period that had run) compared with everything the contract covers, and refunds the rest of your payment; if that price is excessive, the proportionate amount is calculated on the market value of what HIPS supplied;
  3. (c)HIPS makes the refund without undue delay and in any case within fourteen (14) days after the day it is told of your withdrawal, using the same means of payment you used, unless you expressly agree otherwise, and without charging you a fee for it; when it refunds, HIPS removes the unused Credits of that purchase or ends the subscription;
  4. (d)if HIPS started to perform during the withdrawal period without your express request and acknowledgment, you owe nothing for what it supplied during that period;
  5. (e)if you withdraw from the contract under which you use the Free/PAYG Plan, HIPS closes the Workspace's use of that Plan, and Section 27.7 applies to your content; and
  6. (f)after you withdraw, you stop using the Services under the contract you withdrew from, and Section 27.7 applies to your content.
27.7

Your content when a contract ends. HIPS supplies the Free/PAYG Plan without a monetary price, and on that Plan and the lower paid Plan HIPS uses your Inputs and Outputs for Training unless you object under Section 13.2(b). If you withdraw from or terminate a contract for the Services, HIPS excludes the Request Data of your Workspace from every Training dataset not yet used and from retained training copies, as Section 13.11 describes, except content that has already been used to train a model, which Section 13.11 governs and, if you also object under Section 13.2(b), governs as it governs that objection; a dataset not yet used is never content that cannot be separated; HIPS makes available to you, at your request, free of charge, without hindrance, within a reasonable time and in a commonly used and machine-readable format, the content other than personal data that you provided or created using the Services and that HIPS still holds, including the results of task Requests and jobs and the Batch Files of the Workspace, except content that has no use outside the Services, relates only to your use of the Services, has been combined with other data so that it cannot be separated or only with disproportionate effort, or was created jointly with other persons who continue to use it; HIPS does not otherwise use that content, except as this Section allows for Training; and HIPS handles personal data as Regulation (EU) 2016/679 requires.

27.8

Changes to the Services. HIPS changes the Services it supplies to you, beyond what is needed to keep them in conformity, only for a reason listed in Common Clauses Section 9.1, without additional cost to you, and after telling you clearly about the change. If a change negatively affects your access to or use of the Services, and the effect is more than minor, HIPS tells you reasonably in advance on a Durable Medium of the characteristics and the time of the change, and you may terminate the contract free of charge within thirty (30) days after you receive that information or after the change is made, whichever is later; HIPS then refunds your unused Purchased Credits and the unused part of any prepaid Plan fee. This right does not arise where HIPS lets you keep the Services without the change, at no additional cost and in conformity.

27.9

Credits and closure. As a Consumer:

  1. (a)HIPS reminds you before your Purchased Credits expire (Section 8.5);
  2. (b)HIPS closes your Account or a Workspace with immediate effect only for a serious ground under Section 24.2, and on any other ground gives you notice under Section 24.7;
  3. (c)on a closure for cause, HIPS refunds the remainder of your unused Purchased Credits and prepaid Plan fee after deducting only what Section 24.6 allows it to deduct from a Consumer; and
  4. (d)you may terminate at any time under Section 24.1, and your rights under Sections 27.4, 27.8 and 27.12 are not affected.
27.10

Liability. Common Clauses Sections 5.5 (foreseeable loss), 5.8 (no cap for Consumers) and 5.11 (matters outside HIPS's responsibility for Consumers) apply to you, and Common Clauses Section 6.3 applies instead of the indemnities. Nothing in them limits HIPS's liability under Common Clauses Section 5.1 or your remedies when the Services are not in conformity.

27.11

Important for Consumers: your courts and your law

Disputes. Every Dispute is resolved on the Consumer Track of Common Clauses Section 15. Its central provisions read:

Common Clauses Section 15.2: "The Agreement and every Dispute are governed by the laws of Ireland. As a Consumer, you also keep the protection of the provisions of the law of the country where you have your habitual residence that cannot be derogated from by agreement, and the choice of Irish law does not deprive you of that protection." Common Clauses Section 15.3: "You may bring proceedings against HIPS in the courts of the country where you are domiciled or in the courts of Ireland. HIPS may bring proceedings against you only in the courts of the country where you are domiciled." Common Clauses Section 15.4: "Sections 13 and 14, including their agreements to arbitrate and their waivers of class, collective and representative proceedings, do not apply to you. Nothing in the Agreement requires you to submit a Dispute to arbitration."

Common Clauses Section 15.6 sets out how HIPS answers your complaints and the out-of-court dispute resolution available to you.

27.12

Refund of unused Purchased Credits. HIPS refunds you, on your request made within three (3) years after the day on which the Credits expired, or on which you closed your Workspace or your Account, the price of Purchased Credits that expired unused, or that remained unused when you closed your Workspace or your Account, less the fee that the payment processor charges HIPS for the refund. HIPS makes the refund under Section 12.1 and removes the Credits it covers.

Section 27
  1. 27.1Who this Section applies to
  2. 27.2Your statutory rights
  3. 27.3Characteristics you accept expressly
  4. 27.4Your right of withdrawal
  5. 27.5How to withdraw
  6. 27.6If you want to start at once
  7. 27.7Your content when a contract ends
  8. 27.8Changes to the Services
  9. 27.9Credits and closure
  10. 27.10Liability
  11. 27.11Disputes
  12. 27.12Refund of unused Purchased Credits
Copy link

28United States

28.1

Who this Section applies to. This Section 28 applies to you if you are a US User, whether you are a Consumer or a Business User. Sections 26 and 27 do not apply to you. If you are a Consumer, nothing in this Section 28 limits a right that the law of your state gives you and does not allow to be waived.

28.2

Important for US Users: binding individual arbitration, class and jury waiver, and opt-out

Disputes. Every Dispute is resolved on the US Track of Common Clauses Section 14, under the laws of the State of Delaware and the Federal Arbitration Act. Its central provisions read:

Common Clauses Section 14: "PLEASE READ THIS SECTION CAREFULLY. IF YOU ARE A US USER, IT REQUIRES YOU AND HIPS TO RESOLVE DISPUTES BY BINDING INDIVIDUAL ARBITRATION, EXCEPT IN SMALL CLAIMS COURT AND FOR THE OTHER CLAIMS SECTION 14.3 LISTS. YOU AND HIPS WAIVE THE RIGHT TO A JURY TRIAL AND THE RIGHT TO BRING OR TAKE PART IN A CLASS, COLLECTIVE OR REPRESENTATIVE ACTION OR ARBITRATION. YOU MAY OPT OUT OF ARBITRATION WITHIN THIRTY (30) DAYS, AS SECTION 14.13 DESCRIBES." Common Clauses Section 14.9: "YOU AND HIPS MAY BRING CLAIMS AGAINST EACH OTHER ONLY IN AN INDIVIDUAL CAPACITY, AND NOT AS A PLAINTIFF, CLAIMANT OR CLASS MEMBER IN ANY PURPORTED CLASS, COLLECTIVE, CONSOLIDATED, PRIVATE ATTORNEY GENERAL OR REPRESENTATIVE PROCEEDING. UNLESS YOU AND HIPS AGREE OTHERWISE IN WRITING, AND EXCEPT AS SECTION 14.10 PROVIDES, THE ARBITRATOR MAY NOT CONSOLIDATE THE CLAIMS OF MORE THAN ONE PERSON, MAY NOT PRESIDE OVER ANY FORM OF CLASS, COLLECTIVE OR REPRESENTATIVE PROCEEDING, AND MAY AWARD RELIEF ONLY TO THE INDIVIDUAL CLAIMANT. YOU AND HIPS WAIVE ANY RIGHT TO A JURY TRIAL FOR EVERY DISPUTE THIS ARBITRATION AGREEMENT COVERS." Common Clauses Section 14.13: "You may opt out of this Arbitration Agreement by notice to the address in Section 10.3 within thirty (30) days after the earlier of (a) your first acceptance, while you are a US User, of an Incorporating Document that contains this Arbitration Agreement, and (b) the day HIPS notifies you on a Durable Medium, after your Country becomes the United States, that this Arbitration Agreement applies to you. HIPS sends that notice when it records the change of your Country. Until one of these events occurs, this Arbitration Agreement does not apply to you. The notice must state your name, the email address of your Account and that you opt out of arbitration with HIPS. It must be sent by you personally or, for an organization, by a person authorized to act for it, and a notice sent for more than one person is not valid. If you opt out, the rest of the Agreement continues to apply and Disputes are resolved under Section 14.14. An opt-out from an earlier version remains effective without a new notice."

Common Clauses Sections 14.1 to 14.16 apply in full, including the small claims and public injunctive relief exceptions (Common Clauses Sections 14.3 and 14.12), batch arbitration (Common Clauses Section 14.10) and the courts for Disputes that are not arbitrated (Common Clauses Section 14.14).

28.3

Payment in the United States. As a US User, you pay by card only, Machine Payments included (Section 10.11), on every Plan, including top-ups on the Free/PAYG Plan. HIPS never offers you MTO in any form: no MTO payment, no MTO discount, no holding benefit, no wallet connection and no MTO information in the Console. HIPS offers you no payment in USDC or any other Crypto-Asset (Common Clauses Section 3.11(b)).

28.4

Termination at will. In addition to Section 24, HIPS may suspend or terminate your Account, any Workspace or these Terms at any time, for any reason or no reason, with or without notice. When HIPS does so other than for a ground in Section 24.2, HIPS refunds your unused Purchased Credits and the unused part of any prepaid Plan fee, and if you are also a Provider, the Provider Agreement governs your Earnings.

28.5

Prepaid balances. Purchased Credits expire twelve (12) months after purchase (Section 8.5), and Section 24.6(c) applies to you. Purchased Credits are a prepayment for the Services, not a gift card or gift certificate: they are not sold or marketed as one and cannot be transferred (Common Clauses Section 3.7). Where the law of your state does not allow Purchased Credits to expire, or to expire as early, they expire only when that law allows, or do not expire; and where it requires a refund of unused Purchased Credits, HIPS makes it as that law provides. Where the unclaimed property law of a state requires HIPS to report and deliver to it the value of unused Purchased Credits or any other amount HIPS owes you, HIPS does so, removes the Credits concerned, and the delivery discharges HIPS's obligation to you for that value.

28.6

Important for US Users: limit of liability

Disclaimers and limit of liability. Common Clauses Sections 4.3 (disclaimer of warranties) and 5.4 (excluded damages) apply to you, and Common Clauses Section 5.7 provides:

"EACH PARTY'S TOTAL AGGREGATE LIABILITY TO THE OTHER ARISING OUT OF OR RELATING TO AN AGREEMENT OR THE SERVICES, FOR ALL CLAIMS TOGETHER AND UNDER ANY THEORY OF LIABILITY, IS LIMITED TO THE GREATER OF (a) FOR A CLAIM ARISING FROM YOUR USE OF THE SERVICES AS A BUYER, THE TOTAL FEES YOU PAID HIPS IN THE TWELVE (12) MONTHS BEFORE THE FIRST EVENT GIVING RISE TO LIABILITY, AND, FOR A CLAIM ARISING UNDER THE PROVIDER AGREEMENT, THE GREATER OF THE TOTAL EARNINGS HIPS PAID YOU AND THE TOTAL EARNINGS HIPS SETTLED AS PAYABLE FOR YOU IN THOSE TWELVE (12) MONTHS, AND, FOR A CLAIM ARISING UNDER THE AFFILIATE PROGRAM AGREEMENT, THE TOTAL COMMISSIONS HIPS PAID YOU UNDER IT IN THOSE TWELVE (12) MONTHS (THE GREATEST OF THOSE AMOUNTS FOR THE CAPACITIES CONCERNED WHERE A CLAIM ARISES IN MORE THAN ONE CAPACITY); AND (b) ONE HUNDRED UNITED STATES DOLLARS (US$100), WHATEVER THE CAPACITY IN WHICH THE CLAIM ARISES. THESE LIMITS APPLY EVEN IF A LIMITED REMEDY FAILS OF ITS ESSENTIAL PURPOSE."

28.7

Sales tax. Fees do not include sales, use or similar taxes. Where HIPS is required to collect such a tax from you, it adds the tax to your payment; you are responsible for any such tax HIPS is not required to collect, and Section 11.8 applies.

28.8

Payment without set-off. You pay every amount due to HIPS in full, without set-off, counterclaim, deduction or withholding, except as Section 11.7 provides.

28.9

Electronic communications. You consent to receive the Terms, notices, receipts, disclosures and other communications from HIPS electronically, by email or in the Console, and agree that they satisfy any requirement that they be in writing. You may withdraw this consent by notice to HIPS; because HIPS provides the Services only online, HIPS may then close your Account under Section 28.4.

28.10

Automatic renewal. Before you subscribe to a paid Plan, HIPS shows you clearly the price, the billing period, that the subscription renews automatically until you cancel, and how to cancel, and it asks for your express consent. You can cancel online in the Console at any time, effective at the end of the current period. HIPS sends you the confirmations and reminders that the automatic renewal laws of your state require.

28.11

California consumers. If you are a Consumer resident in California, HIPS gives you the following information under section 1789.3 of the California Civil Code when you accept these Terms and each year on or before June 30: (a) the Services are provided by HIPS Payment Group Limited, whose address and telephone number are on the Legal Information Page; (b) HIPS charges you for the Services only the Fees of your Plan and the Price List (Sections 7 to 9), plus any taxes Section 28.7 describes; and (c) you may complain to HIPS about the Services through the contact on the Legal Information Page, find further information about using the Services in the HIPS documentation, and contact the Complaint Assistance Unit of the Division of Consumer Services of the California Department of Consumer Affairs in writing at 1625 North Market Blvd., Suite N 112, Sacramento, California 95834, or by telephone at (800) 952-5210.

28.12

Export controls. You shall comply with the export control and sanctions laws of the United States in your use of the Services and of Outputs, in addition to Common Clauses Section 7.

Section 28
  1. 28.1Who this Section applies to
  2. 28.2Disputes
  3. 28.3Payment in the United States
  4. 28.4Termination at will
  5. 28.5Prepaid balances
  6. 28.6Disclaimers and limit of liability
  7. 28.7Sales tax
  8. 28.8Payment without set-off
  9. 28.9Electronic communications
  10. 28.10Automatic renewal
  11. 28.11California consumers
  12. 28.12Export controls
Copy link

29Changes, notices and general terms

29.1

Changes to these Terms. HIPS changes these Terms only for a reason listed in Common Clauses Section 9.1, with notice under Common Clauses Section 9.2, and Common Clauses Sections 9.3 to 9.6 govern changes that take effect sooner, your right to leave with the refunds it provides, the acceptance of a change, and the rule that a change does not apply retroactively.

29.2

Changes to prices and Plans. Section 9.8 governs changes to the rates of the Price List, Section 7.3 changes to a Plan fee, and Section 6.12 changes to the Services (Common Clauses Section 9.7).

29.3

Notices. Common Clauses Section 10 governs notices. HIPS gives notices to the email address of your Account and in the Console; a notice that concerns a Workspace is given to its Owner and, for payments, to its Billing Members.

29.4

Assignment. Common Clauses Section 11 governs assignment. You may not transfer a Workspace, its Credits or these Terms without HIPS's prior written consent.

29.5

Force majeure. Common Clauses Section 8 governs force majeure, including that HIPS does not charge for a Request that the Services did not perform because of a force majeure event (Common Clauses Section 8.4).

29.6

Severability. Common Clauses Section 16 governs severability. Each Section of these Terms, each numbered clause and each lettered item is a separate and independent provision, and a clause written for one population is a separate provision for that population only.

29.7

Entire agreement and no reliance. Common Clauses Section 17 governs the entire agreement, no reliance on statements outside your Agreement, the order of precedence, HIPS's records, waiver, third-party rights and electronic conclusion.

29.8

Language. Common Clauses Section 18 governs language. These Terms are concluded in English, and the English text is the binding text.

29.9

Sanctions. Common Clauses Section 7 governs sanctions and export control, and a breach of it is a material breach of these Terms.

29.10

Survival. Besides the provisions Common Clauses Section 19 lists, the following survive the end of these Terms: Sections 1.8, 4.6, 4.7, 5.4, 6.22, 8.6, 8.8, 8.10(c), 9, 10.9, 10.10, 10.11(c), (d) and (h), 11, 12, 13.8 to 13.12, 14, 15.4, 15.5, 15.11, 15.12, 16, 20, 21, 24.6, 24.8, 24.10, 25, 26, 27, 28 and this Section 29.

Section 29
  1. 29.1Changes to these Terms
  2. 29.2Changes to prices and Plans
  3. 29.3Notices
  4. 29.4Assignment
  5. 29.5Force majeure
  6. 29.6Severability
  7. 29.7Entire agreement and no reliance
  8. 29.8Language
  9. 29.9Sanctions
  10. 29.10Survival
Copy link

30Contact

HIPS is HIPS Payment Group Limited (registered name HIPS PAYMENT GROUP LIMITED), which trades as HIPS, a company incorporated in Ireland and registered with the Companies Registration Office under number 639131, with its registered office at 5 The Courtyard Building, Carmanhall Road, Sandyford, Dublin 18, Ireland; its VAT number is shown on each invoice (Common Clauses Section 3.1). Hyperscale Inference Processing Systems OÜ, of Estonia, operates the Services for HIPS and is not a party to these Terms. The Legal Information Page sets out HIPS's particulars, any business name under which it trades, its single points of contact for authorities and for users, the list of Restricted Jurisdictions, the current list of sub-processors, the Device Countries (Section 17.3), the criteria, protections and data centers of the Approved Providers (Sections 17.1, 17.4 and 17.6), the Consumer Health Data Privacy Policy (Section 13.2(b)), the information of Section 24.10(g), and every version of these Terms and of the Common Clauses.

Legal notices, Notices of Dispute, withdrawals, switching requests, and US arbitration opt-outs and rejections
legal@hips.com
Postal address
HIPS Payment Group Limited, 5 The Courtyard Building, Carmanhall Road, Sandyford, Dublin 18, Ireland
Privacy questions and requests
hello@hips.com
Support, abuse reports and security issues
the channels listed on the Legal Information Page
Section 30
Copy link

Terms of Service, version 1.0, superseded on 2026-11-16 by version 1.1, last updated 2026-10-27, by Hyperscale Inference Processing Systems OÜ. It is not in force. Questions about it go through Contact HIPS.

Other legal documents

  • 01Terms of Service
  • 02Privacy Notice
  • 03Acceptable Use Policy
  • 04Data Processing Agreement
  • 05Provider Agreement
  • 06Affiliate Program Agreement
  • 07Common Clauses
  • 08Early-Access Privacy Notice
  • 09Cookie Notice
  • 10Biometric Data Retention and Destruction Policy
  • 11Consumer Health Data Privacy Policy
  • 12Website Terms of Use
  • 13Vulnerability Disclosure Policy
  • 14Model Withdrawal Form

Product

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

Developer

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

Provider

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

Resource

  • Security and Data
  • Resources
  • llms.txt

Compare

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

Company

  • About
  • Contact
  • Affiliate program
  • HIPS Payments

Legal

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

Support

  • Contact HIPS
  • Looking for payments support?

HIPS. AI inference for builders.

hips.com

Hyperscale Inference Processing Systems OÜ