Privacy Policy, Kubi

Effective 2026-11-15

This Privacy Policy explains how Arthur Katcher, doing business as Kubi ("Kubi", "we", "us") handles personal data when you visit trykubi.com, sign up for Kubi, use the Service or contact us. Words such as Screen and Your Content mean what our Terms of Service say. The short version is a summary; the numbered sections give the detail.

The short version

We collect what we need to run Kubi, approve accounts, bill you, keep it secure and answer you. We don't sell personal data, use it for advertising or train AI on it.
Kubi is for business use. What is on your Screens is your data, and we process it for you under our DPA.
We look inside a Screen only if you ask, to investigate abuse or a security problem, or when the law requires it, and we log every look. History with screenshots is kept 30 days; the live view is never recorded.
Screens, our database and our backups run in the EU. Stripe handles payments in the US, and the people who run Kubi work from Serbia.
When your Account ends you have 30 days to take your data, and then we erase it. You can see, export, correct and delete your data at any time.

1. Who we are

1.1 Kubi is provided by Arthur Katcher, doing business as Kubi. For the personal data this policy describes as ours, Kubi decides how and why it is used, so it is the controller.

1.2 For anything about privacy, write to privacy@trykubi.com. We have not appointed a data protection officer; that address reaches the person responsible for privacy at Kubi.

2. Business use, and what the DPA covers

2.1 Kubi is for business and professional use (Terms 2.1). When Your Content includes personal data, you are the controller, or a processor for your own customers, and we process that data for you under our DPA. Your own privacy notice covers the people concerned.

2.2 If you use a product another company built on Kubi, its privacy policy applies to you. If a customer's Agent collected data about you from a website, that customer is responsible: we rent the computer and don't choose or watch what the Agent collects. Contact that company first, or write to abuse@trykubi.com with the IP address and the time and we can pass your request on.

3. What we collect and why

3.1 The table shows the personal data we handle as controller, why, and our legal basis under EU and UK law. Section 9 says how long we keep it.

Data	Why we use it	Legal basis
Account: name, email, 18+ and business-use confirmation	Run your Account	Contract
Sign-up note, if you give one	Decide on approval and write to you about it	Legitimate interests
GitHub or Google ID and when that account was created	One Account per person or organization; stop fraud	Contract; legitimate interests
Member invites: email, name, role	Manage access	Contract
Sign-in data: sessions, IP address, device	Keep you signed in; spot account takeovers	Contract; legitimate interests
API keys (stored hashed) and connected apps	Let your code and tools use Kubi; spot leaked keys	Contract; legitimate interests
Record of the Terms you accepted	Prove our contract	Contract; legal obligation
Billing: Stripe ID, invoices, address, country, tax ID	Charge you, send receipts, handle tax and refunds	Contract; legal obligation
Fraud, sanctions and identity check results	Stop fraud; run the checks our hosts and Stripe require	Legitimate interests; legal obligation
Service Data: Screen usage, performance and health	Run, bill, secure and improve the Service	Contract; legitimate interests
Network, operations and admin logs (no Screen contents or keys)	Trace abuse; keep Kubi running; record each look inside a Screen	Legitimate interests; legal obligation
Emails with us	Answer you and keep a record	Contract; legitimate interests
Abuse, security, copyright and legal case records	Handle abuse and illegal content; meet legal duties; fix security problems	Legal obligation; legitimate interests
Waitlist and product news	Invite people to the beta; tell you about Kubi	Consent
Website analytics on trykubi.com (section 13)	See how visitors use the site and improve it	Consent in Europe; legitimate interests elsewhere

3.2 Our legitimate interests are keeping Kubi, our customers and the public secure; stopping abuse and fraud; meeting the checks our data centers and payment provider require; running and improving the Service; and defending legal claims.

3.3 To open and pay for an Account you must sign in and give billing details, including your billing country and, if you have one, your tax ID; without them we can't provide Kubi. If we ask you to verify your identity or payment method and you don't, we may refuse, limit or close the Account.

