Privacy Policy
How Userz, Inc. collects, uses, and protects information when you, your team, and your end users use the Userz platform.
Last updated: 16 October 2026
1. Who we are and what this policy covers
Userz, Inc. ("Userz," "we," "us") operates the Userz platform: the userz.ai website, the web console, the desktop and mobile apps, our APIs, and the embeddable feedback widget and SDKs (together, the "Service"). This Privacy Policy explains what information we handle, why, who we share it with, and the choices you have.
For privacy questions or requests, contact [email protected].
This policy does not cover the websites or applications of our customers, even those that embed our widget, or the third-party tools you connect to the Service (such as your source-code host, chat platform, issue tracker, or the coding agent tools on your machines). Those are governed by their own privacy policies.
2. Our role: controller and processor
Where we decide how information is used, we are its controller. This covers information about visitors to our website, people who request access, and the people who hold Userz accounts, as well as the diagnostic and usage information we collect to run the Service.
Where we process information on a customer's behalf, the customer is the controller and we are its processor. This covers the content a customer's organization brings to the Service: the signals it collects (including feedback from its end users), its source code, the run content mirrored from its machines, and the work produced from them ("Customer Content"). Our handling of Customer Content is governed by our agreement with that customer, including our Data Processing Agreement.
If you are an end user of one of our customers and want to exercise a right over information you submitted through their app, please contact that customer. We are generally not able to act on those requests directly, but we will help the customer respond.
3. Information we collect
3.1 Account information
When you create an account, we collect your name, email address, and the identifier supplied by the sign-in method you choose, as well as the organizations you belong to and your role in each. We also keep a record of each version of our Terms of Service you accepted and when you accepted it.
3.2 Access requests and correspondence
If you request access to the Service, we collect what you enter on the form, such as your email address, name, company, and how you plan to use Userz. If you contact us, we keep the correspondence so we can respond and follow up.
3.3 Billing information
The Service is free during the private beta, and we do not collect payment details. When paid plans are introduced, card details will be submitted directly to our payment processor; we will receive only what we need to manage your subscription, such as a customer reference, subscription status, and invoice metadata.
3.4 Organization configuration and connections
Organization and app settings, and the repositories, chat platforms, issue trackers, and other sources you connect, along with the credentials those connections need. Credentials are encrypted at rest and isolated to your organization. You can disconnect a connection at any time, and you can also revoke our access from the connected service's own settings.
3.5 Signals
Signals are what the sources you connect send to the Service. They include feedback from your end users through the widget and SDKs (with any screenshots, attachments, console output, replay clips, and page or component context you enable), messages from the channels you connect, issues and comments from the trackers you connect, and error and performance events from the SDKs. An end user's identity is included only when your integration provides it. Before any AI model sees a signal, Userz removes API keys, tokens and other secrets, signed session tokens (JWTs), email addresses, payment card numbers, US Social Security numbers, North American phone numbers, IPv4 addresses; an organization may choose to keep a category, such as email addresses, unredacted.
3.6 Source code
Coding agents run on machines you control, not on our servers, and we do not copy your repositories to our servers to run them. When code-aware features are enabled, Userz keeps an index of excerpts of the source files in your connected repositories, stored in the United States, so the Service can relate signals to your code. Secrets such as API keys and tokens are removed from each excerpt before it is stored. Excerpts may be sent to the AI model providers named on the subprocessors page while the Service processes your signals.
3.7 Run content from your machines
While a coding agent works on one of your machines, the Userz desktop app sends us a copy of the run so your organization can follow and review it from the web console and the mobile app. A run's content can include the conversation with the agent, the changes it made, its terminal output, and what it learned about your codebase.
This mirroring is on by default. Each kind of content can be switched off for each machine in the desktop app, and an organization's administrators can switch it off for the whole organization. When a kind of content is switched off, our servers refuse it rather than store it.
3.8 Your machines and devices
For each machine you connect, we keep its name, platform, status, and which repositories and agent tools are available on it. If you enable notifications on the mobile app, we keep the push token your device's platform issues so we can deliver them.
3.9 Usage and diagnostics
Server logs, kept at the level of detail we need to operate and secure the Service (they do not include request bodies); crash and error reports from our apps; the app version and platform when our apps check for updates; and aggregated usage measurements such as job counts and durations. Product analytics are collected only if you allow them: the website, the desktop app, and the mobile app each ask first, and analytics stay off until you agree.
3.10 Cookies and local storage
The Service uses a first-party cookie to keep you signed in, and local storage for preferences such as your theme. Our website asks before it measures anything; if you allow analytics, our analytics tools keep a pseudonymous identifier in your browser, and if you decline, nothing is measured. You can change your answer at any time with "Analytics preferences" at the foot of every page. We do not use advertising or cross-site tracking cookies.
4. How we use information
We use the information above to:
- Provide, operate, and secure the Service, including evaluating signals, turning them into work, and coordinating the coding agents that run on your machines.
- Authenticate users, enforce organization-scoped access, and prevent abuse.
- Decide and respond to access requests during the private beta.
- Send service communications, such as account verification, security alerts, and notices about changes to the Service or these policies.
- Detect, investigate, and respond to security incidents and misuse.
- Process payments and manage subscriptions, once paid plans exist.
- Understand and improve the Service, using diagnostics, aggregated or de-identified usage information, and product analytics where you have allowed them.
- Train and evaluate the models that power the Service, and have authorised personnel review redacted samples of signals, as described below.
- Comply with legal obligations and enforce our Terms of Service.
Userz uses third-party AI model providers to process signals and related content, such as excerpts of your code, to provide the Service. The providers are named on the subprocessors page, and the list will grow as Userz adds providers.
Model training. Userz may use customer data to train and improve the models that power the Service. A model trained on your organization’s data alone serves only your organization. Models shared across customers are trained only on synthetic data, on redacted data that Userz personnel have reviewed and labelled, or on data a customer has agreed may be used for that purpose. Your organization may opt out of training on its data by writing to [email protected]; its data is then excluded from every later training run, and any model trained for your organization alone is retired. Under their published terms, the AI model providers named on the subprocessors page do not train their own models on the data Userz sends them.
Human review. Authorised Userz personnel may review a sample of signals, and how the Service handled them, to measure and improve its quality. They see only the redacted copy of a signal, never the original submission, and every review is recorded against the person who made it. This review is subject to the model-training terms of the Privacy Policy.
Automated decisions. The Service uses automated processing to evaluate signals and propose work for your team. It does not make decisions that produce legal or similarly significant effects about individuals.
Marketing email. If we send product news or other promotional email, you can unsubscribe at any time using the link in the message. Service communications about your account cannot be switched off while you have one.
5. Legal bases (EEA, UK, and Switzerland)
Where the GDPR, UK GDPR, or Swiss law applies, we rely on:
- Performance of a contract: to provide the Service to customers and their users.
- Legitimate interests: to secure the Service, prevent abuse, respond to access requests, and improve the Service, where those interests are not overridden by your rights.
- Consent: for analytics on our website and in our apps, which you can withdraw at any time.
- Legal obligation: to comply with applicable law.
For Customer Content, the customer is the controller and is responsible for the lawful basis on which it collects signals from its users.
6. Sub-processors
We rely on a small set of vetted sub-processors to operate the Service. Each is bound by written terms requiring appropriate confidentiality, security, and data-protection obligations, and each receives only what it needs to perform its function. The categories are:
- Cloud hosting, managed-database, and object-storage providers.
- Content-delivery, DNS, and edge-network providers.
- Authentication and identity providers.
- Transactional-email delivery providers.
- Crash and error reporting, and product analytics (analytics only with consent).
- Payment processors, once paid plans exist.
- AI model providers, named on our subprocessors page. This list will grow: Userz adds AI providers as the Service improves, and names each one on the subprocessors page before it processes customer data.
A current list naming the providers in the other categories is available on request to [email protected]. We give reasonable advance notice of material additions or replacements so that customers with concerns can raise them.
Services you connect. Source-code hosts, chat platforms, and issue trackers are contacted only once you connect your own account, and only for what you connect. The coding agent tools on your machines (such as Claude Code or Codex) run under your own accounts with their makers; what those makers do with the content your agents send them is governed by your agreements with them, not by this policy.
7. How we share information
Beyond our sub-processors, we disclose information only:
- Within your organization, as the Service is designed to work: members of an organization can see the signals, work, and mirrored run content it holds, subject to their role.
- When you direct us to, for example when the Service opens a pull request in your repository or posts to a channel you connected.
- When required by law, subpoena, court order, or governmental request. Where we can, we will notify the affected customer first unless legally prohibited.
- When necessary to investigate fraud, abuse, or security incidents, or to protect the rights, property, or safety of Userz, our customers, or others.
- In connection with a merger, acquisition, financing, or sale of assets, in which case we will provide notice and the recipient will be bound by the commitments in this policy.
- With your consent.
We do not sell personal information, and we do not share it for cross-context behavioral advertising.
8. Data retention and deletion
Deleting it yourself. You can delete your account at any time from Settings → Delete account, on the web, desktop, or mobile app. This also deletes any organization of which you are the only member. An organization's owner can delete the organization and everything it holds from Settings → Delete organization. Deletion starts immediately and normally completes within minutes.
- Account and organization data: kept while the account or organization exists, and deleted when you delete it (longer only where the law requires, such as tax records once paid plans exist).
- Encrypted credentials: deleted when you disconnect the connection or when the organization is deleted.
- Signals, work, and mirrored run content: kept for the life of the organization unless deleted earlier.
- Screenshots, attachments, and replay clips: kept for the period on our Data retention page.
- Code index: The code index is kept current with your connected repositories, replacing older excerpts as they are re-indexed, and is deleted when your organization is deleted or on request to [email protected].
- Quality-review labels and processing records: kept for the periods on the Data retention page.
- Server logs: approximately 30 days, then aggregated or deleted.
- Backups: encrypted, and expire on their own within 30 days, so deleted data can remain in them until then.
After a deletion we keep a record that it happened, with a one-way hash of the email address rather than the address itself, and, where an account's access was revoked for a breach of our Terms, the record of that revocation. Anything the Service already delivered into your own systems, such as branches and pull requests in your repositories, is yours and is not affected.
You can also request deletion by writing to [email protected].
9. Security
We protect information with administrative, technical, and organizational safeguards appropriate to a service that handles source code and acts on third-party content, including encryption in transit and at rest, per-organization isolation, scoped and short-lived credentials, least-privilege access controls, and layered protections against malicious content in signals. No system is perfectly secure, and you should evaluate our controls against your own risk profile before connecting sensitive repositories. If we become aware of a breach affecting your information, we will notify you and the relevant authorities as the law requires.
Customers with specific assurance needs can contact [email protected]. To report a vulnerability, write to [email protected].
10. International transfers
Userz is based in the United States. Userz processes and stores customer data in the United States only; no EU intake or storage zone is offered. Where we transfer personal information from the EEA, UK, or Switzerland to the United States, we rely on Standard Contractual Clauses (and the UK Addendum, where applicable).
11. Your rights and choices
Depending on where you live, you may have the right to:
- Access the personal information we hold about you.
- Correct inaccurate information.
- Delete your information.
- Restrict or object to certain processing.
- Receive a portable copy of your information.
- Withdraw consent where processing is based on consent.
- Lodge a complaint with your local supervisory authority.
You can delete your account yourself at any time (Section 8), and you can withdraw consent to analytics at any time in the app's settings or with "Analytics preferences" on our website. To exercise any other right, email [email protected] from the address associated with your account. We may need to verify your identity before acting on a request. For information collected through a customer's application, please contact that customer first (Section 2).
US state privacy rights. Residents of California and other US states with comprehensive privacy laws have the rights above, including the rights to know, delete, and correct, and to limit the use of sensitive personal information. In the last 12 months we have collected the categories described in Section 3: identifiers, account and commercial information, internet or other electronic network activity, and the content you or your organization submit. We do not sell or share personal information for cross-context behavioral advertising. You may use an authorized agent to make a request, we will not discriminate against you for exercising your rights, and if we decline a request you may appeal by replying to our decision.
12. Children
The Service is intended for business use and is not directed to children under 16. We do not knowingly collect personal information from them. If you believe a child has provided us with personal information, contact [email protected] and we will delete it.
13. Changes to this policy
We may update this policy from time to time. We will post the new version here with a new "Last updated" date. For material changes, we will also email account owners at least 14 days before the change takes effect. Continued use of the Service after the effective date constitutes acceptance.