Subprocessors
Last updated: April 2026
GifyLabs engages third-party service providers (“subprocessors”) to help us deliver and operate our platform. This page lists the subprocessors that may process personal data on behalf of GifyLabs customers.
We review every subprocessor for data-protection compliance before engaging them, and we impose contractual terms at least as protective as our obligations to you. If we add or change subprocessors, we post an update to this page and notify customers in accordance with their Data Processing Agreement.
Infrastructure
| Service | Purpose | Data processed | Location |
|---|---|---|---|
| Amazon Web Services (AWS) | Hosting, compute, storage, database, CDN, email delivery infrastructure | All customer and end-user data stored and processed by the platform | United States (us-east-1) |
| Cloudflare | DDoS protection and DNS (if applicable to your account) | IP addresses, request metadata | Global (edge network) |
Payments
| Service | Purpose | Data processed | Location |
|---|---|---|---|
| Stripe | Payment processing and subscription billing | Billing contact information, payment method details (handled directly by Stripe — we do not store card data) | United States, Ireland |
Platform communications
| Service | Purpose | Data processed | Location |
|---|---|---|---|
| AWS Simple Email Service (SES) | Transactional email delivery (account verification, password reset, notifications) | Recipient email address, email content | United States |
Optional subprocessors (customer-initiated)
The following subprocessors receive data only when a customer explicitly connects the corresponding integration from within the GifyLabs dashboard. If a customer does not use the integration, no data is shared with these services.
| Service | Purpose | Data processed | Location |
|---|---|---|---|
| Shopify | OAuth for Shopify app installation, Shopify Admin API integration | Shop domain, shop metadata, OAuth access tokens (when a customer installs the GifyLabs Shopify app) | Canada |
| Mailchimp | ESP integration — syncing contacts to customer Mailchimp audiences when connected by customer | Contact email, name, phone, and custom fields (only when customer explicitly connects Mailchimp) | United States |
| Klaviyo | ESP integration — syncing contacts to customer Klaviyo lists when connected | Contact email, name, phone, and custom fields (only when customer explicitly connects Klaviyo) | United States |
| SendGrid (Twilio) | ESP integration — syncing contacts to customer SendGrid marketing lists when connected | Contact email, name, phone, and custom fields (only when customer explicitly connects SendGrid) | United States |
| HubSpot | ESP integration — syncing contacts to customer HubSpot when connected | Contact email, name, phone, and custom fields (only when customer explicitly connects HubSpot) | United States |
| Constant Contact | ESP integration — syncing contacts to customer Constant Contact lists when connected | Contact email, name, phone, and custom fields (only when customer explicitly connects Constant Contact) | United States |
Changes and notifications
Material changes to this list (adding a new subprocessor that receives customer data by default) will be posted here and announced via email to customer primary contacts. Customers with an active Data Processing Agreement have the right to object to new subprocessors on reasonable data-protection grounds within thirty (30) days of notice.
Questions
For questions about subprocessors or to request a signed Data Processing Agreement, contact privacy@gifylabs.com or visit our Privacy Policy.