Version 2026-11-13-3. Effective 2026-11-13. Questions or requests: use the contact form.
Oniden Privacy Policy
| Version | 2026-11-13-3 |
| Effective date | 2026-11-13 (the date revision 3 is published; filled in by the publish script) |
| Applies to | oniden.net, the Oniden dashboard, the Oniden client software and the Oniden servers, during the closed beta |
The short version
- Oniden is in a closed beta. You must agree to this policy and the Terms of Service before you sign up.
- During the free trial the client sends us diagnostic and workflow data, and you cannot turn that off while the trial lasts. If you do not want this, do not join the trial.
- That trial data includes samples of the real commands and tool actions your AI tools run. Secrets, names and paths are removed automatically on your machine before a sample is sent. Automatic removal can miss things (section 3).
- We do not collect your prompts, model outputs or file contents. The client is built to strip secrets and credentials from everything it sends.
- You can see exactly what is sent, including every command sample: before the first upload, and at any time on your own machine. Seeing is not a switch: on the trial you cannot stop a sample being sent.
- Raw trial data is kept for up to 30 days (command samples 14 days, crash reports 90 days). Only the operator of Oniden can read command samples. Section 8 lists every period.
- We identify the devices you register. The client sends scrambled values derived from hardware and operating-system identifiers, never the identifiers themselves. We use them, and a scrambled form of your network address, for device limits and to keep banned users out (sections 4.1 and 4.5).
- We keep a security log. When you sign in and when your devices get or renew access, we record your IP address, the time, your account and device, and whether the attempt succeeded. We keep each entry for 180 days, and never for less than 90. Only the operator can look entries up, and each look-up is recorded. The log is kept for that period even if you delete your account (sections 4.1 and 4.8).
- Each device is listed under your computer's name. When you add a device, the client sends the computer's name as the device's name. You can change it at any time, and the new name replaces the old one (sections 3 and 4.1).
- During the closed beta the client reads the local log and session files of Claude Desktop and LM Studio, and this is on by default. Those files can contain your conversations. The client reads them on your machine and sends only counts, timings, model ids and tool names, never the text. You can switch each reader off at any time, also on the trial. After the beta the readers are off unless you turn them on (section 4.7).
- We receive findings about repeated work, such as "the same file was read 4 times in one run". They are counts and shapes. The scrambled values the client uses to spot repeats stay on your machine (section 4.2).
- We do not sell your data, use it for advertising, or use it to train AI models.
- You can export or delete your data at any time. Deleting your account ends the trial.
- Questions and requests: use the contact form at https://oniden.net/contact.
1. Who we are and what the words mean
1.1 Oniden is operated by Oniden, LLC, a limited liability company organised in Illinois, United States. In this policy "we" and "us" mean that operator. We are the controller of the personal data described here.
1.2 Definitions:
- Service: the Oniden website, dashboard, servers and client.
- Client: the Oniden software you install on your machine, including its command line tool and the parts that connect to your AI tools.
- Dashboard: the signed-in web pages where you see your account, devices, invites and data.
- Trial: free, time-limited access granted when you redeem an invite code.
- Member: a person whose invite code was accepted and whose account is active.
- Standard data: the usage data described in section 4.2.
- Trial data: the extra diagnostic and workflow data, including redacted command samples, described in section 4.3. Our systems call this tier
trial-extended. - Content: your prompts, messages, model outputs, files and tool results.
- Command sample: a redacted copy of one command or tool action that an AI tool asked to run on your machine (section 4.3, D36).
- Closed beta: the invite-only period during which this policy applies. We announce its end in the client and on the dashboard.
- Device name: the name a device is listed under. Our systems call it the alias. It starts as your computer's name, and you can change it (sections 3 and 4.1).
- Desktop-app reader: a part of the client that reads the local log and session files of a supported desktop app on your machine (section 4.7).
- Duplicate-work finding: a count showing that the same work was done more than once, worked out on your machine (section 4.2, D38).
- Security log: our record of sign-ins and access events, with the IP address they came from (sections 4.1 and 4.8, D39).
- Hold: a decision to keep particular security log entries past their normal period for a ban, an appeal, an investigation or a legal request (section 4.8.5).
2. The trial: read this first
2.1 The products are still being stabilised. To find and fix defects quickly, trial accounts send much more diagnostic and workflow data than other accounts will.
2.2 While your account is on the trial:
- the client sends the trial data in section 4.3, which includes command samples;
- the standard data flows in section 4.2 are switched on;
- the official client gives you no switch to turn either off.
2.3 This is a condition of the free trial. If you do not accept it, do not redeem a code. If you change your mind later, you can leave the trial by deleting your account (section 11).
2.4 Trial data does not include your prompts, model outputs or file contents. It does include command samples: for a limited number of the commands and tool actions your AI tools run, the client sends the command line or the main argument (a file path, a web address, or the name of a tool) after automatic redaction. We use them to see where our checks are wrong or missing. Section 3 lists what we do not collect and the limits of redaction. Section 5 explains how you can see every sample yourself.
2.5 Your account page and the client both show whether you are on the trial and when it ends.
2.6 Consent at joining. You are shown this section, in short form, on the join page and in the client before you redeem a code, and you confirm it there. The short form says:
- trial data is sent and cannot be turned off while the trial lasts;
- trial data includes redacted command samples, and redaction can miss things;
- your computer's name is sent as the device's name, and you can change it;
- during the closed beta the client reads the local log and session files of Claude Desktop and LM Studio by default, sends counts and timings and never the text, and you can switch this off;
- findings about repeated work are sent as counts.
2.7 What is not tied to the trial. Three things apply to every member during the closed beta, on the trial or not:
- Device name. Your computer's name is sent as the device's name. You can change it (sections 3 and 4.1).
- Desktop-app readers. They are on by default during the closed beta. Unlike trial data, you can switch them off at any time, also on the trial (section 4.7).
- Duplicate-work findings. They are part of standard data (section 4.2, D38). During the trial they are on, as 2.2 says. Outside the trial they follow the switch for workflow data.
3. What we do not collect, and the limits of that
In every tier, the client is built so that these do not leave your machine:
- Content. Raw prompts, system prompts, messages, model outputs and tool results.
- Files. File contents, diffs, clipboard contents and terminal output. This includes text an AI tool writes into a file and the body of a script passed to a command.
- Secrets and credentials. API keys, tokens, passwords, cookies and the keys the client stores in your operating system's keychain.
- Names that identify you or your work. Full file paths, your operating-system user name, repository names, branch names and remote addresses. Your computer's name is sent in one place only, described below. Where a path appears in an error message or a command sample it is sent only in redacted form: the folder parts are removed and the file name is replaced by a scrambled value, unless it is a common name such as
Cargo.toml. - Email addresses and web addresses inside error text. These are replaced by markers before sending. In a command sample a web address is cut down to its site and path, and the site name is kept only for well-known public sites.
- Environment variable values, your list of running programs, or a list of your installed software. The client only notes which supported AI tools and local model runtimes are present, from a fixed list.
- Raw hardware identifiers. Your machine's system identifier, serial numbers, operating-system machine identifier and network adapter (MAC) addresses. The client reads some of these on your machine to identify the device, but only scrambled values that cannot be turned back into the identifiers are sent (section 4.5).
- Precise location.
- Advertising identifiers. We use no third-party analytics and no cross-site tracking.
Commands and tool arguments are the exception. They are not sent in their original form in any tier, and outside the trial they are not sent at all unless you choose to submit a sample (section 4.6). During the trial, redacted command samples are sent (sections 2.4 and 4.3). Before a sample leaves your machine the client removes anything its rules recognise as a secret, replaces your user name, computer name, folder names and most file names with markers, removes long quoted text and script bodies, removes long random-looking strings, and cuts the sample to a fixed short length. If any of these steps fails, the sample is discarded and not sent.
Your computer's name is sent in one place only: as the device's name. When you add a device, the client reads the computer's name and sends it, so that the device is listed under a name you recognise. The join page and the client tell you this before you add a device. A computer's name can identify you or your employer. You can change the device name at any time on the dashboard or in the client. The new name replaces the old one in your device record and your settings. The computer's name is not sent anywhere else: in error text and command samples it is replaced by a marker, and it is not used to identify the device (section 4.5).
The client works on your content locally to do its job. That work stays on your machine, except for the items listed in section 4. This includes the desktop-app readers (section 4.7): they open files that can contain conversations, work out counts and timings on your machine, and send none of the text.
Redaction is automatic and can miss things. Apart from the device name, error text and command samples are the places where text from your machine is sent, and only after redaction and shortening. A command can contain a name, an address or another detail that the client does not recognise as sensitive. If you see something in the log or sample viewer that should not be there, report it from the client or tell us through the contact form at https://oniden.net/contact. We delete that sample, and we can switch a field or the sampling off for everyone.
Some names are sent because they are settings: the device name (your computer's name until you change it) and any name you give a workflow. Do not put personal or confidential information in a name you type.
4. What we collect
4.1 Account and operational data (all accounts)
| Ref | What | Why |
|---|---|---|
| D01 | Sign-in record: account id, email address, sign-in provider, and your display name and photo address if the provider supplies them; creation and last sign-in times | To identify your account and sign you in |
| D02 | Membership: access state, plan, trial end date, join date, invite counters | To run the closed beta and decide what your account may use |
| D03, D04 | Invite records: which code you joined with, who created it, the codes you created, when they were used, and flags or suspension reason codes | To operate invites and to hold members accountable for abuse of them |
| D05, D09 | Agreement and choice records: the version and fingerprint of the Terms and Privacy Policy you accepted, the time, whether you accepted on the web or in the client, client version and browser family; your data choices and when you made them | Evidence of what you agreed to and chose |
| D06 | Devices: a device id, a fingerprint of the device's public key, the device name (your computer's name unless you changed it), first and last day seen, client version, whether it was removed | Device limits, device removal, dispute and abuse review |
| D08 | Settings: your efficiency levels, the list of models you use and how you reach them (never keys), your data choices | To keep your settings the same on each device |
| D22 | Server request logs, written by our hosting provider for every request to our servers: IP address, user agent, path, status and time. They are not linked to your account | Operations, security and abuse response |
| D23 | Admin audit trail: administrative actions that affect your account | Accountability for admin actions |
| D24 | Messages you send to us | Support |
| D26 | Device fingerprint: for each device, scrambled values derived from hardware, operating-system and installation identifiers; whether the device is a physical machine, a virtual machine or a container; how reliably it could be identified; and a record of which accounts have presented the same values | To recognise a device, apply device limits, enforce bans and detect misuse of shared hardware |
| D27 | Network record: a scrambled value derived from the network part of your IP address, noted when you redeem a code, add a device and at most once a day per device | Abuse review and temporary network holds |
| D39 | Security log (section 4.8): for each sign-in and each access event, your full IP address, the date and time, your account id, the device id, what was attempted (for example signing in, adding a device, getting or renewing an access pass, redeeming a code, accepting these documents, removing a device, exporting or deleting your account), whether it succeeded and, if not, a reason code, whether it came from the client or the website, the client version or browser family, your sign-in provider, and the plan and end time of an access pass that was issued. This replaces the log of access passes (D07) of earlier versions | Keeping accounts secure, investigating misuse and suspected takeovers, handling bans and appeals, answering lawful requests, and keeping evidence of access |
| D28, D29 | Ban and appeal records, if your account or device is blocked: the account, scrambled identity, device and network values, a reason code, dates, a reference, and the state and outcome of any appeal | To keep banned users out and to handle appeals |
4.2 Standard data
Standard data contains counts and measurements, not content. Outside the trial, each flow has its own switch and the client shows the payload before sending. During the trial all of these are on.
| Ref | What | Why |
|---|---|---|
| D10 | Usage summaries for model use: numbers of sessions and turns, token counts by kind, share served from cache, counts per model | Your dashboard; tuning the service |
| D11 | Check result counts: which rule, which result code, how often | Rule quality, including false alarms; your dashboard |
| D12 | Usage by task type: counts, time taken (in ranges), outcomes, model ids, role labels, sizes | Quality of recommendations; capacity planning |
| D13 | Workflow summaries: a scrambled identifier for the shape of a workflow (the kinds of steps and their order) with counts and costs. The identifier cannot be turned back into names or matched between users | Quality of workflow recommendations |
| D25 | Counts of uploads that the client or server blocked | To detect redaction failures |
| D30 | Feature and milestone counts: how often each Oniden command, tool and check result occurred, how long Oniden's own steps took (in ranges), the day you first reached each setup step, the number of days in a month the client was active, and counts of error and crash types | To see where setup fails, whether the products are used, and which checks need work |
| - | Device summary: your device name, hardware class and summarised load and memory figures | Recommendations that fit your machine |
| D37 | Desktop-app activity (closed beta; section 4.7): for Claude Desktop and LM Studio, numbers of sessions, messages and tool calls; token counts where the app records them, otherwise an estimate from sizes, marked as an estimate; durations and speeds; the model id if it is on our fixed list, otherwise "other model"; the tool name if it is on our fixed list, otherwise "other tool"; the app's version; and whether each reader ran or stopped. No conversation text, conversation titles, file names or file contents | To include work done in these apps in your workflow picture and your figures |
| D38 | Duplicate-work findings: for each finding, its kind (the same call repeated in a run, the same request repeated across runs, helpers started together that did the same steps, a loop that made no progress, a branch whose result was thrown away, context carried again unchanged, two workflows that look like the same work), which workflow and which step in it, the kind of tool, and counts, rates and estimated tokens. At most 20 findings per device. No tool arguments, no file names, and none of the scrambled values used to find the repeats | To show you repeated work on your dashboard, and to process the findings on our servers so that detection and recommendations improve |
How repeats are found. To recognise that two tool calls were the same, the client keeps a scrambled value for each tool call. It is made from the tool's name and its arguments with a key that never leaves your machine. These values are kept on your machine only, for 90 days, and are not sent. We receive only the findings worked out from them (D38).
4.3 Trial data (trial accounts only)
You cannot switch any of this off while your account is on the trial.
| Ref | What | Why |
|---|---|---|
| D14 | Diagnostic logs: severity, component, event and error codes, retry counts, and redacted error text of up to 512 characters | Finding and fixing defects |
| D15 | Workflow structure and timings: the scrambled workflow identifier, step number, kind of step, class of tool, duration, outcome, token counts and model id, at finer time detail than standard data. This covers steps seen by the desktop-app readers (D37) too. No step content and no tool arguments | Tuning defaults; planning features |
| D16 | Client and system information: client version, operating system family and version, processor architecture, processor, memory and graphics hardware class, periodic readings of load, memory use and power source, which supported AI tools and local model runtimes are present, and whether Oniden's integrations are switched on | Compatibility and performance on different machines |
| D17 | Performance timings: named internal operations with duration, waiting time and sizes | Keeping the client fast |
| D18 | Feature usage: which commands, tools and options were used and how often; which settings were changed. Names only, never values | Deciding what to build and fix |
| D19 | Crash reports: client version, where in Oniden's own code the failure happened, and a redacted message. No memory dumps and nothing about other programs | Reliability |
| D20 | Figures we work out from the above for your account, such as error rates and typical timings | Supporting you; comparing before and after a change |
| D36 | Command samples: for a limited number of the commands and tool actions your AI tools ask to run (at most 20 per device per day), the redacted command line, or the redacted file path, the shortened web address, or the tool name with the names (not the values) of its arguments; with the check result, the rules that matched and the hour. Not included: file contents, what a tool wrote or returned, script bodies, prompts, model output | Finding checks that are wrong or missing |
| D31 | The feature and milestone counts of D30 per day instead of per month, with the hour you first reached each setup step, and the step and error codes recorded during installation and sign-in (sent after you sign in) | Finding where installation, sign-in and setup fail |
4.6 Data you choose to send
None of this is sent unless you send it, in any tier. It is not a condition of the trial. The samples in D33 are ones you pick and send yourself; they are separate from the automatic command samples of the trial (D36).
| Ref | What | Why |
|---|---|---|
| D32 | Marks on a check result: which rule, which result, and whether you marked it right, a false alarm or a miss. No text | Rule quality |
| D33 | Samples for rule tuning: redacted text of commands, tool arguments, paths and web addresses from lines you select. You see the exact text before it is sent and can list and withdraw it afterwards | Rule tuning and finding gaps |
| D34 | Feedback and answers to questions we ask: a rating, a choice, and any text you type | Deciding what to build and fix |
| D35 | Problem reports: a bundle you can inspect before sending, with client version, machine type, recent redacted diagnostic and crash records, setting names and any note you add | Support and defects |
4.4 Combined statistics
D21. We combine data from many accounts into statistics. Each published or retained figure covers at least 5 users. We use these to tune the service and plan work, and we may publish them.
4.5 Device identification, bans and network addresses
4.5.1 When a device signs in or renews its access, the client reads a small set of hardware and operating-system identifiers on that machine, scrambles each one, and sends only the scrambled values. Your computer's name is not one of them; it is sent only as the device name (section 3). Our servers scramble the values again with a secret key before storing them. We cannot turn the stored values back into the identifiers.
4.5.2 The stored values let us recognise the same machine again, including under a different account. We use this only for device limits, abuse review and bans. We do not use it for advertising or to track you outside Oniden.
4.5.3 If we ban an account, we may also block the devices it used and, for a limited time, flag or hold new sign-ups from the networks it used. A block on a device can be applied automatically when a device closely matches a banned one. Network matches are shared by many people, so by default they are only reviewed by a person.
4.5.4 If you are blocked, you are given a reference and can appeal (Terms of Service, section 14). If you bought or share a machine that someone else used, tell us in the appeal.
4.5.5 You can see the values your client sends with the client's device identity command. You cannot switch device identification off; it is part of having an account.
4.7 Desktop-app readers (closed beta)
4.7.1 During the closed beta the client includes readers for two desktop apps: Claude Desktop and LM Studio. They are on by default for every member, on the trial or not. A reader runs only if the app is installed and the client knows that version of the app. Otherwise the reader stays off and the client says so. If we add an app, we will tell you first and list it here.
4.7.2 What is read, on your machine only.
- Claude Desktop: its log files, its local session folders (Claude Code sessions and local agent sessions) and its plan usage history file.
- LM Studio: its saved conversation files and its local server logs.
4.7.3 These files can contain your conversations. They can hold what you typed and what the model answered, and they can mention other people. The reader opens the files on your machine, works out the figures in D37 (section 4.2) in memory, and keeps and sends only those figures. It does not copy the files. It does not store or send conversation text, conversation titles, file names or file contents.
4.7.4 What the readers do not do. They do not read the apps' databases, sign-in data or keys. They do not intercept the apps' network traffic. They do not change the apps' files or settings, and they never ask you to turn on more logging in an app. Connecting Oniden to an app by editing that app's settings file is a separate step: the client shows you the edit and asks you each time.
4.7.5 Command samples. The readers produce no samples. Command samples (D36) come only from Oniden's check of commands and tool actions, under the rules and limits in sections 2.4, 3 and 4.3. If an action started in one of these apps passes through that check, it can be sampled like any other action, within the same daily limit. No other text from these apps is sent.
4.7.6 Your switch. Each reader has its own switch in the settings, on the dashboard and in the client. You can turn a reader off at any time, also on the trial. On the device where you do it, it stops at once; other devices stop the next time they check in. Figures already sent are kept for the periods in section 8. A reader you turned off stays off until you turn it on again.
4.7.7 After the closed beta. When the closed beta ends, the readers are switched off for everyone. After that a reader runs only if you turn it on.
4.7.8 We send nothing to the makers of these apps, and they do nothing on our behalf (section 9.5). Section 5.6 explains what you can inspect.
4.8 The security log and IP addresses
4.8.1 What it is. Each time you sign in and use the service, and each time one of your devices adds itself, gets or renews its access pass, or is refused, our server writes one entry to the security log. Section 4.1 (D39) lists what an entry holds. An entry never holds your password, sign-in tokens, email address, device name, or anything from your work.
4.8.2 Your IP address is stored in full. We need the full address to investigate a suspected takeover of an account, to act on a report of abuse, to review a ban or an appeal, and to answer a lawful request. A scrambled address cannot do these things. An IP address is often shared by many people, so we treat it as one piece of evidence and never as proof of who someone is.
4.8.3 It is not used for automatic decisions. Nothing is blocked, flagged or scored by a program reading the security log. The network record used for bans stays scrambled (D27, section 4.5), and only a person reads the security log.
4.8.4 How long. Each entry is kept for 180 days and then deleted automatically. We will not keep it for less than 90 days. Server request logs (D22) are kept for 90 days.
4.8.5 Holds. We keep particular entries longer only under a hold. We place a hold when we ban an account or a device, when an appeal is open, when we are investigating a specific report of misuse or of a takeover, or when a court or authority lawfully requires us to preserve them. A hold covers only the entries that matter for that case. It ends 90 days after the ban, appeal or investigation ends, or when the legal matter closes. No entry is held for more than 24 months unless the law requires it, and we review such a hold every 6 months.
4.8.6 Who can read it. Only the operator of Oniden. Entries can be looked up only for one account, one device or one IP address at a time, and every look-up, hold and export is itself recorded in the admin audit trail (D23). No other member can see your entries, and the security log is not shown on anyone's dashboard.
4.8.7 Your own entries. Your export (section 11.2) includes your own entries, with the IP address shortened. You can ask us for the full addresses through the contact form; we will first confirm that the request comes from the account holder.
4.8.8 You cannot switch the security log off; it is part of having an account.
5. Seeing what is sent
5.1 Everything the client uploads is first written to a plain-text queue on your machine. What we receive is that queue, compressed.
5.2 Before the first upload, the client shows you the queued records and your data tier and waits for you to continue. On the trial there is no "do not send" choice at that point. The alternative is not to continue, or to delete your account.
5.3 At any time you can view the tier and the reason for it, the queue, a rolling log, and the exact content of any batch already sent. The client keeps sent batches on your machine for 30 days for this purpose. The dashboard links to these views and to this list of data.
5.4 Our servers check uploads again and reject a batch that appears to contain a secret. Each command sample is checked a second time on arrival; if it appears to contain a secret, an email address or your account details, its text is discarded and only a note that this happened is kept.
5.5 Command samples. The client lists every command sample it has sent in the last 30 days and every one waiting to be sent, and shows the exact text of each. You can also type a command and see what the client would send for it. These views show you what is sent; on the trial they do not let you hold a sample back. You can report a sample that contains something it should not, and we delete it. Command samples are not shown on the dashboard.
5.6 Device name, desktop-app readers and findings.
- Your device name is shown on the Devices page of the dashboard and in the client, where you can change it.
- The client lists each desktop-app reader, whether it is on, the folders it reads and when it last ran.
- Every record made from those files (D37) and every duplicate-work finding (D38) goes through the queue, the log and the sent batches in 5.1 to 5.3, so you can check that they contain no text from your conversations.
- Findings are also shown on your dashboard.
- The scrambled values used to find repeats stay in the client's data folder on your machine for 90 days. They are not uploaded and are not shown on the dashboard.
6. Why we use the data, and the legal basis
6.1 We use the data to: provide accounts and the closed beta; show you your own figures, including repeated work; find and fix defects; tune default settings and rule quality; keep the client fast; decide what to build next; answer your support requests; prevent and investigate abuse; and keep evidence of agreements.
6.2 Where the law requires a legal basis, we rely on the following.
| Data | Legal basis |
|---|---|
| Account, membership, devices including the device name, settings (D01, D02, D06 to D08) | Performance of our contract with you |
| Invite records, request logs, admin audit trail (D03, D04, D22, D23) | Our legitimate interest in preventing abuse and operating the service |
| Security log (D39) | Our legitimate interest in keeping accounts and the service secure, preventing and investigating abuse, and keeping evidence of access; a legal obligation where a court or authority requires us to preserve or disclose entries |
| Device fingerprint, network record, ban and appeal records (D26 to D29) | Our legitimate interest in preventing abuse and enforcing bans; performance of our contract with you for device limits. |
| Agreement and choice records (D05, D09) | Legal obligation and our legitimate interest in keeping evidence |
| Standard data outside the trial (D10 to D13, D38) | Your consent, which you can withdraw with the switch for each flow |
| Desktop-app activity (D37) | During the closed beta: your agreement at joining, with a switch you can turn off at any time (section 4.7). After the closed beta: your consent, which you give by turning a reader on and withdraw by turning it off |
| Standard data and trial data during the trial (D10 to D20, D36, D38) | Your consent given when you join, and performance of the trial agreement (command samples included) |
| Combined statistics (D21) | Our legitimate interest in improving the service |
7. What we do not do
We do not sell personal data or share it for advertising. We do not use it for advertising. We do not build profiles for any purpose other than running and improving the service. We do not use it to train AI models. We do not publish any figure that covers fewer than 5 users.
8. How long we keep it
| Data | Kept for |
|---|---|
| Sign-in record (D01) | Life of the account. A sign-in with no accepted invite code is removed within 30 days, or at once if you choose "Cancel and remove my sign-in" |
| Membership (D02) | Life of the account plus 30 days |
| Invite records and flags (D03, D04) | Life of the account plus 24 months; codes for 24 months after they expire |
| Agreement and choice records (D05, D09) | Life of the account plus 6 years |
| Devices (D06) | Life of the account; removed devices 12 months. When you change a device name, the new name replaces the old one |
| Security log (D39), which includes the log of access passes | 180 days from each entry, and never less than 90. Entries under a hold (section 4.8.5): until the hold ends, at most 24 months unless the law requires longer. Kept even if the account is deleted |
| Settings (D08) | Life of the account |
| Standard data and blocked-upload counts (D10 to D13, D25) | 13 months |
| Desktop-app activity (D37) and duplicate-work findings (D38) | 13 months. The finer detail sent during the trial (D15) follows the raw trial data period |
| Scrambled tool-call values used to find repeats (section 4.2) | 90 days, on your machine only. Never sent to us |
| Raw trial data (D14 to D18) | Up to 30 days |
| Command samples (D36) | 14 days. A sample whose text was discarded on arrival (section 5.4) leaves a note without text for 90 days |
| Crash reports (D19) | 90 days |
| Per-account figures derived from trial data (D20) | Until 90 days after your trial ends |
| Combined statistics (D21) | Indefinitely |
| Server request logs (D22) | 90 days |
| Admin audit trail (D23) | 24 months |
| Messages to us (D24) | 90 days |
| Device fingerprint (D26) | Life of the device record; removed devices 12 months |
| Network record (D27) | 90 days |
| Ban records (D28) | While the ban lasts plus 24 months. A block on a device ends after at most 12 months unless renewed; a network flag or hold ends after at most 90 days. Kept even if the account is deleted |
| Appeal records (D29) | 24 months after the decision |
| Feature and milestone counts (D30); rule marks (D32); feedback and answers (D34) | 13 months |
| Daily feature and milestone counts, installation and sign-in codes (D31) | 30 days |
| Samples you send (D33); problem reports (D35) | 90 days, or until you withdraw a sample |
Timed deletion can lag by about a day.
9. Who can access it, and who processes it for us
9.1 Access to stored data is limited to the operator of Oniden. No administrative page or interface returns trial data payloads. Command samples are read only by the operator, from a protected copy that follows the same 14-day period, to correct and extend the checks. They are not shown on the dashboard, not shared, not published, and not copied word for word into our rule tests. The security log (D39) is read only by the operator, for one account, device or IP address at a time, and each look-up is recorded (section 4.8.6).
9.2 You can see your own account, device, invite, settings and standard data, including duplicate-work findings, in the dashboard, and everything we hold in an export (section 11). A member who invites you can see that their code was used and when. They cannot see who used it. No member can see another person's IP address or security log entries.
9.3 We use these service providers.
| Provider | Purpose | Location |
|---|---|---|
| Google (Firebase Authentication, Cloud Firestore, Cloud Run, Firebase Hosting, Cloud Logging, Secret Manager) | Sign-in, database, servers, website delivery, logs. The security log (D39) is stored in Cloud Firestore; server request logs (D22) are stored in Cloud Logging | Database and servers in the EU. Sign-in data, website delivery and some logs may be processed in other countries, including the United States |
| Google or GitHub, as the sign-in provider you choose | Confirming your identity when you sign in | As set by that provider |
| Proton | Email you exchange with us | Switzerland |
| Namecheap | Domain name service for oniden.net | United States |
9.4 We may disclose data where the law requires it, or if the service is transferred to a new operator. If a court or authority lawfully requires security log entries or other data about you, we disclose only what the request compels, and we tell you unless the law or the order forbids it. In a transfer, this policy continues to apply to your data until you are told otherwise and given a choice.
9.5 Desktop apps. The makers of Claude Desktop and LM Studio are not our service providers. The readers in section 4.7 work on files on your own machine. We send those companies nothing, and we receive nothing from them. Their own terms and privacy policies govern how you use their apps.
10. International transfers
Our database and servers are in the European Union. Some providers in section 9 are based in, or process data in, other countries, including the United States. The operator may also access data from the United States. Where the law requires a safeguard for such transfers, we rely on the standard contractual clauses in our providers' data processing terms. You can ask us for details.
11. Your choices and rights
11.1 See. The dashboard and the client show your account data and what was sent.
11.2 Export. You can download everything stored for your account, including decoded trial data, from the client (oniden account export) or by asking us. The export includes your own security log entries with the IP address shortened; section 4.8.7 says how to get the full addresses.
11.3 Correct. You can change your device names, settings and model list yourself. If you do not want your computer's name shown, rename the device; the new name replaces it. Your email address and name come from your sign-in provider. Ask us to correct anything else.
11.4 Delete. You can delete your account from the client (oniden account delete) or by asking us. Deletion removes your membership, devices and device names, settings, standard data including desktop-app activity and duplicate-work findings, trial data including command samples, crash reports and unused invite codes. It ends your trial.
11.5 What deletion does not remove.
- The agreement and choice records, the invite records, the admin audit trail and server request logs are kept for the periods in section 8. We keep them as evidence and to prevent abuse of invites.
- The security log is kept. Entries already written, with your account id and IP address, stay for the rest of their 180 days, or until a hold on them ends (section 4.8). We keep them so that deleting an account cannot erase the record of how it was used. The deletion itself is recorded as an entry.
- If your account or a device was banned, the ban and appeal records are kept for the periods in section 8, so that deleting an account does not undo a ban. Your export shows that a ban exists, its reason code and its dates. It does not include the scrambled values.
- Combined statistics that already include your data are not recalculated, except that a figure which would then cover fewer than 5 users is recomputed or dropped.
- Copies the client keeps on your own machine stay there until you remove them. This includes the scrambled values used to find repeats, which the client itself removes after 90 days.
11.6 Other rights. Depending on where you live, you may also have the right to object to or restrict processing, to withdraw consent, and to complain to a data protection authority. Withdrawing from the trial data condition means leaving the trial. Two things you can stop without leaving: you can switch the desktop-app readers off at any time (section 4.7), and you can replace your computer's name with another device name (section 3). Outside the trial you can stop duplicate-work findings with the switch for workflow data.
11.7 We answer requests within 30 days if you use the contact form at https://oniden.net/contact. We may need to confirm that the request comes from the account holder.
11.8 If you signed in but never redeemed a code, we hold only the sign-in record. You can remove it on the join page or ask us to.
12. When the trial ends
12.1 The client and the dashboard tell you 14 days and 3 days before the trial ends.
12.2 When the trial ends, or your account moves to another plan:
- the client stops collecting trial data, stops taking command samples, and deletes any trial data and samples it has not yet sent;
- the standard data switches return to your control, set to their documented defaults and not left on, and you are shown them once;
- raw trial data already uploaded expires on its normal schedule (up to 30 days; command samples 14 days; crash reports 90 days);
- per-account figures derived from trial data are deleted 90 days after the trial ends;
- combined statistics remain.
12.3 If no plan follows your trial, your membership ends and the retention periods in section 8 start to run. We may instead extend trials while the beta lasts. The trial data condition applies for as long as your account is on the trial.
12.4 When the closed beta ends. The desktop-app readers are switched off for everyone, whatever plan the account is on, and run again only if you turn them on (section 4.7.7). Desktop-app activity already sent is kept for the periods in section 8. Device names and duplicate-work findings are not affected by the end of the beta.
13. How we look after the data
13.1 We describe measures here. We do not promise that they will always work.
- Data is encrypted in transit.
- Stored data is encrypted at rest by our hosting provider's default.
- Only our servers can write to the database. The dashboard can read only your own records. Trial data cannot be read from the dashboard at all.
- Access to the hosting account is limited to the operator.
- The security log can be written only by our servers and cannot be read by the dashboard or the client. Look-ups by the operator are recorded.
- The client limits what it can send to fixed record types, redacts error text and command samples, discards a sample it cannot redact, and stops uploading from a device if its own leak check is triggered.
- Analysis copies made by the operator follow the same retention periods.
13.2 If we learn of a breach that affects your personal data, we will tell you and the relevant authorities as the law requires.
13.3 Report a suspected problem through the contact form at https://oniden.net/contact.
14. Cookies and browser storage
14.1 The public website at oniden.net sets no cookies and runs no scripts.
14.2 The dashboard and sign-in pages store only the following in your browser:
- your light or dark theme choice;
- if you sign in by email link, the email address you typed, so the link can be completed in the same browser;
- your sign-in state, kept by Firebase Authentication.
14.3 These pages load the sign-in library from Google's servers. We use no advertising or analytics cookies.
15. Children
Oniden is for adults. You must be at least 18, or the age of majority where you live if that is higher. We do not knowingly collect data from anyone younger. If you believe a child has signed up, tell us and we will delete the account.
16. Using Oniden at work
If you run the client on an employer's machine or on an employer's work, trial data will describe the structure and timing of that work and will include redacted samples of commands run during it. Those samples can reveal something about the work, such as which tools are used, and redaction can miss a name or detail. A work computer's name often contains the employer's name or yours, and it is sent as the device name unless you change it. The desktop-app readers count activity in Claude Desktop and LM Studio on that machine, including work conversations, though they send none of the text; you can switch them off. Make sure you are allowed to do this before you join. If you are not sure, do not use the trial for that work.
17. Changes to this policy
17.1 Each version has a version string and an effective date. Published versions stay available at a permanent address and are not edited. When you accept a version, we record the version and a SHA-256 fingerprint of its exact text.
17.2 We will tell you about changes in the client and on the dashboard, at least 30 days before they take effect where that is practical.
17.3 If a change is material, for example new kinds of data, new purposes, or new recipients, we will ask you to accept the new version. Until you do, the service will stop renewing your access. You can export and delete your data instead of accepting.
18. Contact
Privacy questions and requests, and security reports: use the contact form at https://oniden.net/contact (choose the topic that fits). We do not list a mailing address or a contact mailbox. Country: United States. No representative in the EU or UK has been appointed.