Service providers

Vercel · primary website

Vercel hosts embiro.ai and www.embiro.ai. It handles page and asset requests and their technical metadata. Waitlist form requests pass through the website’s server route before being forwarded to our designated Sites backend using a signed request.

Vercel infrastructure is international. Website deployment locations do not establish the residence of all data, logs, support access or backups. See vercel.com/legal/privacy-policy.

OpenAI Sites · website platform

OpenAI Sites provides the original hosted version of the website and the managed environment through which the waitlist backend is deployed. The hosted version shares the waitlist flow with the primary domain.

Using OpenAI Sites for hosting does not mean the waitlist calls an OpenAI model. The current form flow does not submit your answers to a model. Platform handling of hosting and account information is governed by its applicable terms and privacy information at openai.com/policies/privacy-policy.

Cloudflare · backend and storage

The Sites deployment runs on Cloudflare Workers and uses a Cloudflare D1 database for waitlist entries, optional questionnaire answers, consent-version records, hashed abuse counters and notification queue snapshots.

These records support form processing, duplicate prevention and email retries. The current application does not establish an Africa-only storage commitment. See cloudflare.com/privacypolicy.

Resend · email delivery

Resend delivers welcome confirmations, internal signup/questionnaire alerts and requested Platform sign-in codes. It receives sender and recipient details, message content and delivery metadata. Internal waitlist alerts go to collins@embiro.ai and include submitted details.

Messages use the verified mail.embiro.ai domain: waitlist@mail.embiro.ai for the waitlist and signin@mail.embiro.ai for authentication. Replies go to collins@embiro.ai, or to the applicant for internal signup alerts. See resend.com/legal/privacy-policy.

Operator correspondence and links

Authorised Embiro operators receive waitlist notifications and any replies in their work mailbox. Email necessarily passes through sender and recipient mail systems. Keep sensitive information out of ordinary email and request a suitable transfer method if needed.

Publisher sites, GitHub, booking services and other destinations you choose to visit process your information under their own policies. A link or a publisher logo is not evidence that we send your waitlist data to that publisher.

Location, contracts and future changes

Provider roles and technical arrangements can change. This list describes the current application and does not make promises about a provider’s independently controlled retention or access practices. Contact us for questions about a specific data flow.

Before accepting production customer workloads, we will publish the relevant service-specific provider list, processing locations, contractual data-processing arrangements, retention controls and change process. A signed data-processing agreement, service-level agreement or model licence is not created by this page.

AWS · Cape Town pilot

AWS Cape Town hosts the pilot control service, PostgreSQL account database and enabled inference backend. Authentication and the API control service are separate from GPU inference capacity. Pilot availability is limited; no high-availability or uptime guarantee is implied. Website hosting and email delivery remain separate dependencies.