Privacy
Last updated 28 September 2026
Fabricwright is run by Rafi Samuel to help network engineers design, document and implement their network fabrics. It is made primarily for greenfield deployments.
This page says what the service collects, why, and what it never does with it. It is written to be read rather than to be survived.
What data do we collect?
- Your identity at Google or GitHub: an identifier for your account there, your display name, the address of your avatar image, and the email address the provider reports.
- What you make: your saved projects — devices, links, roles, VLANs, addressing, the services you switch on, and anything else you type into a design, including any credentials you choose to put in one.
- How you arrived: campaign parameters from the link you came in
on (the
utm_ones) and the site that sent you, as its bare address —https://example.com, never the page or anything after it. Recorded once, when the account is created. - Sign-in times: when the account was created and when it last signed in.
- Server logs: your IP address, the address requested, the time, and your browser's description of itself.
Nothing else. No password, because there is none; no phone number, no postal address, no payment details.
How do we collect your data?
- From Google or GitHub, when you choose to sign in with them. They send your identity and nothing more: Google is asked only for your basic profile and email address, and GitHub only for your public profile and email address.
- From you, when you build and save a project.
- From your browser, automatically: the log entry each request leaves, and the link and site you arrived from.
How will we use your data?
Each use has a reason the law recognises, and it is named here:
- To give you the service you signed up for — recognising you, showing who is signed in, keeping your projects and generating configuration from them. That is the contract between us.
- To answer you, if you write to us. Your email address is kept for that, and is deliberately not how your account is found: providers let people change their address, and an address can later belong to someone else, so an account is recognised by the provider and its identifier alone. Also the contract.
- To keep the service working and safe — the server logs, which are how faults are found and abuse is noticed. That is a legitimate interest, and the logs are never used to build a picture of anyone.
- To learn what brings people here — how you arrived, which is counted, not followed: it is never updated after sign-up and never linked to anything you do later. Also a legitimate interest, and you can object to it.
Your projects are never shared with anyone, shown to other users, or used to train anything.
How do we store your data?
In a database on a server we operate in the Netherlands, reached only through Cloudflare. Every request for a project is checked against the account that owns it, and traffic to the site is encrypted.
The database is copied every night. One copy stays on the server; another is encrypted before it leaves, to a key that is not on the server, and stored with Cloudflare R2 in the European Union.
| What | How long |
|---|---|
| Your account, projects, sign-in times and how you arrived | As long as the account exists |
| Nightly copies of the database | Two weeks |
| Server logs | Two weeks |
When an account is deleted, everything in it goes at once, and survives only in the nightly copies until they rotate out two weeks later.
Who else is involved
Running the service means a small number of other companies necessarily handle some of it:
- Google and GitHub — when you sign in with them, they tell us who you are. Your avatar image is also loaded from them, so while a page shows it, your browser asks Google or GitHub for the picture and they see that request. Nothing else about what you do here reaches them.
- Cloudflare — carries all traffic to the site, stores the encrypted nightly copies, and delivers mail sent to our addresses.
Some of these companies are based outside the European Union. Where your data reaches them, it is transferred under the safeguards European law requires for transfers of that kind, and only to the extent running the service needs. None of them receives anything to advertise with.
Marketing
None. There is no advertising here, no third-party analytics on any page, and no marketing email — the service sends no email at all, so if you hear from us it is a person replying to something you sent. Your data is not sold, rented or traded, under any circumstances.
What are your data protection rights?
You can:
- Erase your data. You can do this yourself, at any time: open the menu under your name and choose Delete account. It removes the account, its projects and its ways of signing in immediately.
- See what we hold about you, and have a copy of it.
- Correct anything that is wrong.
- Take it with you — your projects in a machine-readable form you can use elsewhere.
- Restrict what we do with it while a question about it is settled.
- Object to anything we do on the strength of a legitimate interest, such as recording how you arrived.
For any of these except erasure, email [email protected]. You will have an answer within a month.
What are cookies?
Small text files a website asks your browser to keep and send back on later visits, so that it can recognise the same browser from one page to the next.
How do we use cookies?
Only to sign you in. There are two, both set by Fabricwright itself:
| Cookie | What it does | Kept for |
|---|---|---|
session |
Keeps you signed in. While you are signing in it also carries the sign-in itself, where you were heading, and how you arrived, until the account is created. | 30 days |
remember_token |
Signs you back in if the session cookie has gone. | 30 days |
Both are needed for signing in to work, so there is no banner to click through. Signing out ends both. There are no advertising cookies and no tracking cookies, because there is no advertising and no tracking.
Who the service is for
Fabricwright is not meant for anyone under 16, and does not knowingly hold data about them.
Changes
If this page changes in a way that matters, the date at the top changes and the change is announced on the site before it takes effect. Minor corrections and clarifications happen without ceremony.