Privacy Policy

Who is responsible

The controller of your personal data is Max Wittal, DPT. 196/298, 76120 Cha-Am, Phetchaburi, Thailand. Write to legal@ghostrack.io for anything about your data.

In short

• An account is a key, not a name or an email address. We do not ask who you are.
• We do not read your instances' disks or what their traffic carries. The platform keeps the end of each instance's console or container output for you, and we read it only to help with support or to look into abuse.
• The website has no ads, no tracking and no third-party scripts, and loads nothing from other sites.
• Its cookies keep you logged in and remember your settings, so it asks for no consent.
• Deposits and payouts are on the MMX blockchain, which is public.
• Thai law requires us to keep, for 90 days, which account held which public IP address when, and the IP addresses you log in and make changes from. We keep no traffic content and no addresses your instances connect to.

What we keep and why

We process the data below to provide the service you signed up for (the contract), to meet legal obligations, and where noted for our legitimate interest in keeping the platform secure and working.

Your account

Your account's public keys, its account ID and alias, and its deposit memo. We keep no name or email address unless you write them in a support ticket. A website password, if you set one, never reaches us: we keep only a public key derived from it.

Website sessions

A session holds a hash of its token, the key it was begun with, how it was begun, and when it began, was last used and ends. It holds no IP address and no user agent; the IP address you logged in from is kept apart, in the traffic records below. Its record is deleted a day after you log out of it or it is ended for you, and at the latest a day after the 7 days a login lasts at most: 8 days after the login.

GitHub, when you link it

GitHub's numeric ID of your GitHub account, that account's creation date, when the link began and ended, every login name we saw it under with the first and last time we saw it, and which GitHub account gave the trial credit to which account. We read your public profile once at each sign-in and store no GitHub token. We keep these with the account's records, after an unlinking too, to know who held an account if the law requires us to say (legal obligation and legitimate interest).

Deposits and payouts

The MMX transactions you send us and we send you: their IDs, amounts, memos and addresses, and the exchange rate each was credited or paid at. These are on the public MMX blockchain, where anyone can see them and nobody can erase them.

Billing records

Your ledger: every charge, credit, refund and hold, with what it was for (contract and legal obligation).

Instances and their use

Your instances, backups and their settings, and how they are used: run time, CPU time and the volume of traffic, which billing needs. We meter how much traffic an instance sends and receives, not what it contains.

The end of what an instance writes to its console, or a container to its output: the last 64 KiB of the current boot or run and of the one before, replaced as the host sends newer output, and for a VM the result of cloud-init. You read them on the website and with ghost; we read them only to help with support or to look into abuse, and an operator's read of a VM's console is logged.

What you give an instance to start with: a VM's cloud-init data or startup command, and a container's environment variables, which may hold secrets. They are kept encrypted under a key of the platform's, which decrypts them only to hand them to the host that runs the instance, or to give a container's to an instance restored from its backup.

A review you write of a provider is public on its page, with your account alias and a range of what you paid that provider in the last year.

Support tickets

What you and support write in a ticket, and what it is about.

Emails and abuse reports

What you write to legal@ghostrack.io or abuse@ghostrack.io, with your name and email address, and what we did about it. An abuse report names the instance it is about, so we also keep it with that account's records (legal obligation and legitimate interest).

If you are a provider

Your provider name and alias, the hosts you enroll with their hardware, location, network addresses, measurements, uptime and incidents, your prices, earnings and payouts, and your payout address. Public on the website and in the catalog are your provider name and alias, your offerings with their location, hardware and prices, your hosts' reliability record and network tests, and renters' reviews of you.

Security

The limits on logins and GitHub sign-ups count requests per IP address, and failed logins per account and address, in the server's memory only: the counts are never written to disk or to a log. A count stays in memory until the server restarts, or until its window of at most an hour is over and the server, holding many counts, clears out the old ones. To detect abuse such as port scanning, the platform's machines that carry your instance's traffic may count per instance how many connections it opens and how many go unanswered, without keeping the addresses it connects to (legitimate interest).

Traffic records

The law of Thailand, where the operator is, requires a service provider to keep computer traffic data for at least 90 days and to be able to identify the user of its service (the Computer-Related Crime Act, section 26). For this we keep two records (legal obligation):

• Which account and instance held each public IP address the platform gives an instance, and for an address shared with other instances which of its ports, from when to when.
• The IP address of each login to the website, with a login link, a website password or GitHub, and of each change made with your account key, such as with ghost: by day, with the first and last time that day and how often (changes are counted at most once every five minutes). An IPv6 address is kept by its /64 network.

