> **DRAFT — Data Processing Addendum — draft summary**
>
> This is an operational procurement draft published for review by tokensand, LLC. It is not a signed agreement,
> does not establish approved clauses or commitments, and is superseded by any executed MSA, DPA, SLA or order form.
> Source: docs/procurement/dpa.md. Request the customer-specific version: https://tokensand.com/quote?intent=security_review&source=trust_artifact_api

# Data Processing Addendum Summary

Owner: tokensand, LLC
Contact: privacy@tokensand.app
Status: Operational procurement draft. Enterprise customers may execute a customer-specific DPA.

## Roles

For builder accounts and public product surfaces, tokensand, LLC generally acts as an independent controller for the service data needed to operate tokens&.

For enterprise workspace data, customer-provided product usage events, CRM exports/import metadata, and private adoption intelligence, tokensand, LLC generally acts as a processor or service provider on behalf of the enterprise customer, subject to the signed MSA, DPA, and order form.

## Processing Purposes

tokensand, LLC processes data to operate the platform, authenticate users, personalize builder discovery, power project and launch workflows, ingest customer usage events, generate privacy-safe adoption intelligence, produce enterprise reports, support integrations, prevent abuse, provide support, and comply with legal obligations.

## Data Categories

Data may include account/profile data, work email, company information, public project and tool submissions, saved stacks, searches, comparisons, referrals, event or launch participation, enterprise workspace membership, product usage events supplied by customers, CRM mapping metadata, and operational logs.

## Privacy Boundary

Developers are not sold as a raw list. Enterprise customers receive first-party, consented, public, or aggregate privacy-safe adoption signals. Private workspace data remains organization-gated. Cross-customer learning is aggregate-only and subject to minimum cohort thresholds.

## AI And Model Use

Private enterprise/customer data is used to generate scoped outputs for that workspace and is not used to train public models unless a separate opt-in agreement says so. Agent outputs are decision support, not guarantees.

## Security Measures

Baseline measures include authentication, role-based workspace access, scoped API keys, secret redaction, least-privilege operational access, encrypted transport, hosted infrastructure controls, audit-oriented logging, and approval-only external write actions.

## International Transfers

Where applicable, international transfers are handled through appropriate contractual and vendor safeguards. Enterprise customers may request updated transfer details during procurement.

## Deletion And Return

Upon termination or written request, tokensand, LLC will return customer-controlled enterprise workspace data through the owner export workflow (a scoped operational subset, delivered as CSV/JSON archives) and will delete it through an operator-assisted process within the period agreed in the order form, subject to legal, security, backup, billing, and operational retention requirements. Automated self-serve tenant deletion is not available in the product today; the deletion preview in Settings shows the covered tables. Coverage of remaining systems and provider copies requires customer-specific agreement on scope, ownership, retention exceptions, and verified disposition. This draft does not certify complete erasure across those systems; an archived provider record or revoked connection is not proof of permanent deletion.