DRAFT - version draft-2026-11-03. Not yet in force.

HideFirst Terms of Service

Drafting note: The Services are B2B only (clause 2). A consumer who installs the Extension would bring consumer law (non-waivable rights, withdrawal, stricter unfair-terms control) into play. The founder decides whether to offer a separate consumer track; until then clause 2.2 excludes consumers and the sign-up flow should ask for a business name.

Effective date: [EFFECTIVE DATE]. Version: [VERSION].

1. Parties and definitions

1.1 These Terms of Service (the "Terms") are a contract between HideFirst, Inc., a Delaware corporation with its registered address at [REGISTERED ADDRESS] ("HideFirst", "we", "us"), and the business that creates an account or otherwise uses the Services (the "Customer", "you").

1.2 In these Terms:

1.3 If an Order conflicts with these Terms, the Order prevails for that Order only and only where it expressly says so.

2. Business use, acceptance and eligibility

2.1 The Services are offered to businesses, public bodies and self-employed professionals acting in the course of their trade, business, craft or profession.

2.2 You confirm that you are not a consumer and that you will use the Services only for those purposes. We do not offer the Services to consumers.

2.3 You accept these Terms by creating an account, by using an API key, by installing or using the SDK or the Extension for a business, or by signing an Order, whichever happens first. The person accepting confirms that they are authorised to bind the Customer.

2.4 You may read these Terms before you accept them: they are published at [TERMS URL] and are shown at sign-up. We will give you a copy on request.

2.5 You are responsible for your Authorised Users and for everything done under your account, as if you had done it yourself.

3. Accounts and API keys

3.1 You must give accurate account information and keep it current. An account may be created only by an individual with authority to act for the Customer.

3.2 API keys, passwords and sign-in tokens are secret. You must keep them confidential, store them securely, not embed them in code that is distributed to third parties, and not share them outside your organisation.

3.3 You are responsible for all use of the Services under your keys and accounts, authorised or not, until you revoke the key or notify us of a compromise. Tell us without undue delay at [security@hidefirst.com] if you suspect a key has been lost or misused. Keys can be revoked in the account service.

3.4 The Extension signs in through OAuth and receives an API key valid for 24 hours. A key issued this way is treated as your key.

3.5 We may require a stronger sign-in method, rotate keys, or reject keys that fail our security checks, where reasonably needed for security.

4. Plans, fees, metering, invoicing and taxes

4.1 The Services are offered under the plans described at [PRICING URL]. Paid plans are not yet available. Until we announce them, the Services are provided under the free plan described there, and clauses 4.2 to 4.7 apply only once you have chosen a paid plan.

4.2 Fees are as stated in your Order or plan: [FEES]. Fees are in [CURRENCY] and exclude taxes.

4.3 Usage is metered in units that carry no content: requests, tokens, OPRF elements per key per hour, and documents and characters per account per day. Our metering records are the basis for billing unless you show them to be wrong. Each plan states its included volume and rate limits.

4.4 We invoice [monthly/annually] in advance or in arrears as stated in the Order. Payment is due within [30] days of the invoice date. Payments are processed by Stripe once paid plans are live; Stripe's terms apply to that processing.

4.5 You are responsible for all taxes, duties and levies on the Services, except taxes on our income. Where VAT is due, we charge it as the law requires. If you owe withholding tax, you gross up the payment, unless the law forbids it.

4.6 If you dispute an invoice in good faith, tell us in writing within [30] days of the invoice date, pay the undisputed part, and we will work together to settle the rest. Late payments carry interest at the rate provided by the Belgian Law of 2 August 2002 on combating late payment in commercial transactions, and the fixed compensation it provides.

4.7 We may change prices only under clause 22 (changes). A price change never applies to a period already paid for.

5. Licence to the SDK and the Extension

5.1 Subject to these Terms and payment of any fees, we grant you a limited, non-exclusive, non-transferable, non-sublicensable, revocable licence during the term to install and run the SDK and the Extension, in the form we deliver them, on your own systems and devices, solely to use the Services for your internal business purposes.

5.2 The SDK and the Extension are licensed, not sold. They contain compiled code, WASM, and tables that are our trade secrets and intellectual property. Open-source components included in them are licensed under their own terms, listed in [NOTICES FILE]; nothing in these Terms restricts your rights under those licences.

5.3 We and our licensors keep all right, title and interest in the Services, the SDK, the Extension and the Model Materials, including all intellectual property rights. No rights are granted by implication or estoppel, and all rights not expressly granted are reserved.

