Privacy Policy
Version 2.2 · Last updated: October 28, 2026
This Privacy Policy explains what Zilem Method ("Zilem", "we", "us") collects when you use zilemmethod.com, the optimizer, the Discord bot, the browser extension and the backend at api.zilemmethod.com, why we collect it, who it is shared with, how long we keep it, and what you can ask us to do about it.
In one line: we collect what is needed to sign you in, enforce tier limits and stop abuse. We do not sell your personal information, and we do not use your videos to train models or for advertising.
1. Information we collect
| Category | What it includes | Why |
|---|---|---|
| Discord identity | Your Discord user ID, username and avatar, received when you sign in with Discord. Your password is never visible to us. | To create your session and show your profile. |
| Google identity | Your Google account ID, email address, and the name and profile picture Google returns, received when you sign in with Google or connect Google to an account you already have. Your Google password is never visible to us. See Signing in with Google below. | To recognise you and link that Google account to your Zilem account. |
| Server membership & roles | The roles you hold in the official Zilem Discord server, read through our bot. | To work out which tier you are on. |
| Usage counters | How many patches you have used in the current weekly period, your file-size allowance, and approximate request volumes. | To enforce tier allowances and quotas. |
| Uploaded files | The MP4 or MOV file you choose to process. | To produce your optimized file. See Section 5. |
| Patch history | Discord user ID with basic details of each patch you run (such as time and file characteristics). | So your library and history work, and to resolve support issues. |
| Technical & security data | IP address, request timestamps, request counts, and the device signals described in Section 3. | Rate limiting, abuse prevention and service security. |
| Donation records | Discord user ID, the amount and date of a donation, what it granted, and a reference for the payment. | To grant and extend access, and to handle refunds and disputes. |
| Assistant questions | The question you type, the earlier messages in that conversation, and the name of the page you asked from. Not your account, your ID or your files. | To answer you. See Section 1b. |
We do not ask for and do not want special-category data (such as health, political or religious information). Please do not send it to us.
1a. Signing in with Google
Besides Discord, you can sign in with Google, or connect a Google account to a Zilem account you already have. When you do, Google asks you to approve the basic sign-in scopes openid, email and profile, and returns three things to us: your Google account ID, your email address together with a flag telling us Google has verified it, and your name and profile picture. We never see your Google password.
We use the Google account ID and email address to recognise you and to link that Google account to your Zilem account. The name and picture are used only to label the sign-in screen. We store the Google account ID, the email address and the link to your Zilem account in our database — nothing else from Google.
What we do not do with Google data. Those three scopes are the only ones we request, so we have no access to your Gmail, Drive, Calendar, Contacts, YouTube or any other Google service, and we keep no Google access token. We do not use Google user data for advertising, we do not sell it, and we do not use it to train models. We disclose it to nobody except the hosting providers named in Section 7, who process it on our behalf.
A Google sign-in does not create an account. Zilem accounts are created with Discord, or with Telegram, because tier, credits and roles belong to the account rather than to any one sign-in. A Google sign-in is accepted only once that Google account has been linked to an existing Zilem account; an unlinked one is told plainly that it is not linked yet, and no session is created for it. To use Google as your way in, sign in with Discord first and use the Google row in your account panel to connect it.
Disconnecting Google. Use that same row to remove the link at any time — that deletes our record of it. You can also revoke Zilem's access from your Google Account at myaccount.google.com/permissions. Either stops us receiving new sign-in information from Google.
Zilem's use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.
1b. The AI assistant (Ask Zilem)
The website carries a support assistant, reachable from the bubble in the corner of every page. It is software, not a person, and it cannot see your account, your files, your payments or your credits.
What is sent, and to whom. When you ask a question, we send the question, the earlier messages in that conversation (at most eight) and the name of the page you asked from to Groq, a model provider, which returns the answer. That is the whole request. We do not attach your account key, your email address, your IP address, your payment details or your video files, and the assistant has no way to look any of them up. Groq processes the request under its own terms; we send it nothing beyond the conversation itself.
Questions about your own account are answered in your browser. If you ask for your Zilem ID, handle, plan or credits, the answer is assembled from your own session in the page, not sent to the model.
Transcripts, and the switch that controls them. The panel has a Help improve Zilem AI switch. While it is on, we store the question, the answer, the page name and the time for up to 90 days, so we can see where answers are wrong and improve them. Before anything is stored we remove email addresses, Zilem IDs and Discord IDs from the text, and we never store your IP address or your account key alongside it. The switch is on by default; turn it off and nothing further is stored. You can ask us to delete what was stored (Section 10), and it is deleted automatically after 90 days either way.
What it is not. Answers are generated automatically and can be wrong or out of date. They are not advice, not a statement about your account, and not a promise of access, quality or a processing outcome. Where an answer matters, the page it describes and these policies govern. For anything about a specific account, payment or refund, write to support@zilemmethod.com.
2. Cookies and local storage
We use a small number of first-party cookies. None of them is used for advertising or for tracking you across other websites.
| Name | Purpose | Lifetime | Attributes |
|---|---|---|---|
zilem_ds | Your signed-in session. It holds your account key — a Discord ID, or a Zilem-issued key when you sign in with Google or Telegram — plus your tier, file-size allowance, issue time, display name and avatar URL, and is signed with HMAC-SHA256 so it cannot be forged. | 7 days | HttpOnly, Secure, SameSite=Lax |
zid | An anonymous, HMAC-signed identifier used to apply rate limits without relying on your IP address. | 30 days | HttpOnly, Secure |
zlstate | A short-lived anti-forgery value used during Discord sign-in. It is scoped to /api and is cleared as soon as sign-in finishes. | 10 minutes | HttpOnly, Secure, SameSite=None, Path=/api |
gzstate | A short-lived anti-forgery value used during Google sign-in, and only when Google sign-in is running in its full-page redirect mode. Scoped to /api, and cleared as soon as sign-in finishes. | 10 minutes | HttpOnly, Secure, SameSite=None, Path=/api |
ztg | A short-lived value that lets the Telegram sign-in page recognise its own request when it checks whether you have confirmed in Telegram. It is not readable by JavaScript and cannot sign anyone in on its own. | 15 minutes | HttpOnly, Secure, SameSite=Lax, Path=/auth/telegram |
ztr | Where to send your browser back to after Telegram sign-in. It is validated against our own domain before it is used. | 15 minutes | HttpOnly, Secure, SameSite=Lax, Path=/auth/telegram |
We also use your browser's local storage for short-lived caches (for example statistics and verification widgets, which are refreshed from the server), and IndexedDB for an on-device library of files you have patched. The library is stored only on your device and is kept for up to 4 days. See Section 5.
You can clear cookies and site data at any time through your browser settings. Clearing them signs you out and empties the on-device library, and you may be asked to sign in again.
3. Device and browser signals (abuse prevention)
To tell real visitors apart from automated abuse, the optimizer collects a set of technical signals about your browser and device and sends them with its requests. They are:
- a canvas rendering value — how your device draws a small piece of text and graphics;
- a WebGL renderer string — the graphics hardware and driver your browser reports;
- an audio-processing value — how your device processes a short, silent audio buffer;
- screen information — width, height, colour depth and device pixel ratio;
- timezone, language and platform as reported by your browser;
- approximate hardware capability — processor core count and reported device memory;
- request timing — how long after page load the request was made.
Together these can be quite distinctive, and that is the point: they are used to detect automation, scripted requests and attempts to get around weekly quotas or rate limits. They are used for security and for enforcing allowances — not for advertising, and not to build a profile of your browsing outside Zilem. We do not combine them with any third-party advertising profile.
4. How we use information
- to sign you in and keep you signed in;
- to determine your tier and enforce weekly patch allowances and file-size limits;
- to process your video and return the optimized file to you;
- to run, secure, rate-limit and improve the Service, and to prevent abuse and fraud;
- to grant, extend and verify tier access, and to handle donations, refunds and payment disputes;
- to answer support requests and send you service messages (for example, about a change to these policies).
We do not send marketing email, and we do not sell, rent or trade your personal information.
5. Your files and how processing works
Which engine you select decides where your file goes:
- Server engine. Your file is uploaded to our processing infrastructure, the container metadata is rewritten, and the result is streamed or returned to you. The file is handled in transit and is not kept as a stored copy of your video after processing completes. Uploads are never posted anywhere or published on your behalf.
- Local engine. The work happens inside your browser tab. Your file never leaves your device and is not uploaded at all.
Patched files may also be cached in your browser's IndexedDB library, on your device, for up to 4 days so you can re-download them. That copy is local to you. The Service is not a backup service — always keep your own copy of your original file.
We do not use your videos to train models, we do not use them for advertising, and we do not claim ownership of them.
6. Advertising
Some tiers are supported by advertising, and an ad-free experience is a feature of certain tiers. Advertisements are served by third-party advertising networks — currently including Adsterra (through profitableratecpmnetwork.com) and A-ADS (a-ads.com).
These networks are independent third parties. They may set or read their own cookies and similar identifiers on your device, and they may collect technical information such as your IP address, device and browser characteristics in order to deliver and measure advertisements. That collection is governed by their own privacy policies, not this one, and we do not control it or receive the resulting advertising profiles. If you do not want this, you can use an ad-blocking tool, or choose a tier that removes advertising.
We do not pass your Discord identity, your Google identity, your email address or your videos to advertising networks.
7. Who we share information with
We share personal information only with the service providers needed to run the Service, and only as described here:
| Recipient | What it receives | Why |
|---|---|---|
| Discord | Your sign-in request; your user ID and role information | Sign-in and tier determination |
| Your sign-in request, and the basic profile, email address and account ID it returns to us | Confirming and completing your Google sign-in | |
| Vercel | Hosting of the website and its functions; standard request logs including IP address | Website and API hosting |
| Cloudflare | Storage and delivery of media and files used by the Service | Object storage and delivery |
Our bot backend (Railway-hosted, reached at api.zilemmethod.com) | Your Discord user ID, tier and usage counters | Tier checks, quota accounting, patch history |
TikTok video providers (including tikwm.com and ttvchk-api.tikquick.online) | The URL of a public TikTok video you ask us to analyse, verify or fetch | Public video analysis and verification |
TikQuick (encoder.tikquick.online, ps.tikquick.online) | File bytes and processing parameters, when a server-side engine is used | Server-side video processing |
| Zernio | Your connected-account token and the video you ask to publish | Publishing to a connected TikTok account, when you request it |
| TikTok | Public video data requests; and your video, caption and settings when you publish | Analysis and publishing you request |
| Groq | The question you type, the earlier messages in that conversation, and the name of the page you asked from — only when you use the assistant | Generating an answer to your question |
| Advertising networks (Adsterra, A-ADS) | Advertising identifiers and technical data collected by their own scripts — see Section 6 | Serving advertisements on ad-supported tiers |
We may also disclose information where we are legally required to, or where it is necessary to protect the rights, safety or security of Zilem, our users or the public. If the Service is ever transferred or reorganised, information may transfer with it, and we will tell you if that happens.
8. Where your information is processed
We and our providers operate servers in several countries, so your information may be processed outside the country you live in. Where a provider processes information on our behalf, we expect it to apply protections consistent with this policy.
9. How long we keep it
| Category | Retention |
|---|---|
| Sign-in session | 7 days, or until you sign out or clear your cookies |
| Linked Google account (Google account ID, email address and the link to your Zilem account) | While the link exists; deleted as soon as you unlink Google, or when you ask us to delete your records (Section 10) |
| Linked Telegram account (Telegram account ID, name, username if you have one, profile photo and the link to your Zilem account) | While the link exists; deleted as soon as you unlink Telegram, or when you ask us to delete your records (Section 10) |
Rate-limit identifier (zid) | 30 days in your browser; on the server it is held only briefly in memory for the rate-limit window |
| IP address | Used for rate limiting and abuse prevention at request time; retained in hosting-provider request logs for that provider's standard log period |
| Device and browser signals | Used at request time for abuse scoring; associated counters are short-lived |
| Usage counters | For the current allowance period, and a rolling window while your account is active |
| Patch history | While your account is active; deleted on request (Section 10) |
| Uploaded video (server engine) | Handled in transit; not retained as a stored copy after processing |
| On-device file library (IndexedDB) | Up to 4 days, on your device only |
| Donation records | Kept while your account is active and afterwards as needed for accounting, tax and dispute handling |
| Assistant transcripts (only while the Help improve Zilem AI switch is on) | 90 days from the question, then deleted automatically; deleted earlier on request (Section 10) |
10. Your choices and rights
Depending on where you live, you may have rights to access, correct, delete, restrict or object to the processing of your personal information, to withdraw consent you have given, and to complain to your local data-protection authority. We will honour these requests regardless of where you live.
- Access and correction. Ask us what we hold about you, and ask us to correct anything wrong.
- Deletion. Ask us to delete your patch history and account records. Write to support@zilemmethod.com from the email address you want us to reply to, and tell us your Discord user ID (or your Discord username) so we can find the right records. We may keep the minimum needed to satisfy legal, accounting or dispute-handling obligations, and we will say so if we do.
- Disconnecting Discord. You can withdraw access at any time in your Discord account under Authorised Apps, which stops us receiving new sign-in information. You can also ask us to delete the records we already hold.
- Disconnecting Google. Use the Google row in your account panel to remove the link, or revoke Zilem's access at myaccount.google.com/permissions. Either stops us receiving new Google sign-in information, and unlinking deletes our record of the link.
- Advertising choices. The controls described in Section 6 apply to data collected by advertising networks, and your browser and ad-blocking settings can limit it.
- Cookies and local data. Clearing cookies and site data in your browser removes the cookies and the on-device library at any time.
We respond to requests within a reasonable period, normally within 30 days.
11. Children
The Service is not directed to children under 13, and we do not knowingly collect personal information from them. If you are under 18, or under the age of majority where you live, please use the Service only with the involvement of a parent or legal guardian, and do not make a donation without their permission. If we learn that we hold personal information from a child under 13, we will delete it. A parent or guardian who believes their child has provided information to us can contact us to have it removed.
12. Security
We use HTTPS, signed and HttpOnly session cookies, request rate limiting and abuse-prevention measures, and we limit what our own staff can see. No internet service can be guaranteed perfectly secure. If you believe you have found a security problem, please report it to support@zilemmethod.com rather than testing it publicly.
13. Changes to this policy
We may update this policy. When we do, we change the version number and date at the top of the page and, for material changes, may provide a notice on the website or in our Discord server. The version in effect when you made a donation governs that donation.
14. Contact
Privacy questions, access requests and deletion requests can be sent to support@zilemmethod.com, or raised through the official Zilem Discord community.
See also our Terms of Service and Refund Policy.