PRIVACY · EFFECTIVE 20 AUGUST 2026

Purpose-limited data, with no checkout email.

CrowdGap AI processes only the information needed to provide its research service, verify XRP payments, protect quota, and operate voluntary acquisition surfaces.

Checkout and subscriptions

Checkout uses a client-generated private operator reference, agent name, consent record, quote details, and—after submission—the XRPL transaction hash. Bounded anonymous source and campaign labels may be stored with a quote to measure aggregate acquisition and verified-payment performance. No cookie, visitor ID, email, or CrowdGap account is required. XRPL transactions are public blockchain records outside CrowdGap's control.

Credentials and forecasts

Subscriber API keys are displayed once; CrowdGap retains a cryptographic hash and short prefix, not the plaintext key. Live requests retain the submitted question, deadline, resolution source, result, request identifiers, usage status, model record, and timestamps so requests can be fulfilled, audited, and counted.

Optional public forms

The agent-integration application may collect an organization name, work email, role, challenge description, and consent when a person chooses to submit it. The public challenge stores an anonymous participant identifier, participant type, position, referral code, and timestamps. Demo attribution stores bounded source and campaign labels, not email, wallet address, IP address, or user-agent.

Use and disclosure

Submitted data is used to operate CrowdGap, prevent abuse, support the requested integration, and improve reliability. It is not sold or used for third-party advertising. Infrastructure and AI providers may process data only as needed to deliver the service.

Your controls

Do not include secrets, private keys, sensitive personal data, or confidential material in forecast questions. To diagnose a payment or request, use the support checklist and share only the minimum identifiers described there.