5.4 You may make the copies of the SDK and the Extension that are needed to run them for your Authorised Users, and a reasonable number of backup copies.

6. Restrictions: protection of our intellectual property

6.1 You must not, and must not allow anyone else to, do any of the following, except as clause 6.3 permits:

(a) reverse engineer, decompile, disassemble, deobfuscate, or otherwise try to derive the source code, algorithms, structure, weights or internal logic of the SDK, the Extension, any WASM module, or any model bundle or table, or attempt to access them in decrypted or unpacked form;

(b) extract, copy, or reconstruct the Model Materials, or build a dataset of our Outputs or of the Payload format in order to do so;

(c) distil, imitate or replicate our models, or use the Services, Outputs or Payload to train, fine-tune, evaluate for training purposes, calibrate or improve any model, classifier or detection system, whether yours or a third party's. This covers Outputs of every kind, including probabilities, masks and placeholders, and the Payload format;

(d) query the Services systematically, in volume, or with crafted inputs, in order to learn or reconstruct the model, its word lists, thresholds, feature definitions, safe-word table or any other table, or to map the behaviour of the Services;

(e) scrape, harvest or crawl the Services, the Model Materials or the account service, by automated means or otherwise, except through the documented API within your plan;

(f) benchmark or evaluate the Services in order to build, improve or market a product or service that competes with the Services, or give such benchmarking to a third party;

(g) publish, disclose or give to a third party any benchmark, evaluation or performance result about the Services without our prior written consent;

(h) circumvent, disable or interfere with rate limits, quotas, usage metering, key restrictions or scopes, the OPRF shielding (including per-key limits on OPRF lookups), model-bundle signature checks, licence or access controls, or any other technical protection, or use more keys, accounts or devices than needed to avoid them;

(i) share, sell, lend, lease, resell, sublicense or make available your API keys, accounts, the SDK or the Extension to anyone who is not your Authorised User, or offer the Services as part of a competing or white-label service;

(j) remove, alter or obscure any copyright, trade mark, licence or other proprietary notice, or the identification of HideFirst in the SDK, the Extension or the documentation;

(k) modify the SDK or the Extension, or create derivative works from them, except for configuration that the documentation allows;

(l) re-identify, or attempt to re-identify, a person from Outputs, from pseudonymised text or from a Payload of a third party, or from any Payload by analysis rather than through your own alias book. Restoring your own text with your own alias book, as the SDK and the Extension do, is permitted.

6.2 Ordinary internal evaluation of whether the Services fit your own use (for example, testing them on your own documents to see what they detect, within your plan limits) is permitted. Publishing the results needs consent under clause 6.1(g).

