Subprocessors
Last updated: July 2026
Ellis Intelligence LLC, a Colorado limited liability company, operates Reply Engine as a d/b/a; Reply Engine is not a separate legal entity. This page describes the Subprocessors used specifically by the Reply Engine Service.
Update cadence & your objection right
We review this list quarterly. Before we engage a new Subprocessor, we specifically inform affected customers in writing — by email to the account's designated contacts, or by in-product notice — with notice deemed given when sent, and we post the change here in addition to (not instead of) that written notice. Customers have 30 days from the date notice is given to object on reasonable data-protection grounds; a timely objection suspends our use of the new Subprocessor for that customer pending resolution, per DPA §5.3.
Current Subprocessors
| Subprocessor | Purpose | Data accessed | Region | Notes |
|---|---|---|---|---|
| Fly.io, Inc. | Production application hosting + database (Fly Volume holds the SQLite file) | Tenant data: questionnaires uploaded, answers generated, user accounts, organization membership — in transit and at rest | US (`iad` / Ashburn, VA) | Chosen production host; US-domiciled Delaware C-corp. App migrates to Fly.io before public launch; per-tenant row-level isolation. |
| Anthropic, PBC | LLM inference for answer generation | Questionnaire content + tenant security-posture documents passed to the API; zero-retention config | US | Posture documents are tenant-scoped, sent per-request only. |
| Pinecone (or self-managed FAISS) | Vector index for tenant security-posture documents | Embeddings derived from tenant content; embedding vectors only, not source text | US | DPA required at engagement; may switch to self-hosted FAISS. |
| Stripe, Inc. | Subscription billing | Billing contact, tokenized payment method, invoice metadata | US | — |
| Resend Inc. | Transactional email (signups, password resets, billing receipts, approval-workflow notifications) | Email recipient + message content | US | — |
| Slack Technologies, LLC customer-provided | Notifications pushed to the customer's own Slack workspace | Only the notification content the customer configured | US | Customer's own Slack DPA governs Slack-side handling. |
| Cloudflare, Inc. | Edge/DNS, DDoS protection, WAF, tunnels | Network metadata, request logs | US (global edge POPs) | — |
| Google LLC (Workspace) | Our internal business email | Our internal email only — not customer-product data | US | — |
Data Residency
All Subprocessors above maintain Customer Data at rest in the United States under our current configuration. Cloudflare and Anthropic operate global edge infrastructure for delivery, but data at rest stays U.S.-only under our contracts. Production hosting is Fly.io, Inc. (a U.S./Delaware company), deployed to its U.S. region (`iad` / Ashburn, VA); continuous backups stream to Cloudflare R2 (also a U.S. vendor).
Customers Outside the United States
We do not currently market to or onboard customers in jurisdictions that prohibit U.S. data processing under their data-protection law. Customers in the EU/EEA, UK, or Switzerland may onboard subject to the Standard Contractual Clauses ("SCCs") incorporated by reference into our DPA (together with the UK Addendum, for UK transfers).
Audit Rights
You may request a summary of our subprocessor-management practices, and our most recent SOC 2 report (Type I or Type II, as available), by emailing [email protected]. We do not permit direct audit of our Subprocessors; we share their relevant audit reports under NDA.
Contact Us
Ellis Intelligence LLCAttn: Privacy & Security — Reply Engine
Email: [email protected]
Related: Privacy Policy · Terms. This list is referenced by, and generated in accordance with, our Data Processing Addendum.