← AFKashPrivacy

What we collect, and why.

This is the complete list of data AFKash collects about you as a developer, in one table — not scattered across a wall of prose.

What data is collected

DataCollected whenSource
Anonymous device UUIDAlways, on first installGenerated locally
Device tokenAfter you sign inServer-issued, revocable
Coarse stack tags (e.g. rust, postgres)Only while targeting is on (default on)Detected locally from tooling-file presence, never file content
Account emailOnly if you sign in to claim payoutsGoogle or magic-link sign-in
Impression recordsEvery credited sponsored line shownRecorded server-side, at credit time
Click recordsEvery sponsored link you clickRecorded server-side, at redirect time
Payout details (bank / Stripe identity)Only if you cash outHeld by Stripe via Stripe Connect — not stored as raw bank details on our servers

Contextual, not behavioral

Stack targeting is contextual: an ad shows because your project looks like a Rust project, not because of anything tracked about you across sites or sessions. That’s a real technical distinction, not a rebranding of behavioral tracking. We detect your project’s tech stack locally (never your code) to show relevant ads and pay you more — the device id stays anonymous, there is no cross-site profile, and raw project manifests are never transmitted or stored, only the coarse tag list in the table above.

How long we keep it

Data is retained for as long as your account is active, plus a limited period for fraud review and financial recordkeeping.

Turning targeting off

The targeting toggle in the extension’s sidebar panel turns off stack-tag collection entirely — when it’s off, no tags are generated or sent. You still earn from the untargeted and house ad tiers with it off. This is not pay-for-privacy: turning targeting off costs you the higher targeted rate, not your ability to earn at all.

Requesting deletion

There is no self-service “delete my data” control yet. Open an issue at github.com/fiaaaansoo/AFKash/issues to request deletion; requests are handled manually until an automated path exists.

Advertisers

Advertiser contact and billing information (company name, billing email) is handled separately under our advertiser terms — it is not mixed into the developer-facing data table above, because a targeted developer’s data and an advertiser’s billing data are not the same policy surface.

This page describes what AFKash actually does today, in plain product language — not final legal text, and not yet reviewed by counsel.