Privacy Policy — CodeKeeper

Last updated: October 17, 2026

Who we are

CodeKeeper is a code and document manager, available as a Telegram bot and as a web app. It is operated by Amir Biron. Contact: amirbiron@gmail.com

Google user data we access

Connecting Google Drive is optional. You connect it separately in the bot and in the web app.

CodeKeeper requests only one permission: https://www.googleapis.com/auth/drive.file. It lets CodeKeeper create files and folders in your Drive, and access only the files and folders that CodeKeeper itself created. CodeKeeper cannot see, read or change any other file in your Drive. It does not request access to your email address or to your Google profile.

How we use it

We use this access only to upload backup ZIP files of your own CodeKeeper content to a folder that CodeKeeper creates in your Drive, when you ask for a backup or on a schedule you choose. A backup contains your saved files; a backup from the web app also contains your collections, bookmarks, notes and settings.

To find its backup folder and to avoid uploading the same backup twice, CodeKeeper reads the names and basic details (such as checksums) of the files and folders it created. CodeKeeper never downloads or reads the content of any file in your Drive.

What we store

  • The OAuth access token and refresh token that Google issues for the connection, with their type, expiry time and the permission that was granted.
  • Your backup preferences and status: the schedule you chose, the ID of the backup folder, and the time and result of the last backup.

We do not store copies of your Drive files. This data is kept in CodeKeeper's database, hosted on MongoDB Atlas; the bot and the web app run on servers hosted by Render.

Sharing

We do not sell, share or transfer your Google user data to third parties, other than the hosting providers named above, which store it for us. We do not use it for advertising, and we do not use it to train AI or machine learning models.

Disconnecting and deletion

When you disconnect Google Drive in the bot or in the web app, CodeKeeper deletes the stored tokens of that connection right away, and from then on it cannot start new uploads to your Drive. In the web app, disconnecting also turns off scheduled backups. Backups that were already uploaded stay in your Drive until you delete them.

Disconnecting does not remove CodeKeeper's access on Google's side. To remove it there as well, visit https://myaccount.google.com/permissions.

Limited Use

CodeKeeper's use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

Changes

If this policy changes, we will update this page and the date at the top.