Privacy
What Drift and its Chrome extension send, where it goes, and how to remove it.
What this is
Drift compares a Figma design against the page you built. The comparison needs two
things: the design, and a recording of the page. The recording is made in your own
browser by the extension, because a page on localhost or behind a login
cannot be reached by any server — that is the reason the extension exists at all.
What the extension sends, and where
To this server and nowhere else. There is no analytics, no tracking, no third-party service in the path, and the server address is compiled into the extension rather than configurable — a field to type an arbitrary host into is exactly where a token gets sent to the wrong place.
| Data | Why | Kept |
|---|---|---|
| A recording of the page: a full-page screenshot, and every element with its computed styles, position and text | It is the thing being compared | Until you delete it. Every run is listed with its size under Storage, and Clear runs removes it |
| The page's address and title | To know which page a comparison is about | With the page, until you delete it |
| Your email address, and a password if you sign in with one | To have an account | Until the account is deleted. Passwords are stored hashed, never in the open |
| A sign-in token, held by the extension | So it can act as you without holding your password | In the browser, until you sign out |
| Your Figma personal access token, if you add one | To read the design's layers and render the frame | Encrypted on the server, never returned to the browser, removable in Settings |
What never leaves your browser
- The pasted-CSS comparison. Copy a layer's CSS from Figma, pick an
element, and the properties are compared against
getComputedStylein the page. Nothing is uploaded — it exists precisely for when nothing can be. - Your overlay colours, opacity, and where you dragged the design on each page.
- Your Figma or Drift password. The extension's sign-in either opens this site in a window and receives a token, or posts the password once to sign in — it is never stored by the extension.
Language models
Nothing is ever sent to a model unless you have added your own API key. With one, the only thing sent is the handful of design layer / page element pairs that geometry and copy could not tell apart — short records, a couple of dozen at most, not the page. Every measurement Drift reports is arithmetic and stays that way: a model cannot measure, and one is never asked to. Remove the key and nothing is sent again.
What is not collected
- Browsing history. Drift knows only the pages you deliberately added to a project.
- Keystrokes, mouse movement, clicks, or anything else about how you use a page.
- Payment or financial information. There is nothing to pay for here.
- Anything from pages you have not asked it to record. The extension captures on a button press, never in the background.
Sharing
Your data is not sold, and not transferred to anyone. The single exception is one you make yourself: a run can be given a share link, which makes that one report readable without an account until you revoke it.
Removing it
- Storage in the dashboard shows what is kept, per page, and clears a page's runs and their files.
- Deleting a page or a project takes its designs and recordings with it.
- Deleting your account removes everything belonging to it, files included.
- Signing out of the extension removes the token from your browser.
Where it runs
This is a self-hosted instance. Whoever operates the server at this address holds the data described above, and Drift sends it nowhere else. The source is available, so the claims on this page can be checked rather than taken on trust.