Your privacy, explained.

01Browsing E-ticket

E-ticket by Entertainment Daily lets you browse public event information and explore ticket options without an account. Registered users can access customer and organiser workspaces. Eligible organizer events support checkout in the payment mode shown before you pay. Test transactions collect no real money. Newly verified test bookings provide labelled tickets for testing scanning and check-in. Reference listings cannot be booked through E-ticket.

Selecting tickets does not create an order. When you continue to eligible checkout, E-ticket associates the reservation with your account and shares your email address, amount, currency and transaction reference with Paystack to process the payment. Payment details are entered on Paystack’s hosted checkout, not in E-ticket’s forms.

02Creating and using an account

Registration asks for your full name, email address, country, phone number, password and whether you want to explore or host events. E-ticket uses these details to create your account, identify you when you sign in and maintain your account's contact and role information. Phone validation checks the number against the selected country; it does not send a text message or verify that you own the number.

Your password is sent over an encrypted connection and stored as a password hash, not as readable text. Account records also include an account identifier, creation and sign-in information, and whether your email address has been verified. Session records allow the service to recognise an authenticated account.

Your dashboard lets you view your own order and ticket records and update the available profile and security settings. These requests are associated with your signed-in account. Enabling the organiser workspace changes your account's role and does not create a separate identity or grant staff access.

The website and its account API run on Vercel. Account and session records are stored in a PostgreSQL database hosted by Neon. These providers process information needed to host the service and operate its database. Public browsing and ticket selection do not submit payment details. E-ticket stores booking amounts, processing fees, payment references, payment mode and verification status. It does not store full card numbers or card security codes.

Signing out ends the current session; it does not delete your account. Contact us if you want to ask about correcting or deleting account information. The response and any information that must be retained depend on the request and applicable law.

03Event drafts, publishing and guest records

When you save an event, E-ticket stores its title, description, category, venue, address, dates, timezone, currency and ticket options with your organiser account. Uploaded posters are checked and converted to a web image for storage. Draft event details and posters are available through your account. Published artwork, public event text and organiser display name are visible to everyone. If the organiser chooses venue disclosure after confirmed booking, the exact venue and address fields are shown only to eligible ticket holders and authorised event staff; the city remains public. Organisers should keep private location details out of public artwork and text.

An organiser can view order and issued-ticket records for their own events, including the customer's name, email address and phone number where provided. Customer dashboards show only that customer's records. Tickets are issued only after a verified payment or a confirmed free booking. Test records stay labelled; newly verified test bookings support admission testing without creating payout funds. No example purchases or attendees are generated.

Check-in submits the admission token entered or scanned by the organiser to validate an existing ticket and record its first check-in time. The form clears the submitted token after the attempt. Treat admission tokens as private credentials and do not place them in event descriptions, shared links or support messages. Cancellation preserves historical event, order and ticket records; it does not itself issue refunds or send notifications.

04Account and booking emails

The verification and password-reset pages show whether automated email delivery is available. If the service reports that email is unavailable, E-ticket does not claim to have sent a message. An account can remain unverified while delivery is unavailable.

When email delivery is enabled, eligible requests create a delivery record linked to the account. The email provider handles the recipient address and a verification or password-reset link to deliver the message. A request being accepted does not prove delivery to an inbox. Delivery records track attempts and status without retaining the full email body or the reset token.

E-ticket uses Resend to send transactional email from tickets@eticketng.com. Completed bookings and ticket upgrades create confirmation messages containing the event, ticket and payment details and a link to the signed-in dashboard. The delivery record retains the recipient address and confirmation content for consistent retries. Admission codes are available only in the account's ticket view and are not included in these emails. Resend processes message content and delivery status to provide this service.

Verification and reset links expire after one hour and cannot be reused after successful completion. Keep these links private. Resetting a password invalidates existing account sessions. An unverified account can use its dashboard and create organiser drafts, but email verification is required for publishing, cancelling published events and guest check-in.

05Searches and ticket selections

On the events page, your search text and selected filters may be included in the page address. When you review or edit a ticket selection, the event, selected show and ticket quantities may also be included. This lets the page display the same search or selection when the link is opened again. Dashboard searches and filters are also sent to the E-ticket API to retrieve records you are allowed to view.

The ticket selector does not add attendee or payment information to a URL. Search and selection URLs can still reveal what you searched for or which event and ticket options you are considering. Anyone you share the link with can see those details, and the address may remain in browser history or technical request logs.

06Technical information and cookies

E-ticket uses essential session and security cookies. The session cookie keeps you signed in; a separate CSRF cookie helps protect forms against requests made by another website. These are not advertising cookies. Blocking them can prevent registration, sign-in or other account forms from working.

The sign-in session normally uses a cookie that expires with your browser session. Choosing Remember me allows that session to last up to seven days. Signing out ends it sooner. The session cookie is protected from direct access by page scripts and is sent over secure connections in production.

The services that host and deliver the website may keep technical access logs. Depending on the hosting service, these can include an IP address, browser or device information, the time of a request, the page address requested and a referring page. Such logs support website operation, troubleshooting and security.

No analytics or advertising tools are installed on the current E-ticket website. The site does not use analytics cookies, advertising cookies or a marketing profile to personalise event listings. Your browser may cache website files to make repeat visits faster.

07Protecting account forms

Account registration, sign-in and email requests use Cloudflare Turnstile to help distinguish people from automated abuse. Cloudflare may process your IP address, browser and device characteristics, and information about the security interaction. The server validates the challenge result with Cloudflare before accepting a protected request.

E-ticket also limits repeated authentication attempts. Its rate-limit records use keyed identifiers derived from the client address and, for sign-in, the submitted email address, together with counters and expiry times. The rate-limit records do not store those addresses in readable form; separate hosting access logs may contain an IP address.

08Maps, sharing and other websites

Event details, ticket selection, selection review and the E-ticket blog stay on E-ticket. Source and reference links may open Entertainment Daily or another named website. Directions links open Google Maps. When you choose to visit another service, its privacy policy and settings apply there.

The share button uses your device's sharing options where available, or copies an event link to your clipboard. Downloading a calendar file gives you a file to import into a calendar of your choice. Any information subsequently handled by a sharing or calendar service is subject to that service's own practices.

09When you get in touch

The contact page includes an optional enquiry composer with fields for your name, email address, topic, event link and message. These fields prepare a draft in your browser. Completing them does not send a message or submit the information to an E-ticket support database.

Choosing Open email app passes the draft to your chosen email application. You decide whether to send it there. If you send it, Entertainment Daily receives the email and the information you include so it can handle your enquiry. Your email application and email provider also handle the message under their own practices.

Share the information needed to explain your question, such as an event link and a description of the issue. Do not send passwords, full payment-card details, security codes or identity documents in a general enquiry.

10Your choices and privacy questions

You can browse without creating an account, sign out when using a shared device, leave optional external links unopened, and decide whether to share a selection URL. Your browser's settings let you manage cookies, history, cached files and clipboard permissions. Deleting a cookie does not delete the corresponding account record.

If you have a privacy question or a request about information you have sent, use the contact page and describe the information or interaction concerned. Privacy rights and the steps needed to respond depend on the circumstances and applicable law. The date on this page identifies the current version; review it again as new E-ticket features become available.