Skip to content
Rohit Behera

Privacy

These tools run on my machine
and send data nowhere.

This policy covers the personal command-line tools I publish, including gmail-cli, which uses Google’s Gmail API. There is no server, no account to create and no analytics.

What is collected

Nothing is collected by me. These tools are run locally by the person who installed them. They have no backend, transmit no telemetry, and I have no ability to see what anyone does with them.

Google account data

gmail-cli asks for two Google OAuth scopes:

  • gmail.modify — read, search and label messages in the mailbox that authorised it.
  • gmail.send — send messages from that mailbox.

It does not request permission to delete anything. Message content is read into the local process only to display it in your own terminal, and is not written anywhere except where you explicitly ask the tool to save it.

Google account data obtained through these scopes is never transferred to anyone, and is not used for advertising, profiling, resale, or to train any model. Use of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements.

Where credentials live

Authorising the tool writes an OAuth token to a file on your own computer, readable only by your user account. It never leaves that machine. Deleting the file removes the tool’s access locally.

You can revoke access at any time, independently of me, at myaccount.google.com/permissions. Revoking takes effect immediately.

Children

These are developer tools and are not directed at children under 13.

Questions about any of this?

Ask me directly. Last updated 11 September 2026.

rohit.behera12232@gmail.com
loading index…Full retrieval trace →