Cookie policy

1.1Cookies are small text files that a website places in your browser when you visit. They are widely used to make websites work correctly and to give website operators information about how their sites are used.

1.2This Cookie Policy explains which cookies Reqio uses, why we use them, and how you can control them.

2.1When you sign in to the Reqio dashboard, we set a strictly necessary session cookie. This cookie keeps you signed in as you navigate between pages. Without it, you would be signed out on every page load.

2.2The sign-in flow sets two further short-lived, strictly necessary first-party cookies: one that protects the sign-in forms against cross-site request forgery, and one that remembers which page to return you to after sign-in.

2.3Strictly necessary cookies are exempt from consent requirements under the EU ePrivacy Directive and equivalent rules in other jurisdictions, including India. You cannot opt out of these cookies while using the dashboard, but you can delete them at any time by signing out or clearing your browser cookies.

2.4We do not use these cookies to track you across other websites or for advertising purposes.

2.5The dashboard also stores interface preferences in your browser's localStorage: your theme choice, your last-viewed project, and when you last opened the notification bell. These values stay in your browser and are not used for tracking.

3.1The Reqio widget, embedded on third-party websites, does not set any cookies on the host site.

3.2Instead, the widget uses the browser's localStorage and sessionStorage on the site where it is embedded, under Reqio-prefixed keys. This storage holds a randomly generated anonymous identifier (used to associate submissions and notifications from the same browser), a record of which notifications have already been shown, the identifiers of requests submitted from that browser, and, where the site uses the identity feature, a marker of the last signed-in account so the widget can detect an account change. No personal data is stored in this way unless the end user chooses to provide it.

3.3Because these values live in browser storage and not in cookies, they are not transmitted with HTTP requests and cannot be read by any other website. They are not shared with any advertising network, and Reqio does not use them to track end users across sites.

4.1Reqio uses one product-analytics service, PostHog, to understand how the marketing site and the dashboard are used. It is off by default. Until you choose Accept in the analytics banner shown on your first visit, the analytics service is not loaded at all: no page views, no events, no request of any kind, and no analytics identifier written to your device. If you decline, or simply never answer, that stays true. The only thing kept in your browser either way is the record of your choice, so that we do not ask again.

4.2PostHog data is processed in the European Union. Its requests are routed through reqio.app rather than to PostHog's own domain, so the identifier it stores is a first-party one. We still treat it as requiring your consent, because it is an analytics identifier rather than a strictly necessary one. If you accept, PostHog also records how pages are navigated on the public site, so that we can see where a page confuses people. Three limits apply, enforced in code rather than by policy: every value typed into any field is masked before it leaves your browser, so an email address or a sign-in code is recorded as asterisks and never reaches us as characters; recording is switched off the moment you enter the dashboard, a public board, or a claim link, so pages carrying other people's data are never captured; and recording never starts at all unless you accepted, because the analytics service is not loaded until then.

4.3The Reqio widget is not instrumented. No analytics service of ours runs inside the widget on a customer's website, and PostHog receives nothing about the people who submit feedback through it. Analytics covers our own site and dashboard only.

4.4We use no advertising cookies and no ad networks, and we do not track anyone across other websites. We do not embed Google Analytics, Facebook Pixel, or any advertising or profiling service anywhere in the product.

4.5The dashboard and marketing site also use Vercel Web Analytics, a cookieless, aggregate measurement service. It sets no cookies, stores no identifier on your device, and does not track visitors across sites, so it needs no consent and runs whichever choice you make above.

4.6Our infrastructure sub-processors (Vercel, Neon, Resend) operate internal technical cookies or headers as part of their service delivery, but these are not used for advertising or profiling end users.

5.1You can change your analytics choice at any time using the link in the site footer. Withdrawing is as easy as giving: choosing Decline stops analytics collection immediately, in the session you are already in, without waiting for a page reload, and erases the analytics identifier that accepting had stored in your browser.

5.2You can view, delete, and block cookies through your browser's settings. All major browsers provide instructions in their help documentation.

5.3Blocking the Reqio session cookie will prevent you from signing in to the dashboard. Clearing a site's localStorage resets the widget's anonymous identifier in that browser, but previously submitted requests remain intact on our servers.

5.4For questions about how we use personal data more broadly, see our Privacy Policy at reqio.app/privacy.

6.1We reserve the right to update this Cookie Policy from time to time. Changes will be posted on this page with an updated date at the top.

6.2Continued use of the Reqio service after changes take effect constitutes acceptance of the revised policy.