SecureShare Logo
SecureShare

Privacy Policy

Last Updated: August 1, 2026

1. Introduction

At SecureShare, your privacy is our primary concern. Because we use end-to-end encryption, we cannot see, read, or access the contents of the files you upload. This privacy policy explains what minimal data we do collect and how it is used.

2. The Data We DO NOT Collect

Due to our zero-knowledge architecture:

  • We do not have access to your private encryption keys.
  • We cannot decrypt or view your files.
  • We do not scan your files for content (because they are encrypted gibberish to us).

3. The Data We Do Collect

To provide our service, we collect the following metadata:

  • Account Information: Your email address, username, and profile picture provided by your OAuth provider (GitHub, Google) or entered manually.
  • Public Keys: We store your public RSA key so other users can encrypt files meant for you. Public keys are designed to be shared and contain no private information.
  • File Metadata: File name, file size, MIME type, upload timestamp, and the encrypted AES key (which we cannot decrypt).
  • Usage Logs: Standard web server logs including IP addresses, browser types, and access times for security and abuse prevention.

4. How We Use Your Data

We use the collected metadata solely to:

  • Provide, operate, and maintain the SecureShare service.
  • Facilitate the sharing of encrypted files between users.
  • Send email notifications when a file is shared with you.
  • Prevent abuse and maintain the security of the platform.

5. Data Retention

Files and their associated metadata are stored until you delete them or until their specified expiration date (for shared files). Account information is retained as long as your account is active.

6. Third-Party Services

We use the following third-party services:

  • Cloudinary: Used to store the encrypted file blobs. Cloudinary cannot read your files.
  • MongoDB Atlas: Used to store database metadata.
  • Resend: Used to send transactional emails (e.g., magic links, notification emails).
  • NextAuth: Used for secure authentication via Google and GitHub.

7. Contact Us

If you have any questions about this Privacy Policy, please contact us at contact@bilalkhan.online.