Skip to content

Bawarii Developers Portal Registration Privacy Notice

Version 2 · In effect from 26 Oct 2026

This is an earlier version. Version 2 was in effect from 26 Oct 2026 until 28 Oct 2026. Read the current version (version 3).
What changed in version 2
  • When you apply, we now also ask for your phone number and your job role (sections 3.2, 4.1 and 6.3).
  • You can choose to let us email or call you about Bawarii products and updates. It is optional, you can withdraw at any time, and we keep your choice only while your account exists (sections 3.2, 4.1 and 6.3).
  • Sections 3.3, 4.2 and 4.4 are updated to match that choice.
  • The title now says "Bawarii Developers Portal", the name the portal uses from this version on.

Interim — pending counsel review. This notice covers registration only. A full privacy policy, reviewed by our legal advisers, replaces it before sandbox access opens.

Version 2. Dated 26 October 2026. Effective from the date shown on the Apply form.

What changed in version 2

  • 3.2: when you apply, we now also ask for your phone number and your job role.
  • 4.1: why we use your phone number and job role, and on what basis.
  • 6.3: your phone number and job role are kept and deleted with your application.
  • 3.2, 4.1 and 6.3: you can choose to let us email or call you about Bawarii products and updates. It is optional, you can withdraw at any time, and we keep your choice only while your account exists.
  • 3.3, 4.2 and 4.4: updated to match that choice.
  • The title now says “Bawarii Developers Portal”, the name the portal uses from this version on.
  • Nothing else has changed.

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.

1.3 Our data protection contact is contact@bawarii.com. We have not appointed a data protection officer. For help with your account, write to developers@bawarii.com.

2. What this notice covers

2.1 This notice covers the Bawarii developer portal at developer.bawarii.com: creating an account, signing in, applying for sandbox access, and managing or deleting your account.

2.2 It does not cover use of the sandbox, which is not open to new applicants yet, or any other Bawarii service.

3. What we collect

3.1 When you create an account:

  • your work email address;
  • your password. It is sent over an encrypted connection to our server, which passes it to Google Identity Platform to create your account. We do not store it. Google keeps only a hashed form of it;
  • your authenticator. When you add an authenticator app, Google Identity Platform holds its secret. We record only that you added one and when;
  • the times your account was created and last signed in, which Google Identity Platform keeps with your sign-in record.

3.2 When you apply: your organisation’s name, its website (optional), its country, its category (and your description if you choose “Other”), what you intend to use Bawarii for, and your phone number and your job role (and, if you choose “Other”, the role you type). We also record whether you agreed to marketing contact, the version of the wording you saw, and when you made or changed that choice, including on your Account page later. Please do not include personal details about other people, such as the people you plan to verify.

3.3 Records we create:

  • Sign-up links. Your email address and a coded (hashed) form of the single-use link we email you, so we can confirm the inbox is yours.
  • Password reset links. Your account ID, your email address and a coded form of the single-use link.
  • Limits on attempts and emails. Counts of sign-up attempts and emails for an email address or an email domain on a given day. We store the address or domain only in a coded (keyed hash) form.
  • “Someone tried to sign up” notices. If someone tries to create an account with an address that already has one, we email that address to tell its owner, and keep a coded form of the address so we send that notice no more than once a week.
  • Email delivery. If an email to you bounces permanently or is reported as spam, we keep a coded form of your address so we stop sending to it.
  • Account audit entries. A short record of events on your account: account created, authenticator added, first draft saved, application submitted, marketing contact choice changed, password reset, and account deleted or removed. Each entry holds the event, your account ID, your organisation ID, the time and, where relevant, the version of this notice shown to you, or your marketing contact choice and the version of its wording. It holds no email address, no IP address and no browser details.
  • The version of this notice shown to you when you created your account and when you submitted your application.

3.4 What we do not record ourselves. We do not store your IP address or details of your browser in any of the records above. Our service providers record some technical data to run their services:

  • Google Cloud keeps standard request logs for our servers. They show the time, the address requested and the response, and may show the network address and browser type that reached Google’s servers. Our site is delivered through Google’s network, so that network address is usually Google’s, not yours.
  • Google reCAPTCHA Enterprise, on the two sign-up pages only, looks at information about your browser and device and at how you use the page, to tell people from automated programs. It may store data in your browser. We treat this as strictly necessary to keep sign-up secure.
  • Brevo, our email provider, processes your email address and our message to deliver the emails we send you, and tells us if a message bounced permanently or was reported as spam. It keeps a log of each email (your address, the subject and delivery events) for one month. Amazon Web Services is our standby email provider and would do the same if we switched to it.

3.5 In your browser. Your browser keeps your sign-in session and the time of your last activity, so that we can sign you out after a period of inactivity. We set no cookies of our own, and we use no analytics or advertising tools.

4. Why we use it, and our lawful basis

