Operator details pending
The operator details this page depends on (publisher identity, hosting provider and contact addresses) have not been published yet. This text is a draft for review. It is not indexed by search engines and does not take effect until those details are published.
Who is responsible
The publisher named in the legal notice decides why and how the account, billing, usage and website data described below is processed, and is the controller for it. Contact for privacy questions and data requests: To be provided.
gpuOS (gpuos.si) and cpuOS (cpuos.si) share one account. Your name, email address, password hash, linked sign-in providers, sessions, workspaces, members, invitations and API-key records are stored once and used by both sites, so a workspace created on one exists on the other. This policy describes what gpuOS processes. The cpuOS privacy policy covers cpuOS, including the code and output of its CPU jobs.
Prompts and completions that you send through the gateway are your data. You decide what to send and usually act as the controller. The gateway handles them on your behalf, only to relay them. No data processing agreement is published on this site yet. If you need one, ask at the address above before you send personal or regulated data.
What we process and why
Scroll horizontally to see every column.
| Data | What it includes | Why |
|---|---|---|
| Account | Name, email address, a hash of your password if you sign up with email and password, and, if you sign in with GitHub or Google, your profile image URL, the provider account ID and the tokens the provider issues. | Create your account, sign you in and keep it secure. |
| Account emails | Your email address and name, and a single-use link in each message. Only when email is enabled: a message to verify your address after sign-up, a message to reset a password and a message to confirm the deletion of an account. We send no marketing email. | Confirm your address, let you reset your password and confirm a deletion. |
| Sessions | Session token, expiry time, IP address and browser user agent. | Keep you signed in and detect misuse. |
| Workspaces and teams | Workspace name and URL slug, members and roles, and invitations: invitee email address, role, expiry and a hash of the invitation token. | Run team workspaces and invitations. |
| API keys and node tokens | Name, prefix, a hash of the secret, the products the key works with, limits, expiry time, last-used time and revocation time. Secrets are shown once. An encrypted copy of a new node token is kept only until the agent's first heartbeat, so the install command can be shown again. | Authenticate API calls and agents. |
| Node data | What the agent reports: node name, hostname, operating system, agent and engine versions, GPU inventory and utilization, installed and deployed models, and last-seen time. | Show your nodes and route requests to a node that has the model. |
| Usage metering | For each request: workspace, API key, node, model, endpoint, prompt and completion token counts, latency, HTTP status and time. | Show usage and apply monthly token quotas. |
| Billing | Stripe customer ID, subscription ID and status, billing interval, number of billed GPUs, period end and Stripe event IDs. Card and bank details are entered on Stripe pages and do not reach our servers. | Sell and manage Pro subscriptions. |
| Messages to us | Your email address and what you write. | Answer you. |
We rely on the following legal bases. Performance of our contract with you covers the account, workspace, key, node and usage data and the account emails. A legal obligation covers the accounting records of payments. Our legitimate interests cover security, abuse prevention, operating the service and measuring how the site is used. We do not sell personal data and do not use it for advertising.
Prompts and completions
The gateway relays request and response bodies between your application and your node. It does not write prompt or completion text to its database. Usage metering stores token counts and timings, not content.
- While a request is in flight, its body is held in server memory, and the gateway reads it to validate the request and count tokens.
- TLS ends at our servers, so this traffic is not end-to-end encrypted, and the service is not air-gapped. We can technically read traffic while it passes through.
- Ollama runs on your node. What it logs or keeps there is under your control and outside this policy.
Analytics and cookies
Google Analytics 4 is active only on the public marketing pages of gpuos.si: the home page, the documentation, the model catalog, the guides, the integrations, the tools, the pages about the .si stack, and the legal notice, privacy policy and terms. It is not loaded on the sign-in, sign-up, password reset, invitation, dashboard, workspace and playground pages or on the API, and moving from a public page to one of them switches measurement off. On the public pages it uses cookies and sends usage data to Google, such as the page address, browser and device details and approximate location. We also send interaction events: clicks on calls to action, use of the VRAM calculator (the model and GPU you pick and whether it fits), playing the founder video and clicks on the link to cpuOS. These events do not contain your email address or prompt content. Advertising storage, advertising user data and ad personalization are denied.
The analytics notice informs you. It does not collect your consent: on a public page, analytics cookies are set and usage data is sent as soon as the page loads, closing the notice does not change analytics tracking, and no accept or decline choice is offered today. To avoid analytics, block Google Analytics scripts and cookies in your browser or with a tracking-protection extension. The Analytics information link in the footer reopens the notice.
We also set the cookies needed to keep you signed in. They are first-party cookies from our authentication library, including a short-lived cache of your session data that lasts up to one minute. Your browser's local storage remembers that you closed the analytics notice. We do not use advertising or social media tracking cookies.
Who receives data
Scroll horizontally to see every column.
| Recipient | Why | Data |
|---|---|---|
| Hosting provider named in the legal notice | Hosts the website, gateway and database. | Everything the service stores or relays. |
| Email delivery provider chosen by the operator | Sends the account emails. Used only when email is enabled. | Your email address, your name and the content of each message, including its single-use link. |
| Stripe | Payments, invoices and the billing portal. | Your email address, workspace name and ID, subscription details and the payment details you enter on Stripe. |
| Website analytics, and sign-in if you choose Google. | Analytics data described above. Name, email address and profile image for sign-in. | |
| GitHub | Sign-in, if you choose GitHub. | Name, email address and profile image. |
| Your nodes | Run the models you deploy. | Requests and responses for your workspace, relayed through the gateway. |
Providers handle data under their own terms. The hosted service runs at the location in the legal notice, which does not mean that all processing stays in the EU: Google, Stripe, GitHub and the email delivery provider can process data in other countries, and your nodes run where you installed them.
How long we keep data
Expired sessions, verification codes and invitations that were never accepted are deleted automatically by a periodic task. Other gpuOS data has no automatic deletion: account, workspace, usage and billing data are kept while the account or workspace exists, or until you delete them as described below. Deleting a node removes its record. Revoking an API key disables it and keeps its record for usage history. Accounting records of payments can be kept longer where the law requires it. The code and output of cpuOS jobs are deleted on a schedule that each workspace sets, which the cpuOS privacy policy describes.
You can download your data and delete your account yourself, in Settings > Your account. The download is a JSON file with your profile, sign-in methods, active sessions, workspaces and roles, the API keys you created (never the keys themselves) and the invitations you sent. It does not include usage history or the content of cpuOS jobs, which belong to the workspace. You can download it three times an hour.
Deleting your account removes your profile, sign-in methods and sessions, and you leave every workspace. Each workspace where you are the only member is deleted too, with its nodes, API keys, usage history and cpuOS jobs. Its Stripe subscription is cancelled and its Stripe customer deleted. Workspaces shared with other people stay: if you are the only owner of one, make another member an owner first, because the deletion is refused until then. API keys you created and invitations you sent in a shared workspace stay with it, without your name. gpuOS and cpuOS share one account, so deleting it removes it on cpuOS too.
To confirm a deletion, we send a link to your email address when email is enabled. It works for one hour, in the browser where you are signed in. Without email, you confirm with your password, or with a sign-in from the last ten minutes if you only use GitHub or Google.
Backups. The database is backed up every day. A backup holds the data described in this policy and, for cpuOS, the job code and output stored at that time. Backups are kept for 14 days on the server, and any copy stored away from the server expires within 30 days. Data that you delete, including your account, can therefore remain in a backup for up to 30 days. Backups serve only to recover the service after a failure, and we do not use them to give deleted data back to users.
Your rights
Under data protection law you can ask to access, correct, delete, restrict or export your personal data, and object to processing based on legitimate interests. You can also lodge a complaint with the data protection authority of your country, which in France is the CNIL.
Downloading your data and deleting your account are self-service, as described above. Send other requests to To be provided. We handle them manually and may ask you to confirm your identity first.
Security
Passwords, API keys and node tokens are stored as hashes. Connections to the site use HTTPS. No system is perfectly secure, and we do not hold security certifications. Do not send data through the gateway that you are not allowed to process on a hosted service.
Changes
We update this policy when our practices change. The date at the top shows the latest revision (2026-10-15).