Last Updated: October 29, 2026
RSVPify Inc. uses the following third-party sub-processors to deliver its Services. All sub-processors are contractually bound to process personal data only as directed by RSVPify and in accordance with applicable data protection laws.
This list applies to all RSVPify customers globally. EU and UK customers subject to GDPR or UK GDPR should also refer to the Data Processing Agreement (DPA), which governs sub-processor engagement for those jurisdictions.
For transparency, the sub-processors below are grouped into three categories: core platform services that run RSVPify for every account, platform and email security, and the optional RSVPify Cue AI features that an administrator can choose to turn on. Artificial intelligence is used only where noted in the second and third categories.
Standard operational services used to run RSVPify for every account, including hosting, payments, email delivery, customer support, analytics, and advertising. These services are separate from RSVPify’s AI functionality.
| Sub-Processor | Purpose | Location | Privacy Policy |
|---|---|---|---|
| Amazon Web Services (AWS) | Web hosting, data storage, and infrastructure security | USA | aws.amazon.com/privacy |
| Cloudflare | Content delivery, network security, and transmission of platform traffic, including personal data in transit. Cloudflare may also be used for backup media storage. Cloudflare additionally provides infrastructure supporting the optional AI Features described below, and is engaged for AI purposes only if and to the extent such features are used or enabled on the account. | USA | cloudflare.com/privacypolicy |
| Google (Analytics, Ads, Maps) | Analytics, advertising, and mapping services | USA | policies.google.com/privacy |
| HubSpot | CRM and marketing automation | USA | legal.hubspot.com/privacy-policy |
| Intercom | Chat-based customer support and in-app messaging | USA | intercom.com/legal/privacy |
| LinkedIn (Insight Tag) | Advertising retargeting and campaign measurement | USA | linkedin.com/legal/privacy-policy |
| Mailgun | Email delivery and tracking | USA | mailgun.com/legal/privacy-policy |
| Meta (Facebook Pixel) | Advertising retargeting and campaign measurement | USA | facebook.com/privacy/policy |
| Stripe | Payment processing and invoicing | USA | stripe.com/privacy |
| Twilio SendGrid | Transactional and marketing email delivery | USA | twilio.com/legal/privacy |
| Zendesk | Email-based customer support ticketing | USA | zendesk.com/privacy-notice |
Automated screening that protects the platform and outbound email from spam and abuse. Screening processes the content of outbound emails and the sender name and address only. Guest lists, registration data and payment data are not shared with these providers. Zero data retention terms are in place and no customer data is used to train any model. Security screening applies to every account and cannot be disabled.
| Sub-Processor | Purpose | Location | Privacy Policy |
|---|---|---|---|
| Anthropic | Outbound email abuse and spam screening (automated content classification). Processes the email body and sender name and address only; guest lists, registration data and payment data are not shared. Zero data retention, no training on customer data. | USA | anthropic.com/legal/privacy |
| OpenAI | Outbound email abuse and spam screening (automated content classification). Processes the email body and sender name and address only; guest lists, registration data and payment data are not shared. Zero data retention, no training on customer data. | USA | openai.com/policies/privacy-policy |
Optional. Off by default. RSVPify Cue is RSVPify’s optional AI assistant. It is turned off by default and is not available until a workspace administrator explicitly enables it.
Until an administrator enables Cue, the sub-processors in this section receive no data and perform no processing, and RSVPify involves no AI beyond the platform and email security described above. When Cue is enabled, inputs and outputs are used only to deliver the requested feature and are never used to train or improve any AI model. Administrators control what data Cue may access and can run Cue without access to guest personal information. Cue is governed by the AI Features section of the RSVPify Terms of Service.
| Sub-Processor | Purpose | Location | Privacy Policy |
|---|---|---|---|
| Anthropic | Automated, user-facing AI Features (for example, AI-assisted event creation, content suggestions, scheduling assistance, reporting, and event operations management), enabled optionally by the workspace administrator through account settings. This sub-processor engagement is triggered only by administrator opt-in; no data is processed by this sub-processor unless and until the workspace administrator affirmatively enables AI Features on the account. Not enabled by default. Inputs to, and outputs from, the automated AI Features are processed solely to deliver the applicable feature and are not used to train or improve the underlying AI models. Governed by the AI Features section of the RSVPify Terms of Service. | USA | anthropic.com/legal/privacy |
| OpenAI | Automated, user-facing AI Features (for example, AI-assisted event creation, content suggestions, scheduling assistance, reporting, and event operations management), enabled optionally by the workspace administrator through account settings. This sub-processor engagement is triggered only by administrator opt-in; no data is processed by this sub-processor unless and until the workspace administrator affirmatively enables AI Features on the account. Not enabled by default. Inputs to, and outputs from, the automated AI Features are processed solely to deliver the applicable feature and are not used to train or improve the underlying AI models. Governed by the AI Features section of the RSVPify Terms of Service. | USA | openai.com/policies/privacy-policy |
Self-hosted infrastructure: RSVPify uses self-hosted infrastructure for certain analytics and session recording functions. In these cases, data does not leave RSVPify’s own controlled environment and no third-party sub-processor is involved.
Is this list complete? This reflects RSVPify’s primary sub-processors. RSVPify may use additional infrastructure tooling and software dependencies. For a complete list for compliance purposes, contact [email protected].
See also: Privacy Policy and Data Processing Agreement