LEGAL
Privacy policy
Last updated 2026-10-13.
This policy explains what personal data systemonemodels.ai ("System One Models", the "Service") collects, why, who it is shared with, how long it is kept, and the rights you have under the EU and UK General Data Protection Regulation ("GDPR") and US privacy laws, including the California Consumer Privacy Act as amended by the CPRA ("CCPA") and other US state privacy laws.
1. Who is responsible
The Service is operated by Gilver.ai, Inc., a Delaware corporation, United States ("Gilver.ai", "we", "us"). Gilver.ai is the controller of your personal data for the Service under the GDPR and the "business" under the CCPA.
Contact. [email protected], or by post to Gilver.ai, Inc., 8 The Green, Suite R, Dover, DE 19901, United States.
The Service is a public preview. If System One Models is incorporated as its own company, your data may transfer to it as described in section 11.
2. What we collect
Account data. Email address, username, display name, password (stored only as a hash), two-factor sign-in settings, and when you accepted these terms and this policy.
Profile and organisation data. Avatar, bio, links, organisation names and membership, and roles.
Published content. Models, files, manifests, model cards, evaluation results and comments you publish. Content you make public is visible to anyone, together with your username.
Course and certificate data. Lesson progress and, if you claim a certificate, the name you enter, the course, the completion date and a certificate number.
Playground and inference inputs. The inputs you send to models and the outputs returned. We use them to answer the request and do not store them. For each request we keep a usage record: the model, the time, the number of questions and tokens, how long it took, where it ran, and the account or API key that sent it.
Billing data. Your credit balance and its history: free credit, the packs you buy, what each GPU answer cost, refunds and adjustments. For each purchase we keep the pack or plan, the amounts and Paddle's references for you, the transaction and any subscription. We do not receive or store your card or other payment details: Paddle collects them (section 4).
Technical data. Your IP address, browser user agent, and the time and address of each request, in our server and security logs (section 6).
Usage data from our website. When you open a page of the website, your browser sends us a short record of the page view. It contains the page's address, with secret parts such as an invitation token removed. It names the website that linked to it (its address without any query string, or only our domain when the link was on one of our own pages), the campaign tags in the link (such as utm_source), and the names but not the values of other parameters in it, such as an advertising click identifier. It also says how the page was opened (a link, a reload, back or forward), your screen size class, preferred language, time zone, whether your device has a touch screen, the operating system your browser reports, and whether your browser shows signs of being controlled by software, such as the WebDriver flag. While the page is open and when you leave it, it reports how long the page was visible, how far you scrolled and whether you interacted with it. Your time zone is only compared with your network's, to spot automated traffic, and is not stored. Our servers add your country and the network operator your connection comes from, both looked up from your IP address, and your browser, its version, operating system and device type, read from your browser's user agent. They also record whether the view came from a signed-in account and whether a sign-up or a new API token happened during the visit. They do not record which account, we do not link these records to accounts, and we only ever look at these two as totals; section 8 explains how a record can still be matched to you by its time. We use these records to count visits and where they come from, and to tell people from automated traffic. We do not store your IP address or full user agent for this, and we do not set a cookie for it. The pages you open in one browser tab are grouped into a visit by a random identifier that the page holds in memory and loses when you reload or leave the site (section 10). Pages you open from it within 30 minutes, in the same or another tab, are joined to the same visit using the daily code described next. Your page views on the same day are linked by a code made from your IP address and user agent with a key that changes every day and is then deleted, so we cannot link your visits across days. After 30 days we remove the network operator from records of people, keeping it only for traffic we judged automated, and shorten your language to its main part (for example "en" instead of "en-US"). If your browser sends a Global Privacy Control signal, it sends only the page, the linking website's domain and campaign tags. Our servers still add your country, network type, browser, operating system and device type to tell people from automated traffic, and do not link the view to your other page views.
Communications and preferences. Messages you send us, including support, takedown and privacy requests, and your email preferences and consent records.
Where it comes from. Directly from you; automatically from your browser, device or the CLI; and from sign-in providers you choose to connect.
What is required. An email address, username and password (or a sign-in provider) are needed to create an account, because we cannot provide an account without them. Everything else is optional, but some features will not work without it.
Sensitive data. We do not knowingly collect special categories of data under Article 9 GDPR, such as health, biometric, religious or political data. Please do not include it in your profile, content or playground inputs. Your password and API tokens are "sensitive personal information" under the CCPA; we use them only to authenticate you and secure the Service, never to infer characteristics about you.
3. Why we use it
| Purpose | Data used | Legal basis (GDPR) |
|---|---|---|
| Run your account and the registry | Account, profile, content, credentials | Contract |
| Run the playground and inference | Inputs and outputs | Contract |
| Sell and keep account of credit and plans, and handle refunds and disputes | Billing data, email | Contract, legal obligation |
| Send your inputs to a third-party model provider you select | Inputs and outputs | Contract (at your direction) |
| Issue and verify certificates | Certificate data | Contract |
| Secure the Service and prevent abuse | Technical data, usage data, credentials | Legitimate interests |
| Show usage counts and improve the Service | Technical data, usage data, aggregated usage | Legitimate interests |
| Send service notices (security, policy changes, transfer notices) | Contract, legitimate interests | |
| Send product news | Email, consent record | Consent, withdrawable at any time |
| Meet legal obligations and handle complaints | Any relevant data | Legal obligation, legitimate interests |
Our legitimate interests are keeping the Service secure, preventing fraud and abuse, understanding aggregate usage to improve the Service, and establishing or defending legal claims. We have weighed these against your rights, and you can object to this processing (section 8).
Every product news email includes an unsubscribe link, and you can withdraw consent at any time without affecting processing that took place before.
We do not sell your personal data, "share" it for cross-context behavioral advertising, use it for targeted advertising, or use your private inputs and outputs to train models. We do not make decisions based solely on automated processing, including profiling, that produce legal or similarly significant effects on you.
4. Who we share it with and what is public
Public information. Content you make public is visible to anyone with your username. Certificate verification pages show the name you entered, the course, the completion date and the certificate number, and can be found by anyone with the number, link or QR code. You can ask us to remove a certificate page at any time at [email protected].
Service providers (processors). We use providers for cloud hosting, GPU computing and storage, databases, email delivery, authentication, error monitoring and analytics, and support tools. They process personal data only on our instructions under written contracts that meet Article 28 GDPR and the CCPA's service-provider requirements, and may not use it for their own purposes.
Paddle. Credit, and plans bought through checkout, are sold by Paddle.com, our reseller and Merchant of Record. When you buy credit or a plan, you give your payment details, billing address and any tax number to Paddle directly, and Paddle processes them under its own privacy notice (paddle.com/legal/privacy) as an independent controller. We give Paddle your email address to identify you at checkout, and Paddle gives us the amounts paid and its references for you and the purchase, never your card details.
Third-party model providers. When you use a model hosted by another provider in the playground, your inputs are sent to that provider at your direction and handled under its privacy policy as an independent controller. The model page shows who the provider is.
Other disclosures. We may disclose data to professional advisers under confidentiality duties; to comply with law or valid legal process; to protect the rights, safety or property of users or others; or to a successor company as described in section 11.
5. International transfers
We are based in the United States, and our team and providers may access or process data in the United States, Nepal and other countries whose laws may not protect data to the same standard as your home country.
When we transfer personal data from the European Economic Area, the United Kingdom or Switzerland to a country without an adequacy decision, we use the European Commission's Standard Contractual Clauses (with the UK International Data Transfer Addendum where relevant), or rely on a recipient's certification under the EU-U.S. Data Privacy Framework, together with supplementary measures where needed. You can request a copy of these safeguards by contacting us.
6. How long we keep data
- Account and profile data: while your account exists, then deleted within 30 days of account deletion.
- Published content: until you delete it; backups are overwritten within 35 days.
- Playground and inference inputs and outputs: not stored; discarded once the answer is returned.
- Usage records of requests: while your account exists; after it is deleted they are kept with no link to you.
- Billing data: your balance while your account exists; the record of purchases, refunds and what credit paid for, for as long as tax and accounting law requires.
- API tokens and device-login sessions: until they expire, you revoke them or you delete your account.
- Server and security logs: 90 days.
- Usage data from our website: page-view records for 400 days (about 13 months), then deleted. Records of views we judged to be automated are kept for 90 days, then reduced to daily counts by page. Daily counts of automated visits by crawler name and page are kept for 400 days. The network operator is removed from records of people after 30 days. The daily key that links a day's page views is deleted after two days.
- Certificate records: while the certificate exists, so it can be verified.
- Communications, support and privacy requests: 24 months after the request is closed.
- Records needed for legal reasons (such as takedown notices): as long as the law requires.
- Aggregated or de-identified data, which no longer identifies you, may be kept longer. We will not try to re-identify it.
7. Security
We use encryption in transit, hashed passwords, scoped access tokens and access controls to protect data. No system is completely secure. If a personal data breach occurs, we will notify the relevant supervisory authority within 72 hours where the GDPR requires it, and notify affected users without undue delay where the GDPR or US state breach-notification laws require it.
8. Your rights
Everyone. You can access, correct, delete or export your data, and delete your account and content directly in your account settings.
EEA, UK and Swiss residents (GDPR). You have the right to access your data; correct it; erase it; restrict its processing; receive it in a portable format; object to processing based on legitimate interests; object at any time to direct marketing; withdraw consent at any time; and not be subject to decisions based solely on automated processing. You also have the right to lodge a complaint with a data protection supervisory authority, in particular where you live or work or where you think your rights were infringed. EU authorities are listed at edpb.europa.eu; in the UK it is the Information Commissioner's Office (ico.org.uk).
US state residents. Residents of California, Colorado, Connecticut, Virginia, Utah, Texas, Oregon and other states with comprehensive privacy laws may have the right to:
- know what personal data we collect, use and disclose, including its categories, sources, purposes and recipients, and get a copy of it;
- correct inaccurate personal data;
- delete personal data;
- receive it in a portable format;
- opt out of the sale or sharing of personal data, targeted advertising and profiling (we do none of these);
- limit the use of sensitive personal information (we already use it only for permitted purposes);
- not be discriminated against for exercising these rights; and
- appeal our decision on a request (see below).
Global Privacy Control. We treat a Global Privacy Control signal from your browser as a valid request to opt out of sale and sharing. We also limit our own visit counting for that browser: it records only the page view described in section 2, with no link to your other page views.
Website usage records. These records carry no name, account or lasting identifier, and we do not link them to your account. They can still be matched to you by their time: for example, the records of the visit in which you signed up or created an API token, or of pages you opened while signed in, sit close in time to your account's own records. If you ask for your website usage records, we will look for them that way and show or delete what we find. To limit what is recorded, turn on Global Privacy Control in your browser.
Authorized agents. You may use an authorized agent to make a request. We may ask the agent for signed permission from you and ask you to verify your identity directly.
Appeals. If we decline your request, you can appeal by replying to our decision with "Appeal". We will respond within the time your state's law requires (generally 45 to 60 days). If we deny your appeal, you may contact your state Attorney General.
How to make a request. Email [email protected] from your account email. We will verify your identity, normally by matching your account email, and may ask for more information if needed. We respond within one month under the GDPR and within 45 days under US state laws. Where the law allows us to extend this for complex requests, we will tell you why. Requests are free unless they are manifestly unfounded or excessive.
9. Additional notice for California residents
In the past 12 months we collected the categories of personal information below and disclosed them for business purposes to the recipients shown. We have not sold or shared personal information, and we have no actual knowledge of selling or sharing the personal information of consumers under 16.
| CCPA category | Examples | Disclosed for a business purpose to |
|---|---|---|
| Identifiers | Email, username, IP address, account IDs, API tokens | Hosting, authentication and email providers |
| Customer records | Name on a certificate, email address | Hosting and email providers |
| Commercial information | Credit and plans bought, credit spent, refunds | Paddle, our reseller and payment processor |
| Professional or education information | Course progress, certificates, organisations and roles | Hosting providers |
| User content and inputs | Published content, playground inputs and outputs | Hosting providers; third-party model providers at your direction |
| Internet or other electronic network activity | Pages viewed on our website, the linking site, campaign tags, browser and device type | Hosting providers (Cloudflare) |
Sources, purposes and retention periods for each category are described in sections 2, 3 and 6. We use sensitive personal information only for purposes permitted under the CCPA regulations. We do not disclose personal information to third parties for their own direct marketing purposes.
10. Cookies and similar technologies
We use cookies and local storage that are strictly necessary to sign you in, keep your session and secure the Service. These do not require consent.
Your answers to offer cards. When you answer one of the Service's offer cards (such as free credit for signing up), we remember your answer so the card stays away: 3 days for "Remind me later" (and for "Claim" on the card shown when you are signed out), 30 days for "Not interested". Signed out, the answer is kept only in your browser, in local storage and a first-party cookie (s1_offer_signup) that our servers do not read; signed in, it is kept with your account, with a copy in your browser's local storage. Showing a card stores nothing, and these marks are never used to track you or for advertising.
Counting visits. To count visits to our website and tell people from automated traffic, our pages read the details from your browser described in section 2 and send them to us with each page view. The pages you open in one tab are grouped into a visit by a random identifier held in the page's memory, which is gone when you reload or close the tab. We do this ourselves, only to measure our own website, and never to track you on other sites. We use no third-party analytics and no advertising or cross-site tracking cookies. If we ever add analytics cookies, we will set them only after you consent where the law requires it, including in the EEA and UK. If your browser sends Global Privacy Control, our pages send only the minimum described in section 2.
Do Not Track. Browser "Do Not Track" signals have no agreed standard, so we do not respond to them. We do not track you across third-party websites, and we honor Global Privacy Control as described in section 8.
11. Transfer to a successor company
If System One Models is incorporated as a separate company, or if Gilver.ai is involved in a merger, acquisition or sale of assets, your data may be transferred to the new or acquiring company, which will become the controller of your data and will be bound by this policy. We will notify you by email at least 30 days before the transfer, name the new company, and you may delete your account before then.
12. Children
The Service is not directed to children under 16, and we do not knowingly collect their data. If you believe a child has given us data, contact us and we will delete it.
13. Changes
We will post updates here and change the "Last updated" date. For material changes, we will notify account holders by email before they take effect. Where a change requires your consent under applicable law, we will ask for it.
Contact
Gilver.ai, Inc., operator of System One Models · 8 The Green, Suite R, Dover, DE 19901, United States · [email protected]