Legal
Sub-processors
Effective 6 October 2026
To run Gaurify Meet we rely on a small set of trusted providers. Each one only receives the data it needs to do its job. This is the current list.
| Provider | What it does | Data it handles |
|---|---|---|
| Cloudflare | Hosting, database (D1), and Workers AI for Flow (screenshots, and backup for questions) | All product data, at the edge and at rest |
| OpenRouter | Runs Meta's Llama model to answer Flow questions | Your Flow question, recent messages, and your next 8 meetings (guest name, time, length) |
| Brevo | Transactional and product email delivery | Recipient name and email, message content |
| Brave Search | Web context and grounding for Flow answers | The query text you type into Flow |
| Google sign in, and Calendar and Meet when a host connects them | Account email, calendar busy times and events | |
| Meta (WhatsApp Business Cloud API) | Booking confirmations, reminders and changes on WhatsApp | Guest and host phone numbers, and the message content (names, meeting time, links) |
| Razorpay | Cards, UPI, netbanking, wallets and autopay (India and beyond) | Billing details processed by the provider |
| Apple | In-App Purchase subscriptions in the iPhone app | Purchase and subscription status |
Adding a meeting to Apple Calendar or Outlook happens on your own device or account. We do not sync with them, so neither one is a sub-processor. We add or change a sub-processor only when it is needed to run or improve the product. We hold each one to appropriate data protection terms.
Changes
When we make a material change to this list, we will update this page and, where required, notify account holders. See our Privacy Policy for how data is used and your rights.
Contact
Questions about our sub-processors? Email hello@gaurifyhq.com.