Facebook growth, simplified Explore all six services
BROWSER CONTROLS

Cookies currently used by HitsBoost.

This page lists the cookies the current HitsBoost site sets and separates them from cookies a future payment provider or another website may use. A cookie is a small value a website asks a browser to retain and send back on later requests.

Last updated:
Browser session cookie protected within a privacy ring

See which HitsBoost cookies protect free sample and contact forms, how long they last, and how third-party checkout may use separate cookies.

01 / 07

The cookies on this site today

The local site sets two form security cookies. ‘free_sample_csrf’ is created when you open a free sample page; ‘contact_csrf’ is created when you open the contact page. Each helps the server compare a form's submitted token with a value held by the same browser. They are essential to those forms, and each is set with a maximum age of 24 hours.

These cookies are marked HttpOnly and SameSite=Lax. They are marked Secure when the page is served over HTTPS. They do not contain your Facebook password, payment card number, or the message you type into a form. Browsing ordinary informational pages does not require you to submit either form.

02 / 07

What happens when you block them

If your browser blocks or deletes a form security cookie before you submit the form, the server cannot verify the token and will reject that submission. Reloading the page can create a fresh token. Other pages and browser tools may still be usable without submitting the form.

You can inspect or remove site cookies in your browser's privacy settings. The exact steps differ by browser and device. Removing a cookie may also remove the form state tied to it; it does not by itself delete a contact message or sample request already saved in our database.

03 / 07

Browser tools and local data

The engagement and watch time calculators, caption generator, image resizer, and Facebook link checker run in your browser. They do not need HitsBoost analytics cookies to perform their calculations. The image resizer reads the file you choose locally and creates a download; it does not need a cookie to upload an image.

The site may use normal browser caching to load CSS, JavaScript, images, and fonts efficiently. Caching is different from the two application cookies listed above. Your browser may also retain its own history or downloads according to your settings.

Visitor adjusting cookie and privacy settings in a browser
04 / 07

External resources and checkout

HitsBoost currently requests font styles and files from Google Fonts. Those requests reach Google-controlled domains, which may process request data under their own policies. The page can still be understood if the font fails to load because it has fallback fonts.

When live paid checkout is connected, clicking a package may take you to a third-party checkout site. That provider may set its own payment, security, or fraud-prevention cookies. Review the provider's cookie and privacy notices on its domain before completing a transaction. HitsBoost does not control cookies set only by another site.

05 / 07

Analytics and advertising

No HitsBoost analytics or advertising cookie is configured in the current local application. We do not present a marketing-cookie toggle that implies an active tracking system where none exists. If we add optional analytics, advertising tags, or account preferences later, we will update this inventory and provide controls when required.

Public review and order-activity snippets do not need a visitor-specific advertising cookie. The order feed is requested by the server and displayed as public-safe activity. The review cards shown on service pages come from the HitsBoost review collection, not from a browser tracking profile.

Separate HitsBoost and checkout browser windows with their own data boundaries
06 / 07

Checking a cookie yourself

Most browsers show stored cookies in a privacy or developer-tools panel for the current site. Look for the domain, cookie name, expiry, and security attributes to identify whether a value came from hitsboost.com. A cookie associated with a payment provider or font host belongs to that separate domain rather than to this application.

If you compare the inventory with your browser, remember that a cookie appears only after the page or form that sets it has been opened. The contact cookie is created on the contact page; the free sample cookie is created on a free sample page. A visitor who reads only a guide may not see either one.

07 / 07

Questions and policy changes

For more detail about submitted URLs, contact messages, request records, and service providers, read the Privacy Policy. If a cookie appears in your browser that is not named here, note the exact cookie name and page where you saw it so we can check whether it came from HitsBoost, a hosting layer, or another domain.

Email [email protected] or use the contact form for a cookie question. We will revise this page when live checkout or other integrations change the browser's behavior. The updated date at the top of the page shows when the published description was last revised.