Privacy Policy & Edge Data Practices

When the connector becomes AVAILABLE, a human owner may authorize datasets.get:* for a verified Kaggle account and a seller-owned connector binding. The application will hold one encrypted current refresh-token envelope and its generation. All Access Data will never ask the seller to paste a Kaggle password, API key, access token, or refresh token.

The private draft will retain only the dataset reference, title, current version, byte size, update evidence, privacy status, and provider license label. It will not copy dataset files, rows, schemas, filenames, previews, or descriptions. Account control or a provider license label does not establish resale, redistribution, or AI-training rights.

Revocation removes the live credential envelope from the current record and leaves a noncredential binding tombstone. Deployment-managed encrypted recovery may preserve an earlier state for up to seven days in operator-only quarantine. Recovery is separately authorized, unavailable to the application, and is not a second live credential record. A final retention and deletion procedure will be published before activation.

Current approved MCP activity uses an agent identifier, operator-controlled funding and spend limits, and purchase and reconciliation records. Planned Agent Businesses will add owner or sponsor identity, roles, policy versions, and references to funding sources and revenue destinations. An Agent Business is not a separate legal person. Private keys, access tokens, private policies, buyer history, and prompts are not intended for public display.

Whop hosts enabled checkout where configured. Stripe and x402 settlement are not live. Full card or bank credentials stay with the applicable provider. In the planned Version 2 model, the full buyer payment first enters an All Access Data collection account. All Access Data retains the disclosed platform fee and records the seller's share as payable to a separately selected, verified destination. An Agent Business may start with x402 preselected where supported, but the owner must confirm it and may select another rail. Wallet addresses and settlement activity on a public blockchain may be publicly visible and generally cannot be reversed.

4.1. Routing and Security Data: When an Unlocker resolves an allaccessdata.com/r/:slug link:

• IP Addresses: Cloudflare may process IP addresses for routing, security, and abuse prevention, including provider security logs under its applicable retention settings. The Data Listing application does not intentionally store cleartext IP addresses in its own listing database.
• User-Agent String: Parsed in worker memory to distinguish browsers from automated clients and protect the service.
• Cookies: The Platform uses HttpOnly session cookies for account access and link-specific ga_auth_ access-token cookies after a confirmed purchase. Cookie paths and lifetimes vary by payment flow; these tokens are not advertising trackers. The token itself is a credential, not an encrypted cookie value.

4.2. Publisher Account Data: To publish Data Listings, publishers provide an email address and password. We store a normalized email index and a salted password verifier in private Cloudflare KV, plus an opaque account identifier for listing ownership. Whop OAuth is an optional account-connection flow where configured. Public prepayment metadata does not show the publisher's password verifier or destination URL; an authorized redirect necessarily reveals the destination URL to the recipient.

4.3. Payment Telemetry: Financial credentials are submitted directly to the enabled hosted payment processor. BLCKSWMNGBRD LLC does not ingest or store full card numbers or banking secrets. When payments are enabled, we retain transaction identifiers, amounts, statuses, and related link or account records needed to reconcile access, refunds, and disputes.

4.4. Destination Content: Destination URLs use AES-256-GCM encryption in persistent storage. A current Data Listing uses an Access Link redirect to external content; it does not give the Platform continuous control of that destination. Future managed content is COMING SOON and may involve seller-authorized storage or processing after separate consent, rights checks, and disclosures.

BLCKSWMNGBRD LLC as Data Controller: The Company acts as a Data Controller with respect to creator account data (email and account identifier), optional Whop payout identity, and platform transactional payment logs.

Third-party destinations: Once a buyer follows an Access Link redirect, the destination operator may independently process personal data under its own notice. The precise controller/processor roles for future source connections and managed content depend on the service design and applicable agreements; they are not determined merely by possessing a source API key.