Reference
Security and privacy
What BambooKit stores, where, and how your devices and account are protected.
What is stored where
| Data | Where | Kept |
|---|---|---|
| Chats, tool steps, diffs, project files | Your PC | Until you delete them |
| Model API keys (also those added from the phone) | Your PC | Until you remove them |
| Profile statistics: coding-time intervals, per-session totals (files, lines, tests), achievements, project status | BambooKit Cloud | Until account deletion |
| Sign-in | Each device, encrypted (Windows DPAPI, Android Keystore) | Until sign-out |
| Session index: titles, project names and folder paths, status, model, change counts | BambooKit Cloud | Until deleted on the PC or account deletion |
| Approvals: what the agent asked (e.g. the command) and your answer | BambooKit Cloud | Kept as history |
| Devices: name, platform, version, the PC's public key | BambooKit Cloud | Until revoked or account deletion |
| Actions sent from the phone | BambooKit Cloud | Message text removed when done; record deleted after 15 minutes |
| Realtime events | BambooKit Cloud | 14 days |
| Shared sessions | BambooKit Cloud, public with the link | Until you unpublish |
| Profile photo | Private cloud storage under your account's folder | Until removed |
| Session history copy: prompts, timeline, changed lines (diffs), test commands | Private cloud storage under your account's folder, saved by your PC after each turn | 7 days after the last save |
Chats, full files and Before/After versions that your phone or this site reads pass through BambooKit Cloud in memory and are not saved. The history copy is the one place where your prompts and the changed lines are stored in the cloud, for 7 days.
How it is protected
- No open ports. The agent listens on 127.0.0.1 only. Your PC connects out to BambooKit Cloud; phones and this site never connect to the PC.
- Verified sign-ins. Every request carries a signed token from Supabase or Google (Firebase), checked against their public keys. BambooKit never sees your password.
- Device keys. Each PC signs every request with its own Ed25519 key, stored encrypted by Windows and never sent anywhere.
- Pairing. QR codes work once, for two minutes, and only for the same account. A phone can only act on PCs it is paired with.
- Fixed remote actions. The phone can stop a run, answer approvals and questions, start a session in a project, chat in a session after Continue on PC, rename sessions and add or remove provider keys. This site can answer approvals and questions, rename sessions and ask the PC to continue one. There is no remote shell and no remote file editing; everything the agent does still follows your permission rules on the PC.
- Provider keys from the phone are encrypted end-to-end to the PC's own RSA key (RSA-OAEP-SHA256 wrapping an AES-256-GCM key). BambooKit Cloud only relays the ciphertext, never writes it to the event log or stores it, and deletes it as soon as the PC answers. The key is never shown again.
- Stale actions never run. An action not delivered within 5 minutes is dropped.
- Folder boundary. Remote file views are limited to the session's project folder, including through links.
- Cloud storage. Only BambooKit Cloud holds the storage credentials; devices get links that expire after 5 minutes (photos: 1 hour), limited to their own account's folder.
- Revocation. Revoke a phone or PC at any time; its access ends immediately.
- Website. A static site with no server code, served with anti-framing and no-sniff headers. Shared-session pages escape all content.
Report a security problem
Do not open a public issue. Email bambookit.support@gmail.com with the details.