Consent Architecture

Key Elements of Our Consent Architecture

1. Explicit User Opt-In

• Every data point begins with a clear, user-initiated action in the Permission Agent.

• Consent requests specify what data is being shared, how it will be used, and for how long.

2. Verifiable Metadata

• Each record includes:

  • Timestamp of consent

  • Anonymized user identifier or wallet address

  • Usage permissions (e.g., “training only,” “personalization allowed,” “non-commercial use”)

  • Source traceability (e.g., originating agent, app, or interface)

3. Immutable Consent Records

• Consent events are logged in a tamper-resistant format, with cryptographic proof where applicable.

• ASK token transactions can be tied to these records to confirm that value was returned to the user.

4. Scope-Aware Permissions

• Permissions are not one-size-fits-all.

• Our system supports granular scopes so data requestors can only use the data in the approved context, reducing compliance risk and maintaining user trust.

Why It Matters for AI Builders

• Regulatory Alignment: Meets emerging AI and data privacy standards (GDPR, CCPA, EU AI Act).

• Operational Trust: Verifiable provenance ensures datasets are safe to integrate.

• User Confidence: Increases willingness to share higher-value inputs when they know exactly how their data will be used.

The result is a permission-first data layer that powers AI with compliant, transparent, and auditable inputs — without slowing down your development cycles.

Learn More About Data Delivery Formats →