How we handle
your data.

Service and contact

Simple Fire is an independent project for scheduled TikTok messages. Contact the team through dashboard support or @simpleboostsupport about your data. A ticket number or profile ID is enough to locate your profile; passwords and sign-in codes are not needed.

Available payment methods and their transfer details are shown in the dashboard before you confirm a payment. Contact support about the service or data handling.

Information we process

Telegram sign-in stores your ID, first and last names, username and available profile photo. Email verification stores your address and verification status. The Mini App relies only on Telegram data verified by the server.

Connecting TikTok stores your profile ID and details, encrypted session, chat partners with available names and avatars, streak information, chosen messages, video links and schedules. The service may read relevant conversation data to execute and verify sends. This is not continuous collection of every message.

We also retain balances and balance changes, subscriptions, invitations, task results, notifications, support requests and replies. Sign-in security uses IP address, browser and device type, sign-in time and activity. Push subscription keys are stored only after you enable notifications.

Bot protection for sign-in

The sign-in form and code requests use Cloudflare Turnstile. Cloudflare receives the IP address and technical browser signals to verify the request. Passwords, email codes, TikTok conversations and payment details are not sent for this check.

The verification token is single-use and checked by the Simple Fire server. This protects registration and is separate from analytics.

Google sign-in

If you choose Google sign-in, Simple Fire receives your stable Google identifier and verified email address. They are used to register, return to the same dashboard and prevent duplicate profiles.

Only basic openid and email permissions are requested. Sign-in assertions are verified on the server; Google access tokens are not retained for ongoing access to Google data. An email hosted by another provider may require a one-time confirmation code. Google processes the sign-in navigation under its own policies.

Why we use this information

Profile and session data support sign-in, access controls and tasks you configure. Chat and message data support recipient selection and sending content you approve. Subscriptions and balances determine access and let us verify charges.

IP and sign-in history help detect unfamiliar connections, display devices and end sessions. Support conversations let us answer requests. Sign-in and support-reply emails go to a verified address when email delivery is configured.

Where applicable, processing relies on providing a requested service, protecting it, legal obligations and separate consent. Visit analytics run only after your cookie choice allows them. Marketing emails are not enabled by default.

Yandex Metrica

Counter 113596513 starts after analytics consent. Yandex receives browser technical data, IP, visited public pages and advertising campaign tags. Its cookies, including _ym_uid and _ym_d, follow Yandex retention rules. Session replay and click maps cover public pages only; inputs and the interactive demo are hidden. Workspace reports contain section names only, without screen replay, email, passwords, codes, messages, or user and TikTok identifiers.

Rejection or withdrawal stops new measurements and removes accessible Metrica cookies on this domain. This does not affect sign-in or scheduled sends. Data already collected by Yandex remains subject to its policies.

Who may receive information

TikTok receives actions and messages needed for sign-in and your configured tasks. Telegram receives information passing through the bot or Mini App. A code entered in the bot passes through Telegram; deleting the message does not undo that transfer.

When email delivery is configured, Resend receives the verified address and transactional email content. Enabled push notifications use the browser’s push service. Hosting infrastructure, HTTPS proxies and image caches may process network data to deliver the website. Their applicable policies apply separately.

Administrators have access needed for support and service operations. Impersonating a user’s dashboard requires an administrative session, and actions are audited. We do not sell personal information. International transfers can arise through TikTok, Telegram, Resend and infrastructure; their terms depend on the providers selected.

Safeguards and retention

TikTok sessions and sensitive records are encrypted at rest. Bot tokens, sign-in cookies, passwords and one-time codes are not put in public files or regular logs. TikTok verification input is used for the current attempt; the bot attempts to delete input messages in Telegram.

Website sign-in lasts for 30 days without visits. Activity renews the session, up to 90 days from the original sign-in. Signing out or revoking a device ends its session immediately. Security history is limited to the last 50 events over 90 days. Anonymous visit aggregates are kept for up to 180 days.

Connected TikTok data, schedules and settings remain while the account is connected: subscription expiry freezes tasks without deleting the session. Financial records, audit and support requests may be kept longer for disputes or legal requirements. Backups follow infrastructure retention cycles; a deletion request does not instantly erase every backup.

Your choices and requests

Settings let you view devices, end sessions, and change notifications or cookie choices. Disconnecting TikTok stops new tasks for that connection. Contact support to request a data copy, correction or profile deletion.

We verify that the request comes from the owner. If law or a dispute requires retaining some information, we explain why and how much. Depending on applicable law, you may have rights of access, correction, erasure, restriction, portability, objection and complaint to a relevant authority.

Withdrawing analytics consent applies to future visits without stopping necessary sign-in and security processing. The revision date identifies policy changes; new optional processing purposes are not enabled automatically.