Privacy Policy

When you create an account we receive your name and email address. If you sign in with Google, Google shares your name, email address and profile picture with us. We store a salted Argon2id hash of your password, never the password itself.

We use this information to run your account and to email you about it: address confirmation, password resets, invitations, and usage and billing notices. Goal alerts and weekly reports go to the members chosen for them, and every one of those emails has an unsubscribe link. Members of a workspace see each other's names and email addresses. Messages you send through the contact form are emailed to our support team.

Our servers keep request logs, including IP addresses, for a limited time to protect the service and fix problems. Requests from the tracking script are not written to these logs.

Visitor locations are approximate. Revfaro reads location information supplied by Cloudflare when a visit reaches us through a verified Cloudflare connection. Revfaro does not request the visitor's device location or run a separate location lookup service.

When trusted location information is unavailable, the location stays unknown. This also applies when a customer's proxy forwards a visitor's address, because Cloudflare sees the proxy's location. Revfaro rounds location coordinates before storing them.

See the third-party notices for additional data and software acknowledgments.

Revfaro plans are sold through Dodo Payments, our merchant of record. Dodo Payments collects your payment details, billing address and tax information and tells us the state of your subscription; we never see your full card details. We keep the billing events we receive, such as a payment or a cancellation, for one year.

For each visit, the script records the pages viewed (without query strings), the referring site, campaign tags (utm_* and ref), goals and their properties, outbound link clicks, engaged time, approximate location (country, region, city, and a point rounded to about 1 km), and browser, operating system and device type. Parameters such as email, token or password are removed from page addresses in the browser, before anything is sent.

• Standard script. Sets two first-party cookies on your domain: rf_vid, a random visitor ID kept for one year, and rf_sid, a random visit ID that expires after 30 minutes without activity.
• Cookieless script. Stores nothing on the visitor's device. A visitor is recognized for one day from a hash of their IP address, user agent and your website ID, made with a random key that is replaced every day and then deleted.
• IP addresses. Used only while an event arrives: to validate trusted Cloudflare location information, to apply your exclusions, to stop floods (a keyed hash of the address is kept for ten minutes) and, with the cookieless script, to recognize the visitor for the day. Raw IP addresses and full user agents are never stored.
• People you identify. If you call identify(), we store the user ID, email address and name you send.
• Payments. When you connect Stripe, Lemon Squeezy, Polar or Dodo Payments, or send payments through the API, we store each payment's amount, currency and time, the provider's payment, customer, product and subscription IDs, and the customer's email address and name as the provider sends them. Card details are never stored.
• Telegram sales. If your bot server forwards payment updates, we store the amount, currency, time, a derived charge identifier, renewal status and the Telegram buyer ID when supplied. Visitor and session IDs may link the purchase to a website visit. Telegram bot tokens, message text, invoice payloads, buyer names, phone numbers, addresses and email addresses are not stored from these updates.
• Bot traffic. If you forward bot requests, we keep the bot's name, owner and category, the page path, the status code and the referring domain. The bot's IP address is used only to verify it against published address ranges and reverse DNS; neither it nor the user agent is stored.
• Exclusions. The IP addresses, countries, hostnames and pages you exclude are saved with your website's settings. Events they match are dropped without being stored; only their number is counted.

For this data, you are the controller and we process it on your behalf to provide your analytics. We don't sell it or use it for advertising.

Visits, events, payments and bot traffic are kept for your plan's data history and then deleted automatically. You can delete a website and all its data at any time, workspace owners can delete a whole workspace, and you can delete your account in your account settings. Records of sent goal alerts are kept for 90 days and of weekly reports for about a year. Email delivery records, including recipient addresses, subjects, template versions and attempt results, are kept for 90 days. Subscription webhook records are kept for a year. These operational records may remain until their retention period ends after an account is deleted.

We share data only with the providers we need to run the service:

• our hosting provider, which runs the servers and stores the data;
• Microsoft 365, which delivers our emails;
• Dodo Payments, which sells and bills Revfaro plans;
• Google, when you choose to sign in with Google.

This website and the dashboard load their font from Google Fonts. In the dashboard, website icons come from Google's favicon service and the live map's tiles from OpenFreeMap, and the API reference loads its viewer from jsDelivr.

Privacy questions, data requests or deletion requests: the support email on our website.