Canada Privacy Policy

This Canada page supplements the global policy. The Office of the Privacy Commissioner of Canada explains that PIPEDA sets rules for many private-sector commercial activities and that substantially similar provincial laws may apply in Alberta, British Columbia and Quebec. Which rule applies depends on the real organization, transaction and information flow.

The verified public contact currently published by TokBlaze is support@tokblaze.com. This page does not invent a Canadian company, office, privacy officer or controller identity. Use the Canada Contact page for a request and never send a social-media password, login code or complete payment credential. See the OPC PIPEDA overview.

A Canada-facing page and CAD checkout do not mean every system or service provider is located in Canada. Order and support information may cross provincial or national borders through hosting, email, analytics or checkout providers. The global policy describes the known data categories without claiming an unverified storage location.

A privacy request should identify the relevant email or order reference and the right being requested. TokBlaze must assess the request against the law and actual records that apply, rather than promise a universal outcome from a regional URL.

This policy explains how TokBlaze handles information connected with the public website, support conversations and orders for social-media growth services. It covers visits to tokblaze.com, the free tools hosted here and the hand-off from a service page to an external checkout provider.

The services include TikTok follower packages, engagement for TikTok videos, views, comments and shares. The policy applies to information handled by TokBlaze; a third-party website you visit from this site may have its own policy and practices.

The information needed for an order depends on the service and current provider flow. Some post services begin with a public username and then present a post selector; others request a public-content link directly. If you contact support, you may also provide an email address, order reference, screenshots and the contents of your message.

Do not send a social-media password, login code, recovery code, identity document or unrelated sensitive information. None of those items is needed to deliver the services described on this site. If support needs to identify an order, an order reference and the public target are normally the useful details.

A username or post link submitted for fulfilment already points to material made public on the relevant platform. That does not make it unimportant: the target still becomes part of the order record and should be handled only for fulfilment, support, fraud prevention and resolving problems with that order.

Profile-level services such as buying TikTok followers use a public handle. Current post-level flows may start with that handle and then ask the buyer to select content, or may request the specific public URL directly. Follow the current checkout label, verify the intended post and keep it public while delivery is in progress.

When you email support@tokblaze.com or use the site chat, the message and its routing information are handled by the systems used to send and receive it. The message may be retained with the related order while it remains useful for answering the request, documenting a resolution, detecting repeated abuse or handling a later refill or refund question.

Email is not a suitable place for passwords or highly sensitive material. Before sending a screenshot, crop out unrelated notifications, private messages, payment details and account-recovery information. Support may ask for a clearer order reference, but should not ask for access to your TikTok or Instagram account.

The order-tracking page sends the order ID you enter to the tracking service at pay.promotid.com and displays the latest status data returned for that reference. Depending on the order record, the response can include package, public target, quantity, timing and status information. Tracking does not require a TokBlaze account or a social-media password. Treat the order ID as private order information and do not publish it.

The support-chat launcher loads a chat interface from panel.brecktic.uk when it is opened. That service can receive technical request information and the text or files you choose to send. Do not submit passwords, login codes, complete payment credentials or unrelated sensitive material through chat. Response time varies and the presence of the launcher is not a promise of immediate or continuous staffing.

The public TokBlaze site sends a selected package identifier to an external checkout page. Payment details entered there are handled on that provider's page rather than in a card form hosted on tokblaze.com. Review the information and policies shown at checkout before paying.

TokBlaze may receive information needed to associate a payment with an order, such as a transaction or order reference, payment status, selected package and the public delivery target. This policy does not claim that TokBlaze receives or stores complete card details. If the checkout experience changes, the owner must update this section to match the real data flow.

Like most hosted websites, the server and protective infrastructure may record technical request data. That can include an IP address, browser or device user agent, requested URL, referring page, timestamp and response status. These records help serve the site, investigate faults, limit abusive traffic and understand security events.

Technical logs are not a promise of precise identity. Shared networks, proxies and privacy tools can make them incomplete or misleading. They should be used only where relevant to operating and protecting the service, not presented as more conclusive than they are.

