Prezenca Critique

Privacy policy

Last updated: 16 October 2026

Prezenca Critique is a service of Prezenca Group, Anze Klancar s.p. ("we") that lets websites collect bug reports with a screenshot. We store the reports and deliver them to the site owner's Jira, Asana or email address. This policy describes which data we process, why and for how long.

1. Dashboard users (partners)

When you sign in with your email we store the email address and, if you give it, the time of your consent to product news. When you sign in with GitHub, GitHub shares your name, profile picture and verified email addresses with us; we keep the name, the picture and the email address of your account, do not store a GitHub access token and have no access to your repositories. When you sign in with Google, Google shares your name, profile picture and email address with us; we keep them with your account, do not store a Google access token and have no access to anything else in your Google account. When you connect an Atlassian account we store:

  • your Atlassian account ID, name and email address, so we can recognise the connection,
  • OAuth tokens for your Jira, stored encrypted (AES-256-GCM) and used only to create issues in the projects you configured,
  • the list of Jira sites your account can access, so you can pick one in the project settings.

You can revoke Jira access at any time under "Connected apps" in your Atlassian account. When your Atlassian account is closed or on your request we delete the Atlassian data and tokens; if you signed in with your email, your account itself remains until you ask us to delete it. We check Atlassian's closed-account notifications regularly.

When you connect an Asana account we store:

  • your Asana user ID and name, so we can recognise the connection,
  • OAuth tokens for your Asana, stored encrypted (AES-256-GCM) and used only to list your workspaces, projects and sections and to create tasks with attachments in the projects you configured,
  • the list of Asana workspaces your account can access, so you can pick a project in the dashboard.

You can revoke Asana access at any time in your Asana profile settings under Apps. On your request we delete the Asana data and tokens.

When you add an email address as a destination for reports, we store the address and send a confirmation link to it. Reports go to that address only after it is confirmed.

When you ask on our website to be notified about an integration that is not available yet ("Notify me"), we store your email address, the integration and the time. We use them only to tell you when that integration is available, and delete them on your request. When you suggest a tool we do not support, we store its name and, if you give it, your email address, only to tell you if we add it.

Besides the cookies that keep you signed in and protect a sign-in in progress, the dashboard keeps one cookie that remembers which sign-in method you used last (email, Google or GitHub), so the sign-in page can mark it. It holds nothing else and expires after a year. In the browser's local storage the dashboard keeps only the GitHub repository you last entered for a project under "Fix with an agent".

2. Visitors of sites with the embedded widget

The widget on a partner's site records nothing until the visitor submits a report. Until then, the latest browser console entries and JavaScript errors are held only in the browser's memory on that page and are not sent anywhere.

When the visitor submits a report, we store it. A report contains:

  • the title and comment, and the email address and priority if the visitor gave them,
  • the page URL, the referrer, browser, operating system, screen size, language and time zone,
  • the latest browser console entries and JavaScript errors on that page,
  • data the site passes to the widget with setUser (ID, name, email address) and setCustomData,
  • the annotated screenshot and any files the visitor attached.

We store a report so it is not lost when the destination is unavailable, so we can retry delivery, and so the partner's team can see it in the dashboard. We deliver it to the destination the partner chose: their Jira (through Atlassian), their Asana or an email address (sent through Resend, EU region). The partner is the controller of report data; Prezenca Group, Anze Klancar s.p. processes it on the partner's behalf.

The partner can also let AI agents read their reports (through the Model Context Protocol), with MCP connectors they create and can delete in the dashboard. An agent sees only the projects its connector is attached to. Where the partner's plan includes agent work, it can also mark a report as in progress, ready for review or resolved, with a short note, a link to its fix and how to check it; it cannot change anything else. Each read and each change is logged and shown to the partner. The agents and AI services the partner connects work on the partner's behalf, under the partner's own terms with them.

The report text and technical details are stored encrypted (AES-256-GCM) in our database (Neon, EU). Screenshots and attachments are stored in Cloudflare R2 in the EU jurisdiction. So that the dashboard can list reports, we also keep a log entry for each report: the time, title, the page address without its query string, the key in the destination (such as the Jira issue key or the Asana task ID), browser, operating system and how the report was opened.

Each project keeps reports for 30 days, 90 days or 1 year, as chosen by the partner (1 year by default). After that, the screenshot, the text and attachments are deleted; the log entry remains for as long as the project exists. The partner can delete a report or a whole project at any time, which also deletes its stored files. Copies already delivered to the partner's Jira, Asana or email address stay there, under the partner's control.

To limit abuse, we count reports per IP address; these counts are deleted within two days.

The widget uses no tracking cookies. In the browser's local storage it keeps only the visitor's own conveniences: whether the tab is shown, and the email, issue type and priority they last entered.

3. Where the data lives

We use these sub-processors:

  • Vercel, for hosting (Frankfurt),
  • Neon, for the database (EU),
  • Cloudflare, for storing screenshots and attachments (R2, EU jurisdiction),
  • Resend, for email: sign-in links, address confirmations and reports sent to an email address (EU region),
  • Atlassian, only as the destination a partner connects (their Jira),
  • Asana, only as the destination a partner connects (their Asana).

We do not sell data and do not share it with third parties beyond what is necessary to run the service. A data processing agreement is available on request; write to support@prezen.ca.

4. Your rights

You can request access to, correction or deletion of your data. Write to the address below; we respond within 30 days.

5. Contact

Prezenca Group, Anze Klancar s.p., Jozeta Jame 12, 1210 Ljubljana, Slovenia, email: support@prezen.ca.