Terms of Service

1. Accepting these terms

Using the service accepts these terms: creating an account, embedding the SDK, calling an API with a site key, or reading the dashboard. Where a signed agreement exists with us, that agreement governs and these terms fill its gaps.

A person accepting on behalf of a company must be authorised to do so, and "you" below means that company.

2. What the service is

HideGuard measures the browser and the connection of a visitor to your website and returns a reading: a set of signals, a score, the reasons behind it, and a suggested outcome of allow, challenge or block.

It is a measurement service, and the principles it is built on are also limits on what it claims:

We may change how the engine scores, add checks, and withdraw ones that stop being evidence. A score is not a stable number across versions, and anything of yours that depends on an exact value rather than on the verdict and the reasons will move when the model does. The raw readings are kept precisely so that a change of model can be re-examined against history.

• Signals, not accusations. One flagged check is a signal; a conclusion needs corroboration from an independent cause.
• A measurement not taken is not a clean measurement. Where something could not be read, the record says so rather than treating it as a pass.
• Raw signals are stored, never bare verdicts, so that a changed model can be re-scored over what was actually observed.
• The demo never names the check that fired, because the same engine guards a payment page.

3. Accounts

There is no self-service sign-up. An account is created by us, or by the owner of a workspace through an invitation, which is single-use and expires in seven days.

You are responsible for what is done with your credentials and your keys.

• A site key is embedded in a page and is not a secret. Origin rules, not secrecy, are what stop another site posting as yours — keep them accurate.
• A site secret is a server-to-server credential and is genuinely secret. We store only its digest, we show it once, and we cannot recover it for you.
• Tell us promptly if a credential is exposed. We will rotate it; traffic accepted before the rotation stays accepted.
• Keep your workspace membership current. A member who has left keeps their access until somebody removes it.

4. What you are responsible for

You decide to deploy the SDK, and in data-protection terms you are the controller of what it collects while we are your processor. That makes the following yours rather than ours:

If you cannot meet these, do not deploy the SDK. This is the clause we will hold you to, and the one most likely to matter to the people whose browsers are being measured.

• A privacy notice on your own site that describes this collection and names us as a processor, accurate before the script first runs.
• A lawful basis for the collection, and, where your own legal advice requires consent, a mechanism that prevents the script loading until it is given.
• Answering the requests of your own visitors. We will help you find and delete records, but the obligation is yours.
• Never sending us a card number, a bank account, a government identifier, a credential, a health or biometric record, or anything else in a special category. The payment surface takes a processor token; anything that looks like a card number is refused and not stored.
• Never deploying the SDK on a service directed at children.
• Not using the readings to make a decision with a legal or similarly significant effect on a person without a human being able to review it, and not using them to discriminate on a protected characteristic.
• Keeping your use to your own sites and your own visitors. The readings describe your traffic, and reselling them, publishing them, or handing a raw record to a third party is not within this licence.

5. Acceptable use

You may not, and may not allow anyone else to:

• Use the service to identify, locate, track or expose a specific person outside the fraud-prevention purpose you deployed it for.
• Combine a reading with data from another source in order to attach a name, a face or a document to a visitor id.
• Deploy the SDK on a page whose operator has not agreed to it, or on a page you do not control.
• Resell, sublicense or redistribute the service, or build a competing detection product out of its output.
• Probe, load-test or reverse-engineer the service beyond what your own integration requires, or try to evade a quota or a rate limit.
• Send deliberately falsified readings in order to learn how the engine scores, or use the service to develop or test a tool for defeating it.
• Use the service unlawfully, or in breach of the rights of the people whose browsers it measures.

6. Plans, quotas and payment

Plans are listed in the dashboard. A plan sets the identifications included per month and how much visit history is retained:

Quotas are displayed and not enforced. The collector sits in front of your payment page, and cutting off your fraud checks over an invoice would punish your buyers rather than you, so going over a quota is a conversation. We may ask you to move to a larger plan, and we reserve the right to rate-limit traffic that threatens the service for everyone.

There is no payment provider integrated today. Plan changes are arranged with us directly, listed prices are in US dollars and exclusive of any tax, and nothing on the dashboard charges a card.

7. The verdict is advice

Everything the service returns is advisory. You decide what your site does with it, and that decision and its consequences are yours.

We do not warrant that the engine identifies every automated, tampered or proxied browser, or that it never flags an honest one. It is a probabilistic measurement of a browser that may be actively lying about itself, and an anti-detect build released tomorrow may clear a check that holds today. Treat a verdict as one input to your own risk decision, alongside the rest of what you know about an order.

In particular, the service is not a legal, compliance or identity-verification product. It does not verify who anyone is, it performs no know-your-customer check, and no reading from it should be presented as proof of identity or of fraud.

8. Your data

The records produced by your sites are yours. We process them to deliver the service to you, to keep it running, and to improve the detection engine — the last of these on signals and aggregates, never by handing one customer's records to another. We do not sell them and we do not use them for advertising.

The Privacy Policy describes what is collected and how long it is kept, and it forms part of these terms. Where you need a data processing agreement, ask and we will sign one; where it conflicts with this section, it prevails.

9. Availability

We aim to keep the service up, and will give notice of planned maintenance where we can. No uptime commitment is made by these terms; an availability target is a matter for a signed agreement.

Development and staging environments, and any instance we publish for testing, carry no commitment at all and may be reset without notice. Do not point production traffic at one.

10. Intellectual property

The service, the engine, the SDK, the dashboard and everything we publish about them remain ours. You are granted a non-exclusive, non-transferable, revocable right to embed the SDK unmodified on sites you control and to use the APIs for your own traffic, for as long as these terms are in force.

You may not modify, repackage or re-host the SDK. Feedback you send us may be used without obligation; it transfers nothing of yours to us other than that feedback.

11. Confidentiality

Site secrets, signing keys, prices quoted to you, and anything either side marks as confidential are to be kept confidential and used only for this service. The obligation survives the account.

12. Ending it

You may stop at any time by removing the SDK and asking us to close the account. We may suspend or close an account for a breach of the acceptable-use section, for non-payment under a signed agreement, or where the law requires it — immediately where a breach is causing harm, and with notice otherwise.

On closure, access ends at once. Records already written expire on the clock they were written with, or are deleted immediately if you ask; export what you need before you ask.

13. Liability

To the extent the law allows: the service is provided as it is, without warranty of merchantability, fitness for a particular purpose, or non-infringement. We are not liable for lost profit, lost revenue, lost data, chargebacks, fraud losses, or any indirect or consequential loss, including a loss arising from a verdict that was wrong in either direction.

Our total liability for all claims is capped at the amount you paid us for the service in the twelve months before the claim, or one hundred US dollars where you paid nothing. Nothing here excludes liability that cannot lawfully be excluded, including for death, personal injury, fraud or wilful misconduct.

14. Indemnity

You will indemnify us against a claim brought by one of your visitors, by a regulator, or by a third party, that arises from your deployment of the SDK — in particular from a missing privacy notice, a missing lawful basis, a breach of the acceptable-use section, or sending us data the customer-duties section forbids.

15. Changes to these terms

We may change these terms. The date at the top moves when they change, a material change is notified to account holders before it takes effect, and continuing to use the service after that is acceptance. If a change is unacceptable to you, close the account.

16. Governing law

Governing law and venue are those set out in the signed agreement between us. Absent one, these terms are governed by the laws of the Socialist Republic of Viet Nam, and the courts of Viet Nam have jurisdiction.

If a provision here is unenforceable, the rest stands. Write to [email protected] about anything in this document.