
Runbay Privacy Policy
Last updated: 19 November 2026
Runbay is a personal, local-first developer tool run by Aman Bansal on their own computers. This policy covers the Google OAuth app named "Runbay" and the Google user data it can read.
What data is accessed
When the owner signs in with Google, Runbay asks only for read-only access: Search Console, Analytics, Gmail, Drive, Sheets and Calendar, plus the account's email address and sign-in identity. Runbay cannot send email or create, change or delete anything in a Google account.
How it is used
The data is used only to show the owner their own information inside their own Runbay, for example search performance or calendar events next to their work. It is not used for advertising, profiling or training models, and no person other than the owner reads it.
Where it is stored
- Data stays on the owner's own machines where Runbay runs. There is no Runbay server or cloud copy.
- The OAuth tokens are kept encrypted in Runbay's local vault (AES-256-GCM), unlocked by a key file that stays on that machine.
- Data read from Google is fetched by the owner's own Runbay and is not uploaded anywhere.
Sharing
Google user data is never sold, transferred or disclosed to third parties. Runbay's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.
How to revoke access
You can remove Runbay's access at any time at myaccount.google.com/permissions: choose "Runbay" and remove access. Runbay then can no longer read anything. A revoked token stops working at once, even if a copy remains in the local vault.
Contact
Questions about this policy: khanakia@gmail.com.