TIDE Shadow-first BTC treasury policy cockpit
Back to site

Privacy

Privacy notice

TIDE uses a minimal data posture during public alpha. This page explains what is collected on the landing site and app surfaces.

1. What we collect

  • Basic site analytics and product events needed to understand usage and failure states.
  • Wallet-related metadata needed to operate wallet-bound features if you connect a wallet.

2. What we do not intend to collect for analytics

TIDE strips or avoids scenario names, full URLs with query strings, and user-entered treasury values from analytics events used for product measurement. Simulation data that remains local to your browser is not treated as a submitted lead by default.

3. Contact data

The public hackathon build does not ship a contact intake form. If you contact TIDE by email, the message is handled only for follow-up and deleted on request.

Data-subject rights: to access, correct, export, or delete your message, email privacy@tidesui.pro. We respond within 30 days.

4. Browser storage

TIDE stores local draft and simulation state in the browser so Shadow Mode can work without a wallet. Those local artifacts are part of product function, not a public analytics feed.

5. On-chain proof bundles

When you mint a testnet proof receipt, TIDE builds a content-addressed proof bundle that includes the policy object id, policy version, selected rail, policy owner address, and the USD-denominated thresholds that drove the run. The content digest is anchored on Sui testnet. Public proof pages may show a redacted summary, but when Walrus publishing is configured the canonical bundle is publicly fetchable by blob id through Walrus testnet infrastructure. If publishing falls back to a tide-stub:// URI, no public Walrus bytes are available for that receipt; the on-chain digest remains the verification anchor.

Nothing you type into Shadow Mode, scenario names, email addresses, or contact metadata is intentionally included in the bundle. Policy owner addresses, selected rails, policy versions, and numeric thresholds are public proof data once a receipt is anchored or a Walrus bundle is published, so keep policy fields strictly numeric and do not place sensitive text in any policy-related field.

6. Contact

For privacy questions, data-subject access requests, or deletion requests, email privacy@tidesui.pro. General questions can go to hi@tidesui.pro.