Public directory data
Published product profiles, public projects, public program pages, badges, rankings, share cards, and public proof artifacts.
Enterprise overview
Data processing
tokens& separates public developer surfaces from private enterprise workspaces. Public programs, profiles, and share artifacts are intentionally visible. Enterprise analytics, account intelligence, exports, reports, and competitor monitoring are permissioned by organization.
Customer-provided usage events, CRM context, tracking keys, campaign budgets, and workspace settings should be treated as customer data. Delete-safe QA datasets must be labeled and removable.
Public share kits never include private competitor signals or organization-gated account intelligence. Report cards should be labeled as sample, public, or verified live before distribution.
This page is an operational overview, not the signed DPA. Enterprise customers should request contractual data terms, security review, and subprocessor review through the buyer workflow.
Customer workspace data
Enterprise analytics, account intelligence, exports, campaign budgets, CRM context, tracking keys, and customer reports.
Telemetry and usage data
Docs clicks, SDK starts, API events, product surfaces, campaign UTMs, retention signals, and adoption milestones sent by the customer.
Support and procurement data
Security questionnaires, quote requests, buyer notes, contact information, contract metadata, and support communications.
Enterprise data commitments to finalize in contract
Retention windows, deletion timing, subprocessors, data residency, audit access, breach notice, and support response targets should be finalized in the DPA, MSA, order form, and SLA for each customer.