Effective 29 October 2026.
1. Who we are
Design System Census is a design system adoption and governance service for Figma teams, made of a Figma Community plugin and a small server. It is run by I Don't Know OÜ, Ahtri tn 12, 15551 Tallinn, Estonia, registry code 16915948, VAT ID EE102748956 ("we", "us"). Contact for anything about privacy: hello@designsystemcensus.com.
We, not Figma, are responsible for the data we collect through Design System Census. Design System Census is not made, endorsed or operated by Figma. Figma's own privacy policy covers your use of Figma.
2. The short version
- The free audit in the plugin ("This file") runs on your computer and sends us nothing at all.
- If you sign in, we receive derived data about your files: counts, keys, IDs, and the names of files, folders and library assets. We never receive or store the content of your designs.
- Your data is hosted in the EU (Frankfurt, Germany).
- You can remove files, delete your account or delete your workspace in the plugin at any time, and the deletion happens at once.
- We do not sell data, do not use it for advertising, do not profile you and do not use it to train AI models. We use no tracking cookies or analytics.
3. Our role: processor for your workspace, controller for accounts
| Data | Who decides what happens to it (controller) | Our role |
|---|---|---|
| Workspace data: members' Figma IDs and handles, who scanned what and when, file, folder and library asset names, usage counts and findings | The organization that uses the workspace (the customer) | We are its processor: we process this data only to provide Design System Census, on the customer's instructions (our terms and the settings in the plugin). A data processing agreement (DPA) is available on request. |
| Data we need to run and secure the service: owner accounts and email addresses, sign-in data, security and request logs | Us | Controller |
| Your design files in Figma | You or your organization, under your contract with Figma | Figma is not our sub-processor, and we do not store your design files |
| The free audit | Nobody: we receive nothing | — |
If you are a member of a workspace and have questions about the workspace data, you can contact the workspace owner or us; we forward requests about workspace data to the customer and help them answer.
4. What we collect, why, and for how long
4.1 The free audit
Nothing. The audit reads the open file inside Figma on your computer, shows the result, and makes no network requests, not even error reports. It saves nothing.
4.2 When you sign in and use a workspace
| # | Data | Where it comes from | Why we use it | How long we keep it |
|---|---|---|---|---|
| P1 | Your Figma user ID and handle | Figma, when you sign in | To identify you, show the member list and who scanned which file | Until you delete your account. Then your record is anonymized: the handle becomes "Deleted user" and the Figma user ID and email are removed. If you leave all workspaces but scans you made are still stored, we keep only an internal ID and your handle while those scans exist, then anonymize the record the same way. |
| P2 | Your email address, only if you own a workspace | Figma, when you sign in or create a workspace | Security, service and DPA notices; checking who owns a workspace | While you own a workspace. Members' email addresses are never stored. |
| P3 | Your Figma sign-in: an access token and a refresh token from Figma, with the permissions you granted; or, in the invite-only test version (the friends alpha), the read-only personal access token you paste into the plugin | Figma, when you sign in; for the test version, you | To check who you are, and to check a file link you paste: that you can open the file, and its name and folder. During the beta the refresh token is stored but not used. | Until you sign out, delete your account, leave all workspaces, or the sign-in stops working. Stored encrypted. |
| P4 | Sign-in session (a scrambled copy of the session key, with creation and last-use times) | Generated by us | To keep you signed in to the plugin | Expires after 90 days without use; deleted when you sign out or delete your account, or when an expired session is next used. |
| P5 | Sign-in handshake (a temporary record linking the plugin and the browser while you sign in) | Generated by us | To complete sign-in safely | Deleted after use; an unused one expires after 10 minutes and is removed soon after. |
| P6 | Workspace name and settings | The workspace owner | To run the workspace and its limits | Until the workspace is deleted. |
| P7 | Memberships, roles and invite codes (codes stored only in scrambled form) | Actions of the owner and members | To control who can see and change the workspace | Until a member is removed or the workspace is deleted; your own memberships go when you delete your account. |
| P8 | Projects: the names of Figma folders that hold tracked files | Figma file information, when a file is added | To group files | Until the workspace is deleted. Removing a file does not remove its folder's name, even when no other tracked file is in that folder. |
| P9 | Tracked files: file key, file name, project, whether it is a library or a draft, who added it, when it was last scanned and by whom | The pasted file link and Figma file information | To list tracked files and show how fresh the numbers are | While the file is tracked; deleted at once when the owner removes it. |
| P10 | Library components: what your libraries publish (keys, names and descriptions of a library's published components, component sets, styles and variables, how they are grouped, whether they are published, which properties each variable is meant for, and whether each style uses variables), and the keys and names of the library components placed in scanned files, including ones from libraries you don't track, such as Figma's UI kits, Community libraries or another team's library | Scans of library files, for what they publish; scans of any tracked file, for the library components placed in it | To name library components, count their use, list the ones from libraries you don't track, and match lookalikes | Until the workspace is deleted. Removing a file does not delete them: if a library file is removed, what it published stays without a library, so other files' usage stays correct, and the components placed in a removed file stay with the names its scans saw. |
| P11 | Scans: who scanned, when, plugin, analyzer and counting-rules versions, Figma Design or Dev Mode, number of layers, duration, file-level counts, and how many of a file's colors, text styles, effects and grids use a variable, a style or a raw value (counts only: never the values, the names of variables or styles, or layer names; in a library file, counted per component) | The plugin | To show freshness and usage numbers, and to fix problems, and to check how much of your designs use your variables and styles | Until the file or the workspace is removed. |
| P12 | Usage history: per file, the counts of component instances (placed directly, and placed inside other components) and of detached copies, valid from one scan to the next | Derived from scans | To show usage and how it changes over time | Until the file or the workspace is removed. |
| P13 | Findings: type (local lookalike, detached copy or raw value), the layer's ID and, for lookalikes and detached copies, its name, confidence and details. A raw-value finding is a capped list (500 per scan) of layer IDs with the kinds of properties (such as fill or gap) that hold a raw value instead of a variable or style; never the values or layer names | The plugin | To list local lookalikes and detached copies and to show where raw values remain | Until the file or the workspace is removed. |
| P14 | Request logs, including IP addresses, and a record of each deletion that names only internal IDs | Our hosting provider; the deletion records are written by our service | Operations, security and abuse prevention, and repeating deletions if we ever have to restore a backup | Under the hosting provider's log retention (7 days during the beta). IP addresses are not stored in our database. |
| P15 | Your session key on your computer | The plugin's local storage in Figma | To keep you signed in | Until you sign out, or Figma clears plugin storage. |
| P16 | A small hidden label in each scanned Figma file: workspace ID, file ID, file key and name | Written by the plugin into the file's plugin data | To recognize the file on the next scan | Stays in your Figma file. If the owner removes the file from the workspace while it is open in the plugin, the plugin also removes the label where it can (Figma may not allow it in a view-only file). Otherwise, after a removal we no longer recognize the label and it has no effect; a new first scan replaces it. |
| P17 | The date of the last scan, shown under the Rescan with Design System Census button in each scanned Figma file | Written by the plugin into the file after each saved scan | To show people in the file when it was last scanned | Stays in your Figma file; each saved scan replaces it. It names no one. If the owner removes the file from the workspace while it is open in the plugin and no other workspace has scanned the file, the plugin removes the button and its date where it can. |
| P18 | The size of the plugin window, two numbers (width and height) | The plugin, when you resize the window in Figma Design | To open the window at the size you last gave it | On your computer only, in the plugin's local storage in Figma, until Figma clears plugin storage. Signing out does not clear it, because it names no one. We never receive it. |
| P19 | Components marked Meant to be detached: the component's key, who marked it and when | The workspace owner, in a component's details in the plugin | To show that component's detached copies as expected | Until the owner removes the mark, or the workspace is deleted. Removing a file does not remove it. |
| P20 | The workspace you last opened, on your computer: its ID and name | The plugin's local storage in Figma | To open the same workspace next time, and show its name while it opens | Until you sign out, delete your account or lose access to that workspace, or Figma clears plugin storage. |
| P21 | The Start tabs you hid, on your computer: workspace IDs | The plugin's local storage in Figma | To keep a Start tab (Get started) you hid hidden | Until you sign out or delete your account, or Figma clears plugin storage. |
| P22 | The word that marks a deprecated component, where to look for it (the name, the description or both) | The workspace owner, in Settings in the plugin | To show which components your team has marked as deprecated | Until the owner changes it, or until the workspace is deleted. |
| P23 | What your team checks in the variable and style check: for each property group (fill, stroke, corner radius and so on) whether it counts, and a few switches, with the dates of the changes and who made them | The workspace owner, in Settings in the plugin | To count how many properties use your design system's variables and styles | The current setting until the owner changes it; earlier settings and the dates of changes until the workspace is deleted. Removing a file does not remove them. |
4.3 When you ask to join the alpha
| # | Data | Where it comes from | Why we use it | How long we keep it |
|---|---|---|---|---|
| P24 | Your name, work email, company or team and role; your team's Figma plan, your seat, whether your team publishes its own library, whether you can use the Figma desktop app, and anything else you tell us | You, in the request form linked from Ask to join | To decide whether the alpha fits your team, and to reply | Until the alpha ends, or sooner when you ask. We then delete it from the form service, our inbox and Slack. |
4.4 What we never collect or store
- The content of your designs: layers and their properties, text, images, thumbnails, exports, fonts, prototypes, comments or version history.
- Raw design values such as colors, sizes or type settings.
- Layer names, except the names of layers listed as local lookalikes or detached copies.
- From Figma's file information: who last edited a file, its creator, its thumbnail, its link-sharing setting or your role in it.
- Email addresses of members who do not own a workspace.
- Passwords (you sign in with Figma).
- Figma personal access tokens, except in the invite-only test version, where you sign in with a read-only personal access token instead (row P3).
- Payment details: the beta is free and collects none.
- IP addresses in our database.
- Anything from the free audit.
4.5 Cookies and tracking
We use one cookie, on the sign-in pages only, to connect your browser to the plugin while you sign in. It lasts at most 10 minutes. We use no analytics, advertising or tracking cookies and load no third-party scripts.
5. Legal bases (GDPR Art. 6)
- Workspace data: we process it as a processor for the customer, which chooses the legal basis (typically its legitimate interest in running its design system). We follow only the customer's documented instructions (GDPR Art. 28).
- Owner accounts and the beta terms: performance of a contract (Art. 6(1)(b)).
- Requests to join the alpha: steps you ask us to take before a contract (Art. 6(1)(b)).
- Security logs and abuse prevention: our legitimate interest in keeping the service and your data secure (Art. 6(1)(f)).
- Records we must keep by law: legal obligation (Art. 6(1)(c)).
We do not rely on consent, process no special categories of data and send no marketing.
6. Where your data is stored, and who helps us
All data in our service is hosted in the EU, in Frankfurt, Germany. Requests to join the alpha (row P24) never reach our service: they go through the form service, the automation service and Slack below, and arrive in our inbox.
| Sub-processor | What it does | Location | Company based in |
|---|---|---|---|
| Render (Render Services, Inc.) | Hosting of our server, database and its backups | Frankfurt, Germany | United States |
| Tally | The form for requests to join the alpha, and the email that tells us about a new request | EU | Belgium |
| Make | Passes a new request to our Slack | EU | Czech Republic |
| Slack | Shows us a new request in our own workspace | United States | United States |
Render and Slack are US companies. Render's staff may access systems from outside the EU for support, and Slack stores the request notifications in the United States. Both are covered by the provider's data processing agreement and a recognized transfer mechanism (Standard Contractual Clauses or the EU-US Data Privacy Framework).
Figma is not our sub-processor. Our server sends your Figma sign-in and a file key to Figma to read the name and folder of a file you added, which you already keep in Figma.
7. Deleting your data
Every deletion below takes effect at once, in the plugin, and cannot be undone.
| What you do | Who can do it | What happens |
|---|---|---|
| Sign out (Settings › Account; it signs you out on every computer) | You | All your sign-in sessions, on every computer, and the Figma sign-in we stored for you are deleted; the plugin forgets your session. Workspace data is not changed. |
| Remove our app in Figma (Figma › Settings › Security › Connected apps), or, in the test version, revoke your personal access token (Figma › Settings › Security › Personal access tokens) | You, in Figma | Our next call to Figma with your sign-in fails; we then mark it invalid and delete it. |
| Remove a member | The workspace owner | The membership is deleted and the member loses access at once. Their Figma sign-in is deleted if they belong to no other workspace. Scans they made stay in the workspace's history with their handle; once they belong to no workspace, their record keeps only an internal ID and handle while those scans exist, then it is anonymized. |
| Remove a file | The workspace owner | The file's scans, usage history and findings are deleted. For a library file, the library is removed too, but what it published (row P10) is kept without a library so that other files' usage stays correct. The label in the Figma file stays but is ignored, and the date under the Rescan button stays until the file is scanned again, unless the file is open in the owner's plugin: then the plugin also removes, where it can, the label and, when no other workspace has scanned the file, the Rescan button with its date. |
| Delete your account | You | Your sessions, Figma sign-in and memberships are deleted. Your record is anonymized: your handle becomes "Deleted user", and your Figma user ID and email are removed. Scans you made stay in the workspace, no longer naming you. A workspace owner deletes the workspace first (or asks us for help). |
| Delete the workspace | The workspace owner | All workspace data is deleted, and all members lose access at once. |
Backups. Deleted data stays in our database backups until they roll off, which during the beta takes at most 3 days. If we ever had to restore a backup, we would repeat every deletion made after the backup was taken before the service reopens.
If we stop using Figma's platform, we stop all calls to Figma and delete every Figma sign-in we hold.
8. Your rights
Under the GDPR you have the right to access your data and receive a copy (portability), to correct it, to have it erased, to restrict or object to its processing, and to complain to a supervisory authority.
- Access and copies: ask us at hello@designsystemcensus.com and we send you your account data, or, for a workspace owner, the workspace's data.
- Correction: your handle and email come from Figma and update the next time you sign in.
- Erasure: use Delete account in the plugin (Settings › Account), or ask us. Workspace owners can remove members and files themselves.
- Restriction and objection: contact us; for workspace data we handle this with the workspace owner.
- Workspace data: if you ask us about data in a workspace, we forward your request to the customer that controls it without undue delay, and help them answer.
- Timing: we answer within one month (GDPR Art. 12(3)).
- Complaints: you can complain to your local data protection authority, or to the authority where we are established: the Estonian Data Protection Inspectorate (Andmekaitse Inspektsioon, Tatari 39, 10134 Tallinn, Estonia).
9. Security
We encrypt every Figma sign-in we store (AES-256-GCM, with a key kept outside the database), store only scrambled copies of session keys and invite codes, use HTTPS everywhere, check on every request that you belong to the workspace you access, and limit who on our side can reach production data. If a security incident affects your data, we tell the affected customers without undue delay and the authority where the law requires it.
10. Children
Design System Census is a professional tool and is not meant for children under 16.
11. Changes to this policy
We will update this policy before Design System Census processes data in a new way, and tell workspace owners in the plugin at least 30 days before a change that affects them takes effect. The date at the top shows the current version.
12. Contact
I Don't Know OÜ, Ahtri tn 12, 15551 Tallinn, Estonia, hello@designsystemcensus.com.