Privacy

Privacy policy.

A plain-language privacy note for the current guide foundation and Submit intake.

Information we collect

The Submit form collects the community name, admin name if provided, email, admin contact, official link, additional community link, platform, approximate member count, free/paid status, verification interest, bot-install interest, public proof-page interest, result-sheet interest, preferred cadence, desired publication scope, logo/branding preference, PDF/archive/selected-sheet/private-PDF preferences, featured-visibility interest, support contact, initial consent preferences, signal format examples, and notes. These submissions are stored privately in WordPress for Editorial Desk review.

How we use it

We use submission details to decide what providers may deserve inspection, how to classify verification and result-sheet interest, and how to understand publication preferences. We do not sell form submissions. Payment cannot change verification status, ranking, risk notes, sheet calculations, or editorial conclusions.

Crypto billing records

For accepted paid work, a private billing record may include the accepted scope, invoice identifier, customer contact and required invoice details, reference currency, exact asset and network, quoted amount, rate source and time, expiry, payment address, transaction hash, confirmation state, reconciliation notes, and any refund record. Public blockchains are permanent public records. A transaction may remain visible even after CSR deletes data it controls.

Billing records are not published as a provider relationship by default. They may be retained where required for contracts, accounting, tax, fraud prevention, sanctions screening, disputes, or other legal obligations. Any invoice processor or subprocessor must be identified before payment is requested.

Invoice privacy

Invoice pages must use a high-entropy private link, no public index, no analytics, and private no-store caching. They must not place a provider name, email, wallet address, or transaction hash in a public URL. No public checkout is enabled until the merchant, custody, supported asset and network, tax, retention, and refund controls are approved.

Contact

For privacy requests, contact [email protected].