GHOSTSIG

Cookies & Local Storage

GHOSTSIG sets no cookies at all. There is no analytics, no advertising and no tracking on this site. This page lists everything the app writes to your device, with its purpose and how long it stays.

Local storage (essential)

The app writes these entries to your browser's localStorage, so it can find your account again on your next visit. None has an expiry date: each stays until the app changes it or you clear site data.

ghostsig:credentials

One record per passkey created or signed in with here: its credential identifier, the account name you chose, when the record was first saved, and whether a backup was made, with its date and the name of the backup set (the two words its shares begin with). For each address of the passkey: its label, its address and its public key on each ledger. No key material: a public key is what the ledger already shows. Removing an address removes it from the record, and a record the landing page reports as stale can be forgotten there.

ghostsig:chain

The ledger you last selected. Replaced when you select another.

ghostsig:network:<ledger>

The network you last selected on that ledger. Replaced when you select another.

ghostsig:node:<ledger>:<network>

The node you set for that network: its WebSocket address on the XRP Ledger, its Horizon and Soroban RPC addresses on Stellar. Written when you press Use this node and removed when you press Reset.

ghostsig:watch:<ledger>:<network>:<address>

The Stellar contract tokens you chose to watch for that address on that network. Changed when you watch or stop watching a token, and removed with the address.

ghostsig:logos:<ledger>:<network>

For each asset an account held here on that network: the address of its logo in the curated list, or that the list has none, so the list is not asked again. Written when the list is read. A session restored from shares writes nothing here.

ghostsig:sound

Whether sound is on. Written when you press the Sound key.

Session storage (essential)

The app writes one entry to the tab's sessionStorage, so a reload opens your account again without a sign-in. The browser drops it when the tab closes.

ghostsig:open

One address of the passkey account open in this tab, which is enough to find its record above. No key material. Replaced when you open another address and removed when you disconnect. A session restored from shares writes nothing here.

Offline copy (essential)

The app installs a service worker so that it opens offline, from a copy that is one version of every file. The worker holds nothing about you; the cache holds the XRPL Meta logos you were shown.

Service worker sw.js

Registered on your first visit over HTTPS. Stays until you clear site data. Each visit checks the site for a newer version, and an open page asks again every five minutes and when you return to its tab.

Cache storage ghostsig-<version>

The app's own files: the page, its code, styles, fonts, icons and sounds, the vendored libraries and these legal pages, written once when a version installs. Beside them, the XRPL Meta logos the page showed you, each kept after its first download so it is not downloaded again. All of it is deleted when the next version takes over.

In your authenticator

When you create an account, your authenticator or password manager stores a passkey for this site. It keeps a label (the account name you chose followed by a short random tag), a random user handle generated in the page, and the secret behind the PRF output, which the authenticator never reveals. The passkey stays until you delete it there. Clearing site data does not remove it.

What is never stored

No private key, PRF output or backup share is ever written to storage. The privacy policy says where a key lives, for how long, and what overwriting it does and does not clear.

Consent

The local storage entries, the session storage entry and the offline copy are needed to provide what you ask the app to do: find your accounts again, keep your account open across a reload, keep your settings, and open offline. Without them the app cannot provide these functions. None of them tracks you, and only this app reads them. Under §165(3) TKG 2021 they therefore need no consent, and the app asks for none. Clearing site data removes them, as the next section says.

Clearing storage

Disconnect ends the session and clears the account from the page. To remove the stored entries, the service worker and its cache entirely, clear site data for this site in your browser. Neither action deletes the passkey itself, which lives in your authenticator or password manager and is removed from there.