1. Summary
The Sentinel Chain homepage is a static site and does not require a Sentinel account. It does not use advertising trackers or analytics scripts. The public testnet, explorer, RPC and faucet necessarily process network requests, and all on-chain activity is visible to the public.
This notice covers sentinelchain.net, rpc.sentinelchain.net, explorer.sentinelchain.net and faucet.sentinelchain.net. A wallet extension, browser, Cloudflare or another third party may process data under its own notice.
2. Public blockchain data
When a transaction is submitted or included, the following may be permanently public and copied by anyone:
- wallet and contract addresses;
- balances, token holdings, transaction values and gas use;
- transaction calldata, messages, memos, events and signatures;
- contract deployment and token metadata;
- validator identity, voting power and signatures; and
- the time and block in which activity occurred.
The Operator cannot generally erase confirmed blockchain data. Changing or deleting this website does not remove copies held by nodes, users, indexers or archives.
3. Website and explorer
The main site serves static files and reads current block data from the public RPC. It does not create a site account or set a first-party tracking cookie. “Add to wallet,” faucet and token-launch actions are initiated by the user.
The public explorer is read-only and has no public login. It indexes the ledger to display blocks, transactions, addresses, tokens, holders and validators. A separate private operator explorer is not exposed on the public domain.
4. Faucet abuse-control data
To enforce request limits, the faucet records:
- the requested destination address;
- the source IP address supplied through the trusted edge;
- the request time; and
- the resulting transaction hash.
These claim records are used for per-address, per-source and global limits. The faucet automatically removes claim rows older than 30 days during normal request processing. Blockchain transaction records remain public independently of the faucet database.
5. Security and infrastructure logs
Cloudflare, Athena and the validator edge services may process IP address, user agent, hostname, path, time, response status, TLS and abuse-detection data. Logs are used to operate, secure, diagnose and defend the services. Retention may vary with operational, backup, incident-response and legal requirements.
The public RPC validates namespace, JSON shape, request size, batch size and concurrency before forwarding allowed requests. The origin services are firewalled to the trusted web edge.
6. Service providers and disclosure
Data may be processed by infrastructure and network providers needed to deliver the Testnet Services, including Cloudflare and hosting/network operators. Data may also be preserved or disclosed when reasonably necessary to protect systems and users, investigate abuse, comply with law or respond to valid legal process.
Public blockchain data requires no disclosure by the Operator because it is already available to any person who queries or copies the network.
7. Security
Administrative interfaces remain private, public origins are restricted by firewall, traffic uses TLS at the edge, and public services apply request and concurrency limits. No system can guarantee absolute security. Do not submit production secrets, valuable keys or sensitive personal information.
8. Your choices
- Do not connect a wallet or submit a transaction if you do not want its activity public.
- Use a dedicated test wallet with no relationship to valuable or personally identifying accounts.
- Do not use the faucet if you do not want the limited abuse-control record described above.
- Browser controls may clear local wallet/site state, but cannot erase on-chain data.
9. Children
The Testnet Services are technical developer tools and are not directed to children. Do not use them if you are not legally able to consent to the processing described here.
10. Changes and contact
This notice may change as the public testnet evolves. The effective date above identifies the current version. A formal privacy contact and production legal entity must be designated before commercial launch. Never send a private key or seed phrase in a support or privacy request.