The site currently includes a Google Analytics tag to measure visits and page use. Analytics technology may receive information such as page URLs, approximate location derived from network data, browser characteristics, referring sources and interaction events. The purpose is to understand which pages are useful and where the site fails visitors.

Analytics should not be used to collect a social-media password or the text entered into a free tool. The analytics tag now loads automatically on public pages; browser privacy settings, network filters or content blockers may still prevent measurement. See the Cookie Policy for current disclosures and browser-control options.

The hashtag, caption, bio and profile-analysis interfaces are designed to perform their generation or calculation in the browser. Values entered into those widgets are not needed to create a user account. Ordinary page analytics and server requests can still occur when the page itself loads.

A free-service trial request is different from a local generator. It may place the public target into an order enquiry so the request can be handled manually. Before sending that enquiry, check that the username or link is correct and do not add private credentials in any message.

Information is used to present the site, route a selected package to checkout, fulfil an order against the correct public target, answer support questions, investigate delivery issues, assess refill or refund requests, maintain security and understand aggregate site performance.

An order target should not be repurposed as a marketing list. Support contact details should be used to communicate about the request or order for which they were provided unless the person has made a separate, informed choice to receive something else. The current site does not promise an account dashboard or marketing subscription.

Operating the service can require hosting, analytics, email, checkout, tracking, chat and fulfilment providers. Information should be shared with each provider only to the extent needed for its role—for example, passing a package identifier to checkout, an order ID to the tracking endpoint or a public target to the system that performs delivery.

This policy does not name processors that have not been confirmed by the owner, and it does not make a blanket certification about their contracts or locations. The owner must maintain an accurate provider inventory and revise this policy when a provider or data flow materially changes. ${SITE.name} does not claim to sell personal information.

TokBlaze is not TikTok, ByteDance, Instagram or Meta, and is not endorsed by them. When you open or use those platforms, their own privacy terms apply. A public username or post link remains hosted by the platform, even when it is referenced in an order record here.

Purchasing engagement may conflict with platform rules. That issue is described in the Terms of Service; it is not changed by the fact that the target is public or that no password is collected.

There is no fixed retention period stated here because the owner has not supplied and verified one. Information should be kept only while it has a real operational, security, accounting or dispute-resolution purpose, and then deleted or de-identified when it is no longer needed, subject to obligations that may apply to the operator.

Different records may have different useful lives. A short-lived technical log is not the same as an unresolved order conversation. The owner must define and follow a retention schedule before representing a specific duration to customers.

TokBlaze does not need your TikTok or Instagram password to provide the services described here. No legitimate order-support step should require a login code, recovery phrase or remote access to your device. If someone using the TokBlaze name asks for one, stop and contact support@tokblaze.com through a fresh email message.

Reasonable technical and organisational care reduces risk but cannot make internet transmission or storage risk-free. This policy therefore does not promise absolute security. Customers can materially reduce exposure by sending only the public target and order information actually needed.

The site serves visitors in more than one country, and hosting, email, analytics, checkout or fulfilment systems may make information accessible outside the visitor's location. The exact provider locations and legal transfer arrangements must be verified by the owner rather than guessed in this policy.

If location-specific disclosures or choices are required for a market, the owner must add and operationalise them before claiming that they are available. A global website address by itself does not establish compliance with every local privacy regime.

You can ask TokBlaze to explain, correct or delete information connected with you by emailing support@tokblaze.com. Include enough detail to locate the relevant conversation or order, but do not send a password or full payment credential. The response may need to distinguish data controlled by TokBlaze from data held independently by a platform or checkout provider.

Rights and exceptions can differ by location and context. This page does not invent a universal response period or claim a right that has not been assessed. The owner should verify the request, apply the rules that actually govern it and explain any limitation rather than silently ignoring the request.

This policy should change when the site's real collection, providers, checkout or support practices change—not merely to create a fresh date. Material changes should be reflected in the visible text and its Last updated date.

This remains a working policy requiring owner verification and qualified legal review. If the site behaves differently from this description, the operational mismatch must be corrected or disclosed; wording alone cannot fix an inaccurate data practice.