Set how long registrant data is kept
Updated July 22, 2026
Choose a retention window for the personal data collected through your pages — or keep none on Venue at all.
What it’s for
Registrant data retention controls how long the personal data your pages collect (a registrant’s email and their form answers) is kept on Venue. It is a single, workspace-wide setting: it applies to every page in the workspace, and only workspace admins can change it. A daily backend job permanently deletes anything older than the window you pick.
Use it to match your own privacy policy or a legal requirement — keep data as long as you need it, or store none of it on Venue and rely on Livestorm as the system of record.
Open Settings → AI & privacy. Registrant data retention is the second card, below AI page generation.
Open the “Keep registrant data for” dropdown and pick a window: Unlimited (the default), 2 years, 1 year, 6 months, or 3 months. The change saves as soon as you pick.
Data older than the selected period is permanently deleted. To store no registrant personal data at all, choose “Don’t store on Venue” — only anonymized analytics counts are kept, and a warning explains what that means.
Good to know
- The setting is workspace-wide and admin-only: it applies to everyone, and members see it but can’t change it.
- Data older than the window (email and form answers) is deleted permanently by a daily job — this can’t be undone, so shorten the window deliberately.
- “Don’t store on Venue” keeps zero registrant personal data; only anonymized counts remain for analytics.
Related articles
- Control access and privacyPassword-protect the page, set its visibility, redirect after registration, and cap sign-ups.
- Create and revoke API keysIssue workspace keys to call the Venue API from your own code — then revoke them when you no longer need them.
- Add ad pixels and the consent bannerFire Meta, Google Ads, GA4, LinkedIn or GTM conversion pixels on every published page and hub — gated by a cookie-consent banner.
Still need help?
Ask AI for a docs-grounded answer, or talk to our team.
Was this article helpful?