What Rensa does.

What it does to the sites

• Inside the sitesNothing
• ReadsThe screen, not the site
• InstallsNo extension and no injected code
• UsesNo cookies or passwords, and no requests to any site
• The site seesYour rep, a person browsing

What it keeps, and where

• WhatThe leads your team captured and reviewedKept so they can be downloaded for your CRM.
• The pagesNot keptA captured image is read and discarded; only a one-line description of each page that gave leads is kept with them.
• WhereStored by DD Labs Limited on a server in Nuremberg, GermanyUnder a data processing agreement that is part of the terms.
• How longUntil you delete them, or for ninety days after a seat endsClosing the account deletes them within thirty days.
• Who reads itThe page image is read by model providers, mostly in the USWe never store it; the data processing agreement names each provider.

The DPA names every sub-processor: Google, which reads the image, Stripe for payments, Resend for email, Cloudflare in front of the service, Hetzner, which hosts the server, and Sentry, which receives error reports.

The account

• Where it is decidedA site restricts on page views alone, which is a person's browsingNothing of ours runs where a site decides that.
• Our promiseWe can't guarantee any account, and no tool honestly can
• If Rensa caused itReply to any email from us and we'll help you rebuild this week's listWe don't expect it.

What IT can check

1. The browser's extensions list: nothing of Rensa's is in it.
2. The app's network activity: it talks to Rensa's own service to read images and store leads, to Rensa's update server for new versions and, if turned on, to a crash reporter; to no other site.
3. Every page links the terms, the DPA and the privacy notice.
4. A question we haven't answered here: write to [email protected].