Privacy Policy
Last updated 2026-07-21
SigRank collects four token counts: input, output, cache-read, and cache-write. No prompt content, no code, no conversation text. SigRank (“we”, operated under MO§ES™ / Ello Cello LLC) is built privacy-first. This policy explains what we collect, what we never collect, and how your data is used.
What we collect
- Token telemetry — token counts, content lengths, and model identifiers measured by the local agent. These produce your numeric scores.
- Account identity — when you sign in with GitHub, X, or an email magic link, we receive an identifier and email from that provider to create your account.
- Profile details you choose to add — display name, optional handle, bio, location, links, and an avatar image.
What we never collect
The content of your prompts or AI conversations. The local agent reads only token counts and lengths — never the words. Transcripts never leave your device, and we have no way to read them.
Public vs. private
Public by default: your codename, display name, handle, avatar, bio, location, links, and your scores and rank — the leaderboard is a public, self-promotion surface.
Profile visibility toggle: you can set your profile to Private from your profile editor. When private, only your codename and computed metrics (rank, Υ Yield, class) are visible to other users. Your display name, handle, avatar, bio, location, and links are hidden. You still appear on the leaderboard.
Always private: your sign-in email and any payment identifiers. These are never shown on your profile, the board, or the public API.
Codename changes
You can change your codename from your profile editor. Your codename is your public identity and URL key (signalaf.com/user/<codename>). Changing it updates your profile URL. Previous URLs will not redirect — bookmark the new one.
Service providers
We use Supabase (authentication, database, and avatar storage), Vercel (hosting), your chosen sign-in provider (GitHub, X, or email), and — only if you choose to support the build — Stripe for payments. Stripe handles card data directly; we never see or store it.
Cookies
We use a single authentication cookie to keep you signed in. We do not use advertising or third-party tracking cookies.
Data retention & deletion
Your token telemetry snapshots are retained as long as your account is active — they are the historical record that powers your rank trajectory and cascade analysis.
From Settings you have two deletion options:
- Delete my data — erase all snapshots, scored metrics, ranks, devices, and enrollment codes. Your account, profile, and billing stay intact. This also pauses future data collection.
- Delete my account — fully sever your identity. Runs Delete my data first, then anonymizes your board row (kept as aggregate data), removes your name, email, and device keys, and cancels any active billing. This is permanent and cannot be undone.
Consent & opt-out
Before a device can send token telemetry, you must agree to the current Terms of Service and Privacy Policy. We record the timestamp and version you accepted for audit and compliance purposes.
You can pause data collection at any time from Settings. While paused, your agent submissions will be rejected and no new telemetry is stored. Existing snapshots remain until you delete them.
You can also delete your historical telemetry and revoke all connected devices from Settings while keeping your account. Account deletion permanently severs your identity and anonymizes your board row.
Your choices
- Edit or clear your profile fields anytime from your profile editor.
- Toggle your profile visibility between Public and Private.
- Change your codename (updates your profile URL).
- Pause data collection or delete your historical telemetry from Settings.
- Delete your account permanently from Settings.
Changes & contact
We may update this policy; material changes will be reflected by the date above. Questions: hello@signalaf.com.