Privacy & your data
Operator review required before public participation opens.
Shill stores public X account IDs, handles, selected publications, profile snapshots and contribution assessments. Rewards follow the stable X user ID returned with a publication. Authors who use Claim Rewards sign in through X to verify their account identity. X provides the account ID, handle and display name; public posts are collected separately through TwitterAPI.io.
Public and private information
Public pages show publication text and policy results. Operator-entered recipient handles and USD payment amounts are public. A saved wallet is linked to your verified X account ID and used for future requests. Claim Rewards stores the chosen payout method with each request: a wallet address and network for crypto, or the connected X account for XMoney. These details are visible to the author and authorized operators, including in private Telegram notifications. Crypto transaction hashes are public; their onchain recipients are visible in the block explorer. Browser sessions keep authors connected. No card data or X passwords are entered into Shill.
Retention and requests
Financial records and audit events are append-only. Public content retention, deletion requests and legally required financial retention must be reconciled under the operator’s published retention policy before production. An operator contact and rights-request process must be added before launch.
Third-party processing
Configured public content is sent to TwitterAPI.io and Jev through OpenRouter for ingestion and assessment. Private payment details and secrets are excluded from scoring. No external API calls are made by the isolated demo.