Privacy policy
Last updated on 23 September 2026.
tlwb is an instant, collaborative whiteboard that AI agents can draw on. This policy explains what personal data the service at tlwb.io collects, why, where it lives, and what you can do about it.
Who is responsible
The data controller is JDevelop, a French single-member limited company (EURL), 6 Place du Président Thomas Woodrow Wilson, 31000 Toulouse, France, registered in Toulouse under number 938 123 072. Questions and requests go to tlwb@jdevelop.io.
Drawing without an account
You can draw without signing up. An anonymous board is stored in your own browser (IndexedDB and local storage) and never reaches our servers until you share it. Your browser also keeps a random display name and colour for presence, and the keys of the boards you have opened, so you can find them again. Clearing site data removes all of it.
What we collect when a board is shared or hosted
- Board contents: the shapes, text, freehand strokes and images placed on a board, its name, and a thumbnail we render for the dashboard. Anyone holding a board's share link can read it; an edit link also allows changes.
- Presence: your display name, colour, cursor position and selection are relayed live to the other people on the same board. They are not stored.
- Server logs and rate limiting: your IP address is used in memory to enforce per-address limits, and appears in short-lived server logs.
What we collect when you sign in
- Account: the name, email address and avatar URL provided by GitHub or Google when you sign in, plus which of the two you used and the tokens they issue. We do not receive your GitHub or Google password.
- Sessions: a session identifier stored in a cookie, with the IP address and browser user agent seen at sign-in, so you can review and end sessions.
- Your boards: which hosted boards belong to your account, adopted from your browser when you sign up or created while signed in.
- API keys: keys you generate for MCP clients are stored hashed; we cannot show them again. Calls made with a key are counted per calendar month to apply your plan's quota.
- Billing: if you subscribe to Pro, your Stripe customer identifier and subscription status. Card details are entered on Stripe's pages and never reach our servers.
Why we process it
To provide the service you asked for (hosting boards, live collaboration, agent access, your subscription), which is the performance of our contract with you; to keep the service secure and fair (rate limiting, abuse prevention), which is our legitimate interest; and to meet legal obligations such as invoicing records.
We do not run analytics or advertising trackers, and we do not sell or share personal data for marketing.
Where it lives and who sees it
Hosted boards, accounts and sessions are stored on a server operated by OVH in France, within the European Union. Payments are processed by Stripe, which acts as an independent controller for the payment itself. Sign-in relies on GitHub or Google, under their own privacy policies. Agents you connect through MCP act with the links or keys you give them; what they read or write is between you and them.
How long we keep it
Hosted boards are kept until you delete them, or until the account that owns them is deleted; shared boards that belong to no account are kept so that their links keep working. Sessions expire after a period of inactivity. Account data is deleted when you delete your account from the dashboard, which also cancels any active subscription; billing records are kept for the period French accounting law requires. Rate-limiting counters live in memory only, and server logs are rotated within days.
Your rights
You can access, correct, export and delete your data. Most of it is directly in your hands: rename or delete boards, revoke API keys, manage your subscription, and delete your account, all from the dashboard. For anything else, or to object to a processing, write to tlwb@jdevelop.io. You can also lodge a complaint with the French supervisory authority, the CNIL.
Cookies
tlwb sets one cookie, the session cookie, only after you sign in. It is strictly necessary and needs no consent. There are no third-party or advertising cookies.
Security
Traffic is encrypted in transit. Share keys and API keys are stored hashed. Access to the production server is restricted to the operator. No system is perfectly secure; if a breach affects you, we will inform you as the law requires.
Changes
When this policy changes in a meaningful way, the date above moves and the new version is published at this address before it applies.