> For the complete documentation index, see [llms.txt](https://docs.cindereth.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cindereth.com/legal/privacy-policy.md). # Privacy Policy Effective July 25, 2026. Cinder, a non-custodial utility on Robinhood Chain. Not affiliated with Robinhood Markets, Inc. ## 1. The short version Cinder has no accounts, no sign-up, and no cookies. The interface runs in your browser and your history stays in your browser. One thing exists server-side: an append-only activity log powering the leaderboard and site statistics, holding your public wallet address, the action type, and the transaction hash. All three are already public on the blockchain; the log stores nothing the chain does not. ## 2. What Cinder does not collect * No private keys or seed phrases, ever, under any circumstances. * No names, emails, phone numbers, government IDs, or payment details. * No cookies, no tracking pixels, no fingerprinting, no advertising identifiers. * No IP logging by Cinder itself, no behavioral profiles, no linkage between your wallet and any off-chain identity. ## 2a. The activity log When you complete an action through the interface, your browser sends a few fields to Cinder's statistics service: your public wallet address, the kind of action (burn, sell, swap, send, or revoke), the transaction hash, and the token symbol and amount. This powers the leaderboard and the site's aggregate statistics. Three properties bound its privacy impact: every field is already public on the blockchain the moment your transaction confirms; the log is append-only, so the credentials shipped in the site cannot edit or erase entries; and it contains no IP addresses, no timestamps beyond the entry's own, and no other data. To have your entries removed from the log, email from a message signed by the wallet in question. ## 3. What stays in your browser Your browser keeps a cache of your activity so the Profile draws instantly, and a note of which wallet you last connected so a refresh does not disconnect you. The cache is only a copy: your real history is rebuilt from public sources every time you connect, which is why it follows you to any browser or device. Clear in the Profile tab empties the local copy, disconnecting forgets the wallet choice, and clearing site data removes both. ## 3a. How your history works Your Profile shows the actions you performed through Cinder, and only those. It is read from the activity log described above, keyed to your wallet address, which is why it is identical on any browser or device and why it does not include transactions you made elsewhere. Cinder deliberately does not scan your wallet to guess at history: an outgoing transfer looks the same whether it came from Cinder or any other app, so guessing would put unrelated activity in your Profile. Rows are checked against the chain in the background and anything whose transaction was not sent by your wallet is removed. Cinder does not accept uploaded history files. ## 4. Wallet addresses and the blockchain When you connect, your wallet shares your public address with the page, in your browser. The interface uses it to read balances and build transactions you sign. Blockchain data, including every transaction you make, is public, permanent, and outside anyone's ability to edit or delete. The leaderboard and statistics shown in the interface are computed from this public data. ## 5. Third parties your browser talks to Using the interface, your browser makes requests to: your wallet extension, Robinhood Chain RPC endpoints, the Blockscout block explorer, and Vercel, which hosts the site and keeps standard, short-lived server logs. If the site's privacy-friendly analytics is active, Vercel Web Analytics counts visits without cookies and without tracking individuals across sites. Each of these operates under its own privacy policy, and requests to them necessarily carry your IP address, as all internet traffic does. ## 6. How the little that exists gets used Aggregate visit counts tell the operator whether anyone uses the tool. Public chain data powers the product's features. That is the entire list. There is nothing to sell, rent, or share, and Cinder sells, rents, and shares nothing. ## 7. Data retention Local storage persists on your device until you clear it. The activity log persists to keep the leaderboard's history meaningful, and entries are removable on request as described above. Hosting logs are retained by Vercel per its policy. ## 8. Your rights Rights of access, deletion, and portability under GDPR, CCPA, and similar laws are honored trivially: everything Cinder "holds" about you is in your own browser, where you already control it. For anything else, write to . ## 9. Eligibility and children The interface is for adults 18 and over. Cinder does not knowingly collect anything from anyone, including children, but the service is not directed at children under 13. ## 10. Changes Changes to this policy appear on this page with an updated effective date. A change that starts collecting something new would be called out plainly, not slipped in. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.cindereth.com/legal/privacy-policy.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.