What we access, what we do with it, and what we never do.
This page covers the Email Automation Service — the tool that connects to a client's Gmail account to read and label incoming mail — and Totem, our booking system. Plain language, checked against the actual code, not a copy-pasted template.
What we access
When you connect your Gmail account, you grant access through Google's own permission screen — never a password, never anything typed into our site. Two permissions are requested, in two separate steps: first read access, then, if you choose to enable labeling, read and label access (Google calls thisgmail.modify). We never request permission to delete your account or change your password.
What we store
We keep a record of each message's subject line, sender's domain, its Gmail message and thread IDs, its labels, and when it arrived. We do not store the body of your emails. That record is what lets the tool avoid re-processing a message it has already seen and lets you see a plain-language report of what it has done.
What we send to the AI, and to whom
To decide how urgent a message is, the tool sends the message's content to Anthropic's Claude API — the AI model that reads and classifies it. Before that happens, personal information (names, phone numbers, account numbers, and similar) is stripped out in our own code, not left to the AI to ignore. Anthropic is a subprocessor for this one purpose; their own handling of API data is described in Anthropic's privacy policy. We do not share your email content with anyone else.
The use of raw or derived user data received from Google Workspace APIs will adhere to the Google User Data Policy, including the Limited Use requirements — this data is never used to train, improve, or develop any AI or machine learning model, ours or Anthropic's.
How the data is protected
Your Gmail sign-in credential is stored encrypted, never in plain text. The record described above (subject lines, labels, message IDs) sits in a private database only this service's own code can reach — it is never exposed publicly or handed to a third party beyond the one-time, redacted AI classification call described above. Access to the systems that operate this service is limited to Kush Enterprise LLC.
What we never do
- We never send, compose, or reply to email on your behalf. This is enforced in the code itself, not just a policy — the software will not build if any part of it gains the ability to send mail.
- We never permanently delete a message. Anything moved to Trash stays recoverable there for 30 days, the same as Gmail's own default, and only happens for categories you've specifically approved (like obvious marketing mail) — never applied blindly.
- We never read or act on a mailbox until you've personally completed Google's sign-in screen for it.
Your control
You can remove this app's access at any time from your own Google Account — Security → Third-party access — with no need to contact us first. To have your stored records (subject lines, labels, and the rest described above) deleted, email us at the address below and we'll remove them.
Totem, our booking system
Totem is the booking system behind book.kushautomation.com. A business owner connects their Google Calendar to it through Google's own permission screen. Totem asks for your Google account's email address and two calendar permissions: to see when you are busy, and to add and change events.
What Totem reads. The start and end of busy times on the connected calendar, so a booking page never offers a time that is already taken. It does not keep the titles or details of your other events.
What Totem writes. One event for each booking made through it, with the guest invited. It updates that event if the guest reschedules and removes it if they cancel. It does not change any other event.
What Totem stores. The Google sign-in tokens that let it do the above, encrypted, never in plain text. It also stores the bookings themselves (the guest's name, email, time and any notes they add), which is what a booking system needs to run.
How Totem protects your data. Security procedures are in place to protect the confidentiality of your calendar data. We use encryption to protect your information: Google sign-in tokens and stored bookings are encrypted at rest, never in plain text, and every connection to and from Totem is encrypted in transit over HTTPS. Access to the systems that operate Totem is limited to Kush Enterprise LLC.
Totem's use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. Calendar data is never sold, never used for advertising, and never used to train any AI or machine learning model. Totem sends no calendar data to any AI service.
You can disconnect Totem at any time, from Totem's Integrations page or from your Google Account under Security → Third-party access. Disconnecting from Totem also revokes its access at Google.
Worksheet requests
When you request a downloadable worksheet, we collect your email address, your name if you provide it, and any campaign tags included in the page URL. We use these details to deliver the requested file, record delivery, avoid duplicate sends, and understand which content generated requests.
Request notifications pass through Resend to our business inbox. Our local automation uses Gmail to deliver the file and Telegram to notify the business owner. Cloudflare Turnstile verifies form submissions to reduce abuse. A worksheet request does not subscribe you to marketing email.
Contact [email protected] to ask about or request deletion of your request record.
Site analytics
If you follow a campaign link, we may retain its source labels with your inquiry or booking to understand which content brought you here. These labels do not include a visitor ID and do not require cookies or browser storage.
Separately from the service above, this website uses Cloudflare Web Analytics to count page views and measure how quickly pages load for visitors. Cloudflare states that Web Analytics does not collect or use visitors’ personal data.
Infrastructure
The service runs on Cloudflare (hosting and database) and Google (Gmail API access). Both are infrastructure providers, not parties we share your email content with beyond what's needed to run the service you connected.
Totem runs on a DigitalOcean server we control, behind Cloudflare, and talks to Google (Calendar API access). These are infrastructure providers, not parties we share your calendar data with.
Contact
Questions about this policy, or a deletion request: [email protected].
Last updated September 20, 2026.