Share Text

What is Share Text?

Share Text is a secure text sharing tool that encrypts your content before uploading it to our servers. The encryption key is stored in the URL hash (the part after #), which means it's never sent to the server. This provides end-to-end encryption where only recipients with the full URL can decrypt and view your content. The share automatically expires after your chosen time period and can be set to delete immediately after being viewed (burn-after-read).

How to Use Share Text

• 1. Paste or type your text in the input area
• 2. Select the programming language or format (for syntax highlighting)
• 3. Choose how long the share should remain available (1 hour to 30 days)
• 4. Optionally enable "Burn After Read" to delete after the first view
• 5. Click "Create Share" to generate a unique share link
• 6. Copy the full URL (including the key after #) and share it
• 7. Recipients open the URL and the text is automatically decrypted
• 8. Your text is deleted automatically when it expires or after reading (if burn-after-read enabled)

Security Features

• End-to-End Encryption: AES-256-GCM encryption ensures only authorized recipients can decrypt
• Client-Side Encryption: Text is encrypted in your browser before being sent to servers
• Key in URL Hash: The decryption key stays in the URL hash, never sent to our servers
• No Account Needed: Share instantly without signup or login
• Automatic Expiration: Shares expire after your chosen time period
• Burn-After-Read: Optionally delete shares immediately after the first view
• No Server-Side Access: We never have access to your decryption key or plaintext
• HTTPS Only: All communication uses secure HTTPS connections

Use Cases

• Share API Keys: Temporarily share credentials without risking exposure in chat
• Code Snippets: Share code samples that expire after project completion
• Configuration Files: Share sensitive config with team members with automatic expiration
• One-Time Links: Create temporary sharing links that delete after first view
• Password Distribution: Share temporary passwords that burn after reading
• Source Code: Quickly share source code snippets without public repositories
• Meeting Notes: Share temporary notes that auto-delete after meetings
• Debug Logs: Securely share error logs with support teams for troubleshooting

Encryption Details

Share Text uses AES-256-GCM (Advanced Encryption Standard with Galois/Counter Mode) for encryption. This is the same encryption standard used by governments and enterprises. GCM mode provides both encryption and authentication in a single algorithm, preventing tampering. Each share generates a unique encryption key using the Web Crypto API. The key is Base64-encoded and placed in the URL hash. The encrypted content is stored on our servers but cannot be decrypted without the key from the URL.

Supported Languages

• JavaScript / TypeScript: For web development code
• Python: For backend and scripting
• JSON: For data interchange formats
• HTML / CSS: For web markup and styling
• SQL: For database queries
• YAML: For configuration files
• Markdown: For documentation
• Bash: For shell scripts
• Plain Text: For raw text without highlighting

Privacy & Data Retention

• No User Tracking: We don't track who views your shares
• No Analytics: View count is stored only to show you when shares are accessed
• Automatic Deletion: Shares automatically delete when they expire
• Burn-After-Read: Immediately delete after first view if enabled
• Limited Server Storage: Encrypted content stored on Vercel KV (Redis)
• No Backups: Shares are not backed up after deletion
• No Data Sales: We never sell or share your data
• Compliance: GDPR and privacy law compliant

Expiration Options

• 1 Hour: Share quickly expiring temporary information
• 24 Hours: Default option for daily sharing needs
• 7 Days: Week-long access for longer projects
• 30 Days: Extended sharing for month-long access
• Custom: Set any duration between 1 hour and 30 days
• After expiration, the share is permanently deleted and cannot be recovered
• View count updates help you track if shares have been accessed

Best Practices

• Always use HTTPS links when sharing - never share via HTTP
• Include the full URL with the hash - the key is essential for decryption
• Set shorter expiration times for sensitive information
• Use burn-after-read for one-time passwords or critical credentials
• Avoid sharing PII (personally identifiable information) when possible
• Tell recipients to copy content before expiration
• Use different keys for different recipients (create multiple shares)
• Verify recipient receives the full URL including the hash fragment

Limitations & FAQ

• Q: What happens if I lose the URL? A: The share cannot be recovered. Save URLs in a secure place.
• Q: Can I edit a share after creating it? A: No, shares are immutable. Delete and create a new one.
• Q: How large can shares be? A: Currently up to 1MB of text content.
• Q: What if the recipient doesn't have the full URL? A: They cannot decrypt it - sharing the full URL is essential.
• Q: Can I see who viewed my share? A: Only the total view count is tracked, not individual viewers.
• Q: Are shares encrypted on the server? A: Yes, content stored on server is encrypted. Only encrypted data stored.
• Q: What if the service goes down? A: Shares would be inaccessible. Always save important content elsewhere.
• Q: Can I share the URL publicly? A: Yes, but anyone with the URL can decrypt it - the key is in the URL.