fastest.ee In short: your uploaded design files are used to run your check and are then discarded, unless you opt in to contribute them. The data needed to deliver your report, derived from your files, is kept for 90 days, after which the report is no longer available. Signing in stores an account identifier, never a password. There are no analytics and no advertising trackers. To have your data deleted, email findings@fastest.ee, or use Delete your account on your Billing page.
Who we are
The data controller is Rapla Space Agency OÜ, registry code 17540338, registered in Estonia, which operates fastest.ee. Contact: findings@fastest.ee. This policy covers the fastest.ee checker (the web app), under the EU General Data Protection Regulation (GDPR). We have not appointed a Data Protection Officer: given the nature and scale of what we process, the GDPR does not require us to, and any data-protection question can go to the address above.
Deterministic verdicts, and no decisions about you
Every finding in a report is produced by a deterministic rules engine and carries a citation to the rule it applied; the verdicts are deterministic, never by AI. The report analyses your design files, not you: we make no automated decision about you with legal or similarly significant effect, and we build no profile of you.
What we process, why, and for how long
- Your uploaded design files (netlist, BOM, board) are used to run the check you asked for and are then discarded: they are not kept after the check completes unless you explicitly opt in to contribute them (a tickbox on each upload, off by default). If something goes wrong while a check runs, a copy may be left in our storage. It is deleted automatically, normally within three days of your upload. Opted-in uploads are kept so we can reproduce and fix defects in the checks, until you ask us to delete them. A design file is normally technical data about a circuit rather than personal data; please do not upload personal data that is not needed to run a design check. Legal basis: performance of a contract, and your consent for opted-in retention, which you can withdraw at any time.
- The data needed to deliver your report is derived from your files during the check and does not include the files themselves. We use it only to deliver your report. We keep it for 90 days after the check that produced it, after which the report is no longer available, and delete it sooner on request. Legal basis: performance of a contract.
- The generated report is kept so its share link (the
/r/<id>address) keeps working. The stored report contains the findings, their citations, and run metadata, including names from your design that appear in findings (reference designators, net and part names), but not your uploaded files. Every report, anonymous or signed-in, expires automatically after the window shown next to the link when it is created (90 days by default). An anonymous report can be deleted sooner, no account needed, with the “Delete now” button on the page where you started the check. The button works once the report is saved and only on that page: it is not offered after a reload, from the report's link or from the Recent reports list. A signed-in owner can delete their report sooner at any time. After a report is deleted, we keep only its address and the time it was created, for about two days after the check started, so that the address can never show another report. Legal basis: performance of a contract. - The record of each check. For every check we keep a record of when you started it and how it ended, with your account identifier if you were signed in. The record holds none of your uploaded files. It does hold the settings the check ran with, including any facts you declared about your design, and the error text of a check that failed, which can name a file in your upload; that error text is deleted after at most one year. While a check runs, anyone with its link can follow its progress; a check you started while signed in can be followed only from your account. The link is the report's address: besides a random part, it encodes the time you started the check, to the millisecond. The record of a check run without an account is deleted about 90 days after the check ends, once its report link has stopped working. The record of a check you ran while signed in is listed under “Your checks” for 90 days, is kept while your account exists, and is deleted with your account. We use the record to run your check, to show its progress and, for a check you ran while signed in, to list it under “Your checks”. Legal basis: performance of a contract.
- Your account. If you sign in with Google, GitHub, or Microsoft, we store the provider's stable account identifier, never a password (we do not have one). We also keep the one email address your provider reports as verified: on Google, your verified address; on GitHub, your primary verified address, which is why we ask GitHub for read access to your email addresses; on Microsoft, your address when Microsoft reports that the owner of its domain is verified. We refresh it each time you sign in and clear it when the provider no longer reports one. We use it only to send you the link that confirms a request to delete your account, through our mail server in Amsterdam, in the Netherlands, and it is deleted with your account. Legal basis for keeping it: our legitimate interest in deleting an account only at the request of the person who holds it. Your account is kept until you ask us to delete it and confirm that request, and the records of the checks you ran while signed in are deleted with it. Copies of what we delete can remain in our backups for about a week, until those backups expire; we use backups only to recover from a failure of our systems. The record of your agreement to the Terms is kept for longer, as explained below. Each of our security records is kept for 12 months after the event it records, but deleting your account deletes the link between your security records and you. Your sign-in provider processes the sign-in itself under its own privacy policy. Legal basis: performance of a contract.
- Your agreement to the terms. When you run a check without an account, we record that you accepted the Terms and confirmed you had seen this policy: the time and the versions shown to you, keyed to an anonymous browser identifier, never your design data. When you sign in, we record your account identifier, the time, and the versions of the Terms and this policy that were shown to you before you continued to your sign-in provider. These records are kept as evidence of the agreement, until the limitation period for claims about it has passed, including after an account is deleted. Legal basis: our legitimate interest in being able to show the agreement existed.
- Feedback you send (the per-finding right/wrong buttons and notes) is kept for as long as it helps us keep the checks correct. Each piece of feedback you send is kept as its own record. A record carries the text you typed, if any, the names of the files you uploaded for the check, the report it concerns, your account identifier if you were signed in, and when you sent it. We record only the file names: the files themselves are never stored with your feedback, and are deleted after the check unless you chose to keep them, for example by ticking “Keep my uploaded files on the server” on the upload form. A right/wrong verdict also carries your verdict, the finding reference and whether it named one of our checks at the time. Deleted on request. Legal basis: our legitimate interest in fixing the checks.
- Payments. Paid features are billed through Stripe, our payment processor; your card details go to Stripe and are never stored on our servers. We keep your credit balance for as long as you hold credit, and the accounting records of payments for as long as accounting law requires (in Estonia, seven years). During the closed beta the service is free and no payments are taken. Legal basis: performance of a contract, and our legal obligation under accounting law.
- Purchase and withdrawal emails. When you buy credit, we use the email address you give at checkout to send you the confirmation of your purchase. We do not store that address ourselves; Stripe keeps it with your payment. If you withdraw from a purchase on your Billing page, we use the name and email address you type in the withdrawal form to confirm that we received your withdrawal. We keep them only until that confirmation has been sent, and never longer than 14 days, then delete them. We send these emails through a mail server in Amsterdam, in the Netherlands. Legal basis: our legal obligation under consumer law.
- Emails you send us. If you email us, we process your address and message to answer you. We keep the correspondence while we deal with your query and for up to 12 months after it is resolved, then delete it, and delete it sooner on request. Legal basis: our legitimate interest in answering you.
- IP addresses. Your IP address is used to rate-limit anonymous use and to protect the service against abuse; for that it is held in memory, not stored with your report. Technical logs for security and troubleshooting, which may include IP addresses, are kept for at most one year and then deleted; we do not use them for profiling or analytics. Legal basis: our legitimate interest in keeping the service up and secure.
- Security records. We keep a record of security events that concern you: when you sign in, or when a fault on our side stops a sign-in from completing; when an API key for your account is created or revoked; and when our staff use our tools to look up or delete your feedback, to erase the records of your checks, or to start deleting your account and its API keys. A record holds what happened, when, who acted (you, or the person on our side who handled it), whether it succeeded, and the account or report concerned. An account deletion is recorded as it starts, so its record shows that it was started, not that it finished. It names your account by a pseudonym: a random identifier we give it, never the identifier your sign-in provider gives you. Depending on the event, it also holds the sign-in provider you used, the API key's identifier (never the key itself), or a short note, such as why we acted or how many records were deleted. It holds none of your design data, and no IP address, password or key, and our system refuses a note that contains an email address, an IP address or the account identifier we store for you. The link between the random identifier and your account is kept with your account and deleted with it. While your account exists, we can find the records about you from your account. The link can remain in our database backups until those backups expire; once your account is deleted and those backups have expired, the records no longer identify you. We keep the record of your agreement to the Terms, our payment records and our technical logs separately, and we never combine them with these records to work out who they are about. We keep each record for 12 months from the event and then delete it, to protect accounts and the service. If you want them gone sooner, delete your account, which removes the link between you and them. If you ask us to delete them in any other way, or object to our keeping them, we answer within a month; if we decline, we tell you why, and that you can complain to a supervisory authority or go to court. You can also ask us for a copy. Legal basis: our legitimate interest in keeping your account and the service secure and in preventing fraud.
Do you have to give us this data?
You are never under a legal obligation to give us any data. Some data is simply needed for the part of the service you want: uploading a design is needed to run a check, signing in is needed to have an account, and payment details are needed for a paid feature. If you do not provide it, we cannot provide that part of the service, but there is no other consequence. The optional item above (contributing an upload) is your choice and off unless you turn it on.
Cookies and browser storage
The app sets strictly necessary cookies only: an anonymous identifier (about 30 days), two sign-in cookies (up to an hour), and a session cookie to keep you signed in. There are no analytics or third-party cookies, and no trackers. Your browser's local storage holds your theme choice and your report history; both stay in your browser and are cleared from there whenever you choose.
Processors, and where your design goes
We use a small set of processors under GDPR data-processing terms; as our processors they may not use your data for their own purposes:
- Google Cloud hosts the service, with its databases and stored files, in its europe-west1 region in Belgium. It also carries the service's network traffic, filters attacks on it, and keeps the service's logs.
- Cloudflare runs the DNS for our domain and forwards the emails you send to our addresses on to us.
- Stripe processes payments. For payment fraud prevention Stripe also acts as a controller in its own right, under its own privacy policy.
Your design is processed only by our own deterministic engine, on Google Cloud; no external analysis service receives it.
These are all the processors that can receive data derived from your design. If we add or change one, we will update this list and give reasonable advance notice here before the new processor starts. If you object on data-protection grounds, tell us: you can stop using the affected feature and ask us to delete the data it held. Where a processor is essential to a feature, objecting may mean we can no longer provide that feature to you.
International transfers
The service runs in the European Union, in Google Cloud's europe-west1 region in Belgium, where its databases and stored files are kept. The service's logs are kept by Google Cloud in a location that may be outside the EEA. Google, Cloudflare and Stripe belong to US groups and may process limited data outside the EEA. Where Google, Cloudflare or Stripe process data in the US, the transfer is protected either by the EU–US Data Privacy Framework, where the provider takes part in that framework (an adequacy decision the European Commission has adopted for participating US organisations), or by the European Commission's standard contractual clauses. You can ask us for a copy of the clauses that apply, and we will tell you which safeguard, and whether an adequacy decision, covers a given provider.
Security
Our databases and stored files are on Google Cloud servers in Belgium, and access to stored data is limited to the people who run the service. We hold no SOC 2 or ISO 27001 attestation today, and we will not imply one before it exists.
Your rights
Under the GDPR you can ask us at any time to: access the data we hold about you; correct it; delete it; receive a copy in a portable form; restrict its processing; object to processing we base on legitimate interest; and withdraw any consent you gave, without affecting what was lawfully done before you withdrew. There are three exceptions to deletion. Data the law requires us to keep (accounting records, for example) is kept for that legal period and no longer. The record of your agreement to the Terms is kept until the limitation period for claims about it has passed, so that we can establish or defend a legal claim. Our security records are the third: they are kept for 12 months from the event, and deleting your account removes the link between you and them, as the Security records item above explains. Email findings@fastest.ee and a human will handle your request; we answer within a month (for a complex request the GDPR allows two more, and if we ever need them we tell you within the first month). So that we act only on a request that is really yours, we may ask you to confirm it from the signed-in app, or from the email address your sign-in provider holds for you. To delete your account, use Delete your account on your Billing page while signed in, or email us your account identifier. Either way we email a link to the address your sign-in provider verified, and we delete the account only after you open the link and confirm. The link works once, for 24 hours. If we hold no verified address for you, we tell you how to add one with your provider. If your provider cannot give us one, we cannot confirm the request by email: write to us, and we decide with you, case by case, how you can show the request is yours. You can also complain to a supervisory authority: ours is the Estonian Data Protection Inspectorate (Andmekaitse Inspektsioon), and you may equally complain to the supervisory authority of your own EU country.
Changes to this policy
If this policy changes, the change and its date appear on this page, and a material change is said plainly rather than buried. We will not quietly broaden what we do with your data: a new purpose means we ask you first. If you use the checker without an account, you are asked to agree to the current version before a check runs, so a material change reaches you before it applies.
- 11 October 2026. We now keep the email address your sign-in provider reports as verified, and use it only to send you a link that confirms a request to delete your account; we delete an account only after that confirmation. On GitHub we now ask for read access to your email addresses to find your primary verified one. You can now ask for your account to be deleted from your Billing page. We now say how long copies of deleted data stay in our backups, and what happens if your provider gives us no verified address.
- 11 October 2026. We now say that we keep a security record when our staff start deleting your account and its API keys on your request.
- 10 October 2026. We now describe the security records we keep, such as a record of each sign-in: what they hold, and that we keep them for 12 months from the event. A record names your account by a random identifier, and deleting your account deletes the link between that identifier and you, which is how to have them removed sooner. This policy also now says that the service is hosted on Google Cloud in Belgium instead of Microsoft Azure, and that Cloudflare no longer carries the checker's traffic: it runs our domain's DNS and forwards the emails you send us. We now say that we send purchase and withdrawal emails through a mail server in Amsterdam, and that if we decline a request about your security records, we tell you that you can complain to a supervisory authority or go to court. We no longer say we would email you before adding a processor: we do not keep your email address.
- 9 October 2026. We now describe the emails we send when you buy credit or withdraw from a purchase, and how long we keep the name and address you give to withdraw.
- 8 October 2026. We now describe the record we keep of each check, what it holds and how long we keep it: about 90 days after a check run without an account ends and, for a check you ran while signed in, for as long as your account exists. We also now say that anyone with a check's link can follow its progress while it runs (only you, for a check you started while signed in), that the link encodes the time you started the check, that an anonymous report's “Delete now” button is offered only on the page where you started the check, and that a deleted report's address and creation time are kept for about two days after the check started.
- 8 October 2026. We removed an incorrect reference to an account-level setting for contributing uploads. Contributing an upload is optional and chosen with the tickbox on that upload, which is off by default. What we process has not changed.
- 7 October 2026. This policy no longer describes features the service does not offer. It now says plainly that uploads you contribute are kept until you ask us to delete them. What we process when you use the checker has not changed.
- 5 October 2026. We now say what happens to a copy of your uploaded files left behind when something goes wrong while a check runs: it is deleted automatically, normally within three days of your upload.
- 28 September 2026. The feedback item now lists everything a feedback record keeps. Each piece of feedback you send is its own record. As well as the finding, your verdict, your note and the file names, it keeps the report the feedback concerns, your account identifier if you were signed in, when you sent it, and whether the finding named one of our checks at the time. It also says that we record only the names of your files, never the files themselves.
- 27 September 2026. Signing in now records that you agreed to the terms: your account identifier, the time, and the versions of the Terms and this policy shown to you. These records are kept after an account is deleted, as evidence of the agreement.
- 26 September 2026. We now keep technical logs, which may include IP addresses, for at most one year, up from 90 days. We still use them only for security and troubleshooting.
- 25 September 2026. We now keep the feedback you send for as long as it helps us keep the checks correct, no longer only while the check it concerns is part of the product. You can still ask us to delete it.
- 24 September 2026. We now keep the data needed to deliver your report for 90 days after the check, down from up to 24 months, and use it only to deliver your report, no longer to improve the checks. A signed-in owner's report now expires after 90 days too, as anonymous reports already did.
Effective: 11 October 2026.