# Bawarii Sandbox Privacy Notice

Version: 1.

## 1. Who we are

1.1 TEKNOSPARC LTD is the controller of the personal data described in this notice. We are a company registered in England and Wales, company number 14615978.

1.2 Bawarii is the name of our product. In this notice, "we" and "us" mean TEKNOSPARC LTD. Contact us at developers@bawarii.com.

1.3 This notice covers the developer portal at developer.bawarii.com and the sandbox API at sandbox.api.bawarii.com. It does not cover our production services. Registration and your application (including your phone number and job role) are covered by the Registration Privacy Notice and its retention periods; this notice covers the sandbox and your approved account only. It also explains what we do, as your processor, with the data of your end users that your sandbox sessions process (sections 3 and 10).

## 2. Where your data is

2.1 Sandbox data and your account details are stored in the EU, in Google Cloud's europe-west1 region (Belgium). We use two separate Google Cloud projects: one for your account (the control plane) and one for the sandbox.

2.2 Your sign-in record (email, password hash, authenticator) is processed by Google in the United States. Section 8 explains how that transfer is protected.

## 3. What happens in the sandbox

3.1 **Testing only.** The sandbox is for testing only. Its results are not identity decisions. You may submit only data you are entitled to process (Acceptable Use Policy).

3.2 **Your end users' data.** For the document images, extracted fields and liveness outcomes in your sessions, you are the controller and we are your processor (Annex A of the Terms). We process this data only on your instructions, which are your API calls. Your own privacy notice must tell your end users about it.

3.3 **How long we keep it.** 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.

3.4 **Selfies.** Selfies and liveness frames stay on the user's device; we receive only the liveness outcome. Any face vector sent to the sandbox is discarded unread. The sandbox does not perform face matching and keeps no biometric template.

3.5 **No training.** We never use sandbox data to train or evaluate any model, and sandbox data is excluded from every export.

3.6 **No request bodies in logs.** Our server logs never contain the content of requests or responses.

## 4. Your developer account data

4.1 We collect this data from you when you sign up, apply and use the console. Staff decisions and logs are created by us.

| Data | Purpose | How long we keep it |
|---|---|---|
| Sign-in record: account ID, work email, password hash, authenticator enrolment state | Signing you in; securing your account | Until you delete your account. |
| Sign-up and password-reset records: email, single-use token hash, expiry; per-address counters | Confirming you control the inbox; preventing abuse | Sign-up links: 24 hours. Reset links: 1 hour. Counters: 1 to 2 days. A hashed record of an address sent a "someone tried to sign up" notice: 7 days. |
| Terms acceptance: account ID, organisation, document versions and their fingerprints, time, when you signed in, the authenticator your session was signed in with | Proving which terms you accepted | For the life of the account plus six years |
| Account activity log: sign-ins, password and authenticator changes, sign-outs of all devices, terms accepted, application events | Account security; showing you your activity | 12 months |
| Sandbox activity log: key created, renamed or revoked, file downloads, authenticator mismatch, leaving the sandbox. Entries hold key IDs, the last 4 characters, hash prefixes, and for a model download made by the SDK the session ID and the file's digest, never a full key | Account security; showing you your activity | 12 months |
| Staff decision log: approval, refusal and removal decisions, the reviewer's email, reason category, any note shared with you, and records of staff viewing your application | Accountability for staff decisions | 12 months, including after account deletion |
| API key records: key ID, name you chose, last 4 characters, a keyed hash, creation, expiry and last-used times | Authenticating your requests | While active; then 90 days after the key is revoked or expires |
| Background task records: task type, account and organisation IDs, times, state | Making sure access changes and deletions complete | 30 days after the task closes |
| Server logs: time, path, status code, network address | Security and fault-finding | 30 days |
| Emails we send you: address, message type, delivery and bounce status | Account and security emails | Bounce and complaint status: with your account. Our email provider keeps its own log of each email for one month |

4.2 **Network address in server logs.** Our hosting front does not pass us your own address reliably. The network address we record may belong to our hosting provider's network rather than to you.

4.3 We use your data for marketing only if you opted in, as the Registration Privacy Notice describes, and we do not sell it.

## 5. Legal bases

