Bawarii Developer Preview Terms of Service
Version 1 · In effect from 15 Nov 2026
1. Who we are and what these terms cover
1.1 These terms are an agreement between TEKNOSPARC LTD, a company registered in England and Wales (company number 14615978) (“Bawarii”, “we”, “us”) and the organisation that applies for access (“you”).
1.2 They cover the Bawarii developer portal at developer.bawarii.com, the sandbox API at sandbox.api.bawarii.com, the documentation, the downloads offered in the console, and any API key we issue to you (together, “the Service”).
1.3 The person who accepts these terms confirms that they are at least 18 years old and have authority to bind the organisation. The Service is for organisations building identity verification into their products. It is not offered to consumers.
1.4 These terms work together with:
- the Sandbox Acceptable Use Policy (“AUP”), which forms part of these terms;
- the Data Processing Addendum in Annex A, which forms part of these terms; and
- the Sandbox Privacy Notice, which explains how we handle personal data. It is a notice, not a contract term.
2. Developer Preview status
2.1 The Service is a Developer Preview. It is offered for evaluation, development and testing only.
2.2 There is no service level agreement. We do not promise any level of availability, uptime, response time, accuracy or support.
2.3 The Service may be slow, unavailable or offline at any time. This includes planned changes, slow first requests after idle periods, and periods when we switch the Service off to stay within our budget.
2.4 Sandbox results are test results. In the sandbox, face matching is not performed, every result is marked "environment": "sandbox", and verdicts are capped at the lowest assurance level. Sandbox results are not identity verification. You must not rely on them for any decision about a real person.
2.5 We may change, limit or stop any part of the Developer Preview, including ending it, under clause 9.
3. No production use
3.1 You must not use the Service, or any result from it, in production. “Production” means any use that makes or supports a decision about a real person, a real account, a real transaction or a real compliance decision.
3.2 You may submit only data that you are entitled to process. The AUP sets out this rule in full.
3.3 Production access, live keys and the terms for them are not part of this agreement. They will be offered, if at all, under separate written terms.
3.4 You confirm, for everything you submit to the Service, that: (a) you have a lawful basis for processing it; (b) you have given your end users the notice, and obtained the consent, that the law requires; and (c) you are entitled to process it for the purpose of developing and testing your integration. Annex A applies to this data.
4. Your account and organisation
4.1 You apply through the portal with a work email address. Your account must be secured with an authenticator app (TOTP). You must keep your password and authenticator secure and must not share them.
4.2 You must give accurate information in your application and keep it up to date. We review applications and may approve or refuse any application at our discretion. We may tell you the reason category for a refusal.
4.3 In this version of the Service an account belongs to one organisation, and an organisation has one member.
4.4 You are responsible for everything done through your account and your organisation’s API keys, including by your staff and contractors.
5. API keys
5.1 We issue sandbox API keys (prefix bwr_test_) through the console. Each key is shown once, when it is created. We do not store the key itself and cannot show it again.
5.2 You must keep every key confidential. In particular you must:
- (a) use keys only on servers you control, and never place a key in a mobile app, a web page, client-side code or any software you distribute;
- (b) never commit a key to a public repository, post it in a public forum or include it in a support request;
- (c) never share a key with another organisation; and
- (d) revoke a key in the console as soon as you suspect it has been exposed, and tell us at developers@bawarii.com within 24 hours.
5.3 Keys expire after 90 days. You may hold up to 3 active keys at a time, and you may replace or revoke a key at any time. A revoked key may keep working for up to 60 seconds after revocation.
5.4 You are responsible for activity under your keys until they are revoked and that period has passed.
6. Quotas and limits
6.1 The Service has limits. These include a daily number of sessions per organisation and across the sandbox, a number of uploads per session, a number of active keys, a daily request budget, and limits on requests without credentials. The current figures are published in the documentation.
6.2 When a limit is reached, the Service refuses further requests until the limit resets. You must not try to get around a limit, for example by opening extra accounts or organisations.
6.3 We may change any limit at any time, without notice, to protect the Service or to control cost.
7. Fees
7.1 The sandbox is free of charge during the Developer Preview.
7.2 If we introduce fees for the sandbox, we will give you notice under clause 10 first. Fees for production access will be set out in separate terms (clause 3.3).
8. Suspension and revocation
8.1 We may take any of these steps, depending on the seriousness of the issue:
- (a) a warning;
- (b) revoking one or more API keys;
- (c) suspending your organisation’s access;
- (d) terminating your access and these terms.
8.2 We may take any step immediately, without first taking a lesser step, if we reasonably believe that:
- (a) data that you are not entitled to process has been submitted;
- (b) a key or account has been compromised;
- (c) your use threatens the security, integrity, availability or budget of the Service or of other developers;
- (d) you have broken the AUP or these terms in a serious way; or
- (e) the law, a regulator, a court or a sanctions rule requires it.
8.3 Where it is lawful and safe to do so, we will tell you what we did and why, by email to your account address. You can ask about a decision at developers@bawarii.com.
8.4 While access is suspended or removed you can still sign in to read the decision, revoke keys and request deletion of your account.
9. Ending this agreement
9.1 You may end this agreement at any time by requesting deletion of your account, from your Account page or at developers@bawarii.com. We complete the deletion within one month. Deleting the account revokes all keys and removes your sandbox data, as the Sandbox Privacy Notice describes.
9.2 We may end this agreement for any reason with 30 days’ notice by email, including when the Developer Preview ends. We may end it immediately under clause 8.2.
9.3 When this agreement ends, all your keys stop working and you must stop using the Service. You must also delete every copy of the liveness model, as clause 11.4 requires. Clauses 3, 5.4, 11 (including the duty in 11.4 to delete every copy), 12, 13, 14 and 16 continue after it ends, and Annex A continues until the deletion it describes is complete.
10. Changes to the Service and to these terms
10.1 We may change the Service at any time. We will try to announce changes that break existing integrations in the documentation or by email before they take effect, but in a Developer Preview we cannot promise to.
10.2 Every version of these terms, the AUP and the Sandbox Privacy Notice has a whole-number version and a stable address on developer.bawarii.com. Earlier versions stay available there. Each new version carries a short “What changed” summary.
10.3 When we publish a new version of these terms or the AUP, we will email you at least 14 days before it takes effect. We may shorten that period where a change is needed for security or by law.
10.4 After a new version takes effect, you must accept it in the console before you can create keys or download files. Until you accept, existing keys keep working until they expire, at most 90 days, and you can still revoke keys, sign out and request deletion of your account.
10.5 If you do not agree to a new version, your remedy is to stop using the Service and request deletion of your account.
10.6 We record each acceptance with the document versions and their fingerprints, your account identifier, your organisation, the time, when you signed in, and the authenticator your session was signed in with.
11. Intellectual property
11.1 We and our licensors own the Service, the portal, the documentation and the API. Except for the licences in this clause, nothing in these terms gives you any right in them.
11.2 We give you a non-exclusive, non-transferable, revocable licence, for the term of this agreement, to use the Service and documentation to develop and test your integration with Bawarii.
11.3 The source code of the reference application is published on GitHub under the Apache License 2.0. The SDK packages are under the licence stated in each package, which grants use only under these terms.
11.4 Liveness model. We give you a non-exclusive, non-transferable, revocable licence, for the term of this agreement, to use the on-device liveness model only to develop and test your Bawarii integration against the sandbox. You may include the model in internal test builds of your app that you distribute only to your own staff and testers, and you may let the SDK deliver the model to, and cache it on, the devices that run those builds. The same restrictions apply to the cached copy. You must not publish the model, include it in a public or app-store release, distribute it separately, or use it in production. Production use needs separate terms (clause 3.3). You must keep the NOTICE file (which carries the Apache-2.0 notice of the Silent-Face-Anti-Spoofing work the model derives from) with every copy. When this agreement ends or your access is revoked, you must stop using the model and delete every copy, including copies cached on devices.
11.5 You keep all rights in your own software and data. You give us the rights we need to process what you send to the Service in order to run it.
11.6 If you send us feedback, we may use it without any obligation to you.
11.7 You may say that your product integrates with Bawarii. You must not use our name or logo in any other way, or suggest that we certify, endorse or partner with you, without our written consent. “Bawarii” is a trademark for which an application is in process; it is not yet registered.
12. Your responsibilities and indemnity
12.1 You must comply with all laws that apply to your use of the Service, including data protection, export control and sanctions laws.
12.2 You confirm that neither your organisation nor anyone who controls it is the target of sanctions administered by the United States (OFAC), the European Union, the United Kingdom or the United Nations, and that you will not use the Service for the benefit of any such person or in any territory subject to comprehensive sanctions. We check each organisation and its signatory against those lists before approval.
12.3 You will indemnify us against third-party claims, fines and reasonable costs arising from your breach of clause 3, clause 5, Annex A or the AUP, including any submission of data you were not entitled to process and any claim by your end users about what you submitted.
13. Disclaimers
13.1 The Service is provided “as is” and “as available”. To the extent the law allows, we give no warranty of any kind, express or implied, including fitness for a particular purpose, accuracy of results, merchantability and non-infringement.
13.2 We do not warrant that the Service will detect forged documents, spoofing attempts or any other fraud.
14. Limitation of liability
14.1 Nothing in these terms limits liability that cannot be limited by law, including liability for death or personal injury caused by negligence, or for fraud.
14.2 Subject to 14.1, neither party is liable for loss of profit, revenue, business, goodwill or data, or for any indirect or consequential loss.
14.3 Subject to 14.1, our total liability under or in connection with these terms is limited to EUR 100.
14.4 Clause 14.2 and 14.3 do not limit your liability under clause 12.3.
15. Notices
15.1 We send notices to your account email address or show them in the console.
15.2 You send notices, including formal legal notices, to developers@bawarii.com.
15.3 Security vulnerabilities go to developers@bawarii.com, as described in the AUP.
16. General
16.1 Order of precedence. If documents conflict, this order applies: (a) a separate agreement signed by both parties for the Developer Preview; (b) these terms; (c) the AUP; (d) the documentation. Nothing in these terms reduces your rights described in the Sandbox Privacy Notice.
16.2 Governing law. These terms are governed by the law of England and Wales.
16.3 Venue. The courts of England and Wales have exclusive jurisdiction over any dispute arising from these terms.
16.4 Assignment. You may not transfer these terms without our written consent. We may transfer them to a company that takes over the Service.
16.5 Entire agreement. These terms, with the AUP, are the whole agreement about the Developer Preview and replace any earlier discussion about it.
16.6 Severability and waiver. If a court finds a clause unenforceable, the rest still applies. A failure to enforce a clause is not a waiver of it.
16.7 No third-party rights. Nobody else may enforce these terms.
Annex A. Data Processing Addendum
A.1 Roles. For the data of your end users that the Service processes in your sandbox sessions, you are the controller and we are your processor. For your own account data, we are the controller, as the Sandbox Privacy Notice describes. This Annex applies to the first kind of data and forms part of these terms.
A.2 Subject matter, duration, nature and purpose. We read identity documents and run liveness checks for your sandbox sessions, so that you can develop and test your integration. We process for the term of these terms, until the deletion described in A.9.
A.3 Data and people. The data is identity document images and the fields read from them, and liveness outcomes. We keep no biometric template. The people are your end users.
A.4 Instructions. We process this data only on your documented instructions, which are your API calls to the Service, and as the law requires. If we think an instruction breaks the law, we will tell you.
A.5 Confidentiality. Our staff and anyone else who handles this data for us are bound by a duty of confidentiality. No staff screen shows session content.
A.6 Security. Data is encrypted at rest and in transit. Only the Service’s own service account can read session data. Operator access to the sandbox database is for emergencies only and is recorded. Our logs do not contain request or response content, and identifier-shaped values are removed from log records.
A.7 Sub-processors. You allow us to use Google Cloud (europe-west1, Belgium) and, in transit, Google Firebase Hosting for this data, as listed in the Sandbox Privacy Notice. We will tell you by email before we add or replace a sub-processor that touches this data. You may stop using the Service if you object. Each is bound by data protection terms at least as protective as this Annex (Google’s Cloud Data Processing Addendum).
A.8 Help with requests and breaches. We will help you answer requests from your end users to exercise their rights, as far as we can without identifying them, and we will tell you without undue delay after we become aware of a personal data breach affecting this data.
A.9 Deletion. Document images are never stored and are deleted when the request ends. Session results and extracted fields are deleted within 25 hours of the session’s creation. Audit entries hold only identifiers, event names and hashes and are kept for 30 days. We keep no copy to return to you; results are returned to you through the API when the session runs.
A.10 Audits. On written request we will answer reasonable questions and provide documentation showing that we comply with this Annex.
A.11 Transfers. We store and process this data in the EU; in transit it may pass through Google’s global network (A.7). Any other transfer follows section 8 of the Sandbox Privacy Notice.
Version details
- Version
- 1
- In effect from
- 15 Nov 2026
- Exact text
- Download the exact text (Markdown)
- SHA-256
- d47687bc73ec743f91beb3a5468ce1b61a0d7bd3b50b50dafe9c4c432f4a7596