Data Processing Addendum

For personal data that reaches Userz through your app — end-user feedback, telemetry events, replay clips, attachments, and the identity you attach to them — you are the controller and Userz is the processor. Userz processes that data only on your documented instructions: the configuration of your App, the settings of the SDK you deploy, and the actions your team takes in the Userz dashboard and API.

For your account data (your team's names, emails, billing and configuration), Userz is an independent controller under the Privacy Policy.

• Subject matter. Collecting, storing, connecting and evaluating signals from your users and systems, and turning the ones you approve into work for your codebase.
• Categories of data. Feedback text and attachments; telemetry events (errors, performance, engagement, and custom events you define); replay clips where you enable them; identifiers you attach (an external user id, an email, a name); page URLs and user agents; console output your app writes; messages and issues from the sources you connect; content mirrored from coding-agent runs on your machines; redacted copies of a sample of signals kept for quality review; and, when code-aware features are enabled, excerpts of the source files in your connected repositories.
• Processing activities. 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. 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. Authorised personnel may review redacted samples (§6), and Userz trains models under the model-training terms of the Privacy Policy.
• Data subjects. End users of your applications, and members of your team.
• Duration. The term of your subscription, plus the deletion periods on the retention page.

Userz processes and stores customer data in the United States only; no EU intake or storage zone is offered.

Customer data is received, stored and processed in the United States, and the SDK cannot be configured to send it to another region. If an EU option is offered later, it will be a separate choice and will not change where existing data is held.

Userz may also process customer data on computing hardware that Userz owns and operates in the United States, connected over encrypted channels. That hardware is a Userz processing location, not a subprocessor.

Userz uses a small set of subprocessors, each bound by written terms with confidentiality, security and data-protection obligations at least as protective as this addendum, and each given access only to what its function needs. The categories and their locations are on the subprocessors page. The AI model providers are named individually on that 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. Userz gives reasonable advance notice of material additions or replacements so that you can object.

Userz maintains technical and organisational measures appropriate to the data it processes: encryption in transit and at rest; customer secrets and end-user identifiers encrypted per organisation; coding agents that run on machines the customer controls, so repositories are not copied to Userz’s servers to run them; removal of secrets from source-code excerpts; short-lived, scoped credentials; least-privilege access; and redaction before any AI model sees a signal, covering 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 unredacted). The controls are described in more detail in the security documentation.

Userz personnel with access to customer data are bound by confidentiality obligations and receive access on a need-to-know basis.

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.

Where an end user exercises a right against you, Userz assists: on your instruction, keyed on the identifier you attached to that user, Userz deletes their feedback, telemetry, replay clips and derived records, and records the erasure so it can be evidenced. Userz does not respond to end users directly on your behalf unless you ask it to.

Userz notifies you without undue delay after becoming aware of a personal data breach affecting your data, with the information you need to meet your own notification obligations, and cooperates in the investigation.

On written request, and no more than once a year unless required by a regulator, Userz provides the information reasonably necessary to demonstrate compliance with this addendum. Where that is not sufficient, Userz will discuss an audit under agreed scope and confidentiality.

On termination, your data is deleted on the schedule on the retention page; you can export feedback and signals through the API before then. Encrypted backups expire on their own cycle after live data is deleted.

This page is a summary. The binding Data Processing Addendum, including the Standard Contractual Clauses where they apply to transfers from the EEA, UK or Switzerland to the United States, is executed with your subscription agreement. To request a copy or to execute one for an existing account, write to [email protected].