Privacy Policy — CodeKeeper
Last updated: November 15, 2026
Who we are
CodeKeeper is a code and document manager, available as a Telegram bot, as a web app, and as a connector that AI assistants such as Claude can use (see The CodeKeeper connector for AI assistants). 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.
The CodeKeeper connector for AI assistants
CodeKeeper offers a connector, built on the Model Context Protocol (MCP), that lets an AI assistant you choose, such as Claude, work with your own CodeKeeper content: your saved files and their versions, your collections, and your sticky notes and boards. This section explains what happens to your data when you use it.
Connecting and access
You connect the connector yourself. When you add it to your AI assistant, you sign in to CodeKeeper with Telegram and approve the access on a consent screen. Access is read-only unless the assistant asks for write access and you approve it on that screen. If you use Claude Code with a personal access token from the CodeKeeper bot (/connect_claude), the token is read-only unless you ask the bot for a write token. The connector only ever works on your own account: it knows who you are from the sign-in or the token, never from what the assistant sends.
With write access, the assistant can create files, save new versions of your files, change a file's description, add a file to a collection, and create and edit sticky notes. The connector has no way to delete your files, notes or collections.
What the connector receives
The connector only receives what the assistant sends to it: tool requests, such as "read this file" or "save this text as a file"; text the assistant uploads so that it can be saved as a file; and technical details that the assistant's app reports about itself, such as its name and version. It answers with the content you asked for, and it has no access to the rest of your conversation with the assistant.
The connector asks the assistant to describe its task in one place only: when the assistant comments on a sticky note, it writes in one short sentence, up to 60 characters, what it is working on. That sentence is saved with the comment (see What we store). Content the assistant reads through the connector becomes part of your conversation with that assistant, and from there it is handled under the assistant provider's own privacy policy (for Claude, Anthropic's).
What we store
- What the assistant saves through the connector (files, versions, descriptions and sticky notes), stored like any other CodeKeeper content. A comment that the assistant writes on a sticky note is saved together with the name that the assistant's app reports about itself, such as "claude-code", and with the sentence the assistant wrote about what it is working on; both are shown next to the comment.
- The sign-in tokens of the connection. We store only a SHA-256 hash of each token, never the token itself. An access token expires after 1 hour and a refresh token after 30 days; using a refresh token replaces it with a new one. Expired token records are deleted automatically.
- The registration details that your assistant's app sends when it first connects, such as its name and the addresses it returns to after sign-in.
- If you created a personal access token in the bot: a hash of the token, its first few characters so that tokens can be told apart, its name, its permissions, and when it was created and last used.
- Text that the assistant uploads to the connector's upload address so it can then save it as a file. It can be used for up to 10 minutes, and it is deleted when it is used or when it expires.
Usage analytics
To learn which tools are used, how fast they are and how often they fail, the connector sends usage events to PostHog, our analytics provider. An event includes the tool's name, how long the request took, whether it failed and the type of error, the name, version and user-agent string of the assistant's app, and a random ID of the connection session. It does not include your CodeKeeper user ID, and PostHog does not build a profile of you from these events.
The events never include what the assistant sent to a tool or what the tool returned, so the content of your files and notes stays out of them. Two kinds of free text can be included: when a request fails, its error message, after we filter out known formats of keys and tokens (the message can still contain part of the request that caused the error); and when the assistant reports a capability it is missing (the get_more_tools tool), the sentence it writes about what it needs.
Logs and notifications
Our servers keep technical logs to run the service and fix problems, such as which operation ran, how long it took, data sizes and your CodeKeeper user ID. The logs are stored by our hosting provider, Render, according to its log retention.
If you turned on browser notifications in the web app, you get a notification when the assistant saves a file or comments on a sticky note through the connector.
Sharing
We do not sell your data, and we do not share it with third parties other than the providers named on this page, which store or process it for us: MongoDB Atlas (the database), Render (servers and logs) and PostHog (usage analytics, without your content). We do not use your data for advertising, and we do not use it to train AI or machine learning models.
Disconnecting and deletion
You can remove the connector in your AI assistant's settings at any time. The tokens that the assistant's app held stop working when they expire (1 hour for an access token, 30 days for a refresh token), or sooner if the app revokes them. A personal access token from the bot does not expire on its own; to revoke one, contact us.
Content created through the connector is ordinary CodeKeeper content, and you can delete it in the bot or in the web app. To ask us to revoke your connector access or to delete your data, contact us at the address in Who we are.
Changes
If this policy changes, we will update this page and the date at the top.