Privacy

Kitshift is run by Jon San Roman, NIF 78997534D, Alameda Mazarredo 35, 3A, Bilbao, Bizkaia, Spain. The site is https://kitshift.jonsanroman.cloud. One person, not a company: the controller of everything described below.

To exercise a right, to ask a question, or to object to a cited profile, write to Jon San Roman, Alameda Mazarredo 35, 3A, Bilbao, Bizkaia, Spain. Say which @ you are writing about and we can act on it.

Your account. Signing in with X stores your X user id, display name, profile photo, username (@), and the email address X confirms, when it confirms one. Name, photo and @ are public on your profile. The email is not public: it is there for account notices and to reach you about the service. It goes on no mailing list unless you ask, and it is never sold. Legal basis: performing the service you asked for, art. 6(1)(b) GDPR.

What you publish. Your kit, every dated restore point, the notes you attach to them, your role and your bio. Restore points are append-only — that is the product — so a shift adds a record instead of overwriting one, and the history stays public. It stays until you delete the account. Legal basis: art. 6(1)(b).

Session and logs. The session cookie is httpOnly and strictly necessary. There is no analytics, no advertising and no third-party tracker, so there is no consent banner to click. The server keeps ordinary logs — IP address, user agent, timestamps — to run the service and to spot abuse. Legal basis: legitimate interest in a service that stays up and is not abused, art. 6(1)(f).

What your browser fetches. Profile photos are the ones X hosts, so a page that shows a person loads that image from pbs.twimg.com and X sees the request. We send no referrer with it. Tool logos are served from this site, not from a favicon service.

Not every profile here was opened by the person. An operator reads a public post on X, cites it, and Kitshift assembles a dated kit keyed to that @. Those pages say so under the name and link the post they came from. This is the treatment on this site that touches people who never asked for it, so it is set out in full.

For a cited profile we hold the public username (@), the display name and profile photo shown on the public X profile page, the line quoted from the post, the link to the post, and the date of the post. The address on that row (cited-username@users.kitshift.invalid) is a placeholder that reaches nobody. We do not read protected accounts, private messages, or anything that needs a login. We store no contact details, and we infer nothing the post does not say.

These profiles are public and search engines index them, like the rest of the site. That is deliberate: a record of who says they run what is worth nothing if it cannot be found. It also means the way out has to be easy, and it is — see below.

Legal basis: legitimate interest, art. 6(1)(f) GDPR. The balancing, in full. The interest is a public, dated record of which tools practitioners say they use, which no vendor publishes and which is otherwise scattered across posts that sink. Against it: the material is a professional statement its author made in public, there is no special-category data, nothing is inferred beyond the tools named, the source post is always linked so the reader can check us, the kit is labelled as an assembly by Kitshift rather than a statement by the person, and objection is unconditional and free: no reason, no account, and nothing asked in return. What we cannot claim yet is that it is quick. Until the mailbox below is live the only route is the postal address, which is slower than this kind of record deserves; we weigh that against ourselves, not against you. On that balance the interest does not override rights the public post had not already engaged. If you disagree, say so and the profile goes.

When someone objects we delete the profile, its restore points, its citations and its follows, and we record the @ on a block list so a later citation cannot rebuild it. That list holds the @, the date and a short line saying why it was blocked — nothing else, and no copy of the profile. Keeping it is what makes the deletion stick.

The app and the database run on our own server at https://kitshift.jonsanroman.cloud. No analytics vendor, advertising network or marketing tool receives anything, because none is installed.

X is the exception, and it is unavoidable: X is where sign-in happens and the source of your name, photo and @; your browser fetches profile photos from X; and an operator assembling a cited profile reads the public X profile page. X Corp. is in the United States, so those requests leave the EEA. We send X nothing beyond what a sign-in or a page request needs, and that transfer runs under the terms and safeguards X publishes for its own platform, not under any agreement of ours.

Beyond that, data goes to a third party only where the law requires it, and to the hosting provider that runs the server as a processor on our instructions.

Account data and restore points: while the account exists. Deleting the account removes, in one transaction, your user row, your restore points and their contents, your follows in both directions, your notices, the citations recorded about you, your sessions and the X account linked to them. Nothing is archived for later.

Two things survive that deletion, and neither is about you. A tool you added to the catalog stays in the catalog with your name taken off it, and a post you cited as an operator stays, because it is the record of somebody else's kit. And if your profile had been assembled from your public posts, deleting also writes the @ to the block list described under cited profiles, so it cannot be cited back into existence.

Cited profiles: until the person objects or claims the profile. After an objection only the block list row remains — the @, the date and the line saying why — and only so the profile cannot come back.

Server logs: short retention, weeks rather than years. Kits that stay public stay dated, which is the point of the record — a restore point is history, not a current claim about anybody.

You have the right of access, rectification, erasure, restriction, objection and portability over the data described here. No treatment on this site rests on consent, so there is no consent to withdraw. There is no automated decision-making and no profiling: trends and rankings are counts over public kits, not judgements about people.

Two of those rights are controls in the product, and they need nobody on our side. On your profile, Download my data gives you everything Kitshift holds about you as JSON, and Delete my account removes the account and everything attached to it.

For the rest — rectification, restriction, access to something the export does not cover, or an objection to a cited profile — write to Jon San Roman, Alameda Mazarredo 35, 3A, Bilbao, Bizkaia, Spain. One month is the legal ceiling and we do not use it as a target: an objection to a cited profile is acted on as soon as it reaches us. If we ask you to identify yourself it is only so we do not hand your data to someone else.

If you think we handled it badly you can complain to the Agencia Española de Protección de Datos, aepd.es. You do not have to write to us first.

Two doors, both public, and you do not have to explain yourself at either.

Claim it: sign in with X using that same @, and the profile becomes yours — the kit, every restore point, the citations and the followers move to your account, and you can edit or delete any of it from then on.

Or have it removed: write to Jon San Roman, Alameda Mazarredo 35, 3A, Bilbao, Bizkaia, Spain naming the @. No reason needed, no account needed. We delete the profile and block the @ so it cannot be cited again.

The date at the top is the date of the last substantive change. A material change also gets a notice in the app. We do not backdate, and an older version is what applied before that date.