What we collect, why, and the large parts of your work we never see. Written in English; the English text governs.
Last updated: 4 October 2026.
Fucini Consulting, Reg. No. 46062728, 04053 Kyiv, Nestorivskyi Lane, Building 10, Office 2/1, Ukraine. We are the controller for the data described here.
Privacy questions: support@fucini.software. General enquiries: info@fucini.consulting.
Paddle.com Market Limited acts as merchant of record for every purchase. They collect and process your payment details; we never receive or store your card number. Paddle tells us your email address, your name if you gave one, your country for tax purposes, and the status of your subscription. See Paddle's privacy notice for what they do with it.
From that we create an account on this site so you can reach your licence, holding your email address, a hashed password once you set one, and the identifier that links you to your subscription. We use it to deliver your activation code, to let you manage seats, and to contact you about the service.
When you activate the extension it sends a request code derived from the machine you are activating on. We store a fingerprint derived from it, so a seat can be tied to a device and freed again later. We store the seats in your pool, when each was last seen, and the email address of anyone you invite to one.
Along with the request code go the extension and VS Code versions, your operating system with its release and architecture, and VS Code's display language, and our web server records the address the request came from. We do not receive your machine's name, your username, or anything about your projects as part of activation.
Team plans (Pro Plus, Business and Enterprise) check in every twelve hours so the seat can be verified and its key renewed. That check-in also says which machine holds the seat: an install identifier, the VS Code and extension versions, and the machine’s time zone. Our web server records the address it arrives from, and a country where our host provides one. This is what lets whoever pays for the seats see which machines are using them, and free one up. It applies to team plans only, and what the free tier sends instead is described next. An individual Pro licence holds no seat and checks in nowhere: it works offline. The one exception is its renewal — from seven days before the key expires until forty-five days after, and only in that window, the extension asks our licence server every twelve hours for the renewed key, so that a paid renewal arrives without you doing anything. That request carries the request code the key was issued against, the machine fingerprint, the extension and VS Code versions, your operating system and its release and architecture, your editor language and the plan; our web server records the address it arrives from. None of this is affected by the telemetry setting below, and we keep only the most recent check-in for each seat rather than a history of them.
Every install reads the minimum supported version from our licence server about once a week (from version 1.2026.1). It is a download of one public, signed file and sends nothing about you: no request code, no install identifier, no version and no key. Our web server’s access log records the address it arrives from, as for every request to this site.
The trial and the free Community tier keep a usage ledger with us (from version 1.2026.0). The evaluation period and the free weekly allowance are limits, and a limit kept only on your own machine is reset by deleting a file. So while an install is on the trial or on Community it tells our licence server, shortly after it starts, after a counted action and twice a day: a hash of VS Code’s machine identifier — hashed together with a fixed label of ours, so that it matches no value any other product holds; that label is part of the extension rather than a secret, so what protects the identifier is that a hash cannot be reversed — the edition, the day the evaluation began, and how many of each counted action (reports, exports, comparisons, threshold checks, annotated-source views, coverage loads) have been used in the current week or day. The server answers with the same figures as it holds them, and the extension uses whichever is higher.
The ledger holds no name, no email address, no file path, no coverage figure and nothing about your projects. The ledger has no field for the address a report arrives from and never reads it; our web server’s access log records that address, as it does for every request to this site, and we do not join the two. The machine hash is a pseudonymous identifier: we cannot turn it back into anything, but it does single out one machine, which is why it is listed here. If you take the 30-day telemetry trade described below, the ledger also records that this machine has used it. A paid licence never reports to the ledger, and the extension never waits for it: offline or behind a firewall, it simply runs on the counters it has. It relies on our legitimate interest in keeping the limits of the free tier meaningful; you can object by writing to us. Because the ledger knows a machine only by that hash, the extension shows it to you — as the usage ledger ID, under Show License / Activation and under What Community Includes — so that you can quote it. With it we will tell you what the ledger holds for your machine, delete it, or record your objection; after an objection the ledger stores nothing further for that machine, keeping only the hash and the fact that you objected, and the extension stops reporting. The ledger is licence administration, like the seat check-in above: the telemetry settings do not switch it off.
From version 2.2026.2: an install also sends a second hash, made the same way, of the operating system’s own machine identifier together with the computer’s name — or, where the system has none, of its network cards’ hardware addresses. Only the hash leaves the machine, and the ledger treats a report that matches under either hash as the same machine. A new install’s trial begins with the ledger’s first answer; until the licence server has been reached once it runs on the Community tier, and after that nothing waits for the ledger. In a development container or a Codespace no trial begins and the second hash is not sent. An objection or a deletion request covers the machine under both hashes.
If you ask for a free student licence we store what the form asks for: your name, your email address, your school and its address, what you are studying and which year you are in. We use it to decide whether to grant the licence and to issue it, and we ask for the school's address rather than yours — where you live plays no part in the decision, so it is not a field we have.
If your email address is not one we can recognise as a school's, we will ask you to show us a student card photographed together with your face, or — if you have no card — a letter from the school. You may black out anything else on it: a student number, a date of birth, the photograph on the card. Only your name and the name of the school need to stay readable, because those are the only two things we look at. We rely on your consent for this, and you never have to send one: write to us instead and we will find another way. What you send is deleted the moment we have decided, and after 30 days in any case even if nobody has looked at it. It is never included in a backup, it is never reachable from the web, and the location data a phone writes into a photograph is removed the moment it arrives. Only the two people who administer licences here can open one, and each time one is opened is recorded. We keep the decision and the fact that you showed a card or a letter — never the picture.
If you join the pre-release channel — the Test pre-release builds button in the Coverage view — the daily licence message above adds one field saying so, and one short message is sent at the moment you join and again when you leave. That is how we know how many people are testing and can tell them what changed. It is your consent, asked for in the dialog where you join, and it is the only reason that field exists; leaving the channel stops it. Nothing else is added: it says which builds this installation receives, in the same way the ping already says which edition it is, and nothing about you or your work.
Coverage Studio can report usage back to us to help us improve it. The usage summary is disabled by default and is not sent until you switch it on. A handful of much smaller pings go out either way: one when the extension is installed, one short licence message a day, and — as separate pings from older versions, inside that daily message from current ones — a set of coverage formats loaded for the first time, a tracefile that would not parse, a licence change and an update. With the summary on, uninstalling also sends a removal notice with how many days the extension was installed. We describe all of it in full rather than calling it anonymous. Between them they contain:
Every install sends one short message a day, even with telemetry switched off. It carries the extension version, the edition (Pro or Community) and the licence state — trial, licensed, expired or Community — with the days left and the expiry date where there is one, and, if you hold a licence, its plan and the request code it was issued against. It carries no usage: nothing about what you loaded, which commands you ran or how often. It tells us how many installs are in use and when a trial or a licence is about to run out.
Coverage Studio for Visual Studio sends the same pings, under the same rules. One when it is first started, the one short licence message a day, and — only if you switch fuciniCoverage.telemetry.enabled on in its settings — the usage summary. Where this page names VS Code, read Visual Studio: its version stands where VS Code's would, the edition is given as Visual Studio, and the install identifier is its own, not VS Code's. It sends no error reports.
Coverage Studio on the command line sends one message, once. The first command run on a machine sends a random install identifier, the version and the operating system (platform, release, architecture), so installs can be counted; the country is taken from the address it comes from, as for the editions, and the install record is kept like theirs. Nothing about your code, your reports, your folders or you, and nothing after that first message. It is never sent in a CI pipeline, and FUCINI_COVERAGE_TELEMETRY=off, DO_NOT_TRACK=1 or fuciniCoverage.telemetry.enabled set to false in its settings file turns it off.
If your install holds a licence, what it sends is linked to the account that bought it. We match the request code to the purchase, so Fucini’s administrators see that daily licence message — and, if you have switched telemetry on, your install’s usage — beside the customer and the subscription it belongs to. It is deleted on the same schedule as the rest of telemetry.
When something in Coverage Studio fails, the extension sends an error report, even with Coverage Studio’s telemetry setting off — unless VS Code’s own telemetry level (telemetry.telemetryLevel) is set to crash or off. It contains no file content: the error code; the error message, with names, paths and addresses removed; where in the extension it happened; which parsers looked at the file and why each turned it down; facts about the file — its extension, a size range, its encoding, whether it is compressed or binary, the name of an XML file’s root element or of a JSON file’s top-level keys, and the shape of its first line with letters and digits masked; how often the error happened; and the install identifier, versions, edition, operating system and licence state described above. It relies on our legitimate interest in finding and fixing what breaks, and you can object by writing to us.
You can also choose to send a diagnostic report from the notification that follows a failed load. It shows exactly what will be sent before you send it: the same facts, a comment and an address for our reply if you want one, and — only if you tick the box — the first 4 KB of the file. Nothing is sent until you click, and ignoring the notification sends nothing beyond the automatic report above. A diagnostic report relies on your consent.
Installs that unlocked all features in exchange for telemetry, or that hold a student licence, and that accepted the current terms, send the first 4 KB of a file that fails to load with its error report automatically, without asking each time. An install that has not accepted the current terms sends no file content this way.
Our web server also records the IP address the ping came from, as any web server does, and the country, region and city that address resolves to. We work those out ourselves — your address is never sent to another company to look up — and we use them only to count how many installs are in each place. The region and city are derived from the address alone and are approximate: they describe where your internet provider routes that address, which can be somewhere other than where you are. The country, region and city worked out this way are also written once into the install record described under “How long we keep it”, which is kept rather than deleted after 90 days; the address they came from is not.
Some of the above identifies you or your machine. The usage summary and the removal notice are opt-in: we rely on your consent, and you can withdraw it at any time by turning telemetry off in settings, which stops both. The small pings, the daily licence message among them, rely on our legitimate interest in knowing how many installs are active, which versions are in use, when a trial or licence runs out and whether coverage files fail to load. Turning telemetry off does not stop them, but you can object by writing to us, and we will delete what your install has sent.
We do not send your source code, your file paths, or your project’s name. There is one exception: the first 4 KB of a file that failed to load, sent with an error report as described above — when you tick that box in a diagnostic report, or automatically from an install on the Community unlock or a student licence that accepted the current terms. It cannot be switched on by enabling telemetry alone, and a paid licence never sends file content unless you attach it to a diagnostic report yourself. Until September 2026 there was a second exception: the Community unlock also sent one randomly chosen file’s annotated source each month, with that file’s path. That collection has been withdrawn — no install sends it, nothing new is stored, and what had been kept has been deleted.
On the free Community tier you can trade telemetry for every Pro feature, MC/DC included, for 30 days, once per machine, by running Unlock Full Features in the extension (until version 0.2026.82 the trade lasted for as long as telemetry stayed on, and installs that made it then keep what they were given). It asks for your email address, so that we can tell you about the data your install sends and delete it if you ask us to. That is a trade you opt into, not a condition of using the extension: with telemetry off, Community keeps working with its standard feature set. A paid licence never depends on this — its features are unaffected by your telemetry setting, and the source sample above is never reachable from one.
The questionnaire is voluntary and is never a condition of getting a licence: keys are issued on request without it, and your answers play no part in that decision. If you do fill it in, we keep what you submit — your name, email, company and your answers — so we understand who is using the product and can improve it, and so we can issue the reward key where one applies.
If you subscribe we store your email address and your confirmation status, and nothing else. Every message carries an unsubscribe link, and unsubscribing removes you.
We set one functional cookie to remember your language choice. With your permission we use your approximate location, derived from your IP address, to suggest the right country — that is the only thing the consent prompt asks for, and declining it costs you nothing but the suggestion.
We do not use advertising cookies and we do not track you across other sites.
Ask us to delete something and we will, unless we are required to keep it.
We do not sell your data and we do not share it for advertising. It reaches only:
fuciniCoverage.update.checkForUpdates off to stop it;Our servers are in the EU. We are established in both the Netherlands and Ukraine, and data reaches us in both — including in Ukraine, which is outside the EEA and has no EU adequacy decision, so that transfer rests on the standard contractual clauses.
If you are in the EU, UK or another territory with comparable law, you can ask us for a copy of your data, to correct it, to delete it, to restrict or object to how we use it, and to receive it in a portable form. Where we rely on consent you can withdraw it at any time without affecting what we did before.
Write to support@fucini.software and we will answer within one month. If you think we have handled your data badly you may complain to your local supervisory authority.
The site is served over HTTPS. Passwords are stored hashed, never in readable form. Licence keys are cryptographically signed. Databases are not reachable from the web and are backed up daily. No system is perfect, and we will tell you if something happens that affects you.
This is a developer tool sold to businesses and professionals. It is not directed at children and we do not knowingly collect their data.
If we change this policy we will update the date at the top, and tell you directly if the change is significant.