Privacy Policy
Last updated: February 2026
ezagentauth does not collect, store, or have access to any of your Google user data. Your data stays between you and Google.
This Privacy Policy explains how ezagentauth ("we", "our", or "the Service") handles data when you use our OAuth authentication service at ezagentauth.com. This policy complies with the Google API Services User Data Policy.
1. Data Accessed
When you authenticate through our service, you authorize access to the following types of Google user data (OAuth scopes):
- Google Calendar - Read and write access to your calendar events
- Google Drive - Access to view and manage files in your Google Drive
- Google Docs - Access to view and manage your Google Docs documents
- Google Sheets - Access to view and manage your Google Sheets spreadsheets
- Google Slides - Access to view and manage your Google Slides presentations
- Gmail - Read and send emails on your behalf
- Google Contacts - Read-only access to your contacts
- Google Chat - Read spaces and send messages
- Basic Profile - Your basic profile information
Important: While these scopes are requested during authentication, ezagentauth itself does not access, read, or process any of this data. The OAuth token that grants access to these services is provided directly to you.
2. Data Usage
ezagentauth does not use your Google user data in any way.
Here's exactly what happens during the authentication flow:
- You click "Sign in with Google" and are redirected to Google's authentication servers
- You authenticate directly with Google and approve the requested permissions
- Google sends an authorization code to our callback endpoint
- Our server exchanges this code for OAuth tokens with Google's servers
- The tokens are immediately displayed in your browser for you to copy
- The tokens exist only in your browser's memory and are never stored on our servers
We do not:
- Read any emails, calendar events, documents, or other content from your Google account
- Send emails or create events on your behalf
- Analyze or process any of your Google data
- Use your data for AI/ML model training
- Use your data for advertising or marketing purposes
3. Data Sharing
ezagentauth does not share your Google user data with any third parties.
Since we do not collect or store any of your Google data, there is no data to share. Specifically:
- We do not sell your data to anyone
- We do not share your data with advertisers
- We do not share your data with analytics providers
- We do not share your data with any other third parties
Your responsibility: The OAuth token you receive is under your control. When you share this token with an AI agent or any other application, you are granting that application access to your Google account. We are not responsible for how those applications use your data.
4. Data Storage & Protection
ezagentauth does not store any Google user data.
Our Architecture
This service runs on Cloudflare Workers, a stateless serverless platform. Our implementation:
- No database: We have no database of any kind - no SQL, no NoSQL, no key-value store
- No persistent storage: Cloudflare Workers do not retain data between requests
- No logging of user data: We do not log OAuth tokens, user identifiers, or any Google account information
- No cookies: We do not set any cookies on your browser
- No analytics: We do not use Google Analytics or any other tracking tools
What We Do Store
The only data we store are our OAuth client credentials (Client ID and Client Secret) as encrypted secrets in Cloudflare. These are our application's credentials, not your personal data.
Security Measures
- All traffic is encrypted via HTTPS/TLS
- OAuth client secrets are stored as encrypted environment variables
- The service is open source for full transparency and audit
5. Data Retention & Deletion
Since we do not store any Google user data, there is no data retention period.
Token Lifecycle
OAuth tokens exist only temporarily during the authentication process:
- Tokens are generated by Google's servers
- Tokens pass through our server's memory for less than a second during the exchange
- Tokens are displayed in your browser
- Tokens are cleared from server memory immediately after the response is sent
Once you close the browser tab or navigate away, the tokens exist only where you have saved them.
Revoking Access
You can revoke the OAuth tokens and disconnect ezagentauth from your Google account at any time:
- Visit myaccount.google.com/permissions
- Find "ezagentauth" in the list of connected apps
- Click "Remove Access"
This immediately invalidates all tokens issued through our service.
Data Deletion Requests
Since we do not store any of your personal data or Google user data, there is no data to delete. If you have any concerns, you can:
- Revoke access through Google (as described above)
- Contact us at the GitHub repository with any questions
6. Open Source Transparency
This entire service is open source. You can:
- Audit the complete source code at github.com/araa47/ez-google
- Verify that no data collection occurs
- Deploy your own instance if you prefer
- Submit issues or questions on GitHub
7. Changes to This Policy
We may update this Privacy Policy from time to time. Changes will be posted on this page with an updated "Last updated" date. Continued use of the service after changes constitutes acceptance of the updated policy.
8. Contact
If you have questions about this Privacy Policy or our data practices, please: