Privacy

When you compute a Wagecard, we store the inputs you provide (role, geographic tier, experience band, list of tasks, hours per task, and an optional salary) plus the computed outputs (operational AI cost, market rate, substitution distribution, exposure score). For signed-in users, the Wagecard is linked to your account. Anonymous previews are linked only to a one-time draft token that is destroyed when the preview is claimed or expires.

We use Supabase Auth for sign-in via magic link. We don't store passwords — there isn't one. We collect your email address for authentication and transactional communication only.

For anonymous opt-in adoption signals (the “How much of your work do you already do with AI?” flow), we store your per-task bucket choice indexed only by role × task × geographic tier × experience band. No user id, name, email, salary, or company is attached.

We don't ask for your name, employer, exact city, exact salary at granular resolution, or any government identifier. We don't scrape your social profiles. We don't infer demographic attributes. The aggregate dataset that informs future methodology updates is anonymous by architectural construction — not by promise.

We use PostHog for product analytics and error tracking. PostHog runs in identified-only mode: events are linked to your user id only after you sign in for the first time. Page views and feature interactions on the marketing pages are anonymous until then. We do not run third-party advertising or marketing trackers.

You can opt out of analytics at any time by emailing hello@wagecore.ai — we'll suppress your user id in PostHog within 7 days.

When you generate a public share link for a Wagecard, the linked page becomes publicly visible at wagecore.ai/w/<token> and search engines may index it. We rotate or revoke share tokens on request.

The OpenGraph image rendered for a shared Wagecard contains the role title, geographic tier, experience band, headline class, and key numbers — never your email or any account-level identifier.

We rely on a small set of subprocessors. Each is contractually bound to handle your data only for the service they provide:

• · Supabase — authentication and database (US region).
• · Vercel — application hosting and edge functions.
• · Cloudflare — DNS and inbound email routing.
• · Resend — outbound transactional email (magic-link sign-in).
• · PostHog — product analytics and error tracking.
• · Stripe — payment processing (only for Pro subscribers).

We update this list when it changes. If a subprocessor change matters for you, ask and we'll explain.

Wagecards and personal account data are retained while your account is active. Email hello@wagecore.ai to request account deletion — we remove your account and personal Wagecards within 30 days. Anonymous aggregate metrics that don't identify you remain in the dataset.

You can export your Wagecards at any time. We'll add a self-serve export to the dashboard during pre-launch.

You have the right to access, rectify, and delete your personal data. We honor GDPR and CCPA requests from anyone, regardless of jurisdiction. Send a request to hello@wagecore.ai and we'll respond within 30 days.

We'll note any material change at the top of this page with a new “Last updated” date. We don't silently expand our use of your data.