Privacy Policy

Development draft · Updated 6 October 2026. This page describes the current implementation. The operator must complete its identity, contact, retention, and applicable privacy information before a public launch.

Account information

ackteev uses Clerk for account registration, sign-in, verification, and session management. Clerk handles your password and authentication credentials. ackteev uses your Clerk user identifier, display name, and primary email address to connect your account to your events and RSVPs.

Event and RSVP information

The application stores event details, organizer identifiers, RSVP names and email addresses, RSVP status, registration times, and check-in times in its PostgreSQL database. Published public events appear in Discover for signed-in users. An unlisted event is accessible to any signed-in person with its link.

What organizers see

An event’s organizer can see and export that event’s guest names, email addresses, RSVP statuses, and check-in times. Other guests cannot access the organizer guest list through the app. Share only the event and attendee information you intend to make available in this way.

QR tickets and camera access

QR tickets contain event and RSVP identifiers, a random ticket value, and a signature. They do not contain your name or email address. The optional organizer camera scanner decodes QR codes in the browser and sends the decoded ticket code to the server for check-in. Camera permission is requested only when the scanner is started; the application does not store camera recordings.

Sessions and service providers

Clerk processes authentication and security information. The database service stores event and RSVP records. The app also saves a local return path in browser session storage to bring you back to the correct event after account setup. The app does not store passwords in that session storage.

Development data and requests

Cancelling an RSVP changes its status; it does not delete the stored record. The preview does not yet provide a self-service data deletion screen or an automated retention schedule. Do not use real attendee data for development tests. Before launch, the operator must provide a contact and process for privacy and deletion requests.

See the Terms of Service for using the development preview.