EntryBooth Privacy Policy

Effective Date: September 19, 2026

EntryBooth LLC, a Minnesota limited liability company ("EntryBooth," "we," "us," or "our"), provides event-management software, public event-entry forms, payment-related tools, and related services for equestrian organizations and event producers. This Privacy Policy explains how we collect, use, disclose, and protect personal information when you use EntryBooth websites, web applications, desktop applications, public entry forms, support services, and related services (collectively, the "Services").

This Privacy Policy applies both to organization administrators who create or manage EntryBooth accounts and to people who interact with public event forms or other public-facing parts of the Services.

1. Our role and the event organizer's role

EntryBooth processes personal information for more than one purpose.

For information associated with an EntryBooth organization account, our own subscription billing, service security, support, and operation of the EntryBooth platform, EntryBooth determines how and why that information is processed.

For information collected through an event organizer's public entry form, the event organizer generally determines what information to collect and why it is needed for the event. EntryBooth processes that information to provide the Services to the organizer. The organizer is responsible for its event rules, notices, waivers, consent requirements, refund policies, and legal obligations relating to the personal information it asks entrants to provide.

If your question or request concerns information you submitted to a particular event organizer, you may need to contact that organizer directly. We may refer a request to the organizer or assist the organizer in responding where appropriate.

2. Information we collect

The information we collect depends on how you use the Services.

A. Account and authentication information

When an organization administrator creates or uses an EntryBooth account, we may collect:

• email address;
• account and authentication identifiers;
• password-authentication information handled through our authentication provider;
• email-verification, password-reset, and session information;
• if you use Google sign-in, information made available through the Google authentication flow, such as your account identifier, email address, and basic profile information made available to the authentication service.

We do not receive your Google password.

B. Organization and event information

Organization administrators may provide or create information such as:

• organization name and timezone;
• event names, dates, schedules, classes, age groups, divisions, teams, and event settings;
• event-entry form configuration, pricing, discounts, limits, and availability settings;
• scoring, placings, times, draws, results, jackpot or sidepot configuration, and payout calculations;
• form logos, images, instructions, waivers, acknowledgements, and other organization-created content.

C. Entrant and form-submission information

Public event forms are configurable by the event organizer. Depending on how an organizer configures a form, EntryBooth may process information such as:

• rider or participant name;
• email address and phone number;
• age or age-group information;
• horse names;
• class and event selections;
• rider numbers, team names, and team membership information;
• drawn signatures;
• responses to custom text, number, date, selection, checkbox, or other form fields;
• information included in organizer-created waivers, acknowledgements, or instructions;
• submission status, payment status, and related event-registration records.

Some forms allow a person to register or pay for teammates or other participants. If you submit information about another person, you represent that you are authorized to provide that information to the organizer and EntryBooth for the event-related purposes described in the form and this Privacy Policy.

Where an organizer enables team-member lookup, limited information about existing entrants within that event, such as names, rider numbers, and horse names, may be displayed to a person completing a team registration so that the correct teammate can be selected.

D. Payment, subscription, payout, and transaction information

EntryBooth uses Stripe for EntryBooth subscription billing and for event-entry payment processing and financial-account functionality. We also plan to make PayPal available to event organizers as an alternative event-entry payment processor. PayPal is not an alternative payment method for EntryBooth subscription billing.

For EntryBooth subscriptions, we may receive and maintain information such as:

• Stripe customer, checkout, invoice, and subscription identifiers;
• selected plan;
• subscription status and billing period;
• payment status and limited payment-method metadata made available by Stripe.

For event-entry payments, organizations may use Stripe connected accounts and, where PayPal is made available, their PayPal accounts. In either case, the event organization is the merchant or seller responsible for the event-entry transaction. Depending on the payment processor used, we may receive and maintain information such as:

• Stripe connected-account identifiers and onboarding status;
• PayPal merchant-account or integration identifiers and account status made available to EntryBooth;
• payment, order, checkout, capture, refund, dispute, balance, and payout identifiers, as applicable;
• gross amounts, processor fees, refunds, net amounts, payment status, payout status, and transaction timestamps;
• masked or limited payout-destination information made available by the payment processor;
• account-health, verification, risk, or eligibility status made available by the payment processor.

Payment-card numbers, full bank-account numbers, and identity-verification documents requested within Stripe-hosted, Stripe-embedded, PayPal-hosted, or other processor-controlled interfaces are submitted to the applicable payment processor. EntryBooth does not use its own custom event-form fields to process payment-card numbers or full bank-account credentials.

