Designrail privacy policy
Last updated: 3 November 2026
Designrail (the browser extension, the designrail command-line tool, its MCP server and GitHub Action) does not collect, transmit, sell or share personal data or browsing data.
What the extension reads
When you open the side panel, press Rescan, scan a whole site or check a build, the extension reads the computed styles of the pages involved (colours, fonts, sizes, spacing, radii, shadows, CSS variables and stylesheet rules) and the length of text runs (not the text itself), plus the page title, its address, same-origin link addresses (for whole-site scans) and short element selectors such as button.btn-primary (for Check my build reports). Whole-site scans open same-origin pages in background tabs, read them the same way, and close them.
This happens entirely inside your browser. Nothing is sent to us or to any third party.
What the extension stores
In your browser's extension storage (chrome.storage.local), on your device only:
- design systems you save to the library, and their versions
- your licence key, if you enter one (checked offline, never sent anywhere)
- preferences such as the auto-rescan setting
Removing the extension deletes this data. You can also remove saved sites (in Saved) and the licence key (in Settings) at any time.
Files
Files are written only where you choose: downloads, or a project folder you pick with "Add to project…".
Permissions
Site access is optional and requested only when you use a feature that needs it (auto-rescan, whole-site scan, Check my build). You can revoke it in your browser's extension settings.
Purchases
If you buy a Pro licence, the purchase is handled by the store you buy from, under its own privacy policy. The licence key it sends you contains your email address and plan; it is stored only in your browser.
Contact
Questions: open an issue on GitHub