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

Privacy Notice.

What personal data HIPS collects, why, who receives it, how long it is kept, and the rights you have.

SupersededSuperseded on 2026-10-27 by version 1.2. The version in force

About this document
Entity
HIPS Payment Group Limited
Status
Superseded on 2026-10-27 by version 1.2
Applies to
Website visitors, early-access registrants, buyers (businesses and consumers) and Workspace Members, providers, Program Partners of the Affiliate Program and the people they refer, and people who contact HIPS
Acceptance
Not accepted: this Notice gives information to everyone whose personal data HIPS processes. The version shown when you accept the Terms of Service, the Provider Agreement or the Affiliate Program Agreement is recorded with that acceptance.
Version
1.1
Last updated
2026-10-27
In effect from
2026-10-27
Length
16 sections23 defined terms
Questions
hello@hips.comSection 16
Contents0% read
  1. The commitments in brief
  2. 1Who we are and the scope of this Notice
  3. 2Controller and processor roles
  4. 3Personal Data we collect
  5. 4How we use Personal Data and our legal bases
  6. 5Automated decisions and profiling
  7. 6Request Content and model training
  8. 7Retention
  9. 8Security
  10. 9Recipients and Sub-processors
  11. 10International transfers
  12. 11Your rights
  13. 12Children
  14. 13Cookies and similar technologies
  15. 14Information for particular countries
  16. 15Changes to this Notice
  17. 16Contact
Contents16 sections
  1. The commitments in brief
  2. 1Who we are and the scope of this Notice
  3. 2Controller and processor roles
  4. 3Personal Data we collect
  5. 4How we use Personal Data and our legal bases
  6. 5Automated decisions and profiling
  7. 6Request Content and model training
  8. 7Retention
  9. 8Security
  10. 9Recipients and Sub-processors
  11. 10International transfers
  12. 11Your rights
  13. 12Children
  14. 13Cookies and similar technologies
  15. 14Information for particular countries
  16. 15Changes to this Notice
  17. 16Contact

This Privacy Notice (the Notice) explains how HIPS Payment Group Limited (HIPS, we, us or our) collects, uses, discloses and otherwise processes Personal Data, itself and through Hyperscale Inference Processing Systems OÜ, which operates the Service for HIPS as its Processor (Section 2.7), in connection with the HIPS inference marketplace, including the Website, the early-access program, the Console, the HIPS API and SDK, and the Provider App, and the rights available to the individuals concerned. This Notice gives information; it is not a contract, and nobody accepts it. The terms on which HIPS supplies the Service are in the Terms of Service, the Provider Agreement, the Affiliate Program Agreement and the Common Clauses they incorporate, and the DPA for Business Users. Capitalized terms are defined in Section 1.6.

The commitments in brief

  • Who HIPS is. HIPS is HIPS Payment Group Limited, an Irish company, the Controller of the Personal Data this Notice describes (Section 2). Hyperscale Inference Processing Systems OÜ, an Estonian company, operates the Service for HIPS as its Processor, only on HIPS's instructions, and uses the data for nothing of its own (Sections 1.1 and 2.7).
  • HIPS sells and buys in its own name. HIPS sells inference to Buyers and buys GPU time from Providers as the principal on both sides. It keeps the records of each side as its own and does not tell either side who the other is, with one exception that data protection law calls for: a Buyer that is a Business User and the Controller of Personal Data that a Provider's Device processed may see that Provider's name, Country and contact address, which HIPS gives under a duty of confidentiality (Sections 1.3 and 9.3).
  • Request content is not stored by default, except for training where your plan allows it and in the cases Section 7.1 lists. Prompts, inputs and generated outputs are processed to answer a request and are not stored, except that a copy may be kept for training on plans whose policy allows it; the files of a batch you submit are kept for thirty (30) days, an input file still used by an open batch until that batch ends, and then deleted, sooner if you set a shorter expiry or delete them (a training copy made from a batch where your plan allows training is not removed by deleting the file; Section 6.6 says how to exclude it); the body of an asynchronous job is kept until the job ends; the answer to a task request sent with an idempotency key is kept for twenty-four (24) hours so that a retry returns it without a second charge; and in the other cases Section 7.1 lists.
  • Your plan sets the training policy. On Free/PAYG and the lower paid plan, request inputs and outputs may be used for training; on the higher paid plan, it is off by default. The same rule applies to the files of a batch. If you are a consumer in the United States, training is off unless you turn it on (Section 14.4(g)).
  • Consumers: training on legitimate interest, and one switch to say no. If you are a consumer outside the United States, HIPS trains on your request content on the basis of its legitimate interest, after weighing it against yours, and brings your right to object to your attention, separately from any other information, before your first request. You can object at any time with one switch in the Console, without giving a reason, and keep your plan (Section 6.10). If you are a consumer in the United States, HIPS does not train on your request content unless you turn training on, by a separate consent that meets the consumer health data laws of Washington and Nevada (Section 14.4(g)). Anyone may object to training on personal data that concerns them (Section 11.2). HIPS waits at least thirty (30) days after it writes a training copy before it first uses it, so that an objection made in that time removes the copy first, and keeps training copies for no longer than twenty-four (24) months (Sections 6.6 and 6.10(i)). Before it writes any training copy, HIPS's automated filters screen out requests whose input or output reveals sensitive data, such as data about health, religion, politics or sex life, or that concern a child, and a request the filters cannot assess is not used (Section 6.6). Filters can miss some content, so leave such data out where you can. HIPS trains only models it runs itself, and never sells or discloses training data, or the weights of the models trained on it, to any third party, except where the law or a binding order of a court or authority requires it, or to a successor that takes over the Service and is bound by the same commitment; a service provider that handles them only for HIPS is not a third party. HIPS treats every model trained on request content as containing personal data: it runs only on data-center capacity in the European Economic Area or in a country, territory or sector whose adequacy decision covers it, never on a personal Device, and is offered only to buyers in the European Economic Area or whom such an adequacy decision covers (Sections 6.10(a), 9.8 and 10.5). Customer-owned model weights are never used to train other models.
  • Every identity check includes a face check, and you choose how; HIPS stores only the result. Bynn, HIPS's verification provider, checks your identity document. For the face check you choose, without giving a reason, between the automated face check, which compares your face with the photograph in your identity document and runs only with your explicit consent, and the face check by a person, in which a person at HIPS sees you on a video call that is never recorded, with no automated processing of your face. Both have the same effect, and HIPS keeps no record of which you used. If you decline both, you cannot complete verification, and without it you receive no Credits, cannot buy, cannot use inference for yourself or as a Member, and cannot earn as a Provider or a Program Partner. HIPS itself stores only the result and keyed hashes from which your document details cannot be read without HIPS's secret key, never a document image or biometric data, except the documents you send for a check of other evidence by a person after a deletion, which it deletes shortly after the check (Sections 3.1, 3.7, 7.6 and 11.5).
  • Prompt caches stay inside your Workspace. Caching is automatic. A cache is kept apart for each Workspace, and, in a consumer's Workspace, for each Member and API key unless an owner lets them share one; it lives only in the memory of a data-center worker, never on its disk, and becomes unreadable within twenty-four (24) hours and at once when the Workspace is deleted, after which HIPS clears it from the worker's memory within a further twenty-four (24) hours; personal devices keep no cache between requests at launch. To bill cached tokens, HIPS keeps, for each Workspace, pseudonymized hashes of blocks of your prompt, from which HIPS cannot read the prompt (Section 6.12).
  • No cookie crosses hosts. Every HIPS cookie belongs to one host only, and you give your cookie choice once on hips.com and once on console.hips.com. A referral code reaches the Console in the link, never in a shared cookie, and HIPS's edge removes from every request each cookie that is not one of the cookies this Notice lists, without logging it (Section 13).
  • The Affiliate Program. If you take part, HIPS records your referrals, commissions and payouts and checks them for self-referral and fraud. It never tells a Program Partner who was referred, or what a referred person paid or was paid, unless the law requires it, and shows a Program Partner its referrals and commissions only as totals, never one referral or its state. Each payout pays commissions from at least the number of referrals that Section 3.8(c) sets, so it does not show what one referral earned, except a last payout when the Program Partner leaves or the Affiliate Program 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; such a payout to a Program Partner with few referrals can show approximately what one referral earned (Sections 3.8 and 9.3).
  • Your country is where you live. The country rules that apply to you follow the country of your habitual residence, which you declare and HIPS checks, never your nationality or the country that issued your identity document (Section 4.3).
  • Providers: the Provider App reports your hardware, not what you do. The app decides on your computer when it may work and sends HIPS only that decision, its reasons as codes (for example that the camera is in use or a game is running, never which one) and measurements such as GPU load and temperature, never the names of your applications, games or windows, your keystrokes, your screen or your computer's name. It also sends your computer's hardware inventory and the serial numbers, UUIDs and MAC addresses of its hardware, which HIPS keeps as the app reports them and which only HIPS's authorized personnel can read, to schedule work, to recognize a machine and a GPU, and to keep hardware involved in fraud or other abuse from returning under another account, with a review by a person at HIPS for anyone who holds that hardware later and an entry on the hardware blocklist that lapses after three (3) years unless renewed on a new finding (Sections 3.1, 3.5 and 3.9). Only if you agree when you enroll a Device, it also sends crash reports: where in its code the app stopped, its versions, your GPU and driver, and its recent events, never its memory, your work or your computer's name; you can turn them off at any time with one switch (Section 3.10).
  • Where your data is. HIPS keeps account data, billing records and backups in Ireland, and processes requests in its regional processing locations in Ireland, the United States and Japan, and on data-center capacity and Devices reached from them. A request to ai.hips.com is first decrypted, in memory only, at the edge location of HIPS's content delivery network nearest you, which may be in any country (Section 10.2(c)). A request without a region requirement may be served in any region. Once region selection is offered, a Workspace on the higher paid plan may require a region, and uses that region's own address where the connection itself must stay there. Devices take requests only in the countries Section 10.3 opens, and Buyers and Devices never connect to each other directly (Sections 9.3 and 10).
  • Providers give the tax information the law requires. Before HIPS pays a Provider, it collects the tax details that tax withholding and reporting rules call for, such as a taxpayer identification number, an address, a date of birth and, for the United States, Form W-9 or a self-certification of foreign status, and it reports payments to tax authorities where those rules require (Sections 3.2, 4.2 and 9.4). It never asks for a national identity or tax number whose collection the law of your country restricts, such as Japan's Individual Number or Australia's tax file number (Section 3.2).
  • No crypto. HIPS accepts no crypto-asset payment, makes no crypto-asset payout, connects no wallet and offers no benefit for holding a crypto-asset. Payouts go in money to a bank account in your own name (Section 9.6). In Japan, Singapore, the Republic of Korea, Taiwan and Australia, payouts are made through Stripe Global Payouts once it opens in your country; until then you may enroll and HIPS runs only unpaid test work on your Devices, and no bank payout is available yet in the Republic of Korea (Section 3.3). HIPS never encourages or advises anyone to acquire, hold, sell or trade MTO or any other crypto-asset. Crypto-assets carry extreme risk, including the total loss of their value; any such decision is your own, and you should take advice from your own independent financial, legal and tax advisors (Section 3.4 and Common Clauses Section 3.12).
  • Your right to object. You may object at any time to processing based on HIPS's legitimate interests, and to direct marketing without giving a reason (Section 11.2).
  • Your other rights. Access, rectification, erasure, restriction and portability, withdrawal of consent, human review of automated decisions (Section 5), deleting your Account at any time, which HIPS never refuses because Earnings or commissions are pending (Section 11.5), and a complaint to the Data Protection Commission of Ireland or the supervisory authority where you live or work (Section 11.7). Section 14 adds what the law of particular countries gives you, among them Japan, the Republic of Korea, Singapore, Taiwan and Australia.
Before section 1
  1. The commitments in brief
Copy link

01Who we are and the scope of this Notice

1.1

The Controller. HIPS Payment Group Limited (registered name HIPS PAYMENT GROUP LIMITED), trading as HIPS, is a company incorporated in Ireland, 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. HIPS is the Controller of the Personal Data this Notice describes, except where Section 2 states otherwise. Hyperscale Inference Processing Systems OÜ, of Estonia (the Operating Company), operates the Service for HIPS as HIPS's Processor (Section 2.7). HIPS's main establishment in the European Union is in Ireland, where it decides how and why the Personal Data this Notice describes is processed, so the Data Protection Commission of Ireland is its lead supervisory authority for cross-border processing (Article 56 of the GDPR). HIPS's contact details, and those of its data protection officer, who is also its data protection officer under the law of Singapore (Section 14.7) and its chief privacy officer under the law of the Republic of Korea (Section 14.6), are in Section 16, and its representatives in the United Kingdom and Switzerland in Sections 14.1 and 14.2.

1.2

Who this Notice covers. This Notice applies to:

  1. (a)visitors to the Website;
  2. (b)people who register for early access or send HIPS an inquiry;
  3. (c)Buyers, whether Business Users or Consumers, and the Members of their Workspaces;
  4. (d)Providers who supply GPU Time through the Provider App, the representatives of Providers that are organizations, and the representatives of Approved Providers;
  5. (e)Program Partners in the Affiliate Program, and the people they refer, once the program opens;
  6. (f)people whose Personal Data a Consumer includes in Request Content, or is in a training copy of which HIPS is the Controller, for the processing Sections 2.3 and 2.4 describe; and
  7. (g)anyone else who contacts HIPS.

For early-access registrations, the early-access privacy notice shown on the forms is the notice recorded with your registration. Sections 3.1, 4.1 and 7.4 of this Notice describe the same processing and do not change it. Before the Affiliate Program opens, HIPS updates the early-access privacy notice to describe the referral data of Section 3.8(b) stored with a registration, and stores none until it has.

1.3

HIPS sells and buys in its own name. 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 is the principal on both sides: it sells inference to Buyers in its own name, as the merchant of record for every payment, and it buys GPU Time from Providers for its own account, paying them from its own money through its own Stripe account. HIPS is nobody's agent and holds no money for anyone. For your Personal Data this means:

  1. (a)HIPS is the Controller of the commercial records of both sides: what Buyers buy, use and pay, and what Providers supply and are paid;
  2. (b)a Buyer's payment data goes to HIPS and its payment processor, never to a Provider;
  3. (c)a Provider's payout and Tax Information goes to HIPS, its payout processor and the tax authorities that Section 9.4 names, never to a Buyer; and
  4. (d)HIPS does not disclose the identity of either side to the other, except that, so that a Controller can know who processes its Personal Data (Article 28 of the GDPR), a Buyer that is a Business User and the Controller of Personal Data that a Provider's Device processed may receive that Provider's name, Country and contact address under a duty of confidentiality (Section 9.3).
1.4

HIPS Payments. HIPS Payments is a payment business carried on under the HIPS Payments name by legal entities other than HIPS and the Operating Company, whose address is https://hipspay.com. It is not part of the Service. HIPS, despite the word in its name, 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 Service, makes payments only of its own debts, and carries on no part of the HIPS Payments business. HIPS does not disclose Personal Data to HIPS Payments, and an account with HIPS Payments is separate from an Account. HIPS's systems run in an Amazon Web Services account and a Kubernetes cluster that also hold the separate systems of HIPS Payments, isolated from them by their own namespaces, nodes, network rules, databases, caches, keys, roles and logs; no system or person of HIPS Payments receives Personal Data that HIPS processes or has access to it, and anyone who administers that shared infrastructure for HIPS does so only on HIPS's instructions and under a duty of confidentiality, and HIPS itself holds that Amazon Web Services account, under the data processing terms of Amazon Web Services (Section 9.1). The entities of HIPS Payments process their customers' data under their own privacy notices, at the address that the Legal Information Page gives (Common Clauses Section 3.2(h)).

1.5

Parts not yet available. The Service opens in stages, beginning with the early-access website. Where this Notice describes a part of the Service that has not opened, such as the Console, the API, Batches, the Provider App, paid plans, payouts or the Affiliate Program, HIPS collects no Personal Data through that part until it opens, and the description states how HIPS will process Personal Data when it does. HIPS offers no crypto-asset payment, payout or benefit (Section 9.6). Training jobs, through which a Customer trains models on its own datasets, and the HIPS MCP server are not described in this Notice; HIPS collects no Personal Data through them, and updates this Notice and the DPA before they open.

1.6

Defined terms. In this Notice:

Account
has the meaning given in Common Clauses Section 2.1, the user account a natural person holds to sign in to the Console or the Provider App. An Account may be a Member of one or more Workspaces and a Provider at the same time. HIPS links every Account that resolves to the same verified person; a linked Account is kept, receives no further Free Allowance or Referral Discount, and gives the person no second provider account or participation in the Affiliate Program (Section 5.2).
Affiliate Program, Affiliate Program Agreement and Program Partner
have the meanings given in Common Clauses Section 2.1. The Affiliate Program is shown on the Website as the Affiliate program and in the Console as Refer and earn (Section 3.8); it has nothing to do with the term Affiliate, which Common Clauses Section 2.1 defines as a legal person that controls HIPS, that HIPS controls or that is under common control with HIPS, and which this Notice never uses for the program or its participants.
Applicable Law, Approved Pool, Approved Provider, Business User, Buyer, Console, Consumer, Country, Credits, Customer Model, Device, Earnings, EEA, GPU Time, Input, Member, Personal Pool, Provider, Provider App, Purchased Credits, Request Data, Settlement and Workspace
have the meanings given in Common Clauses Section 2.1. Section 4.3 explains how your Country is established.
Batch, Batch File, Batch Line, Batch Rates and Completion Window
have the meanings given in Common Clauses Section 2.1. Section 6.11 describes how HIPS runs a Batch, and "the lines of a Batch" are its Batch Lines.
Common Clauses
the HIPS Common Clauses, which the Terms of Service, the Provider Agreement, the Affiliate Program Agreement and the Acceptable Use Policy incorporate.
Controller, Processor and Personal Data
have the meanings given in the GDPR.
Customer
the Buyer that holds a Workspace, whether a Business User or a Consumer; where this Notice refers to the DPA, the Customer is a Customer that is a Business User, as the DPA defines it.
DAC7
Council Directive (EU) 2021/514, which sets the reporting rules for digital platform operators, and the Irish rules that apply it (section 891I of the Taxes Consolidation Act 1997).
Device Country
a country in which a Device may take Requests of Buyers, as Section 10.3 states.
DPA
the HIPS Data Processing Agreement published at /legal/dpa, between HIPS and a Customer that is a Business User, as Common Clauses Section 2.1 defines it.
Free Allowance and Referral Discount
have the meanings given in Terms of Service Section 2.2, and Request the meaning given in Common Clauses Section 2.1. HIPS grants a Free Allowance only where the Price List states one, and grants none at launch; where this Notice mentions the Free Allowance, it means any Free Allowance HIPS grants.
GDPR
has the meaning given in Common Clauses Section 2.1, Regulation (EU) 2016/679, the General Data Protection Regulation.
Operating Company
has the meaning given in Common Clauses Section 2.1: Hyperscale Inference Processing Systems OÜ, which operates the Service for HIPS (Section 2.7).
Prefix Ledger
has the meaning given in the Terms of Service: the record HIPS keeps of pseudonymized hashes of blocks of the tokens of the Inputs of Requests to language models served by data-center workers whose prompt cache is on, keyed for each cache scope as Terms of Service Section 13.7 states, with the worker that served each Request and the time, used only as Terms of Service Section 13.7 describes (Section 6.12). Its hashes are derived from Request Content and are Personal Data wherever the prompt contained Personal Data: HIPS cannot read a prompt from them, but could check with them whether a Workspace sent a known text. The Prefix Ledger does not keep the text of a prompt.
Referred Person
a person whom HIPS attributes to a Program Partner as a new Buyer, a new Provider, or both, as the Affiliate Program Agreement defines it.
Provider Agreement
has the meaning given in Common Clauses Section 2.1, the HIPS Provider Agreement.
Request Content
Request Data as the Common Clauses define it: the inputs of a Request sent to the Service (prompts, messages and uploaded inputs) and the outputs generated from them. The lines of a Batch are Requests, and the content of its Batch Files is Request Content.
Service
the Services as Common Clauses Section 2.1 defines them, together with the Website.
Sub-processor
a service provider that processes Personal Data on HIPS's behalf and under its instructions, as HIPS's Processor where HIPS is the Controller, and as its sub-processor where HIPS is a Processor for a Business User (Sections 2.5 and 9.1).
Training
has the meaning given in the Terms of Service: 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 Section 9.5(f) and is bound by this provision; a service provider that processes them only on HIPS's behalf and under its instructions is not a third party for this purpose. A model that HIPS trains on Request Data runs only on data-center capacity of the Approved Pool located in the EEA or in a country, territory or sector for which an adequacy decision of the European Commission under Article 45 of Regulation (EU) 2016/679 is in force, and never on a Device of the Personal Pool, and is offered only to Buyers whose Country is in the EEA or in a country, territory or sector for which an adequacy decision of the European Commission under Article 45 of Regulation (EU) 2016/679 is in force and covers that Buyer, which, for a Buyer in Japan or the Republic of Korea, HIPS establishes from the Buyer's confirmation in the Console that it is subject to the law the decision names and does not use the model for a purpose the decision excludes (so never a Buyer in the United States that is not certified under the EU-U.S. Data Privacy Framework, or a Buyer in Canada that the Personal Information Protection and Electronic Documents Act does not cover). HIPS treats every model it trains on Request Data as containing personal data, and does not host or offer such a model anywhere else or to any other Buyer. HIPS 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 Terms of Service Section 13.13, with its own assessment, and would apply only to Request Data HIPS accepts after it takes effect. Sections 6.10(a), 9.8 and 10.5 describe how HIPS applies it. A training copy is a copy of Request Content that HIPS keeps for Training.
Tax Information
for a Provider, the information that Provider Agreement Section 15.2 defines as Tax Information; for a Program Partner, the same information where a tax rule requires it for their commissions. The table in Section 3.2 also lists, beside it, the declaration of status that Provider Agreement Section 3.4 governs.
Usage Data
the operational metadata of Requests described in Section 3.1.
Website
the HIPS website at hips.com, including the early-access forms and the Affiliate program page; www.hips.com redirects to it (Section 1.7).
1.7

Where the Service runs. Under hips.com, the Service uses these hosts, and only these:

  1. (a)hips.com, the Website, with the Docs, the early-access forms and the Affiliate program page; 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 (Section 13.1);
  2. (b)console.hips.com, the Console, including the page where you approve the sign-in of a tool that acts for you (console.hips.com/device);
  3. (c)ai.hips.com, the global address of the HIPS API, served through Amazon CloudFront: the encrypted connection ends at the CloudFront edge location nearest the client, which may be in any country, where the Request is decrypted in memory and sent on, encrypted again, to the nearest of HIPS's regional processing locations, where it is served or forwarded as Section 10.2 states; CloudFront stores no Request Content and caches no answer of the API (Section 10.2(c)): the inference API, the task API and the batch API at ai.hips.com/v1; a path reserved for HIPS's own API at ai.hips.com/platform/v1; the paths on which Stripe, Bynn and Amazon SES notify HIPS of events (webhooks); and the paths through which a tool you use, such as the HIPS command-line tool, the Provider App or HIPS Code, asks to sign in as you (device sign-in). The webhooks and the device sign-in are answered in Ireland, at eu.ai.hips.com, and ai.hips.com relays them there;
  4. (d)eu.ai.hips.com, us.ai.hips.com and jp.ai.hips.com, the regional addresses of the HIPS API, each of which reaches only the regional processing location of its region (the European Economic Area, the United States and Japan) and ends encryption only inside that region (Section 10.2);
  5. (e)providers.hips.com, the connection between the Provider App and HIPS for the enrollment of a Device and the renewal of its certificate, and the hosts under providers.hips.com of HIPS's regional processing locations, to which a Device connects for its work (Section 10.2(d)); and
  6. (f)weights.ai.hips.com, from which Devices download the Provider App's updates, the engines and the catalog models from a server near them, on addresses that HIPS issues for each download; it sets no cookies and receives no Request Content.

HIPS's service emails come from noreply@hips.com. Any other host under hips.com is not part of the Service and this Notice does not cover it; HIPS Payments is at https://hipspay.com, and that address and the hosts that HIPS Payments uses under hips.com are run by HIPS Payments under its own privacy notices (Section 1.4), and no cookie of the Service is ever sent to them (Section 13.1).

Section 01
  1. 1.1The Controller
  2. 1.2Who this Notice covers
  3. 1.3HIPS sells and buys in its own name
  4. 1.4HIPS Payments
  5. 1.5Parts not yet available
  6. 1.6Defined terms
  7. 1.7Where the Service runs
Copy link

02Controller and processor roles

2.1

HIPS as Controller. HIPS is the Controller of Website data, early-access registrations, Account Data, identity verification records, Usage Data, the records of Batches, the Prefix Ledger, Billing data, Provider and Device data, Earnings and settlement records, Payout data, Tax Information, trust and safety records, Affiliate Program data and communications with HIPS, inquiries included, of the Request Content of Consumers, their Batch Files included, as Section 2.3 describes, and of training copies as Section 2.4 describes. HIPS decides why and how this data is processed, and this Notice governs it. No other company decides why or how HIPS processes it; the Operating Company and HIPS's other Sub-processors process it only on HIPS's instructions (Sections 2.7 and 9.1).

2.2

HIPS as Processor for Business Users. When the Workspace of a Customer that is a Business User sends a Request, or submits a Batch, its Request Content may contain Personal Data. The Customer is the Controller of that Personal Data, and HIPS processes it as a Processor on the Customer's behalf, under the DPA, to answer the Request, including by storing the Batch Files of its Batches for as long as Section 7.1(c) states. The same applies to a Customer Model of such a Customer, whose weights may embed Personal Data, and to the access token the Customer stores for a private or gated model repository. The Customer's own privacy notice governs that data. HIPS's own use of that Request Content for training, where the Customer's plan allows it, is described in Section 2.4. An individual whose Personal Data such a Customer has sent should contact that Customer; HIPS forwards any request it receives about such data to the Customer concerned, except as Section 11.6 states for training copies and the Prefix Ledger.

2.3

Request Content of Consumers. If you use the Service as a Consumer, HIPS is the Controller of the Personal Data in your Request Content, your Batch Files included, and in your Customer Models, and of the access token you store for a model repository, and processes it under this Notice to answer your Requests and as Section 6 describes; the DPA does not apply to you. Where your Workspace's policy allows training, HIPS uses your Request Content for training on the basis of its legitimate interest, unless you object with the training switch (Sections 2.4 and 6.10), or, if your Country is the United States, only if you turn training on (Section 14.4(g)). If your Request Content contains Personal Data of other people, you are responsible for being entitled to share it with HIPS. Where you use the Service only for purely personal or household activities, data protection law may not apply to what you yourself do with that data, but HIPS processes it only as this Notice describes.

2.4

