Privacy Policy

1. Introduction

DCP (Delegated Custody Protocol) is a local-first, open-source vault system. Your privacy is fundamental to our design philosophy. This policy explains how DCP handles data.

Core principle: Your vault data never leaves your device in plaintext. We cannot access your private keys, credentials, or stored data.

2. Data Collection

What we collect:

• Nothing by default. DCP is local-first software that runs entirely on your device.
• Relay server (optional): If you use remote agents via our public relay server, we collect:
  • Connection metadata (IP address, connection timestamps)
  • Encrypted message payloads (we cannot decrypt these)
  • Rate limiting data (request counts per vault ID)

What we DO NOT collect: Private keys, passwords, vault contents, transaction details, personal information, or usage analytics.

3. Data Storage

Local storage:

• Vault data is encrypted with XChaCha20-Poly1305 and stored locally in a SQLite database on your device
• Master key is derived from your password using Argon2id (never stored)
• You control the vault file location and backup strategy

Relay server storage (if used):

• Encrypted messages are temporarily held in memory (max 5 minutes)
• Connection logs retained for 7 days for debugging and abuse prevention
• No vault contents are stored on the relay server

4. Third-Party Services

Public Relay Server (relay.dcp.1ly.store):

• Operated by 1ly.store for remote vault access
• End-to-end encrypted using HPKE (Hybrid Public Key Encryption)
• Cannot read your vault data (transport encryption only)
• You can self-host your own relay server to avoid third-party reliance

No other third parties: DCP does not use analytics services, crash reporting tools, or external APIs by default.

5. Data Sharing

We do not sell, rent, or share your data.

Your vault data stays on your device. When using the relay server, encrypted payloads are transmitted but remain end-to-end encrypted. We have no access to plaintext vault contents.

Legal obligations: If legally required, we can only provide relay server connection logs (IP addresses, timestamps). We cannot provide vault contents as we do not have access to them.

6. Your Rights

You have full control:

• Access: All your data is stored locally and accessible via DCP commands
• Export: Use dcp activity --export json to export audit logs
• Delete: Delete your vault file to permanently remove all data
• Portability: Vault file can be moved between devices
• Opt-out: Use local-only mode to avoid any relay server connection

7. Security Measures

Encryption standards:

• XChaCha20-Poly1305 for vault encryption (AEAD cipher)
• Argon2id for password-based key derivation (memory-hard, GPU-resistant)
• HPKE (RFC 9180) for relay transport encryption
• Ed25519 for wallet key generation (Solana, Ethereum, Base)

Security best practices:

• Use a strong, unique password for your vault
• Regularly backup your vault file to secure storage
• Keep your DCP software updated
• Review the open-source code for transparency

8. Contact

For privacy questions or concerns:

• Email: privacy@1ly.store
• GitHub: Open an issue
• Discord: Join our community

9. Changes to This Policy

We may update this privacy policy as DCP evolves. Changes will be posted on this page with an updated "Last updated" date. Significant changes will be announced via GitHub releases and Discord.