E. Communications and support information

If you contact us or submit a support request, we may collect:

• your email address and, where available, name and organization;
• request category, subject, and message;
• app version;
• operating system or browser/platform information;
• current screen or route;
• relevant event name or event identifier;
• limited troubleshooting diagnostics supplied by the application.

EntryBooth is designed not to attach access tokens, passwords, secrets, arbitrary local-storage contents, or full request bodies to support requests.

F. Technical, security, and device information

When you use the Services, we or our service providers may process technical information needed to provide, secure, and troubleshoot the Services, such as:

• IP address and network information;
• browser, device, operating-system, and user-agent information;
• application version and route or screen information;
• security and rate-limiting signals;
• authentication-session and browser-storage information;
• error and crash information.

Our error-monitoring configuration is designed to avoid sending default personally identifiable information, cookies, HTTP request or response bodies, authentication headers, and sensitive query parameters to our error-monitoring provider. Error events may include pseudonymous account or organization identifiers and limited application context needed to diagnose problems.

3. How we use information

We use personal information to:

• create, authenticate, and secure accounts;
• provide the EntryBooth web, desktop, and public-form Services;
• store and process event registrations and organizer-configured form submissions;
• calculate entries, results, fees, refunds, balances, and payout-related information;
• process EntryBooth subscriptions through Stripe and facilitate event-entry payments through Stripe and, where available, PayPal;
• send account-verification, password-reset, event-confirmation, support, billing, and other service-related communications;
• send marketing or promotional communications about EntryBooth where permitted by law and consistent with your communication preferences;
• provide customer support and investigate reported problems;
• detect bots, abuse, fraud, security threats, and unauthorized activity;
• enforce rate limits and other security controls;
• maintain, debug, and improve the reliability and usability of the Services;
• comply with law, legal process, and valid governmental requests;
• establish, exercise, or defend legal claims;
• enforce our Terms of Service and protect the rights, safety, and property of EntryBooth, our customers, entrants, and others.

We do not sell personal information. We do not use personal information for cross-context behavioral advertising or targeted advertising based on activity across unrelated websites or services.

4. How we disclose information

We may disclose personal information in the following circumstances.

A. Event organizers

Information submitted through a public event form is made available to the organization that created or operates that event. The organization may use that information to administer entries, communicate with participants, determine eligibility, process refunds, create draws or teams, score events, publish results, and perform other event-related functions.

B. Service providers

We use service providers to operate the Services. Depending on your use of EntryBooth, these providers may include:

• Supabase for database, authentication, storage, and related backend services;
• Stripe for EntryBooth subscription billing, Stripe Connect, event-entry payment processing, refunds, disputes, balances, account onboarding, and payouts;
• PayPal, where offered as an event-payment option, for merchant-account connectivity, event-entry payment processing, refunds, disputes, and related payment functionality;
• Cloudflare for gateway, networking, abuse-prevention, rate-limiting, and Turnstile bot-detection services;
• Resend for transactional and service-related email delivery;
• Sentry for error monitoring and application diagnostics;
• Google when you choose Google as an authentication method.

These providers process information according to their own contractual and privacy obligations and, where applicable, on our instructions.

C. Legal, safety, and compliance disclosures

We may disclose information if we reasonably believe disclosure is necessary to comply with law or legal process; respond to lawful requests; protect the security or integrity of the Services; investigate fraud, abuse, or security incidents; or protect the rights, safety, or property of EntryBooth or others.

D. Business transfers

If EntryBooth is involved in a merger, acquisition, financing, reorganization, sale of assets, bankruptcy, or similar transaction, personal information may be disclosed or transferred as part of that transaction, subject to applicable law.

E. At your direction or with your consent

We may disclose information when you direct us to do so or otherwise provide consent.

5. Cloudflare Turnstile

EntryBooth public forms use Cloudflare Turnstile in invisible mode to help distinguish legitimate visitors from automated or abusive traffic.

Cloudflare states that Turnstile may process client-side signals such as an IP address, TLS fingerprint, user-agent information, the Turnstile sitekey, and the associated website origin for bot detection and security purposes. Turnstile may also use cookies or similar technologies that Cloudflare describes as strictly necessary for its security function.

Because EntryBooth uses Turnstile's invisible mode, this Privacy Policy expressly references Cloudflare's Turnstile Privacy Addendum, which provides additional information about Cloudflare's processing for Turnstile:

Cloudflare Turnstile Privacy Addendum

Cloudflare's broader privacy practices are described in its Privacy Policy:

