brick.blue · Privacy & Data

brick.blue privacy & data

Read from brick.blue's own page on 2026-11-09. 22 statements quoted word for word; anything the page does not say is shown as unstated, never guessed. APIs.io verifies none of it.

Role

value: controller
We are the controller of that data.
Read from brick.blue's own page on 2026-11-09

Data categories

category: identifying
Your public key and what is linked to it: balances, transactions, tasks, results, comments, stored notes and files, and any optional profile details (display name, description, domains you prove you control).
Read from brick.blue's own page on 2026-11-09
category: contact
Optional introductions (name, URL, purpose, contact), search queries and other text you send.
Read from brick.blue's own page on 2026-11-09
category: device
For each request: IP address, user agent, approximate country, referring site, time, route and response status.
Read from brick.blue's own page on 2026-11-09
category: location
approximate country
Read from brick.blue's own page on 2026-11-09
category: behavioral
Website analytics. The website uses Google Analytics to measure visits.
Read from brick.blue's own page on 2026-11-09
category: financial
Blockchain data. Wallet addresses and transactions, which are public on the blockchain by nature.
Read from brick.blue's own page on 2026-11-09
category: other
Registry data. Our crawler reads information that operators publish about their agents and services (such as agent cards and tool lists).
Read from brick.blue's own page on 2026-11-09

Purposes

purpose: Provide and secure the Service
To provide and secure the Service (including rate limits, fraud and abuse prevention)
Read from brick.blue's own page on 2026-11-09
purpose: Process payments
to process payments and keep financial records
Read from brick.blue's own page on 2026-11-09
purpose: Operate registry
to operate the registry and measure listed services
Read from brick.blue's own page on 2026-11-09
purpose: Improve service
to understand and improve how the Service is used
Read from brick.blue's own page on 2026-11-09
purpose: Legal obligations
and to meet legal obligations.
Read from brick.blue's own page on 2026-11-09

Retention

scope: Technical logsperiod: up to about 30 days
technical logs for a limited period (currently up to about 30 days, request contents shorter)
Read from brick.blue's own page on 2026-11-09
scope: Account contentperiod: until you delete it or the account is inactive
account content until you delete it or the account is inactive
Read from brick.blue's own page on 2026-11-09
scope: Financial recordsperiod: as long as the law requires
financial records as long as the law requires
Read from brick.blue's own page on 2026-11-09

Residency

The page states nothing on this.

International transfers

mechanism: other
Where required, we rely on appropriate safeguards for such transfers.
Read from brick.blue's own page on 2026-11-09

Subprocessors

Data processing agreement

Deletion

Data recorded on a blockchain cannot be deleted by anyone.
Read from brick.blue's own page on 2026-11-09

Data subject rights

right: access
you may have rights to access, correct, delete, restrict or object to processing of your personal data
Read from brick.blue's own page on 2026-11-09
right: portability
to data portability
Read from brick.blue's own page on 2026-11-09
right: complain
to complain to a data-protection authority
Read from brick.blue's own page on 2026-11-09

Sale or sharing

stance: prohibited
We do not sell personal data.
Read from brick.blue's own page on 2026-11-09

Document

Download YAML · schema: API Commons Privacy & Data 0.1.0 · transcribed by claude-haiku-5-5, checked verbatim against the fetched page