Privacy

Privacy notice

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

1. What we collect

• Basic site analytics and product events needed to understand usage and failure states.
• Request-access form details that you submit voluntarily.
• 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. Request-access submissions

When the request-access endpoint is active, form submissions (name, email, company, role, use case, and optional handle) are sent to TIDE intake systems for follow-up. If intake is unavailable, you may be asked to contact TIDE manually by email instead.

Retention: request-access submissions are kept for up to 180 days from the date of submission, then deleted. You can shorten this period on request.

Data-subject rights: to access, correct, export, or delete your submission, 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. Request-access fallback storage is kept out of persistent localStorage.

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 pinned on-chain; public proof pages show a redacted summary, while the canonical bundle remains private until durable publishing is enabled. Once real Walrus publishing replaces the current stub, the bundle itself will be publicly fetchable by digest.

Nothing you type into Shadow Mode, scenario names, email addresses, or contact metadata is included in the bundle. If you intentionally put anything sensitive into a policy field (for example as a label), it may become publicly readable once mainnet publishing is live — keep policy fields strictly numeric.

6. Contact

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