OAuth & Privacy Help

Understanding Gmail permissions and data privacy

Common Questions

Why do you need access to my Gmail?

We need read-only access to analyze your emails for billable content. This includes reading email text, sender/recipient information, and timestamps to identify client communications and time-trackable activities. We cannot modify or delete your emails.

Is my email data stored on your servers?

No. Your email content is processed in memory only and immediately discarded after analysis. We only retain the extracted billable information (client names, time entries, etc.) that you explicitly choose to save for your reports.

Can you send emails from my account?

Absolutely not. We only request "read-only" permissions, which means we can view your emails but cannot send, modify, or delete anything from your Gmail account.

How do I revoke access later?

You can revoke access at any time by visiting yourGoogle Account permissions page and removing "Email Billables" from your connected apps.

Exact Permissions We Request

gmail.readonly (Read Gmail messages)

Allows us to read email content, sender/recipient info, and timestamps. This is read-only access - we cannot modify or delete emails.

✓ Required for email analysis

userinfo.email (Basic profile info)

Your email address for account identification and session management. We don't access any other profile information.

✓ Required for account setup

How We Protect Your Data

End-to-End Encryption

All data is encrypted during transit using industry-standard TLS

Memory-Only Processing

Email content is never written to disk or permanent storage

Immediate Cleanup

Raw email data is deleted from memory after processing

No Data Training

Your emails are never used to train AI models

Minimal Retention

Only billable summaries are kept, never raw email content

Access Controls

Strict access controls and audit logs for all data handling

Troubleshooting OAuth Issues

"Access Denied" Error

This happens when you don't grant the required permissions during sign-in.

Solution: Click "Try Again" and make sure to check all permission boxes during the Google sign-in process.

"Redirect URI Mismatch" Error

This is usually a configuration issue on our end.

Solution: This error is automatically reported to our team. Try again in a few minutes, or contact support if it persists.

Sign-in Page Won't Load

Browser security settings might be blocking the OAuth flow.

Solution: Try disabling ad blockers, allow popups for this site, or try a different browser (Chrome works best with Google OAuth).

Still Have Questions?

We're here to help you understand how your data is protected and used.