← Scanenter home

Your trust matters

Privacy Policy

How information is used when you plan events, send tickets, and welcome guests with Scanenter.

Last updated 18 October 2026

Your data supports your event.

Google sign-in is optional. Connecting Gmail is a separate choice for sending tickets. Scanenter does not read your Gmail inbox, sell your personal information, or use Google user data for advertising.

1. About this policy

Scanenter is an event operations service for organizers and their teams. This policy covers our website and application, including event setup, attendee imports, ticket delivery, billing, and QR check-in.

For privacy questions, contact Scanenter at eventpro62@gmail.com. If an organizer uploaded your information, that organizer controls how it is used for their event. You may contact the organizer or ask us for help identifying the relevant workspace.

2. Information we handle

  • Account and team details: your name, email, profile image if provided, account identifier, workspace membership, and assigned permissions. Authentication is handled through our authentication provider.
  • Event and guest information: event details, uploaded artwork and guest lists, attendee names, email addresses, phone numbers when supplied, ticket identifiers, and check-in records.
  • Ticket delivery: the recipients, subject, message, generated PDF tickets, and send status needed to carry out an organizer's dispatch.
  • Billing: payment and order identifiers, event capacity, currency, amount, and payment status. Razorpay processes checkout details; Scanenter does not store full payment card numbers, CVVs, or UPI PINs.
  • Technical and support information: session cookies, local preferences, request and error logs, and information you provide when contacting support. Hosting providers may process IP addresses and browser information for delivery and security.

3. Google sign-in and Gmail access

Google sign-in: if you choose it, Google and our authentication provider supply account identity information such as your Google identifier, name, email address, and profile image when available. We use it to authenticate you and display your profile. Signing in does not by itself connect Gmail for ticket sending.

Optional Gmail connection: when you select Connect in Gmail Settings, we request openid, email, and https://www.googleapis.com/auth/gmail.send. These identify the mailbox you approve and let Scanenter send the ticket emails you initiate from that mailbox, with PDF attachments, to your event attendees.

We store the connected mailbox email and an OAuth refresh token server-side so you do not need to authorize every dispatch. Temporary access tokens are used to call Google. We do not ask for or store your Google password.

The Gmail connection does not request permission to read, search, or delete your inbox messages or access your Google Drive or contacts. Google processes outgoing email content and attachments to provide sending.

You can disconnect a Gmail slot in Settings and remove Scanenter's access from your Google Account connections.

4. How information is used

We use information to operate your account and workspace, create events and tickets, send authorized attendee emails, validate QR tickets, show event counts, verify payments, provide support, and prevent unauthorized access or abuse.

Organizers must have a lawful basis to upload attendee information and send event communications. Attendee data is used for the organizer's event operations, not sold as a marketing list.

5. Google API Limited Use

Scanenter's use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements, and the applicable Google Workspace user data policy.

Google user data is used only to provide the visible account and ticket-sending features you authorize. It is not sold, used for advertising, used for credit decisions, or used to train generalized AI or machine learning models.

Access or transfer is limited to providing those features with your consent, security investigations, legal obligations, or another exception permitted by Google's Limited Use rules. Human access to Google user data is limited to those permitted cases, including explicit consent for support or necessary security and legal handling.

6. Sharing and service providers

Your authorized workspace users can access event and attendee information according to their roles. Ticket recipients receive the ticket and message addressed to them.

Scanenter uses Supabase for authentication, database and file storage; Vercel for website hosting and server execution; Google for sign-in and optional Gmail sending; and Razorpay for payment processing. These services process the information needed for their functions under their applicable terms and privacy policies. Processing may occur outside your country.

We may disclose information when required by law or necessary to protect users and the service. Google user data remains subject to the additional Limited Use restrictions above.

7. Storage, retention and security

Account, event, attendee, and delivery records are retained to provide your workspace until removed through available controls or a verified deletion request. Gmail connection details remain until disconnected or removed. Records needed for legal, accounting, fraud prevention, or dispute purposes may need to be retained longer.

Deletion from active systems may not immediately remove copies in service-provider backups; backup retention follows the relevant provider's lifecycle. Copies of sent emails in a sender's or recipient's mailbox are controlled by that mailbox owner.

We use HTTPS, server-side credential handling, authentication, and workspace access controls to protect information. Please protect your account and give team members only the access they need.

8. Cookies and local storage

Scanenter uses cookies for sign-in sessions and OAuth security, and browser storage for authentication state and preferences such as the selected Settings section. Blocking essential storage may prevent sign-in or connected features from working.

The installed web app caches public icons and a generic offline screen. Its service worker does not cache attendee lists, account pages, ticket PDFs, authentication responses, or event API responses for offline use. Live event operations require an internet connection.

Scanenter does not currently use advertising cookies or third-party advertising trackers. Payment and identity providers may use their own storage when you interact with their services.

9. Your choices and deletion

You can edit available profile details, disconnect Gmail, revoke Google access, and use available event deletion controls. For access, correction, export, or deletion requests, email eventpro62@gmail.com from your registered email address. We may verify your identity and workspace authority before acting.

See Data Deletion for the steps and the distinction between revoking Google access and deleting Scanenter records. Attendees may ask their event organizer to correct or remove their information, or contact us for assistance.

10. Children, updates and contact

Scanenter organizer accounts are intended for adults authorized to run events. Organizers are responsible for obtaining any required permission before uploading information about children.

We update this policy when the service or our practices change and show the revision date above. Material changes to Google data use require appropriate notice and any additional consent required before that new use. Questions can be sent to eventpro62@gmail.com.

Questions about this page? Contact eventpro62@gmail.com.