Privacy Policy

Who is responsible for your information

RealEvents is operated by Parklife, Inc. (registration 6515416), 131 Continental Dr, Suite 305, Newark, DE 19713, United States ("Parklife"). Parklife decides how personal information in RealEvents is processed and is responsible for it, wherever you are: under South Africa’s Protection of Personal Information Act (POPIA) it is the responsible party, and under US state privacy laws it is the business. "We" below means Parklife.

The organiser of an event you register for is separately responsible for what they do with the information they receive about you (see the section on sharing with organisers). Privacy questions and requests go to privacy@real-events.com.

What we collect

We collect only what the service needs. In full:

• Account: your name, email address, whether the email is verified, an avatar if you upload one, and how you sign in. If you sign in with Google or Microsoft, we receive your name, email and profile picture from them; we never see your password there. A password you set with us is stored hashed. One-time sign-in codes are stored hashed and expire.
• Organiser: if you become an organiser, the organiser’s name, slug, logo, country and payment region, who is on the team and with what role, which version of the organiser terms you accepted and when, and, in the United States, the identifier of your connected Stripe account and its onboarding status.
• Registrations and orders: the events you register for, how many tickets, the ticket type and price, the amounts, currency and fees of a paid order, the payment provider’s reference numbers, and refund amounts. We never receive or store your card number; the payment provider does.
• Tickets: each ticket’s confirmation code and QR code, and when and by whom it was checked in.
• Responses and waiting lists: Maybe and Can’t-go responses, waiting-list entries and the offers made from them, and your replies to a reschedule.
• Registration forms: your answers to the questions an organiser attaches to an event, including any image you upload. Images are stored in a private store and served only to you, the organiser’s team and our staff.
• RealEventsAI: the messages you send to the assistant and its replies, kept as your one ongoing thread, including the actions you approved.
• Reports and support: reports you file about an event and the details you give, the messages you send through the contact page (your name, email address, the topic, the message, and your account if you were signed in) together with our replies and staff notes on them, and the emails you send us.
• Notifications: the notifications we send you inside RealEvents and your notification preferences.
• Technical: the IP address and browser used for each sign-in session, the IP address recorded against actions in our activity log, IP addresses and account identifiers in the rate-limit counters that stop abuse, delivery events for the emails we send, and, when you ask us to email you a sign-in code or a password-reset link, or send us a message through the contact page, signals from your browser that tell a person from an automated script.

Why we use it

• To run the service: create your account, register you for events, take payment, issue tickets, deliver them by email and to your wallet, admit you at the door, run waiting lists and process refunds.
• To tell you what you need to know: your tickets, a cancellation or reschedule, a waiting-list offer, a refund, and the sign-in codes themselves. These transactional emails cannot be switched off while you hold a ticket; other notifications follow your preferences.
• To keep the service safe: rate limiting, detecting fraud and abuse, investigating reports, and keeping an activity log of who did what.
• To support you: answering your emails and reading your RealEventsAI thread when you ask for help or when we are improving the assistant.
• To meet our legal obligations: keeping financial records of orders, payments, refunds and payouts, and responding to lawful requests.
• We do not use your information for advertising, we do not build profiles of you for marketing, and we do not sell it to anyone.

Sharing with organisers

When you register for an event, the organiser and their team see your name, your email address, your ticket details, your check-in status and your answers to their registration form. That is what registering means: the organiser needs to know who is coming. They can also export their guest list.

If you use Contact the host on an event page, your question is emailed to the organiser with your name and email address as the reply-to, so they can answer you directly; the organiser’s own address is never shown to you. A record that you asked is kept in the organiser’s activity log.

Organisers agree, in their organiser terms, to use that information only to run the event you registered for and not to add you to a mailing list or use it for marketing without a lawful basis of their own. What an organiser does with information they take out of RealEvents is their responsibility, and questions about it go to them, through Contact the host on their event page.

Other guests never see your name or email. Attendance shows as counts, not names.

Services that run RealEvents

We use these companies to run the service. Each receives only what its job needs, under a contract that limits it to that job:

