US Cookie Policy

US privacy and tracking requirements vary by jurisdiction and context. This page does not claim that a single federal opt-in rule applies to every visitor or that the current control alone satisfies every state requirement.

Google Analytics loads automatically after a public page becomes interactive. There is no TokBlaze analytics-consent control in the current interface. Browser privacy settings, network filtering and content blockers may prevent or limit the tag, cookies and measurement requests.

This working policy explains cookies and similar browser technologies associated with tokblaze.com. It covers the static public pages, free tools, analytics tag, order tracker, support chat and links that hand a selected package to an external checkout page.

A third-party checkout or social platform can use its own cookies under its own policy. This page does not claim to list an external provider's cookie names, purposes or retention periods without verified evidence. The owner must review the deployed site and provider configuration before relying on this disclosure.

A cookie is a small value a website asks a browser to store and send with later requests. Similar technologies include local storage, session storage, pixels, tags and identifiers held in memory. They can support essential functions, remember choices, measure usage or connect activity across pages.

Not every browser request creates a cookie. Servers can still receive technical data such as IP address, user agent, requested URL and timestamp without placing anything in browser storage. The Privacy Policy explains those broader data flows.

TokBlaze is exported as static HTML, CSS and JavaScript. Its core public pages do not require a TokBlaze login or customer session cookie to display content. The site can therefore present service information without creating an account-based profile on the apex domain.

Static hosting does not mean that every request is anonymous or that third-party scripts cannot use storage. Analytics, the hosting layer and external checkout may still process technical information, so their real behaviour must be considered separately.

A first-party cookie is associated with tokblaze.com; a third-party technology is supplied by another service loaded from or visited through the site. The practical distinction matters because TokBlaze directly controls its own code but may have more limited control over an external provider's implementation.

The site should not describe a third-party tool as strictly necessary merely because it is commercially useful. Each technology needs an accurate purpose and, where applicable, an appropriate user choice based on the markets served.

The current site includes a Google Analytics tag. Analytics can use cookies or related identifiers to distinguish visits and report information such as pages viewed, referring source, device or browser characteristics, approximate geography and interaction events.

The intended purpose is aggregate measurement and site improvement, not collecting a TikTok password or the private contents of a social-media account. The tag loads automatically on public pages and may set or read analytics identifiers. The owner must review that configuration against actual deployment and applicable requirements rather than assume this paragraph makes it compliant.

Selecting a package on a money page sends a numeric package identifier to an external checkout page. That provider may use cookies or similar technologies for payment security, transaction continuity, fraud prevention, preferences or measurement. Its own notice should explain what it does on its domain.

This applies whether the visitor chooses TikTok followers, likes, views, comments or shares. TokBlaze does not need a social-media login cookie to identify the public target, and the checkout hand-off should not be described as permission to access the customer's platform account.

Entering an order ID on the tracking page sends a request to pay.promotid.com. A request can create ordinary technical logs even when it does not place a browser cookie. The tracking result is shown on the page and no TokBlaze account session is created for that lookup.

The chat interface from panel.brecktic.uk is loaded when the visitor opens the launcher. Because it runs from that provider's origin, it may use its own cookies or browser storage for conversation continuity, security or interface state. TokBlaze does not claim an exact cookie list or retention period that the provider has not supplied and verified.

A future feature may need short-lived storage for security, load balancing or a form step. Any such technology should be limited to what the function genuinely needs and added to this policy when implemented.

The current public site does not claim that analytics is essential to displaying a page. Security controls at the hosting or network layer may operate without a browser cookie, and those technical logs are addressed in the Privacy Policy.

The hashtag, caption, bio and engagement-analysis widgets are designed to generate or calculate results in the browser. They do not require a TokBlaze user account. Some browser state may exist temporarily while the page is open because JavaScript components hold the current input and output in memory.

Page analytics loads on free-tool pages as it does elsewhere on the public site, while the tool inputs are intended to remain in the browser. A free trial request that proceeds to an order enquiry is not the same as a local generator and may carry the public target in the page URL or prepared email; review the target before sending it.

TokBlaze service pages do not ask you to sign in to TikTok or Instagram, and do not need a platform session cookie, password or login code to deliver to a public target. Do not paste credentials into a free tool, order-support message or checkout note.

If a page using the TokBlaze name unexpectedly asks for platform credentials, leave it and contact support@tokblaze.com from a new message. A legitimate cookie notice should explain browser storage; it should never be used as a reason to request account access.

Browser technologies should have a defined purpose: serving and protecting a page, maintaining a necessary step, remembering a user choice or measuring aggregate use. Data collected for basic measurement should not silently become a list of social-media targets for unrelated marketing.

TokBlaze does not claim to use cookies to sell personal information or build third-party advertising profiles. The owner must verify that statement whenever analytics, advertising or checkout configuration changes.

The current public site loads the Google Analytics script automatically after the page becomes interactive. There is no TokBlaze analytics-consent control in the current interface. Browser privacy features, network filtering and content blockers may still prevent the script, cookies or measurement requests from operating.

Automatic loading is a deployment choice, not a blanket claim of legal compliance in every location. The owner must keep the deployed behavior, analytics configuration and this notice aligned, and should obtain qualified advice for markets that require consent before non-essential analytics.

Most browsers let you inspect, block or delete cookies and site storage. Blocking third-party cookies or analytics should not prevent static service information from loading, although blocking storage that an external checkout genuinely needs could interrupt payment or security checks on that provider's page.

Deleting browser storage may remove saved preferences used by this site or an external provider. Instructions differ by browser and device, so use the help documentation for the software you actually use rather than relying on a generic sequence here.

Browsers may send signals such as Do Not Track or Global Privacy Control. This policy does not claim a specific automated response that has not been tested in the deployed analytics and checkout configuration.

The owner should assess which signals require action in the markets served and configure the site accordingly. A visitor can also use browser blocking controls and contact support with a privacy question as described in the Privacy Policy.

Retention can vary by cookie, analytics setting, provider and browser action. No fixed period is stated here because a verified inventory and configuration-specific durations have not been supplied. Inventing one would create false precision.

The owner must inspect the deployed cookies and storage, document their real lifetimes and reduce them where longer retention is not needed. Third-party provider notices may describe additional retention on their domains.

Cookies and storage should not contain a TikTok or Instagram password. Sensitive authentication values should use protective settings appropriate to their function if the site ever introduces them. The current public site does not operate a TokBlaze customer-login session.

No browser technology is risk-free. Keep the browser updated, be cautious with extensions and verify the domain before entering payment information on an external checkout page. Report a suspicious TokBlaze-branded page or request to support.

This policy should be updated after a real change to analytics, storage or checkout behaviour. The Last updated date should not move merely because the static site was rebuilt.

This remains an honest working disclosure, not a claim of lawyer review or universal regulatory compliance. The owner must verify it against a live cookie scan, provider settings and the markets served, then obtain qualified legal advice before relying on it for production sales.