# Privacy and data > What Revfaro collects about your visitors, which cookies it sets, how cookieless mode works, how long data is kept, and how to delete it. **In short:** Revfaro records pages, sources, campaigns, goals, approximate location and device type for each visit. It never stores IP addresses or full user agents, and personal data in page addresses (such as `?email=`) is removed in the browser. The standard script sets two first-party cookies; the cookieless script stores nothing on the device. Data is kept for your plan's data history and then deleted. This page describes what the Revfaro script and integrations collect about **your website's visitors**. How Revfaro handles data about **you as a customer** is described in the [Privacy Policy](https://revfaro.com/privacy). ## What is recorded for each visit | Recorded | Details | | -------- | ---------------------------------------------------------------------------------------------- | | Pages | The path of each page viewed (without the query string), entry and exit page, and the hostname | | Source | The referring site (host and path), and `utm_*` and `ref` tags on the link | | Location | Country, region and city, and a point rounded to about 1 km for the live map | | Device | Browser, operating system and device type (desktop, mobile, tablet) | | Activity | Goals and their properties, outbound link clicks, and engaged time | | Identity | Only what you send with [identify](https://revfaro.com/docs/identify-users/): user ID, email and name | | Payments | Amount, currency and customer email and name, as your payment provider sends them | ## What is never stored - **IP addresses.** They are used for a moment when an event arrives (Cloudflare location validation, [exclusions](https://revfaro.com/docs/exclude-traffic/), flood limits and cookieless visitor recognition) and then discarded. - **Full user agents.** The browser string is reduced to browser, operating system and device type. - **Personal data in page addresses.** Query parameters such as `email`, `name`, `phone`, `password`, `token`, `code`, `secret` and `key` are removed by the script in the browser, before anything is sent. Location information comes only from verified Cloudflare request headers; Revfaro makes no separate location lookup. Missing data stays unknown. A [first-party proxy](https://revfaro.com/docs/proxy/) forwarding a visitor's address does not provide a location, because Cloudflare sees the proxy's connection. ## Cookies and storage | Script | Stores on the visitor's device | | ---------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `script.js` | `rf_vid`: a random visitor ID, 1 year. `rf_sid`: a random visit ID, renewed while the visitor is active and expiring after 30 minutes without activity. Both are first-party, on your root domain, `SameSite=Lax`, and `Secure` on HTTPS. | | `script.cookieless.js` | Nothing. A visitor is recognized for one day from a hash of IP address, browser and your website ID, made with a daily key that is then deleted. See [Cookieless mode](https://revfaro.com/docs/cookieless/). | Both scripts write one item to local storage only when you opt yourself out with `?rf_ignore=true`. Bots and automated browsers are not tracked as visitors. If you set up [bot tracking](https://revfaro.com/docs/bot-traffic/), Revfaro keeps the bot's name, owner and category, the path and the status code, never its user agent or IP address. ## Do you need a cookie banner? That depends on where you and your visitors are, and on your other tools. Revfaro can't give legal advice. What helps: - The [cookieless script](https://revfaro.com/docs/cookieless/) stores nothing on the device and sends no visitor ID. - Mention your analytics in your privacy policy either way. - Respect opt-outs: anyone can stop being tracked in their browser with `?rf_ignore=true`. ## How long is data kept? Data is kept for your plan's **data history** (see [Plans, billing and usage limits](https://revfaro.com/docs/billing/)). Visits, events, payments and bot hits older than that are deleted permanently, and so are visitors with no visits or payments left. ## Delete data - **A website**: **Website settings › General › Delete site and all data** deletes its visits, events, payments and funnels permanently. - **A workspace**: the owner can delete it under **Workspace settings › General › Delete workspace**, with all of its websites, data, members and settings. - **Your account**: **Account settings › Delete account** deletes your account and personal data; workspaces you own alone are deleted with it. Deleting can't be undone. ## Frequently asked questions ### Does Revfaro store IP addresses? No. The IP address is used when an event arrives to validate Cloudflare location information, apply your exclusions, limit floods and (in cookieless mode) recognize a visitor for one day, and is then discarded. ### Which cookies does Revfaro set? The standard script sets `rf_vid` (a random visitor ID, kept for one year) and `rf_sid` (a random visit ID that expires after 30 minutes without activity), both first-party on your own domain. The cookieless script sets none. ### Is Revfaro GDPR compliant? Revfaro is built to collect little: no IP addresses or user agents are stored, locations are approximate and personal data in page addresses is removed. Whether you need consent depends on your country and your setup, so mention your analytics in your privacy policy and consider the cookieless script. --- Source: https://revfaro.com/docs/privacy/ · Last updated 2026-11-02