Every LaunchSure credential carries a valid-through date. People sometimes ask us to remove it — a badge that lasts forever feels like more value. It’s the opposite. A badge that never expires proves nothing.
Software changes; a snapshot doesn’t
A security review is a snapshot. It says: on this date, against this standard, this app passed. The moment you ship a new release, that snapshot is slightly out of date. Ship fifty releases and it may be meaningless.
If the badge never expired, a visitor in 2028 would have no way to tell whether the app was checked yesterday or three years and two rewrites ago. The mark would look identical either way — and that’s exactly how trust marks lose their meaning.
The date does the honest work
Our seals print the date the app was last checked, right on the face of the credential:
- Issued — when the review passed.
- Valid through — twelve months later, by default.
Anyone can read those two dates in one click at the public verify page and decide for themselves whether the check is recent enough to rely on.
Keeping it current
Re-certifying is deliberately easy. We re-run the check, and if it still passes, we issue a fresh date. On the Assured tier this happens automatically on every release — the badge renews itself the moment a passing build lands, so your valid-through date is always recent.
An expiry date isn’t a catch. It’s the mechanism that keeps the whole thing honest.
Want proof your app is safe to ship?
Check my app