Subprocessors
Emboss relies on the categories of provider below to run the API, store documents, process payments, and send email. This page does not name individual companies; see the security page for how documents are handled overall.
| Category | What it does | Region |
|---|---|---|
| Hosting and database for the API | Runs the API and stores the forms, sessions, receipts and usage records | United States |
| Object storage and DNS | Holds uploaded and generated documents at rest; resolves the domains; bot checks on signup and password reset | United States |
| Model routing | Routes model calls to the model provider below | United States |
| Model inference | Field detection and context fills on the pages and documents a job sends, and reading plain-language requests sent to the A2A agent and planning requests that ask for several jobs | United States |
| Value check model | Judges whether a filled value fits its box and settles competing values found in your documents, and decides which job a plain-language request sent to the A2A agent asks for | Region to be confirmed |
| Card payments | Card payments: invoices for account holders, and card payments on the pay-per-call API | United States |
| Stablecoin payment rails | Settlement for the pay-per-call API | United States |
| Transactional email | Signup, reset, receipts and notifications | United States |
| Product analytics | Usage events for the website and the API | United States |
| Advertising measurement | Attributes website signups to our ads, while we run ad campaigns | United States |
| Website hosting | Serves getemboss.ai | United States |
| Error reporting | Stack traces from the API and the website, with each request's method and path only; no request bodies, headers, query strings or IP addresses | United States |
| Fax transmission | Transmits a document you ask us to fax to the number you give, over the telephone network; receives the document from a short-lived link and reports delivery back | United States |