Training on Request Content. Where a Workspace's request-data policy allows training (Section 6), HIPS may keep a copy of its Request Content, the content of its Batch Files included, for Training, that is, to develop, fine-tune and evaluate machine learning models that HIPS itself operates and offers through the Service. HIPS decides why and how it uses those training copies and is their Controller, independently of the Customer. HIPS relies on these legal bases:

  1. (a)for the Request Content of a Consumer, except a Consumer whose Country is the United States, for whom HIPS relies on the consent of Section 14.4(g), HIPS's legitimate interest in Training (Article 6(1)(f) of the GDPR), which HIPS has weighed against your interests, rights and freedoms and protects with the safeguards that Section 6.10 sets out. 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 (Section 6.10(d)), and you may object at any time with one switch in the Console, without giving a reason and without losing your plan or your access. HIPS does not rely on your consent for training, except as Section 14.4(g) states for Consumers in the United States, and does not treat your acceptance of the Terms of Service as consent; and
  2. (b)for Personal Data in the Request Content of a Customer that is a Business User, HIPS's legitimate interest in Training (Article 6(1)(f) of the GDPR). By using a Workspace whose request-data policy allows training, the Customer instructs HIPS to disclose that Request Content to HIPS for that purpose, and the Customer is responsible for having a legal basis for that disclosure, for informing its data subjects, including of the request-data policy of its plan, and, where the Customer is itself a processor, for its controller's authorization of that disclosure (DPA Section 14.3). The plan rule applies to the Customer's Workspaces as the Terms of Service state it; the switch of Section 6.10 is for Consumers.

HIPS never relies on its legitimate interest, or on any other basis, 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: its automated filters screen the Request Content of every Request, its input and its output, in memory before any training copy of it is written, and HIPS writes no training copy of a Request whose input or output they identify as revealing such data (Section 6.6). 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 the 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, for every Buyer, in the way DPA Section 5.3 provides for a request of a public authority: it discloses only what the law or the order compels and tells the Buyer of the request unless the law prohibits it, and except to a successor that takes over the Service under Section 9.5(f) and is bound by this commitment; a service provider that processes them only on HIPS's behalf and under its instructions is not a third party for this purpose (Section 9.8). Anyone whose Personal Data is in Request Content may object at any time to its use for training, and HIPS then excludes it as Sections 6.6 and 11.2 describe. HIPS recorded its assessment of that legitimate interest, for the Request Content of Consumers and of Business Users, 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 at the privacy contact address in Section 16. Where HIPS cannot identify or reach the people whose Personal Data a Business User sent, this Notice is how HIPS informs them (Article 14(5)(b) of the GDPR).

2.5

Providers as sub-processors. A Provider whose Device executes a Request, including a line of a Batch, processes Request Content for HIPS, as HIPS's Sub-processor where HIPS is a Processor for a Business User and as HIPS's Processor where HIPS is the Controller. The Provider Agreement forbids every Provider to copy, inspect, retain or interfere with the models and content its Device processes, and its Section 8 imposes on the Provider, by contract, the data protection obligations that Article 28 of the GDPR requires of a processor engaged by another processor; for Business Users, DPA Sections 7 and 8 describe Providers as a category of Sub-processor.

2.6

Stripe and Bynn. Stripe acts as HIPS's Sub-processor when it processes Personal Data to provide its payment and payout services to HIPS on HIPS's instructions, and as an independent Controller, under its own privacy policy, for the processing whose purposes and means it decides itself, including detecting and preventing fraud, meeting its own legal obligations such as anti-money-laundering screening and customer identification, and, for a Stripe Connect account or a recipient record of Stripe Global Payouts, opening and verifying that account or record. Bynn acts as HIPS's Sub-processor for identity verification, under its data processing agreement with HIPS, so HIPS is the Controller of the identity verification data Bynn holds for it; HIPS's agreement with Bynn does not permit Bynn to use that data to develop or train its models, or for any other purpose of its own. Tax authorities that receive Personal Data from HIPS (Section 9.4) are independent Controllers.

2.7

The Operating Company. Hyperscale Inference Processing Systems OÜ, of Estonia, operates the Website, the Console, the API, the Provider App and the systems behind them for HIPS. It processes the Personal Data this Notice describes only on HIPS's documented instructions, as HIPS's Processor under a contract that meets Article 28 of the GDPR and, where HIPS is a Processor for a Business User, as HIPS's Sub-processor (DPA Annex 3). It does not use that data for any purpose of its own. HIPS's other Sub-processors listed in Section 9 act for HIPS through it, and transfers outside the European Economic Area are made with the safeguards of Section 10.

Section 02
  1. 2.1HIPS as Controller
  2. 2.2HIPS as Processor for Business Users
  3. 2.3Request Content of Consumers
  4. 2.4Training on Request Content
  5. 2.5Providers as sub-processors
  6. 2.6Stripe and Bynn
  7. 2.7The Operating Company
Copy link

03Personal Data we collect

3.1

Categories. HIPS collects the following categories of Personal Data. A category that belongs to a part of the Service that has not opened is collected only once that part opens (Section 1.5).

TableCategories of Personal Data HIPS collects
CategoryWhat it includesSource
Website dataThe records the web server and HIPS's edge network keep of each request to hips.com and console.hips.com: the IP address, the browser's user agent, the page requested and the time, kept as Section 7.10 states. HIPS's edge network keeps no IP address in its records of requests to ai.hips.com, only the country derived from it. Preferences the Website keeps in your browser stay on your device (Section 13). When the explainer film or its poster loads, Cloudflare, which hosts the film, receives your IP address.Generated automatically
Early-access registrationYour email address, which you confirm through a link; whether you want to buy inference, sell GPU time or both; your choice about other HIPS news; the optional answers you give (what you build, your company, the models you use, the model hub and the visibility of your models, and your country, operating system, GPU and availability); the time of each step and the version of the early-access privacy notice shown to you; a hash of your IP address and your browser's user agent at submission and at confirmation, and a two-letter country code derived from the IP address before it is hashed (the IP address itself is never stored); whether your email address belongs to a disposable-email domain, which never refuses a registration; the delivery events of HIPS's emails to you (sent, delivered, bounced, complained); whether HIPS approved your registration, and the invitation it issued to you and whether it was redeemed; if you arrived through a Program Partner's referral link while the Affiliate Program is open, the referral code, the time it was first seen and the link's campaign values, taken from the Website's referral cookie (Section 13.4); and, if you registered from the Affiliate program page while the program was closed, that you asked to be told when it opens. Your own country answer is kept separately and is never overwritten by the derived country. Registration never asks for model weights or a model hub token.You; generated automatically
InquiriesThe message you send to HIPS's contact address, which HIPS keeps as a Communication. The Website asks you to "Start with a short description rather than confidential model weights, credentials, or customer data." Sending an inquiry never adds you to early access or to any mailing; HIPS uses your address only to answer you.You
Account DataYour name and email address; how you sign in (an emailed one-time link, Google, or a passkey); your sessions; the devices and tools you authorize to act for your Account through device sign-in (Section 1.7), with the tool's name, its scopes, the name, platform and version that the tool reports for the device it runs on (the Provider App reports no computer name), a shortened form of its user agent, and the country and network range it connected from beside a hash of its IP address (the full address is held only while the authorization is pending, and the user agent and network range are cleared after the anti-abuse window); your Workspace memberships and roles; your declaration whether you use the Service as a Consumer or as a Business User, for each capacity in which you deal with HIPS, and, for a business, its name, country and VAT or registration number; the Country you declare and the evidence of residence HIPS checks it against (Section 4.3); if you are a Consumer, the position of your training switch or, in the United States, your consent to training (Section 14.4(g)), and each change to it, with its time (Section 6.10), your consent under Section 6.8, with its time, the version of its text and any withdrawal, and your agreement to receive information and documents in English; your consent to the face check (Section 3.7), with its time and the version of the face-check consent text shown to you, in one record that covers both methods of the face check and does not show which you used, and any withdrawal; the terms you accept, their versions, and your separate confirmation of the clauses that most affect your rights; the notices sent to you; and the audit log of actions taken with your Account. If you sign in with Google, Google provides the identity of your Google account under its own privacy policy. A passkey gives HIPS a public key; the biometric unlock of your device does not reach HIPS.You; the Workspace owner or admin who invites you; Google, if you choose it
Identity verification recordsHIPS's reference for your verification, its status, the time of the decision, Bynn's case identifier and the checks run (identity document, face check and sanctions screening), never which method of the face check you used (Section 3.7(d)); the record of your consent to the face check and any withdrawal (Section 3.7), which covers both methods and does not show which you used; the issuing country of your identity document, which Bynn reports, and which never decides your Country (Section 4.3); the identifiers of you as a natural person that HIPS computes as keyed hashes from Bynn's result, with a secret key that only HIPS holds, never from your face or any other biometric data, and from which neither your document number nor your date of birth can be read without that key, used only to keep one verified identity per person, to recognize a person whose Account HIPS closed for cause (Section 7.9) and, after a deletion, to confirm who may change where HIPS pays an amount it owes you (Section 11.5), and kept as Section 3.7 states; the result that you are at least eighteen (18) years old (Section 12); the number of your attempts and what started each one, never which method of the face check an attempt used; the reason category of a verification that failed; and an administrator's decision after a review. For identity verification, HIPS never stores a document image, a document number, a date of birth, a face or any biometric data: it reads in memory, from Bynn's result, only the particulars it needs to compute the keyed hashes and to confirm your age, discards them at once, and never fetches the images that Bynn holds; a person at HIPS who runs the face check by a person sees you only live, on a call that is never recorded, and keeps only the outcome of the verification (Section 3.7(d)). The one exception is the check of other evidence by a person of Section 11.5: where a person at HIPS checks other evidence, after a deletion, to confirm who may change where HIPS pays, the records also hold the documents that person sends, which a person at HIPS checks and HIPS deletes within seven (7) days after the later of HIPS's decision and the end of the waiting period of Section 11.5, unless it needs them to establish, exercise or defend a legal claim about that change, and then only until the claim is resolved (Section 7.12), keeping only the decision, its time, the person at HIPS who made it and the kinds of document checked. HIPS asks only for what that check needs and never processes the photograph in such a document to identify anyone by the features of the face. For a change of name, HIPS accepts any official document or register extract that shows both names, such as an extract from a population or civil register, a court order or a deed of change of name, asks you to redact everything else, including any statement of why the name changed, except what HIPS needs to confirm the document with the register or authority that issued it, and never asks why the name changed. Where the document you choose can still reveal a special category of Personal Data, such as a marriage or a change of gender, HIPS processes it only on your explicit consent, which you give by a separate action when you send it (Article 9(2)(a) of the GDPR), uses it only to confirm the change, and deletes it as this row states; you are not obliged to send it, and HIPS pays what it owes you to the payout account already connected whatever you decide (Section 11.5).Bynn; HIPS; the person who asks, for the check of Section 11.5
Identity verification data held by BynnThe image and details of your identity document, the images or video of your face captured for the automated face check, only where you choose it and with your explicit consent (Section 3.7 describes the check), and the results of sanctions screening. Bynn collects these and does not pass them to HIPS, which never fetches the images. Bynn holds them as HIPS's Sub-processor, and HIPS is their Controller (Section 2.6).You; sanctions lists, through Bynn
Usage DataFor each Request and each attempt to answer it: the Request identifier, the API key, the Workspace, the model, the pool and lane, the pricing mode and quote, the region, the regional processing location that accepted the Request and the one that served it, and whether it was forwarded between them (Section 10.2), the units and their rate version, the cost, the outcome, the latency, the error type and code, the token and unit counts (cached input tokens included), the Batch and line a Request belongs to, the timestamps, and the worker or Device that served it; the client IP address, stored only as a hash, with a coarse country code and a flag for anonymizing networks derived before hashing; and the class of the user agent. Usage Data never includes Request Content.Generated automatically
Request ContentPrompts, messages, uploaded inputs and generated outputs, the content of Batch Files included. It contains Personal Data only if the Buyer chooses to include it. It is processed in transit and in memory to answer the Request and is not stored by default, except as Section 7.1 states, for example the Batch Files of a Batch, the body of an asynchronous job until the job ends, and the answer to a task Request sent with an idempotency key.The Buyer, through the API, the SDK or the Console playground
Batch recordsFor each Batch: its identifier, the model, the Completion Window chosen (twenty-four (24) hours by default, and up to seven (7) days), its status and times, the counts of lines completed, failed and expired, the price quote bound when HIPS accepted it, the maximum charge held against the prepaid balance and its release line by line, the expiry the Customer set for the Batch Files, and the address of the endpoint to which HIPS sends signed notices of completion; the name of each Batch File as the Customer gave it; and the metadata the Customer attached to the Batch, which HIPS keeps only to return it, treats as Request Content and lets a person at HIPS reach only as Section 8 allows. A Batch record holds no other Request Content; its Batch Files are Request Content.The Buyer, through the API or the SDK; generated automatically
Prefix LedgerFor each Request to a language model served by a data-center worker whose prompt cache is on, kept for each Workspace and, in a Consumer's Workspace, for each Member and API key whose caches are kept apart: pseudonymized hashes of the blocks of the prompt's tokens, with the worker that served the Request and the time. The hashes are derived from Request Content and are Personal Data wherever the prompt contained Personal Data: HIPS cannot read a prompt from them, but could check with them whether a Workspace sent a known text (Section 6.12). The Prefix Ledger does not keep the text of a prompt.Generated automatically from Request Content
Customer ModelsThe weights a Customer imports from a model hub, which may embed Personal Data; the repository, the pinned version and the hub's license; the record of the Member's license attestation (the Member, the time and the version of the attestation text); and, for a private or gated repository, the hub access token the Customer stores, with the name of the hub account that the token authenticates as, where the hub states it.The Customer, and the model hub on the Customer's instruction
Billing dataStripe's customer, payment and invoice identifiers; the card brand, last four digits and expiry date, and a hash of Stripe's card fingerprint, never the card number; any Referral Discount on your first top-up, with its promotion code and the referral it came from (Section 3.8); the billing address and tax identifier you give Stripe Checkout; for value added tax, your status as a Consumer or a Business User, your VAT number and the result of validating it, including the name and address the register returns, and the evidence of your location that VAT law requires, such as your billing address and the country derived from your IP address; receipts and invoices; Credit balances, the expiry of Purchased Credits and refunds; the ledger of Credits and charges; for a payment that an agent acting with an API key of your Workspace makes through Stripe's Machine Payments Protocol (a machine payment), the reference of the Shared Payment Token, the identifiers of the payment and of its receipt, and the card brand, last four digits and usage limits of the token that Stripe returns, never the card number, with the API key that made the payment, the amount and the time; whether the Workspace has turned machine payments on, with its limits, and the record of the acceptance of the owner or admin who turned them on, with its time and the text shown; and payment disputes.You; Stripe; an agent that makes a machine payment for your Workspace; the tax registers HIPS validates VAT numbers against; generated automatically
Provider and Device dataFor each Device: its capabilities and its hardware inventory, the app, engine, operating system and driver versions, its hardware identifiers, kept as the Provider App reports them (Section 3.9), the hardware id, a hash that the Provider App computes on the Device to bind the Device's certificate to it and by which a Device whose certificate has expired enrolls again on its own, keyed hashes of the identifiers that its engines report for its GPUs, used to detect one GPU enrolled as more than one Device, whether the Device is marked as a data-center server, and the contents of its model cache; regular heartbeats with its condition, the level of work it may take (none, light or full) and the codes of the reasons for that level (Section 3.5), and measurements such as GPU and processor load, GPU memory in use and free, temperatures, power use and power source, the use of its NPU, and engine health, and nothing else about the owner's activity; job events; the country of the Device, which HIPS takes from the network address of each connection by looking the address up in a copy of MaxMind's GeoIP2 Country database that HIPS holds itself, so that the address is never sent to MaxMind, and updates at each connection, with when it was taken (a Provider never enters or reports it); for each connection, a keyed hash of its network address, kept for the period of Section 7.8, the country derived from it, whether it comes from an anonymizing network or a hosting network, and the location HIPS derives from network measurements (Section 10.3); the network address from which a Device downloads a catalog model or an engine, in the records of the content delivery network, kept for thirty (30) days, as Section 7.10 keeps web server records; its settings, schedule, daily limit and minimum price, with each change, its time and where it was made (the Console, the Provider App or the Device's configuration file); the attempts it performs; the records of its certificate; whether its GPU or machine matches an entry of the hardware blocklist (Section 3.9); the round trips between the Device and each of HIPS's regional processing locations, which the Device and HIPS measure, and the regional processing location to which the Device is connected (Section 10.3); and crash reports, if you agree to send them (Section 3.10).The Provider App; generated automatically
Earnings and settlement recordsFor each Device and provider account: the Earnings recorded for each attempt and their state (estimated, accrued, payable or paid); the Settlement of each period and its statement; holds, with their reason category; adjustments, forfeitures and the documented costs of fraud that a Provider pays HIPS (the Fraud Costs of Provider Agreement Section 12.5), with the basis for them; the entries of the netting account that the Provider Agreement describes; your disputes of a statement and their outcome; and the self-billed statements HIPS issues for the GPU Time it buys.Generated by HIPS; you
Payout dataYour payout profile (legal name, Country and status as an individual, a registered sole proprietor or an organization); your payout method, which is a Stripe Connect account or, in a country where HIPS pays through Stripe Global Payouts, the recipient record Stripe keeps for you under it (Section 3.3); and your payouts, with their amount, currency, date, status and reference. Documents a payout provider needs to verify you are collected by that provider and are not stored by HIPS, and the bank details of a Global Payouts recipient are entered in Stripe's own form and are not stored by HIPS (Section 3.3(e)).You; Stripe
Tax InformationThe information Section 3.2 lists, and the amounts withheld for tax and the statements and reports HIPS issues or files.You, and, for United States tax forms, through Stripe's tax reporting service once Stripe confirms it for HIPS's account (Section 9.1); the tax registers HIPS validates numbers against; generated by HIPS
Trust and safety recordsAssessments of the risk of fraud or abuse at sign-up, in payments and in usage; the results of the checks HIPS runs on Providers' work; links between Accounts that resolve to the same verified person; the sanctions screening of you and your payout destinations; each measure taken (a flag, a limit, a hold, a pause, a suspension or a closure) with its ground, the statement of reasons sent to you, any review you ask for and its outcome; findings of fraud made after review, with the forfeitures and Fraud Costs that follow them; the entries of the hardware blocklist, with the finding of a breach of the Provider Agreement each rests on, never a characterization as a criminal offense, and every review of it (Section 3.9); and the evidence HIPS gives to answer a payment dispute.Generated by HIPS from the categories above; reports HIPS receives from others, such as abuse reports and the notices of rights holders; and payment disputes and inquiries reported through Stripe on behalf of card issuers
Affiliate Program dataOnce the Affiliate Program opens: for a Program Partner, the items Section 3.8(a) lists, including the record, the codes, the daily click counts, the referrals, the commissions, the payout account and payouts, the Tax Information a tax rule requires for commissions, the results of the fraud checks, and the copies of Partner Content and the placement, targeting and traffic-source information of Section 3.8(a); for a Referred Person, the referral record Section 3.8(b) lists; and the referral cookie and parameter of Section 13.4.You; the Program Partner's link or code; generated automatically; Stripe
CommunicationsMessages you send HIPS, inquiries included, and HIPS's replies, including notices you give under the Terms of Service, the Provider Agreement, the Affiliate Program Agreement or the Common Clauses, such as a Notice of Dispute or a United States arbitration opt-out; a support bundle you choose to send from the Provider App after reviewing its list of files: the app's logs, which hold names and codes and no content, its settings, including your minimum price unless you remove it, its capabilities report and its versions, never its key, certificate or tokens; the service emails HIPS sends you from noreply@hips.com, and their delivery events.You; generated automatically
3.2

Tax Information of Providers and Program Partners. Before HIPS pays you for GPU Time, HIPS collects the tax information below. HIPS asks only for the items that apply to you, and Section 4.2 explains why it needs each of them.

TableTax Information HIPS collects
InformationWho is askedWhen
Your status (an individual, a registered sole proprietor or an organization), and your declaration whether you supply GPU Time as a Business User, with your business registration number or VAT number, or as a private individual (Section 4.3)Every ProviderWhen you create your provider account, before any Device is eligible for work
Your registration as a sole proprietor (FIE) in Estonia and its registry code, or your company's name and registry code: HIPS accepts private individuals resident in Estonia as Providers and Program Partners only as registered sole proprietors or through a company (Section 4.2)Providers and Program Partners resident in EstoniaWhen you create your provider account or join the Affiliate Program
Your legal name, primary address and date of birthEvery Provider who is an individual, including a sole proprietorBefore the first payout
Your tax residence, as a self-certification, and each taxpayer identification number issued to you with the country that issued it, or, if none was issued, your place of birthEvery Provider, except as the next row states for Providers in Japan, Singapore, the Republic of Korea, Taiwan and AustraliaBefore the first payout
Your tax residence, as a self-certification, and, where you have one, a business number: in Japan, a corporate number; in the Republic of Korea, a business registration number; in Taiwan, a unified business number; in Singapore, a Unique Entity Number; in Australia, an Australian Business Number. HIPS never asks for Japan's Individual Number, Australia's tax file number, the Republic of Korea's resident registration number or Singapore's NRIC number, on any form, including a United States tax form, because the law of those countries restricts who may ask for them; where a United States form asks for a foreign taxpayer identification number, HIPS does not need it and you leave it blankProviders whose Country is Japan, Singapore, the Republic of Korea, Taiwan or AustraliaBefore the first payout
Your VAT identification number, or the identification number of a small-business VAT exemption, where you have one, and the result of validating itProviders who have oneBefore the first payout, and when it changes
Form W-9: your name, address and United States taxpayer identification number, and the certifications the form asks forProviders who are United States personsBefore the first payout to them
A self-certification that you are not a United States person, which asks for no taxpayer identification number, or, where United States tax law makes a payment to you subject to United States withholding, Form W-8BEN (for an organization, Form W-8BEN-E), which asks for information such as your country of citizenship, permanent residence address, date of birth and any tax treaty claim; HIPS never asks for a foreign taxpayer identification number on itProviders who are not United States persons. HIPS asks only for a self-certification that you are not a United States person, which asks for no taxpayer identification number, and asks for Form W-8BEN or Form W-8BEN-E only where United States tax law makes a payment to you subject to United States withholdingBefore the first payout
A document certifying your tax residence for a tax treaty, where a tax rule requires HIPS to withhold tax from a payment to you and the treaty would reduce itProviders and Program Partners to whom such a rule appliesBefore the payout concerned
Your tax reference number (your VAT registration number or Personal Public Service Number)Providers and Program Partners resident in IrelandBefore the first payout

HIPS checks Tax Information for reliability against its own records and against the free electronic services that tax authorities provide for validating taxpayer and VAT identification numbers, and asks you to correct what does not match. Program Partners give the same information where a tax rule requires it for their commissions (Section 3.8(e)). You must keep your Tax Information current.

Important for Providers: tax reporting

If DAC7 applies to GPU Time, and you are resident in a Member State of the European Union, information relating to you "will be collected and transferred in accordance with" DAC7: HIPS reports your name, primary address, taxpayer identification numbers and the countries that issued them (or your place of birth), your VAT number, your date of birth and the Earnings HIPS paid or credited to you to the Revenue Commissioners of Ireland, which may transmit it to the tax authority of the Member State where you are resident, and HIPS tells you each year what it reported. HIPS reports the Earnings it paid or credited to you in each quarter: those it settled as payable in that quarter, whether or not paid out yet, and never amounts that were only estimated or accrued. If you are resident in Ireland, HIPS reports the Earnings it pays you to the Revenue Commissioners on Form 46G where the law requires it (Section 4.2). If you are a United States person, HIPS files Form 1099-NEC for its payments to you where United States tax law requires it and sends you a copy.

3.3