They hold no traffic content, no addresses your instances connect to, and no record of the pages you read. We look at them only to answer an authority or a court, or to handle an abuse report about an address, and each lookup is logged with its reason.

Website visits

The website counts its own use on the server: the page by its route, whether it was found, whether you were logged in, the site a link came from, and the kind of device. To count visitors once a day it hashes your IP address and user agent with a secret that changes every day and is held only in memory; only the counts are stored. It sets no cookie for this (legitimate interest). What the website counts (external site) has the details.

The website's and the API's own logs record no IP address. The web servers in front of them may log connections, with the IP address, to keep the service running and secure (legitimate interest).

What we do not do

• We do not read your instances' disks or what their traffic carries; we read console and container output only to help with support or to look into abuse. Providers run hosts for renters, and the Terms of Service forbid them to look inside them.
• We do not sell data, show ads, or track you across sites.
• The website loads its scripts, styles and fonts from its own address only, with no third-party scripts.

Who else receives data, and where

The operator is in Thailand, so running the service moves data abroad. These receive the data they need for their part:

• The data centres that host the platform's servers and database, in France; database backups are stored in Germany.
• The storage that holds hosted backups, in Germany, the United States or Singapore, nearest the host. Hosted backups are encrypted with a key derived from your account key, so the storage cannot read them.
• The providers that run the hosts your instances use, in the location each offering names. They run your instances, receive what an instance is started with, and carry its traffic.
• The network providers of the platform's gateways, in Europe, the United States and Asia, which carry the traffic of instances that reach the internet through a gateway.
• The content delivery network that serves the downloads of ghost, ghostd, the desktop app, the host agent and their updates from servers around the world. It receives the IP address of every download.
• The documentation site, docs.gigahost.cloud, is served through the platform's servers by an instance on a host in Poland, which receives the requests passed on to it.
• GitHub, when you sign up or log in with it.
• Authorities and courts, when the law requires us to disclose data.

How long we keep it

• Accounts, the ledger, deposits and payouts: for as long as the account exists, and after that as long as accounting and tax law requires. The platform does not delete them by itself.
• Sessions: a day after you log out of them or they are ended for you, and at the latest 8 days after the login.
• Support tickets: deleted a year after the ticket was closed or resolved, counted from its last change.
• GitHub link data: with the account's records, as above.
• Emails and abuse reports: as long as we need them to handle the matter and to show what was done.
• Instances: their disks are deleted when they are deleted; backups as you keep them, until deleted.
• Console output, cloud-init's result and container output: replaced by newer output, and deleted with the instance. A container's environment variables: until the instance is deleted and no backup of it can still be restored. A VM's cloud-init data or startup command: no longer used once its host has applied it, while its encrypted copy stays with the instance's records.
• If you are a provider: your hosts' records and your earnings and payouts, as the ledger above.
• Traffic records: 90 days after an address was let go, or after the day of a login or change; longer only when an authority orders it for a named account, until the date the order names.
• Visit counts: by the hour for 30 days, by the day for 2 years.
• What is deleted from the database stays in its encrypted backups until they expire, after about four weeks.

Cookies and storage

Every cookie and storage key the website uses is below. Each one is needed for something you asked for, such as staying logged in, or keeps a setting: the theme you chose and, until you close the browser, your browser's time zone. None is used for tracking or statistics, so the website asks for no consent.

The documentation site, docs.gigahost.cloud, sets no cookies. It keeps the theme you choose (starlight-theme) and the tab you last picked in its examples (starlight-synced-tabs__interface) in local storage, and which sidebar groups are open (sl-sidebar-state) in session storage.

Your rights

You may ask for access to your data, its correction or deletion, a restriction of its processing, a copy in a portable form, and you may object to processing based on our legitimate interest. Where the law requires us to keep data, such as bookkeeping records, we restrict it instead of deleting it.

Write to legal@ghostrack.io. An account has no email address, so we may ask you to prove that you hold the account key, for example with a support ticket of the account.

You may also complain to a supervisory authority: in the European Union the one where you live or work, and in Thailand the Personal Data Protection Committee (PDPC).

Changes to this policy

When this policy changes, the date at the top changes with it, and we say what changed on this page. The Terms of Service say how changes to them are announced.

25 October 2026: we keep the traffic records Thai law requires, which account held which public IP address when and the IP addresses of logins and changes, for 90 days (What we keep and why, How long we keep it).