PRIVACY POLICY
Your work deserves privacy.
We collect only what we need to run your account, provide your computer, take payment, and keep the service safe. We do not sell your personal data.
Who is responsible for your data
The controller of your personal data is Krzysztof Cybulski, a Polish sole trader (JDG) operating as Just computer and justcomputer.dev, NIP: 5243021418, REGON: 540048490, correspondence address: Głębocka 88/11, 03-287 Warsaw, Poland. Contact us at hello@justcomputer.dev with privacy questions or requests.
What we process
- GitHub account ID, username, profile name, avatar, and any profile email GitHub returns when you sign in. If you choose project import, we also process repository names and a short-lived GitHub access credential so the selected repositories can be cloned.
- Account, subscription, and service records needed to provide and support your computer.
- Payment and billing information handled by Stripe. We do not receive or store your full payment-card number.
- Your SSH public keys, selected region and plan, setup progress, connection timestamps, provider resource identifiers, and support communications.
- Technical and security information such as request time and route, limited error details, and pseudonymous rate-limit identifiers. The hosting platform may also process IP address and device/request information in its infrastructure logs.
- Content you choose to place on your computer, such as project files and configuration.
Why we use it
- To create your account, take payment, provision and support your computer, import projects you select, and manage cancellation: to enter into and perform our contract with you.
- To keep the service secure, prevent abuse, diagnose failures, and establish or defend legal claims: our legitimate interests in operating a secure and reliable service, balanced against your rights.
- To keep accounting, tax, transaction, and consumer-rights records: compliance with legal obligations.
- For an optional purpose where consent is legally required: consent, which you may withdraw at any time without affecting earlier lawful processing. This is the basis for PostHog analytics.
Service providers
We use GitHub for sign-in and repository access, Stripe for payments, Hetzner for the infrastructure that runs your computer, Supabase for service records, Vercel to host this website and service routes, PostHog for analytics after consent, and Resend for contract email. Cloudflare routes incoming support email to a Google-hosted inbox. These providers may use their own subprocessors and, where applicable, process data outside your country. Their privacy notices and subprocessor information explain their handling under their control. Where GDPR restricts an international transfer, the transfer must rely on an adequacy decision or appropriate safeguards such as standard contractual clauses. You may ask us for information about the safeguard relevant to your data.
SSH keys and access
Your private SSH key stays on your own device. If you choose a public key from GitHub or provide one during setup, we use it to configure access to your computer. Treat private keys and account credentials as secrets; do not send them to us by email.
Retention and deletion
A signed-in browser session expires after no more than 30 days. GitHub OAuth state and project-import credentials are short-lived, normally between 10 minutes and one hour; they are not kept as general account credentials. Your computer data is retained while your subscription is active. After access ends, a recovery snapshot may be retained for up to 7 days, subject to successful creation and verification, then deleted.
We keep account, transaction, invoice, complaint, and tax records for the periods required by applicable law. Security and support records are kept only while reasonably needed for the relevant incident, request, or potential claim. When no continuing legal basis applies, we delete or anonymize the record. Provider backups may age out on the provider's documented backup cycle rather than immediately.
Providing data and automated checks
GitHub account details, payment details collected by Stripe, and a public SSH key are required to provide the paid service. Without them, we cannot create or secure your computer. Project import is optional. Automated capacity, payment-entitlement, security, and rate-limit checks may temporarily reject or pause an action. We do not use your data for solely automated decisions that produce legal or similarly significant effects through profiling.
Your choices and rights
Depending on where you live, you may have rights to access, correct, delete, restrict, object to, or receive a portable copy of your personal data, and to withdraw consent where processing relies on it. You may object to processing based on legitimate interests. You can also complain to your local data-protection authority; in Poland this is the President of the Personal Data Protection Office (UODO). To make a request, email hello@justcomputer.dev or contact us while signed in. We may need to verify your identity, but we will not require an account-linked email if GitHub did not provide one.
Access to workspace content
Your workspace is not end-to-end encrypted from us. Authorized operators and infrastructure providers may be technically able to access workspace content when necessary for provisioning, security, support, recovery, or legal compliance. We limit such access to those purposes. Keep independent backups and do not store data in the workspace if this access model is unsuitable for it.
Cookies
We use necessary cookies to keep you signed in and operate the service. If you accept analytics, PostHog stores an anonymous device identifier and analytics preferences in browser storage and cookies and receives page-view and interaction events. We disable session recording, captured page text and element attributes, and personal profiles. We do not send your GitHub identity to PostHog or use it for cross-site advertising. Declining does not affect the service. You can change or withdraw your choice through Analytics choices in the site footer. Blocking necessary cookies may prevent sign-in or account features from working.
Updates
If this policy changes in a meaningful way, we will update this page and its date. We will take reasonable steps to notify you when a change materially affects how we use your data.
Last updated: 16 September 2026