• Vercel (hosting, scheduled jobs, file storage and bot detection): everything the service processes passes through Vercel’s servers; event images and avatars sit in a public store, registration-form images in a private one. Vercel BotID, with Kasada behind its deeper analysis, checks the browser signals above when you ask for a sign-in code or a password reset.
• Neon (database): stores all the data listed above.
• Resend (email): your email address and the content of the emails we send you, including tickets.
• Stripe (payments in the United States, and organisers’ connected accounts): your email address and the amount, currency and reference of each order; Stripe collects your card details on its own pages and holds organisers’ identity and bank details.
• Google Maps: when an event page shows a map or an organiser looks up a venue, Google receives the venue and your browser’s requests under Google’s own privacy policy.
• Apple Wallet and Google Wallet: only if you add a ticket to a wallet, the ticket details needed to build and update the pass.
• Anthropic, through Vercel’s AI Gateway: each RealEventsAI message and the recent thread it needs for context, to generate the reply. Anthropic does not use it to train its models.
• Google and Microsoft: only if you sign in with them, to confirm who you are.
• Slack: internal alerts to our staff about events, reports and payments, which may include the text of a report you filed.

Cookies

RealEvents sets only cookies the service needs to work, which is why there is no cookie banner:

• A session cookie that keeps you signed in.
• A cookie that remembers whether you collapsed the sidebar (staff portal only).
• A short-lived cookie that remembers which organiser you were joining while you sign in.
• We do not use analytics, advertising or tracking cookies, and we do not load third-party trackers.

Where your information goes

RealEvents is hosted in the United States, and the service providers above operate there and elsewhere. If you are in South Africa, your personal information leaves the country to be processed. POPIA allows that where the recipient is bound by a contract that protects the information to a standard like POPIA’s, which is what our contracts with these providers do, and where it is necessary to perform the contract with you, which delivering your tickets is.

How long we keep it

• Your account and its data: until you ask us to delete it.
• Orders, payments, refunds and payouts: kept as our financial record for as long as tax and accounting law requires, even after an account is deleted; they are then kept without your name where the law allows.
• Tickets and check-ins: for the life of the event’s record. Events are never deleted; a cancelled event stays reachable so tickets and calendar entries remain valid.
• Registration-form answers: until the organiser deletes them or you ask us to.
• RealEventsAI thread: kept as your one thread; "Start fresh" hides earlier messages from the assistant and from you but does not delete them.
• Activity log: kept, because it is the record of who did what.
• Contact messages: for a year after the conversation is closed, then deleted.
• Sign-in sessions: until they expire or you sign out. Rate-limit counters: about a day. One-time codes: minutes. An account whose email address was never verified: a week, after which it is deleted.

Your rights

You can ask us what personal information we hold about you, ask us to correct it, ask us to delete it, and object to a use of it. You can change your name and avatar yourself in your account settings. To exercise any other right, email privacy@real-events.com from the address on your account; we answer within a month and never charge for a reasonable request.

If you are in South Africa, these are your rights under POPIA, and if you are not satisfied with our answer you may complain to the Information Regulator (South Africa). Privacy requests go to privacy@real-events.com.

If you are in a US state with a privacy law that applies to you, you have the rights that law gives, which include knowing what we collect, deleting it, and not being treated differently for exercising a right. We do not sell or share personal information for advertising, so there is nothing to opt out of.

Deleting your account

There is no self-service delete yet. Email privacy@real-events.com and we delete your account, your registrations, responses, form answers, notifications and RealEventsAI thread. Orders, payments and refunds stay as a financial record, without your name where the law allows, and the activity log keeps its record of actions. An organiser you own cannot be deleted while it has events with guests; contact us and we will work it out with you.

Children

RealEvents is for people aged 18 and over. We do not knowingly collect personal information from anyone younger. A child attends an event on a ticket bought by a parent or guardian, on the guardian’s own account. If you believe a child has created an account, tell us at privacy@real-events.com and we will delete it.

Security

Everything travels over encrypted connections. Sign-in is by one-time codes that are stored hashed and expire, by trusted identity providers, or by passwords that are stored hashed. Card details never touch our systems. Access to personal information inside our team is limited to what a job needs, and staff actions on your behalf are logged as the staff member’s own. If a breach affects your personal information we will tell you and the regulator as the law requires.

Changes to this policy

When this policy changes we post the new version here with a new effective date, and for a change that affects how we use your information we tell you by email or a notice in the service.

Contact

Privacy requests and questions: privacy@real-events.com. General support: support@real-events.com, or the contact page  (opens in a new tab). Postal addresses for each company are in the first section.