LEGAL / CLEAR OPERATING TERMS

Privacy, explained in operating terms.

This notice explains what personal data RECAST receives through the website and call-booking journey, why it is used, which service providers may process it and what choices are available.

Who is responsible

The final notice will identify RECAST’s contracting entity, registered contact details and the appropriate privacy contact before production launch.

Data we receive

Depending on your use, this may include contact and company details submitted through Calendly, appointment status and referral details, correspondence with RECAST, and technical request data used to deliver and protect the website. If you allow marketing, Whop also receives browsing, attribution and identification data described below. We store your marketing choice in your browser. The private partner area separately stores access and consent choices. Do not send system credentials or sensitive operational data through the booking service.

Why we use it

Data is used to provide and protect the website, respond to requests, schedule and prepare calls, manage appointment updates and operate requested private partner features. With marketing consent, Whop is used to measure visits and understand which campaigns and referrals bring people to the website.

Service providers and transfers

The website is hosted on Netlify, and public booking links open Calendly. Netlify also supports the configured server-side booking-status records. With your marketing consent, Whop, Inc. receives tracking data through its pixel on public production pages; that pixel is not loaded in the private partner area. Media files are served through the website rather than third-party video-player embeds. These providers process data through their own infrastructure and policies. The final policy will identify the complete production vendor list and applicable international-transfer safeguards.

Retention

Retention depends on the purpose and system involved. We remember your public marketing choice for 180 days. Whop’s _wuid browser cookie lasts approximately 730 days and may be renewed when written. Related local-storage identifiers have no automatic expiry and can remain until removed; session markers use session storage. These browser periods do not define how long data already received by Whop is retained. Hosting records, correspondence and booking data have separate retention requirements; final server-side periods will be documented against the production systems.

Your choices and rights

Depending on location and applicable law, you may have rights to access, correct, delete, restrict or object to processing, receive portable data, withdraw consent and complain to a supervisory authority. You can change marketing consent through “Cookie preferences” in the footer. Withdrawing permission reloads the page to stop the loaded Whop script. It does not erase data already sent or affect prior lawful processing. You can also remove cookies and site data in your browser.

Calendly and booking data

Public booking buttons open Calendly on its own website; they do not load a calendar widget on public RECAST pages. In the private partner area, the embedded calendar loads only after it is requested and functional services are allowed. An external booking link is also provided there. Information submitted to Calendly is also governed by Calendly’s own privacy information.

Optional Whop marketing measurement

Whop loads only after you accept marketing on the public production website. Its SDK measures page views and can collect the page URL, referrer, campaign and click identifiers, browser and device information, and device-fingerprinting signals. It can read names, email addresses and phone numbers from recognized URL parameters and form-field changes, including before a form is submitted. Browser identifiers and accessible cookies from other vendors may be associated with this activity. These are not necessarily anonymous records. Declining marketing prevents this Whop integration from loading; essential hosting and requested booking services still operate. This integration does not report a completed Calendly booking as a verified conversion.

Questions

The approved privacy, legal and accessibility contact details will be published here before production launch.

Start a conversation