Read how HitsBoost handles public social-media links, free sample requests, contact messages, cookies, reviews, analytics, and third-party checkout information.
Who this policy covers
HitsBoost is the website at hitsboost.com. This policy covers visits to our pages, browser-based tools, free sample forms, contact messages, and the public review and activity snippets we display. You can ask questions about this policy at teams@hitsboost.com, through our contact page, or by writing to HitsBoost LLC, 155 Willowbrook Blvd, Ste 110 #8965, Wayne, NJ 07470.
HitsBoost is independent of Facebook and Instagram. When you use either social platform or leave HitsBoost for a separate checkout, that service controls its own collection and processing. We link to our Terms of Service and Cookie Policy below so you can read the related site rules together.
Information you choose to send
A free sample request asks for a public Facebook Page, profile, post, video, or Reel URL, depending on the offer. We save the selected service, normalized URL, fixed sample quantity, submission time, and a request reference. Our forms do not ask for a Facebook or Instagram password. The link identifies where a request should be reviewed; it may still reveal the public account or content you chose.
A contact message includes your name, email address, selected topic, optional order ID, message, and submission time. If you email us directly, we receive the details in that email. Share only what is needed to explain your question; payment card numbers and account passwords do not belong in a support message.
Information created during a visit
The free sample and contact forms use short-lived, security-related cookies to check that a submission came from the browser that opened the form. We also store a keyed hash of the submitting IP address with form records to limit repeated automated requests. The application may create routine server access or error logs through its hosting environment. If you allow optional analytics, Google Analytics measures visits and interactions and may use browser identifiers or analytics cookies; Ahrefs Web Analytics provides aggregated traffic measurements without persistent identifiers.
The browser tools for engagement rate, watch time, image resizing, caption drafts, and Facebook link format checks run in the browser. The image resizer reads a file you select locally and exports a new file to your device; it does not upload that image to HitsBoost. Language choices and dismissed regional suggestions can be remembered in session storage. Your optional analytics choice is remembered in local storage until you change it in the footer. A regional suggestion may use an approximate country code supplied by our hosting provider through this site; it does not request your device's precise location. A browser request for a page or image still reaches the site host in the ordinary way.
Why we use these details
We use submitted links and request references to record and review sample requests. We use contact details to answer the question you sent, connect a support question with a relevant order where possible, and prevent duplicate submissions. Security tokens and rate-limit hashes help keep forms usable for ordinary visitors.
We do not use a free tool calculation to build a personal profile. Public review cards come from customer feedback supplied to HitsBoost; the displayed name, service, comment, and rating appear only when that information is present in the approved source. Order activity displays fixed summaries supplied to HitsBoost, without customer contact or payment details. The activity snippets do not request updates from an external service.
Service providers and checkout
The current site may rely on a hosting provider, mail service, Google Analytics, and Ahrefs Web Analytics. Those providers may process data needed to run their part of the service. HitsBoost pages also load web fonts from Google and a support widget from help.hitsboost.com. Loading the widget connects your browser to that help service; a chat message you choose to send is handled there. Do not send account passwords or full payment details in chat.
Paid package buttons redirect to a third-party checkout provider. Available package prices are retrieved from the provider's live pricing feed for the page's currency; confirm the selected product, currency and final total on the checkout page before payment. The provider's terms and privacy notice govern the payment information it collects; HitsBoost may receive an order reference, public destination, and status details needed for fulfillment and support. HitsBoost does not collect full payment card numbers on its own pages.
Storage, protection, and retention
Sample and contact submissions are saved in the local application database. If outgoing team email is configured, the details needed to handle a request may also be sent to teams@hitsboost.com. Access should be limited to people who need the records for support, fulfillment, security, or legal administration. No website can promise that data transmission or storage is risk-free.
We keep records for as long as reasonably needed to process the request, handle related questions, maintain security, or meet applicable obligations. Retention depends on the type of record and the purpose for which it is held. If you want us to review an existing record, contact us with the request reference or the email you used so we can locate it.
Your choices and questions
You can use most pages and browser tools without submitting a form. You can decline to send a free sample or contact request. Browser settings let you manage cookies, though blocking the form security cookies can prevent those forms from working. You may ask us to access, correct, or delete information associated with you where applicable law provides that right.
Send a privacy request to teams@hitsboost.com with enough detail to locate the record. We may need to verify that the request is yours and may retain some information where required or permitted for security, disputes, or legal compliance. We will update this page when site integrations or data practices materially change.