Privacy · Waitlist
Clear about your data.
This notice explains how Ambra handles information submitted through the launch waitlist. It applies to this website and waitlist only; the future Ambra application will have its own privacy information.
- Controller
- Manlio Chite, trading as Ambra
- Based in
- United Kingdom
- Last updated
- 21 July 2026
01
Who is responsible
Manlio Chite, trading as Ambra, is the data controller for the waitlist information described here. Questions and privacy requests can be sent to manlio92--@live.it.
02
Information we collect
- The email address you enter.
- Consent details, including the notice version, form location, and date and time of signup.
- A keyed HMAC-SHA256 fingerprint derived from your IP address, together with the attempt time, for abuse prevention.
Ambra's application code does not save your raw IP address in its waitlist database. The server receives it long enough to create the one-way keyed fingerprint. Infrastructure providers may separately process ordinary connection logs to operate and secure their services.
03
Why we use it
Launch communications
We use your email to manage the waitlist and send Ambra launch, early-access, and closely related product updates. The lawful basis is your consent.
Service protection
We use the IP fingerprint to limit repeated submissions and protect the form. The lawful basis is our legitimate interest in preventing misuse and maintaining security.
Providing an email address is optional. If you do not provide one, you will not join the waitlist. We do not use waitlist data for solely automated decisions that have legal or similarly significant effects.
04
Storage and retention
- Waitlist emails and consent records are kept while the Ambra waitlist and early-access programme remain active. They are reviewed at least annually and deleted or anonymised within 90 days after that programme ends, unless you ask us to delete them sooner or a legal obligation requires longer retention.
- IP fingerprints are used for a 24-hour abuse-prevention window. Once older than 24 hours, they are deleted when the next valid signup attempt triggers database cleanup. If there are no new attempts, deletion may therefore occur later.
Waitlist records are stored in Supabase. Access is restricted to authorised server-side operations and is not available through the public or signed-in client roles.
05
Who receives the information
We use service providers acting on our instructions to operate the website and database, including Supabase for waitlist storage and the provider that hosts this website when it is deployed. We may also disclose information where required by law or to establish, exercise, or defend legal claims.
We do not sell waitlist information. If a provider processes information outside the UK, we will rely on an applicable legal transfer mechanism and appropriate safeguards.
06
Your choices and rights
Depending on the circumstances, UK data-protection law may give you rights to access, correct, erase, restrict, or receive your personal information, and to object to certain uses.
We may need to verify your identity before acting on a request. Withdrawing consent does not affect processing that was lawful before withdrawal.
07
Cookies and analytics
The waitlist page does not currently use advertising or analytics cookies. If analytics or other non-essential tracking is added, this notice and any required consent controls will be updated before that processing begins.
08
Questions and complaints
Please contact us first at manlio92--@live.itso we can try to resolve your concern. You also have the right to complain to the UK Information Commissioner's Office.
Visit the ICO complaints guidance09
Changes to this notice
We will update this page when our processing changes. If a change materially affects how we use existing waitlist data, we will bring it to your attention before the new use begins where required.