6.3 Nothing in these Terms prevents you from doing what mandatory law expressly permits you to do notwithstanding a contractual prohibition, in particular the acts permitted by articles 5(3) and 6 of Directive 2009/24/EC on the legal protection of computer programs (observation, study and testing of the program's functioning, and decompilation strictly necessary to achieve interoperability), as implemented in Belgium. This permission is narrow and applies only to the extent and in the circumstances the law prescribes. We make interface information available on request at [legal@hidefirst.com], so that it is readily available. Decompilation of any part of the SDK or the Extension is permitted only where and to the extent that Directive 2009/24/EC art. 6 allows it, that is, when that information is not readily available to you. The information you obtain this way may be used only for the permitted purpose, must not be given to others except where necessary for interoperability, and must not be used to develop, produce or market a program substantially similar in expression, or for any other act that infringes our rights.

6.4 You will promptly tell us if you learn of a breach of this clause 6, and will cooperate with us to stop it.

6.5 You acknowledge that a breach of clause 6 would cause us harm that damages cannot fully repair, and that we may seek an injunction or other urgent relief from a competent court, in addition to other remedies.

7. Customer Content, Outputs and Feedback

7.1 You keep all rights, title and interest in the Customer Content. We receive no rights in it under these Terms. The SDK and the Extension process your text on your own device; the text itself is never sent to us. Only the Payload leaves your device.

7.2 We do not store the Payload or the responses to it, except a Payload you choose to send to our support for diagnosis, which we handle under the DPA. Our logs hold only the method, path, status, token count, timing and per-key counts, and no Payload or response content.

7.3 You may use the Outputs for your own pseudonymisation and for your internal business purposes. Outputs may not be used in the ways that clause 6.1 prohibits.

7.4 We and our licensors keep all rights in the Model Materials, in the Services, and in the aggregate scores and Outputs of the Services considered as a dataset, and in all tables and word lists used by them. Nothing in clause 7.3 gives you any right in them.

7.5 The alias book (the map from real names to placeholders) is kept only on your devices, encrypted. We cannot recover it. If you lose the passphrase or the device key, we cannot restore it, and text pseudonymised with it can no longer be restored to its original form by us.

7.6 If you send us suggestions, bug reports or other feedback about the Services ("Feedback"), you grant us a worldwide, perpetual, irrevocable, royalty-free, transferable and sublicensable licence to use it without restriction and without any duty to you. Feedback does not include Customer Content. We will not identify you as its source without your consent.

8. Customer data and privacy

8.1 The Privacy Statement describes how we handle personal data for which we are the controller, such as account data and usage records.

8.2 To the extent that we process personal data on your behalf in providing the Services, the DPA applies. It forms part of these Terms, and takes effect when you accept these Terms, without separate signature. If these Terms and the DPA conflict on the processing of personal data, the DPA prevails.

8.3 The Payload is not anonymous. It contains no letters, no hash of a word and no offsets, but a determined party with access to it could infer some information from it, and about 44% of tokens reach us as the word itself (function words and common safe words). You must treat the Payload as pseudonymous personal data where the underlying text contains personal data. You remain the controller (or, for your own customers' data, their processor) of the personal data in the Customer Content, and you are responsible for having a lawful basis and for the information you owe to the individuals concerned.

8.4 You must not send us, or process with the Services, data that you have no right to process, or any data in a way that the law forbids.

9. No warranty of complete detection

9.1 The Services reduce the exposure of personal data and other sensitive information. They do not eliminate it, and they are not a guarantee of anonymity.

9.2 Detection is imperfect. The Services will miss some names and identifiers. Categories of known weakness include names written in lower case, numbers written out in words, text in scripts other than Latin script, and unusual formats of identifiers, dates, addresses and the like. They may also mask text that should have remained visible.

9.3 Our published measurements describe performance on our own test corpus and are not a promise of performance on your documents. Results vary with language, genre, formatting and policy settings.

9.4 You must review the output wherever the stakes of a missed item require it, in particular before sending it to a third party, to a public forum, to a regulator, or to an AI chat service. You remain solely responsible for deciding what to send to third parties, and for your compliance with law and with your own obligations of confidentiality and secrecy. The Services are a tool to assist you, not a replacement for your judgment, and you should not use them as the only safeguard for information whose disclosure would cause serious harm.

9.5 The local rules in the SDK (identifiers with checksums, e-mail addresses and phone numbers) are applied on your device regardless of the server's responses. A compromised or faulty server could still return lower probabilities, so that less is masked. We do not warrant that this will not occur.

9.6 Subject to clause 10 and to our express commitments in these Terms and the DPA, and to the extent permitted by law, THE SERVICES, THE SDK AND THE EXTENSION ARE PROVIDED "AS IS" AND "AS AVAILABLE", AND WE GIVE NO OTHER WARRANTY, EXPRESS OR IMPLIED, INCLUDING OF COMPLETE OR ERROR-FREE DETECTION, UNINTERRUPTED AVAILABILITY, OR FITNESS FOR A PARTICULAR PURPOSE.

9.7 Where mandatory law gives you rights against us that cannot be excluded by contract, these Terms do not exclude them.

10. Our commitments

10.1 We will provide the Services with reasonable care and skill, as a diligent provider of similar services would.

10.2 We do not store the content of your documents. We do not receive your text, and we do not store or log the Payload or the responses to it, except a Payload you choose to send to our support for diagnosis, which we handle under the DPA.

10.3 We will keep the technical and organisational security measures described in the DPA, and we will not materially reduce them during the term.

10.4 We will use reasonable efforts to keep the Services available and will tell you in advance, where practicable, of planned maintenance. [Service levels, if any, are stated in the Order.]

10.5 We will keep model bundles signed, and the production service will refuse unsigned bundles.

10.6 These commitments are essential obligations of ours. Nothing in clause 9 or 11 limits them to the point of emptying them of substance.

11. Liability

11.1 Subject to clause 11.4, the total liability of each party to the other arising out of or in connection with these Terms, whether in contract, tort or otherwise, in any period of twelve months is limited to the greater of (a) the fees you paid to us for the Services in the twelve months before the event that gave rise to the claim and (b) EUR [5,000].

11.2 Subject to clause 11.4, neither party is liable to the other for indirect or consequential loss, loss of profit, loss of revenue, loss of anticipated savings, loss or corruption of data, loss of goodwill, or reputational harm, even if told of the possibility.

11.3 You acknowledge that the Services can fail to detect or to mask information (clause 9), and that we do not control what you do with the output. Loss resulting from the disclosure of information that the Services did not mask is, to the extent that it is a consequence of the limits described in clause 9, within clauses 11.1 and 11.2.

11.4 The limits and exclusions in clauses 11.1 to 11.3 do not apply to:

(a) intentional fault (opzet / faute intentionnelle), or fraud;

(b) gross fault (zware fout / faute lourde) of the party, its legal representatives, or its employees or agents;

(c) harm to life or to physical integrity;

(d) your breach of clause 6 (intellectual property restrictions) or of the Acceptable Use Policy;

(e) your obligation to pay fees;

(f) your indemnity under clause 12;

(g) any liability that cannot be limited or excluded under mandatory law.

Clause 11.2 does not exclude our liability for failing to perform the essential obligations in clause 10; that liability remains subject to the cap in clause 11.1.

11.5 These limits apply to the fullest extent permitted by law, are reflected in our pricing, and do not require either party to prove the other's loss in any special form beyond what the law requires.

12. Indemnity

12.1 You will indemnify us against third-party claims, and the losses, damages, costs and reasonable legal fees arising from them, to the extent that they result from: (a) your breach of clause 6 or of the Acceptable Use Policy; or (b) the Customer Content, or your processing of it, including your lack of a right to process it.

12.2 We will tell you promptly of the claim, let you control its defence and settlement (except that you may not settle in a way that admits fault for us or imposes obligations on us without our consent), and give you reasonable help at your cost.

12.3 We will defend and pay damages finally awarded against you in a third-party claim that the Services, used as these Terms permit, infringe that third party's intellectual property right in the EU, subject to clause 11, under the procedure in clause 12.2 applied in reverse. If a claim is likely, we may modify the Services or end the affected feature and refund prepaid fees for the unused period. This is your exclusive remedy for such claims.

13. Suspension

13.1 We may suspend your access, or a key, an account or a feature, immediately if: (a) it is needed to address a risk to the security or integrity of the Services or of other customers; (b) we reasonably believe you are in breach of clause 6 or of the Acceptable Use Policy, or your use is abusive or unlawful; or (c) you have not paid an undisputed invoice within [14] days after a written reminder.

13.2 Suspension must be proportionate to the reason, limited to what is needed, and lifted as soon as the reason has gone. We will notify you in advance where we can, and otherwise as soon as we can, and say why.

13.3 If we suspend you under clause 13.1(c), you are still liable for fees for the suspension period.

14. Term and termination

14.1 These Terms apply from acceptance until terminated.

14.2 You may terminate for convenience at any time, by closing your account or by written notice. Subject to clause 15, termination takes effect at the end of the current paid period unless the Order says otherwise, and prepaid fees are not refunded except as the Order or the law provides.

14.3 We may terminate for convenience on [30/90] days' written notice. If you have prepaid, we will refund the fees for the period after termination.

14.4 Either party may terminate on written notice if the other commits a material breach and does not cure it within [30] days of a written notice that describes it. No cure period applies to a breach of clause 6 or of the Acceptable Use Policy, or to a breach that cannot be cured, and we may terminate for it immediately on notice.

14.5 Either party may terminate immediately on notice if the other becomes insolvent, enters liquidation, or ceases to carry on business, to the extent that insolvency law allows.

14.6 On termination: (a) your keys are revoked and your access ends; (b) the licence in clause 5 ends, and you must stop using the SDK and the Extension, and delete all copies of them and of any Model Materials in your possession; (c) fees accrued up to the termination date remain due; (d) we will delete or anonymise the account data we hold about you within [RETENTION: 30 days after closure], except what we must keep by law; and (e) clauses that by their nature should survive do so, including clauses 1, 4 (fees accrued), 6, 7.4, 7.6, 9, 11, 12, 14.6, 15, 17, and 20 to 29.

14.7 The local alias book stays on your devices. Termination does not remove it. You should restore any pseudonymised text you need before you delete the SDK or the Extension.

15. Switching and exit

15.1 In line with articles 25 and 26 of Regulation (EU) 2023/2854 (the Data Act), you may initiate switching to another provider of comparable services, or to your own systems, or exit the Services, on notice of at most two months.

15.2 After the notice period, a transitional period of up to 30 calendar days applies. During it we keep providing the Services under these Terms, with the same level of security, and we assist you with the switch. At your request we extend the transitional period where the law allows.

15.3 After the transitional period, you have a data-retrieval period of at least 30 calendar days.

15.4 The exportable data is exhaustively: account and organisation data, members and roles, settings, API key metadata (not the secrets) and usage records. We give it to you in a structured, commonly used and machine-readable format (such as JSON or CSV). No Customer Content or Payload is held by us, so there is none to export. The alias book and the per-organisation OPRF customer key and word table are [exportable / not exportable: founder to decide]. Moving pseudonymised text to another provider needs your own alias book and keys.

15.5 After the data-retrieval period we erase the exported data and confirm the erasure to you in writing.

15.6 We make no switching charge and no data-egress charge. Standard fees for the period before the switch remain due.

15.7 On request, and in the documentation, we give you information on the switching procedure and on the export formats.

15.8 Nothing in this clause limits any right you have under Regulation (EU) 2023/2854 (the Data Act).

16. Confidentiality

16.1 "Confidential Information" means non-public information that one party discloses to the other in connection with these Terms and that is marked confidential or that a reasonable person would see as confidential. Our Confidential Information includes the Model Materials, the non-public parts of the SDK and Extension, security information and non-public pricing. Customer Content is yours; it is not disclosed to us.

16.2 The recipient will use Confidential Information only for these Terms, protect it with at least reasonable care, and disclose it only to those of its employees, advisers and subcontractors who need it and are bound to confidentiality.

16.3 This clause does not cover information that is or becomes public without breach, was already known to the recipient, is independently developed, or is lawfully received from a third party. A party may disclose Confidential Information where law or a court order requires it, after giving the other party notice where it lawfully can.

16.4 This clause continues for [five] years after termination, and for trade secrets for as long as they remain trade secrets.

17. Export control and sanctions

17.1 You will not use, export or re-export the Services in breach of applicable EU, Belgian, U.S. or other export control or sanctions law. You declare that neither you nor your Authorised Users are on a sanctions list or owned or controlled by a listed person.

17.2 We may suspend or end the Services to the extent needed to comply with such law.

18. Force majeure

18.1 Neither party is liable for a failure or delay in performing (other than payment obligations) caused by events beyond its reasonable control, including natural disaster, war, terrorism, strike, failure of public networks or power, failure of an upstream hosting provider despite reasonable precautions, or government action, if it notifies the other and takes reasonable steps to limit the effect.

18.2 If the event lasts more than [60] days, either party may terminate the affected Services on written notice, with a refund of prepaid fees for the period after termination.

19. Assignment and subcontracting

19.1 You may not assign or transfer these Terms without our prior written consent, which we will not unreasonably withhold, except to a successor to all or substantially all of your business who is bound by these Terms and is not one of our competitors.

19.2 We may assign these Terms to an affiliate or to a successor to our business, on notice to you. If you object on reasonable grounds, you may terminate under clause 22.3.

19.3 We may use subcontractors and sub-processors, and remain responsible for them as for ourselves. Sub-processors of personal data are governed by the DPA, including its list of sub-processors and its notice and objection procedure.

20. Notices

20.1 We may give notices to the e-mail address of your account owner or administrator, or by a message in the account service. You may give notices to us at [legal@hidefirst.com], with a copy to [REGISTERED ADDRESS] for notices of termination for breach or of a claim.

20.2 A notice by e-mail is treated as received on the next business day after it is sent, unless the sender receives a delivery failure message. You must keep your contact address current.

20.3 Security notices and notices of personal data breaches follow the DPA.

21. Entire agreement and order of precedence

21.1 These Terms, the DPA, the Acceptable Use Policy and any Order are the entire agreement on their subject and replace earlier agreements and proposals on it. Terms in your purchase orders or other documents do not apply.

21.2 In case of conflict, the order of precedence is: (1) the DPA, for the processing of personal data; (2) an Order, where it expressly overrides; (3) these Terms; (4) the Acceptable Use Policy; (5) documentation.

22. Changes to the Terms and to the Services

22.1 We may change these Terms, the fees, or the features of the Services only for a valid reason, namely: a change in law or in a regulator's or court's requirements; a security need; the technical obsolescence of a component or of a third-party dependency; a change in the costs of providing the Services that is outside our control; the correction of an error; or new features or services added at no extra charge that do not reduce existing ones. The notice will state the reason.

22.2 We will give you at least 30 days' notice of a change that is not purely favourable to you, by e-mail to your account owner and in the account service. A change that is needed for security or required by law with immediate effect may take effect sooner, to the extent necessary, and we will tell you why.

22.3 If you do not accept a change, you may terminate before it takes effect, without penalty, by written notice, and we will refund any prepaid fees for the period after termination. If you continue to use the Services after the change takes effect, you accept it, if the notice said so.

22.4 The change does not apply to a period you have already paid for.

22.5 We may change or discontinue a feature of the Services only for one of the reasons in clause 22.1 and with the notice in clause 22.2, unless the change is purely favourable to you. If we discontinue a material paid feature, we refund the prepaid fees for it.

22.6 Neither party has the sole right to interpret these Terms. Where a provision is unclear, it is interpreted by the competent court or arbitrator under the law in clause 26, and, against the party that drafted it, in case of doubt, as the law provides.

23. Severability and waiver

23.1 If a provision of these Terms is void, invalid or unenforceable, in whole or in part, the rest of these Terms remains in force, and the parties will replace the provision with a valid one that comes as close as possible to its economic purpose.

23.2 A party's failure or delay in exercising a right is not a waiver. A waiver must be in writing and applies only to the case it concerns.

24. Relationship of the parties and third parties

24.1 The parties are independent contractors. These Terms create no partnership, agency, employment or fiduciary relationship.

24.2 These Terms confer no rights on third parties, except that our affiliates and licensors may enforce clauses 5 to 7 and 16.

25. Language

25.1 These Terms are written in English. A translation is given for convenience only, and the English text prevails.

26. Governing law and disputes

26.1 These Terms and any dispute arising out of or in connection with them are governed by Belgian law, excluding its conflict-of-law rules and the UN Convention on Contracts for the International Sale of Goods.

26.2 The courts of Brussels (the French-speaking or Dutch-speaking section, at the claimant's choice, as the law on language permits) have exclusive jurisdiction, except that we may also seek injunctive relief to protect our intellectual property in any court competent for the infringer.

26.3 [ALT: These Terms are governed by the law of the State of Delaware, USA, without regard to its conflict-of-law rules, and the courts of Delaware have exclusive jurisdiction, for Customers whose principal place of business is outside the European Union.]

26.4 Before starting court proceedings, except for urgent relief, each party will try in good faith to settle a dispute by a written notice to the other and a meeting of senior representatives within [30] days.

26.5 The courts' jurisdiction and the choice of law do not remove the protection of mandatory provisions that apply to you under Belgian or EU law irrespective of the contract, including Book VI of the Code of Economic Law on unfair terms between businesses, Book 5 of the Civil Code, the Data Act and the GDPR.

Drafting note: Belgian law and the Brussels courts are the default, the Delaware alternative is for non-EU customers. Whatever law is chosen, the GDPR and the Data Act apply through their own scope. The Belgian B2B unfair-terms rules (WER VI.91/3 ff.) and Civil Code 5.89 protect the customer reliably only under Belgian law: HideFirst, Inc. is a US company, so Rome I art. 3(3) and 3(4) do not apply, and these rules are probably not overriding mandatory provisions under art. 9. Also check whether a language-of-proceedings rule applies to a Delaware entity facing Belgian customers.

27. Compliance with law

27.1 Each party will comply with the laws that apply to it in connection with these Terms. You are responsible for deciding whether and how you may lawfully use the Services in your jurisdiction and in your sector, including any professional secrecy duties (for example those of lawyers, doctors and accountants).

27.2 You will not use the Services in a way that infringes the rights of others, including privacy and intellectual property rights.

28. Publicity

28.1 We will not use your name or logo as a reference without your written consent, which you may withdraw at any time.

29. Contact

29.1 General and legal: [legal@hidefirst.com]. Privacy: [privacy@hidefirst.com]. Security and vulnerability reports: [security@hidefirst.com]. Post: HideFirst, Inc., [REGISTERED ADDRESS]. EU representative or establishment for data protection matters: [EU REPRESENTATIVE / EU ESTABLISHMENT].

Terms of Service | Data Processing Agreement | Privacy Statement | Acceptable Use Policy