Beta Privacy Policy
Last Updated: August 22, 2026
1. Introduction
TokenPager ("we", "our", or "us") is committed to protecting your privacy. This Privacy Policy explains how we collect, use, disclose, and safeguard your information when you use our digital customer pager platform.
2. Information We Collect
For Business Users (Workspace Administrators):
- Email Address: Required for account creation, workspace administration, and authentication.
- Business Details: Business name and workspace customization settings.
For Queue Customers (Guests):
- Pager Identifiers: Token number entered to connect to a pager. No phone numbers, emails, or name registration is required for guests.
- Notification Tokens: Device web push notification tokens, if permission is granted, to trigger ready notifications.
Automatically Collected:
- IP address and browser/device metadata required to establish real-time Server-Sent Events (SSE) connections.
- Local Storage variables used to store your active pager token locally on your device.
3. How We Use Your Information
- To establish, maintain, and optimize real-time customer paging alerts.
- To authenticate workspace owners securely.
- To track performance logs, crash exceptions and errors during the beta testing phase.
- To respond to support requests and compile user feedback.
- To comply with regulatory and legal audit obligations.
4. Third-Party Services
We integrate secure infrastructure partners to run and analyze our beta application:
- Supabase: For cloud data hosting and user account authentication. Data is encrypted in transit and at rest. Privacy Policy
- PostHog & Sentry: Used for exception reporting, performance metrics, and anonymous telemetry. PostHog Privacy | Sentry Privacy
- Google (FCM) & Apple (APNs): Deliver device-level push notification payloads.
5. Data Storage and Security
Your data is stored securely using Supabase infrastructure hosted within the European Union (EU). We implement standard security measures, including HTTPS encryption in transit, physical storage drive encryption at rest on the hosting servers, and secure passwordless authentication. Note that alert/pager messages are stored in cleartext in the database for operational routing purposes, and workspace administrators are instructed to never input sensitive customer details (such as names or phone numbers) in pager messages.
6. Push Notifications
With your explicit permission, we send push notifications to deliver pager messages. These notifications are essential for the core functionality of our service. Customers can disable push notifications at any time through their browser or device settings.
7. Data Retention
We retain your personal data only as long as required. Business account data is stored for the duration of the beta testing workspace lifecycle. Customer pager messages, logs and connection metadata are automatically and permanently purged after **24 hours**.
8. Children's Privacy
Our service is not directed to children under 16. We do not knowingly collect metadata from minors. If you believe a minor has accessed the pager system, please notify us via our contact page to request a purge of the connection log.