If you install a REVU SDK on your site, we receive information about how people use it. You decide whether to install it, where, and what it sends. We use this information to give you REVU Behavior.
-
What the Web SDK sends
Pages viewed (address, title and description, the page that linked to it, campaign tags in the address), time on page, how far a page is scrolled, clicks with the visible text, label and title of the clicked element (each up to 120 characters) and the link address, file downloads and links to other sites, form submissions with field names and types only, changes to form fields (which field, and whether a checkbox or option is selected, never typed text), right clicks, when the visitor switches tabs or goes idle, repeated clicks, window size changes and page speed measures. With each event: the browser's user agent, languages, time zone, screen and window size, connection type and type of device, and random identifiers for the visitor and the visit. The SDK never reads what visitors type in a form field, and removes passwords, tokens, email addresses and similar values from addresses before sending them.
-
What you choose to send
A user id, if you call identify when someone signs in, and any custom events and properties you add. Do not send passwords, payment details or other sensitive information this way.
-
What the Server SDK sends
For requests to your server made by crawlers and AI agents: the host, the path without its query string, the method, the response status, the user agent, the IP address and the name of the referring site. It never sends request or response bodies, cookies or credentials. Requests from ordinary browsers are filtered out on your server and not sent.
-
Identifiers on your site
The Web SDK keeps its visitor and visit identifiers, the user id you set with identify, the campaign tags of the visitor's first and latest visit, and the visitor's consent choice on your site: in a first-party cookie that expires 2 years after it was last updated, and in the browser's local storage, which keeps them until the visitor clears it.
-
IP addresses and location
We use the IP address of each request to work out an approximate location (country, region and city) and network, on our own servers, and to check whether a crawler is genuine. The approximate location stays with the events.
-
Why we use it
To show you and your team how your site is used, which crawlers and AI agents read it, and to answer your questions about it. When your team asks REVU a question about Behavior data, the question and the data needed to answer it are sent to AI service providers to produce the answer. We do not use your visitors' data to contact them, and we do not sell it.
-
Where it is processed
On servers run for REVU by our hosting provider in Germany. Requests to REVU first pass through a network provider that protects and speeds up traffic, which may handle them in other countries.
-
How long we keep it
Your plan sets how far back your dashboard shows Behavior data: 90 days on Starter, 1 year on Growth, 2 years on Professional, with no limit on Enterprise. Today, data older than that is hidden from your dashboard but stays stored. We are building automatic deletion of data older than your plan's window plus 30 days, and will update this section when it is live. When you delete your organization, its Behavior data is deleted with it, 30 days after your request.
-
Your role toward your visitors
You decide whether to use REVU on your site, on which pages and what it sends. Tell your visitors that you use REVU to understand how your site is used, ask for any consent the law where you and they are requires, and use the SDK's consent controls to stop collection when a visitor declines. When you opt a visitor out, the SDK stops collecting new events from them.
-
When a visitor asks for their data to be deleted
Email [email protected] with the person's user id, or the visitor identifier from your site, and we delete that person's events, visits and profile from your organization within 30 days and confirm by email. Copies in our backups are removed when those backups expire. If a visitor writes to us directly, we ask which site they used and handle the request with that site's owner.