Privacy Policy

This Privacy Policy describes how Saysar handles information when you visit this website, create an account, run the launcher, play on Saysar Client, buy or earn cosmetics, or write to us in Discord, Telegram, or another channel we publish.

It sits next to the Terms of Service and User Agreement. Refund rights (failed delivery, removal by our fault, Plus pro-rata, full shutdown) are in the Terms. Data rights requests go to [email protected].

We keep what is required to run and secure the product. We do not store your Minecraft password or Microsoft credentials. We do not inventory other programs, screenshots, or files on your PC beyond the table below.

While the account is open, categories stay for the purpose stated. After a confirmed closure or erasure request to [email protected], the Delete / keep column applies. “Deleted” means removed from active systems and then from backups on the next backup cycle (within 30 days), not kept as a shadow profile.

Your data is protected in transit and at rest. Passwords are hashed. Connections use HTTPS / TLS. Account records, friends data, and Saysar chat we store sit on encrypted storage with access limited to systems that run the account, launcher, store, and messaging.

• We do not sell personal information to ad networks or data brokers.
• We do not build marketing profiles from your HUD or who you queued with.
• We are not responsible for phishing, reused passwords, malware on your PC, or unofficial launchers.
• Chat encryption at rest is not end-to-end between players — we must decrypt to deliver messages and, when required, to handle reports.

If we confirm a personal-data breach that is likely to result in a risk to your rights or account security, we are obligated to notify affected users by email to the address on the account within seventy-two (72) hours of that confirmation. We may also post on Discord / Telegram. This is a hard deadline we commit to, not a best-effort hope.

Where the law requires notice to a supervisory authority, we will make that notice as well. The message will describe what happened, what categories of data were involved if known, and what steps we recommend. Report suspected vulnerabilities or breaches to [email protected].

We use the categories in the table to create and secure your account, sign you in, install and update the client, show cosmetics, run friends and chat, prevent abuse, enforce bans, and answer support.

• OS, architecture, HWID, and selected Minecraft version decide which build to offer and help block repeat abuse — until erasure deletes those device ids.
• IP and device signals help detect stolen sessions, spam, and ban evasion during retention.
• We do not fingerprint you for advertising.
• We do not train public AI models on your chat or sell your email list.
• Staff do not casually read private friends chat. Message content may be reviewed only when a report, safety issue, fraud, or legal demand makes it necessary — and only by staff with a need to know.

Saysar is a multiplayer-facing client. Other people using the client can see your username, cosmetics, and online or in-game status you have not hidden.

We share data only when it is required to run the product. We do not sell personal data. Processors and hosts change over time; the list below reflects how Saysar operates. The exact payment brand is always the one shown on the checkout page for your purchase.

• Payment processors / aggregators shown at checkout — to complete a purchase and handle disputes. Card data stays with them; we do not receive full card numbers or a Minecraft password.
• Crypto Bot (@CryptoBot in Telegram) — processes crypto payments when you choose that option at checkout. To create the invoice we send only the price and currency, the description “Saysar store”, and a random order id. We do not send your username, email, HWID, or IP. You pay inside Telegram, so Crypto Bot and Telegram handle your Telegram account, wallet, and transaction details under their own terms. Crypto Bot sends us back the invoice status, the amount paid, and that order id so we can deliver the purchase.
• Lyrics services for the in-game music island — LRCLIB (lrclib.net), NetEase Cloud Music (music.163.com), Textyl (api.textyl.co), and Lyrics.ovh (api.lyrics.ovh). When the Lyrics option is on (it is on by default), the client sends the song title and artist name of the track playing on your PC to look up lyrics. In the Auto source it asks them in that order until one has the song; if you pick one source, only that one is asked. Requests go directly from your computer, so these services also see your IP address — no Saysar account data is sent. Turn off Lyrics in the Dynamic Island settings to stop these requests.
• Cloudflare — CDN, DDoS / bot protection, and Turnstile-style checks. Connection metadata may pass through their network.
• Hosting and infrastructure for the website (for example Vercel or equivalent), API, launcher downloads, and account database — wherever we currently operate those services.
• A legal demand we are required to meet.

Account and product data are stored on servers and databases operated by Saysar and its hosting providers. Providers may process data in the European Union, the United States, or other regions where they run infrastructure.

If you use Saysar from another country, your information may be transferred across borders to those locations. We use providers that offer standard contractual or equivalent safeguards where applicable. By creating an account you understand that transfer is needed to run the service.

The website may store a session, preference, or device identifier in the browser (including local storage). The launcher stores install paths and login state on your machine so you do not sign in every launch.

• No third-party advertising cookies on this landing site for cross-site tracking.
• Clearing site data or uninstalling the launcher removes local files — not your server-side account or purchases.
• A new browser or PC may create a new device id; that does not reset your purchases.

The table in section 2 is the retention schedule. On a confirmed erasure we delete chat messages and HWID / device identifiers for that account on the stated timelines — not merely deactivate the login while keeping a forever archive of those fields.

You may also ask [email protected] to delete chat history while keeping the account; we will purge stored Saysar chat for your account within 30 days of confirming the request.

Saysar is not directed at children under 13 (or a higher age if your country sets one). If we have such an account, contact [email protected] and we will close it and run the same deletion rules.

Subject to proving you own the account, you may ask us to access, correct, or delete personal data we hold, or to close the account. Write to [email protected] from the email on the account (GDPR and similar rights). For product help use [email protected]; for payment refunds use [email protected].

• Access — a copy of account fields we store (username, email, entitlements).
• Correction — fix a wrong email or username where the product allows it.
• Erasure — close the account and delete chat, HWID, friends, and profile data per section 2. Billing refs follow the table, then end.
• Chat-only delete — wipe stored Saysar chat without closing the account, within 30 days of confirmation.
• We will not restore cosmetics after a full erasure. Cash refunds follow the Terms.

Material changes to this Privacy Policy are published on this page and emailed to the address on your account at least thirty (30) days before they take effect, the same way as the Terms of Service. Discord / Telegram or launcher posts may accompany that email but do not replace it. The updated date at the top is the version in force after the effective date in that notice.

We hash passwords, encrypt traffic, and encrypt stored account and chat data at rest as described in section 3. You still have to protect the keyboard.

• Use a unique password. Do not reuse the Minecraft or Discord one.
• Do not share the account. Do not paste the password into fake launchers.
• Phishing pages, cracked “Saysar” jars, and session stealers are not our software. Losses from those are yours.
• Report security issues to [email protected] — not in public chat.

The data controller for this policy is Saysar, trading as Saysar Client (https://saysar.net). Correspondence: Saysar Client, Attn: Legal, correspondence for the operator of saysar.net, Russian Federation.

Privacy and data-subject requests: [email protected]. Security: [email protected]. General support: [email protected].