vesperREAL LIFE. NO ADDED FEES.

YOUR LIFE IS NOT INVENTORY

Privacy,
plainly.

Pre-launch privacy draft. Final operator, retention and rights details require review before bookings open.

This MVP has no advertising pixel, analytics script or marketing subscription. It does process the information needed to run ticketing. It does not claim that no personal data is collected.

What is used

Guest names and email addresses operate bookings, ticket delivery, support and check-in. Creator application and meeting information supports manual curation. Account email addresses and single-use sign-in tokens provide access. A necessary Vesper session cookie keeps forms and sign-in secure. Rate-limit keys are HMAC hashes of the request IP or email and are automatically purged after expiry.

Who receives it

Vesper administrators and the event’s own creator can access the attendee and order data needed to run that event. Stripe handles card collection and payment processing; Vesper does not store card numbers. IONOS hosts the service and sends configured email. Hosting and mail providers may keep their own operational logs.

Security and retention

Sign-in links expire after 15 minutes. Private ticket and order links are bearer credentials: do not share them publicly. Sensitive link payloads in the database are encrypted at rest with the Vesper application key. Operational records and payment references are retained for event support, accounting and legal obligations. The operator must publish a final retention schedule before launch; this build purges consumed login records and sent mail bodies on its scheduled worker.

Your choices

A ticket purchase is not consent to receive marketing. Contact nikita@nolongernetwork.com for access, correction, deletion requests or a privacy concern. Certain financial records may need to be retained by law. No automated data deletion or portability request system is claimed in this MVP.