← lastmsg.app

Privacy Policy

[ LAST UPDATED: 12 OCTOBER 2026 ]

LastMessage exists to carry a message once and then forget it. This page explains, plainly, what we hold while that happens — and for how long.

§ 1The short version

Your message is stored encrypted in transit, deleted 24 hours after the recipient opens it, and never used to profile, advertise to, or train anything on anyone. We keep the bare minimum needed to deliver a message and confirm it was read. We do not run analytics, trackers, or advertising on this site.

§ 2What we collect

Message content. The letter, voice note, photo, or video you send, plus your optional choices (signature, ambient sound, dedicated song, unlock PIN). Content lives only until the message purges — see § 3.

Recipient identifier. The phone number, Instagram handle, or email address you address a message to, so it can be delivered.

Sender contact (optional). If you ask to be notified when the message is opened, the phone number or email you leave for that receipt.

Payment record. We never see your card. Payments run entirely on Stripe's hosted checkout; we receive only a Stripe session reference and a confirmation that the $5.00 charge succeeded.

Technical logs. Standard server logs (time, IP address, request) kept briefly for security and debugging.

§ 3How long anything lasts

This is the heart of the service. A message is deleted — database row and stored media alike — 24 hours after the recipient opens it. Unopened messages stay sealed until they are read. Unpaid drafts are discarded within a day. Deletion is not a setting you manage; it is the default state of the system.

One honest footnote: deletion runs when the system next touches the message after expiry (for example, on a visit to its link). It is automatic, but not instantaneous to the second.

§ 4Third parties we rely on

Stripe — payment processing. Card data is entered on Stripe's pages and never reaches our servers.

Twilio — sends the SMS notification when you address a message to a phone number, and the read-receipt text if you left a contact.

Resend — sends the same notifications by email, when you choose email delivery.

Spotify — if a song is dedicated to a message, the recipient's page loads Spotify's embed player, which is served by Spotify under their own privacy policy. We search Spotify's catalog without identifying you to them.

Amazon Web Services — hosts our database and stores message media until it purges.

§ 5Security choices we made

Recipient links carry a long random token that cannot be guessed. Optional four-digit PINs are stored only as salted cryptographic hashes — we could not tell you the PIN even if asked. Media links are short-lived signatures, not permanent URLs. Recipient pages are never cached, indexed, or archived.

§ 6What we cannot prevent

Ephemeral is our promise about storage, not about people. A recipient can photograph their screen, forward a copy, or simply remember what they read. We cannot retract that, and no service honestly can. Send accordingly.

§ 7Your rights

Depending on where you live, you may have rights to access, correct, or delete personal data. Because messages delete themselves by design, most data is gone before a request could reach it — which is rather the point. For anything remaining (an identifier in a still-sealed message, a payment record), write to us and we will handle it promptly.

§ 8Children

LastMessage is not for anyone under 16. Please don't use it to contact anyone under 16 either.

§ 9Changes to this policy

If we change what we hold or why, this page changes with it, and the date above moves. Material changes get a notice on the site before they take effect.