Privacy policy

Who we are

devctrl.dev and devctrl Cloud are run by the devctrl maintainer, who is based in the European Union and is the controller of the personal data described here. Contact for anything in this policy, including data protection requests: maintainer@devctrl.dev.

What this policy covers

This policy covers three things:

If you run a devctrl server for other people, you decide what happens to their data on that server and you are responsible for it. This policy does not cover servers run by others.

Summary

The website

devctrl.dev is a set of static files served by Cloudflare. Its pages set no cookies, store nothing in your browser and load no analytics, advertising or third-party scripts. Scripts on the pages run only in your browser: navigation, the terminal recording player, the installer command builder and the interactive demo. Language selection is a plain link.

The interactive demo runs in a sandboxed frame with made-up sample data. It does not connect to any devctrl server and sends nothing to us.

To deliver the site and protect it from abuse, Cloudflare processes the technical data of each request, such as your IP address, the requested address, your browser's user agent and the time. We have not enabled request logging, analytics or log export for the site.

Links to other services, for example GitHub, take you to those services, whose own privacy policies apply. We do not embed their content.

devctrl Cloud

Your account

You sign in with GitHub or Google. We do not use passwords. From the provider you choose we receive and store:

From this we keep an account with a display name and a primary email address, plus each linked sign-in identity and the time of its last sign-in. The provider's access token is used once to read these details and is then discarded. We do not request access to your repositories, organizations, files or any other data at GitHub or Google. Accounts are never merged by email address; you link a second sign-in method yourself while signed in.

Sessions and cookies

devctrl Cloud uses only cookies it needs to work: a session cookie and a security token against cross-site request forgery, both set when you sign in (a session expires after 12 hours without activity and at the latest after 30 days); a ten-minute cookie that ties a sign-in attempt to your browser; a one-minute cookie that carries a confirmation message to the next page; and, only if you choose a language, a cookie that remembers it for one year. We store only hashes of the session and security token values. With each session we keep its times, your network prefix (the first three parts of an IPv4 address, or the first 48 bits of an IPv6 address) and a hash of your browser's user agent, so that you can review and revoke your sessions. devctrl Cloud uses no analytics, advertising or tracking cookies and loads no third-party scripts.

If you use devctl cloud login on a computer, we store a label for that device and hashes of its tokens. Such a login lasts at most 90 days and can be revoked at any time.

Organizations and servers

We store the organizations you create or join (name, address, your role), invitations (the invited email address or username, role and expiry; an invitation is valid for at most seven days) and the servers you link. When an owner or administrator chooses to invite someone by email, devctrl Cloud sends that one invitation email through Resend (see below): it goes to the invitee's email address and names the inviter's display name, the organization, the offered role, the expiry and the invitation link. We record only whether and when the email was sent. devctrl Cloud sends no other emails; invitation emails contain no images, and open and click tracking is switched off. For a linked server we store its name, address on the edge, product and protocol version, public keys, state and the time of its last report, plus your role on it.

A linked server sends a signed status report every 60 seconds: protocol and product version, connector state, key identifier, edge mode and address, a sanitized error message if its gateway reports one, and an installation identifier. Counts of hosts, users and sessions are added only if the server's operator turns them on; they are off by default. A linked server never sends us its secrets, its users' data, terminal content or files.

While a request to link a server is waiting for approval, we keep the IP address it came from and show it on the approval page, so that you can recognise your own server. The address is removed when the request is approved, denied or locked.

Audit log

Each organization has an append-only audit log of security-relevant events, such as sign-ins to linked servers, invitations, role changes and servers being linked, rotated or unlinked. An event records who acted, when, what happened and the network prefix. It never contains passwords, tokens, codes or email addresses. Owners and administrators of the organization can read it.

Signing in to linked servers

A linked server can offer "Sign in with devctrl Cloud". Each time you choose it and confirm on app.devctrl.dev, we send that server your devctrl Cloud account ID, name, username and primary email address, so that it can recognise you. The server alone decides whether you have access. We record the sign-in (time, server, network prefix and outcome) in the organization's audit log; the name and email address in a pending sign-in are kept encrypted and deleted as soon as the server collects them, or one minute after the sign-in code expires.

