Legal & risk
Privacy notice
What SER stores, why, for how long, and how unlinking deletes your data. Draft pending legal review.
Last updated Sep 26, 2026
Draft — pending legal review
This is a plain-language working draft published for transparency. It will be replaced by a reviewed version, and the reviewed version is the one that will apply.
- SER identifies you by a wallet address and, if you link one, an X account’s immutable user ID.
- X access tokens are encrypted on the server and never stored in your browser.
- SER never asks for, stores or transmits seed phrases or private keys.
- Tracked-link analytics use hashed identifiers.
- Unlinking X deletes SER’s stored tokens for that account.
What SER stores
| Data | Why |
|---|---|
| Sign-in identity | The account you sign in with on the Become a ser page — a social account (X, Farcaster, Telegram), Google or email, or a wallet if you choose one. SER stores the provider’s stable id for it, as your account identifier. |
| Wallet addresses | The Solana and Robinhood Chain addresses you save for rewards, or a wallet you signed in with: used to check holdings and to publish and send reward allocations. |
| Solana payout wallet | If you link one: its address, the time you linked it and the signature that proves it is yours — so rewards from coins on Solana can be allocated and sent to it. |
| Session cookie | An httpOnly, signed session token set after sign-in; it expires after 7 days. |
| X account | Immutable X user ID, current handle, display name, profile image URL, verification status and link time — to show your identity and attribute posts. |
| X OAuth tokens | Encrypted with AES-256-GCM at rest; used only to read the data SER needs from X on your behalf. |
| Tracked posts | Public text, media type, links and engagement metrics of your posts that are relevant to a campaign, plus their classification and score. |
| Scores and standing | SER Score, tier, rank, trust level and the per-post scoring records behind them. |
| Rewards | Allocations, claims and related transaction hashes. |
| Account activity | Campaigns joined, notifications, and appeals you submit (including your message). |
| Tracked-link events | Clicks, landing visits, wallet connects and campaign interactions, stored with hashed identifiers. |
| Launches without a wallet connection | Token details, your refund wallet, a fingerprint of your manage link (never the link), the launch address and its transactions, and a keyed hash of your IP address for rate limiting. SER’s one-time launch key is held in a key management service, never in SER’s database, logs or your browser. |
What SER never stores
- Your seed phrases, private keys or wallet passwords.
- Your X password. X sign-in happens on X; SER receives only the tokens X issues.
- OAuth tokens in browser storage.
X content handling
- SER reads public posts from linked accounts through X’s official API to classify posts that relate to campaigns.
- SER displays post text and metrics with a link back to the original post on X.
- When a post is deleted or an account becomes protected, SER marks the post ineligible (“post deleted” or “account protected”) and stops displaying its content after the next sync.
- By default, X data is used for identity, display and reputation only. It feeds reward allocation only if X has granted written permission.
Tracked links
Tracked links (/r/…) let SER measure a funnel from a post to a click, a landing visit, a wallet connection and a campaign interaction. Events are recorded with hashed identifiers rather than raw ones, and shown to sers and projects only as aggregate counts labelled Tracked Attribution. Activity SER can only observe is labelled Observed Activity and is never presented as caused by a post.
Public and onchain data
- Public on SER: Ser passports and leaderboards show your handle, avatar, score, tier, rank, badges, public trust level and reward totals.
- Not public: trust-engine evidence, OAuth tokens, appeal messages and tracked-link identifiers.
- Onchain: transactions, reward epochs (including allocation Merkle roots), claims and fee routing are public on Robinhood Chain and permanent. On Solana, launches, fee distributions and reward transfers to your payout wallet are public and permanent. SER can’t delete onchain data.
Retention and deletion
- Account data is kept while your account is active.
- Unlinking X deletes SER’s stored OAuth tokens for that account immediately — even if revoking them at X fails — and removes the link between your wallet and that X account.
- Records needed to verify published rewards (epoch allocations and their Merkle proofs) are kept, because the onchain roots can’t be changed and claims depend on them.
- Security and audit logs are kept to protect the service and to investigate abuse.
Pending legal review
Specific retention periods and a data-request contact channel will be added in the reviewed version of this notice.
Security
- Sign-in is verified on SER’s server before a session is set; wallet sign-in uses single-use nonces that expire after five minutes.
- Session cookies are httpOnly, Secure and SameSite=Lax.
- X OAuth uses PKCE and a state parameter; tokens are encrypted at rest.
- Secrets and tokens are never written to logs. Administrator actions require a wallet signature and are audit-logged.
Service providers
SER runs on infrastructure providers that process data on its behalf: application hosting (Vercel), background workers and databases (Railway), Solana and Robinhood Chain RPC providers, X’s API, and error monitoring. Your wallet also sends requests directly to the RPC endpoint it is configured with.
Your choices
- Unlink your X account at any time from your dashboard.
- Clear your session by signing out.
- Appeal trust decisions as described in trust and appeals.