Privacy Policy
This policy explains how the locally operated bitshell application accesses and handles Google user data when sending email.
Data accessed
When a user authorizes a Google account, bitshell may access:
- the Google account email address used to verify the authorized identity;
- the recipient, subject, sender display name, and text or HTML body supplied by the user or the user's configured local agent;
- the ability to send that user-supplied message through Gmail; and
- OAuth access and refresh tokens required for authorized API requests.
bitshell does not read, list, modify, delete, or download existing Gmail messages.
How data is used
Google user data is used only to verify that an authorized account matches the account selected by the user and to send a message requested through the local application or a user-configured local AI agent. It is not used for advertising, profiling, surveillance, or sale.
bitshell does not transfer Gmail data to an AI model and does not use raw, derived, or aggregated Google user data to train or improve generalized or personalized AI models.
Storage and protection
bitshell runs on the user's own Windows computer. Account-to-environment mappings and authorization status are stored in a local SQLite database. OAuth refresh tokens are encrypted with Windows Data Protection API and can be decrypted only in the same Windows user context. Tokens, passwords, and message contents are not written to application logs or returned to the browser dashboard.
Sharing and transfer
bitshell does not sell Google user data or share it with advertisers, data brokers, AI model providers, or unrelated third parties. The outbound message is sent to Google and its intended recipient only as necessary to provide the user-requested Gmail sending feature. The local operator is responsible for the security of the computer on which bitshell runs.
Retention and deletion
Local account bindings and encrypted credentials remain until the user disconnects or unbinds the account, or deletes the local database. Outbound message content is processed for the send request but is not retained by bitshell after the command completes. Unbinding an environment removes its locally stored OAuth credential. A user may also revoke bitshell access at any time from the Google Account third-party connections page.
Google API Services User Data Policy
bitshell's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.
Contact
Privacy questions and deletion requests: qdman006@gmail.com.