1. Two roles, one principle
Everlage processes personal data in two roles. For operator accounts (you and your team) we are the data controller. For guest data collected through your branded storefront, your organization is the controller and Everlage is the processor acting on your instructions. In both roles the principle is the same: data is collected for a purpose, not for resale.
This Privacy Policy also covers the Everlage mobile application for iOS and Android, including event operations, ticket scanning, offline check-in and Secure Sign-In where enabled. Everlage is provided by DLTS. For privacy questions or requests, contact contact@everlage.com or visit https://everlage.com/en/privacy-requests. Your organization controls its event and attendee information; Everlage processes that information on its instructions. Everlage separately handles information needed for its own account, security and service administration.
2. What we collect
Operator data: name, work email, role, login and billing records. Guest data (on your behalf): registration details you request through your forms, ticket and order records, check-in timestamps and communication logs. We do not sell personal data, and we never market to your guests.
Conference features may also process speaker biographies, photographs, presentation uploads and associated permissions. Account and website operations may record support requests, consent choices and security events. Private speaker contact details and uploaded presentations are not automatically published.
3. Why we process it
To run the service you bought: issuing tickets, validating QR codes at the door, sending reminders you configure, generating badges, producing your reports and preventing fraud and duplicate entry.
As organiser, you determine which attendee details and event communications you request and must provide the appropriate notices and permissions for that use. Where consent is required, use the available controls and honor the attendee’s choice; optional marketing consent is separate from messages necessary to deliver the requested event service. Everlage processes organiser-controlled event data on the organiser’s documented instructions under the applicable agreement.
3A. Mobile application: data, purposes and device permissions
When you use the mobile application, the features enabled for your account may process:
Account and workspace information, such as your name, work email, phone number where supplied, account identifier, organization, role and assigned permissions, to identify you and provide the tools you are authorized to use.
Ticket and check-in information, including ticket identifiers or QR payloads, event identifiers, scan outcomes and timestamps, to validate admission, detect duplicates and reconcile check-ins.
Device location, which may be precise depending on the permission you grant and the information available from your device, when you use the check-in workflow. A recent device location may be reused for a check-in. Location is attached to the check-in record and may be stored locally for later synchronization when offline. The mobile application requests foreground location access, not continuous background tracking.
An installation identifier, device name/model, operating system and app version, notification token, public security keys and device/app integrity proofs, to enroll and identify trusted devices, protect sessions, prevent misuse and deliver enabled security or operational notifications.
Images you deliberately select and upload, namely your business's app logo, site logo or favicon (JPEG, PNG or WebP, up to 1 MB per image), to perform the administrative action you requested.
Camera access is used to read ticket and connection/sign-in QR codes. The scanning workflow processes the decoded code; it does not upload camera video. Photo access is used when you choose an image for an available upload feature. The app does not request microphone access for QR scanning.
Device authentication, including Face ID, fingerprint or device passcode, is handled by the operating system. Everlage receives an authentication result or cryptographic proof; it does not receive your face image, fingerprint template or device passcode.
You can change device permissions in iOS or Android settings. Refusing or withdrawing a permission may prevent the related feature from working. Withdrawing a device permission does not by itself delete information previously submitted to the service. To request deletion, use the privacy request route at https://everlage.com/en/privacy-requests. An account-deletion option is also available in app settings where your app version supports it.
4. Where it lives
Data is stored on hardened cloud infrastructure with encryption in transit and at rest. Access inside Everlage is role-based and logged. We use service providers for functions such as hosting, email and notification delivery. See our Service Providers and Processing Scope notice for information about the services used.
4A. Mobile service providers and sharing
The mobile service uses Expo/EAS, provided by 650 Industries, Inc. (United States), for application delivery and updates, and Expo push services for notification routing. Push delivery also uses Apple Push Notification service, provided by Apple Inc. (United States), on iOS and Firebase Cloud Messaging, provided by Google LLC (United States), on Android. Everlage uses Firebase only for Cloud Messaging. These services process the identifiers, technical delivery information and notification payload needed to provide that function.
Authentication codes and service emails are delivered through Postmark. SMS authentication codes and service messages are currently delivered through 019. We may add or replace SMS delivery providers, including Twilio. Such a provider processes the recipient's phone number, message content (including an authentication code where applicable) and delivery information only when it is enabled for the relevant message route. Listing a possible provider does not mean it currently receives personal data.
Where device-integrity verification is enabled, Everlage processes public security keys and app/device integrity proofs to verify an authentic installation and protect account access. On iOS this can use Apple App Attest. Where enabled on Android, the implementation uses Android Key Attestation; any separately enabled integrity service applies only to the builds and flows configured to use it.
Where an organizer enables Apple Wallet or Google Wallet ticket delivery and you choose to save a ticket, the relevant Wallet flow processes the ticket identifier, event information, admission status and any holder details included on that pass. The relevant provider receives the information needed by that delivery or update flow. Enabled pass updates can reflect changes such as cancellation or revocation. Scanning a ticket displayed in a Wallet is a separate check-in operation. The Everlage staff application does not need access to the rest of your Wallet to scan that ticket's QR code.
Authorized people in your organization can access operational information according to their assigned permissions. We use service providers for the relevant hosting, delivery and security functions. The applicable provider arrangements must protect the personal information they process for us consistently with this policy. The configured primary application hosting region does not mean that every delivery, support or provider operation takes place in that same region.
4B. Offline storage on mobile devices
To support offline check-in, the app stores a minimized event validation list and encrypted check-in records on the device. The validation list contains ticket digests and status information rather than the raw guest directory. A pending check-in can include its ticket/QR reference, event, timestamp and location and is sent to the server when synchronization is available.
Prepared validation lists expire according to the server's retention limit or the event retention window. During normal operation, unsynchronized check-ins are retained for synchronization or review. Explicit device revocation, security erasure, clearing app data or uninstalling may delete local records before synchronization. Prepared validation lists expire within at most 48 hours of download, and may expire sooner. Do not assume that ordinary sign-out immediately deletes all pending operational records.
Synchronize pending check-ins before uninstalling the app or clearing its storage. Uninstalling the app does not request deletion of your server-side account.
5. Your guests' rights
Guests can request access, correction or deletion of their personal data. Requests arriving to Everlage are routed to the operator who controls that data, and we provide the tooling to honor them within statutory windows (GDPR and equivalent regimes where applicable).
6. Retention
Tenant-owned operational data and assets are scheduled for permanent deletion 30 days after the effective service-end date under the standard retention policy. For an unpaid expired trial, this begins at trial expiry. For a cancelled paid subscription, it begins at the end of the current paid billing period. Failed payments first follow the configured payment-recovery grace period; the 30-day period starts when service ends after that grace period.
For trial expiry and cancellation at the end of a paid subscription, daily reminders are sent during days 1–7 after service ends, and normal tenant and administrator access is restricted after day 7. For failed payment, normal access is restricted when the configured payment-recovery grace period ends; that is the effective service-end date and the start of the 30-day retention period, with no additional seven days of normal access. Authenticated payment, reactivation, export and support routes remain available during restriction. Warnings continue, including a delivered final warning with at least four days to respond before deletion may proceed. Applicable dates, configured variations and permitted holds are shown for the business. Successful payment or reactivation stops pending deletion where the applicable policy and state permit it; an authenticated owner acknowledgment records the deletion consequences when required. The displayed deletion date is planned: deletion may occur later where a required warning has not been delivered, a support or legal hold applies, or operational processing is delayed.
After permanent deletion, only minimum records needed for legal or operational purposes may remain, including financial/security/audit records and normalized business identity and trial history needed to prevent repeat free trials. Those retained records are not a backup of deleted event content. Backup copies age out under the applicable documented backup-retention cycle, whose duration is not asserted here. Restore procedures must retain deletion records and prevent a deleted tenant from being reintroduced into active service.
7. Contact
Privacy questions and data-subject requests: contact@everlage.com. We handle privacy inquiries and rights requests in accordance with applicable data-protection law, including the relevant response deadlines.
