TikQuick is an independent project made by mikedev_. We operate tikquick.online, the TikQuick browser extension, the desktop and Android apps, and the associated video processing services.
We are the data controller for the personal data described in this policy. We are not affiliated with, endorsed by, sponsored by, or in any way connected to TikTok, Douyin, or ByteDance Ltd.
This policy covers our website, the browser extension, the apps, the /web/ and /optimize/ tools, and the public API. It does not cover TikTok itself, which has its own privacy policy.
When you sign in with Google or Discord, we receive and store:
| Field | What it is |
|---|---|
| username | The username associated with the provider you signed in with, and your TikQuick display name. |
| provider / provider_id | Which sign-in provider you used (google or discord) and your unique user ID at that provider. Used to recognise you on future sign-ins. |
| avatar_url | A link to your profile picture, so the site can show it to you. Refreshed from the provider when you load a page. |
| created_at | The date your TikQuick account was created. |
We never see or store your Google or Discord password. Authentication happens entirely on the provider's side.
To keep you logged in, we record a session token along with the IP address and browser user-agent string the sign-in came from.
| Field | What it is |
|---|---|
| token | A random 64-character string that authenticates your session. |
| type | Whether the session is for the website (web) or the extension (extension). |
| ip_address | Your IP address at sign-in, used for security and rate limiting. |
| user_agent | Your browser and operating system identification string, used for compatibility and abuse detection. |
| expires_at | When the session stops working. |
Before your browser can send a video for processing, our site issues a short-lived one-time token. We store the token, the issuing user, its expiry, and — for anonymous users only — the IP address it was issued to.
Tokens are single-use and expire automatically. Logged-in tokens last 30 minutes; anonymous tokens last 5 minutes.
If you create an API key, we store the key itself, an anonymous public identifier for it, the account that owns it, the IP address that created it, and a usage counter. Other developers integrating TikQuick see only the anonymous identifier — never your username or account.
When a video is processed, our processing servers keep a log entry containing your TikQuick user ID and username, an internal job ID, a timestamp, the success or failure outcome, and technical error output from the media tools (for example ffmpeg or ffprobe). This is used to diagnose failed jobs and is visible only to the operators.
We rely on Cloudflare for content delivery and network protection, and on Cloudflare Turnstile to rate-limit anonymous users. When an anonymous user solves a challenge, Cloudflare shares the resulting verification with us so we can confirm it. We also keep short-lived rate-limit counters tied to an IP address in order to stop abuse and automated abuse.
We do not run analytics or advertising trackers, we do not build advertising profiles, we do not sell or rent data to anyone, and we do not collect the contents, captions, or metadata of your videos on our servers.
When you use /web/ or /optimize/, the video is uploaded directly from your browser to our processing servers and the finished file is streamed straight back to you. We operate no public library of user content, and processed videos are not retained after the job completes or fails.
Processing servers may create temporary working files in order to run the media tools. These are deleted when the job finishes. Nothing is kept for you to browse or share afterwards.
If you upload a video to TikTok — through the extension or through TikTok Studio — the upload goes from your device to TikTok. That publication is governed by TikTok's privacy policy, not this one. We have no access to what TikTok stores once your content is on their platform.
Previous releases of the browser extension included an optional usage-telemetry feature that reported install identifiers, browser and region data, and upload captions. That collection has been fully disabled server-side and is no longer in effect. Any data collected before it was switched off is stored on our private server and can be deleted on request — see §08.
We use data only for the following purposes:
Providing the service — authenticating you, keeping you logged in, issuing upload tokens, enforcing per-account usage limits, and minting API keys.
Security and abuse prevention — rate limiting anonymous access, blocking automated abuse, detecting ban evasion, and restricting internal administrative endpoints by IP allowlist.
Diagnostics — reviewing processing logs to identify why a job failed and to fix the underlying problem.
Account administration — applying bans, responding to abuse reports, and honouring deletion requests.
We do not use your data for advertising, profiling for advertising, or any automated decision-making that produces legal or similarly significant effects. We do not train models on your data.
We do not sell personal data. We share it only with the following categories of recipient, and only to the extent needed to operate the service:
We do not share personal data with advertising networks, data brokers, or social platforms beyond the sign-in flows you initiate yourself.
All primary data is stored on our own servers and is not sent to third-party analytics services. Backups are copied to a private Backblaze B2 bucket in the EU.
| Data | Retention |
|---|---|
| Account profile | Until you delete your account, or the account is closed by us. |
| Web sessions | Up to 30 days, or until you sign out. |
| Extension sessions | Up to 90 days, or until you sign out. |
| Upload tokens | Up to 30 minutes (5 minutes for anonymous users); expired tokens are deleted automatically. |
| API keys | Until you delete the key or your account. |
| Rate-limit counters | Short-lived; cleared as counters reset. |
| Processing logs | Retained for service reliability and diagnostics, then pruned. |
| Legacy extension telemetry | Collection is disabled. Historic records are deleted on request. |
We keep data only as long as needed for the purposes above, and will delete or anonymise it when no longer required.
TikQuick does not use advertising cookies or cross-site tracking cookies. We use a minimal number of strictly necessary ones:
| Cookie | Purpose |
|---|---|
| tq_sess | Session cookie. Holds your session identifier so you stay logged in. HttpOnly, SameSite=Lax, Secure. |
| tq-theme | Stored in your browser's local storage, not a cookie. Remembers whether you chose light or dark mode. |
Blocking or deleting cookies will sign you out and reset your theme preference, but will not otherwise affect the service.
You control your data. Depending on where you live, you may have the following rights:
Delete your account. Account deletion is available directly from your account settings on the site. It removes your profile, your sessions, your API keys, and your tokens.
Everything else. Email or Discord us at the contact in §11 and we will respond within 30 days. Please include your TikQuick username and, if relevant, the TikTok handle associated with your account so we can locate your records. We will verify your identity before disclosing anything.
Where the GDPR or equivalent legislation applies, we rely on:
If you are in a jurisdiction such as California, we affirm that we do not sell your personal information and do not share it for cross-context behavioural advertising. We have not done so in the preceding 12 months and will not do so without your explicit opt-in consent.
We do not use automated decision-making that produces legal or similarly significant effects about you. Account bans are reviewed by a human operator.
We take reasonable technical and organisational measures to protect your data: traffic is served over HTTPS, session cookies are HttpOnly and Secure, API tokens and session tokens are randomly generated, internal administrative endpoints are gated by secret keys and IP allowlists, and access to operator dashboards is restricted and logged.
No system is perfectly secure. If a breach affects your personal data we will notify you and the relevant supervisory authority as required by applicable law.
TikQuick is not directed at children under 13, or under the minimum age of digital consent in your country. We do not knowingly collect personal data from children below that age. If you believe a child has provided us personal data, contact us and we will delete it.
If you have questions about this policy, want to request access to or deletion of your data, or want to report a privacy concern, reach us on Discord:
DiscordPlease include your TikQuick Username and, if relevant, your TikTok @handle, so we can locate and act on your request.
Our use of this service is also governed by our Terms of Service.
If we materially change what data is collected or how it is used, we will update the "Last updated" date at the top of this page. Where a change is significant, we will post a notice in the site footer or on our Discord. Continued use of TikQuick after such a change constitutes acceptance of the updated policy.