Sub-Processors
Last updated: April 13, 2026
Gaze uses the following sub-processors to provide the Service. This list is maintained in accordance with our obligations under the General Data Protection Regulation (GDPR) and our Data Processing Agreement.
Current Sub-Processors
| Sub-Processor | Legal Entity | Location | Purpose | Data Processed |
|---|---|---|---|---|
| Supabase | Supabase, Inc. | United States | Database hosting, user authentication, file storage | Account data, event data, media files, authentication credentials |
| Stripe | Stripe, Inc. | United States | Payment processing | Email address, subscription details (Stripe handles card data directly) |
| Resend | Resend, Inc. | United States | Transactional email delivery (magic link authentication, account notifications) | Email address, email content |
| Google LLC | United States | OAuth sign-in (optional) | Email, name, profile picture (only if user chooses Google sign-in) | |
| hCaptcha | Intuition Machines, Inc. | United States | Bot prevention during signup | Captcha challenge tokens |
| Microsoft | Microsoft Corporation | United States | Session replay analytics via Microsoft Clarity (marketing and organizer dashboard pages only — not loaded on guest-facing pages) | Anonymized interaction data, page URLs, device/browser info |
Changes to Sub-Processors
We will notify event organizers by email at least 30 days before adding a new sub-processor. During this period, organizers may object to the addition by contacting us at support@gaze.photo. If an organizer objects and we cannot reasonably accommodate the objection, the organizer may terminate their use of the Service.
We will update the "Last updated" date on this page whenever a sub-processor is added, removed, or changed.
Questions
If you have questions about our sub-processors or data processing practices, please contact us at support@gaze.photo.