Clarity about your information.
Understand what information is used, why it is needed, and who to contact about your rights.
Last reviewed: 25 October 2026
Who is responsible
AurumPass is provided by Top Prestige Technologies LLC. For platform enquiries, account administration and our own service-security records, the provider determines how information is used.
For an event’s guest list, registration questions, invitations and attendance records, the event organizer generally determines the purpose and use of the information. AurumPass processes that information to provide the organizer’s service, subject to the applicable agreement. Your invitation and the organizer’s event notice identify the relevant event contact.
Information used
- Enquiries: name, work email, company, optional role and phone, meeting preferences and any notes you choose to provide.
- Accounts: business contact details, user roles, authentication records, subscription status and onboarding information. A demo enquiry may create a pending business workspace and inactive administrator record; it does not itself activate access or start paid billing.
- Events: guest details, registration answers, party or seating information where collected, credential identifiers, payment status and attendance scans with their time and station.
- Service protection: technical request information, rate-limit records and operational logs. The hosting environment and enabled integrations may process additional technical identifiers.
Purposes and legal grounds
We use platform information to answer enquiries, prepare demos, administer accounts, provide agreed services, maintain security and meet applicable legal obligations. Where GDPR applies, the relevant grounds may include steps requested before a contract, performance of a contract, legitimate interests in secure service operation, legal obligations, or consent for a specific optional activity.
The applicable ground depends on the activity and relationship; consent is not a blanket condition for necessary service processing. Event organizers must determine and explain the grounds for their event’s processing, including optional marketing or sensitive registration questions.
Provide only information relevant to the enquiry or event. Do not include sensitive personal information in general enquiry notes. Where an event needs accessibility, dietary or similar information, ask its organizer how that information will be protected and used.
Providers and international processing
Access is limited to authorized people and service providers supporting the relevant activity. Depending on configuration, these may include hosting and database providers, email delivery, payment processing, CAPTCHA verification, wallet services and organizer-enabled integrations.
Stripe may handle checkout and payment information when enabled. Google reCAPTCHA or hCaptcha may process verification signals when configured. The specific providers, hosting locations and processing countries must be confirmed for the customer’s deployment.
Where processing crosses borders and applicable law requires safeguards, the provider and organizer must establish an appropriate transfer mechanism and contractual protections. A particular hosting region, data-residency guarantee or transfer certification should be relied on only when confirmed in the service agreement.
Retention and deletion
Information should be retained for the purpose for which it is needed, including relevant contractual, security, accounting and legal requirements. The applicable event retention period is set by the organizer and the service agreement. Platform enquiries, inactive accounts, operational logs, backups and event records may require different periods.
The application does not establish a universal automatic deletion schedule for all these records. Ask for the schedule applicable to your deployment. Deletion requests must account for legal holds, required financial records, authorized backup cycles and the organizer’s instructions.
Offline scanner submissions have a limited replay window of up to 12 hours. This technical window is not a retention period for the organizer’s attendance records or a guarantee that every browser record is automatically erased after 12 hours.
Your choices and rights
Depending on the law and processing involved, you may have rights to access, correct, erase, restrict or receive a portable copy of your information, and to object to certain processing. Where processing relies on consent, you may withdraw it without affecting the lawfulness of earlier processing.
Right to object: where applicable, you can object to processing based on legitimate interests and to direct marketing. Explain the processing you wish to challenge when contacting the relevant controller.
For event records, start with the event organizer. For platform enquiry or account records, contact the provider. Requests may require proportionate identity checks and are assessed under the applicable law; deletion is not an unconditional right. Where GDPR applies, requests are generally addressed within one month, subject to lawful exceptions and extensions.
You may also complain to the competent data-protection authority. For EU/EEA matters, this may be the authority where you live, work or believe an infringement occurred. UAE matters depend on the applicable federal or free-zone regime.
Protection and browser storage
Read our Security page for the controls implemented in the application and our Cookie & storage notice for session cookies, preferences and scanner storage. No system or document alone guarantees compliance with every law or protection against every threat.
Privacy contact and updates
Contact: privacy@aurumpass.com.
Include the event or account concerned and a brief description. Do not send passwords, station secrets, payment-card details or a complete guest list.
This notice describes the service generally. The event-specific notice, agreed provider schedule and applicable contract supply deployment-specific details. Material changes should be reflected in an updated notice and communicated where required.