Introduction

CredenShare is a secure credential sharing platform designed for teams that handle sensitive information — API keys, passwords, certificates, and other secrets that need to be transmitted safely.

Why CredenShare?

Traditional methods of sharing credentials — Slack messages, email, sticky notes — leave sensitive data exposed in chat histories, email archives, and insecure locations. CredenShare replaces that with encrypted, expiring links that you can also limit by view count and protect with a password.

Key Benefits

• Encrypted in the client — Credentials shared from the web, the REST API or an SDK are encrypted in the client with AES-256-GCM. The decryption key never reaches us, so we store ciphertext we cannot read. Credentials created through the Slack app are encrypted on our servers with AES-256 envelope encryption using a customer-managed key in AWS KMS. All traffic is TLS.
• Auto-expiring links — Set an expiration from 1 hour up to 3 months
• Optional view limits — Cap how many times a link can be accessed. Views are unlimited by default; a share ends at its expiration
• Access logging — Every access attempt is recorded with its timestamp, IP address, platform and user agent. How far back you can read it depends on your plan
• No SOC 2 attestation yet — see Compliance for what is and is not in place today

How It Works

1. Enter your credential — Paste the password, API key, or secret into CredenShare
2. Configure sharing options — In the app, set the expiration, a view limit, and optional password protection. Shares created from the homepage widget are fixed at a 24-hour expiry, a single view, and no password
3. Share the link — Send it over one channel you trust. The key that decrypts the credential travels in the link, so treat the link itself as the secret
4. Credential self-destructs — After the link expires, or reaches a view limit if you set one, the stored ciphertext is permanently deleted

Who Uses CredenShare?

• Development teams sharing API keys and database credentials
• IT administrators distributing passwords during onboarding
• Security teams handling sensitive access credentials
• Vendors and contractors receiving temporary access credentials