Terms & privacy

What an assessment is

Assessments are derived from public chain state at the stated block. Every page that shows one lists the reads it made, the block each was made at and the exact RPC calls to repeat them.

An assessment describes who holds keys or controls an address. It never describes any party's obligation or intention: a line saying that an exchange or a team is able to move funds is a statement about capability read from the chain, not a promise, a demand or a prediction of what that party does next.

What the site keeps

The check you start from the landing page runs in your browser against public RPC endpoints and is not recorded. To list other tokens the address holds, or the contracts it created, the address is also sent to our server, which asks a blockchain data provider; we do not keep it.

To list other tokens a contract holds, the address of a contract you scan on the For projects page is sent to our server, which asks a blockchain data provider.

A proof page is kept for up to seven days, so that everyone who opens the same link, and every chat app that unfurls it, sees one check instead of each paying for a new one. What is kept is the address in the link, the chain, and the transaction or owner address if the link carries them, together with what was read from the public chain. It is keyed by exactly those values, it expires by itself, and it is never joined to an account or to anything else.

The paid plans for projects keep what an account needs, and nothing more:

• The email address you sign in with, and a project or team name. We send nothing to that address.
• Your password never leaves your browser. We keep a keyed hash of a value derived from it, and a keyed hash of your one-time recovery code.
• One cookie, __Host-sr_session, which keeps you signed in for up to 30 days. Scripts on the page cannot read it, and it is sent only to this site. It is needed to sign in, so there is no cookie banner. There is no other cookie and no advertising.
• Your orders and payments: the period, the amount, the network, the transaction hash and the sending address, which are public on the blockchain anyway, and the invoice details you enter, with the invoice itself, and which plan each order and period is for.
• For the watch: the contracts you watch, their networks, and where alerts go (a Telegram chat or a Discord webhook you give us).
• For the security watch: the contracts you add to it, their networks, the admin wallets you name, the Safes you name, the limits you set, the wallets you name and their known addresses, the issuer request packs you open, the price feeds and bridge apps you name and your listing lines, the services you say you depend on, where its alerts go, how urgent each kind of alert is, the mutes you set, and a log of which member changed these settings and when. Our service also keeps the addresses it finds in control of each contract, the alerts it sent, and what it last read from the public chain, so that a restart neither repeats an alert nor misses a change, and so your team can read them on this site.
• For governance alerts: the governors and Snapshot spaces you add. Our service keeps the proposals it last read, so that a restart neither repeats an alert nor misses one.
• For the address book: the names, roles and links you give your addresses, including the name of a person or a counterparty you link an address to, and a log of which member changed it and when. Our watch service receives the book so that your alerts print those names.
• For the signer phone check: a phone number you give for a signer of your Safe, kept only locked with a key our watch service holds, so the site cannot read it, together with its last two digits, which signer it belongs to, who confirmed that the signer agrees and when. The watch service opens it only to ask a phone-data provider, whose name is on the account screen, whether that line recently changed carrier, was ported, is forwarded, or was SIM-swapped; the provider sees the number, and nobody else does. We keep the answer's outcome, never the number, in our logs or alerts. Without the signer's recorded agreement we keep no number and make no lookup. A number is deleted at once when you remove it, when you remove its signer from the address book, and when the team deletes its data.
• For the signer confirm ping: if a signer links their Telegram account, the Telegram number of that account, kept with the team and the signer's address until they unlink, the signer is removed from the address book or the team deletes its data, and which button they pressed for which queued transaction.
• For your own rules: the rule file you save on this site or deploy from your repository, the rules read from it, and a log of which member or key saved or deployed it and when.
• For API keys: a hash of each key, never the key itself, which is shown once; its first 12 characters, its scope, who made it, and when it was made, last used, expires or was revoked; and for each call made with it, when it was made, the route and the answer, kept for 90 days.
• For the bot heartbeat: the name and check-in interval you give each bot, a hash of its check-in URL's secret, never the URL itself, which is shown once; the time of its latest check-in; and a log of which member added, deleted or renewed a bot and when.
• For the alert history: with each alert, the address, transaction and block that triggered it, and, for each CSV export, which member made it, when, the filters used and how many rows it held.
• Scan reports you save.
• A log of actions taken by us and by our own service on accounts, without passwords or the contents of requests.
• To limit abuse, a keyed hash of your connection's address that changes every day. The address itself is not stored.
• For approval alerts and minimum balances: the minimum balances you set, and the spenders each of your wallets has approved, so that a spender counts as new only once.

How long: an unpaid order expires 30 days after it was made, or 30 days after the last amount it quoted you if that is later. Watching stops on the day a period ends; your account and your past reports stay open to you for a month after that. Paid orders, payments and invoices are kept, because tax law requires it.

An account that has never paid is deleted within a day once 30 days have passed since it was made, its last order and the last amount it was quoted.

Where: with Cloudflare, which hosts this site and its database. Blockchain data providers can see the addresses and amounts our checks read, which are public anyway. Safe's Transaction Service can see which Safes we ask it about. Snapshot can see which spaces we ask it about. Telegram, Discord, Slack and PagerDuty can see only the alerts you choose to receive there, and so can whoever runs a webhook address you give us.

To see, correct or delete what an account holds, except what tax law requires us to keep, write to legal@sixstarlab.com from the email address you sign in with. The seller named under "Who runs this" decides what this site keeps and why.

What it costs

Checking an address, the proof page and recovering funds yourself are free. You pay only the network's own gas when you move funds.

SixStar does not recover funds for you and never touches your money. There is no success fee, because there is no service that takes one.

A project or a support team can buy a period of the paid plan, which covers whole-contract scans and watching up to 25 contracts. You pay once, in advance, in the stablecoin and on the network you choose, at the price shown when you choose the period. A period starts on the UTC date your payment was made on the chain, once the network confirms it. If a period is still running, the new one follows it. Nothing renews by itself.

If a payment is not exact, nothing is decided by guessing: a short payment can be completed or refunded on request; more than one dollar extra is refunded on request; a second identical payment adds another period, or is refunded if you ask within 14 days; the wrong token is credited or returned, never kept; a payment on another network we support is credited by a person.

The paid plans are sold to projects and teams for their work, not to private individuals. A period is a service that starts as set out above, and by paying you ask for it to start then. A period that has started is not refunded, except as set out above for payments that are not exact.

Before you buy, check that the law where you are allows you to buy and use this service.

The code

The code is Apache-2.0 and provided without warranty; you use it at your own risk, and nothing here is advice.

Who runs this

This site is run by SixStar Lab. The public channel for questions is @SixstarLab on X.

For a data request or a takedown about a proof page, write to contact@sixstarlab.com.

The paid plans are sold by SixStar Lab. For a question about a purchase or an invoice, write to legal@sixstarlab.com.