Cookie Policy
Every cookie and browser storage item builderify.com uses: who sets it, what it is for, and how long it stays. Our own servers set no cookies at all.
01 What this policy covers
This policy covers the public website at builderify.com, run by Builderify ("we", "us"). It explains the cookies and similar technologies used when you browse it, and sits alongside our Privacy Policy, which explains how we handle personal data in general.
The Builderify dashboard at app.builderify.com uses the cookies it needs to keep you signed in. Websites that install Builderify are run by their own owners, who are responsible for telling their visitors what the Builderify script stores there.
02 Cookies and browser storage
A cookie is a small text file a website stores in your browser and reads back on later visits. localStorage and sessionStorage do a similar job without being sent to a server with every request: localStorage stays until it is cleared, sessionStorage until you close the tab.
The law treats them the same way, so this policy lists both. First-party items belong to builderify.com; third-party items belong to another company whose script runs on the page.
03 What we use, and why
Our pages are served without any cookies from our own servers. Everything below is set in your browser by a script on the page.
Strictly necessary
These keep the site reachable and protect it from abuse. They are set only when needed and cannot be switched off without blocking the site.
| Name | Type | Set by | Purpose | Lasts |
|---|---|---|---|---|
| __cf_bm | Cookie | Cloudflare | Set only when Cloudflare needs to tell people from automated traffic. | 30 minutes |
| cf_clearance | Cookie | Cloudflare | Set only after you pass a Cloudflare security check, so you are not asked again. | Up to 30 minutes |
Analytics and site features
Our own Builderify script runs on this site the way it runs on our customers' sites. It keeps its data in your browser's storage rather than in cookies, and it is not shared with advertisers.
| Name | Type | Set by | Purpose | Lasts |
|---|---|---|---|---|
| builderify_d3394025-91e1-4fde-97cf-3c90d7d7c524_storage | localStorage | Builderify | When you first visited, an anonymous identifier that links your page views into one journey, and whether you have already seen the language switcher. | Until you clear it |
| builderify_d3394025-91e1-4fde-97cf-3c90d7d7c524_storage | sessionStorage | Builderify | An identifier for the current visit, so pages viewed together count as one visit. | Until you close the tab |
| lastExternalReferrer | localStorage | Builderify | The website that sent you here, and when, so we know which links bring visitors. | Until you clear it |
| bdf_ab_id | localStorage | Builderify | When we test two versions of a page, keeps you on the same version every visit. | Until you clear it |
Advertising
We use the Meta Pixel to measure whether our ads on Facebook and Instagram lead to visits, signups and purchases, and to show our ads to people likely to find them useful.
| Name | Type | Set by | Purpose | Lasts |
|---|---|---|---|---|
| _fbp | Cookie | Meta | Recognises your browser across visits so Meta can connect ad views to actions on this site. | 90 days |
| _fbc | Cookie | Meta | Set only when you arrive from a Meta ad. Holds the ad click identifier. | 90 days |
| multiFbc | localStorage | Meta | A copy of the ad click identifiers, kept by the Meta Pixel. | Until you clear it |
04 What we share with Meta
Through the Meta Pixel, Meta receives the pages you view and these actions on our site: clicking to sign up, starting a credit pack checkout, opening an email link to contact us, and searching the site.
When you buy a credit pack and return to our confirmation page, we also tell Meta about the purchase: the pack, its price, and your email address in hashed form (scrambled one way before it leaves your browser or our server), so Meta can match the sale to an ad you saw. We send that confirmation from our server as well, so it still arrives if your browser blocks the pixel.
Search engine crawlers and other automated visitors are kept out of the pixel. Meta handles what it receives under its own Privacy Policy.
05 Your choices
The site works without any of these items, so blocking or clearing them never locks you out.
- Clear or block them in your browser. Chrome, Safari, Firefox and Edge all let you clear cookies and site data for one site, or block third-party cookies everywhere, from their privacy settings.
- Control Meta's ads. Your Facebook ad preferences let you limit how activity from other websites is used to show you ads.
- Opt out of interest-based ads. Your Online Choices in Europe and the Digital Advertising Alliance in the US let you opt out across many advertisers at once.
If our site shows you a cookie notice, you can answer it there as well.
06 Other companies' cookies
Some links take you to services run by other companies, which set their own cookies under their own policies:
- Meta may also set cookies on its own facebook.com domains, as described in its Cookies Policy.
- JVZoo runs the checkout when you buy a credit pack through it, and sets its own cookies on jvzoo.com.
- Cloudflare delivers and protects this site; its Cookie Policy covers the security cookies listed above.
07 Changes and contact
When we add or remove a cookie or storage item, we update this page and its effective date at the top.
Questions about this policy, or a request about your data: support@builderify.com.
Stop losing the visitors
you already paid for.
More leads from the traffic you already have, and follow-up that sends itself. Free to start. No card, no monthly fee.