Text for your privacy policy

Paste-ready paragraphs and storage-table rows that describe DebugGo accurately. Pick the variant that matches how you installed it.

Fill in the brackets

Replace [DebugGo legal entity name], the contact address and the retention period with your own values before publishing. The retention period must match the diagnostics retention set on your project in the dashboard (30 days by default). This text describes the product; it is not legal advice, and your own counsel decides what your policy needs.

Team-only installs

For projects installed with the team-only loader. Visitors never contact DebugGo, so this text explains the inline check and what happens for invited reviewers.

Website review tool (DebugGo)

We use DebugGo, a feedback and website-review service provided by [DebugGo legal entity name] (https://debuggo.dev), so that our own team and reviewers we invite can comment on pages of this website while looking at them. DebugGo processes data on our behalf as our processor.

For ordinary visitors the tool does nothing: no script is loaded from DebugGo, no data is sent to DebugGo, and nothing is stored in your browser. A small piece of first-party code on each page checks whether the address contains a review link and whether a DebugGo review entry already exists in your browser; if neither is the case, it stops.

The tool becomes active only for a person who opens a private review link we issued. For that reviewer, DebugGo keeps a review token and the display name they choose in the browser for up to 30 days (or until they exit the review), and receives the comments they submit together with the page address and their screen size. If a reviewer sends a bug report and leaves "Include technical details" selected, the report also contains their browser name, version and operating system and the most recent console messages and failed network requests recorded on this website from the moment they opened the tool, with email addresses and access tokens redacted before sending. DebugGo stores this data in the United States (AWS us-east-2) and deletes technical details after 30 days.

A full description of what the tool reads, stores and sends is published at https://debuggo.dev/docs/privacy/widget.

Storage table rows

Markdown rows for a cookie or storage table. The entries only exist in a reviewer's browser, which is worth saying in the table.

storage rows, team-onlytext

| Name | Type | Set by | Set when | Duration | Purpose |
|---|---|---|---|---|---|
| debuggo:review:<project key> | localStorage | DebugGo | Only after a private review link we issued is opened | 30 days, or until the reviewer exits | Keeps the reviewer's session across pages. Strictly necessary for the review service; never created for ordinary visitors. |
| debuggo:reviewer:<project key> | localStorage | DebugGo | Only when a reviewer first enters a name or sends a comment | 30 days from the last comment, or until the reviewer finishes the review | Random reviewer id and chosen display name, so the reviewer can edit their own comments. Strictly necessary. |

Add this row only if you installed with data-review-storage="cookie", and drop the first localStorage row in that case:

cookie row, optionaltext

| debuggo_review_<project key> | Cookie (first-party, SameSite=Lax, Secure) | DebugGo | Only after a private review link we issued is opened | 30 days | Keeps the reviewer's session across pages. Strictly necessary; replaces the localStorage entry on sites that chose cookie storage. |

Everyone installs

For projects where every visitor can open the feedback bubble. The second paragraph has an alternative sentence in brackets for sites that load the script after consent or self-host it.

Feedback widget (DebugGo)

This website uses the DebugGo feedback widget, provided by [DebugGo legal entity name] (https://debuggo.dev), so that you can send us feedback and bug reports directly from the page you are on. DebugGo processes this data on our behalf as our processor.

When a page loads, your browser downloads the widget script from debuggo.dev. Like any file download, that request shares your IP address, browser type and the page address with DebugGo's hosting provider, which keeps request logs for a limited time. [If you load the widget only after consent or self-host it, replace this sentence with: "The widget script is only loaded after you have given your consent in our cookie settings." or "The widget script is served from our own domain and no request is made to DebugGo until you send a report."]

The widget does not set cookies, does not create an identifier for you, does not track you across websites, and sends nothing to DebugGo until you press Send. What you send is the message you typed, an email address if you choose to enter one, the address of the page (without query parameters), and your screen size. If you send a bug report and leave "Include technical details" selected, the report also contains your browser name, version and operating system, the most recent console messages and failed network requests recorded on this website from the moment you opened the widget, any page elements you selected, and any screenshot you attach. Email addresses, access tokens and similar values are redacted before sending.

We use this data to answer your feedback and to fix the problems you report. Technical details are deleted after [30] days; your message is kept until we delete it or you ask us to. To have a submission deleted, contact us at [your contact address]. The legal basis is our legitimate interest in receiving the feedback you chose to send (Art. 6(1)(f) GDPR) and, where technical details are included, your consent given by leaving the option selected (Art. 6(1)(a) GDPR). [TODO: have your own counsel confirm the bases for your jurisdiction.]

A full description of what the widget reads, stores and sends is published at https://debuggo.dev/docs/privacy/widget.

If you use data-capture="always"

If you installed the widget with data-capture="always", replace "from the moment you opened the widget" with "from the moment the page loaded" in the paragraph above, and classify the widget under a consent category in your cookie settings.

Storage table rows

storage rows, everyonetext

| Name | Type | Set by | Set when | Duration | Purpose |
|---|---|---|---|---|---|
| (none) | – | DebugGo | – | – | The feedback widget sets no cookies and writes nothing to browser storage for visitors. Console messages and failed requests are held in memory only while the page is open, after you open the widget, and are sent only if you submit a bug report with "Include technical details" selected. |
| debuggo:review:<project key> | localStorage | DebugGo | Only after a private review link we issued is opened | 30 days | Keeps a reviewer's session across pages. Strictly necessary; never created for ordinary visitors. |
| debuggo:reviewer:<project key> | localStorage | DebugGo | Only when you first enter a name or send an on-page comment (after a review link, or on sites using the unified experience) | 30 days from the last comment | Random reviewer id and chosen display name, so you can edit your own comments. Strictly necessary. |

Facts behind the text

Every claim above maps to a line in the data sheet. If you shorten the paragraphs, keep these points, because they are the ones people ask about.

Claim	Where it is documented
Nothing is sent until Send is pressed	Data sheet: what a report contains
No cookies or storage for ordinary visitors	Data sheet: browser storage
30-day lifetime of review entries	Data sheet: browser storage
Capture starts on open, not on load	Data sheet: capture modes
Redaction before sending	Data sheet: redaction
Technical details deleted after 30 days	Data sheet: retention and deletion
DebugGo is your processor	Data processing agreement
Where the data is stored	Sub-processors