Privacy

We use account, product, project, search, save, compare, build, opportunity, campaign, and share activity to make tokens& more useful for developers and to power enterprise adoption analytics where permissions allow.

Public activity can include published projects, profiles, product submissions, public programs, badges, and share cards. Private enterprise activity, account intelligence, market signals, exports, and reports are visible only to authorized workspace users.

Referral links may set a cookie so we can attribute signups or conversions to the share that brought someone to tokens&. We do not auto-post to social networks.

Developers can use personal or work email. Company workspaces require a company domain so we can reduce impersonation and protect enterprise data.

Enterprise buyers can request a deeper data review, DPA, or security conversation through sales.

Enterprise contracts should define retention, deletion, export, support, subprocessors, and notice requirements for that customer. The public trust center and data processing overview explain the operating model before contract review.