1.Who runs Runjet
Runjet is run by Tomáš Jablonický, a sole trader registered in the Czech Trade Licensing Register (živnostenský rejstřík), Company ID (IČO) 87666570, Czech Republic (the Provider). It is one person, and the same person who builds the Service reads everything sent to hello@runjet.dev.
This policy is written for somebody reading it before they decide, and it is short for that reason. The detail is in the GDPR notice at runjet.dev/gdpr: exactly what is stored, on what legal basis, who else it reaches, and what a Customer agrees to as a processing agreement. Where the two documents disagree, the more detailed one governs, and a disagreement between them is a bug to report.
2.What is recorded about you
If you are only reading runjet.dev, nothing is written down about you; all that remains is your answer to the question in the cookie banner, and that stays in your browser. No measurement, no tracking, no third-party script. The site has no server of its own: its files, fonts included, are stored and delivered by Cloudflare, which therefore sees your IP address and which page you asked for. Nobody else learns of your visit.
If you submit the registration form, what is stored is the email address, the name given, the chosen workspace name, the declared legal form, a registration number if one was entered, and the IP address the form came from. Registering means agreeing to the Terms of Service, and the version you agreed to is stored with the time you did. The details are stored even if you never finish the registration; such a registration is deleted thirty days after the link to confirm it runs out. After registering, and after buying a plan, you receive a confirmation of the contract with the Terms attached as a PDF.
If you have an account, the Service holds your email address, your name, a hash of your password and a record of your sessions. The workspace audit log records what you did in it, with your address and the IP address you did it from. It also records failed sign-in attempts, with the address exactly as it was typed into the form.
What the Service sees of your jobs — the command text, the schedule, the exit code, the output and the details of your agents — is described in the Terms of Service. Anything your command prints can end up in the run output; that is your decision, not Runjet’s.
3.Why it is recorded
Account and workspace data so that there is somebody to provide the Service to and somebody to bill. The audit log so that an admin can see who did what in their workspace. The limit on sign-in attempts and the request logs so that the Service can be defended against abuse.
Runjet does not sell data, does not pass it to advertisers, and does not use it for profiling or automated decision-making. The legal basis for each group is listed in the GDPR notice.
6.How long it is kept
A workspace’s data lives as long as the workspace does. After suspension it stays readable for thirty days, then it is deleted, and thirty days after deletion it is purged along with its database. Run history is kept for as long as the workspace exists; output text for the window your plan gives it. The audit log is not deleted while the workspace exists.
The record of emails sent is kept for a year and the request logs for thirty days; an unfinished registration is deleted thirty days after the link to confirm it runs out. A completed registration has no retention period yet.
7.Where it is stored
Where the databases will physically live has not been decided. When it is, it will be added here and to the GDPR notice, and with it the answer to whether and how far data leaves the European Union.
Stripe, Cloudflare and GitHub are US companies, so processing by them may involve a transfer outside the Union.
8.How it is protected
Every workspace is its own database. Passwords are stored as hashes, connections are encrypted, the Service never holds the values of secrets, and commands for agents are signed with the workspace’s key, which the agent verifies before it runs anything. The agent connects outward and opens no port on your machine.
What the Service does not have is intrusion detection: failed sign-ins do reach the audit log, but nothing evaluates them and nothing raises an alarm. The duty to report a breach is unaffected, but noticing one today depends on somebody looking.
9.What you can do about it
You have the right of access to your data, and the rights to rectification, erasure, restriction of processing, portability, and to object to processing that rests on legitimate interest. Write to hello@runjet.dev; an answer comes within a month, and where a request is complex the Provider may extend that by two further months, telling you so within the first month.
Two things are worth saying in advance. The data export is an export of the whole workspace and only an admin can run it — an individual account cannot download just its own data. And deleting an account makes it unusable but leaves the email address and name in it, along with the rows in the audit log; those go only when the whole workspace is purged. Whatever the product cannot do itself, the Provider does by hand.
Consent to the optional cookie category can be withdrawn at any time in the banner, which the Cookies link in the site’s footer opens again, or by deleting the cookies in your browser.
You can complain to the Office for Personal Data Protection (Úřad pro ochranu osobních údajů), Pplk. Sochora 727/27, 170 00 Prague 7, uoou.gov.cz. You do not have to come to the Provider first, though it is usually quicker.
10.Children
Runjet is a tool for administering servers and is not meant for children. The product does not ask for an age and does not verify one. If the Provider learns that it holds a child’s data, it will remove it.
11.Changes to this policy
This policy may change, and the current text is always at this address.
How a Customer is told about a change that affects them belongs to the section on changes in the Terms of Service. That section is still waiting on a decision, and until it is made no notice period is promised here.
12.Contact
hello@runjet.dev. The controller is Tomáš Jablonický, Company ID (IČO) 87666570, a sole trader registered in the Czech Trade Licensing Register; the imprint at runjet.dev/imprint says the same.
Questions about this document? hello@runjet.dev