Cloudflare Privacy Policy

6. Browser storage, cookies, and similar technologies

The Services use browser or application storage where needed for core functionality. For example, EntryBooth may use local storage or session storage to maintain authentication sessions, remember limited interface preferences, preserve a short-lived checkout-return state, or temporarily retain information needed to complete a public-form checkout flow.

Our service providers may use cookies or similar technologies that are necessary to provide authentication, payment, fraud-prevention, or security functionality. Cloudflare's Turnstile practices are described above.

EntryBooth does not currently use third-party advertising pixels for behavioral advertising.

7. Data retention

We retain personal information for as long as reasonably necessary for the purposes described in this Privacy Policy, including to provide the Services, maintain event and transaction records, comply with legal and accounting obligations, resolve disputes, prevent fraud or abuse, and enforce agreements.

Retention periods vary based on the type of information and the relationship involved. For example:

• account and organization information may be retained while an account is active and for a reasonable period afterward;
• event and entrant records may be retained on behalf of the organization that operates the event;
• payment, refund, payout, subscription, and accounting records may be retained for legal, tax, fraud-prevention, reconciliation, and financial-recordkeeping purposes;
• support and security records may be retained for troubleshooting, abuse prevention, and dispute resolution;
• service providers may retain information according to their own legal and contractual requirements.

When information is no longer reasonably necessary, we may delete, anonymize, or aggregate it, subject to legal, backup, security, and technical limitations.

8. Security

We use administrative, technical, and organizational measures designed to protect personal information. These include access controls, authentication, encryption in transit where supported, tenant-scoped authorization controls, server-side payment and security validation, restricted service credentials, and filtering of sensitive diagnostic information.

No method of transmission, storage, or security is completely secure. We therefore cannot guarantee absolute security.

9. Your choices and privacy rights

Depending on where you live and subject to applicable law, you may have rights to request access to, correction of, deletion of, or a copy of certain personal information, or to object to or restrict certain processing.

To make a privacy request concerning EntryBooth-controlled information, contact us at support@entrybooth.com. We may need to verify your identity before completing a request.

If your request concerns information collected by a particular event organizer through that organizer's EntryBooth form, the organizer may be the party responsible for responding to your request. You should contact the organizer directly where possible. If you contact EntryBooth, we may route the request to the organizer or assist the organizer in responding.

We may send marketing or promotional emails about EntryBooth in the future where permitted by law. You may opt out of those emails at any time by using the unsubscribe method included in the message. Opting out of marketing does not prevent us from sending transactional or service-related communications that are necessary to operate your account, process transactions, provide security notices, or otherwise provide the Services.

Because EntryBooth does not sell personal information or use it for cross-context behavioral advertising, we do not currently provide a sale or targeted-advertising opt-out for those activities.

10. Children and minors

EntryBooth organization accounts are intended for adults and other persons legally able to enter into a binding agreement on behalf of an organization.

The Services are not directed to children under 13 for the purpose of creating or managing an EntryBooth organization account. Event organizers may run youth events and may collect information about minor participants when a parent, guardian, or other authorized adult submits an event entry or otherwise provides the information as permitted by law.

Event organizers are responsible for determining whether parental consent, guardian authorization, or other special notice or consent is required for their event and form configuration.

If you believe personal information from a child under 13 was provided directly to EntryBooth without appropriate authorization or consent, contact us at support@entrybooth.com.

11. Information about other people

Some EntryBooth features allow an authorized user or entrant to submit information about another person, including teammates, riders, or event participants. Before providing another person's information, you are responsible for having authority to provide it and for giving any notices or obtaining any consents required by law.

Organizations should not use custom EntryBooth form fields to request full payment-card numbers, full bank-account credentials, account passwords, Social Security numbers, or other highly sensitive information unless collection is lawful, necessary, and specifically supported by an appropriate secure workflow.

12. U.S. availability and processing

EntryBooth currently offers organization accounts for use in the United States. EntryBooth and its service providers may process information in the United States and, depending on the provider and service, in other countries. Those countries may have data-protection laws that differ from the laws where you live. Where required by applicable law, we use appropriate mechanisms for international data transfers.

13. Changes to this Privacy Policy

We may update this Privacy Policy from time to time. When we make changes, we will update the Effective Date at the top of the policy. If a change is material and applicable law requires additional notice, we will provide notice through the Services, by email, or by another appropriate method.

14. Contact us

For privacy questions, requests, or concerns, contact:

EntryBooth LLC
Email: support@entrybooth.com
Website: https://entrybooth.com