How AdFanz handles account data, campaign data, publisher data, and beta tracking signals.
AdFanz uses Clerk for account authentication. Clerk may process account identifiers, login methods, session data, and related authentication information according to its own service terms and privacy practices.
AdFanz may use your authenticated account ID to keep campaigns, publisher sites, creator profiles, reports, payouts, credits, and dashboard records separated by account.
AdFanz stores beta product data such as creator campaigns, creator profiles, publisher sites, categories, preview image URLs, destination links, reports, review statuses, manual credit records, and manual payout ledger entries.
Public profile and ad data may be visible publicly when approved and active, including display names, bios, categories, preview media URLs, outbound link labels, and sponsored ad content.
AdFanz tracks impressions, ad clicks, creator profile views, and outbound profile link clicks to support reporting, fraud prevention, campaign credits, publisher earnings estimates, and beta analytics.
IP addresses and user-agent strings are hashed for tracking and fraud prevention. Raw IP addresses and raw user-agent strings are not intentionally stored in tracking collections.
AdFanz may use hashed request identity signals, timestamps, publisher keys, campaign IDs, profile IDs, status information, and click history to detect duplicate, suspicious, invalid, or non-billable activity.
These controls are beta-stage safeguards and may be adjusted as the platform learns more about traffic quality.
For privacy, account, or data requests during beta, contact: privacy@adfanz.com.
This contact is a placeholder for the beta and should be replaced with the final support process before production release.