Effective August 25, 2026
Inbox Zero Privacy Policy
This policy applies to Ben Garcia's private, self-hosted Inbox Zero instance.
Google data the app accesses
The app requests only the access Ben authorizes for the features he chooses to use:
- Basic Google profile information and email address for sign-in and account identification.
- Gmail messages, metadata, attachments, labels, drafts, sending capabilities, and basic mail settings such as filters. Requested rules and actions may also archive, trash or delete, mark as spam or read, star, or forward messages.
- Google Calendar calendars, events, attendees, and free/busy information. The app may create, update, or delete events when Ben requests scheduling and meeting actions.
- Google Drive files and folders created by, or explicitly opened with, the app for attachment filing and AI search. Selecting a folder can let the app discover and process accessible files in that folder and its subfolders without selecting each file individually.
How Google data is used
Google data is used only to provide requested Inbox Zero features: organizing email; archiving, trashing or deleting, marking as spam or read, starring, or forwarding messages; drafting or sending messages; applying labels and filters; scheduling calendar events; checking availability; and filing or indexing selected attachments.
Google user data is not used for advertising, sold, rented, or used to build credit, employment, insurance, or other eligibility profiles.
Storage, retention, and deletion
Ben-controlled, self-hosted infrastructure stores OAuth tokens and Google-derived records needed to operate and audit the requested features. Depending on the features used, these records can include Google account identifiers; email addresses; message and thread identifiers; sender and recipient addresses; message subjects, snippets, digest content, attachments and attachment metadata; drafted or sent message text; labels, rules, and executed-action history; Calendar identifiers, names, event titles, attendees, booking details, meeting details, and generated meeting briefings; and Drive file names, folder names or paths, file identifiers, web URLs, MIME types, modification times, sizes, and filing history. When Ben selects an accessible Drive file or folder as a draft-attachment or AI-search source, the app may download accessible files and store extracted or cleaned text, generated summaries, page counts, truncation status, indexing status, and indexing error details. For a selected folder, the current app may recursively scan subfolders to a depth of five, store metadata for up to 500 discovered PDFs, and download and index up to 12 PDFs per refresh.
Google remains the system of record for source Gmail, Calendar, and Drive content unless the app performs an action Ben requests. Copies and derived records stored by the app remain until they are removed through the applicable feature or account cleanup, the self-hosted instance data is deleted, or a deletion request is honored. Deleting an email account or user removes account-linked records but may not remove every independently stored record. In particular, public-contact research started from a Gmail sender may retain that sender's email address and research history independently of the account or user until the instance data is deleted or a deletion request is honored.
Disconnecting an integration or revoking Google access stops future API access, but it does not by itself delete every record already stored by the app. To request deletion of app-stored Google data, contact hey@bengarcia.dev.
Sharing and disclosure
Google user data is not shared with third parties except service providers that Ben explicitly configures to operate a requested feature, or when disclosure is required by law. Any optional third-party integration will be enabled and disclosed by the operator before Google data is sent to it.
The app's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.
Security and account control
The application is restricted to Ben's private network, uses encrypted HTTPS connections, and stores credentials in access-restricted server configuration. No system can guarantee absolute security.
Ben can review or revoke access at any time in Google Account permissions. He can also disconnect integrations in Inbox Zero or contact the operator to delete app-stored data.
Changes and contact
This policy may be updated when the self-hosted configuration or its integrations change. The effective date above will be updated with material changes.
Questions or deletion requests: hey@bengarcia.dev.