Privacy policy

Responsibility and scope

FetchTik administers service data needed for the extension, accounts, memberships and support. Contact FetchTik administration about privacy at haithamx09@gmail.com or @FetchTikBot. This policy covers the extension, cloud account service, administration dashboard and related support bot.

This document describes FetchTik processing. Google, Cloudflare, TikTok, Telegram and payment providers also have policies for their services. Referring to those policies does not remove FetchTik responsibilities for the data it controls.

Google sign-in and sessions

Google sign-in verifies your identity and supplies a name, email and account identifier to link membership and usage. The Google identifier is stored as a protected keyed hash. We do not request your Google password or permission to read your email or files.

Session credentials stay in private extension storage; the server stores hashes for validation. Session records include a random installation or browser identifier, browser/operating-system description, sign-in and last-contact times and session status. These are software identifiers, not hardware serial numbers, and browser labels do not establish a physical device identity.

Local and cloud data

The optional profile photo and interface preferences stay in your browser. A display name may be sent during account synchronization. The cloud service stores account, membership and trial details and dates, usage/quota, access status and sessions needed to provide access and prevent allowance resets through reinstallation.

Video preparation runs locally. Video files and filenames are not uploaded to the dashboard as part of preparation or its analytics. Records include operation, account and session identifiers, time and success/failure status; completed operations also include output dimensions, resolution and frame rate. Operational analytics do not include general browsing history or email contents.

Video and browser permissions

On authorized TikTok Studio pages, the extension connects preparation options to the upload interface. Storage permission keeps extension settings and sessions; video processing runs inside your browser on your device without an additional native component. Google mail or file access is not requested for sign-in.

Local processing does not mean local publishing: uploading or publishing sends the video to TikTok under your settings and its terms. FetchTik support receives a video only if you separately choose to send it there. Avoid sensitive attachments or other people’s information without an appropriate basis.

Support messages, attachments and payments

Subscription and support channels depend on the displayed settings: Telegram or WhatsApp. Contact drafts include the plan, price and, when signed in, account email and order reference for review before sending. Telegram or WhatsApp processes conversations under its policy. Stars checkout links your Google account to Telegram using a temporary link; account identifiers, order, amount and payment reference are retained to activate your subscription after confirmed payment. Other direct payment arrangements require administrator review. No recurring charge is initiated automatically.

Using the bot supplies a Telegram identifier, display name, language, messages, ticket references, support replies, timestamps and status. Attachments you choose to send can include photos, documents, video and audio, with metadata such as type, name, size and Telegram file identifier. Sending a video to support is optional and separate from local video preparation.

Authorized administrators can view the conversation in the dashboard, and notifications and attachments are relayed to the owner’s Telegram account. The service database stores text and attachment references; attachment copies move between Telegram chats. Downloading an attachment in the dashboard transfers a copy through the service to the administrator’s browser. Owner replies and attachments sent using native Telegram replies are recorded in the ticket too.

Order, plan, amount, currency, payment status, provider/transaction references and evidence you choose to submit may be kept to verify and link purchases and resolve disputes. Never send full card information, passwords or verification codes in support chat.

Purposes and legal basis

Data is used to provide the requested service, manage accounts, memberships, quota and sessions, verify payment, answer support and protect against abuse. Technical statistics help evaluate operation and review preparation events; they are not used for advertising profiles or cross-site tracking.

The applicable legal basis depends on purpose and law, such as providing the agreed service, a legal obligation, a permitted legitimate interest in protection or consent for optional processing where required. A photo, Telegram linking and support attachments are separate choices. Reading this policy or signing in does not consent to advertising or undisclosed purposes.

Recipients, hosting and Limited Use

Cloudflare hosts the account/membership service, dashboard and database. Google verifies sign-in, Telegram carries bot messages and attachments, and the selected payment provider handles payment. We do not sell personal data or add advertising trackers. Administration access is restricted to authorized people as needed for their work; disclosure may be required by a valid request from a competent authority.

These providers can process data on global infrastructure outside your country; we do not claim Saudi-only hosting. Network and hosting services process technical request information, such as network addresses, to provide and protect connections under their policies. Applicable transfer and protection requirements must be observed; ask the official email about recipients and safeguards.

Use and transfer of extension user data is limited to providing, supporting and securing its disclosed functionality under the Microsoft Edge Add-ons policies and applicable Limited Use requirements. Google data is not used for advertising, resale or unrelated purposes.

Retention and deletion

Local photos and preferences remain until changed or browser extension data is cleared. Signing out ends a session, not the account, membership or support record. Uninstalling does not erase cloud records, Telegram/payment-provider copies or files downloaded by a user or support administrator.

Preparation analytics display the last 90 days; older operation records are pruned when the log is updated. Necessary account, membership and usage data is retained while providing service. Support and payment records are reviewed according to request handling, fraud prevention, legal retention and dispute needs. There is currently no single automatic expiry deleting every account record.

After a deletion request and ownership verification, data without a continuing lawful purpose is removed or de-identified. Where a category must remain, its reason and scope are explained as applicable and its use is restricted to that purpose. Removing FetchTik records does not promise removal of independently controlled copies; you may ask what was removed, retained and why.

Your rights and how to exercise them

Depending on applicable law, you can request information about data, purposes and sources, access and a copy, correction or deletion, and withdrawal of optional consent where it is the processing basis. Proportionate identity verification, other people’s rights and retention duties may limit a request. We do not ask for your password or Google verification code to verify a privacy request.

Send privacy requests to haithamx09@gmail.com or @FetchTikBot. A paid membership or continued extension access is not required; email remains available if Telegram is unavailable. Requests are handled within applicable statutory periods, with an explanation of justified restrictions or delay. You can edit your photo and display name in the extension and may complain to the competent authority.

Protection and incident reporting

The public service uses HTTPS, session validation and administrative permissions to restrict access. Login credentials are not included in public documents or displayed analytics. No system guarantees absolute security; protect your Google account and device and do not share sessions.

Report suspected unauthorized access to the official email without passwords or verification codes. Incidents are assessed and protective measures and notices required by applicable law are handled for the case. This policy is not a guarantee that an incident can never occur.

Changes and contact

This revision was updated on 19 October 2026. Material purpose or recipient changes are explained before new processing where required, and separate consent is obtained when legally necessary. Merely posting new text does not authorize undisclosed uses of your data.

Official channels are haithamx09@gmail.com and @FetchTikBot linked from the extension. Verify the channel and do not trust unsolicited links requesting passwords or payment information.