Privacy Policy
Effective 14 September 2026
We keep this short and honest. This explains what Gaurify Meet collects, why, who helps us process it, and the choices you have. Gaurify is the data controller for the product. Reach us at hello@gaurifyhq.com.
What we collect
- Account details from a host: name, email, page handle, and a password hash or passkey. We never store a readable password.
- Booking details from a guest: name, email, and any note or answer you add when you book.
- Calendar data, only if a host connects a calendar: busy times to work out availability, and the events we create for bookings. We request the narrowest access that makes this work.
- Screenshots you give to Flow, only when you drop one in, to pull out the meeting details and pre-fill the form.
- Basic technical data: IP address and request logs, used for security and rate limiting, kept briefly.
Why we use it
- To run the product: show availability, take bookings, put events on calendars, and send the emails a booking needs.
- To keep the service safe and prevent abuse (rate limits, fraud checks).
- To bill paid plans and issue invoices.
- To reply when you contact us.
We do not sell your data, we do not use your content or a guest's details to train AI models, and we do not run advertising trackers on you.
Google Calendar data (Limited Use)
When you connect your Google Calendar, Gaurify Meet requests the narrowest scopes that make scheduling work: calendar.freebusy and calendar.calendarlist.readonly, to read only your busy times across your calendars and work out when you are free, and calendar.events, to create, update and cancel the specific events for meetings you book. We do not request access to read or download the content of your calendar events, and we do not read, store or use them.
Gaurify Meet's use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements. Specifically, we use Google Workspace data only to provide and improve the user-facing scheduling features above. We do not transfer this data to others except as needed to provide the service or as required by law, do not sell it, do not use it for advertising, and do not use it (in raw, aggregated, anonymised or derived form) to develop, improve or train any generalised or foundational AI or machine-learning models. You can disconnect at any time from your account, which revokes our access and stops any further reads or writes.
Who we share Google user data with
We do not sell or rent your data. We share Google user data only with the infrastructure providers that are strictly required to run the product, and only to the extent needed to operate it on your behalf:
- Cloudflare (our application host and database): stores and processes the data that runs Gaurify Meet, including your calendar connection and the events we create for your bookings.
- Google itself, when we call the Google Calendar API on your behalf to read availability and create the meeting.
- Nobody else. Google user data is never shared with our AI features, advertising networks, data brokers, or any third-party AI or analytics provider.
The full list of every provider we use, with what each one does, is on our Sub-processors page.
How we protect your data
We apply security controls suited to sensitive data, including Google user data:
- Encryption in transit: all traffic runs over HTTPS/TLS.
- Encryption at rest: data is stored on encrypted infrastructure at our host.
- Least privilege & access control: access to production data is limited to the people who need it, over authenticated channels; OAuth tokens are held only as long as your calendar stays connected and are deleted when you disconnect.
- No secrets in the clear: passwords are stored only as hashes and passkey secrets never leave your device; nobody, including our staff, can read them.
- Data minimisation: we request the narrowest scopes, keep only what a booking needs, and age out short technical logs automatically.
AI features and your data
Gaurify Meet includes an assistant called Flow that answers questions about the product and can help draft a booking from a sentence or a screenshot you choose to share. Flow processes only the text or image you deliberately give it in that moment. Flow and any AI or machine-learning service we use never receive your Google Calendar data, and no Google user data, and no guest's personal data, is ever used to train, fine-tune, or improve any AI model. AI requests are processed by Cloudflare Workers AI for the sole purpose of returning your result, and are not used by us or the provider to train generalised models.
Guests are protected end to end
A guest's details are only ever shown to the host they booked with. A team member sees their team's data. A change to a guest's own name, number, or email is confirmed by that guest through a link or one time code before it takes effect. Nobody, including our staff, can read a password or a passkey secret.
How long we keep it
We keep account and booking data while your account is active. When you close your account we delete or anonymise your data within a reasonable period, except where we must keep records (for example, tax and invoice records for the period the law requires). Short technical logs age out on their own.
Your rights
Depending on where you live, you can ask to access, correct, export, or delete your data, and to object to certain processing. Email hello@gaurifyhq.com and we will act on it. A guest can also ask the host they booked with, or contact us directly.
International transfers
Our providers may process data in more than one country. Where data leaves your region we rely on the provider's safeguards for lawful transfers.
Children
Gaurify Meet is not meant for children under the age needed to consent in your country. We do not knowingly collect their data.
Changes
If we change this policy in a way that matters, we will tell account holders by email or in the product before it takes effect.
Contact
Privacy questions or requests go to hello@gaurifyhq.com. See also our Security page.