Mail integration privacy

This notice covers Tavern outgoing Gmail, the website integration that sends mail through the Tavern operator's Google account.

Information used

Messages contain recipient addresses, subject lines and message bodies needed for the requested workflow. Depending on the request, they may include names, contact-form text, application details or private alpha invitation links. Do not include passwords, credentials, private saves or unreviewed diagnostics in a contact message.

Google account access

The operator authorizes the Gmail send-only scope. The integration uses that permission to send messages, not to read, search, modify or delete messages in the mailbox. It does not connect visitors' Google accounts. The operator can still review messages directly in Gmail when providing support.

Processing and storage

Google processes outgoing messages and keeps mailbox copies according to the sending account's settings. The website's hosting infrastructure processes message content to prepare and send it. OAuth credentials are stored in the website's secret settings; they are not included in emails or public pages. Application records and feedback submitted to Tavern are separate from Gmail mailbox storage.

The integration does not automatically delete Sent mail or support correspondence. Contact the operator to request deletion of a message or correction of your details. The operator will verify the request before changing records; deleting a mailbox copy does not remove copies already delivered to recipients.

Use and sharing

Message information is used to operate Tavern communications and respond to support requests. It is sent to Google and the intended recipients for delivery. This integration does not use Gmail data for advertising or model training. Tavern outgoing Gmail'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.

Your choices

Visitors can contact hello@thetavern.dev directly instead of using the website contact form. The sending account owner can revoke this integration through Google Account connections. Revocation stops future API access; it does not recall messages already sent.