Skip to main content
Ghost Cheats
Sign in
Ghost · Privacy

Privacypolicy

Effective July 5, 2026. Reads in 6 minutes — short and to the point.

This is a plain-words account of what data we collect, why we need it, and what you can do about it. We're a private software store, and privacy isn't just a word to us: minimum data, maximum protection, and we never trade your information. The essentials are below, the detail is in the sections on the right.
01

Who we are and how to reach us

This policy describes how the Ghost project handles your data on the site and in our products. By placing an order, registering, or launching our software, you agree to what's written here.

  • Data controller — the Ghost team, a private software store.
  • Site — ghost.one. Product — a temporary license to software we build and maintain ourselves.
  • We decide what data is processed and why, and we're responsible for keeping it safe.
  • The service is meant for adults. We don't knowingly collect data from minors.
Data questionsSupport on Telegram
For anything about your data — from "what do you store about me" to "delete me" — write to support. It's a live channel, and we answer fast.
02

What data we collect

We split data into three groups: what the service can't run without, what you give by choice, and what we never touch.

Necessary

  • Nickname and email — login, orders, purchase emails
  • Password — only as an irreversible hash, never in plain text
  • Device identifier and basic tech configuration — to bind the license
  • IP and login session data — security and account-takeover protection
  • Order details — what you bought, amount, payment method

By choice

  • Phone — if you decide to add it to your profile
  • Avatar — uploaded or from a social network
  • Social login — Google, Yandex, Discord, Telegram
  • Telegram for notifications — if you connect it

Never

  • Your bank card details — only the payment service sees those
  • Your password in readable form — even we don't know it
  • The content of private messages outside support
  • And we don't sell your data — under any circumstances
03

Where the data comes from

We get data in a few ways, and all of them are obvious.

01

Directly from you

When you register, place an order, set up your profile, or write to support.

02

Through social login

If you sign in via Google, Yandex, Discord, or Telegram, we get a basic profile: email, name, and avatar.

03

From your device

The site and loader send technical device and license-activity data — for the product to work and stay secure.

04

From payment systems

Payment status and transaction ID. Card details stay with the payment service.

05

From analytics

Anonymized visit statistics — which pages people open and how they move around the site.

04

Why we need this data

We process data only for a specific job. Next to each purpose is the legal basis we rely on.

  • Create an account, issue a key, and service your licenseContract
  • Bind the license to a device and prevent access theftContract
  • Take payment and protect it against fraudContract
  • Answer in support and resolve your issuesContract
  • Catch multi-accounts, bonus abuse, and misuseLegitimate interest
  • Measure traffic and improve the siteConsent
  • Send service emails — codes, receipts, order statusContract
  • Send news and deals — only if you're subscribedConsent
  • Comply with the law and settle disputesLegal duty
05

Device data and the loader

Our product is a license bound to a single device. For that to work, the loader reads technical data from your computer. It's not about your identity — it's about the hardware and the launch.

  • Device identifier — to bind the key to one machine, one key per device.
  • Basic system configuration — components and OS parameters, network identifiers; needed for compatibility and to prevent device spoofing.
  • License activity data — loader version, launch times, and approximate region by IP.
This data serves the license itself and protects it from theft. Without access to a device identifier, the one-key-one-device binding is physically impossible.
06

Cookies and analytics

We use cookies and similar technologies. Some are required for the site to work, others are optional.

Strictly necessary

Keep your session and login alive. Protected and inaccessible to scripts. Without them you can't stay logged in.

Functional

Remember your language, referral code, and small interface settings.

Analytics

Help us measure traffic and improve the site. Anonymized, with no link to your identity.

Protective

Anti-bot protection (reCAPTCHA) to filter out automated attacks.

Analytics and protective cookies are set by third-party services. You can manage cookies in your browser settings — but without the strictly necessary ones, the site may not work properly.
07

Who we share data with

We don't trade your data. But for the site to work, some data is processed by vetted contractors — strictly to the extent their job requires.

Taking payments

Payment providers receive the amount and email for the receipt and payment verification. Card details stay only with them.

Analytics and protection

Web analytics and anti-bot services receive anonymized technical data — statistics and security signals.

Social login

If you use social login, we exchange basic profile data with Google, Yandex, Discord, or Telegram.

Infrastructure and delivery

Hosting and CDN store media and avatars; the mail service delivers emails; Telegram handles notifications and support.

Some contractors are located outside the EEA. In those cases we rely on the legally provided safeguards for transfers — standard contractual clauses and equivalent guarantees.

We don't allow any contractor to use your data for their own purposes — only to provide the service to us.
08

How long we keep data

We keep data exactly as long as the job needs, then delete or anonymize it.

Account and profile
As long as the account exists
Unfinished registration
Up to 30 days, then deleted
Login sessions
From 3 to 30 days
Verification and reset codes
10 minutes
Service and payment logs, analytics
Up to 90 days
Orders and reviews
Indefinitely, anonymized on deletion
09

How we protect data

We take your data seriously and protect it with technical and organizational measures.

  • Passwords and tokens are stored only as irreversible hashes — even we don't see your password.
  • Sensitive secrets, such as your two-factor key, are encrypted.
  • Sessions live in protected cookies inaccessible to scripts; 2FA login is available.
  • Access to data inside the team is limited and role-based.
  • When data is served outward, extra fields are stripped automatically.
No system is one hundred percent secure. If you spot a security issue — write to support, and we'll handle it fast and without red tape.
10

Your rights

It's your data. By law you have a set of rights, and we respect them — without bureaucracy.

Access

Find out what data we hold about you.

Rectification

Fix inaccurate data — some of it right in your profile.

Erasure

Wipe your account and related data — the right to be forgotten.

Restriction

Pause processing in disputed cases.

Portability

Get your data in a machine-readable form.

Objection

Object to processing based on legitimate interest.

Withdraw consent

Withdraw consent where processing relies on it, such as marketing.

Complaint

Reach out to a data protection supervisory authority.

To use any right — write to support on Telegram. To protect the account, we may ask you to confirm it's yours.

We respond within a reasonable time — usually within 30 days.
11

What happens when an account is deleted

When an account is deleted — at your request or automatically — here's what we do:

Fully deleted

  • Personal profile and contacts
  • Avatar
  • Balance and bonus history
  • Referral links and notifications

Anonymized

  • Orders and reviews
  • Support requests
  • Detached from you, kept for accounting and guarantees

Kept briefly

  • Some service and payment logs
  • Up to 90 days for security and disputes
  • Then deleted automatically
We must keep certain data if the law, an open payment, or a dispute requires it.
12

Changes to this policy

We may update this policy — for example, when we change services or contractors. We'll announce material changes in your account and in the Telegram channel. The date of the latest revision is at the bottom. Continuing to use the site after an update means you accept the new version.

Revision of July 5, 2026