Privacy Policies
Privacy Policy — TGOS TIM Gmail
Turtle Garden Lodge
Effective date: 27 August 2026
The use of information received from Google Workspace APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
This Privacy Policy describes how Turtle Garden Lodge (“we”) handles personal information collected through our website, reservations, and the internal application TGOS TIM Gmail (“the app”).
Contact: mail@turtlegardenlodge.com
1. Who this policy covers
This policy covers information provided through the Turtle Garden Lodge website or during a reservation, as well as Google Account data accessed when an authorized Turtle Garden Lodge operator connects TGOS TIM Gmail.
TGOS TIM Gmail is an internal operations tool. It is not a public mailbox service and is not offered to guests or other Google users.
2. Website and reservation information
We may collect information that a guest or prospective guest voluntarily provides, including names, contact details, travel information, reservation details, payment-related information, activity preferences, diving information, and messages.
We use this information to answer inquiries, arrange reservations, provide requested services, communicate with guests, and operate Turtle Garden Lodge.
We do not sell personal information. We may share information when reasonably necessary to provide a requested service—for example, with a dive operator, transport provider, payment provider, or another service provider involved in a guest’s arrangements.
Our website is hosted by Cloudflare, and our domain is registered through GoDaddy. Their handling of information is governed by their respective privacy policies.
3. Google user data accessed by TGOS TIM Gmail
The app requests only these Google OAuth scopes:
- openid — to authenticate the Google Account and obtain its stable OpenID account identifier.
- email — to receive the Google Sign-In email claim associated with that authentication.
- https://www.googleapis.com/auth/gmail.readonly — a restricted Gmail scope used today to read Gmail profile information needed to bind the mailbox and to register, renew, and stop a Gmail INBOX watch.
The Gmail watch allows Google to notify our servers that the authorized mailbox changed. We do not currently list mailbox history or retrieve Gmail messages, headers, bodies, or attachments.
During authorization, we also receive OAuth tokens from Google. Access tokens and ID tokens are used temporarily and are not stored after their immediate use. The refresh token is encrypted and stored so the Gmail watch can be renewed without repeatedly asking the operator to sign in.
Gmail profile responses may include mailbox message and thread counts. The app may receive those fields temporarily, but it does not store them.
4. Why the Google scopes are required
The openid scope lets us identify the verified Google Account using its stable account identifier rather than relying on a changeable email address.
The email scope supports Google Sign-In and OpenID Connect authentication.
The gmail.readonly scope supports the Gmail profile and watch functions currently used by the app. It is also the least-privilege Gmail scope capable of supporting the intended later retrieval of INBOX history and operational message content for the same authorized mailbox. We do not request gmail.modify, gmail.send, or full mail.google.com access.
5. Current use of Google user data
We currently use Google user data only to:
- complete operator-initiated Google authorization for one Turtle Garden Lodge operational mailbox;
- store encrypted credentials for that connection;
- read the Gmail profile email address so Google push notifications can be matched to the connection;
- register and periodically renew an INBOX watch;
- receive authenticated Google Pub/Sub notices that the INBOX changed and record that inspection may be required later; and
- allow authorized operators to check connection health and disconnect or revoke the connection.
We do not currently:
- retrieve Gmail messages or MIME content;
- ingest Gmail messages into TIM transport storage;
- send Gmail data to TGOS; or
- provide Gmail features to the public.
6. Intended later use of the same Google authorization
If Turtle Garden Lodge later activates Gmail history and message retrieval for the same authorized operational mailbox, the same gmail.readonly grant may be used to:
- list Gmail history after a stored watermark; and
- retrieve message content needed to turn authorized operational mail into Turtle Garden Lodge operations records.
This capability is planned but is not currently active. Gmail message content is not currently accessed, stored, or transmitted by TIM.
Before activating that capability, we will ensure this policy still accurately describes the implemented use. If the use goes beyond what is disclosed here, we will update this policy and obtain new operator consent before accessing additional Google user data. We will not use Google user data for an undisclosed purpose.
7. Server-side processing and security
TGOS TIM Gmail is a server-side application operated through Cloudflare Workers, Workers KV, and a Durable Object used for mailbox connection state.
The Gmail refresh token is encrypted with AES-GCM before being stored in a dedicated Workers KV namespace. Access tokens are not written to storage. Gmail credentials are not stored in TIM’s WhatsApp or general transport storage.
We use HTTPS, OAuth PKCE, encrypted refresh-token storage, restricted administrative credentials, and fail-closed configuration controls. No security measure is perfect.
8. Information stored for a connected mailbox
While a mailbox is connected, we may store:
- the Google Account’s OpenID account identifier;
- the Gmail profile email address and an email-to-account lookup index;
- the encrypted refresh token;
- the scopes granted by the operator;
- the Gmail watch history identifier and expiration;
- connection status and operational timestamps; and
- mailbox connection-state information, including generation and inspection flags.
Temporary OAuth state, including the PKCE verifier and nonce, is stored for approximately ten minutes and then deleted.
We do not currently store Gmail message bodies.
9. Sale, advertising, credit, and artificial intelligence
We do not sell Google user data.
We do not use Google user data for advertising, retargeting, credit decisions, lending decisions, or data-broker activities.
We do not use Gmail data to create, train, or improve machine-learning or artificial-intelligence models.
10. Sharing and service providers
We do not share Gmail mailbox content with advertisers, data brokers, or the public.
We use:
- Google to provide OAuth, the Gmail API, and Gmail Pub/Sub notifications; and
- Cloudflare to run the app, store encrypted credentials and connection metadata, and host operational logs.
Cloudflare hosts Turtle Garden Lodge’s public website and these legal pages. GoDaddy provides domain-registration services. The public website does not receive Gmail tokens or Gmail messages.
TGOS, Turtle Garden Lodge’s operations system, does not currently receive Gmail data from TIM.
11. Human access
Authorized Turtle Garden Lodge operators who hold administrative credentials for TIM, Cloudflare, or Google Cloud may access connection metadata, including the connected email address and Google account identifier, when reasonably necessary to operate, troubleshoot, secure, or revoke the integration.
TIM does not currently retrieve Gmail message content. If retrieval is later activated as described in section 6, authorized operators may process operational mailbox content only for the disclosed Turtle Garden Lodge operations purpose, for security, or to comply with applicable law.
12. Logging
Operational logs generally use shortened cryptographic digests of mailbox identifiers rather than raw email addresses or Google account identifiers.
Operator-authenticated connection tools and the Google OAuth callback may return the connected email address and account identifier to the authorized operator.
We do not intentionally log refresh tokens, access tokens, or Gmail message bodies.
13. Retention
Website, inquiry, and reservation information may be retained for as long as reasonably necessary to communicate with guests, provide requested services, maintain business records, resolve disputes, and comply with applicable obligations.
Connected Gmail credentials and watch metadata are retained while the mailbox remains connected and the information is needed to operate and renew the connection.
When an operator disconnects the mailbox, TIM deletes the encrypted refresh token and email lookup index, attempts to stop the Gmail watch, and asks Google to revoke the token. TIM may retain a disconnected connection record containing the Google account identifier, email address, previously granted scopes, last watch history identifier, and disconnection timestamp. TIM does not currently run an automatic purge of this remaining metadata.
Temporary OAuth state expires after approximately ten minutes.
14. Disconnecting, revocation, and deletion requests
An authorized operator may disconnect the mailbox through TIM. The operator may also revoke TGOS TIM Gmail through the Google Account’s third-party access settings, which invalidates its Google tokens.
TGOS TIM Gmail is operator-controlled and has no public self-service account system.
To request deletion of remaining connection metadata or to ask a privacy question, contact mail@turtlegardenlodge.com.
15. Children
TGOS TIM Gmail is not directed to children and is not intended for anyone under 13 years of age.
16. Changes to this policy
We may update this Privacy Policy when our practices or legal obligations change. We will revise the effective date when we do.
If we materially change how we use Google user data, we will update this policy and, when required by Google’s policies or applicable law, obtain new consent before beginning the new use.
17. Google API Limited Use
Our use and transfer to any other application of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
We also follow the Google Workspace API user data and developer policy to the extent it applies to this personal, operator-controlled integration.
