← Use cases OnePeek for developers: share API keys, .env files and database credentials safely Secrets pasted into Slack, Jira or email end up in search indexes, exports and backups. A leaked key in a chat log is a common way in. OnePeek gives you a one-time link: the secret is encrypted in your browser, and the server only ever holds ciphertext.
The problem today Keys pasted in Slack or Teams are searchable by everyone in the channel, and kept by exports and integrations. .env files emailed to contractors stay in their inbox after the contract ends. Production credentials end up in tickets, screenshots and screen recordings.Examples A .env file for a new contractor Upload the file with one view and a recipient lock to their work email. They download it once.
Rotating a database password Send the new password with a 1-hour expiry and a viewing timer, so it isn’t left open on someone’s screen.
Getting a client’s cloud credentials Send a request link. The client pastes the key, it’s encrypted to your browser’s key, and it never sits in their email.
On-call handover Share the break-glass password with a time window (only during office hours) and an opened alert.
Playbooks Step by step, with the settings to use.
Share an API key with a teammate When: Setting up a service, rotating keys, pairing.
1 Paste the key into OnePeek (text). 2 Set Views to 1 and Expiry to 1 hour. 3 Add a 60-second viewing timer if they’ll copy it straight away. 4 Create the link and send it with Microsoft Teams, Slack or email. 5 When it shows as Opened in your dashboard, nobody else can use the link. Settings Views: 1 Expiry: 1 hour Viewing timer: 60s Turn off copying: no (they need to paste it)Collect credentials from a client When: Integrations, migrations, onboarding a customer.
1 Dashboard → Requests → New request. 2 Write what you need, e.g. “Read-only AWS access key for the billing account”. 3 Send the link to your client contact. 4 They paste the key. It’s encrypted to your private key in their browser. 5 Open it once, put it straight into your secret manager, and the answer is deleted. Settings Keep the request page open in the browser that created it, or save the private key link somewhere safeGood habits Don’t commit secrets to Git, even private repos. Use a secret manager for storage and OnePeek for handoffs. Don’t paste the OnePeek link into a public channel. Anyone with the full link can open it once.More use cases Everyday sharing Send a Wi-Fi password, a streaming login, an ID scan or bank details to family and friends without leaving them in your chats forever. HR teams Give new joiners their first passwords, collect bank details and ID documents, and send salary information without leaving it in inboxes. Support teams Send temporary passwords and collect account details from customers without leaving them in your helpdesk, chat transcripts or email threads. IT & MSPs Hand over devices, Wi-Fi, router and admin passwords to staff and clients with one-time links, QR codes and geofences. Finance & accounts Share bank account details, tax documents and statements with clients, auditors and vendors through links that open once.