Payouts. At launch HIPS pays Providers, and Program Partners once the Affiliate Program opens, only in money to a bank account in their own name, never in a crypto-asset (Section 9.6), and only through a route that pays out from HIPS's own Stripe account in their Country: Stripe Connect in the United States, the United Kingdom, the European Economic Area, Switzerland and Canada, and Stripe Global Payouts in Japan, Singapore, Taiwan and Australia; in the Republic of Korea no payout can be made until a payout method opens there (point (h)).

  1. (a)Stripe Connect. HIPS pays you through a Stripe Connect account with an Express dashboard in your name, on Stripe's full service agreement, under which you accept the Stripe Connected Account Agreement with Stripe. HIPS asks Stripe to open the connected account and gives Stripe your email address, your Country, whether you are a natural person or an organization and, so that Stripe's form starts with them, your verified legal name or, for an organization, its registered name. Stripe collects every other detail directly from you.
  2. (b)Stripe collects directly from you the identity, bank account and tax details it requires, under its own terms and privacy policy, and HIPS does not store them.
  3. (c)HIPS receives from Stripe the identifier of your connected account, its country, default currency and status, its capabilities and whether payouts are enabled, the requirements Stripe still needs from you and the reason for any restriction, the country, currency, bank name and last four digits of the bank account it pays to, and for each transfer and payout its amount, currency, date, status, failure or return reason and reference. When you give personal data to Stripe, Stripe receives it and processes it as the Stripe Privacy Policy (https://stripe.com/privacy) describes.
  4. (d)HIPS gives Stripe the amounts it transfers to your account or pays to your bank account; where Stripe asks for it to meet its own obligations or to handle a dispute, the information about you and your activity that the request concerns; and, on its own initiative, information about fraud, holds and breaches of the Provider Agreement or the Affiliate Program Agreement that concerns your connected account or your recipient record.
  5. (e)Stripe Global Payouts. In Japan, Singapore, Taiwan and Australia, HIPS pays you through Stripe Global Payouts, from its own Stripe account, to a bank account in your own name, in the currency Stripe pays in your country. Stripe keeps a recipient record for you, which HIPS creates, giving Stripe the details Stripe needs for it: your name, your email address, your Country, whether you are a natural person or an organization and, where Stripe requires them for your country, your address and telephone number. You accept with Stripe the Stripe Recipient Notice, under which Stripe offers you no service of its own, and Stripe processes your personal data as the Stripe Privacy Policy (https://stripe.com/privacy) describes. You enter your bank details in Stripe's own form, directly with Stripe, and HIPS does not store them. Stripe makes HIPS responsible for verifying the people it pays this way, so HIPS relies on its own identity verification (Section 3.7) and sanctions screening, and the name on the bank account must match your verified identity.
  6. (f)For a recipient record, HIPS receives from Stripe its identifier and status, its payout capabilities and what Stripe still needs from you, the country, currency, bank name and last four digits of the bank account, and for each payout its amount, currency, exchange rate, fees, date, status, trace identifier, reference and any failure or return reason.
  7. (g)Until Stripe Global Payouts opens in your country. Stripe Global Payouts opens in each of these countries only once Stripe has confirmed it in writing for HIPS's account and HIPS has the tax view it needs there. Until then, you may enroll and link your Devices, and HIPS runs only unpaid test work on them, assigns them no paid work and so records no Earnings for them, and a Program Partner earns no commissions; the Console says that payouts in your country, and paid work and commissions with them, open with Global Payouts (Provider Agreement Sections 1.10 and 14.13; Affiliate Program Agreement Sections 7.4 and 10.17). If payouts close in your country after they opened, HIPS stops paid work there and commissions stop until a payout method opens again, and HIPS settles what was earned before then as usual and owes it to you, but cannot pay it out meanwhile; HIPS keeps the records of what it owes you as Section 7.7 states (Provider Agreement Section 14.13(d); Affiliate Program Agreement Section 10.17(d)).
  8. (h)The Republic of Korea. Stripe publishes no bank payout to the Republic of Korea for HIPS's account, so no payout to a bank account there is possible until a payout method opens, and until then your Devices take only unpaid test work and a Program Partner earns no commissions, as point (g) states.

The Provider Agreement, and for a Program Partner the Affiliate Program Agreement, authorizes HIPS to act on your connected account or your recipient record in these ways.

3.4

No crypto-asset benefit and no wallet. HIPS offers no benefit for holding MTO or any other crypto-asset, connects no wallet and collects no wallet address, balance or signature (Common Clauses Section 3.11). HIPS does not encourage, invite, recommend or advise anyone to acquire, hold, sell or trade MTO or any other crypto-asset, for any reason, and never asks or encourages anyone to acquire a crypto-asset to use the Service. Crypto-assets carry extreme risk, including the total loss of their value; acquiring or holding one is your own decision, on which you should take advice from your own independent financial, legal and tax advisors (Common Clauses Section 3.12). If HIPS ever offers a benefit related to a crypto-asset, it first updates this Notice to describe the data it would process for it.

3.5

What the Provider App never sends. The Provider App decides on the Device whether the Device may take no work, light work or full work, from signals that it reads on the Device and keeps there: how long ago the keyboard or the mouse was last used, whether the screen is locked, whether an application is in full screen, whether the camera or the microphone is in use, whether Do Not Disturb is on, whether a game is running, whether a remote session is open, whether the Device is on battery, the load that other programs put on the GPU and the processor, the temperature of the GPU, and whether its graphics driver has recently reset. The signals of your session are read inside it by a small part of the Provider App that runs in your session: on Windows and macOS the program behind its icon, and on a Linux desktop a helper with no window. The Provider App sends HIPS only the resulting level, the codes of the reasons for it, such as that the camera or the microphone is in use, a game or a full-screen application is running, a remote session is open or the Device is on battery, and the measurements that Section 3.1 lists; a code shows that a reason applies, never which application or game it concerns or what you do in it. It reads none of these signals of a person's presence on a Device marked as a data-center server. Apart from these, the hardware inventory and hardware identifiers of Section 3.9, the crash reports of Section 3.10, the round trips it measures to HIPS's regional processing locations (Section 3.1), the results of the jobs it runs, and a support bundle that you choose to send (Section 3.1), the Provider App never sends HIPS Request Content or outputs, keystrokes, screen contents, the name of any application or game, window titles, file names outside its own state directory, the Device's computer name, the labels of its drives, its asset tag, information about the owner's other accounts, browsing, or location beyond what the network connection itself reveals. The app contains no third-party analytics or crash-reporting software. It sends its own crash reports to HIPS only if you have agreed to send them, as Section 3.10 describes, and a crash report carries none of the items this Section says the Provider App never sends.

3.6

Business verification. Where a Workspace held by an organization is on the higher paid plan, or a Provider, an Approved Provider or a Program Partner is an organization, HIPS verifies its owner or representative as a natural person, and verifies the organization itself as this Section describes. Where HIPS verifies an organization (Provider Agreement Section 3.7; Terms of Service Section 4.4), Bynn collects the organization's register data and the names, dates of birth and nationalities of its representatives and of the natural persons who own or control it, and screens them against sanctions lists, for HIPS, on the basis of HIPS's obligations under sanctions law (Article 6(1)(c)) and its legitimate interest in knowing whom it pays (Article 6(1)(f)); HIPS keeps the organization's name, registry code, the result and the reference, and Bynn keeps the rest as Section 7.6 states.

3.7

The face check and your consent. Every identity verification includes a face check, and you choose, without giving a reason, between two methods, which have the same effect and give the same access, Credits and benefits: the automated face check, for which HIPS asks your explicit consent, and the face check by a person (point (d)). The automated face check, also called the liveness check, 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. Bynn is HIPS's identity verification provider, and the automated face check involves biometric data used to confirm your identity. 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 of the Workspace nor a Member in the role of admin or billing, 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 Terms of Service Section 5.2 does not hold. 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; it does not use it to search for your face among other people's verifications: Bynn 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 keeps one verified identity for each person (Section 4.1) through its identifiers 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 point (e) excludes). HIPS computes each keyed hash with a secret key that only HIPS holds, from the result that Bynn 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, point (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 those identifiers, on the basis of its legitimate interest in preventing fraud (Section 4.1), to keep one verified identity per person, so that nobody receives a second Free Allowance or Referral Discount, to recognize a person whose Account, Workspace, provider account or participation in the Affiliate Program HIPS closed for cause (Section 7.9), and, after a deletion, to confirm who may change where HIPS pays an amount it owes you (Section 11.5). Because they are not derived from your face, HIPS keeps them whether or not your consent to the face check stands: while your Account exists; after its deletion, for the period of Section 7.6 and, beyond it, while an amount remains owed to you (Section 11.5(d)); and after a closure for cause, for the period of Section 7.9. Bynn performs the automated face check for HIPS, and a person at HIPS performs the face check by a person:

  1. (a)before the automated face check, HIPS tells you what is captured, why, who captures it and how long it is kept, and that the check is automated, asks for your explicit consent by a separate action, apart from your acceptance of any terms (Article 9(2)(a) of the GDPR), and records your consent with its time and the version of the text shown to you, in one record for both methods of point (d), which does not show which method you used; you may withdraw it at any time, without affecting the lawfulness of a check already made; if you withdraw it after the check, the verification decision already made stands, and HIPS instructs Bynn to destroy the face captures and any biometric data it still holds for HIPS, unless the law requires Bynn to keep them; Bynn holds that data as HIPS's Sub-processor (Section 2.6);
  2. (b)whatever your Country and wherever you are, your 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. The release reads: "I have read the notice above. If I choose the automated face check, I consent to HIPS and its identity verification provider, Bynn Intelligence, Inc., collecting, storing and using scans of my face geometry, made from the images of my face captured during the check and from the photograph in my identity document, only to confirm that I am present and that I am the person whom that document shows. They are stored for no longer than thirty (30) days after the decision on my verification, or, if I ask for a review of that decision or a legal claim about it is made, until that review or claim is resolved, and are then permanently destroyed under the policy at hips.com/legal/biometric-data. I sign this release electronically by selecting I agree." For persons in Canada, Section 14.3 also applies;
  3. (c)HIPS publishes, at hips.com/legal/biometric-data, a written policy that sets how long face captures and biometric data are kept and how they are permanently destroyed, with its protocol for an incident that may compromise them, and requires Bynn to destroy them under it: within thirty (30) days after the decision on your verification, unless you have asked for a review of that decision or HIPS needs them to establish, exercise or defend a legal claim, and then when that review or claim is resolved; and in every case on the earliest of the date on which the purpose for which they were collected has been satisfied, twenty-four (24) months after your last interaction with HIPS, and forty-five (45) days after HIPS's annual review finds that keeping them is no longer necessary, whether or not your Account still exists. HIPS also publishes, at hips.com/legal/consumer-health-data, linked from the home page of hips.com and from the Console, a Consumer Health Data Privacy Policy that covers face captures and biometric data as consumer health data under the Washington My Health My Data Act (RCW 19.373) and Nevada Senate Bill 370, and the Request Content of Consumers in the United States (Section 14.4(g)), and honors the deletion right those laws give, including for the copies Bynn holds, which HIPS instructs Bynn to delete. HIPS applies this policy, the release of point (b) and the notices of the biometric privacy laws of Illinois, Texas and Colorado to every person, whether or not those laws apply to HIPS or to that person;
  4. (d)you may choose the face check by a person instead of the automated face check, without giving a reason: a person at HIPS sees you live on a video call that is never recorded and compares you with the photograph in the identity document you show, with no automated processing of your face, and Bynn then runs its checks of your identity document and the screening without any face capture. It has the same effect as the automated face check and gives the same access and benefits. 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, and it updates this Notice before it does; until then, the automated face check and the face check by a person are the only routes of the face check. You ask for it 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, which video-call service carries the call, 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. If you decline both methods, you cannot complete identity verification. Without verification: a Workspace you own receives no Credits, the Free Allowance included, and runs no Request, so you cannot buy, or use inference for yourself or as a Member; none of your Devices becomes eligible for work, so you cannot earn as a Provider; and HIPS issues you no referral code or link for the Affiliate Program, so you cannot earn commissions. Your Account stays unverified and inactive, and you may verify later, as Terms of Service Section 4.3 provides for retries, review and the deletion of Accounts and Workspaces that never pass. An employer or other organization may not require you to consent to the automated face check as a condition of your work, and if you decline both methods, you may still use the Service for a business that employs or engages you through an API key of its Workspace, without becoming a Member (Terms of Service Sections 4.10 and 5.2); this route gives that person no Workspace, Credits or Free Allowance of their own. HIPS tells the owner and admins of a Workspace only whether you have passed verification, never which method of the face check you used or whether you declined or withdrew your consent (Terms of Service Section 4.10); and
  5. (e)Documents in the Republic of Korea, Singapore and Japan. HIPS accepts, for a person whose Country is the Republic of Korea, only a passport that does not show a resident registration number, such as a passport of the Republic of Korea issued from 21 December 2021 or a passport of another country, and never a document that shows a resident registration number; for a person whose Country is Singapore, an NRIC, a passport or another document that shows an NRIC number or another national identification number, which Bynn reads only to verify your identity to the high degree of fidelity that granting benefits once per person and paying Earnings and commissions require, with your consent; and for a person whose Country is Japan, a passport, a driver's license or a residence card, and an Individual Number Card only where Bynn captures its front side alone, never its back or the Individual Number. HIPS never derives the keyed hash of this Section from a resident registration number, an NRIC or other national identification number of Singapore, or an Individual Number, and derives it only from the document number of the document accepted under this point.

HIPS itself never stores an image of your face or any biometric data (Section 3.1), and a person at HIPS who runs the face check by a person sees you only live, on a call that is never recorded, and keeps only the outcome of the verification; the only exception is a photograph in a document sent for the check of other evidence by a person of Section 11.5, which HIPS never processes to identify anyone by the features of the face and deletes as Section 3.1 states. Section 7.6 states how long verification records and face captures are kept.

3.8

The Affiliate Program. The Affiliate Program ships closed and opens only if HIPS decides to open it, which HIPS announces on the Website's Affiliate program page and in Refer and earn, together with the program's figures. Its public page is the Website's Affiliate program page, and its screen in the Console is Refer and earn. Once it opens:

  1. (a)Program Partners. A person who holds an Account may take part where HIPS issues them a referral code and link in Refer and earn, which HIPS does only after they have passed identity verification (Section 3.7) and, where HIPS asks for it, accepted the Affiliate Program Agreement, and HIPS attributes no referral to them before then; until they accept that Agreement, the referrals and commission records HIPS keeps for the code and link are information only (Affiliate Program Agreement Sections 1.5, 3.6 and 4.1); HIPS creates the Program Partner's record, code and link the first time it does so. HIPS processes: the record (its status, the codes held and their history, eligibility and the count of qualified referrals, the version of the Affiliate Program Agreement accepted and when, any rate or threshold an administrator set with its reason, and any suspension or termination with its category and the note sent); daily counts of clicks on the link by campaign values, which name no person; the referrals attributed to the Program Partner; the commission ledger (each commission, reversal, clawback and adjustment, with its status and the end of its hold); the payout account and the payouts; the Tax Information a tax rule requires for commissions; the results of the checks in (d); and copies of Partner Content (the material in which a Program Partner promotes HIPS, as the Affiliate Program Agreement defines it) that HIPS reviews or records, and the placement, targeting and traffic-source information a Program Partner gives under Affiliate Program Agreement Section 15.16, used to check compliance with that Agreement and with advertising and consumer law, on the basis of HIPS's legitimate interest (Article 6(1)(f) of the GDPR), and kept while a claim about them can be brought (Section 7.10). No commission becomes payable to a Program Partner who has not reached the eligibility the Affiliate Program Agreement sets, passed identity verification (Section 3.7) and accepted the Affiliate Program Agreement, or whose Country is not one in which HIPS pays commissions, and none is paid until a payout account is connected (Affiliate Program Agreement Sections 7.10 and 10.2).
  2. (b)Referred Persons. If you arrive through a Program Partner's link, or enter a code when you create your Account or make your first top-up, HIPS records a referral: the Program Partner and the code, whether it came from a link or a code, the link's campaign values, when the code was first seen and when the referral was attributed, a hash of your IP address at sign-up with the country and the anonymizing-network flag derived from it before hashing, the referral's state and the reason for it, your first qualifying top-up or first payout and its amount, the Referral Discount you received, and, to calculate the commission, the amounts you paid for usage, or HIPS paid you for GPU Time, during the commission period. An existing user, a Member invited into an existing Workspace, and a person who resolves to an already verified person are never Referred Persons. Point (c) tells you what a Program Partner learns from your referral. If you object to the processing of your data for the Affiliate Program (Section 11.2), or have it erased, HIPS stops attributing amounts to your referral from then on, without weighing your objection against its own interest, and its commission period ends (Affiliate Program Agreement Section 5.9). Commissions already recorded for it stay as they are, subject to their reversal or forfeiture (Affiliate Program Agreement Sections 9 and 12), as far as HIPS may still lawfully process the data they need; HIPS keeps only what it needs to check them for fraud, to keep its financial and tax records and to establish, exercise or defend a legal claim, and erases the rest of your referral data that it no longer needs.
  3. (c)What each side sees. Refer and earn shows a Program Partner its referrals only as totals. Until a role has at least five (5) of the Program Partner's referrals, or any larger number that the Affiliate Program Agreement states, it shows for that role only the number of its referrals, with no count by state and no commission total; once a role has that many, it shows for that role the number that are pending, qualified, not qualified and reversed. It shows how many qualified referrals count toward eligibility only once the Program Partner has at least that number of referrals across all roles. It never lists your referral on its own or shows its dates, its state or its amounts. Where HIPS must identify your referral to the Program Partner, in a statement of reasons, a notice of forfeiture or a dispute between HIPS and the Program Partner, it 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). Once a role has at least that number of referrals, Refer and earn and the Program Partner's payout statements show its commissions only as totals for each role and period, combining periods so that each total covers at least that number of referrals; until then, a payout statement shows only the total of each payout across all roles (Affiliate Program Agreement Section 5.8). 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 or the Affiliate Program 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. HIPS never tells a Program Partner your name, email address, Workspace, provider account or Device, or what you paid or were paid, unless the law requires HIPS to disclose it, and the Affiliate Program Agreement forbids a Program Partner to try to identify you from what HIPS shows, or to contact you because HIPS's records show that you were referred. A HIPS administrator may see who was referred, in a read that is recorded. HIPS processes your referral data for this purpose on the basis of its legitimate interest in attributing referrals and paying the commissions it owes for them, which it has weighed against your interest in keeping your spending, your Earnings and your payment events from a person who may know you; showing only totals and reason categories, withholding totals until a role has enough referrals, paying commissions only in payouts that come from at least that number of referrals, and a reference only where a measure or a dispute requires it, is how HIPS meets that balance, and HIPS tells you here that each payout named in the exception above, made to a Program Partner with few referrals, can still show it approximately what a referral earned it.
  4. (d)Checks against self-referral and fraud. HIPS compares each referral with its Program Partner: whether the two resolve to the same verified person; whether they share, or shared, a Workspace; whether the card of the first top-up matches a card saved on a Workspace the Program Partner belongs or belonged to; whether a referred Provider's payout account or a hardware identifier of one of their Devices matches one of the Program Partner's (Section 3.9); whether the two email addresses are the same once normalized; and whether the sign-up or the first top-up came from the same network as the Program Partner, from the same email domain other than a free email service, or from an anonymizing network. A match of the same person, a shared Workspace, card, payout account or Device, or the same email address rejects the referral, or reverses it if found later, and HIPS repeats those checks while commissions accrue; a match of network, email domain or an anonymizing network holds the referral until a person at HIPS decides it (Section 5).
  5. (e)Payouts and tax. HIPS pays commissions to a bank account through Stripe Connect or Stripe Global Payouts, as Section 3.3 describes, reusing the Program Partner's provider payout account or recipient record where there is one. HIPS pays commissions only in money and makes no crypto-asset payout (Section 9.6), and a payable commission stays an amount in United States dollars that HIPS owes until it is paid. The Referral Discount is applied through a Stripe promotion code that carries the Program Partner's identifier. Before the first payout, HIPS collects the Tax Information a tax rule requires for commissions: if you are a United States person, Form W-9, and HIPS files Form 1099-NEC for commissions paid to you in a calendar year of at least the amount the law sets (two thousand United States dollars (USD 2,000) for 2026); otherwise a self-certification that you are not a United States person, and Form W-8BEN only where United States tax law makes a payment to you subject to United States withholding; and, if you are resident in Ireland, your tax reference number, with which HIPS reports your commissions to the Revenue Commissioners on Form 46G where the law requires it (Section 4.2). HIPS does not report commissions under DAC7, because a Program Partner supplies its service to HIPS and not to other users of a platform.
3.9

Device hardware, hardware identifiers and the hardware blocklist. When you enroll a Device as a Provider, and each time it connects, the Provider App sends HIPS the Device's hardware inventory: the maker, model and version of the computer, its board and its firmware; its processors, GPUs, NPUs and other accelerators, with their capabilities, memory, drivers and the programming interfaces they support; its memory modules and disks, with their size, type and speed; and its operating system, version and build. It also sends the Device's hardware identifiers, which HIPS keeps in the Device's record as the Provider App reports them, as the last paragraph of this Section describes. The hardware identifiers are the serial number and UUID of the computer and the serial numbers of its board and its chassis, as its firmware or, on a server, its management controller reports them, the serial numbers of its memory modules and disks, the UUID, serial number and board part number of each GPU, the identifiers of its other accelerators, the identifier that the operating system gives its installation, the MAC addresses of its network adapters, and the model numbers, part numbers and makers of its components. The Provider App never sends the computer name of a Device, the labels of its drives or its asset tag. This is in addition to the hardware id, the hash that the Provider App computes on the Device to bind the Device's certificate to it (Section 3.1).

HIPS uses the hardware inventory and the hardware identifiers only to know the hardware of each Device, to recognize each machine and each of its GPUs as one unit, so that each GPU is enrolled, scheduled and paid once, to detect hardware enrolled more than once and other fraud, to keep hardware involved in fraud or other abuse from returning, and as evidence in a review, a complaint or a dispute. It uses the inventory to send each Device only work that its hardware can perform; it compares the identifiers of Devices to detect one GPU or one machine enrolled more than once, hardware that misreports what it is, and a Device that matches one of a Program Partner's (Section 3.8(d)); it checks them against its hardware blocklist when a Device enrolls and each time it connects; and it relies on them as evidence where a review, a complaint, a dispute or a legal claim about a Device, its earnings or its hardware turns on which hardware it is. HIPS does not give them to Buyers, Program Partners or other Providers, and never uses them for advertising.

Where a person at HIPS has established, after a review, a breach of the Provider Agreement committed with a Device, such as fraud or another abuse, HIPS may add the Device's GPU, by its UUID and serial number, and its machine, by its serial number, UUID and board serial number, to its hardware blocklist (Provider Agreement Section 17.13). A Device whose GPU or machine matches an entry of the hardware blocklist takes no work and cannot be enrolled again, under any Account or after any reinstallation. Whoever holds blocked hardware, such as a person who bought a used GPU, may ask for a review by a person at HIPS, who answers within thirty (30) days and removes the entry where the hardware has passed to someone who took no part in the abuse, or where it otherwise no longer serves its purpose. An entry names only the hardware's identifiers listed above, never a value shared by many Devices, and lapses after the period of Section 7.8 unless a person at HIPS renews it on a new finding. HIPS tells the Provider of a Device that matches an entry that its hardware is blocked and how to ask for that review, without disclosing who held the hardware before.

HIPS reads the hardware inventory and the hardware identifiers from a Device because the service you ask for when you enroll it, the enrollment of a machine and the scheduling and payment of each of its GPUs as a unit of its own (Provider Agreement Sections 5.5 and 5.14), requires HIPS to know the hardware and to recognize the machine and each GPU, including after a reinstallation; that reading is strictly necessary for that service. HIPS keeps the hardware inventory and the hardware identifiers as the Provider App reports them, in the Device's record in its database, and compares those values directly with the records of other Devices and with the hardware blocklist. It keeps the values themselves, and not hashes of them, because it needs them to recognize the same hardware across reinstallations, changes of operating system and updates of the Provider App, including where a maker or a driver reports an identifier in another form, and to check a claim by a Provider, or by a seller or reseller of hardware, about which unit they hold or sold against the serial number on an invoice, a label or a warranty record, which hashes of them would not reliably allow. Only HIPS's authorized personnel can read them, in HIPS's administration tools and as far as their work for the purposes of this Section requires, and the database that holds them is protected by the measures of Section 8, including encryption at rest and access control. Section 4.1 states the legal basis for this processing, and Section 7.8 how long HIPS keeps the inventory, the identifiers and the entries of the hardware blocklist.

3.10

Crash reports. When a part of the Provider App, or an engine it runs, stops unexpectedly, hangs or fails to update, the Provider App sends HIPS a crash report, if you have agreed to send them.

  1. (a)Only with your consent, with one switch. When you enroll a Device, the Provider App asks whether it may send crash reports, with neither answer selected in advance. You can change your answer for each Device at any time: in the Provider App's terminal view, in the Support part of its Settings window on Windows and macOS, or in the Console's settings of the Device, which keep the same setting. Once you turn crash reports off, the Provider App sends no further report, including a report it had not yet sent, and deletes the reports it had queued. Declining or turning them off is not a breach of the Provider Agreement (Provider Agreement Section 5.10(d)) and has no other effect on your use of the Service.
  2. (b)What a report carries. A random identifier of the report; which part of the Provider App, or which engine, failed, and the kind of failure (a crash, a hang, an abort, an engine that stopped, or a failed update); when it happened, how long the process had run and how many identical failures the report stands for; the versions of the Provider App and of the engine, the engine's build and the catalog model it was running, never the name of a Customer Model; the operating system, its version and its build; the GPU's maker and model and its driver version; the exception or exit code and, for a fault in memory, only its kind and the program file and position where it happened, never the contents or value of the address; where in the code it stopped, as the names of program files (never a full path), their build identifiers and the positions in them that the Provider App works out on the Device; the identifier of each attempt it was serving; the last events of its own log, which are names and codes with no content (Provider Agreement Section 5.14); the last measurements of the Device that Section 3.1 lists; and how the report was captured.
  3. (c)What a report never carries. The contents of the Device's memory, a memory dump or core dump, Request Content, outputs, prompts or model weights, the Device's computer name, user or account names, full file paths, or the signals of Section 3.5 that stay on the Device.
  4. (d)Where it goes. A report travels over the Device's authenticated connection to the regional processing location to which the Device is connected, and from there to HIPS's systems in Ireland, where HIPS matches the code addresses to the functions and source lines of its own releases. HIPS then forwards it to its error-reporting service, Rollbar, in the United States (Section 9.1), without the identifier of the Device or of your provider account, your name, your Country or the attempt identifier, so that only HIPS can link it to you. What HIPS forwards is the code location of the failure as functions and source lines of HIPS's releases, the kind of failure, the versions of the Provider App and of the engine, the operating-system build, the GPU model and driver, a signature that groups identical failures, the report's random identifier and HIPS's own reference for it. Rollbar processes it in the United States and keeps it for the period of Section 7.11.
  5. (e)What HIPS uses it for. HIPS groups the crash reports of all Devices whose owners send them by app version, operating-system build, GPU model, driver and engine version, and uses them to find and fix faults in the Provider App and its engines; to halt a staged release of the Provider App whose crash rate rises; and to mark a combination of graphics driver and GPU that fails as not eligible for work until its driver is updated, in which case the Console tells you which driver to install (Section 5). A crash report is not one of the methods by which HIPS verifies your work, and never alone a ground for a finding of fraud (Provider Agreement Sections 22.2 and 22.3).
  6. (f)Who sees it. HIPS shows crash reports to no Buyer, no Program Partner and no other Provider.

Section 4.1 states the legal basis for crash reports, and Section 7.11 how long HIPS keeps them.

Section 03
  1. 3.1Categories
  2. 3.2Tax Information of Providers and Program Partners
  3. 3.3Payouts
  4. 3.4No crypto-asset benefit and no wallet
  5. 3.5What the Provider App never sends
  6. 3.6Business verification
  7. 3.7The face check and your consent
  8. 3.8The Affiliate Program
  9. 3.9Device hardware, hardware identifiers and the hardware blocklist
  10. 3.10Crash reports
Copy link

04How we use Personal Data and our legal bases

4.1

Purposes and legal bases. HIPS uses Personal Data for the following purposes, and relies on the legal basis stated for each.

TablePurposes of processing and their legal bases
PurposeData usedLegal basis
Operating and securing the Website, including delivering the explainer filmWebsite dataHIPS's legitimate interest in providing the Website you request and keeping it secure (Article 6(1)(f))
Sending early-access updates and invitations, including, if you asked for it on the Affiliate program page, one notice when the Affiliate Program opensEarly-access registrationYour consent (Article 6(1)(a)), given when you register and confirm your email address; HIPS sends these updates only with that consent, as the rules on electronic direct marketing also require, and keeps the record of it
Sending other HIPS news and product announcements, only if you choose themYour email address and your marketing choiceYour consent (Article 6(1)(a)), given separately from your registration
Understanding interest from the optional answers and the derived country, to plan the launch and to weigh invitations, provider payouts and sanctions screening by countryEarly-access registrationHIPS's legitimate interest in planning its launch and deciding whom to invite (Article 6(1)(f)); HIPS derives only a two-letter country code from the network address of your submission, never stores the address, and uses the code only for this purpose and to prevent abuse of its forms; you may object as Section 11.2 describes
Preventing abuse of the forms and of HIPS's email deliveryHashed IP address and user agent, email delivery events, trust and safety recordsHIPS's legitimate interest in keeping its forms and email delivery free of abuse (Article 6(1)(f))
Answering inquiriesInquiries, communicationsHIPS's legitimate interest in answering people who contact it (Article 6(1)(f)), or steps taken at your request before entering into a contract (Article 6(1)(b))
Creating and administering Accounts and Workspaces: sign-in, sessions, memberships, authorized devices and tools, and the audit logAccount DataPerformance of the contract with you (Article 6(1)(b)); for a Member of a Customer's Workspace, HIPS's legitimate interest in providing the Workspace to the Customer (Article 6(1)(f))
Establishing your status as a Consumer or a Business User and your Country, and applying the terms, prices, taxes, payment and payout methods, dispute track and country restrictions that follow from them (Section 4.3)Account Data, Usage Data, Billing data, Payout data, Tax InformationPerformance of the contract (Article 6(1)(b)); compliance with VAT and sanctions law (Article 6(1)(c)); HIPS's legitimate interest in applying to each person the terms and the law that fit that person (Article 6(1)(f))
Verifying the identity of every person HIPS onboards; screening against sanctions lists at onboarding, again before each payout and at each re-verification; asking 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, but not on a fixed schedule; confirming that you are at least eighteen (18) years old (Section 12); keeping one verified identity per person; and recognizing a person whose Account, Workspace, provider account or participation in the Affiliate Program HIPS closed for cause (Section 7.9)Identity verification records, Account Data, Payout data, trust and safety recordsFor sanctions screening, compliance with HIPS's legal obligations under the sanctions regulations of the European Union, which apply to HIPS directly (Article 6(1)(c)), and, for screening against the lists of other countries, HIPS's legitimate interest in not dealing with persons whom those countries sanction (Article 6(1)(f)); for identity verification, re-verification, the age check, one identity per person and recognizing a person closed for cause, HIPS's legitimate interest in preventing fraud, abuse and duplicate Accounts on its marketplace (Article 6(1)(f)), since HIPS is not a designated person under section 25 of the Criminal Justice (Money Laundering and Terrorist Financing) Act 2010 of Ireland: it is not a credit institution or a financial institution within that Act, holds no payment, e-money or crypto-asset service authorization, accepts no cash and provides none of the other services that section 25 lists, and so it does not verify identity under that Act; for the automated face check, your explicit consent (Article 9(2)(a)), which is freely given because you may verify through the face check by a person instead (Section 3.7(d)). HIPS screens only against sanctions lists, never against lists of politically exposed persons or of criminal convictions or offenses
Confirming, after a deletion, who may change where HIPS pays an amount it owes, and holding a payout where neither a match of HIPS's identifiers of a natural person (Section 3.7) nor the check of other evidence confirms the person asking (Section 11.5)The documents sent for the check by a person, identity verification records, Payout data, communicationsHIPS's legitimate interest in paying the right person, in preventing the takeover of a payout and in defending claims (Article 6(1)(f)); HIPS asks for no special category of Personal Data for it (Section 3.1)
Providing the inference service: routing and executing Requests, returning outputs, importing and deploying Customer Models, and allocating always-on capacityRequest Content, Customer Models, Usage Data, Account DataFor the Request Content and Customer Models of a Business User, the Customer's instructions as Controller under the DPA; for those of a Consumer, performance of the contract with you (Article 6(1)(b)); for Usage Data and Account Data, performance of the contract (Article 6(1)(b))
Running Batches: storing the input file, running its lines within the chosen window, producing the output and error files and keeping them for download, holding the maximum charge and releasing it line by line, and sending the signed completion notice and its emailBatch Files, Batch records, Usage Data, Billing data, Account DataFor the Batch Files of a Business User, the Customer's instructions as Controller under the DPA; for those of a Consumer, performance of the contract with you (Article 6(1)(b)); for Batch records, Usage Data, Billing data and Account Data, performance of the contract (Article 6(1)(b))
Prompt caching: keeping caches apart for each Workspace and, in a Consumer's Workspace, for each Member and API key, sending a Request to a worker that already holds its Workspace's prefix, grouping the lines of a Batch that begin alike, billing cached input tokens only where HIPS can verify them, detecting and investigating a cache shared across Workspaces or across the Members of a Consumer's Workspace, and answering a binding order of a competent authority that concerns the Prefix Ledger (Section 6.12(c))Prefix Ledger, Usage DataFor sending a Request of a Business User's Workspace to a worker that holds its prefix and grouping the lines of its Batches, the Customer's instructions as Controller under the DPA; for a Consumer's Workspace, performance of the contract, for the Consumer's own Personal Data (Article 6(1)(b)), and HIPS's legitimate interest in answering Requests and running Batches efficiently, for the Personal Data of others (Article 6(1)(f)); for the Prefix Ledger, which HIPS keeps as the Controller, HIPS's legitimate interest in charging only for cache hits it can verify and in keeping each Workspace's Requests apart from every other's (Article 6(1)(f)); compliance with a legal obligation, for a binding order of a competent authority (Article 6(1)(c))
Billing: Credits and their expiry, subscriptions, payments, machine payments (Section 3.1), receipts and invoices, refunds, value added tax (validating VAT numbers and keeping the evidence of a Buyer's location), other taxes and accountingBilling data, Usage Data, Account DataPerformance of the contract (Article 6(1)(b)); compliance with accounting and tax law, including VAT law (Article 6(1)(c))
Answering a payment dispute or chargeback: giving Stripe, for the card issuer, the evidence of the purchase and of the use of the ServiceBilling data, Usage Data, Account Data, trust and safety recordsHIPS's legitimate interest in defending itself against payment disputes (Article 6(1)(f))
Running the provider program: approving Devices, knowing the hardware of each Device from its hardware inventory, assigning work within your schedule, limits and minimum price and the level of work the Device reports (Section 3.5), keeping a Device's settings the same in the Console and on the Device, and measuring and verifying workProvider and Device data, Usage DataPerformance of the Provider Agreement (Article 6(1)(b)); HIPS's legitimate interest in buying only honestly performed GPU Time (Article 6(1)(f))
Recognizing each machine and each of its GPUs as one unit, so that each GPU is enrolled, scheduled and paid once; detecting hardware enrolled more than once and other fraud; keeping hardware involved in fraud or other abuse from returning, by comparing the hardware identifiers of Devices and keeping and applying the hardware blocklist; and relying on the hardware identifiers as evidence in a review, a complaint or a dispute (Section 3.9)Provider and Device data, trust and safety recordsHIPS's legitimate interest in preventing fraud and abuse on its marketplace and in keeping the integrity of its network of Devices, including against hardware that returns under another Account or after a reinstallation (Article 6(1)(f)), which Recital 47 of the GDPR recognizes. HIPS has weighed that interest against your interests and those of whoever later holds hardware on the blocklist: the hardware identifiers describe components, not you or what you do, and the computer name, the labels of the drives and the asset tag are never sent; HIPS keeps the values themselves because it needs them to recognize the same hardware across reinstallations and to check a claim of a Provider, or of a seller or reseller of hardware, about which unit is concerned, which hashes of them would not reliably allow; only HIPS's authorized personnel can read them, in a database protected as Section 8 describes, including by encryption at rest; they are kept only for the periods of Section 7.8; an entry is made only after a person at HIPS has established a breach of the Provider Agreement committed with the Device; it names only the hardware, never its later holder; the later holder is told that the hardware is blocked and how to ask for a review, without learning who held it before, and the match alone leads to no other measure; a person at HIPS removes the entry where it no longer serves its purpose; and every entry lapses after the period of Section 7.8
Receiving and using crash reports from the Provider App: finding and fixing faults, halting a staged release whose crash rate rises, and marking a combination of graphics driver and GPU not eligible for work until its driver is updated; forwarding them to Rollbar (Section 3.10)Provider and Device data (crash reports)Your consent (Article 6(1)(a)), which you give or refuse when you enroll a Device and may withdraw at any time with the switch of Section 3.10(a), without affecting reports already sent; it is also the consent that Article 5(3) of Directive 2002/58/EC requires for reading the crash record on your Device. HIPS processes no special category of Personal Data for this purpose
Measuring the round trips between a Device and HIPS's regional processing locations, to connect the Device to the location that serves it best and as evidence of where the Device is, on which the Requests it may take depend (Sections 3.1 and 10.3)Provider and Device dataPerformance of the Provider Agreement (Article 6(1)(b)); HIPS's legitimate interest in confirming the location of each Device, on which the transfer safeguards of Section 10.3 depend (Article 6(1)(f)); HIPS keeps the round trips for the period of Section 7.8
Routing a Request to the nearest regional processing location, forwarding it to another region's location where the first has no eligible capacity, and forwarding a Request that requires a region to that region (Section 10.2)Request Content, Usage DataFor the Request Content of a Business User, the Customer's instructions as Controller under the DPA; for that of a Consumer, performance of the contract with you (Article 6(1)(b)); for Usage Data, performance of the contract (Article 6(1)(b))
Telling Buyers who processes their Personal Data: showing a Buyer whose Workspace allows the Personal Pool the Providers that may receive its Requests, each by a pseudonymous identifier and Country; keeping the record of the Provider and Device that ran each Request; and showing the owner and admins of the Workspace of a Buyer that is a Business User and the Controller, in the Console, and giving a supervisory authority that asks, the name, Country and contact address of each Provider on the Workspace's list and of each Provider whose Device processed that Buyer's Personal Data (Section 9.3)Account Data, Provider and Device data, Usage DataHIPS's legitimate interest in acting as a processor that lets each Buyer know who processes its Personal Data, as the European Data Protection Board reads Article 28 of the GDPR in its Opinion 22/2024, and in meeting its obligations under the DPA (Article 6(1)(f)), which HIPS has weighed against Providers' interests: the list shows only a pseudonym and a Country, and a Provider's name, Country and contact address go only to the owner and admins of the Workspace of a Buyer that is a Business User and the Controller of Personal Data that the Provider processes or may process, under a duty of confidentiality, which the Provider Agreement tells every Provider before enrollment; compliance with a legal obligation (Article 6(1)(c)), for information a supervisory authority orders under Article 58(1) of the GDPR
Settling and paying Earnings: applying the published conditions of Settlement, holds, adjustments, the forfeiture of Earnings and the Fraud Costs after a finding of fraud, the netting account, self-billed statements, and payouts through Stripe Connect and Stripe Global Payouts, and keeping the record of what HIPS owes until a payout method opens in a Provider's Country (Section 3.3(g) and (h))Earnings and settlement records, Provider and Device data, Payout data, Tax Information, trust and safety recordsPerformance of the Provider Agreement (Article 6(1)(b)); compliance with VAT and accounting law, including the rules on self-billing (Article 6(1)(c)); HIPS's legitimate interest in protecting itself and its Buyers from fraud and in recovering its documented costs (Article 6(1)(f))
Tax compliance for Providers and Program Partners: collecting and verifying Tax Information, withholding tax where the law requires, and filing returns and reportsTax Information, Payout data, Earnings and settlement recordsAs Section 4.2 states for each item
Detecting and preventing fraud, abuse, sanctions evasion and dishonest work; keeping the Service secure; and enforcing the Terms of Service, the Provider Agreement, the Affiliate Program Agreement, the Common Clauses and the Acceptable Use PolicyUsage Data, Account Data, identity verification records, Provider and Device data, Earnings and settlement records, Billing data, trust and safety recordsHIPS's legitimate interest in protecting the marketplace, its Buyers and Providers, and HIPS from fraud, abuse and dishonest work (Article 6(1)(f)); compliance with legal obligations (Article 6(1)(c))
Applying the safeguards of Acceptable Use Policy Section 11.10 to catalog models that can generate realistic images, video or audio of people: classifying their inputs and outputs automatically, refusing the Requests and withholding the outputs the safeguards flagRequest Content, Usage Data, trust and safety recordsHIPS carries out this classification as the Controller, for every Buyer, for the safety of the Service and its own compliance (DPA Section 14.2); from 2 December 2026, where Article 5(1), points (ba) and (bb), and Article 5(1a) of Regulation (EU) 2024/1689, as Regulation (EU) 2026/1744 amends them, apply to HIPS, its basis is that legal obligation (Article 6(1)(c)), and otherwise HIPS's legitimate interest in preventing the generation of child sexual abuse material and intimate imagery made without consent (Article 6(1)(f)); the classification keeps nothing of what it does not flag
Telling you of a restriction, a suspension, a closure or a hold and its ground, and reviewing it at your requestTrust and safety records, Account DataCompliance with legal obligations, including Article 17 of Regulation (EU) 2022/2065 where it applies (Article 6(1)(c)); performance of the contract (Article 6(1)(b))
Training on Request Content, the content of Batch Files included, on plans whose request-data policy allows it: developing, fine-tuning and evaluating the models HIPS itself operates and offers through the Service, after filtering out special categories of Personal Data, Personal Data relating to criminal convictions and offenses, and data concerning children (Sections 2.4, 6.6 and 6.10)Request ContentFor the Request Content of a Consumer, HIPS's legitimate interest in Training (Article 6(1)(f)), weighed and safeguarded as Section 6.10 states, to which you may object with one switch and keep your plan, except for a Consumer whose Country is the United States, for whom the basis is the consent of Section 14.4(g) (Article 6(1)(a)); for Personal Data in the Request Content of a Business User, HIPS's legitimate interest in Training (Article 6(1)(f)), on the Customer's instruction; never for a special category of Personal Data, never for Personal Data relating to criminal convictions or offenses, and never for Personal Data concerning a child; HIPS is the Controller of training copies (Section 2.4)
Processing special categories of Personal Data about you that you include in Request Content, to answer your Requests and to keep that data out of training copiesRequest ContentYour explicit consent (Article 9(2)(a)), optional and withdrawable at any time (Section 6.8)
Service notices: changes to terms and policies, security notices, and notices about your Account, Workspace, Devices, Earnings or payoutsAccount DataPerformance of the contract (Article 6(1)(b)); compliance with legal obligations (Article 6(1)(c))
Operating, analyzing and improving the ServiceUsage Data, Provider and Device data, aggregated dataHIPS's legitimate interest in running and developing its Service (Article 6(1)(f))
Running the Affiliate Program, once it opens: creating a Program Partner's record, code and link, counting clicks, attributing referrals, applying the Referral Discount to a Referred Person's first top-up, qualifying referrals, calculating, holding, reversing and paying commissions through Stripe Connect or Stripe Global Payouts, and telling Program Partners of their state, as totals and reason categories (Section 3.8(c))Affiliate Program data, Account Data, Usage Data, Billing data, Earnings and settlement records, Payout data, Tax InformationFor a Program Partner, performance of the Affiliate Program Agreement (Article 6(1)(b)) and compliance with tax law (Article 6(1)(c)); for a Referred Person, HIPS's legitimate interest in attributing referrals and paying the commissions it owes for them (Article 6(1)(f)), and, for the Referral Discount, performance of the contract with you (Article 6(1)(b))
Checking that Program Partners promote HIPS lawfully: reviewing, recording and keeping copies of Partner Content, and the placement, targeting and traffic-source information a Program Partner gives (Section 3.8(a))Affiliate Program dataHIPS's legitimate interest in ensuring that its program is promoted in compliance with the Affiliate Program Agreement and with advertising and consumer law, and in defending claims about it (Article 6(1)(f))
Preventing fraud in the Affiliate Program: the checks of Section 3.8(d), holds, reversals and clawbacks of commissions, and the suspension and termination of Program PartnersAffiliate Program data, Account Data, identity verification records, Billing data, Provider and Device data, Payout data, trust and safety recordsHIPS's legitimate interest in preventing self-referral, collusion and payment fraud (Article 6(1)(f))
Recovering amounts owed to HIPS, including through a collection agency or legal proceedingsAccount Data, Billing data, Earnings and settlement records, communicationsHIPS's legitimate interest in being paid what it is owed (Article 6(1)(f))
Complying with the law, responding to lawful requests, including delivering to an authority an amount HIPS owes where an unclaimed property law requires it (Section 11.5), and establishing, exercising or defending legal claims in court or in arbitrationAny of the above, as necessaryCompliance with legal obligations (Article 6(1)(c)); HIPS's legitimate interest in protecting its rights (Article 6(1)(f))
4.2

Why HIPS collects Tax Information. HIPS needs each item of Tax Information for the reason, and relies on the legal basis, that the table below states.

TableWhy HIPS collects Tax Information
InformationWhy HIPS needs itLegal basis
Your status, and your declaration whether you supply GPU Time as a Business User or as a private individual, with your business registration number or VAT number if you are a Business UserIt decides how VAT applies to the GPU Time HIPS buys from you, and which clauses and which dispute track of the Common Clauses apply to youPerformance of the Provider Agreement (Article 6(1)(b)); compliance with VAT law (Article 6(1)(c))
Registration as a sole proprietor (FIE) or a company in EstoniaEstonian law makes HIPS liable to pay social tax on payments for services to private individuals resident in Estonia, even though HIPS is not resident there, but not on the business income of registered sole proprietors or on payments to companies (sections 2(1), 4 and 9(1) of the Estonian Social Tax Act); HIPS therefore accepts Estonian private individuals as Providers and Program Partners only as registered sole proprietors or through a companyPerformance of the Provider Agreement (Article 6(1)(b)); HIPS's legitimate interest in not incurring a foreign tax it cannot pass on (Article 6(1)(f))
Legal name, primary address, date of birth, taxpayer identification numbers and the countries that issued them (or place of birth), and VAT numberDAC7 requires a platform operator to collect and verify this information from each seller resident in a Member State and to report it with the consideration paid. Whether DAC7 applies to GPU Time is not yet confirmed, so HIPS collects it in order to comply if it does. Your name, address and VAT number also appear on the self-billed statements that VAT law requires for the GPU Time HIPS buysCompliance with legal obligations under Irish and EU tax law (Article 6(1)(c)); until DAC7's application to GPU Time is confirmed, HIPS's legitimate interest in being able to comply with it (Article 6(1)(f))
Tax residence self-certification and treaty documentationTo establish whether a tax rule requires HIPS to withhold tax from a payment to you and whether a tax treaty reduces it, and to document a Provider's foreign status for United States tax reportingHIPS's legitimate interest in applying the correct tax treatment to its payments (Article 6(1)(f)); compliance with a legal obligation where Union or Irish law requires the withholding (Article 6(1)(c))
Tax reference numberIrish tax law requires HIPS to report to the Revenue Commissioners its payments for services to persons resident in Ireland, with their tax reference number, on Form 46G (sections 889 and 894 of the Taxes Consolidation Act 1997)Compliance with a legal obligation (Article 6(1)(c))
Form W-9United States tax law requires a payer of reportable amounts to obtain the payee's taxpayer identification number in order to file information returns, and to withhold tax (backup withholding) where none is given; payments for GPU Time performed in the United States may be such amountsHIPS's legitimate interest in complying with the United States tax law that applies to its payments (Article 6(1)(f)); performance of the Provider Agreement (Article 6(1)(b)). United States law cannot be a legal obligation under Article 6(1)(c), which requires European Union or Member State law (Article 6(3) of the GDPR)
Form W-8BEN, Form W-8BEN-E or a self-certificationTo document that you are not a United States person, so that HIPS does not report or withhold United States tax on its payments to youAs for Form W-9
Validation of taxpayer and VAT identification numbersTo check that the information is reliable, as DAC7 requires, and to apply the correct VAT treatmentAs for the number validated

HIPS uses Tax Information only for payouts, tax compliance, the prevention of fraud and the defense of legal claims, and never for marketing.

4.3

Your status and your Country. As a Buyer, HIPS asks whether you use the Service as a Consumer or as a Business User and relies on your declaration. As a Provider, you declare under the Provider Agreement whether you supply GPU Time as a Business User, giving your business registration number or VAT number, or as a private individual; both may be Providers (in Estonia, only as a registered sole proprietor or a company, Section 3.2), and if you declare that you are a private individual, or a court finds that you are a Consumer, the clauses and the dispute track written for Consumers apply to you. 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. Your Country is, for an individual, the country of your habitual residence and, for an organization, the country of its registered office or, where its central administration is in another country, that country; it is never your nationality or the country that issued your identity document. Your status and your Country decide which terms and dispute track of the Common Clauses apply to you, how VAT applies, which payment and payout methods and which features are offered to you, whether HIPS may serve you as a Consumer, which it does only in the European Economic Area and the United States, selling only to Business Users elsewhere (Terms of Service Section 3.4), and whether HIPS may serve you at all under sanctions and export-control law. You declare your Country, and HIPS checks it against the evidence of residence it holds: the billing address and the country of the card or bank account used for a payment, as Stripe holds them; the address, and the country of the bank account, in your payout profile; the address in your Tax Information; and the country of the network address of your sessions, which are the kinds of evidence that Articles 24b and 24f of Implementing Regulation (EU) No 282/2011 use for the place of a customer. Where an item points to another country, HIPS asks you for further evidence, such as a certificate of residence or registration from a public authority, a tax residence certificate, a residence permit, or a recent bank statement or utility bill showing your address, and suspends only the features that depend on your Country until it is resolved (Common Clauses Section 2.1). HIPS never uses your nationality or the issuing country of your identity document as evidence of your Country. Before you declare it, HIPS uses the location of your network address only to decide what the Website and the Console show you.

4.4

Legitimate interests. Where HIPS relies on its legitimate interests, it has balanced them against your interests and rights, and you may object at any time as Section 11.2 describes. You may ask HIPS for information on how it balanced its interests against yours at hello@hips.com.

4.5

Consent and how to withdraw it. Where HIPS relies on your consent, you may withdraw it at any time, without affecting processing that took place before. Withdrawing from early access ends the updates and deletes your optional answers; unsubscribing from HIPS news ends that news only. Each relevant email carries a link for each. You withdraw your consent to crash reports with the switch of Section 3.10(a), your consent under Section 6.8 in the Console, and, if you are a Consumer in the United States, your consent to training with the training switch (Section 14.4(g)). HIPS does not ask other Consumers for consent to training: it relies on its legitimate interest, to which you may object with the training switch (Section 6.10). If you withdraw your consent to the automated face check before it runs, HIPS does not run it, and you may verify through the face check by a person instead (Section 3.7(d)); if you withdraw it afterwards, Section 3.7(a) applies.

4.6

No sale and no advertising. HIPS does not sell Personal Data and does not use it for targeted advertising, and does not share it for cross-context behavioral advertising; HIPS's disclosures to its Sub-processors, to Stripe and Bynn for the services you use, and at your direction are not sales. HIPS's emails carry no tracking pixel and no click tracking; HIPS keeps the open and click tracking of its email service turned off.

4.7

Information you must provide. Some Personal Data is required, and not providing it has these consequences:

  1. (a)your email address, to register for early access; without it HIPS cannot register you or send you updates;
  2. (b)your name and email address, to create an Account; without them HIPS cannot create the Account;
  3. (c)identity verification, which is a requirement of the contract with HIPS and not of any law; the sanctions screening within it is how HIPS meets its obligations under the sanctions regulations of the European Union (Section 4.1); the face check within it is a requirement necessary to complete verification, and so to receive Credits, the Free Allowance included, to buy, to run Requests and to earn; you choose between the automated face check, which runs only on your explicit consent, and the face check by a person (Section 3.7(d)); you are not obliged to undergo either, no contract obliges you to, and Section 3.7(d) states what follows if you decline both. The owner of a Workspace passes verification before any Credits are granted, the Free Allowance included, and before any Request runs, a Provider passes it before any Device becomes eligible for work, and a Program Partner passes it before HIPS issues a referral code and link. Until then, a Workspace holds no Credits and accepts no Request, and a Device may install, enroll and report but takes no work and accrues nothing;
  4. (d)your declaration of status as a Consumer or a Business User and of your Country and, for a business, its name, country and VAT or registration number, which are a requirement of the contract; without them HIPS cannot apply the terms, prices and taxes that fit you, and may decline to open the Workspace or provider account;
  5. (e)the billing details Stripe Checkout asks for, to make a payment, or, for a machine payment, the Shared Payment Token that the agent presents; without them the payment cannot be made;
  6. (f)the Device data the Provider App sends (Section 3.1), including the hardware inventory and the hardware identifiers (Section 3.9), to take part as a Provider; without it a Device cannot be approved or receive work; crash reports are sent only if you agree, and you may turn them off at any time (Section 3.10);
  7. (g)a payout profile and a payout method, before your first payout; without them HIPS cannot pay out your Earnings or, for a Program Partner, your commissions; and
  8. (h)the Tax Information that applies to you (Section 3.2). Where a tax rule requires it, giving it is a statutory requirement that tax law places on HIPS and a requirement of the Provider Agreement. Without it HIPS cannot settle or pay your Earnings. Where a tax reporting rule requires information you have not given after HIPS's request and two reminders in writing, HIPS may, sixty (60) days after the second reminder, hold your payouts and stop assigning paid work to your Devices until you give it, and, if you still have not given it twenty-four (24) months later, pay you what it held and close your provider account (Provider Agreement Section 15.12). If you are a United States person and do not give a correct taxpayer identification number, United States law may require HIPS to withhold tax from your payouts.

Everything else is optional, including the optional answers at early access; leaving them out does not affect your registration.

Section 04
  1. 4.1Purposes and legal bases
  2. 4.2Why HIPS collects Tax Information
  3. 4.3Your status and your Country
  4. 4.4Legitimate interests
  5. 4.5Consent and how to withdraw it
  6. 4.6No sale and no advertising
  7. 4.7Information you must provide
Copy link

05Automated decisions and profiling

5.1

Where HIPS uses automated processing. HIPS uses automated processing, including profiling, for:

  1. (a)identity verification: Bynn checks your identity document, performs the automated face check if you choose it, with your explicit consent (Section 3.7), screens you against sanctions lists, and returns a result;
  2. (b)sign-up risk: assessing the risk of an early-access registration, an invitation or a new Account, using a fraud-scoring service whose provider acts for HIPS as its Sub-processor, under a processing agreement that meets Article 28 of the GDPR and forbids that provider to use the data for any purpose of its own (Section 9.1);
  3. (c)fraud and abuse signals: detecting patterns in Usage Data, Account Data and payment events that suggest fraud, abuse or sanctions evasion, from metadata and rate signals only;
  4. (d)provider trust: measuring whether a Device performs work honestly, with test jobs, timing checks, probes and the sampling of results;
  5. (e)Settlement: applying the published conditions of the Provider Agreement to decide which Earnings of a period become payable;
  6. (f)country rules: applying to you, from your Country, the payment and payout methods, the features and the restrictions that the law of your Country and HIPS's terms allow;
  7. (g)safety classification: for a catalog model that can generate realistic images, video or audio of people, classifying that model's inputs and outputs automatically, and refusing the Requests and withholding the outputs that the classification flags, to prevent child sexual abuse material and intimate imagery made without consent (Acceptable Use Policy Section 11.10) (HIPS tests those safeguards before it lists such a model and after every change, and keeps no content they flag except where the law requires it to preserve or report it, Section 7.1(e));
  8. (h)Affiliate Program checks: comparing each referral with its Program Partner as Section 3.8(d) describes, and deciding from the Affiliate Program's published conditions whether a referral qualifies and when a commission becomes payable;
  9. (i)the hardware blocklist: comparing the hardware identifiers of each Device with the entries of the hardware blocklist when the Device enrolls and each time it connects (Section 3.9); and
  10. (j)crash reports: grouping the crash reports of all Devices whose owners send them; halting a staged release of the Provider App when its crash rate on a platform is higher than that of the release before it, once enough Devices have run it for the difference to be reliable; and marking a combination of graphics driver and GPU model not eligible for work until its driver is updated, when that driver version fails on that GPU model more often than the model's other driver versions, once enough Devices have run it for the difference to be reliable (Section 3.10). A mark applies at once, because a Device that fails a Request harms the Buyer who sent it; a person at HIPS reviews each mark and confirms, narrows or lifts it, the Console tells you which driver to install, and you may ask a person at HIPS to review the mark of your Device (Section 5.3).

The sign-up risk assessment rates the risk that a registration, an invitation or a new Account is fraudulent or abusive, from the email address's domain and whether it belongs to a disposable email service, the country derived from the network address, the hashes of the network address and the browser's user agent (to recognize repeated registrations), the timing of the registration's steps, the optional answers, and whether the email address or the person matches a registration, an Account or an identity HIPS closed for cause; no single item decides, and the assessment only ranks and flags registrations for the administrator who decides each approval (Section 5.3). The fraud and abuse assessment never reads Request Content. It combines signals from metadata, such as a duplicate identity, a verification that changes from pass to fail, a payment dispute or inquiry, repeated failed payments, a burst of Requests far above an API key's usual peak, Requests from a new kind of network or from a blocked country, and spend that lands repeatedly on the same few Devices. Each signal carries a weight, and the combined result decides whether an Account or Workspace is flagged for review or limited. Of these steps, only a flag and a temporary limit are applied automatically; a pause, a suspension, a closure and a report to an authority are decided by a person at HIPS. HIPS does not publish the weights or the thresholds, because publishing them would let the assessments be defeated (Acceptable Use Policy Section 3.6), and it explains to you on request which of your data it used and how they led to a decision (Section 5.4). The provider trust assessment compares what a Device returns with what HIPS expects, using test jobs whose correct answer HIPS knows, timing checks, probes, and sampled jobs run again on other capacity; a mismatch holds the Device's Earnings while it is investigated. Settlement checks, for each period, that the work qualified, that verification passed, that the Device has passed its probation, that the amount is within the limit for the Device's standing, that no hold applies, and that your payout profile, Tax Information and sanctions screening are complete.

5.2

Decisions with significant effects. Some of these produce decisions that significantly affect you:

  1. (a)a possible match against a sanctions list holds onboarding, a payment or a payout until a person at HIPS has reviewed it;
  2. (b)an Account whose holder does not pass identity verification, or declines both methods of the face check, stays inactive as Section 3.7(d) states, as Terms of Service Section 4.3 provides for retries, review and the deletion of Accounts and Workspaces that never pass;
  3. (c)a second Account that resolves to an already verified person is kept and linked to the first: it receives no Free Allowance or Referral Discount, the person may hold no second provider account or participation in the Affiliate Program, and a measure concerning the person may apply to every linked Account (Terms of Service Section 4.5); the link alone is not a measure, and you may ask a person at HIPS to review it;
  4. (d)a mismatch in a Device's results holds its Earnings; Earnings for an attempt do not accrue where two independent checks confirm a mismatch in it; a new Device's Earnings are not settled as payable until its probation passes; and a Device may be suspended automatically where an exact mismatch in its results is confirmed by a second strong signal;
  5. (e)a hold of Earnings on reasonable grounds to suspect fraud, or on another ground the Provider Agreement lists, lasts no longer than the maximum the Provider Agreement states, which is ninety (90) days, or one hundred eighty (180) days where a Buyer's payment is disputed with the card issuer (an inquiry by a card issuer alone is not a dispute), unless the law or a competent authority requires a longer hold;
  6. (f)a dispute of a card payment for a Workspace with the card issuer blocks the Credits that payment bought, and new purchases, while the dispute is open; where HIPS has reasonable grounds to suspect fraud, or the Buyer is in the United States, the dispute may also freeze the Workspace: its API keys are refused, the Console becomes read-only except for receipts, its always-on capacity stops, its owner and admins cannot create another Workspace, and, where the Buyer is also a Provider, its payouts are held up to the disputed amount and the fees the dispute may cost HIPS, until HIPS lifts the measure after the card issuer decides (Terms of Service Section 12.4);
  7. (g)Settlement decides which Earnings become payable for a period; an amount that does not meet the published conditions is not settled as payable for that period;
  8. (h)your Country decides which payment and payout methods and which features are offered to you, and HIPS refuses the Service to a person whose Country is a restricted jurisdiction; a Device located in a restricted jurisdiction takes no work, and a Device outside a Device Country, or whose location HIPS cannot confirm, takes no Request of a Buyer (Section 10.3);
  9. (i)a referral that matches its Program Partner's person, Workspace, card, payout account, Device or email address under Section 3.8(d) is rejected, or reversed with its commissions, and earns nothing;
  10. (j)a Device whose GPU or machine matches an entry of the hardware blocklist takes no work and cannot be enrolled again (Section 3.9);
  11. (k)a Device whose combination of graphics driver and GPU is marked not eligible takes no work until its driver is updated, the Console tells you which driver to install, and the Device becomes eligible again on its own once the driver is updated (Section 3.10); and
  12. (l)a flag, which changes nothing for you, and a temporary limit on a Workspace or an API key, with the time it ends, may be applied automatically from the fraud and abuse assessment; a pause, a suspension or a closure is decided by a person at HIPS (Section 5.3).
5.3

Human involvement. The decision to approve an early-access registration is made by a HIPS administrator, whom a risk assessment may inform. A referral held under Section 3.8(d) is approved or rejected by a HIPS administrator, and a Program Partner may ask a person at HIPS to review a rejected or reversed referral. A finding that a Provider committed fraud, and the forfeiture of a Device's Earnings for a period and the Fraud Costs that follow it, are decided only after a review by a person at HIPS. HIPS adds hardware to the hardware blocklist only after such a review, and a person at HIPS reviews an entry at the request of whoever holds the hardware (Section 3.9). A person at HIPS reviews every mark of a combination of graphics driver and GPU model, and reviews it again at the request of a Provider whose Device it affects. Every restriction, hold, pause, suspension or closure of a Workspace, an Account, a provider account or a Device is notified to you, with the ground relied on, on a medium you can store, together with a route to ask for its review, unless the law prohibits telling you or telling you would prejudice the prevention or investigation of fraud or a security incident, in which case HIPS tells you when that reason ceases.

5.4

Your right to human review. Where a decision based solely on automated processing produces legal or similarly significant effects for you, HIPS makes it only where it is necessary for entering into or performing a contract with you, or is authorized by law, or is based on your explicit consent. A verification outcome that relies on the biometric data of the automated face check rests on your explicit consent (Article 22(4) with Article 9(2)(a) of the GDPR), with the safeguards of this Section. Each decision of Section 5.2 that is based solely on automated processing is necessary for entering into or performing your contract with HIPS (Article 22(2)(a) of the GDPR): HIPS cannot accept, pay or keep serving a person or a Device that fails the checks on which the safety of its marketplace, of its Buyers and Providers and of HIPS's own compliance depends. HIPS relies on no law of a Member State for such decisions. For each, HIPS tells you of the decision and its ground, lets you express your point of view and contest it, and has a person with authority to change it review it at your request; on request it explains the procedure and principles it applied, which of your Personal Data it used and how they led to the decision, and it gives the thresholds and weights of its controls, which it does not publish, to a supervisory authority or court that asks for them (Case C-203/22). You may ask for a person at HIPS to review the decision, express your point of view and contest it, through the route to dispute the decision that the notice of it gives you, or by writing to hello@hips.com. A person at HIPS with the authority to change the decision reviews it, considers your point of view, and tells you the outcome.

Section 05
  1. 5.1Where HIPS uses automated processing
  2. 5.2Decisions with significant effects
  3. 5.3Human involvement
  4. 5.4Your right to human review
Copy link

06Request Content and model training

6.1

Not stored by default. A request log holds operational metadata, not stored prompts and outputs. HIPS does not store the prompts, messages, uploaded inputs or generated outputs of a Request, the request or response bodies of a Request that ends in an error, or the tokens themselves, except as Section 7.1 states, for example the Batch Files of a Batch, the answer to a task Request sent with an idempotency key, the body of an asynchronous job until the job ends, and the prompt cache a data-center worker may keep in memory for the time Section 6.12 allows. The Console playground stores no content on HIPS's servers.

6.2

The request-data policy of each plan. The policy for request inputs and generated outputs depends on the Workspace's 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. On the higher paid plan, request-data training is off by default."

TableRequest-data policy by plan
Plan (the public name of each Plan is the one the Price List of the Terms of Service gives it)Request-data policyCan the Workspace change it
Free/PAYGRequest inputs and generated outputs may be used for trainingNo
Lower paid planRequest inputs and generated outputs may be used for trainingNo
Higher paid planRequest-data training is off by defaultYes: an owner or admin may turn training on; the change is audited, shown before any Request, and applies only to Requests accepted after it

The policy applies to Consumers and Business Users alike, and to the lines of a Batch as to live Requests, with two differences for Consumers: if you are a Consumer, you may object to training with one switch and keep your plan, and HIPS then makes no training copy of your Request Content whatever the plan's policy (Section 6.10); and if your Country is the United States, training is off for the Workspaces you hold as a Consumer unless you turn it on (Section 14.4(g)).

6.3

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 separate policy for request inputs and generated outputs." No part of the Service returns a Customer Model's weights to anyone, the Customer's own Workspace included.

6.4

How the policy applies. The policy applies to catalog models and Customer Models alike. It is shown before every Request, in the playground, the API key settings, the model pages and the API's list of models, and a Request cannot override it; only a Consumer's training switch can (Section 6.10). The policy in force when HIPS accepts a Request, and the position of a Consumer's switch at that moment, are recorded with the Request and apply through every retry; for a Batch, they are recorded with each line when HIPS accepts the Batch, except that a Consumer's objection applies from the moment HIPS records it, including to lines of an accepted Batch that have not yet run (Terms of Service Section 13.4). A plan lapse never changes the policy: a lapsed subscription to the higher paid plan keeps the Workspace's policies and pauses the Workspace for inference until an owner acknowledges the request-data policy of the Free/PAYG plan or pays.

6.5

Training off is not zero retention. Where training is off, no copy of Request Content is made for training. "Turning training off is not, by itself, a promise of zero retention": Section 7.1 states when Request Content is kept.

6.6

Training copies. Where the policy allows training, each item kept for training records its provenance (the Workspace, the API key, the Request identifier, the plan and the policy at acceptance), and is curated and deduplicated after the filters have run. HIPS runs its automated filters over the Request Content 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; for a Consumer, the screening of special categories of Personal Data about you rests on your explicit consent (Section 6.8), and for a Business User it is part of the processing HIPS carries out for the Customer under the DPA, before any Request Content is made available to HIPS for training. Automated filters can miss some content; if HIPS learns that a training copy holds such data, it deletes the copy and excludes it from every dataset not yet used. 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's filters combine automated classifiers for each of those categories with detectors for the identifiers and secrets it masks; HIPS tests them before their first use and after every change against examples of each category in each language the Service supports, documents the results, and writes no training copy of a Request they cannot assess. The contributions of a Workspace paused or closed for fraud, abuse or sanctions, of any Workspace on request (a Workspace of a Business User on the Free/PAYG plan or the lower paid plan once in each calendar quarter, as Terms of Service Section 13.11 provides, which does not limit any person's objection under Section 11.2), and of a Consumer who turns the training switch off (Section 6.10) or whose contract ends (Terms of Service Section 27.7), and the Personal Data of a person who objects under Section 11.2, as far as HIPS can identify it, are excluded from every dataset not yet used and removed from retained copies; a dataset already used records the Workspaces it drew on. Where a person objects under Section 11.2, a Consumer turns the training switch off, or HIPS learns that a training copy already used held data that this Section excludes, and a dataset that holds the Personal Data concerned has already been used, HIPS, within three (3) months after it records the objection or learns of the data, retrains without it, or stops offering, every model trained on that dataset; until it has done so, and from no later than one (1) month after it records the objection or learns of the data, it applies to that model measures that prevent it from outputting the Personal Data concerned; and it tells the person who objected, where there is one, which it did. "Retention, deletion, and any other permitted uses will be set out in the service terms before production access." They are: training copies, and datasets made from them, kept for no longer than twenty-four (24) months after the Request and then deleted, a dataset's record of the Workspaces it drew on kept without content while a model trained on it is offered; a wait of at least thirty (30) days before a training copy is first used (Section 6.10(i)); access only for 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 have run, each access to an individual training copy being recorded; no use other than training; and no reliance on consent for training, except for Consumers in the United States as Section 14.4(g) states.

6.7

The responsibility of Business Users. A Customer that is a Business User decides whether its Requests contain Personal Data and is responsible, as Controller, for having a lawful basis for sending it and for informing its own data subjects, including of the request-data policy of its plan.

6.8

Consumers. If you use the Service as a Consumer, HIPS is the Controller of your Request Content (Section 2.3). Include Personal Data of other people only where you are entitled to share it. HIPS asks you not to include special categories of Personal Data, such as data concerning health, Personal Data relating to criminal convictions and offenses, or Personal Data of children in Request Content sent from a Workspace whose policy allows training or that may be served from the Personal Pool (Terms of Service Section 13.12). 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 both, as Sections 6.6 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, excludes it from every dataset not yet used and acts as Section 6.6 provides for a model already trained on it. HIPS asks you, separately from every other choice, for your explicit consent (Article 9(2)(a) of the GDPR) to process the special categories of Personal Data about you that you include in Request Content, only to answer your Requests and to keep that data out of training copies. The consent is optional; refusing or withdrawing it, at any time in the Console, does not affect your plan, your price or your access; if you have not given it, do not include such data about yourself. It does not cover such data about anyone else (Terms of Service Section 13.12(b)).

6.9

Where Requests run. Section 9.2 describes who executes a Request and what they can access while it runs.

Important for Consumers: training on your Request Content, and your switch

If you are a Consumer on the Free/PAYG plan or the lower paid plan, and your Country is not the United States, HIPS uses your Request Content to train and improve models on the basis of its legitimate interest, not your consent. You may object at any time, without giving a reason, with one switch in the Console. Objecting keeps your plan, your price and your access to the Service. HIPS brings this right to your attention, clearly and separately from any other information, and shows you where the switch is, at the latest in its first communication with you after you create your Account, and in any case before your first Request. If your Country is the United States, HIPS does not train on your Request Content unless you turn training on (Section 14.4(g)).

6.10

Training on the Request Content of Consumers. If you are a Consumer and your Workspace's policy allows training, HIPS uses your Request Content, the content of your Batch Files included, for training on the basis of its legitimate interest (Article 6(1)(f) of the GDPR). If your Country is the United States, Section 14.4(g) applies instead. HIPS assessed that basis by the three steps that the European Data Protection Board recalls in its Opinion 28/2024 on certain data protection aspects related to the processing of personal data in the context of AI models, adopted on 17 December 2024 (the interest, the necessity of the processing, and the balance between HIPS's interest and your interests, rights and freedoms), and applies the safeguards that follow them:

  1. (a)The interest. HIPS's interest is Training: using Request Content to develop, fine-tune and evaluate machine learning models that HIPS itself operates and offers through the Service, so that they serve the kinds of Requests people send to it. 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 the 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, for every Buyer, in the way DPA Section 5.3 provides for a request of a public authority: it discloses only what the law or the order compels and tells the Buyer of the request unless the law prohibits it, and except to a successor that takes over the Service under Section 9.5(f) and is bound by this commitment; a service provider that processes them only on HIPS's behalf and under its instructions is not a third party for this purpose (Section 9.8). A model that HIPS trains on Request Content 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 the GDPR is in force, and never on a Device of the Personal Pool; HIPS treats every such model as containing Personal Data, and offers it 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 the GDPR is in force and covers that Buyer (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) (Section 10.5). The interest is lawful, stated here precisely, and real and present while the Service runs.
  2. (b)Necessity. Learning from the Requests that real users send is how a model improves at them. HIPS limits what it uses: it makes no training copy where a Workspace's policy is off or where you have objected, it screens out special categories of Personal Data, Personal Data relating to criminal convictions and offenses, and data concerning children, and masks other identifying details, before any training copy is written (point (g) and Section 6.6), and it keeps training copies only for the period Section 7.1(a) states.
  3. (c)The balance. HIPS weighed that you give your Request Content to HIPS directly, in a Service that tells you of the training policy before your first Request and before every Request, so that you can reasonably expect it; that training is the policy only of the Free/PAYG plan and the lower paid plan, while the higher paid plan keeps it off by default; that Request Content may contain Personal Data of you and of others, including sensitive data, which HIPS's filters screen out before any training copy is written under point (g) rather than HIPS relying on you to leave it out; that a model trained on Personal Data may in some cases reproduce it; that training copies stay with HIPS and the service providers that process them for it, and that a model trained on them runs only in the Approved Pool, in the European Economic Area or a country with an adequacy decision, under HIPS's contract with its operator; and that training improves the models for everyone who uses the Service, not only for you.
  4. (d)Notice of your right to object. 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, and tells you then that it trains on your Request Content on the basis of its legitimate interest and where your switch is.
  5. (e)One switch, unconditionally. You may object at any time, before or after any training copy is made, with one switch in the Console, without giving a reason. Turning the switch off changes neither your plan nor your price nor your access to the Service, and you may turn it on again at any time.
  6. (f)Effect of your objection. HIPS makes no training copy of the Request Content of any Request, or line of a Batch, that runs after you turn the switch off, and excludes your earlier contributions from every dataset not yet used and removes them from retained training copies; where a dataset that holds them has already been used, HIPS retrains without them, or stops offering, every model trained on it within three (3) months, applies output measures to that model until it has done so, and tells you which it did (Section 6.6).
  7. (g)Sensitive data screened out before any copy is written. HIPS runs its automated filters over the Request Content of a Request, its input and its output, in memory, before it writes any training copy of it. It writes no training copy of a Request whose input or output the filters identify as revealing racial or ethnic origin, political opinions, religious or philosophical beliefs, trade union membership, genetic or biometric data, health, sex life or sexual orientation, or criminal convictions or offenses, or as concerning a child, or that the filters cannot assess, and it masks names, contact details, identification numbers, payment card data and authentication secrets in the input and the output before it writes the copy. The filters keep nothing of what they screen out, and can miss some content, which HIPS deletes from training copies when it learns of it, acting as Section 6.6 provides for a model already trained on it. 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 (Section 6.6).
  8. (h)Erasure and reports. You may ask HIPS to erase your contributions from training copies at any time, even where no ground of Article 17(1) of the GDPR applies, and you may report an output that reproduces your Personal Data, which HIPS assesses and answers. HIPS tries to reproduce the output you report; where it confirms it, it applies at once measures that keep the model from outputting that Personal Data, treats your report as an objection under point (f), and tells you what it did within one (1) month of receiving the report, a period it may extend as Section 11.3 states.
  9. (i)Time to object. HIPS waits at least thirty (30) days after it writes a training copy before it first uses it in training, so that an objection you make in that time removes the copy before it is used.
  10. (j)No weights. HIPS never trains on the weights of a Customer Model (Section 6.3).

Turning the switch off is an objection under Article 21 of the GDPR that HIPS honors without asking for reasons and without weighing compelling grounds against it, with the effects that point (f) states. You may ask HIPS for a summary of its assessment at hello@hips.com. HIPS weighed in particular that the Court of Justice, in Case C-252/21 (Meta Platforms), doubted that an interest in improving a product could override the interests of users who cannot reasonably expect the processing. HIPS's training differs from that case in the respects points (a) to (j) state: you give your Request Content to HIPS directly for the Service that trains on it; HIPS tells you of the training before your first Request and before every Request; it uses only the content of your own Requests, never data about you from elsewhere, and never for advertising or profiling; it screens, masks and keeps that content for a limited time; and you can stop it at any time with one switch, without any effect on your plan.

6.11

Batches. A Customer may submit a Batch (Section 1.6), which HIPS runs when capacity is free and within the Completion Window the Customer chooses (twenty-four (24) hours by default, and up to seven (7) days).

  1. (a)HIPS stores the input file, runs its lines, and keeps the output file and the error file it produces for the Customer to download, until each file is deleted under Section 7.1(c). HIPS promises no completion time. A line still unfinished when the window closes expires: it is not charged and produces no output, and every finished line is delivered.
  2. (b)The lines of a Batch run in the same pools and under the same requirements as live Requests: they may run on Devices in the Personal Pool, which take them when they come online, and on spare capacity of the Approved Pool, where the Workspace's requirements allow it (Section 9.2).
  3. (c)The content of Batch Files follows the same training rule as a live Request on the same plan, including a Consumer's switch (Sections 6.2 and 6.10).
  4. (d)When HIPS has validated a Batch, and before any line runs, HIPS holds its maximum charge against the Workspace's prepaid balance and releases it line by line as each line finishes or expires; a Batch whose maximum charge the balance cannot carry ends as failed for insufficient Credits, and nothing is held or charged for it; and HIPS notifies the Workspace when the Batch ends, by a signed notice to the endpoint the Customer set and by email.
6.12

Prompt caching and the Prefix Ledger. When Requests begin with the same text, the engine on a data-center worker may reuse the work it kept in memory for that beginning (a prompt cache), which makes the answer faster and cheaper. Prompt caching is automatic; HIPS promises no minimum lifetime for a cache and charges nothing to make one, and point (e) sets the longest a cache can be read. You may turn prompt caching 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 it and charges it no cached input token (Terms of Service Section 9.9(a); DPA Section 14.2); until that setting is available in the Console, HIPS does the same, without undue delay, when an owner or admin of the Workspace asks it to in writing at hello@hips.com. Either is also how you object to the Prefix Ledger for a Workspace (Section 11.2). A prompt cache is derived from Request Content and may contain Personal Data; HIPS processes it as the Controller for Consumers and as the Processor for Business Users under the DPA (Sections 2.2 and 2.3).

  1. (a)Caches are kept apart for each Workspace. HIPS gives each Workspace's Requests a value of its own that the worker mixes into its cache, narrowed further by the cache key a Customer may set, so that no Request of one Workspace can reuse, or learn from the speed of an answer, what another Workspace sent. HIPS sets that value itself and refuses one sent by a client. Within a Workspace, a Request may reuse the cache of any other Request of the same Workspace, whichever Member, API key or tool sent it, so a Member could tell from the speed of an answer whether another Request of the same Workspace began with the same text; a Customer can keep those caches apart by sending a different cache key for each Member or API key. In a Workspace held by a Consumer, HIPS keeps the caches of each Member and each API key apart by default, and an owner of the Workspace 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.
  2. (b)No cache on personal Devices at launch. Devices in the Personal Pool run with their cache between Requests switched off, so a Device keeps nothing of one Request for the next, and no cached input token is billed for work on a Device. A Provider may never switch on a cache or a learning feature that HIPS has switched off (Provider Agreement Section 6.12). HIPS will update this Notice before a Device may keep a cache, which it will allow only in memory, never on disk, once the engine keeps Workspaces apart and clears on command.
  3. (c)The Prefix Ledger. To charge for a cached input token only when it can verify it, the HIPS API keeps the Prefix Ledger: for each Request to a language model served by a data-center worker whose prompt cache is on, it splits the prompt's tokens into blocks and records pseudonymized hashes of those blocks, 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, with the worker that served the Request and the time. The hashes are derived from Request Content and are Personal Data wherever the prompt contained Personal Data: HIPS cannot read a prompt from them, but could check with them whether a Workspace sent a known text, and uses them only for the purposes of this Section and to answer a binding order of a competent authority, which HIPS treats as a request for the Customer's own data: it discloses only what the order compels, tells the Customer unless the law forbids it, and, for a Business User, follows DPA Section 5.3. The Prefix Ledger does not keep the text of a prompt. HIPS charges the lower of the worker's count of cached tokens and the count the Prefix Ledger supports, and treats a worker's count above the ledger's for that scope as a fault in keeping Workspaces, or the Members of a Consumer's Workspace, apart, which it investigates as a security incident (Section 8) and handles as a breach affecting Personal Data until it establishes that no Personal Data of one Workspace, or of one Member of a Consumer's Workspace, reached another, and notifies a Business User of it once it has not established that within twenty-four (24) hours after the fault is detected (DPA Section 11.6). HIPS also uses the Prefix Ledger to send a Request to a worker that already holds its Workspace's beginning, and to group the lines of a Batch that begin alike; for a Business User, it does so as the Processor under the DPA, as part of answering the Customer's Requests (Section 2.2). HIPS keeps the Prefix Ledger as the Controller, for the Workspaces of Business Users too, only to charge cached input tokens it can verify, to investigate a fault in keeping caches apart and to answer a binding order of a competent authority (Section 2.1); Section 11.6 states how HIPS handles a request or an objection about it.
  4. (d)How long the Prefix Ledger keeps a hash. HIPS records the Prefix Ledger only for Requests served by data-center workers whose prompt cache is on, and never for a Workspace whose prompt cache is turned off under Terms of Service Section 9.9(a). It deletes each record no later than the maximum lifetime of a prompt cache under point (e) 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. 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.
  5. (e)How long a cache can be read. A prompt cache lives only in the memory of the data-center worker that made it, never on its disk, and ends when the engine needs that memory, when the engine restarts and when the worker stops. 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 (point (a)), and at once when the Workspace is deleted, when the Customer's agreement ends or when the Customer asks; 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.
Section 06
  1. 6.1Not stored by default
  2. 6.2The request-data policy of each plan
  3. 6.3Model weights
  4. 6.4How the policy applies
  5. 6.5Training off is not zero retention
  6. 6.6Training copies
  7. 6.7The responsibility of Business Users
  8. 6.8Consumers
  9. 6.9Where Requests run
  10. 6.10Training on the Request Content of Consumers
  11. 6.11Batches
  12. 6.12Prompt caching and the Prefix Ledger
Copy link

07Retention

7.1

Request Content. Request Content is not kept after a Request is answered, except:

  1. (a)on a plan whose policy allows training, a copy kept for training, for no longer than twenty-four (24) months after HIPS accepted the Request it copies, unless Section 6.6 requires its earlier removal;
  2. (b)the results of an asynchronous job and the inputs uploaded for a task, kept for seven (7) days after the job completes for results and twenty-four (24) hours after upload for inputs, and less where the Customer deletes them; the request body of an asynchronous job, kept as an encrypted object from its acceptance until the job ends, and then deleted; and, where a Request to the task API carries an idempotency key, its completed answer, kept as an encrypted object for twenty-four (24) hours so that a retry with the same key returns the same answer without running or charging the Request again, and then deleted;
  3. (c)the Batch Files of a Batch: the input file is kept for thirty (30) days after it is uploaded or, where a Batch that uses it is still open when those thirty (30) days end, until that Batch ends, and the output file and the error file for thirty (30) days after HIPS produces them, and each is then deleted from the Service; a file is deleted sooner when the Customer sets a shorter expiry for it or deletes it. Batch Files are held only as encrypted objects in object storage that is not included in HIPS's backups, and deleting a Batch File removes every stored version of it, so no copy of the file remains in the Service after its deletion, except a training copy made from its content where the Workspace's policy allows Training (point (a)), which deleting the file does not remove (DPA Section 12.2; Section 6.6 states how to have it excluded), and a verification sample still being compared (point (d)). The record of the Batch, which holds no Request Content other than the metadata and the file names of Section 3.1, is kept as Usage Data (Section 7.3);
  4. (d)a Request sampled to verify a Provider's work, whose input and output are kept only for that comparison and deleted when it completes, and in any case within seventy-two (72) hours of the Request; HIPS samples no content from a Workspace whose policy is training off;
  5. (e)the content of a Request that the safeguards of Acceptable Use Policy Section 11.10 flag, only where the law requires HIPS to preserve or report it, and only as long as that law requires; otherwise HIPS keeps only the record that the Request was refused or its output withheld, with the category and the time, and no content;
  6. (f)content a Customer asks HIPS in writing to hold for debugging, naming the API key and the period, held for that time-boxed period and audited;
  7. (g)content HIPS must keep under the law or the order of a competent authority; and
  8. (h)a prompt cache: the state that an engine computed from a Request's prompt, kept only in the memory of the data-center worker that served it, never on its disk, for the Workspace that sent it, readable never longer than Section 6.12(e) allows, and cleared from that memory within the further period it states.

The Prefix Ledger, which keeps pseudonymized hashes of blocks of prompts and not their text, is kept as Section 6.12(d) states.

7.2

Customer Models and hub tokens. A Customer Model's stored copy is kept until the Customer deletes the model or its version, and is then deleted within seven (7) days; stopping a deployment does not delete it. While a security incident or a rights holder's notice that concerns a deleted version is open, HIPS keeps that version's copy for that purpose only, tells the Customer, and deletes it when the matter ends. A hub access token is deleted when the Customer deletes it, and at once when the Workspace is deleted; encrypted backups of the database that still hold it expire within the backup period and are never restored into service. HIPS cannot revoke a token at its hub, so the Customer should also revoke it there. When a Workspace is purged after its restore period, the stored copies of its Customer Models are deleted within the same period.

7.3

Usage Data. Usage Data is kept for thirteen (13) months from the Request, and is 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. Usage records that support billing, Settlement or a tax record are financial records under Section 7.7. The record of the Provider and the Device that ran each Request and each line of a Batch is kept for thirteen (13) months, so that HIPS can answer a Buyer as Section 9.3 states.

7.4

Early-access registrations and inquiries. HIPS keeps early-access registrations as the table below states. An inquiry is a communication, which Section 7.10 governs.

TableRetention of early-access data
DataKeptThen
A registration whose email address is never confirmedThirty (30) days from submissionDeleted
A confirmed registration and its answersUntil you withdraw, or until ninety (90) days after HIPS announces on the Website that the early-access program has ended, whichever is earlierDeleted, or reduced to counts; a registration that leads to an Account keeps only the link to the Account and the timestamps
A withdrawn registrationThe email address, the state and the timestamps only, so that the consent record and re-registration workDeleted three (3) years after the withdrawal
Consent records (timestamps, source and notice version)While the registration exists, and after withdrawal for three (3) years, so that HIPS can establish, exercise or defend a legal claim about the consentDeleted
Suppression records (addresses HIPS must not email)As long as the suppression must be honoredReviewed on a schedule
Email delivery eventsNinety (90) daysDeleted; only counts remain
The hashed IP address and the user agent at submission and confirmationUntil confirmation and the anti-abuse window of thirty (30) days that followsDeleted
7.5

Accounts and Workspaces. An Account is kept while it is open. When you delete your Account, your sessions and authorized devices are revoked, your memberships and any provider account are closed, and any Affiliate Program Agreement of yours ends. Your email address is replaced by a hash once nothing remains for HIPS to settle, pay or report to you (Section 11.5) and, if you are a Consumer and a Workspace deleted with your Account held unused Purchased Credits, once the period in which you may ask for their refund under Terms of Service Section 27.12 has ended (Section 11.5(e)), and a minimal record is kept for seven (7) years from the end of the financial year in which the Account was deleted, the period of Section 7.7, or, where the record is evidence of your location for a supply that HIPS declared under the One Stop Shop scheme, ten (10) years from the end of the year of the last such supply (Article 369k of Council Directive 2006/112/EC), with the reference, status and time of your identity verification, and your Country, kept as a financial and legal record, and, for the period of Section 7.6 (after a closure for cause, the period of Section 7.9) and as Section 3.7 states, HIPS's identifiers of you as a natural person, which are not derived from your face, and whether you received the Free Allowance or a Referral Discount, kept only to keep one verified identity per person, so that a later Account of yours receives no second Free Allowance or Referral Discount, and, while an amount remains owed to you, to confirm who may change where HIPS pays it (Section 11.5(d)); your Earnings and settlement records, Affiliate Program data, Payout data and Tax Information are kept under Sections 7.7 and 7.10. A Workspace of which you are still the only active owner when your Account is deleted is deleted with it, except that a Workspace held by a Business User other than you yourself is not deleted with your Account: HIPS makes the Member whom the Business User named beforehand as its successor owner its owner or, where it named none, keeps the Workspace running without an owner for thirty (30) days, with its Credits and data, its API keys, deployments and open Batches still running and its admins keeping their roles, so that the Business User can name its owner; this is not a measure against the Workspace, and only what an owner alone may do is unavailable in that time; HIPS chooses no owner itself and deletes the Workspace only if the Business User names none in that time. A Workspace you hold yourself as a sole proprietor is deleted with your Account unless you first make another Member its owner (Terms of Service Section 4.7(a); DPA Section 12.4; Section 11.5). When an owner deletes a Workspace, it can be restored for thirty (30) days and is then purged; its usage, ledger, receipts and audit records are kept under Sections 7.3, 7.7 and 7.11.

7.6

Identity verification records. Identity verification records are kept while the Account exists, and after it is closed for three (3) years, so that HIPS can establish, exercise or defend a legal claim arising from the contract with it, except that the record of the consent to the face check of a person to whom HIPS gave the notices of a state of the United States is kept until five (5) years after the check, if that is later, the period in which a claim under the Illinois Biometric Information Privacy Act can be brought; this is subject to Section 3.7 for HIPS's identifiers of a natural person, which Section 7.9 governs after a closure for cause, and to Section 3.1 for the documents sent for the check of other evidence by a person of Section 11.5. Because HIPS does not verify identity under anti-money-laundering law (Section 4.1), that period rests on HIPS's legitimate interests in preventing fraud and the abuse of benefits it grants once per person, including keeping one verified identity per person (Section 7.5), in demonstrating the consent it relied on (Article 7(1) of the GDPR), and in establishing, exercising or defending legal claims (Article 17(3)(e) of the GDPR). Bynn keeps the images of your identity document, the face captures and the screening results for thirty (30) days after the decision on your verification, or, where you have asked for a review of that decision or HIPS needs them to establish, exercise or defend a legal claim, until that review or claim is resolved, and then deletes them, destroying face captures and any biometric data under the policy of Section 3.7(c); it destroys face captures and biometric data sooner when you withdraw your consent to the automated face check (Section 3.7(a)), unless the law requires it to keep them. Your consent to the face check, the version of the consent text shown to you, its time and any withdrawal are kept with the identity verification records and for as long as they are; that record does not show which method of the face check you used, and of the face check by a person only the outcome of the verification is kept, as Section 3.7(d) states.

7.7

Financial and tax records. Billing records, receipts and invoices, the ledger, VAT records (including the validation of VAT numbers and the evidence of a Buyer's location), the records of machine payments and of their acceptance, Earnings and settlement records, self-billed statements, payout records, Tax Information and the returns and reports HIPS files are kept for seven (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 for which Irish VAT law requires HIPS to keep its records (section 84 of the Value-Added Tax Consolidation Act 2010), except that: the records of supplies that HIPS declares under the Union One Stop Shop scheme, the evidence of each Consumer's location included, are kept for ten (10) years from the end of the year of the supply (Article 369k of Council Directive 2006/112/EC); the records of the due diligence and reporting that DAC7 requires, where it applies, are kept for six (6) years from the end of the year in which HIPS applied the procedures or relied on the information, or longer where they form part of a record that this Section keeps longer; the records of Form 46G are kept as Irish tax law requires; and United States tax forms and information returns are kept for four (4) years from the due date of the last return to which they relate, or longer where they support a record that this Section keeps longer. Records that a tax audit, an assessment or a dispute needs are kept until it ends (Section 7.12).

7.8

Provider and Device data. Device telemetry is kept for ninety (90) days, after which it is deleted or reduced to counts that identify no Device. The round trips between a Device and HIPS's regional processing locations, the record of the location to which it was connected, and the session records of its connections, with the keyed hashes of their network addresses, are kept for ninety (90) days; the country and the regional processing location recorded for each attempt are kept with the record of Section 7.3. The hardware inventory and the hardware identifiers of a Device (Section 3.9) are kept while the Device is enrolled and, after it is removed, for twelve (12) months, so that HIPS can recognize the machine and the GPU if they are enrolled again. An entry of the hardware blocklist is kept until a person at HIPS removes it after a review (Section 3.9), and for no longer than three (3) years after it was made, unless a person at HIPS renews it after a review on a new finding (Section 3.9). The records of attempts and verification results on which Earnings were settled, held, adjusted or forfeited are kept with the Earnings and settlement records for the period of Section 7.7, which covers the six (6) years within which a claim founded on a contract, such as a claim about Earnings, can generally be brought under section 11(1)(a) of the Statute of Limitations 1957 of Ireland, and, where a dispute about them has been brought, until it is resolved.

7.9

Trust and safety records. Trust and safety records are kept for three (3) years after the last event they record: the measure, its review, or the end of the Account, Workspace, provider account or participation in the Affiliate Program concerned. A finding of fraud, with the forfeiture and Fraud Costs that followed it, is kept for ten (10) years from the end of the calendar year in which HIPS notified the finding, because the limitation period of a claim based on fraud begins to run only when the fraud is discovered (section 71 of the Statute of Limitations 1957 of Ireland); HIPS keeps for that period only the finding, its basis, the amounts concerned and any review, and the evidence for the periods of the rows that govern it. Where HIPS closes an Account, a Workspace, a provider account or a participation in the Affiliate Program for fraud, abuse or sanctions, it keeps the verification reference and HIPS's identifiers of the person concerned (Section 3.7), whether or not that person's consent to the face check stands, for five (5) years after the closure, so that it can recognize a later Account of the same person and refuse it an invitation, a provider account or a participation in the Affiliate Program.

7.10

Website data, Affiliate Program data and communications. Web server records are kept for thirty (30) days. Affiliate Program data is kept as follows: a Program Partner's record, codes and payout account while the Account exists, and afterwards for the period the payout records it supports must be kept (Section 7.7); a referral for as long as a commission refers to it, except that once the Account, Workspace or provider account of the Referred Person is purged, the referral no longer identifies that person, and the hash of the IP address recorded with a referral is erased ninety (90) days after the referral qualifies, is rejected or ends without qualifying; the hash of an IP address used to count a click, for one day; daily click counts, which name no person, for twenty-four (24) months from the day counted, and afterwards only as monthly totals for each campaign that name no code; a referral stored with an early-access registration, as long as that registration's answers (Section 7.4); and copies of Partner Content, with the placement, targeting and traffic-source information a Program Partner gave, for three (3) years after the Program Partner last used the Partner Content, so that HIPS can establish, exercise or defend a legal claim about it, and, where a claim about it has been made, until the claim is resolved. Commissions, payouts and the Tax Information of Program Partners are financial and tax records under Section 7.7. Communications, inquiries and support bundles included, are kept for three (3) years after the matter they concern is closed, unless they form part of a record that this Section 7 keeps longer; a notice you give under the Terms of Service, the Provider Agreement, the Affiliate Program Agreement or the Common Clauses, such as a Notice of Dispute or an arbitration opt-out, is kept for the term of the agreement concerned and seven (7) years after it ends.

7.11

Other records. HIPS keeps the other records below for the periods the table states.

TableRetention of other records
DataKept
Payout profile and payout methodWhile your provider account or your Affiliate Program record is open; afterwards as part of the payout records under Section 7.7, for seven (7) years from the end of the financial year of the last payout they concern
Your declarations of status and of your Country, the business details you give, the evidence of residence HIPS checked, the position of a Consumer's training switch or a Consumer's consent to training in the United States, and their changes, and a Consumer's consent under Section 6.8 and agreement to receive information and documents in English (Section 7.6 governs your consent to the face check)While the Account exists; afterwards, where they are evidence of the place of a supply HIPS declared under the One Stop Shop scheme, ten (10) years from the end of the year of the last such supply (Article 369k of Council Directive 2006/112/EC), and otherwise seven (7) years from the end of the financial year in which the Account was deleted (Section 7.7)
Audit records of actions taken with an Account or in a Workspace, and records of terms accepted and of the clauses you confirmed separatelyRecords of terms accepted and of the clauses you confirmed separately: for the term of the agreement and seven (7) years after it ends. Audit records: three (3) years from the action they record, and longer where a record under Section 7.7 refers to them
License attestation records of Customer ModelsWhile the Customer Model exists, and afterwards for three (3) years, and while a rights holder's notice about the model is open
The hardware id of each Device and the keyed hashes of its GPUs' identifiers (Section 3.1); the hardware inventory, the hardware identifiers and the hardware blocklist are kept as Section 7.8 statesWhile the Device is enrolled and twelve (12) months after it is removed
Crash reports from the Provider App (Section 3.10)Ninety (90) days from receipt, and no longer than the retention HIPS sets for its Rollbar project, which is the same ninety (90) days; daily counts that name no Device or provider are kept as aggregate data
7.12

Enforcement. HIPS enforces these periods with scheduled deletion. When a period ends, the data is deleted or reduced to counts that contain no Personal Data, unless the law requires HIPS to keep it longer or it is needed to establish, exercise or defend a legal claim, in court or in arbitration, in which case HIPS keeps only what that claim needs and only until it is resolved.

Section 07
  1. 7.1Request Content
  2. 7.2Customer Models and hub tokens
  3. 7.3Usage Data
  4. 7.4Early-access registrations and inquiries
  5. 7.5Accounts and Workspaces
  6. 7.6Identity verification records
  7. 7.7Financial and tax records
  8. 7.8Provider and Device data
  9. 7.9Trust and safety records
  10. 7.10Website data, Affiliate Program data and communications
  11. 7.11Other records
  12. 7.12Enforcement
Copy link

08Security

HIPS protects Personal Data with technical and organizational measures appropriate to the risk. Every connection is encrypted in transit, and the data HIPS stores in its own databases, caches, object storage and backups is encrypted at rest; a copy of a Customer Model on the disk of an Approved Provider's worker is protected at rest as that Approved Provider's published conditions on the Legal Information Page state (Section 9.2); as HIPS states publicly, encryption "protects data during transfer and storage, but does not by itself prevent a GPU operator from accessing weights or request data during execution" (Section 9.2). Staff work with restricted permissions and troubleshoot from metadata first. Apart from the automated processing that answers Requests, returns asynchronous results and prepares training copies, a person at HIPS may access Request Content only for a defined purpose (abuse review, a Customer's written debugging request, a security incident, a legal obligation, or a check under Section 11.6 of a text a person gives HIPS against the Prefix Ledger), with the approval of a second administrator and a record of the access. The comparison of a verification sample runs automatically, without human access. Apart from the automated import checks and profiling, nobody at HIPS opens a Customer Model's weights except for a legal obligation, at the Customer's written request, or for a security incident or an abuse case that concerns the model, with the same approval and record. Hub access tokens are encrypted, shown only by their last four characters, never returned after creation, never logged, and never sent to a worker or a Device. Session tokens are stored as hashes; a Device's key never leaves the Device's own keystore; card data stays with Stripe, and the bank account details of a payout account or a Global Payouts recipient record stay with Stripe, apart from what Section 3.3 lists. A Customer Model runs as weight files only, executed by HIPS's own engines; no customer code runs. Batch Files are stored encrypted and deleted on the schedule of Section 7.1(c). Prompt caches on data-center workers are kept apart for each Workspace, made unreadable within the period of Section 6.12(e) and cleared from memory within the further period it states, personal Devices keep no cache between Requests at launch, and a worker that reports a cache hit the Prefix Ledger cannot support is investigated as an incident and handled as a breach affecting Personal Data until HIPS establishes that no Personal Data of one Workspace reached another (Section 6.12). Error reports and crash reports carry no Request Content (Section 3.10). Buyers and Devices never connect to each other directly, and HIPS's regional processing locations hold Request Content only in memory (Section 10.1). No method of transmission or storage is completely secure, and HIPS cannot guarantee absolute security. HIPS handles a breach affecting Personal Data under the GDPR's notification duties, notifying the Data Protection Commission of Ireland, its lead supervisory authority, and the people affected where the law requires, and the authority of another country where its law requires it (Section 14), and notifies Customers that are Business Users of a breach affecting their Request Content as the DPA provides.

Section 08
Copy link

09Recipients and Sub-processors

9.1

Sub-processors and service providers. HIPS uses the following Sub-processors and service providers, each under a written agreement or its own terms as Section 2.6 describes:

TableSub-processors and service providers
RecipientWhat it does for HIPSPersonal Data involvedLocation
Hyperscale Inference Processing Systems OÜ (Estonia), the Operating CompanyOperates the Service for HIPS (Section 2.7)All Personal Data of the ServiceEstonia, for its operations and administration, with the data stored and processed where this table and Section 10 state
Amazon Web ServicesHosting, database, storage, encryption keys and secrets; email delivery (Amazon SES); HIPS's regional processing locations; the content delivery network in front of the Website and the Console, in front of ai.hips.com, where the encrypted connection of each Request ends at the edge location nearest the client, and in front of the downloads of catalog models and engines to Devices (Amazon CloudFront)All categories HIPS stores; Request Content in memory at each regional processing location, and the short-lived stores of Section 10.1; Request Content in transit and in memory at the CloudFront edge location that receives a Request to ai.hips.com; the traffic of the Website and the Console in transit; and the network address of a Device that downloads a catalog model or an engineIreland (AWS region eu-west-1), for everything HIPS stores and the regional processing location there; the United States (us-east-2, Ohio) and Japan (ap-northeast-1, Tokyo), for HIPS's regional processing locations there (Section 10.1); and Amazon CloudFront's points of presence, which may be in any country where CloudFront operates: the one nearest the visitor ends the encrypted connection to the Website, the Console and ai.hips.com, holds what passes through it in memory only, and HIPS cannot restrict these points of presence to the European Economic Area (Section 10.4(g))
Runpod Inc. (RunPod), and each Approved Provider HIPS adds laterGPU capacity of the Approved Pool, in RunPod's Secure Cloud only, never its Community CloudRequest Content, prompt caches and Customer Models while a Request, a line of a Batch or a deployment runsData centers of RunPod's Secure Cloud in the European Economic Area, the United States and Japan, listed by country on the Legal Information Page
ProvidersGPU Time of the Personal PoolRequest Content of Requests to catalog models, lines of Batches included, while they run; no Customer Model runs on a Device at launchThe Device Countries where a Provider's Device is located, as HIPS takes it from each connection (Section 10.3): the European Economic Area, the countries for which an adequacy decision of the European Commission is in force, and the further countries HIPS has opened and lists on the Legal Information Page; each Provider's own Country is a Provider Country: the European Economic Area, the United Kingdom, Switzerland, Canada, the United States, Japan, Singapore, the Republic of Korea, Taiwan or Australia
BynnIdentity verification: identity document, the automated face check where you choose it, and sanctions screeningThe identity data you give Bynn, including the capture of your face where you choose the automated face check (Section 3.7); HIPS receives only the resultBynn Intelligence, Inc. (United States), which processes the data in the European Union under its agreement with HIPS; as a company of the United States, it is a recipient outside the European Economic Area (Section 10)
StripeCard payments, including machine payments by Shared Payment Token (Section 3.1), subscriptions, invoices, tax calculation and disputes; the promotion codes that apply the Referral Discount; payouts to Providers and Program Partners through Stripe Connect and Stripe Global Payouts (Section 3.3)Billing data, the references and card details Stripe returns for a machine payment, never the card number, Payout data, the recipient records of Stripe Global Payouts, the amounts and references of transfers and payouts, the Program Partner identifier carried by a promotion code, and the evidence HIPS gives in a payment disputeIreland (Stripe Payments Europe, Limited and Stripe Technology Europe, Limited, with which HIPS contracts), the United States (Stripe, LLC), and the other countries where Stripe and its affiliates process data to provide their services; Stripe, LLC is certified under the EU-U.S. Data Privacy Framework
Stripe, for tax reporting, once Stripe confirms this service for HIPS's accountCollecting Forms W-9, verifying taxpayer identification numbers with the Internal Revenue Service, preparing and filing Forms 1099 and delivering them to the recipientsTax Information of United States persons, Payout dataThe United States
RollbarError reports from the Service, and crash reports from the Provider App (Section 3.10)Error details, and crash reports without the identifier of a Device or provider account, a provider's name or Country, or an attempt identifier, which only HIPS can link to a provider; never Request ContentThe United States (Rollbar, Inc., San Francisco, which hosts on Google Cloud in the United States); kept by Rollbar for ninety (90) days, the period of Section 7.11, which HIPS sets in its Rollbar plan
GoogleSign in with Google, for users who choose itAccount DataThe United States (Google LLC, certified under the EU-U.S. Data Privacy Framework) and the other countries where Google processes data; you sign in at Google directly, and Google acts under its own terms
CloudflareHosting the explainer film on the WebsiteYour IP address when the film or its poster loadsThe point of presence of Cloudflare's network nearest you, which may be in any country where Cloudflare operates (Cloudflare, Inc., United States, certified under the EU-U.S. Data Privacy Framework)
The provider of a fraud-scoring service, acting for HIPSSign-up risk, fraud and provider-trust assessments (Section 5), under a processing agreement that meets Article 28 of the GDPR and forbids the provider to use the data for any purpose of its ownFor sign-up risk, the early-access registration data of Section 5.1; for fraud and abuse signals, Usage Data, Account Data, Billing data and trust and safety records, never Request Content; for provider trust, Provider and Device data and the results of verificationThe EEA or, outside it, under the safeguards of Section 10.4(e)
The provider of a video-call service, acting for HIPS under a processing agreement that meets Article 28 of the GDPR, with recording, transcription, facial processing and every capture offCarrying the live call of a face check by a person that a person at HIPS runs (Section 3.7(d))The image and voice of the person on the call, live, and the call's link and time; nothing kept after the callThe EEA or, outside it, under the safeguards of Section 10.4(e)

When a Customer imports a model, HIPS fetches the files from the model hub the Customer names (Hugging Face first), on the Customer's instruction and with the Customer's token where one is needed, and sends the hub no customer data beyond the request for files. A model hub acts for the Customer under the Customer's own terms with it, not for HIPS, and is not a Sub-processor. HIPS uses no third-party bot-check service on its forms; if it adds one, it is listed here.

9.2

Important: who can access Request Content while a Request runs

Who executes a Request. A Request runs either on the Personal Pool, the idle GPUs of Providers, or on the Approved Pool, data-center capacity of Approved Providers. In both pools, whoever controls the hardware can in principle access the model and the Request Content while the Request runs. HIPS makes no confidential-computing claim for either pool.

In the Personal Pool, the Device operator can in principle access the model and Request Content during execution: 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 reading it, but the owner has physical control of the Device, and the verification of results detects dishonest outputs, not silent copying. In the Approved Pool, the data-center operator administers the host and could access GPU memory, the container's filesystem and the storage holding the weights. HIPS makes no confidential-computing claim for either pool, and "will publish the execution protections and access conditions for each pool before customers deploy workloads to it." They are on the Legal Information Page. Customer Models run only in the Approved Pool at launch. The lines of a Batch run in either pool on the same terms as live Requests, under the Workspace's requirements. Fallback from one pool to the other is off by default, requires explicit enablement, and never overrides region or data-use rules.

9.3

Buyers and Providers do not see each other. Buyers and Devices never connect to each other directly: every Request reaches a Device through HIPS's regional processing locations, and its result returns the same way, so no Buyer learns the network address of a Device and no Provider learns a Buyer's. A Provider sees the model and, while a job runs, the content in its Device's memory, but HIPS never discloses to it a Buyer's identity, a Workspace's name, an API key, a Buyer's price, or which jobs are verification samples. HIPS does not tell a Buyer which Provider served a Request, except as this Section states, and never tells a Program Partner whom it referred, except where the law requires HIPS to disclose it; it shows a Program Partner only the totals and reason categories of Section 3.8(c). To meet Article 28 of the GDPR, under which a Buyer that is the Controller of Personal Data in its Requests must be able to know who processes it (DPA Sections 7.3 and 7.5; Provider Agreement Section 8.15; Common Clauses Section 3.8):

  1. (a)HIPS shows each Buyer whose Workspace allows the Personal Pool a list of the Providers that may receive its Requests, each by a stable pseudonymous identifier and its Country, which does not identify the Provider, and may tell that Buyer when a Provider is added to it;
  2. (b)HIPS keeps a record of the Provider and the Device that ran each Request and each line of a Batch, for the period Section 7.3 states, and shows the owner and admins of a Workspace of a Buyer that is a Business User and the Controller, at any time in the Console and under a duty of confidentiality, the name, Country and contact address of every Provider on the Workspace's list and of every Provider whose Device processed that Buyer's Personal Data, with the period in which it did; on a written request it gives the same within five (5) business days. The contact address is the email address of the Provider's Account, unless the Provider gives HIPS another one for this purpose;
  3. (c)HIPS gives the same information to a supervisory authority that asks for it; and
  4. (d)Approved Providers are named in Section 9.1 and in the DPA.

If you are a Provider, this is how a Buyer that is a Business User may learn your name, Country and contact address, and, apart from a disclosure the law requires, the only way. Provider Agreement Section 6.11 governs any contact that follows.

9.4

Tax authorities. HIPS discloses Personal Data to tax authorities where tax law requires it, each acting as an independent Controller:

  1. (a)the Revenue Commissioners of Ireland: HIPS's VAT and One Stop Shop returns and the records VAT law requires it to keep; Form 46G for payments to Providers and Program Partners resident in Ireland; and, if DAC7 applies to GPU Time, the reports Section 3.2 describes, which the Revenue Commissioners may transmit to the tax authority of the Member State where you are resident;
  2. (b)the United States Internal Revenue Service: Form 1099-NEC for payments to Providers and Program Partners who are United States persons, where United States tax law requires it; and
  3. (c)any other tax authority, where a law that applies to HIPS requires it, including in an audit or an inquiry.
9.5

Other recipients. HIPS may also disclose Personal Data:

  1. (a)to the owner and admins of a Workspace you belong to, who may see your membership, role and actions in that Workspace;
  2. (b)to HIPS's professional advisers, such as lawyers, auditors, accountants and tax advisers, under a duty of confidentiality;
  3. (c)to Stripe, for the card issuer, as evidence to answer a payment dispute about a purchase from HIPS;
  4. (d)to a collection agency or lawyer HIPS engages to recover an amount owed to it, limited to what the recovery needs;
  5. (e)to courts, arbitral institutions and arbitrators, regulators, law enforcement or other authorities, where the law requires it, where needed to establish, exercise or defend a legal claim, or where necessary to protect the rights, property or safety of HIPS, its Buyers, its Providers or others;
  6. (f)to a successor or acquirer in a merger, acquisition, financing or sale of all or part of HIPS's business, subject to this Notice;
  7. (g)with your consent; and
  8. (h)to an authority that an unclaimed or abandoned property law designates, where that law requires HIPS to deliver to it an amount HIPS owes you, with the information that law requires, such as your name, your last known address and the amount (Section 11.5).
9.6

No crypto-asset payments or payouts. HIPS accepts no payment and makes no payout in MTO, USDC or any other crypto-asset, connects no wallet, and no crypto-asset service provider receives Personal Data from HIPS. Payouts go to a bank account in your own name through Stripe Connect or Stripe Global Payouts (Section 3.3). If HIPS later offers a crypto-asset payment or payout, it first updates this Notice to name the crypto-asset service provider and the data it receives. Common Clauses Section 3.12 applies to any decision you make about a crypto-asset.

9.7

Changes to the list. The current list of Sub-processors is published in this Notice, in the DPA and on the Legal Information Page. HIPS notifies the owner and admins of each Workspace of a Business User of a change to the list, as DPA Section 7.5 provides, at least thirty (30) days before the change, and updates this Notice for everyone else. DPA Sections 7 and 8 authorize Providers in the Personal Pool as a category of Sub-processor, list the countries in which they may be located (Section 10.3), and let a Customer that is a Business User object to them by excluding the Personal Pool, through the pool requirement of its Workspace, API keys and Requests (DPA Section 7.4).

9.8

Training copies go to no one else. 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 the 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, for every Buyer, in the way DPA Section 5.3 provides for a request of a public authority: it discloses only what the law or the order compels and tells the Buyer of the request unless the law prohibits it, and except to a successor that takes over the Service under Section 9.5(f) and is bound by this commitment; a service provider that processes them only on HIPS's behalf and under its instructions is not a third party for this purpose. Apart from an authority or a successor in the cases this Section states, their only recipients are such service providers, acting as HIPS's processors: the Operating Company and the Sub-processors of Section 9.1 that store and process training copies and datasets for HIPS, which store and process them only in the European Economic Area, with Amazon Web Services in Ireland (eu-west-1) and on data-center capacity of Approved Providers located in the EEA, HIPS never running training on a Device of the Personal Pool; and the Approved Providers that run a model trained on them, as they run every model HIPS offers through the Service (Section 9.2); none of them may use them for itself. A model that HIPS trains on Request Content 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 the GDPR is in force, and never on a Device of the Personal Pool; HIPS treats every such model as containing Personal Data, and offers it 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 the GDPR is in force and covers that Buyer (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) (Section 10.5). Buyers who send Requests to a model that HIPS trained on Request Content receive its outputs. An output may in some cases reproduce Personal Data from the Request Content the model was trained on, and the Buyer who receives it is then a recipient of that Personal Data; HIPS assesses and answers reports of such outputs from anyone, as Section 6.10(h) describes, and acts on them as Section 6.6 provides. Before HIPS offers such a model, it tests it for the reproduction of Personal Data from its training copies; it masks identifiers before training and removes duplicates to reduce memorization; and it applies output filters that keep the model from outputting the Personal Data of a person who has objected or reported an output. If HIPS ever decides to use them for a wider purpose or to disclose any of them to another recipient, it first amends this Notice to state that purpose or name that recipient, with its own balancing test, and applies the change only to Request Content HIPS accepts after the amendment. HIPS has no such purpose or recipient.

Section 09
  1. 9.1Sub-processors and service providers
  2. 9.2Who executes a Request
  3. 9.3Buyers and Providers do not see each other
  4. 9.4Tax authorities
  5. 9.5Other recipients
  6. 9.6No crypto-asset payments or payouts
  7. 9.7Changes to the list
  8. 9.8Training copies go to no one else
Copy link

10International transfers

10.1

Where HIPS keeps and processes Personal Data. HIPS hosts its databases, storage, email delivery and backups with Amazon Web Services in Ireland (eu-west-1), and keeps its backups in that region: your Account, your Workspaces and their settings, billing, payout and tax records, identity verification records, Usage Data and the other records HIPS keeps about you are kept there, whichever region serves your Requests. HIPS processes Requests in its regional processing locations in Ireland (eu-west-1), the United States (us-east-2, Ohio) and Japan (ap-northeast-1, Tokyo), each run with Amazon Web Services, and on the data-center capacity and Devices reached from them. Each regional processing location:

  1. (a)holds Request Content only in memory, while it routes a Request, forwards it where Section 10.2 allows and relays its result;
  2. (b)holds the copies of account data it needs to serve Requests without waiting for Ireland, such as hashes of API keys with their Workspaces, the policies of Workspaces and the Credits it may spend for them; and
  3. (c)keeps, in its own region, short-lived operational stores, none of which holds Request Content: the queue of records it has not yet delivered to Ireland (usage records, which hold your network address only as a keyed hash, and the records of jobs, attempts, Devices' sessions and telemetry summaries, and crash reports), each deleted once Ireland has received it and in any case no later than fourteen (14) days after it was written; its operational store, which holds the current records and telemetry of the Devices connected to it, rate limits, the Credits it may spend for each Workspace, the records of uploads and the Prefix Ledger of the workers it serves, each only while it is current and the Prefix Ledger for no longer than Section 6.12 states; and its operational logs, which carry no Request Content and stay on its servers only until they are delivered to HIPS's systems in Ireland, and in any case no longer than fourteen (14) days.

Usage records, the records and telemetry of Devices, and crash reports flow from each regional processing location to HIPS's systems in Ireland. Content stored for a Request that requires a region, such as an upload or the files of a Batch, rests in that region (Section 10.2(b)); other stored content rests in Ireland.

10.2

Regions and where Requests run. HIPS's regions are "eu", the European Economic Area (the 27 member states of the European Union, Iceland, Liechtenstein and Norway); "us", the United States (its fifty states and the District of Columbia); and "jp", Japan.

  1. (a)Without a region requirement. A Request sent to ai.hips.com passes through the edge of point (c) and reaches the nearest regional processing location. It may run there or, where that location has no eligible capacity, be forwarded to another region's location and run there, on any eligible capacity: RunPod's data centers in the European Economic Area, the United States and Japan, listed on the Legal Information Page, or the Devices of Providers located in a Device Country, whose country HIPS takes as Section 10.3 describes. The same applies to a line of a Batch.
  2. (b)With a region requirement. Region selection is available only on the higher paid plan, for each region once HIPS enforces it there. A region requirement keeps in its region the processing of a Request, every retry and fallback and any verification of it, its prompt caches and the content stored for it with its backups. It never covers account data, billing and usage records, which HIPS keeps in Ireland (Section 10.1); the operational logs, metrics and error and crash reports, which carry no Request Content; access by HIPS personnel, which takes place from the European Union (Section 8); or, on ai.hips.com, the decryption at the point of presence and at the regional processing location a Request first enters (point (c)). Where a Workspace requires a region, no Request silently crosses it: if the region has no eligible capacity, the Request fails rather than running elsewhere.
  3. (c)The regional addresses. On ai.hips.com, encryption first ends at the point of presence of Amazon CloudFront nearest to you (Section 1.7(c)), which may be in any country where CloudFront operates; it holds the Request in memory only, caches no response and passes it to a regional processing location over an encrypted connection; HIPS treats that as a transfer to the country of the point of presence, with the safeguards of Section 10.4(g). On eu.ai.hips.com, us.ai.hips.com and jp.ai.hips.com, which pass through no point of presence, the connection reaches only the regional processing location of that region and encryption ends only inside it, and a Request there that requires another region is refused. A Request that requires a region and is sent to ai.hips.com may first reach a regional processing location outside that region; that location decrypts it in memory only, stores nothing of its content, forwards it to its region, where it is processed, and relays the result. That decryption is processing of the Personal Data in the Request in the country of that location, which HIPS treats as a transfer to that country, with the safeguards of Section 10.4(a) and (b). A region requirement covers neither decryption. A Workspace that needs the connection itself kept inside its region should therefore use that region's address.
  4. (d)Devices. A Device connects to the regional processing location it measures as nearest, and HIPS may move it to another. A Request reaches a Device only through the regional processing location to which the Device is connected, never directly from a Buyer (Section 9.3).
10.3

Safeguards for Request Content processed on Devices. HIPS accepts Providers whose Country is in the European Economic Area, the United Kingdom, Switzerland, Canada, the United States, Japan, Singapore, the Republic of Korea, Taiwan or Australia, each from the date the Console lists that country as open (Provider Agreement Section 3.3). A Provider's Devices may be located in any country other than a restricted jurisdiction, but a Device takes Requests of Buyers only while it is located in a Device Country: the European Economic Area, a country for which an adequacy decision of the European Commission is in force, or a country HIPS has opened after assessing, as Clause 14 of the Standard Contractual Clauses requires, the laws and practices of that country that bear on the processing of Request Content in a Device's memory, and documenting that assessment; at launch HIPS opens in this way the United States, Singapore, Taiwan and Australia, and the Legal Information Page lists every Device Country. Elsewhere a Device may enroll and take test work, which carries no Request Content of a Buyer. When a Device first connects from a country that is not yet a Device Country, HIPS assesses that country in the same way and opens it as a Device Country where the assessment allows, adding it to the Legal Information Page; until then, the Device takes only test work. A Device located in a restricted jurisdiction takes no work at all, and HIPS sends it no model, Provider App update or Request Content. HIPS takes the country of each Device from the network address of each of its connections, by looking the address up in a copy of MaxMind's GeoIP2 Country database that HIPS holds, so that no address is sent to MaxMind, and it keeps of the address only a keyed hash; it also checks that the address is on no known anonymizing network, and may compare with that country the round trips that its regional processing locations measure to the Device, never the Device's own report of them. A Device that connects through an anonymizing network, or whose country HIPS cannot derive or whose measurements contradict it, takes no Request of a Buyer until its location is confirmed (Provider Agreement Section 3.3); so that HIPS can confirm it, the Provider App may reach HIPS outside a virtual private network that the Device uses, where the Device's operating system allows it, and HIPS reads the country of that connection's network address as this Section describes. HIPS keeps these records with the Device's session records for the period of Section 7.8, on the basis of its legitimate interest in running Requests only where this Section allows them (Section 4.1). Where a Device outside the European Economic Area runs a Request, HIPS transfers Request Content to the Provider, and the safeguard follows the country where the Device is located, not the Provider's own Country:

TableTransfer safeguards for Providers
Where the Device isSafeguard
The European Economic AreaNo transfer outside the European Economic Area
The United Kingdom, SwitzerlandAn adequacy decision of the European Commission (for the United Kingdom, as renewed on 19 December 2025)
Canada, Japan, the Republic of KoreaThe Standard Contractual Clauses incorporated into the Provider Agreement, which bind every Provider there, together with the European Commission's adequacy decision for that country (Canada: commercial organizations subject to the Personal Information Protection and Electronic Documents Act; Japan: Implementing Decision (EU) 2019/419; the Republic of Korea: Implementing Decision (EU) 2022/254) where it covers the Provider
The United States, Singapore, Taiwan, AustraliaThe Standard Contractual Clauses incorporated into the Provider Agreement, after HIPS's assessment of the country under their Clause 14
Another country for which an adequacy decision of the European Commission is in forceThe Standard Contractual Clauses incorporated into the Provider Agreement, which bind every Provider there, together with that adequacy decision where it covers the Provider
Another country HIPS has opened as a Device CountryThe Standard Contractual Clauses incorporated into the Provider Agreement, after HIPS's assessment of that country under their Clause 14; no Request runs on a Device in a country HIPS has not opened
A Provider established in the European Economic Area, with a Device outside itThe GDPR, which binds the Provider, and Provider Agreement Section 8, which also binds it to the duties of Clauses 14 and 15 of the Standard Contractual Clauses for the country where the Device is located
10.4

The regional processing locations, and other transfers. HIPS relies on these safeguards:

  1. (a)The United States. HIPS's processing at its regional processing location in Ohio runs on the infrastructure of Amazon Web Services, so HIPS treats it as a transfer to Amazon Web Services in the United States. HIPS relies on the European Commission's adequacy decision for the United States, Implementing Decision (EU) 2023/1795, which covers organizations certified under the EU-U.S. Data Privacy Framework, under which Amazon Web Services, Inc. is certified, and also on the Standard Contractual Clauses of Amazon Web Services' data processing terms, which apply should that decision cease to cover the transfer.
  2. (b)Japan. For its regional processing location in Tokyo, run with Amazon Web Services, HIPS relies on the European Commission's adequacy decision for Japan, Implementing Decision (EU) 2019/419, which covers the Amazon Web Services company that processes the data in Japan as a business subject to the Act on the Protection of Personal Information, and on the safeguards of point (a) for any access to that data from the United States. RunPod's data center in Japan is covered by point (c).
  3. (c)RunPod's data centers. For the data centers of RunPod's Secure Cloud in the United States and Japan, HIPS relies on the Standard Contractual Clauses (Module Three where HIPS processes the data as a processor, Module Two where it is the controller) of its data processing agreement with Runpod Inc., which is not certified under the EU-U.S. Data Privacy Framework, with a transfer impact assessment that HIPS has documented; in Japan, also on the adequacy decision for Japan where it covers RunPod's processing there.
  4. (d)Forwarding between regions. A Request forwarded to another region's location is processed there with that region's safeguard, and the records each regional processing location sends to Ireland (Section 10.1) are HIPS's own records returning to its systems in the European Union.
  5. (e)Other Sub-processors. Rollbar, Inc. processes error reports and crash reports in the United States, under its certification under the EU-U.S. Data Privacy Framework and the Standard Contractual Clauses of its data processing agreement; Stripe processes payment and payout data in Ireland, the United States and the other countries Section 9.1 states, under Stripe, LLC's certification under that Framework and the Standard Contractual Clauses of Stripe's data transfer terms; Bynn Intelligence, Inc., a company of the United States, processes identity verification data in the European Union under its agreement with HIPS, with the Standard Contractual Clauses of its data processing agreement for any access from the United States; Cloudflare serves the explainer film from its network, under Cloudflare, Inc.'s certification under that Framework and the Standard Contractual Clauses of its data processing addendum; and each other Sub-processor of Section 9.1 is named or described there with its location. Where Personal Data goes to a country without an adequacy decision, HIPS relies on the Standard Contractual Clauses of Implementing Decision (EU) 2021/914 or, in the United States, on the recipient's certification under that Framework together with those clauses where its terms offer them.
  6. (f)Tax returns. Information returns are prepared and filed by Stripe in the United States once Stripe confirms this service for HIPS's account (Section 9.1), to which HIPS transfers the information on the basis of Stripe, LLC's certification under the EU-U.S. Data Privacy Framework and the Standard Contractual Clauses of Stripe's data transfer terms; the disclosure to the Internal Revenue Service rests on Article 49(1)(b) of the GDPR, since the information return is necessary for HIPS to pay a United States person under the Agreement with them.
  7. (g)The content delivery network. For the points of presence of Amazon CloudFront, HIPS relies, in the United States, on the adequacy decision for organizations certified under the EU-U.S. Data Privacy Framework, under which Amazon Web Services, Inc. is certified, and, in any other country without an adequacy decision, and in the United States should that decision cease to cover the transfer, on the Standard Contractual Clauses of Amazon Web Services' data processing terms.

Where the law of the country in which you are sets its own rules on transfers out of it, Section 14 states what HIPS does under them.

10.5

Outputs of models trained on Request Content. HIPS treats every model it trained on Request Content as containing Personal Data (Section 9.8), and offers it only to Buyers whose Country is in the European Economic Area or in a country, territory or sector for which an adequacy decision of the European Commission under Article 45 of the GDPR is in force and covers that Buyer (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), because an output of such a model may in some cases reproduce Personal Data; HIPS does not host or offer such a model anywhere else. Adequacy decisions of the European Commission are in force for Japan and the Republic of Korea, each for the recipients it covers, and none is in force for Singapore, Taiwan or Australia. HIPS may therefore offer such a model to a Buyer in Japan or the Republic of Korea whom the decision for that country covers, and only once the Buyer, a business, has confirmed in the Console that it is a personal information handling business operator subject to the Act on the Protection of Personal Information (Japan) or an entity subject to the Personal Information Protection Act (the Republic of Korea), and that it does not use the model for a purpose the decision for its country excludes; and never to a Buyer in Singapore, Taiwan or Australia.

10.6

Copies of the safeguards. A copy of the relevant safeguards is available on request at hello@hips.com.

Section 10
  1. 10.1Where HIPS keeps and processes Personal Data
  2. 10.2Regions and where Requests run
  3. 10.3Safeguards for Request Content processed on Devices
  4. 10.4The regional processing locations, and other transfers
  5. 10.5Outputs of models trained on Request Content
  6. 10.6Copies of the safeguards
Copy link

11Your rights

11.1

Your rights under the GDPR. You have the right to access your Personal Data; to have it rectified; to have it erased; to restrict its processing; to receive it in a portable format where that right applies; to object to processing based on legitimate interests, and at any time to direct marketing; to withdraw consent at any time, without affecting earlier processing; and not to be subject to a decision based solely on automated processing that produces legal or similarly significant effects for you, as Section 5 describes. These rights are the same whether you are a Consumer or a Business User, and whichever dispute track applies to you.

11.2

Important: your right to object

Your right to object. You may object at any time. Where HIPS processes your Personal Data on the basis of its legitimate interests (Section 4.1), you may object to that processing at any time, on grounds relating to your particular situation. HIPS then stops it, unless HIPS demonstrates compelling legitimate grounds that override your interests, rights and freedoms, or needs the data to establish, exercise or defend legal claims. Where HIPS uses Personal Data that concerns you in Request Content for training (Section 2.4), you may object at any time without giving a reason, and HIPS then excludes it from training as Section 6.6 describes. If you are a Consumer, you object for your own Request Content with the training switch in the Console, and keep your plan (Section 6.10). Where HIPS uses your Personal Data to send you HIPS news and product announcements, you may object at any time without giving a reason, and HIPS then stops using it for that purpose. To object, use the training switch, the prompt-cache setting of a Workspace (if you are its owner or admin; anyone else writes to the address below, as Section 11.6 describes) or, until it is available, a written request (Section 6.12), the unsubscribe link in any HIPS news email, or write to hello@hips.com.

11.3

How to exercise your rights. You may unsubscribe or withdraw from early access through the links in every relevant email, and manage or delete your Account in the Console. For any other request, write to hello@hips.com. Exercising your rights is free of charge, except that, where a request is manifestly unfounded or excessive, in particular because it repeats, HIPS may charge a reasonable fee for its administrative costs or decline to act on it, as Article 12(5) of the GDPR allows, and tells you why. Where HIPS has reasonable doubts about who is making a request, it may ask for the information needed to confirm it, such as a confirmation from the email address of your Account or registration, and no more. HIPS responds within one (1) month of receiving a request, which the GDPR allows HIPS to extend by two (2) further months where necessary, telling you why within the first month. If HIPS does not act on a request, it tells you why within one (1) month, together with your right to complain to a supervisory authority and to seek a judicial remedy.

11.4

Where a right is limited. Some rights do not apply in every case. HIPS keeps data that tax, accounting or sanctions law requires it to keep, or that it needs to establish, exercise or defend a legal claim, even after you ask for its erasure, and only for those purposes. Where giving you a copy of data would adversely affect the rights and freedoms of others, including another person's identity, the confidentiality of a Buyer toward a Provider or of a Provider toward a Buyer, or HIPS's trade secrets such as which jobs are verification samples and how its checks are weighed, HIPS withholds that part and tells you that it has. HIPS may also restrict your rights, and its own obligations to inform you, to the extent that section 60(3)(a) of the Irish Data Protection Act 2018 allows, where and for as long as that is necessary and proportionate: to prevent, detect or investigate fraud or another criminal offense against HIPS, its users or Providers, including by not telling you that a fraud review concerns you while telling you would prejudice it; and to establish, exercise or defend legal claims or to enforce civil claims, including HIPS's claims under the Provider Agreement and the Affiliate Program Agreement. HIPS tells you of a restriction and the reason for it, unless telling you would itself prejudice that purpose, and you may complain about it to a supervisory authority (Section 11.7). This does not restrict any right where the law of your country does not allow it. Where another law or the order of a competent authority forbids HIPS to tell you something, HIPS tells you as soon as it may. Where you, a supervisory authority or a court disputes HIPS's withholding of information as a trade secret or to protect others, HIPS gives the withheld information to that authority or court so that it can decide.

11.5

Deleting your Account. You may delete your Account at any time, in the Console or by writing to hello@hips.com. HIPS never refuses or delays the deletion because Earnings or commissions of yours are estimated, locked, pending, held or payable, or because you owe HIPS an amount. HIPS does not refuse or delay it because you are the only active owner of a Workspace either: before you confirm, the Console shows you each such Workspace and what its deletion means, 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, except that a Workspace held by a Business User other than you yourself is not deleted with your Account: HIPS makes the Member whom the Business User named beforehand as its successor owner its owner or, where it named none, keeps the Workspace running without an owner for thirty (30) days, with its Credits and data, its API keys, deployments and open Batches still running and its admins keeping their roles, so that the Business User can name its owner; this is not a measure against the Workspace, and only what an owner alone may do is unavailable in that time; HIPS chooses no owner itself and deletes the Workspace only if the Business User names none in that time. A Workspace you hold yourself as a sole proprietor is deleted with your Account unless you first make another Member its owner (Terms of Service Section 4.7(a)). When you delete your Account:

  1. (a)your provider account closes and the Provider Agreement ends; Earnings for work your Devices performed before then are settled and paid under the Provider Agreement's published conditions at the Settlements that follow, whatever their size and whether or not they reach the payout threshold, and holds, adjustments and forfeitures under the Provider Agreement continue only until they are complete (Provider Agreement Section 17.10);
  2. (b)your Affiliate Program Agreement ends; before you confirm the deletion, the Console shows you the totals of your commissions in each state and what Affiliate Program Agreement Sections 19.9 and 19.11 do with them; commissions that are payable then, or become payable afterwards, are paid as Affiliate Program Agreement Section 19.11 provides, and a commission is lost only where that Agreement provides that it lapses (Affiliate Program Agreement Sections 7.12 and 19.11), is reversed (Affiliate Program Agreement Sections 6.6 and 9) or is forfeited (Affiliate Program Agreement Section 12);
  3. (c)an amount you owe HIPS remains owed, and HIPS may recover it (Section 4.1);
  4. (d)HIPS keeps only what it needs to settle, pay, report and recover those amounts, such as your contact address, payout profile, payout method, Tax Information and HIPS's identifiers of you as a natural person (Section 3.7), until the last of them is paid or recovered, or the limitation period for claiming it has ended, whichever comes first, and afterwards only the records that a legal obligation requires HIPS to keep or that HIPS needs to establish, exercise or defend a legal claim, and the record that keeps one verified identity per person for the period of Section 7.6, or of Section 7.9 after a closure for cause, as Section 3.7 states (Sections 3.7, 7.5, 7.6, 7.7, 7.9 and 7.12); and
  5. (e)if you are a Consumer, before you confirm the deletion, the Console shows you the unused Purchased Credits of each Workspace that is deleted with your Account and lets you ask for their refund under Terms of Service Section 27.12 in the same step; if you do not, you may still ask within the period of that Section by writing from the email address of your Account, and HIPS keeps that address and the ledger records the refund needs until that period ends (Section 7.5).

After the deletion, HIPS uses your contact address to send you the statements and notices still due to you and, where a condition of payment is not met, such as a complete and current payout profile or Tax Information or a connected payout account, a link through which you may meet it without restoring your Account. Before an amount HIPS owes you can no longer be claimed, HIPS reminds you of it at least three (3) times, the last no later than ninety (90) days before the limitation period ends (Provider Agreement Section 17.8(f); Affiliate Program Agreement Section 19.9(g)). Where an unclaimed property law requires HIPS to deliver an amount it owes you to an authority, HIPS gives that authority the information that law requires, such as your name, your last known address and the amount (Section 9.5). HIPS sends that link only to the email address of your Account as it was when you deleted it. HIPS accepts another address for its notices, a change of the legal name in your payout profile, 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 identity verification again, a face check included (Section 3.7), with a match of the identifiers of a natural person that HIPS kept for you (Section 3.7); or, where HIPS kept none, the identifiers do not match, or the person declines a new face check, after a person at HIPS has checked other evidence that HIPS reasonably asks for, without any face check (Section 3.1 states what HIPS keeps of it); 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 identifiers change when an identity document is renewed or replaced, unless both documents carry the same personal identification number, so a mismatch alone is not a sign of takeover. Where the identifiers do 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 the Account as it was at the deletion, 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 it confirms with the register or authority that issued it; and after a deletion HIPS pays only in money, as Section 3.3 provides, to a payout account held in the name of the person or organization so confirmed. HIPS never refuses payment of an amount it owes only because a person declines a new face check or because the identifiers do 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. You may also close your provider account, or end your Affiliate Program Agreement, without deleting your Account. Section 7.5 describes what is kept after a deletion and why.

11.6

Requests about Request Content. Where your request concerns Personal Data that a Customer that is a Business User sent to the Service, HIPS forwards it to that Customer, which decides how to respond, and assists the Customer as the DPA provides. Because Request Content is not stored by default, HIPS may not hold the data concerned. This does not apply to Request Content of which HIPS is the Controller under Section 2.3, or to a training copy, of which HIPS is the Controller under Section 2.4. HIPS then handles your request itself, including an objection under Section 11.2, and tells you how it removes or excludes your Personal Data from retained training copies and from datasets not yet used. HIPS searches its retained training copies, and the datasets not yet used, for the identifiers you give it, such as a name or an email address, uses them only for that search and the exclusion, deletes them when it has finished, and tells you within the period of Section 11.3 what it found and what it did; because training copies are masked, HIPS may find nothing it can link to you. This does not apply either to the Prefix Ledger, of which HIPS is the Controller (Section 6.12(c)): HIPS handles a request or an objection about it itself, whoever sent the Request concerned. Because the Prefix Ledger holds only keyed hashes that HIPS cannot link to a person without the text, Article 11 of the GDPR applies; where you give HIPS the text concerned, HIPS checks for matching records, deletes them on your request or objection, and tells you whether it found any and what it did; every record is in any case deleted within the period of Section 6.12(d).

11.7

Complaints. You have the right to complain to a supervisory authority, in particular in the Member State of your habitual residence or place of work or of the place of the alleged infringement. HIPS's lead supervisory authority is the Data Protection Commission, 6 Pembroke Row, Dublin 2, D02 X963, Ireland, www.dataprotection.ie. Section 14 names the authorities outside the European Union. HIPS asks that you contact it first, so it can try to resolve your concern.

Section 11
  1. 11.1Your rights under the GDPR
  2. 11.2Your right to object
  3. 11.3How to exercise your rights
  4. 11.4Where a right is limited
  5. 11.5Deleting your Account
  6. 11.6Requests about Request Content
  7. 11.7Complaints
Copy link

12Children

The Website, the early-access forms and the Service are not directed at children, and the early-access forms collect no age data. Every Account holder, whether a Consumer or a Business User, must be at least eighteen (18) years old and have reached the age of majority and full legal capacity where they live, and passes identity verification before using the Service as a Buyer or a Provider; identity verification confirms, from the date of birth in the identity document, that the person is at least eighteen (18), and HIPS keeps only that result, never the date of birth. HIPS does not knowingly collect Personal Data from children as a Controller, and deletes it if it learns that it has. Where HIPS relies on consent for an information society service offered directly to a child, Irish law sets the age at which a child may consent at sixteen (16) (section 31 of the Data Protection Act 2018); the Service, which requires identity verification of every Account holder, is not offered to children. A Customer that is a Business User and sends Personal Data of children in Request Content is responsible, as Controller, for having a lawful basis to do so. HIPS asks Consumers not to include Personal Data of children in Request Content, and does not train on Request Content that its filters identify as concerning a child (Section 6.6). Contact hello@hips.com if you believe a child has given HIPS Personal Data.

Section 12
Copy link

13Cookies and similar technologies

13.1

Every cookie belongs to one host. The Website and the Console use only what they need to work. Every cookie the Service sets is a first-party cookie for one host only, set with no Domain attribute, so no other host receives it: a cookie set on hips.com never reaches console.hips.com, and the reverse. No cookie of the Service is ever set for the whole hips.com domain, so none reaches a host of HIPS Payments or any other host under hips.com (Section 1.7). www.hips.com answers every request with a permanent redirect to hips.com before any cookie is set, except a request for the script address of a service worker that an earlier website used, which it answers with a script that unregisters itself and a Clear-Site-Data header limited to storage and cache. The redirect keeps the link's parameters, and www.hips.com sets no cookie and asks for no choice of its own. Browsers may also send HIPS's hosts cookies that another host under hips.com set for the whole hips.com domain, or that an earlier website at hips.com or www.hips.com set. HIPS's edge removes from each request every cookie whose name does not carry the __Host- prefix or is not listed in 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 Website reads from your browser's storage only the entries this Notice lists, and never reads or uses storage, caches or service workers that an earlier website at hips.com or www.hips.com left in your browser. HIPS 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 the first response to a browser that does not yet hold the cookie hips_cleared (Section 13.3), which then records only that this was done; and www.hips.com, which sets no cookie, answers such a request as this Section states above, because a browser does not follow a redirect when it fetches the script of a service worker (the script addresses of service workers that the earlier website used, which HIPS compiled from that website before hips.com began to serve the Website). HIPS stops sending that header and setting hips_cleared twelve (12) months after hips.com began to serve the Website, on the date that the Legal Information Page states, and keeps answering the script address of an earlier service worker with the script that unregisters itself. Until an earlier service worker is unregistered, it may still handle requests in your browser; HIPS does not control or use it, and receives from it nothing but the requests it passes on to HIPS's hosts. The API hosts ai.hips.com, eu.ai.hips.com, us.ai.hips.com and jp.ai.hips.com, and providers.hips.com and the hosts under it, set no cookies: API callers and tools authenticate with API keys and access tokens, and Devices with their certificates.

13.2

Your choice, asked once on each host. A cookie banner on hips.com and on console.hips.com asks for your choice the first time you visit that host, with Reject all as easy as Accept all. Because your choice is itself kept in a cookie of that host, you answer once on hips.com and once on console.hips.com, and each answer governs only the cookies of its host. Cookie preferences in the Website's footer, and in the Console's account menu, reopens the choice at any time; withdrawing is as easy as answering. At the date of this Notice every cookie HIPS sets is strictly necessary, and the referral cookie of Section 13.4 is set only once the Affiliate Program opens, so no optional category is offered. When the Affiliate Program opens, HIPS adds the referral cookie to the banner as an optional category, off until you switch it on, and asks you again on each host. The referral cookie is not strictly necessary for the Website or the Console, so HIPS sets it, and uses a referral code that arrives in a link, only with your consent.

13.3

The cookies HIPS sets. The table lists every cookie of the Service. Every cookie HIPS sets carries the __Host- prefix (for example __Host-hips_session), 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 that HIPS's edge lets through; the table gives each name without that prefix. The Console cookies and hips_ref are HttpOnly, Secure and SameSite=Lax, so no script on the page can read them; the consent record is read by the banner itself.

TableCookies, by host
HostCookieWhat it doesHow long it lasts
hips.com and console.hips.com, each its ownThe consent record, hips_consentKeeps your choice per category, the banner's version and the time; holds no identifier of you; is also kept in your browser's storage; is set when you answer the banner, on any page, the early-access pages included, and is never sent to HIPS's platformSix (6) months from your answer; the banner then asks again
hips.comhips_clearedRecords only that HIPS has removed the storage, caches and service workers an earlier website at hips.com left in your browser (Section 13.1); holds no identifier of you; strictly necessary for the security of the Website you asked for, because a service worker left by an earlier website can intercept and answer your requests to hips.comUntil the date in Section 13.1 on which HIPS stops setting it, and no longer than thirteen (13) months
console.hips.comhips_sessionKeeps you signed inUntil your session expires or you sign out
console.hips.comhips_workspaceRemembers the Workspace you are working inUntil you sign out
console.hips.comhips_oauthProtects a Google sign-in while it completesUntil that sign-in ends, and no longer than ten (10) minutes
console.hips.comhips_inviteKeeps a Workspace invitation through sign-inUntil you accept the invitation
hips.com, once the Affiliate Program opens and only with your choice on that hosthips_refRemembers the Program Partner's referral link you opened (Section 13.4)The Attribution Window that Affiliate Program Agreement Section 24 states, counted from when the referral was first seen on hips.com
console.hips.com, once the Affiliate Program opens and only with your choice on that hosthips_refKeeps the referral that the ref parameter carried from hips.com (Section 13.4)The same lifetime, counted from when the referral was first seen on hips.com
13.4

The referral cookie and the ref parameter. Once the Affiliate Program opens, and only on a host where your choice allows the referral cookie:

  1. (a)opening a Program Partner's referral link, an address on hips.com with a ref parameter, sets hips_ref on hips.com. It holds the referral code, the time it was first seen and the link's campaign values, and nothing else about you. The first link counts: an unexpired hips_ref is never replaced by a later one;
  2. (b)setting it counts one click for the code. HIPS counts a click once per code per network address per day, using a hash of your IP address that it keeps for one day, and stores only daily counts per code and campaign values, which name no person;
  3. (c)every link from the Website into the Console points at hips.com/console, and the Website answers it with a redirect to console.hips.com. If you hold an unexpired hips_ref on hips.com, the redirect adds one ref parameter carrying its value. The Console keeps that value in its own hips_ref, under the same first-link rule, and at once removes the parameter from the address in your browser, so that it does not stay in your address bar or in a bookmark. 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 hips_ref only if your answer allows the referral cookie; otherwise it drops the value. No cookie passes from one host to the other;
  4. (d)when you register for early access on the Website, the value of your hips_ref on hips.com is stored with your registration, and when you create an Account, the Console sends the value of its own hips_ref with your sign-up; the earlier of the two counts (Section 3.8(b)). The Console clears its hips_ref once your Account is created, and the hips.com cookie expires on its own; and
  5. (e)on a host where your choice does not allow the referral cookie, HIPS sets none, and a ref parameter arriving there is dropped. HIPS removes the ref parameter from the server and edge records of www.hips.com, the Website (including the hips.com/console redirect) and the Console. The Website, the Console and the early-access forms work the same without it.
13.5

Browser storage, analytics and the film. Browser storage also remembers display preferences, such as the language of code samples and the explainer film's volume and mute choice, keeps an unsent playground draft in your browser's session storage, and keeps in session storage that you closed the invitation to watch the film. These stay in your browser and are not used to track you. At the date of this Notice, the Website runs no analytics, no advertising and no third-party script, and serves its fonts from its own domain; the explainer film is served by Cloudflare, which receives your IP address when the film or its poster loads. If HIPS introduces analytics, or any other cookie or similar technology that is not strictly necessary, it first adds it to this Section and to the table of Section 13.3 as a category of its own, off until you switch it on, and asks for your consent on each host before using it; HIPS's Cookie Notice gives the same information on cookies and browser storage in one place.

Section 13
  1. 13.1Every cookie belongs to one host
  2. 13.2Your choice, asked once on each host
  3. 13.3The cookies HIPS sets
  4. 13.4The referral cookie and the ref parameter
  5. 13.5Browser storage, analytics and the film
Copy link

14Information for particular countries

14.1

United Kingdom. If you are in the United Kingdom, the UK GDPR and the Data Protection Act 2018 give you rights that correspond to those in Section 11, and you may complain to the Information Commissioner's Office. HIPS has designated Prighter Ltd, 20 Mortlake High Street, London SW14 8JN, United Kingdom, as its representative in the United Kingdom under Article 27 of the UK GDPR. You and the Information Commissioner's Office may contact it, in addition to or instead of HIPS, on any matter concerning HIPS's processing of your Personal Data: data subjects through the Privacy Rights Manager that Prighter provides for HIPS at prighter.com, and authorities at office@prighter.com.

14.2

Switzerland. If you are in Switzerland, the Federal Act on Data Protection gives you rights that correspond to those in Section 11, and you may contact the Federal Data Protection and Information Commissioner. HIPS has not designated a representative in Switzerland: Article 14 of the Federal Act on Data Protection requires one only of a controller abroad whose processing of the personal data of persons in Switzerland is extensive, regular and involves a high risk for their personality, which HIPS's processing does not. If that changes, HIPS designates one and names it here; meanwhile you reach HIPS directly at hello@hips.com.

14.3

Canada. If you are in Canada, the Personal Information Protection and Electronic Documents Act applies to HIPS's handling of your Personal Data in the course of its commercial activities, and if you are in Quebec, Alberta or British Columbia, HIPS also complies with that province's private-sector privacy law to the extent it applies to HIPS. You may access and correct your Personal Data as Section 11 describes, and complain to the Office of the Privacy Commissioner of Canada or to the privacy commissioner of your province. Before the automated face check, HIPS gives you the notice and asks for the consent that Section 3.7 describes, and you may choose the face check by a person instead (Section 3.7(d)). For persons in Quebec, HIPS discloses its process of verifying identity by biometric characteristics, and the records Bynn creates for it, to the Commission d'accès à l'information du Québec before it runs any automated face check of a person in Quebec, and at least sixty (60) days before such records are first created, as sections 44 and 45 of the Act to establish a legal framework for information technology require; it asks for your express consent, records only the characteristics needed to link you to your identity document, uses them for no other purpose, and destroys them as Section 3.7(c) provides. Your Personal Data is kept in Ireland, is processed in HIPS's regional processing locations in Ireland, the United States and Japan, and may be processed in the other countries Section 10 describes, where courts and authorities may be able to obtain access to it under the law of those countries.

14.4

United States. If you are in the United States:

  1. (a)HIPS does not sell your Personal Data or share it for cross-context behavioral advertising (Section 4.6); on its present size and activity, HIPS does not meet the thresholds under which the California Consumer Privacy Act or the comprehensive privacy law of another state applies to it, and it checks this every year and before any change that could alter it. Whether or not such a law applies, HIPS gives every person in the United States the rights of Section 11, to know and access, to correct, to delete and to obtain a copy of their Personal Data, on the terms of that Section, and never treats anyone less favorably for exercising them. The Washington My Health My Data Act and Nevada Senate Bill 370, which apply without a size threshold, are addressed in points (e) and (g);
  2. (b)the Website and the Console do not track you across other websites, so they respond in the same way whether or not your browser sends a Do Not Track or Global Privacy Control signal, and HIPS allows no third party to collect information about your online activities over time and across websites through them;
  3. (c)HIPS offers no MTO in any form, and no other crypto-asset, to anyone in the United States, and connects no wallet (Section 3.4);
  4. (d)if you are a Provider or a Program Partner and a United States person, Sections 3.2, 3.8(e) and 4.2 describe Form W-9 and the information returns HIPS may file;
  5. (e)before the automated face check, HIPS asks for the written release, and publishes the retention and destruction policy and the Consumer Health Data Privacy Policy, that Section 3.7 describes;
  6. (f)a dispute between you and HIPS about your Personal Data is resolved as the United States section of the Common Clauses provides, except where a law that gives you a privacy right does not allow it;
  7. (g)if you are a Consumer whose Country is the United States, HIPS does not train on your Request Content unless you turn training on by the consent of Terms of Service Section 13.2(b), a separate and clear affirmative act, never preselected or bundled with any other choice, which names training and the screening, the categories of consumer health data the screening may process, its purpose, the categories of service providers that process it for HIPS and how to withdraw it; you may withdraw it at any time with the same switch; until you give it, HIPS's filters do not screen your Request Content for training and HIPS writes no training copy of it; and the Consumer Health Data Privacy Policy of Section 3.7(c) also covers your Request Content; and
  8. (h)HIPS processes Requests in its regional processing location in the United States (Ohio), and may forward a Request to it, while it keeps your Account data and billing records in Ireland (Section 10).
14.5

Japan. If you are in Japan, the Act on the Protection of Personal Information (the APPI) applies to HIPS's handling of your Personal Data in connection with supplying the Service to you, whether you use it as a Buyer, a Provider or a Program Partner, and HIPS applies it to you on that basis; the APPI requires no representative in Japan. In addition to the rest of this Notice:

  1. (a)HIPS and its representative. HIPS's name and address are in Sections 1.1 and 16, and the name of its representative, a director who represents HIPS, is given to you without delay on request at hello@hips.com.
  2. (b)Purposes. HIPS uses your Personal Data only for the purposes of Section 4.1, which include crash reports from the Provider App that you agree to send (Section 3.10) and the round trips of a Device (Section 10.3). Sections 3.5, 3.9 and 3.10 state what the Provider App sends from a Device, to whom and why; HIPS publishes them on the Legal Information Page and links them from the Provider App.
  3. (c)Entrusted handling. HIPS entrusts the handling of your Personal Data to the Operating Company and the Sub-processors of Section 9.1, such as Amazon Web Services, Rollbar and Bynn, and to Providers for Request Content; Stripe acts for HIPS and, for the purposes it decides itself, for itself (Section 2.6).
  4. (d)Recipients in foreign countries. HIPS keeps your Personal Data in Ireland, in the European Union, which the Personal Information Protection Commission designated on 23 January 2019, under what is now Article 28 of the APPI, as a foreign country with a system for the protection of personal information equivalent to Japan's. Some of your Personal Data also goes to the United States, which is not so designated: crash reports and error reports to Rollbar, payment and payout data to Stripe, which processes it in Ireland and the United States (Section 9.1), and a Request forwarded to HIPS's regional processing location in Ohio (Section 10.2); and Request Content may run on Devices in the other countries of Section 10.3. For each recipient in a country that the Personal Information Protection Commission has not designated, HIPS does not rely on your consent: each such recipient (Rollbar, Stripe, Amazon Web Services in the United States, and, for Request Content, Providers in the countries of Section 10.3) is bound by a contract with HIPS that requires it to handle your Personal Data with measures in line with the APPI, which is the system that Article 28(1) of the APPI and Article 16 of the Commission's rules allow; HIPS checks at least once a year that each recipient applies those measures and whether a law of its country may affect them, acts if an obstacle arises, and stops the provision if the measures can no longer be ensured. On request, HIPS gives you without delay the information Article 28(3) of the APPI requires: how the recipient's system is established, an outline of its measures, how often and how HIPS checks them, the recipient's country, any law of that country that may affect the measures, and any obstacle and what HIPS did about it.
  5. (e)Your requests. You may ask HIPS to notify you of the purpose of use of, to disclose, to correct, add to or delete, or to stop using or providing, the Personal Data HIPS holds about you, by the procedure of Section 11.3; HIPS discloses it in electronic form unless you ask for another form, and charges no fee.
  6. (f)Leaks. Where a leak of your Personal Data falls within the cases the Commission's rules set, HIPS reports it to the Personal Information Protection Commission and tells you, as Article 26 of the APPI requires.
  7. (g)Authority. You may contact the Personal Information Protection Commission of Japan.
14.6

The Republic of Korea. If you are in the Republic of Korea, the Personal Information Protection Act (the PIPA) gives you rights that correspond to those in Section 11, which you exercise as Section 11.3 describes, and you may complain to the Personal Information Protection Commission. HIPS has no address or place of business in the Republic of Korea and meets none of the criteria of Article 32-3 of the Enforcement Decree of the PIPA, so it has not designated a domestic agent; if it comes to meet one, it designates one and names it here. HIPS's chief privacy officer is its data protection officer, who can be reached at hello@hips.com (Section 16). The data of the automated face check is sensitive information under Article 23 of the PIPA. Before it runs, HIPS tells you its purpose, the items collected, how long they are kept, that you may refuse and what follows if you do (Article 15(2)), and asks for your consent separately from any other consent; it also asks, separately, for your consent to the processing of your passport number, which is personally identifiable information under Article 24 of the PIPA, and protects it by encryption. You may choose the face check by a person instead, and HIPS never refuses you a service because you refuse a consent that the service does not need (Article 16(3)). HIPS never asks for your resident registration number as Tax Information (Section 3.2), and never accepts an identity document that shows it (Section 3.7(e)).

HIPS stores your Personal Data outside the Republic of Korea, and entrusts its processing there to the recipients in the table below that act for HIPS (the Operating Company, Amazon Web Services, Rollbar, Bynn and Providers), because this is needed to conclude and perform its contract with you, which Article 28-8(1)(3) of the PIPA allows where this privacy policy discloses the items its paragraph (2) lists; the table below gives them. Where Stripe receives your Personal Data for its own purposes rather than as HIPS's entrusted person (Section 2.6), the provision rests on the Personal Information Protection Commission's recognition of the European Union and the European Economic Area under Article 28-8(1)(5) of the PIPA for Stripe Payments Europe, Limited and Stripe Technology Europe, Limited in Ireland and for any recipient in the European Economic Area, and, for a recipient elsewhere, on your separate consent under Article 28-8(1)(1), which HIPS asks for, with the items of Article 28-8(2), before the payment or payout that needs it. The Personal Information Protection Commission recognized the European Union and the European Economic Area on 16 September 2025, on which the transfers to Ireland and Estonia rest; the other transfers in the table rest on Article 28-8(1)(3), entrusted processing and storage needed to conclude and perform HIPS's contract with you, with the items of Article 28-8(2) disclosed in this table.

TableTransfers of Personal Data outside the Republic of Korea
RecipientCountryPersonal Data transferredWhen and howPurposeHow long the recipient keeps it
HIPS, with Amazon Web ServicesIrelandThe categories of Section 3.1 that concern youEach time you use the Service, over an encrypted network connectionThe purposes of Section 4.1The periods of Section 7
The Operating Company, Hyperscale Inference Processing Systems OÜEstoniaThe categories of Section 3.1 that concern you, as it operates the ServiceEach time you use the Service, over an encrypted network connectionOperating the Service for HIPS (Section 2.7)The periods of Section 7
Amazon Web Services (Amazon CloudFront)The country of the edge location nearest youRequest Content, in transit and in memoryEach time you send a Request to ai.hips.com, over an encrypted network connectionAnswering the RequestNot kept after the Request
HIPS's regional processing location, with Amazon Web ServicesJapanRequest Content, in memory; for a Provider, the data of Devices, their round trips and crash reports; the copies of account data of Section 10.1(b)Each time you send a Request or your Device connects, over an encrypted network connectionAnswering Requests and running Devices (Section 4.1)Request Content is not kept after the Request; the stores of Section 10.1(c) for the period stated there
HIPS's regional processing location, with Amazon Web ServicesThe United StatesRequest Content, in memoryWhen a Request without a region requirement is forwarded there (Section 10.2), over an encrypted network connectionAnswering the RequestNot kept after the Request
RollbarThe United StatesCrash reports from your Devices, without your identity (Section 3.10), and error reportsWhen the Provider App sends a report that you agreed to send, over an encrypted network connectionFinding and fixing faultsSection 7.11
StripeIreland and the United States (Section 9.1)Billing data and Payout dataWhen you pay or are paidPayments and payouts (Section 3.3)Under Stripe's own terms
BynnThe European Union; Bynn Intelligence, Inc. is a company of the United States (Section 9.1)The identity verification data of Section 3.1When you verify your identityIdentity verification (Section 3.7)Section 7.6
ProvidersThe countries of Section 10.3Request Content of a Request their Device runsWhile a Request runs on a Device, over an encrypted network connection through HIPS's regional processing locationsAnswering the RequestNot kept after the attempt

You may refuse these transfers by not using the Service, or by deleting your Account (Section 11.5); since HIPS cannot provide the Service without them, refusing them means that HIPS cannot provide it to you. You may refuse the transfer of crash reports alone by not agreeing to crash reports, or by turning them off (Section 3.10(a)), which has no other effect on your use of the Service.

14.7

Singapore. If you are in Singapore:

  1. (a)the Personal Data Protection Act 2012 (the PDPA) applies to HIPS's collection, use and disclosure of your Personal Data in Singapore; HIPS's data protection officer, designated under the PDPA, can be reached at hello@hips.com, and reads it during Singapore business hours;
  2. (b)you may ask for access to and correction of your Personal Data as Section 11 describes, and complain to the Personal Data Protection Commission;
  3. (c)HIPS transfers your Personal Data to Ireland, Estonia, Japan and the United States, to the recipients Sections 9.1 and 10 name, and, for Request Content, to Providers in the countries of Section 10.3. Section 26 of the PDPA allows a transfer out of Singapore only where the recipient is bound by legally enforceable obligations to protect the data to a standard comparable to the PDPA's, as the Personal Data Protection Commission's guidance explains; HIPS relies for its own processing on the law that binds it, the GDPR and, in Japan, the APPI; for its Sub-processors and Providers, on contracts that bind them to protect your Personal Data to a standard comparable to the PDPA's and that specify the countries to which it may be transferred, which are those of Sections 9.1 and 10; and, where a transfer is reasonably necessary for the conclusion or performance of HIPS's contract with you, on that necessity; and
  4. (d)HIPS never asks for your NRIC number as Tax Information (Section 3.2). Bynn reads your NRIC number, where your identity document shows it, only to verify your identity for HIPS, with your consent, because HIPS must establish your identity to a high degree of fidelity before it grants benefits once per person and pays Earnings or commissions, where a wrong identification risks significant financial harm (Personal Data Protection Commission, Advisory Guidelines on NRIC and other national identification numbers, paragraphs 3.12 and 3.13); HIPS stores no NRIC number and never derives the keyed hash of Section 3.7 from it.
14.8

Taiwan. If you are a national of Taiwan, the Personal Data Protection Act of Taiwan applies to HIPS's handling of your Personal Data although HIPS is outside Taiwan (its Article 51(2)). HIPS gives everyone in Taiwan, and every national of Taiwan, the information its Article 8 requires:

  1. (a)the collector is HIPS (Sections 1.1 and 16);
  2. (b)the purposes and the categories of Personal Data are those of Sections 3 and 4.1;
  3. (c)HIPS uses your Personal Data for the periods of Section 7; in Ireland, Estonia, Japan and the United States, where HIPS and its Sub-processors process it (Sections 9.1 and 10), and, for Request Content, in the countries of Section 10.3; by the recipients of Section 9; and by the automated and manual processing that Sections 4 and 5 describe;
  4. (d)you have the rights that Article 3 of the Act gives you: to inquire into and review your Personal Data, to ask for copies of it, to supplement or correct it, to ask HIPS to stop collecting, processing or using it, and to ask HIPS to delete it, which you exercise as Section 11.3 describes;
  5. (e)Section 4.7 states what follows if you do not provide Personal Data;
  6. (f)if your Personal Data is stolen, leaked or otherwise unlawfully accessed, HIPS tells you and reports it where the Act requires, as its Article 12 provides; and
  7. (g)you may complain to the Personal Data Protection Commission once the amendments to the Act of 11 November 2025 take effect on the date the Executive Yuan sets, and until then to the central government authority in charge of the relevant industry; HIPS collects and processes crash reports from the Provider App and the round trips of a Device on the basis of its contractual relationship with you (Article 19(1)(2) of the Act), with the security measures of Section 8, and you may decline crash reports, or turn them off at any time (Section 3.10).
14.9

Australia. If you are in Australia, HIPS handles your Personal Information in accordance with the Australian Privacy Principles of the Privacy Act 1988, whether or not that Act applies to it, and this Section gives the information that the Principles ask a privacy policy and a collection notice to give:

  1. (a)Overseas recipients. HIPS is likely to disclose your Personal Data to recipients overseas, and they are likely to be located in Ireland and the other states of the European Economic Area, the United States and Japan, and, for Request Content, in the other countries of Section 10.3; Sections 9 and 10 name them (Australian Privacy Principles 1.4(f) and (g) and 5.2(i) and (j)).
  2. (b)Access and correction. You may ask for access to your Personal Data and for its correction as Section 11.3 describes (Australian Privacy Principles 12 and 13).
  3. (c)Complaints. You may complain to HIPS at hello@hips.com, and, if you are not satisfied with its answer, to the Office of the Australian Information Commissioner.
  4. (d)Sensitive information. The automated face check involves biometric information used to verify your identity, which is sensitive information; Bynn collects it for HIPS only with your consent, and HIPS itself receives no biometric information, only the outcome of the check (Sections 3.1 and 3.7). The consent the face check needs under Australian Privacy Principle 3.3 is the explicit consent of Section 3.7(a): HIPS asks for it before the check, for that check only, after telling you what Section 3.7 describes, and you give it voluntarily, since you may choose the face check by a person instead, without detriment (Section 3.7(d)).
  5. (e)Automated decisions. HIPS uses computer programs to make, or to do things substantially and directly related to making, decisions that could significantly affect you (Section 5): (i) the kinds of Personal Information they use are your identity verification result, your Account, Workspace and payment data, Usage Data, the data of your Devices, their results and their hardware identifiers, and your referrals; (ii) the decisions made solely by them are an Account that stays inactive without verification, a hold of Earnings on a mismatch in a Device's results, the suspension of a Device where an exact mismatch in its results is confirmed by a second strong signal, the blocking of Credits on a card dispute, Settlement, the payment and payout methods and features offered for your Country, the rejection of a referral that matches its Program Partner, a Device kept from work by the hardware blocklist or a driver mark, and a flag or a temporary limit on a Workspace or an API key (Section 5.2); and (iii) the decisions for which they do a related thing, a person at HIPS deciding, are the review of a possible sanctions match, a finding of fraud and its consequences, a pause, a suspension or a closure of a Workspace or an Account, an entry on the hardware blocklist and the review of a held referral (Section 5.3). You may ask for a review by a person (Section 5.4).
  6. (f)Tax file numbers. HIPS never asks for your tax file number (Section 3.2).
Section 14
  1. 14.1United Kingdom
  2. 14.2Switzerland
  3. 14.3Canada
  4. 14.4United States
  5. 14.5Japan
  6. 14.6The Republic of Korea
  7. 14.7Singapore
  8. 14.8Taiwan
  9. 14.9Australia
Copy link

15Changes to this Notice

15.1

Updates. HIPS may update this Notice. HIPS gives at least thirty (30) days' notice of a material change before it takes effect, by email to Account holders and early-access registrants and by a notice on the Website, except where Applicable Law or a competent authority requires the change to take effect sooner or the change only adds to your protection, in which case HIPS gives notice as soon as it can, and shows the version and the date of the latest revision at the top of this page. The version of this Notice shown to you when you accept terms is recorded with that acceptance, and the version of the early-access privacy notice shown to you when you register for early access is recorded with that registration.

15.2

Effective date. This version of the Notice takes effect on the effective date shown at the top of this page, the date on which HIPS published it as in force. Version 1.1, of 27 October 2026, names HIPS's representative in the United Kingdom (Section 14.1), which only adds to your protection, and replaces version 1.0 of the same date.

Section 15
Copy link

16Contact

Postal address: HIPS Payment Group Limited, 5 The Courtyard Building, Carmanhall Road, Sandyford, Dublin 18, Ireland; registered in Ireland, number 639131; its VAT number is shown on each invoice. HIPS's Operating Company is Hyperscale Inference Processing Systems OÜ, Estonia (Section 2.7). HIPS has designated a data protection officer under Article 37 of the GDPR, who is also its data protection officer under Singapore's PDPA and its chief privacy officer under the Republic of Korea's PIPA, at hello@hips.com (Sections 14.6 and 14.7). HIPS's representatives outside the European Union are named in Section 14. The Legal Information Page at https://hips.com/legal lists HIPS's single points of contact for authorities and for users of the Service, the current list of Sub-processors, and every version of this Notice. Service emails come from noreply@hips.com and name support@hips.com as their reply-to address, which people at HIPS read; please write to the addresses below for privacy questions. General inquiries go to the contact address that the Website gives.

Privacy questions and requests
hello@hips.com
Security issues
security@hips.com, also published in /.well-known/security.txt on hips.com
Section 16
Copy link

Privacy Notice, version 1.1, superseded on 2026-10-27 by version 1.2, 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Ü