GigRadar

Privacy & governance

GigRadar is a co-pilot: it finds gigs and drafts the pitch; you close the deal. This page says plainly what it does and doesn't do. This is a hackathon build — see the repository's docs/COMPLIANCE.md for the engineering detail and known gaps.

What we store

Account
Email, display name, and a scrypt-hashed password (or a GitHub identity if you sign in with GitHub). Sessions are HTTP-only, SameSite=Lax cookies.
Skills profile
What you enter: skills, niches, rate floor, bio, portfolio links, excluded keywords. Used to score listings and write drafts. Nothing else is inferred about you.
Listings
Only the listings you open or send from the extension (title, budget, description text, public client signals, URL). Never marketplace passwords, cookies, messages, or anything behind a login you didn't open.
Drafts & digests
Proposal drafts, work-bench documents and the digest emails we composed for you.
Billing
Stripe holds your card data; we store only the Stripe customer/subscription ids and plan status.
Usage & audit trail
Counts of scored matches/drafts (for plan limits) and security events such as license rotation, with no listing content.

What we never do

AI use

Draft text is generated by a third-party language model (configured by the operator) from your profile and the listing. Listing text is treated as untrusted data, never as instructions; links in drafts are limited to your own portfolio links; and every draft ships with a checklist telling you to verify it before sending. When no model is available a labelled, deterministic template is used.

Your controls

Marketplace terms

Upwork, Fiverr and Freelancer set their own rules about automation and data use. You are responsible for following them. GigRadar is not affiliated with or endorsed by any marketplace; fixture mode exists so the full loop can be evaluated without touching one.

Demo deployment: Stripe runs in test mode. No real charges are made.