5.1 We rely on:
- **Contract** (GDPR Article 6(1)(b)) for your account, application, keys and account emails;
- **Legitimate interests** (Article 6(1)(f)) for security logs, activity logs, the staff decision log, bot protection on sign-up, abuse prevention and the terms acceptance record. Our interest is keeping the Service secure, accountable and free from abuse. You can object (section 9);
- **Legal obligation** (Article 6(1)(c)) where a law requires us to keep or disclose data.

5.2 Approval decisions are made by people, not solely by automated means. Sign-up automatically refuses free email domains; you can contact us if you think this is wrong.

## 6. Deleting your account

6.1 You can request deletion of your account from your Account page or at developers@bawarii.com. We complete it within one month. Deletion revokes your keys, then deletes your sandbox data and your account.

6.2 Once deletion starts, we remove your account records from the sandbox within 7 days at most. Usually it takes seconds.

6.3 The records in section 4 marked as kept after deletion are kept for the period shown, then deleted.

## 7. Who receives your data

7.1 We use these service providers. Each acts on our instructions.

| Provider | What it does | Where |
|---|---|---|
| Google Cloud (Firestore, Cloud Run, Secret Manager, Cloud Tasks, Cloud Scheduler, Cloud Logging, Artifact Registry) | Hosting, storage and processing | EU (europe-west1) |
| Google Identity Platform | Sign-in, password and authenticator | United States |
| Google Firebase Hosting | Serves the portal and routes API traffic | Google's global network |
| Google reCAPTCHA Enterprise | Bot protection on the sign-up pages only | Google's global network, which may include the United States |
| Brevo | Sends our emails to you; tells us about permanent bounces and spam reports; keeps a log of each email for one month | European Union (France, Germany and Belgium) |
| Amazon Web Services (Amazon SES and Amazon SNS) | Standby email provider: would send our emails and report permanent bounces and spam reports if we switched to it | Sweden (Stockholm, eu-north-1) |
| IONOS | Hosts our bawarii.com mailboxes, so it processes any email you send us | We are confirming the location and will state it in the next version |
| Cloudflare | DNS for bawarii.com addresses (DNS only; it does not see portal or API traffic) | Cloudflare's global network |

7.2 We may disclose data if the law requires it, to protect people or the Service, or to a company that takes over the Service.

## 8. International transfers

8.1 Your sign-in record is processed by Google in the United States. That transfer relies on Google's standard contractual clauses and, where applicable, the EU-US Data Privacy Framework.

8.2 Google relies on the safeguards in 8.1. For any other transfer outside the EU, you can ask us which safeguards apply.

## 9. Your rights

9.1 You can ask us to give you a copy of your data, correct it, delete it, restrict its use, or send it to you in a portable format. You can object to processing based on legitimate interests.

9.2 Some of these are self-service in the console: your activity and your terms record. You request account deletion from your Account page.

9.3 Email developers@bawarii.com. We reply within one month. We may need to confirm your identity first.

9.4 You can complain to the UK Information Commissioner's Office (ico.org.uk), or to the data protection authority in the country where you live or work.

## 10. If your document was processed through a developer's app

If your document or photo was processed in the sandbox through a developer's app, that developer is the controller of your data and we act on the developer's instructions. Please contact the developer first; their own privacy notice explains how they use your data. We never store the images. We delete the results within 25 hours of the session's creation and keep only a hash of the image and session identifiers for 30 days, so we usually cannot tell whose data a session holds. You can write to developers@bawarii.com and we will pass your request to the developer where we can.

## 11. Cookies and storage in your browser

11.1 The portal uses no analytics, advertising or tracking, and sets no cookies of its own.

11.2 In your browser:
- session storage keeps your sign-in session, which belongs to the one browser tab and ends when you close it, the page to return to after sign-in, and which step of the sandbox application you were on;
- local storage keeps three items only: the time of your last activity, a short notice code shown once after sign-in, and whether you collapsed the Developer Preview banner;
- IndexedDB keeps only a small store that Google's Firebase code uses for its own heartbeat (software versions and dates). It holds no sign-in state.

11.3 The sign-up pages load Google reCAPTCHA, which may store data in your browser.

## 12. Changes to this notice

We will publish each new version at a stable address with a "What changed" summary, keep earlier versions available, and tell you by email. You will be asked to confirm that you have read it before key operations.

