1. What We Store

MyDataGit is designed so that the plaintext of your secrets and project files never reaches our servers. Encryption happens on your device. What we store server-side is limited to:

• Encrypted (ciphertext) content blobs.
• Wrapped cryptographic keys and related metadata.
• Content identifiers and hashes used for version control.
• Account, project, member, and device metadata required to operate the service.

We do not store your plaintext passwords, plaintext project files, plaintext Project Data Keys, private device keys, recovery-key mnemonics, or decrypted content.

2. What We Do Not Do

• We do not sell, rent, or share your personal data with third parties for advertising.
• We do not place your secrets in analytics, logs, or telemetry.
• We do not access your decrypted vault contents.

3. Device and Session Data

Authentication uses short-lived session credentials. Access and refresh tokens are handled according to our documented expiration and rotation rules. Refresh-token reuse is detected and revokes the token chain for security. Passwords are stored only as salted hashes; personal-access tokens are stored only as salted hashes.

4. Audit and Security Events

For protection, we record an immutable audit trail of security-sensitive actions — such as device approval, key rotation, member changes, and environment promotion. Audit entries never contain secret values, plaintext content, tokens, or private keys.

5. Encryption Details

Content is encrypted with AES-256-GCM authenticated encryption using a fresh 96-bit nonce for every operation. Content identity is derived via HMAC-SHA256 and versioned by Project Data Key generation. Device keys use X25519. Recovery uses a BIP-39 mnemonic. See our security documentation for full details.

6. Data Retention and Deletion

You may delete your account at any time. Historical encrypted versions are preserved in line with our version-control model until removed by you. We retain data only as needed to provide the service or comply with law.

7. Sub-processors and Infrastructure

We rely on Cloudflare (including D1 for metadata and Backblaze B2 for ciphertext object storage) to operate the service. These providers may process the encrypted and metadata content described above to provide the service.

8. Security

All client-server traffic is protected with TLS in transit. Backend storage is isolated behind our metadata and object store abstractions. We employ rate limiting, expiration controls, and server-side authorization checks on every mutating endpoint. Refer to our public security and threat-model documents.

9. Your Choices

You can export your project state, rotate recovery and project keys, revoke devices, and delete your account at any time from your settings. Because encryption is client-side, you are responsible for protecting your recovery key; losing it means the data is unrecoverable by anyone, including us.

10. Contact

For privacy questions, reach out through the support channels in our documentation.