Terms of Service & Privacy Policy

Last updated: 2025-12-01. Review these PoE terms and privacy notes before submitting a commitment.

Part 1: Terms of Service (PoE Terms)

1. Service Scope

Fideseal is provided as a production Proof-of-Existence service. A paid Service Level Agreement (SLA) will define uptime and support commitments for commercial use. While you are using the free tier, we provide no warranties about uptime, future availability, or legal sufficiency. Anchoring may be delayed, batched, or declined without prior notice.

Fideseal is not a qualified trust service provider and does not issue regulated qualified timestamps under eIDAS or similar regulations.

2. No Legal Advice

The Proof-of-Existence (PoE) receipts generated by this service provide technical evidence that a specific digital file existed at a specific time. This does not constitute legal advice. The legal admissibility of blockchain timestamps varies by jurisdiction. You are solely responsible for determining if this technical proof meets your legal requirements.

3. User Responsibilities

Only submit content that you have the right to hash and anchor. Do not upload illegal content or materials that would violate privacy, export, or professional secrecy obligations.

You are responsible for verifying every receipt and ensuring the resulting commitment matches the file you intend to protect before relying on it.

4. Changes to Terms

We may update these PoE terms by publishing a new version. Because we use content-addressing, the terms_hash will change with the text, cryptographically indicating which version of the terms you accepted at the moment of anchoring.

Part 2: Privacy Policy

1. Zero-Knowledge File Handling

We prioritize your privacy through a "Client-Side Hashing" architecture:

Your Files: The browser processes your original file bytes locally. We do not retain, inspect, upload, or reconstruct your documents. Your file never leaves your device.
What We Receive: The backend only receives the cryptographic fingerprint (commitment_hex), the raw file hash (raw_file_hash_hex), and the minimal metadata required to build a receipt (e.g., file type profile).
Your Responsibility: Because we do not store your file, if you lose the original file, the receipt becomes useless. We cannot recover it for you.

2. Authentication & Identity Data

You may use the service anonymously or signed in:

Anonymous Mode: No personal identity data is linked to the anchor.
Authenticated Mode (Google): If you sign in, we process your email address and internal ID (sub) solely to embed them into the receipt as the "Actor." This allows you to prove who requested the timestamp. We do not use this data for marketing or tracking.

3. Data Retention & Public Blockchain

Consent Logs: When you submit a commitment, we store a secure server log containing: your IP address, user-agent, the timestamp, and the fact that you accepted these terms. We retain these logs as long as required for security auditing and legal compliance.

Blockchain Immutability: We anchor a Merkle root derived from your commitment_hex and raw_file_hash_hex on a public blockchain (e.g., Base/Ethereum). The on-chain root is permanent and cannot be removed. The file-specific hashes live in your receipt and proofs, not directly on-chain.

Part 3: Technical Metadata

Hash this text with scripts/compute_terms_hash.js

Current Terms Hash:0x4d7101379330022dc3d40d87f48e37a42a509df7cd3ee1c4d1f7659e8186c8c0

Canon Profile:txt.v1.basic

The hash is computed over the canonical text above (excluding this metadata block).