How do you use Post Secret Voicemail to tell or hear a secret?

Post Secret Voicemail is a web app at postsecretvoicemail.com with the tagline "Tell a secret, hear a secret." Based on the site's own page evidence, the only confirmed requirement is that you must enable JavaScript in your browser for the app to run — the page itself renders nothing but "You need to enable JavaScript to run this app." without it. The site's public page evidence does not document specific recording, submission, or playback steps, so treat the walkthrough below as the general pattern for this kind of voice-secret app rather than a confirmed menu-by-menu guide.

What the site actually tells you

The available page evidence is minimal:

Because the page is a JavaScript app, everything — the recording interface, the playback interface, any prompts — is generated after the script loads. That is why the raw page shows only the JavaScript notice.

Before you start

1. Use a modern browser (Chrome, Firefox, Safari, Edge) with JavaScript enabled. JavaScript is on by default in most browsers; if you use extensions like NoScript or a hardened privacy mode, allow scripts for this domain.
2. Decide whether you want to speak or listen. The tagline implies two separate actions, and the app likely presents them as separate entry points.
3. Check your microphone situation if you plan to record. Browser-based recording normally requires granting microphone permission through a prompt. If you deny it, recording will not work.
4. Assume anything you submit may be heard by strangers. The premise of the site is sharing secrets with an audience, so do not submit information you would not want public.

Telling a secret

The exact controls are not documented in the available source, but for a voice-based secret app the flow is typically:

1. Open postsecretvoicemail.com and wait for the app to load.
2. Choose the option to record or leave a secret.
3. Grant microphone access when the browser asks.
4. Record your message, then stop.
5. Review the recording if a playback option is offered, then submit.

Expected result: your recording is accepted by the app and, per the site's premise, becomes something other visitors can hear.

Common snags:

• Nothing appears on the page → JavaScript is blocked or the script failed to load; reload or check your extensions.
• No microphone prompt appears → the browser may have already blocked mic access for the site; reset the permission in site settings.
• Recording button does nothing → another app may be holding the microphone, or the connection dropped.

Hearing a secret

1. Open the site with JavaScript enabled.
2. Choose the option to listen or hear a secret.
3. Play whatever the app serves you.

Expected result: you hear an audio clip submitted by another user.

Common snags:

• Silence on playback → check your device volume and whether the tab is muted.
• Nothing to play → the app may depend on other people having submitted secrets first.

Limits and cautions to keep in mind

• JavaScript is mandatory. This is the one limitation the site itself states outright.
• No documented pricing. The available source lists no pricing signals, so do not assume the service is free — and equally, do not assume it costs anything. The source simply does not say.
• No documented account or login flow. Whether you need an account is not stated in the available evidence.
• Privacy is inherently limited. A site built around telling secrets to strangers should be treated as public by default. Avoid names, addresses, workplace details, or anything identifying.
• Content may be moderated or removed. Most secret-sharing services review submissions; the available source does not describe this, so treat it as unknown.
• Availability can change. A small web app can go offline or change behavior without notice.

Quick decision guide

• You want to leave a voice secret anonymously: open the site with JavaScript on, allow microphone access, record, submit.
• You want to listen: open the site with JavaScript on and use the listen option.
• You need guaranteed privacy or a documented retention policy: this site's public page does not provide that information, so look elsewhere or assume the least privacy-friendly case.
• The page shows only the JavaScript message: that is expected behavior, not a broken site — enable JavaScript and reload.