Privacy Policy

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.
• Support and beta reports — when you contact us or explicitly send a plugin bug report, we receive the summary, reproduction steps, expected and actual behavior, surface, board window and optional plugin version, tool name and reply email you provide. The plugin does not attach your full chat, local logs, or token telemetry.

SigRank | SignalAF Analyst in ChatGPT, Codex and Claude

The Analyst plugin retrieves public leaderboard statistics and public operator profiles. These lookups do not require a SignalAF account. We receive the tool arguments needed for your request, such as an operator codename, board window or comparison scope. The plugin does not receive your full conversation or access your private local logs. Local measurement and telemetry submission use separate services covered by this policy.

Beta reports are optional. You can review, edit or decline a report before sending it. Approved reports are delivered through Resend to hello@signalaf.com so our support team can investigate the issue and reply if you provide an email address. Report contents are not published on the leaderboard.

To limit spam, the reporting service uses the incoming request IP address in a short-lived rate-limit counter, held in memory or Upstash Redis. Redis counters expire approximately one hour after their last update. The IP address is not attached to the bug report. Our hosting and email providers also process the request and delivery information needed to operate their services.

What we never collect

The local measurement agent reads only token counts and lengths — never the words of your prompts or AI conversations. It does not send transcripts. If you choose to include text in a support message, that message is sent to our support inbox.

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), Resend (support email delivery), 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.

Support and beta reports are kept while the issue is open and for up to 90 days after it closes. We then delete the retained report and personal contact details from our support records, including our support mailbox. We may keep an anonymized technical summary to improve the service. You can request earlier deletion by emailing hello@signalaf.com; a SignalAF account is not required.

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.