Privacy
Effective [PLACEHOLDER: effective date]. Last updated [PLACEHOLDER: effective date].
This page explains what this site collects, why, and who else receives it. It covers this site only. [PLACEHOLDER: legal entity name and state of incorporation] ("Rendr") is a US company operated from Italy, and this policy describes the offer page and booking confirmation page you are reading, not any separate client engagement.
It describes what the site does today, including two things that are not live yet and are marked as such.
What we collect directly
Nothing is collected by us until you interact with the booking widget. Browsing this page sends us no form data, and there is no account, login or newsletter here.
Booking a call (iClosed)
The booking widget on this page is an embed operated by iClosed, a third party. When you use it, you provide your name, email address, phone number, your website, and answers to two qualifying questions about annual revenue and monthly ad spend. That information is submitted to iClosed and shared with us so we can hold the call.
iClosed is a separate processor with its own privacy policy and its own data handling. We also pass a booking event identifier and any campaign parameters described below into the widget so a booking can be matched to the visit it came from.
iClosed privacy policyAdvertising measurement (Meta)
This site uses the Meta pixel, a script from Meta Platforms that runs in your browser. Bookings are also reported to Meta from the booking provider's server through Meta's Conversions API, with a shared identifier so the same booking is not counted twice.
What is sent: page views, that the video was watched and how far, taps on the booking buttons, which question you opened in the FAQ, that a booking was made or that a visitor was not a fit, the booking event identifier, the headline variant you were shown, and the standard information a browser reveals to any site it requests: IP address and user agent. It is used to measure whether ads produce booked calls and to optimise ad delivery. Meta processes it under its own terms.
Meta privacy policyVideo (Wistia)
Not added yet; the video on this page is currently a placeholder. When the player is added, Wistia will receive viewing data: that the video loaded, how much of it was watched, and the technical information any embedded player receives. We use it to see whether the video is watched, not to identify you.
Wistia privacy policyThird parties loaded by the booking widget
The booking widget is a third-party embed: an iframe served by iClosed, which loads its own tools inside it. We do not choose them, configure them, or receive their data, and they set their own cookies inside their own frame. They are listed here because they run while you are on this page.
- Hotjar: session recording. It records interaction with the booking widget, such as pointer movement, clicks, scrolling and typed input events.
- Bugsnag: error reporting for the widget.
- ipify: an IP address lookup service.
- Google reCAPTCHA: bot detection on the booking form.
Cookies
The Meta pixel described above sets one advertising cookie on this domain: _fbp, an identifier Meta uses to link ad clicks to what happens on this page. It expires after three months. If you arrived from a Meta ad, the click identifier in the link is stored alongside it as _fbc. Apart from those, nothing in this site writes a cookie: there are no cookies of ours, and no other analytics cookies. Two operational cookies are set by the hosting and network layer that serves the page: __dpl, which identifies the deployed build and expires after a day, and __cf_bm, a Cloudflare bot-protection cookie that expires within the hour. Neither is used to profile you or to measure marketing.
That covers this site only. It does not cover the booking widget: iClosed and the tools it loads inside its own iframe, listed above, set their own cookies under their own policies. The video service described above will do the same once it is live.
Browser storage we do use
Instead of cookies, this site stores a few small values in your own browser. None of them contains your name, email or any other personal detail you typed.
- Booking event identifier: a random ID generated on your first visit, used to match one booking to one ad click and to stop a single booking being counted twice. Stored in sessionStorage: it is erased when you close the tab.
- Already-reported flag: records that a given booking has already been reported once, so reloading the confirmation page does not report it again. Stored in localStorage, keyed by that booking's identifier, and persists until you clear your browser storage.
- Campaign parameters: any utm_ values and a Meta click identifier (fbclid) present in the link you arrived on, captured once so a booking can be attributed to the campaign that produced it. Stored in sessionStorage: erased when you close the tab.
- Headline variant: which of the page's headline versions you were assigned, stored in localStorage so you see the same one on every visit.
Personal data in the address bar
After a booking, the confirmation page may be reached with parameters attached to its URL. We read only the ones we recognise and immediately rewrite the address to remove the rest, so anything the booking system forwards is not left sitting in your browser history or passed on to third-party requests.
Retention
Browser storage lifetimes are described above. For booking data held by us and by iClosed: [PLACEHOLDER: retention period].
Your rights and how to reach us
You can ask what we hold about you, ask for it to be corrected, or ask for it to be deleted. Depending on where you live you may have additional rights under local law.
Contact: [PLACEHOLDER: privacy contact email] ยท [PLACEHOLDER: postal address].