Data and access · Last updated 11 November 2026
Privacy Policy
Operator and contact
Zenith is operated by Gustavo Dos Santos in Switzerland. Questions about data access or deletion can be sent to 17gustavosantos@gmail.com.
Purpose and Google permission
Zenith uses the operator’s Google account to organise selected emails, extract property-alert information and support personal intake, summaries and classification. The currently declared scope is https://www.googleapis.com/auth/gmail.readonly. This is a mailbox-wide read permission; configured labels and searches narrow which emails individual workflows process. The scope does not permit sending, changing or deleting Gmail messages.
Information processed
The Gmail Intelligence Intake workflow fetches up to 20 messages matching a configured Gmail label per run. It retrieves each selected message and stores the Gmail message and thread identifiers, sender, subject, plain-text email body and received date in Supabase. It checks the message identifier to avoid re-importing existing records.
The sender, subject and plain-text email body are sent to OpenAI for AI classification. The resulting pillar, classification, priority, confidence, summary, suggested action and classification time are saved in Supabase. OAuth credentials authorise Gmail access without supplying the Google account password to Zenith.
Storage and service providers
n8n runs the workflows; Supabase stores structured records. The current workflow server is hosted by OVHcloud in Canada. The Supabase database is located in London, United Kingdom (eu-west-2). OpenAI is used for AI-assisted classification and chat, and relevant content or derived information can be included in model requests where those workflows are enabled. Infomaniak hosts this public information website. Processing can therefore involve service providers and locations outside Switzerland.
The sender, subject and plain-text body of selected emails are transmitted to OpenAI to provide classification and summaries. Optional OpenAI API data-sharing settings are disabled in the operator’s organisation. Processing an email through the API is distinct from opting in to share API data for model improvement.
Retention and deletion
Supabase email records and derived classifications are separate from the original Gmail messages. This intake workflow has no automatic deletion step. Imported records can remain until manually removed; deleting an original message or revoking Google access does not automatically erase these copies.
The installed n8n defaults enable execution-history pruning, with an age threshold of 336 hours (14 days) and a count threshold of 10,000 executions. Successful, failed and manual executions are saved by default. These thresholds govern eligibility for periodic cleanup, not an exact deletion deadline. They do not govern Supabase records, provider-side records or backup copies, and do not establish that every eligible execution has already been deleted.
To request deletion or clarification, contact the operator. Deletion from active records and any remaining copies must be assessed separately; no automatic complete-erasure deadline is currently promised.
Provider-side retention and backups
OpenAI API data is not used for model training by default unless the customer opts in. Optional sharing is disabled for the operator’s organisation. This does not mean zero retention: OpenAI’s standard abuse-monitoring logs can retain content for up to 30 days, subject to exceptions described in its documentation. The Responses API also has application-state storage by default, generally with a 30-day retention period; the inspected workflow does not explicitly disable that storage. See OpenAI’s data-controls documentation for the applicable conditions and exceptions.
The current Supabase Free plan does not include project backup features in the dashboard. This statement does not establish that no provider-internal recovery copies or separately created manual backups exist. Previously exported or backed-up copies must be handled separately from live data. No fixed complete-erasure deadline for all copies is promised here.
Control of access
The operator can revoke the Google connection through Google Account connections. Questions or deletion requests can be directed to the contact above.
Limited Use
Zenith’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. Google-derived data is used for the personal organisation and assistance functions described here, not for sale, advertising or training general-purpose AI models. Sharing with processing providers is limited to delivering those functions. This website does not offer public account connections.
Public website
These static pages contain no contact form, analytics scripts or advertising code. The hosting provider may process technical request logs. The public website does not display the operator’s mailbox or private Zenith records.