Last Updated: August 13, 2026
This policy explains how Haze ("Haze", "we", "us") handles information when you use the Haze website, Discord bot, browser extension, and backend at api.hazemethod.xyz. It also covers the website Ticket Center and optional integrations such as Zernio.
Video processing at a glance: the standard Haze patch runs locally in your browser. When you explicitly enable TikQuick HandBrake, your browser sends the selected video to TikQuick for re-encoding before applying the Haze patch locally. Haze TikUpload sends the video from your browser to Zernio when you confirm a post.
When you sign in with Discord or use the Haze bot, we may process your Discord user ID, username, avatar, server membership, and Haze-related roles. We use this information to authenticate you, provide bot commands, determine your tier, grant or remove roles, and keep the website and Discord server in sync. Haze's OAuth flow does not request your Discord email address.
The bot processes the commands, buttons, and other interactions you send to it. Depending on the feature used, it stores information needed for Haze Credits, XP and levels, moderation and anti-abuse controls, sticky messages, server statistics, donation roles, and feature settings. Chat activity may earn XP, but it does not earn Haze Credits. When a feature depends on a Discord message event, the bot processes the message and channel identifiers and the content needed to perform that feature.
For donation tickets, we store the ticket number, Discord account, selected payment method and amount, ticket status, associated Discord channel, staff decision, rejection reason when provided, and role expiry. Payment services may provide Haze with a transaction identifier, amount, and payment status so we can prevent duplicate processing and grant the correct role.
The website Ticket Center shows your ticket's status only — number, payment method, amount, months, and creation date. It does not display, store, or transmit the messages in your Discord ticket channel.
We store records used to operate the service, including your weekly and purchased Haze Credits, temporary processing reservations, detected resolution, frame rate and file-size pricing data, upload count, approximate MB saved, HandBrake usage, account restrictions, warnings, and Donator or TikTok-role expiry. Weekly balances reset every Monday at 12:00 AM Manila time; lifetime totals may remain on the account record.
We do not use submitted videos to train models, advertise to you, or build advertising profiles.
If you connect Haze TikUpload, we store your Zernio API key in encrypted form and associate it with your Discord user ID. It is used only for the Zernio account and publishing actions you request. You can disconnect Zernio to delete the saved connection from Haze.
When you use Haze, we process normal request information such as IP address, timestamps, request metadata, and rate-limit events. For multi-account and abuse detection, we may also store a browser-generated device identifier, hashed identifiers, linked account IDs, detection outcomes, warnings, and termination status.
The website and extension store session details, basic profile and tier data, credit balances, feature preferences, and interface settings using cookies, local storage, or extension storage. Signing out clears Haze authentication data from the active browser. The extension's optional TikTok repair action deletes the ttwid cookie when you ask it to; it does not transmit that cookie's value to Haze.
The Haze bot uses one Discord privileged gateway intent, Server Members. This section describes what it is used for and the controls available to you. Message-content features (such as info commands and link moderation) are provided by a separate companion bot.
Used to welcome new members, log departures for moderators, and keep your Haze tier in sync when donation or booster roles change. As described above, we store your Discord user ID, assigned tier, and role expiry off-platform; this is required to grant your perks.
We do not sell personal information or share it with advertisers or data brokers.
| Information | Typical retention |
|---|---|
| Local optimizer video | Remains on your device |
| TikQuick HandBrake input and output | Processed by TikQuick; the output download identifier expires about 10 minutes after completion. TikQuick controls service-side file retention. |
| Ticket records | Retained while the donation record is needed |
| Zernio connection | Until you disconnect or request deletion |
| Account, credit, economy, role, and security records | While needed to operate the account, enforce limits, resolve payments, secure Haze, or meet applicable obligations |
Information is shared only as needed to provide a feature you use:
We may also disclose information when required by law or when reasonably necessary to protect Haze, its users, or others.
Haze uses HTTPS for network communication, encrypted storage for saved Zernio API keys, signed sessions, access controls, rate limits, and other technical safeguards. No internet service can guarantee absolute security.
Haze is not intended for children under 13, and we do not knowingly collect personal information from children under 13.
We may update this policy as Haze changes. The date at the top will be updated when the policy changes materially, and we may also provide a website or Discord notice.
For privacy questions or data-deletion requests, email haze@hazemethod.xyz or contact staff through the official Discord community linked at hazemethod.xyz.
This policy applies to the Haze website, Discord bot, browser extension, and backend service. Third-party services maintain their own privacy practices.