Subprocessors
Last updated: July 2026
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: planners, weddings, couples, vendors, timelines, documents — in transit and at rest | US (`iad` / Ashburn, VA) | Chosen production host; US-domiciled Delaware C-corp. Per-tenant + per-wedding row-level isolation. |
| Anthropic, PBC | LLM inference for venue-dossier generation, vendor-outreach drafting | Wedding metadata (date, location, vibe, budget), vendor metadata; zero-retention config | US | Couple PII is excluded from LLM prompts to the maximum extent practical. |
| Stripe, Inc. | Subscription + onboarding-fee billing | Planner billing data | US | Couples do not pay through Stripe — planners are our customers. |
| Resend Inc. | Transactional email for planners and couple portals | Email recipient + content | US | Couple-facing emails are branded with the planner's logo and reply-to address. |
| Cloudflare, Inc. | Edge, DDoS, WAF | Network metadata | US | — |
| Google LLC (Workspace) | Our internal business email | Our internal email only | US | — |
| Venue/inventory data provider, TBD | Venue location data, regional inventory monitoring | Public venue information enriched with our cached research | US | Added when implementation finalized. |
Subprocessors NOT used. No third-party advertising pixel, no Meta / Google ad-tracking on couple-facing portals, no SMS provider in v1 (text notifications are roadmap, not launch).
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 LLC
Attn: Privacy & Security — Peony & Lace
Email: [email protected]
Related: Privacy Policy · Terms. This list is referenced by, and generated in accordance with, our Data Processing Addendum. Peony & Lace is software, not a wedding-planning service.