🛡 TRUST CENTER

How we handle your truth.

The constitution sets our principles. This page is the mechanics — what we do, what we never do, and what your descendants can do without us.

The trust substrate

Your anchored moments are not protected by trust in SoulInTime. They are protected by the Bitcoin blockchain. Every anchor is a SHA-256 hash embedded in a Bitcoin block. As long as Bitcoin exists, your moments are verifiable — even if every server we run is destroyed.

What we store, where, and how

✓Content for moments marked private is encrypted at rest and only readable by you.
✓Only the SHA-256 hash is embedded on Bitcoin. Your actual content never touches the blockchain.
✓Media files (photos, videos, voice notes) are stored at separate storage URLs; we never embed media bytes on chain.
✓Heirloom Vault contents are only visible to designated heirs after the vault's release rules trigger.
✓Push subscriptions are stored per-device with VAPID encryption.

What we refuse, even when profitable

✕We will not sell your data. There is no data product.
✕We will not run ads. There is no ad surface.
✕We will not let you delete an anchored moment. Permanence is the contract.
✕We will not introduce engagement metrics (likes, follows, "trending"). Time orders the wall — nothing else.
✕We will not allow AI to author first-person moments on your behalf. AI witnesses. Humans author.
✕We will not pivot away from Bitcoin. The Timechain is the substrate, not a feature.

What happens if SoulInTime disappears

Every anchored moment can be verified without us. Visit mempool.space, your own Bitcoin node, or any block explorer. Submit the moment's SHA-256 or block height. The truth is on Bitcoin — independent of our company, our infrastructure, our existence.

If our domain expires, all current moments remain in the Bitcoin record. Your descendants will be able to verify them in 100 years using whatever Bitcoin tooling exists then.

Transparency commitments

✓Weekly digest of platform activity, anchored publicly: /digest
✓Weekly self-audit retrospective, anchored publicly: /evolution
✓Every shipped improvement is itself anchored as a public Evolution Moment.
✓Our marketing health audit is public-facing — its findings file improvement suggestions automatically.
✓Our AI crawler reach is tracked publicly per endpoint.

Reporting issues

Security disclosures, data concerns, or behavior inconsistent with the constitution — please reach out via /contact. We respond directly. We do not respond with PR.

If your concern is significant and we fail to address it, anchor a moment about it and send us the link. Your record will outlive any deflection.

Standards we adhere to

✓SHA-256 hashing (NIST FIPS 180-4).
✓OpenTimestamps for select anchor types (open protocol).
✓VAPID push notification keys (RFC 8292).
✓Schema.org structured data on public pages.
✓RSS 2.0 for the Memory Wall feed.
✓OpenAPI 3.0 spec for our public APIs: openapi.yaml
✓AI agent manifests: llms.txt, ai-plugin.json

The deeper version — anchored on-chain.

⚖️ Read the Constitution