Canopy legal
Subprocessor Register
This register identifies providers that may receive customer or guest personal data when Canopy or an enabled integration uses them.
Effective July 28, 2026
How to read this register
“Optional” means the provider receives data only when the relevant feature is configured or used. A processing location describes the provider's expected operational footprint, not a promise that data remains only in that country.
| Entity | Purpose | Data categories | Country | Processing location | Effective |
|---|---|---|---|---|---|
| Vercel Inc. | Application and tenant-site hosting, request delivery, and deployment logs | IP address, request metadata, application content, and diagnostic logs | United States | Global edge network and provider operating locations | 2026-07-28 |
| Supabase, Inc. | Managed PostgreSQL database and object storage | Customer, staff, guest, booking, message, configuration, and uploaded-file data | United States | Configured project region and provider support locations | 2026-07-28 |
| Stripe, Inc. and Stripe Payments Canada, Ltd. | Subscription billing, connected-account onboarding, guest payments, and fraud prevention | Operator and guest identity/contact data, payment details collected by Stripe, transaction and booking metadata | United States (Stripe, Inc.); Canada (Stripe Payments Canada, Ltd.) | Canada, the United States, and other provider processing locations | 2026-07-28 |
| Resend, Inc. | Transactional and authorized marketing email delivery | Recipient and sender addresses, subject, message body, attachments, and delivery metadata | United States | Provider infrastructure and support locations | 2026-07-28 |
| Twilio Inc.Optional | Optional SMS, MMS, and WhatsApp communications | Telephone numbers, message bodies, media links, and delivery metadata | United States | Provider-selected regional and support locations | 2026-07-28 |
| Anthropic, PBCOptional | Optional cloud AI generation for operator, site, and guest workflows | Prompts and responses that may include guest or operator names, messages, property context, and booking metadata; Anthropic retains API inputs and outputs for approximately 30 days by default, subject to its stated exceptions | United States | United States and other provider processing locations | 2026-07-28 |
| Inngest, Inc. | Background workflow execution and scheduled jobs | Organization, booking, and conversation identifiers, workflow payloads, and limited contact/content data required by a job | United States | Provider infrastructure and support locations | 2026-07-28 |
| OpenPanel ABOptional | Cookieless product and website analytics for Fernwood/Tenant Zero | Page and event data, browser/device attributes, and transient network data used for coarse location and a rotating identifier | Sweden | Cloud analytics data hosted in Germany; European Union provider operations | 2026-07-28 |
| Functional Software, Inc. (Sentry)Optional | Optional error, crash, and performance diagnostics | Error messages, stack traces, request and device context, and diagnostic metadata after configured scrubbing | United States | United States or configured provider data region and support locations | 2026-07-28 |
| Seam Labs, Inc.Optional | Optional smart-lock and thermostat integration | Device identifiers, access-code labels and values, validity windows, and related booking references | United States | United States and other provider processing locations | 2026-07-28 |
Change notice
Canopy will post changes here and email the administrative or billing contact at least 30 days before a material new subprocessor begins processing Customer Personal Data, except for an urgent replacement needed for security or continuity. To object on reasonable data-protection grounds, contact hello@hostwithcanopy.com within 15 days of notice.