Last updated: 2026-08-09

This page describes the data Triadive collects, how it is used, and the choices available to visitors. Triadive is an editorial reference site about OpenClaw; it does not require an account, does not run a forum, and does not maintain a mailing list at this time.

Data collected automatically

When you load a page on this site, the following may be recorded by third-party services:

  • Page URL and referrer — for traffic analytics.
  • Approximate geographic region (city or country level) — derived from IP by the analytics provider, not stored by Triadive.
  • Device class (desktop or mobile) and browser family — used for layout and rendering decisions.
  • Cookie or local-storage identifier — used to distinguish unique visits from repeat visits.

The analytics provider used is Google Analytics 4 (GA4). Triadive does not have access to the raw IP addresses GA4 collects, only to aggregated reports.

Advertising

Triadive displays ads served by Google AdSense. AdSense uses cookies to associate a session with ad targeting categories. Triadive does not select which categories are used; AdSense makes that determination based on the visitor's browsing context.

Third-party vendors, including Google, use cookies to serve ads based on a user's prior visits to this site or other sites. Google's use of advertising cookies enables it and its partners to serve ads based on the visit to Triadive and/or other sites on the internet.

The DART cookie. Google, as a third-party vendor, uses the DART cookie to serve ads on Triadive. Visitors may opt out of the use of the DART cookie by going to the Google Ad and Content Network privacy policy.

Visitors who do not want AdSense to use their browsing history for ad personalization can opt out at Google Ads Settings. Other ad-vendor opt-outs are available at www.aboutads.info.

Cookies in use

Triadive itself sets no first-party cookies. Cookies and local storage identifiers may be set by:

  • Google Analytics (analytics)
  • Google AdSense (advertising)

Data triadive does not collect

Triadive does not collect:

  • Names, email addresses, or any contact information from visitors.
  • Account credentials (because there are no accounts).
  • Payment information (because there are no paid offerings).
  • Any content submitted by visitors (because there are no submissions).

The contact form on this site is a plain mailto: link; it opens the visitor's mail client rather than routing through a web form.

Third-party services

A current list of the third-party services that may load on Triadive pages:

  • Google Analytics 4 — analytics
  • Google AdSense — advertising
  • The OpenClaw documentation site, when an article links to it — outbound link only, no embedded content

Each of those services has its own privacy policy. Triadive is not responsible for the data practices of third-party services.

Do Not Track

The site honors the "Do Not Track" browser signal where the browser makes it available. When the browser sends a DNT header, the analytics provider does not associate the visit with ad targeting categories. The DNT signal is the user's way of telling the site that the user does not want to be tracked; the DNT signal is the user's way of controlling the analytics.

Data retention

The analytics provider's data retention is governed by the analytics provider's privacy policy. Triadive's local archive (email correspondence, etc.) is retained for as long as the editorial team needs it for reference, and the local archive is deleted at the sender's request. The local archive is not sold to third parties; the local archive is not shared with third parties; the local archive is not used for advertising.

Data location

The site's content is hosted on a CDN. The CDN's servers are located in the United States, the European Union, and the Asia Pacific region. The CDN's servers are the location of the site's content; the CDN's servers are not the location of the data the analytics provider collects. The analytics provider's data location is governed by the analytics provider's privacy policy.

Children's privacy

Triadive is not directed at children under 13 and does not knowingly collect information from anyone in that age range.

Changes to this policy

Material changes to this policy will be reflected by an updated "Last updated" date at the top of this page. Continued use of the site after a change indicates acceptance of the updated policy.

Contact

For questions about this policy, email [email protected] or see the contact page.

About Triadive

Triadive was launched in 2024 as a field manual for the human / agent / robot triad.

Editorial leadership credentials: Triadive Editorial Desk — operators with experience in long-running AI systems, agent runtimes, content production pipelines, and trading automation. The editorial team includes one peer reviewer per piece before publication.

Editorial process: every article is reviewed against current operational data (cron logs, build scripts, deployment records) and primary sources before publication. Pieces are written in Markdown and reviewed by at least one other operator before being committed to the deployed artifact.

Corrections: if you spot an error, email [email protected] — we typically respond within 48 hours and post a dated correction note for any substantive change.

Disclosure: Triadive is editorially independent; we have no sponsored content relationships and no undisclosed commercial affiliations. Content is published under a single editorial byline, and the editorial voice is meant to be plain, deliberate, and respectful of the reader's time.

About this manual

Editor: Triadive Editorial Desk. The desk is staffed by operators with experience tracking agent cognition, long-running agents, and tool-chain design across OpenClaw and adjacent agent runtimes, with bylines in operational newsletters and primary-source research notes.

Launched: Triadive went live in as a field manual for the human / agent / robot triad — the operating environment that has formed around long-running AI systems.

Editorial process: Each piece distils primary research (operator logs, build scripts, deployment records, peer review) into the worked-example frame: question, method, finding, what to do this week. Articles are screened against current operational data and reviewed by at least one other operator before publication.

Corrections policy: When a piece gets a fact wrong, we correct it inline and append a dated correction note at the top of the next dispatch. Send corrections to the editor — we typically respond within 48 hours.

Disclosure: Triadive publishes operator research notes and pattern analysis — not financial, investment, or legal advice. Nothing here is a recommendation to buy, sell, or hold any asset or tool, and no trading signals, price calls, or buy/sell timing are ever issued by the desk.