4.1 We use your details under the UK GDPR and, where it applies, the EU GDPR, on these bases:

  • Steps you ask us to take before an agreement (Article 6(1)(b)). We use your email address, password, authenticator and application to create your account, sign you in, send you emails about your account, and assess your application. We use your job role, like the rest of your application, to assess your application. We use your phone number to contact you about your application and your account, and for marketing calls only if you agree to them (below). We do not use your job role for marketing, we do not share either with anyone else, and we do not give them to our email providers.
  • Your consent (Article 6(1)(a)). If you tick the marketing box when you apply, or agree on your Account page later, we may email you or call you, at the email address and phone number you gave us, about Bawarii products and updates. It is optional: your application and your account do not depend on it. You can withdraw your consent at any time on your Account page, or by writing to developers@bawarii.com. Withdrawing does not affect the emails we send about your application and your account, or the lawfulness of contact before you withdrew.
  • Legitimate interests (Article 6(1)(f)). We use the bot check, the limits on attempts and emails, the coded records in 3.3, the account audit entries and the request logs to keep sign-up and your account secure. Our interest is protecting the service and the people who use it from automated sign-ups, abuse and misuse of accounts, and being able to show what happened on an account. You can object to this use (section 7).

4.2 We ask for your consent only for marketing contact (4.1), and it is optional. There is nothing else to accept when you register. This notice is shown to you so you know how your details are used.

4.3 Sign-up automatically refuses addresses from personal and disposable email providers, and the bot check may refuse a sign-up attempt. No other decision about you is made automatically. If you think a refusal is wrong, write to developers@bawarii.com.

4.4 We use your details for marketing only if you agree to it (4.1), and we do not sell them.

5. Who processes your details, and where

5.1 Your account details and application are stored in the EU. Your sign-in record (email, password hash, authenticator) is processed by Google in the United States.

5.2 These service providers process your details on our instructions:

Provider What it does Where
Google Cloud (Firestore, Cloud Run, Cloud Logging) Stores your account details, application and the records in 3.3; runs our servers; keeps request logs Belgium (europe-west1)
Google Identity Platform Holds your sign-in record: email address, password hash, authenticator, sign-in times United States
Google Firebase Hosting Delivers the website and passes your requests to our servers Google’s global network
Google reCAPTCHA Enterprise Bot check on the two 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

5.3 Some of this processing happens outside the UK and the European Economic Area, mainly in the United States: your sign-in record always is, and parts of website delivery and the bot check may be. For these transfers Google relies on Google’s standard contractual clauses and, where applicable, the EU-US Data Privacy Framework. This point is part of the legal review named at the top of this notice. You can ask us for a copy of the safeguards.

5.4 Within our company, only the people who review applications can read your application. Browsers and apps cannot read or write our database directly; only our servers can.

5.5 We do not share your details with anyone else, unless the law requires us to.

6. How long we keep it

6.1 We delete records automatically when the periods below end. Deletion runs throughout the day, so a record is removed shortly after its period ends.

Record How long we keep it
Sign-up link 24 hours
Password reset link 1 hour
Limits on attempts and emails, and “someone tried to sign up” records 1 to 7 days
An account with no authenticator Deleted 7 days after it was created
An account with an authenticator but no submitted application Deleted 90 days after it was created, or 90 days after you last saved a draft application, whichever is later
A submitted application with no decision Your account and application are deleted 12 months after you submitted it
Your account, organisation and application in any other case Until you delete your account
Account audit entries Each entry is kept for 12 months, then deleted. This continues after your account is deleted
Record that an email to you bounced permanently or was reported as spam As long as we need it to stop sending to that address, and no more than 12 months
Google Cloud request logs 30 days
Emails about a request to use your rights 12 months after we complete the request, then deleted

6.2 Deleting your account. You can delete your account at any time from the Your account page. Unless you signed in very recently, we first ask you to confirm your password and your authenticator. This deletes your sign-in record, your organisation and your application straight away. The other records in the table, such as account audit entries, are kept only for their own periods.

6.3 Your phone number and job role are part of your application. They are kept and deleted with it, under the application rows in the table in 6.1, and when you delete your account (6.2). We do not copy them into any other record in this notice. Your marketing contact choice is kept while your account exists, or until you withdraw it: after you withdraw, we keep only the fact that you withdrew and when, so that we do not contact you. It is deleted with your account.

7. Your rights

7.1 You have the right to:

  • get a copy of your details (access);
  • have wrong details corrected (rectification);
  • have your details deleted (erasure);
  • ask us to limit how we use your details (restriction);
  • object to our use of your details for security under legitimate interests (objection);
  • receive the details you gave us in a format a computer can read, where this right applies (portability).

7.2 How to use them. You can delete your account yourself from the Your account page, which also shows your email address and when you added your authenticator. For anything else, or if you cannot sign in, write to contact@bawarii.com from the address on your account. We reply within one month. We may ask you to confirm the request from that address before we act on it.

7.3 Complaints. 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.

8. Children

8.1 The developer portal is for adults acting for an organisation. Do not create an account if you are under 18.

9. Changes to this notice

9.1 This is version 2, dated 26 October 2026. What changed from version 1 is listed at the top of this notice. Each version is published at its own address, and earlier versions stay available.

9.2 We record which version was shown to you when you created your account and when you submitted your application.

9.3 If we change how we use details you have already given us, we will tell you by email before the change applies.

Earlier versions

Version details

Version
2
In effect from
26 Oct 2026
Exact text
Download the exact text (Markdown)
SHA-256
01e021631724813acde754d39202c33a2ac430bc106b44abea2d372dd506bccb