Tracked Clixsy — Privacy Policy

Last updated: 2026-06-27

Tracked Clixsy is an internal Chrome extension that adds Kanban boards on top of Basecamp. It is operated by Clixsy for its own team. This page explains what the extension accesses and how that information is handled.

What the extension does

The extension displays your Basecamp to-dos as a Kanban board and lets you organize them into columns, labels, estimates, and ordering. That organizational data is stored in a backend server operated by Clixsy (the "Backend"). The extension does not send your data to any other third party.

Information accessed

• Basecamp content — project, to-do list, and to-do information (titles, assignees, due dates, comment counts, status) needed to render your board. This is read from Basecamp through the Backend using your authorized connection.
• Your board organization — the column, label, estimate, and ordering you assign to cards. Stored in the Backend so your board persists across sessions and is visible to your team.
• Authentication — a session token issued by the Backend is stored locally in the browser so you stay signed in. Sign-in uses Basecamp's OAuth via the Backend.
• Settings — the Backend URL and your display preferences (density, dark mode, filters) are stored in Chrome storage.

How information is used

Accessed information is used solely to provide the Kanban functionality described above. It is not sold, rented, or shared with third parties, and is not used for advertising, profiling, or any purpose unrelated to the extension's single purpose. The extension contains no analytics or tracking.

Where data is stored

Board organization data is stored in the Clixsy-operated Backend (a private PostgreSQL database). Authentication tokens and preferences are stored in your browser's local and sync storage. No data is transmitted to the extension's developers beyond the Clixsy Backend.

Data retention & removal

Data persists in the Backend until removed by a Clixsy administrator. You can clear local data at any time by removing the extension or clearing its storage in Chrome.

Permissions

• storage — save your Backend URL, session token, and display preferences.
• identity — start the Basecamp sign-in (OAuth) flow.
• Host access to 3.basecamp.com / app.basecamp.com — inject the board into Basecamp pages and read your to-dos.

Contact

Questions about this policy: bogdan@clixsy.com.