Legal
iVvy Sub-processors
The third parties iVvy engages to process Customer Data in the course of providing the iVvy platform.
What this page covers
iVvy engages the third parties listed below as Sub-processors to process Customer Data on its behalf. In this arrangement iVvy is the Data Processor and the customer is the Data Controller, under the agreements between the parties.
This page covers the Sub-processors engaged in the delivery of the iVvy platform. It does not cover the suppliers iVvy uses to run its own business, where iVvy acts as Data Controller rather than as Data Processor. Those are addressed in the iVvy Privacy Policy.
Current sub-processors
| Sub-processor | Purpose of processing | Categories of customer data | Security reference | Optional |
|---|---|---|---|---|
| Amazon Web Services | Cloud hosting and storage for the iVvy platform. | Customer personal data held within the iVvy platform. | aws.amazon.com/compliance | No |
| Userpilot | Product analytics and in-app guidance. | May include user name and email address. No access to customer data held in AWS. | trust.userpilot.com | No |
| Sleekplan | Customer feedback portal, reached from within the iVvy platform. | User name, email address, company, and the content of any feedback submitted, including attachments. No access to customer data held in AWS. | trust.sleekplan.com | No |
| HubSpot | Customer support ticketing. | User name, email address, and the content of any support request submitted, including attachments. No access to customer data held in AWS. | trust.hubspot.com | No |
| Cloudflare | Denial of service protection for the public marketplace. | No customer data. | cloudflare.com/trust-hub | No |
| Payrix | Payment gateway for iVvy Pay. | Personal and financial data required to process card transactions. No access to other customer data. | PCI DSS Attestation of Compliance, available on request | Yes |
| PayPal | Payment gateway for ticketed events. | Personal and financial data required to process card transactions. | PCI DSS Attestation of Compliance, available on request | Yes |
| SecurePay | Payment gateway for events. | Personal and financial data required to process card transactions. | PCI DSS Attestation of Compliance, available on request | Yes |
| Workato | Enterprise service bus for specific customer integrations. | Personal data and other data relevant to the integration. Enabled only with customer approval. | docs.workato.com/security | Yes |
| Hivr AI | AI generated event proposals and lead generation from enquiry emails. | Personal data required to manage leads and proposals. | hivr.ai privacy policy | Yes |
| Heroku | Hosting for the iVvy status page. | Name and email address of subscribers to status notifications. No customer data stored. | heroku.com/compliance | Yes |
| Mailgun | Email delivery for status page notifications. | Subscriber email addresses. No customer data stored. | mailgun.com/security | Yes |
A Sub-processor marked Optional is engaged only where a customer uses the feature it supports, or where the customer has approved it. A Sub-processor marked No is engaged in the delivery of the platform to all customers.
Changes to this list
This page is the current list of Sub-processors. It is updated when a Sub-processor is added, replaced or removed. The engagement of Sub-processors is governed by Schedule 2 of the iVvy Master Services Agreement.
iVvy reviews the security posture of each Sub-processor before engaging it.
The security posture of each Sub-processor is published at the reference listed against it.
Questions about this page or about any Sub-processor can be directed to privacy@ivvy.com.
Stay informed about sub-processor changes
Complete the form below and we'll let you know whenever a Sub-processor is added, replaced or removed.