The current application has no advertising cookies or dedicated behavioural analytics integration. Hosting services can still handle technical information.
What these technologies do
Cookies are small values a website or supporting provider stores through your browser. Local storage stays within a browser profile until cleared; unlike a cookie, it is not automatically sent with every request. Temporary JavaScript state disappears when a page is reloaded or closed.
Ordinary page, font, image and API requests still reach the relevant host. Blocking cookies alone does not prevent all network logging.
Motion preference
Key: labs-motion. Type: first-party local storage. Purpose: remember whether you paused decorative motion. Values: paused or on. It is written when you change the motion control, has no automatic expiry, and remains until you clear site data or change the preference.
Your operating system’s reduced-motion preference is also respected. Reading that setting does not create an advertising profile.
Platform sign-in cookies
Platform uses Better Auth essential session cookies (including __Secure-better-auth.session_token on HTTPS) to identify your session. Sessions last up to 24 hours and can be renewed while active. The server checks the database-backed session; a cookie alone is not proof of access. Passkey ceremonies may use short-lived authentication state.
Signing out ends your session. Clearing site cookies signs you out in that browser. The previous embiro-console-demo-v1 local-storage record, if present from an earlier demo, is no longer used by Platform and can be removed through browser site-data settings. Platform does not store full application keys in localStorage.
Forms, preferences and signature generation
Waitlist form values and the optional one-use questionnaire token are held in page memory during that flow. Submitted information is sent to the waitlist backend as described in the Privacy notice. The token expires after one hour. We do not store the raw questionnaire token in local storage.
The signature generator holds entered details in page memory and creates files or clipboard content only when you request them. Downloaded files, copied signatures and values retained by your browser’s autofill are outside this page-memory lifecycle. Model filters and other page controls may be held in memory or in the page URL.
Hosting, security and email requests
Vercel, Cloudflare and OpenAI Sites may process network addresses, user agents, request metadata and necessary access or security cookies depending on the host and access method. We do not assign a single expiry to provider-managed cookies because their configuration and purpose can differ. Their current notices are linked from Service providers.
Branded emails reference images hosted on embiro.ai. Your email client or its image proxy requests these images when it loads them. You may block remote images in your email application; the message text remains available. We do not embed our own tracking pixel in the email templates.
Control and removal
You can remove first-party storage through your browser’s site-data controls for embiro.ai, www.embiro.ai and the Sites domain separately. Removing the motion key resets that preference. Removing or blocking session cookies prevents Platform sign-in but does not prevent reading public pages.
There is no optional advertising or analytics category to enable in the current site, so we do not show a pretend consent banner. If we introduce optional tracking, we will update this inventory and obtain any required consent before activating it.
A real person, a real address.
Embiro Labs4 Norfolk Gardens, Kyambogo
Kampala, Uganda
collins@embiro.ai