Privacy policy
Effective September 16, 2026
Information we access
When you connect Google, you authorize access through Google’s consent screen. Depending on the permissions you grant and the features you use, Lowkey Agent Email can access your account address, message headers and bodies, sender and recipient details, labels, threads and attachments. Sending and mailbox changes require the corresponding permissions.
If you separately connect other services, such as Calendar or Drive, access depends on those services’ permissions and your requested task. Connecting email does not itself grant permission to other Google services.
Your workspace also stores conversations, uploaded or downloaded files, generated results, account configuration and operational records. The public website and hosting systems may log technical information such as IP addresses, request times, requested pages and errors.
How information is used and shared
We use connected data to carry out the features you request: finding and reading messages, summarizing correspondence, working with attachments, preparing or sending authorized replies, organizing mail and running automations you enable.
For an AI-assisted task, relevant message content, attachments and conversation context may be sent to the AI provider configured for your workspace, such as Anthropic or OpenAI. That processing takes place outside your workspace host. Sending mail shares its contents with the recipients you authorize. A task may also transfer selected information to another service when you direct that workflow.
People with access to a shared workspace may see its conversations, files and results. Hosting, backup and AI service providers process information needed to deliver those services. Support personnel may access specific data with your permission, or when necessary to investigate security issues or meet legal obligations.
We do not sell Google user data or use it for advertising, credit decisions or unrelated profiling. Google user data must not be used to train general-purpose AI or machine-learning models. Workspace operators must use provider terms and settings consistent with that restriction before processing Google data.
Lowkey Agent Email’s use and transfer of information received from Google APIs follows the Google API Services User Data Policy, including its Limited Use requirements.
Storage and protection
Mailbox data stays with your email provider unless a requested operation changes it. Copies of message content, attachments or derived information may also be retained in workspace files, conversation history, logs and backups. AI providers may retain submitted information under the terms and settings of the configured service.
Google handles your Google sign-in; Lowkey Agent Email does not ask for your Google password. OAuth credentials are stored on the workspace host in a credential store or restricted local files, depending on the deployment. API connections use HTTPS. Access controls and deployment protections reduce risk, but no system can guarantee absolute security.
Retention, revocation and deletion
OAuth credentials are retained to maintain your connection until they are removed or become unusable. You can revoke the application’s Google access through your Google account connections. Revocation stops future authorized access; it does not automatically erase copies already stored in your workspace.
Ask your workspace operator to disconnect the account and delete downloaded mail, attachments, conversation records or other retained copies. You can also contact us below for help. Retention and backup expiration depend on the deployment; there is no single automatic deletion period for every workspace. Copies may persist in backups until those backups expire, and information may be retained where legally required. Deleting a local copy does not delete the original email in Google.
Contact and updates
For privacy questions, access or deletion requests, contact sourcheeks@gmail.com, the support contact for this Google application. Identify the workspace and account involved; do not send passwords or access tokens.
We update this page when practices change and revise its effective date. Material changes to Google data use will be disclosed before that new use begins, with additional consent where required.