Beta terms for invited testers. This beta list of sub-processors applies to free use of the Ordainer beta by people we've invited. Paid plans and live keys aren't offered during the beta. Version: Beta preview 2026-10-09. Last updated: October 9, 2026. If we publish a new version, we'll email you before it applies to you.
Ordainer Sub-processors
Version: Beta preview 2026-10-09. Last updated: October 9, 2026.
This page lists the third parties that Ordainer ("we", "us"), a business based in Ottawa, Ontario, Canada, uses to provide the Ordainer service, what each does, what data it handles, and where.
During the beta, the service runs on our beta environment, hosted by Render and Neon in the United States (Ohio region).
Sub-processors that process Customer Personal Data
These providers process personal information in the data you send us as our customer (for example End Customer records, Agent Key metadata and Decision Records). We act as your processor for that data under our Data Processing Addendum (https://ordainer.ai/legal/dpa, Annex 3).
| Sub-processor | What it does | Data involved | Location |
|---|---|---|---|
| Render | Hosts the application, API and console | All Customer Data passes through it in transit; application logs | United States (Ohio region) |
| Neon | Hosts the database | All Customer Data is stored here | United States (Ohio region) |
| Microsoft (Microsoft 365) | Email hosting for support@ordainer.ai and our team mailboxes | Support emails only: the contact details and message content of people who email us, and our replies. We don't send End Customer data to it on purpose, but a support email may contain whatever the sender includes (for example a decision row or an End Customer ID) | United States or Canada (Microsoft 365 data region for our GoDaddy-provisioned account; not yet verified in our admin tools — we'll update this page when we confirm which) |
| Cursor (Anysphere, Inc.) | Runs the AI assistant and cloud computer that help draft and send replies to support emails. It uses AI model providers of its own to do this | Support emails only: the contact details and message content of people who email support@ordainer.ai, and our replies. We don't send End Customer data to it on purpose, but a support email may contain whatever the sender includes (for example a decision row or an End Customer ID) | United States |
Render uses Cloudflare (United States) for its network edge; see Render's sub-processor list at https://render.com/security. Render and Cloudflare record client IP addresses in their own platform request logs.
Render and Neon also host the account data described in our Privacy Policy (https://ordainer.ai/legal/privacy, section 6.2). Microsoft and Cursor handle support emails, which are mostly account data under that policy (sections 3.4 and 6.2).
Planned, not yet in use
| Provider | What it would do | Status |
|---|---|---|
| Backblaze | Daily encrypted off-site backup of our database, in Canada | Planned, not yet in use |
We plan to add a daily encrypted off-site backup with Backblaze in Canada; it isn't in use yet, and we'll update this page before it starts. Until then, there is no off-site backup copy; our database host (Neon) keeps 7-day point-in-time recovery history.
Providers that do not receive Customer Personal Data
These providers handle account data, such as account owner and staff email addresses and billing details. We act as controller for that data under our Privacy Policy. They receive no End Customer data.
| Provider | What it does | Data involved | Location |
|---|---|---|---|
| Stripe | Payments and subscriptions | Account owner email, organisation name, billing details | Stripe is used only for paid plans and the test checkout; no payments are taken during the beta |
| Resend | Email delivery | Customers' staff email addresses, as Account Data, for sign-in links (sent from login@ordainer.ai), billing and payment-failed notices, sandbox nudges and the account-deleted notice. We handle this as controller under our Privacy Policy. Our internal alerts to our own team also carry org IDs and Stripe subscription IDs. No End Customer data: no End Customer name, email, ID or key label | United States |
Stripe also processes payment information for its own purposes, such as fraud prevention and meeting financial regulations, under its own privacy policy (Privacy Policy section 6.3).
How we tell you about changes
We tell you about any new or replacement sub-processor at least 30 days before it starts processing Customer Personal Data, or, for changes made by our providers' own sub-processors, as soon as we reasonably can after we are told. We do that by email to your account owner's email address and by updating this page, including the "Last updated" date above and the change history below (DPA section 7.3). A change to this list does not require you to accept our Terms or DPA again. You may object on reasonable data protection grounds by emailing support@ordainer.ai with "Privacy" in the subject within that notice period. We will discuss the concern in good faith. If we can't resolve it, you may cancel your subscription with effect before the change, and we will refund any prepaid fees for the period after cancellation (DPA section 7.4). If we must replace a sub-processor urgently, we tell you as soon as we can, and you can still object (DPA section 7.5).
Change history
| Date | Change |
|---|---|
| October 6, 2026 | Beta preview list published: Render, Neon, Microsoft (Microsoft 365, support email) and Cursor (AI assistant for support replies) (sub-processors); Stripe and Resend (account-data providers). Backblaze off-site backup listed as planned, not yet in use. |
| October 9, 2026 | Beta preview 2026-10-09 (replaces 2026-10-06): no change to the providers listed. Operator wording updated and links moved to ordainer.ai. |
Questions about these terms? Email support@ordainer.ai