The edge

When you open a linked server's console at <name>.on.devctrl.dev, the connection passes through our edge. The encrypted connection ends on your own server, not on the edge: the edge reads only the server name your browser asks for, to route the connection, and forwards the encrypted bytes unchanged. It cannot read your console traffic. The edge does not log your IP address or the address you visit. It keeps hourly counters per server (bytes, streams and connections) to operate and size the service. Its logs record when a server's connector connects or disconnects, with that server's network prefix.

Abuse protection

To protect devctrl Cloud from abuse, the application counts requests per IP address for rate limits. These counters are kept only in memory and are never written to the database or to logs. The devctrl Cloud application itself does not write access logs with IP addresses. Cloudflare, which carries the traffic of app.devctrl.dev and api.devctrl.dev, processes request data as described for the website.

Google user data

devctrl Cloud uses Google sign-in only to authenticate you. The data we receive from Google is listed under "Your account": your Google account ID, email address and its verification status, your name and, if present, your Workspace domain. We use it only to sign you in, to show who is signed in, to match invitations addressed to your email address, to check a Workspace domain that an organization requires, and, when you ask for it, to sign you in to a linked server as described above. We do not use it for advertising, do not sell it, do not use it to train AI models, and do not let people read it except when needed for security, to comply with the law, or with your permission. We do not keep Google access or refresh tokens.

devctrl Cloud's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. You can remove devctrl Cloud's access to your Google account at any time at myaccount.google.com/permissions, and the access of a GitHub App under GitHub settings, Authorized GitHub Apps.

The self-hosted devctrl software

devctrl runs on servers and computers you control. Your projects, repositories, sessions, agent conversations, users, credentials and logs are stored there and are not sent to us. devctrl sends no usage telemetry and no crash reports. It makes only these connections that are not set up by you:

devctrl also connects to the services you configure, with your own accounts, for example AI agent providers, Git hosts, cloud and sandbox providers and messengers. Their own terms and privacy policies apply.

Email

If you write to maintainer@devctrl.dev, we use your message and address only to answer you and keep them no longer than needed for that.

Service providers and other recipients

We use these providers. Hosting providers process data on our behalf; sign-in providers act on their own behalf under their own privacy policies.

Within devctrl Cloud, other members of your organizations see your name, role and membership, and owners and administrators see the organization's audit log. Linked servers you sign in to receive the details listed above. We do not otherwise disclose personal data unless the law requires it.

How long we keep data

Security

All connections to devctrl.dev and devctrl Cloud are encrypted with TLS. devctrl Cloud stores only hashes of session cookies, tokens and codes, keeps each organization's data separate with database row-level security, discards sign-in provider tokens after use and never stores a linked server's secrets. The edge forwards connections to linked servers without decrypting them. No system is perfectly secure; if you find a vulnerability, please write to maintainer@devctrl.dev.

Your rights

Under the GDPR you have the right to access your personal data, to have it corrected or deleted, to restrict or object to its processing, and to receive it in a portable format. Where processing is based on legitimate interests, you can object to it at any time for reasons relating to your situation.

You can delete your devctrl Cloud account yourself: sign in, open Account → Security → Delete account, re-authenticate with your sign-in provider and confirm. If you are the only owner of an organization that has other members, make another member an owner first. Your entries in organizations' audit logs are pseudonymised as described above, not deleted.

To exercise these rights, email maintainer@devctrl.dev from the address of your account, or tell us which account you mean. We answer within one month. You also have the right to lodge a complaint with a data protection supervisory authority, in particular in the EU country where you live or work.

Children

devctrl and devctrl Cloud are tools for software developers and are not directed at children. They are not intended for anyone under 16. If you believe a child has created a devctrl Cloud account, please contact us and we will delete it.

Changes to this policy

We update this policy when the website, devctrl Cloud or the software change what they do with personal data. The date below shows the last change.

Contact

Questions or requests about this policy or your data: maintainer@devctrl.dev. See also the terms of service.