Privacy
Exactly what we hold, who else sees it, and what is permanent because it lives on a public chain. Checked against the database column by column, not written from memory.
Last updated September 19, 2026
1What we hold
The whole list, not a summary. Everything below is a column in our database or a record we create while you use the product.
- From X, when you sign in: your X user id, handle, display name and avatar URL, plus the access token from that sign-in. We ask X for two permissions only — reading your public profile — and for nothing that would let us act as you. We do not read your timeline, your followers or your direct messages, and we never receive your email address from X.
- An email field, which is usually not an email. The account row has one and it cannot be empty. X does not hand out addresses without elevated API access, so what we store is
[email protected]— a placeholder built from your handle. If X ever does return a real address, that is what lands there instead, and this page changes with it. - From you: the username you pick on SHILL, and the wallet addresses you add for payouts.
- From using the platform: the contests you join, the post URLs you submit and what you wrote about them, the curation decision on each entry with the reviewer and the note, the view count the curator recorded, your placings, payouts and transaction hashes, and any cards issued to you.
- Technical: each session record carries the IP address and browser user agent it was created from. This is how a session is recognised and how abuse is traced.
2What we never ask for
No date of birth, no phone number, no home address, no government ID, and no real email address — we never ask you to type one, and the field on your account is the placeholder described above.
No password either. Signing in with X is the only way into the deployed site, so there is no password to hold. A local development build does offer email and password, because a developer running the project has no X app to sign in with; that path is off everywhere the public can reach.
The reason is narrow and worth saying: the prize goes onchain to a wallet. Nothing in this product needs those fields, and a field we do not have cannot leak.
3What other people can see on SHILL
Your profile is public: username, X handle, avatar, entries, approvals, wins, payouts by token, and the submission heatmap. The global ranking shows your accumulated views. This is the point of the product — a record someone can check.
Active cards are public on the infractions board. Expired ones are not: keeping someone listed after a temporary punishment ends would be a permanent penalty for a temporary offence.
4Your wallet address
We never expose your wallet address to other users. Linking a handle to an address is doxxing: with the address, anyone reads that person’s entire balance and history onchain, forever. Our public endpoints select columns explicitly so an address cannot slip into a response by accident.
The one exception is the organizer of a contest you won, at the moment they prepare the payout. They have to send the money somewhere.
Be aware of what this cannot protect: the payout transaction itself is public. Anyone who already knows your address can see that it received a prize from a SHILL vault, and work backwards. We keep the link out of our product; we cannot keep it off the chain.
5What is permanent, and not ours to erase
Deposits, settlements and payouts are transactions on a public blockchain. They carry wallet addresses and amounts, they are readable by anyone, and they cannot be deleted or corrected by us or by anyone else. Deleting your SHILL account removes you from the product; it does not unwind a payment that already happened.
6Who else is involved
- X — sign-in, and the posts you enter with, which are public on X already and governed by their terms.
- DefiLlama — we ask it the price of a token. We send a chain and a token address, never anything about you.
- Our hosting provider and managed database — they store what is listed above in order to run the service.
- Public RPC nodes — reading contract state means asking a node, and a node operator sees the requests our server makes.
7Cookies and tracking
Two cookies, both for your session and nothing else. One is the session token. The other is a five-minute copy of your own account row — name, handle, avatar — so that loading a page does not mean a database round trip. Both are signed, both are HttpOnly so no script can read them, and both disappear when you sign out.
No analytics product, no advertising pixel, no third-party script that watches you. The numbers on the analytics page come from our own database and from public chain data, not from following anybody around.
8Deleting your account
Ask us and we delete your account, your wallet addresses and your sessions. What stays: entries already judged and payouts already made, because they are part of contests other people competed in and a ranking that removes a competitor afterwards is a rewritten result. Cards stay for as long as they are active, for the same reason. Anything already onchain stays forever, as above.
9Contact
Questions, corrections or a deletion request: @justSHILLapp. See also Terms.