3.4 Don't put regulated data on Kubi, such as health records covered by HIPAA or full card numbers, unless we agree in writing (Terms 8.6). Please don't send sensitive details to our support addresses.

3.5 Service emails, such as receipts, security alerts and notices of changes, are part of the Service. Product news goes only to people who opt in, and every such email has an unsubscribe link.

3.6 Our emails contain no tracking pixels and their links carry no tracking codes, so we don't know whether you opened one. Resend tells us only whether an email was delivered or bounced.

4. Where it comes from

Most of it comes from you or is created as you use Kubi. We also receive data from GitHub or Google when you sign in with them (account ID, name, verified email and the account's creation date); from Stripe (payment status, fraud signals and identity check results); from Account owners who invite you (email and role); from people who report abuse, website operators and rights holders (complaints, with IP addresses and times); from security researchers (name, email and the report); and from authorities (legal requests).

5. Your Screens and your content

5.1 Your Content includes everything on your Screens and in your templates: disk contents, files, apps, the logins and keys you give your Agents, browser data, your Agents' output, and each Screen's history and saved screenshots. You own it. We process it for you under the DPA, only as needed to provide the Service.

5.2 We never use Your Content, or anything derived from it, to train AI models, we don't let our subprocessors do so, and we never sell it.

5.3 We don't routinely scan inside your Screens. We look inside only if you ask us to, to investigate abuse or a security problem, or when the law requires it. We log every look and tell you about it, unless the law forbids it, telling you would put someone at risk, or it would compromise an investigation.

5.4 Screenshots and the live view stream to your Agents and viewers, and our servers carry them on the way. We never store the live view. Each screenshot a call returns is saved, encrypted, in that Screen's history for 30 days, unless you turn detailed history off; saved screenshots have no backup copy and are erased with the Screen.

5.5 A Screen's history records each call made on it: what was called, its parameters, including text your Agents type, which key or app called it, the result and how long it took. Typed text that matches a secret you saved is blanked before it is stored. With detailed history off, it keeps only what was called, by whom, when and the result.

5.6 For our own disaster recovery we keep encrypted copies of Screen disks for 7 days. They are not a backup service for you, and we don't restore a deleted Screen or file from them.

6.1 Subprocessors. Other companies help us run Kubi: Ikoula for the servers that run Screens; Hetzner for our main server and database; Scaleway for backups, saved screenshots and disk exports; Stripe for payments, fraud and identity checks and tax; Grafana Labs for monitoring; PostHog for website and product analytics; Vercel for this website and its waitlist form; Resend for the emails we send; Lark for our mailboxes; and Better Stack for our status page. Our subprocessors page, trykubi.com/legal/subprocessors, names each one, what it does and where it processes data, and we announce new ones at least 30 days before they start. They are bound by contract, and we remain responsible for their work.

6.2 Stripe and sign-in providers. Stripe runs checkout and identity checks under its own privacy policy as well as ours, and your full card number stays with Stripe. GitHub and Google send us your profile details when you sign in with them, so we never see or store a password for Kubi.

6.3 Advisors and buyers. We share data with our lawyers and accountants under confidentiality, and with a buyer or successor if Kubi is merged, acquired or sold, in which case we tell you.

6.4 Authorities. We report child sexual abuse material as US law requires, and tell the police about information suggesting a crime that threatens someone's life or safety. Otherwise we disclose data to authorities only when the law requires it, after checking that the request is valid, and we tell you unless the law forbids it or it would put someone at risk.

6.5 Abuse complaints and claims. To resolve a credible complaint or defend a claim, we may share the minimum needed, such as account identity, IP addresses, times and evidence of the abuse, but never the contents of your Screens unless the law requires it.

6.6 No selling. We don't sell personal data, share it for cross-context behavioral advertising, or give it to data brokers or advertisers. The AI models, websites and services your Agents use are your own choice, not our subprocessors.

6.7 Our own use of AI. We may use an AI tool to help draft support replies and sort abuse reports, and a person reviews every reply before we send it. Any such provider is listed on our subprocessors page before we use it, may not train on what we send it, and never receives the contents of your Screens. We don't use your emails, Service Data or other personal data to train AI models.

7. Automated decisions

Automated checks on payments, new Accounts and network or resource use can limit an Account, or slow down or pause a Screen, before a person looks at it. Where practicable, a person reviews the case before we suspend or close an Account; in an emergency, we act first and review afterwards. We tell you what we did and why, and you can ask for a human review by replying to that email or writing to support@trykubi.com; a person answers, normally within 7 days.

8. Where your data is processed

8.1 Screens, our main database and our backups run in the EU, in France and Germany. Each Screen runs in the location shown when you create it, and we don't move Your Content to another country without telling you first, unless an emergency or the law requires it.

8.2 Some personal data is also handled outside the EU. Stripe processes payment data in the US, Resend stores the emails we send in the US, Lark keeps our mailboxes outside the EU, and other subprocessors work where the subprocessors page says. The people who run Kubi work from Serbia and reach our systems remotely over encrypted connections.

8.3 Kubi is not certified under the EU-US Data Privacy Framework. Where the law requires a safeguard for a transfer, we use the EU Standard Contractual Clauses, with the UK Addendum for data from the UK, and you can ask us for a copy.

8.4 Our export and switching page, trykubi.com/legal/data-export, shows where our infrastructure is, which countries' laws apply to it, and how we protect data against unlawful government access.

9. How long we keep it

9.1 We keep personal data only as long as we need it for the purposes in section 3:

Data	How long we keep it
Account, identity check result and Service Data	While the Account exists, then 30 days
A sign-up we decline, with its note	30 days after we decline it
Record of the Terms you accepted	As long as the billing records
Billing and tax records	As tax law requires
Fraud and sanctions checks	2 years
Sanctions matches and reports	10 years, as US sanctions rules require
Sign-in sessions	7 days after last use
Sign-in records and network log	90 days
Operations logs and metrics	14 days
Admin log, including each look inside a Screen	1 year
Emails with us	2 years after the last message
Service emails we send	30 days
Abuse cases and bans; ban identifiers	2 years after closing; identifiers 5 years
Reports of child sexual abuse material	1 year after we report it
Waitlist: confirmed, then never confirmed	Until the sign-up email goes out plus 30 days; 14 days if never confirmed
Website analytics	Recordings 30 days; the rest 12 months
Your Content on Screens, and templates	Until you delete it, or 30 days after the Account ends
A deleted persistent Screen	Restorable for 7 days, then erased
A deleted disposable Screen	Erased at once
History and saved screenshots	30 days
Disk exports; recovery copies; database backups	7 days; 7 days; 14 days

9.2 When you delete a persistent Screen you can restore it for 7 days; a deleted disposable Screen is erased at once. Then we erase its disk, its history and its saved screenshots, and its recovery copies expire within 7 days.

9.3 When your Account ends, you have 30 days to download your data, and then we erase it. Copies in our backups expire within 14 days, and we never restore a deleted Account or Screen from them.

9.4 We keep data longer only when the law requires it, for example when an authority asks us to preserve it while it obtains a court order, or when we need it for an abuse case, a security incident or a legal claim.

10. Security

We protect personal data with reasonable technical and organizational measures, described on our security page and in the DPA. Each Screen runs in its own virtual machine; Screen disks, recovery copies, database backups, saved screenshots and disk exports are encrypted at rest; and access by a person is limited and logged. No system is perfectly secure. If we learn of a breach that affects Your Content, we tell you without undue delay. Report vulnerabilities and leaked keys to security@trykubi.com, as our vulnerability disclosure policy at trykubi.com/legal/vulnerability-policy explains.

11. Your rights

11.1 You can ask us for a copy of your personal data, and ask us to correct it, delete it, send it to you in a machine-readable format, or restrict its use while a question is resolved. You can object to our legitimate interests (section 11.3), withdraw consent at any time without affecting earlier use, and ask for a person to review an automated decision (section 7). We answer requests from everyone, whatever the local law gives. We keep billing records for the tax period and data under a legal hold (section 9.4) even if you ask us to delete them.

11.2 In the dashboard you can see and correct your Account details, export your data and close your Account. For anything else, write to privacy@trykubi.com from the email on your Account. We answer within one month; if a request is complex, we may take up to two more months and tell you why within the first month. Requests are free unless they are clearly unfounded or excessive.

11.3 Where we rely on legitimate interests, you can object at any time. We then stop, unless we have compelling grounds to continue, such as security or a legal claim.

11.4 You can complain to the data protection authority where you live or work, or where you think the problem happened. In the UK you can also complain to us first: we acknowledge within 30 days and tell you the outcome. You can go to the Information Commissioner's Office (ico.org.uk) at any time. The authorities of each EU and EEA country are listed at https://www.edpb.europa.eu/about-edpb/our-members_en, and in Switzerland you can complain to the Federal Data Protection and Information Commissioner at https://www.edoeb.admin.ch/en.

12. US states and California

We don't sell personal data, share it for cross-context behavioral advertising, or give it to other companies for their own marketing. If your state's law gives you privacy rights, use them as section 11 describes; if we refuse a request, you can appeal by replying to our answer, and we won't treat you differently for using your rights. Sections 3, 4 and 6 list the categories of personal data we collect, where they come from and who receives them. Outside Europe our website analytics, including recordings of visits with everything you type hidden, run when a page loads, and you can turn them off at any time (section 13). We treat a Global Privacy Control or Do Not Track signal from your browser as a refusal of them, and we use no advertising cookies or pixels.

13. Cookies and similar technologies

13.1 The dashboard uses only the cookies it needs to sign you in, keep your Account secure and remember your display settings, so it has no cookie banner. We measure dashboard use from requests our servers already receive, without an analytics script.

Cookie or storage key	Purpose	Lifetime	Consent
__Secure-kubi.session_token	Keeps you signed in to the dashboard	7 days, renewed on use	Not needed
kubi_sign_up	Carries your sign-up through the Terms step	30 minutes	Not needed
kubi-theme and sidebar_state	Remember your dashboard display settings	1 year; 7 days	Not needed
ph_(project key)_posthog	Website analytics on trykubi.com	Up to 13 months	In Europe, yes
__ph_opt_in_out_(project key)	Remembers your analytics choice, in local storage	Until you clear it	Not needed

13.2 What our website analytics collect. PostHog, in the EU, records the pages you open, the page that sent you here, what you click and scroll, a recording of your visit with everything you type hidden, your browser and screen size, and your IP address with the country and city it points to. We use this only to understand and improve trykubi.com: no ads, no profiles, nothing sold, and it is never linked to your email address. Recordings are kept for 30 days and the rest for 12 months.

13.3 In Europe. If your browser's time zone is in Europe (the EU, the EEA, the UK, Switzerland and their neighbours), the analytics in section 13.2 run only if you accept in the cookie notice, and only then set their cookie. Until you choose, and if you reject, we only count your visit without any cookie, recording or heatmap, using a privacy-preserving code that PostHog works out on its servers.

13.4 Everywhere else. The analytics in section 13.2 run when a page loads. You can turn them off at any time with Reject in the cookie notice or with the setting below, and they stay off in that browser.

13.5 Nothing loads if your browser sends Do Not Track or Global Privacy Control. Stripe sets its own cookies on its checkout pages. Our SDK sends us only what it needs to work, and sends usage statistics only if you turn them on.

14. Children

Kubi is only for people aged 18 or older (Terms 2.2), and we don't knowingly collect personal data from anyone younger. If we learn that someone under 18 is using Kubi, we close their access and delete their personal data, except what the law requires us to keep.

15. Changes to this policy

For significant changes, such as a new purpose, a new kind of recipient or a new country, we email everyone with a Kubi Account and show a notice in the dashboard at least 30 days before the change takes effect. Changes the law requires may take effect sooner, and so may a change that is urgent for security or to keep the Service running; then we tell you as soon as we can and say why. Every earlier version stays online with its date.