KEYLL

Legal · Your information

Privacy Notice

Last updated: 6 November 2026

This notice explains how K3S Studio handles information when you visit keyll.cloud, use the free key check, tell us which services you use, or have a Keyll account at app.keyll.cloud. It also covers the waitlist Keyll ran before it launched.

Who is responsible

K3S Studio runs keyll.cloud and Keyll. For a privacy question or to use any of your data protection rights, use the K3S Studio contact page.

Your Keyll account

  • Your email address, and a hash of your password if you set one. If you sign in with GitHub or Google, we receive your email, name, profile picture link and account ID from them, and whether they've verified the email. We store the sign-in tokens they send encrypted and don't use them.
  • For each signed-in session: when it started, your IP address and your browser's user agent, so you and we can spot a session you don't recognise.
  • The link tags you arrived with (for example ref and utm_source from a post on X) and how you signed up, so we can see which announcements bring people in.
  • For the launch offer, a one-way hash of your email address with any +tag removed, so the same person can't take two of the free spots. We don't store the address in that list.
  • Your settings: workspace name, whether email alerts are on, and your Slack webhook URL if you add one, stored encrypted.
  • What the watcher you install reports: each API key's ID, name, restrictions and status, and how much each key was used per minute, per service or model, and per day in dollars where the provider reports it. Never the key itself. From that, Keyll keeps incidents with their evidence, the commands it sent, and a log of actions taken in your workspace.

We use this to run the service you signed up for: to sign you in, watch your keys, send alerts by email and Slack, block and restore keys when the rules you set say so, and help with a refund claim. Emails to you go through Resend.

On keyll.cloud

  • Which services do you use? The services and links you enter, your note, and the link tag you arrived with. Your email is optional; if you give it, we use it to send one email if a watcher for that service ships, and for nothing else.
  • The free key check. The repo scan sends the repo name you enter to GitHub's API and reads that public repo. Any key it finds is masked before it leaves the scanner, and full keys are never logged or stored. We keep the masked result in memory for 15 minutes so repeat scans of the same commit are fast. The limits checklist runs in your browser; your answers aren't sent to us.
  • The waitlist. Before launch, people could join a waitlist with their email and a few answers. Those entries are used for one launch email and then deleted, as promised when they were collected.

On both sites we use your IP address, in memory or for at most a day, to limit automated sign-ups, sign-in attempts, scans and form submissions. Our hosting and network providers process connection information to deliver and protect the sites.

Analytics

keyll.cloud and app.keyll.cloud use PostHog to learn where people get stuck: which pages and buttons are used, where sign-up or setup stops, errors in the page, and how fast pages load. PostHog sets a cookie on keyll.cloud so a visit to the website and the app counts as one journey. Once you sign in, it's linked to your account's internal ID, the way you signed up, your sign-up date, the link tag and whether you have the launch offer. Never your email.

PostHog also records sessions: the page layout, mouse movement and clicks. In the app, every piece of text and every input is masked before a recording leaves your browser, and install commands, watcher tokens and similar screens are left out entirely. On keyll.cloud, inputs are masked and the key check's results are left out. PostHog uses your IP address for an approximate location. The data goes to PostHog through our own domains and is processed by PostHog Inc. on our behalf.

keyll.cloud also counts page views with Open Analytics, which we run ourselves, and may load X's conversion pixel to see whether ads and posts on X lead to sign-ups. The pixel sends no email address or form answers to X.

Legal basis

  • Your account and everything the watcher reports: to provide the service you asked for (Article 6(1)(b) GDPR).
  • Security logs, rate limits, the one-spot-per-person check, and analytics that show where the product fails: our legitimate interest in running a secure and working service (Article 6(1)(f)). You can object through the K3S Studio contact page, and you can block analytics cookies and scripts in your browser.
  • The optional email on the services form, and the waitlist: your consent (Article 6(1)(a)). You can withdraw it at any time through the K3S Studio contact page. Withdrawing does not affect processing that happened before.

We do not sell your information or make automated decisions about you that have legal or similar effects.

Who we share it with

Only providers that process data for us to run Keyll: our hosting and network providers (including Cloudflare), Resend for email, PostHog for analytics, and GitHub or Google when you sign in with them. If you connect Slack, alerts about your keys go to your Slack workspace. Some of these providers are outside the EU; where that applies, they rely on the safeguards data protection law requires, such as the European Commission's standard contractual clauses.

How long we keep it

  • Your account, settings, incidents and action log: until you ask us to delete the account.
  • Per-minute usage: 8 days. Hourly usage: 35 days. Daily costs: 40 days. Sent alerts: 90 days.
  • Sessions: until you sign out or 14 days pass without use. Rate-limit counters: a day.
  • The launch offer's email hashes: until the last free period ends.
  • Services form entries: while we use them to plan watchers. Your optional email: until we've sent that one email, or 12 months.
  • PostHog keeps analytics and recordings for the period set in our PostHog project.

Your rights

Subject to data protection law, you can ask to access, correct, erase, or restrict your information, receive a portable copy, object, and withdraw consent. You can also complain to the data protection authority in your country or place of work. Send requests through the K3S Studio contact page. To delete your account, remove the watcher from your project first with its uninstall script. The European Commission explains how organisations handle individual rights requests.

Security

We use HTTPS, store watcher tokens only as hashes and Slack webhooks encrypted, never receive your API keys, and restrict database access. No internet service can guarantee absolute security.

Changes

We will update this page if the way we handle information changes. The date above shows the latest revision. If a change needs new consent, we will ask before applying it.