Privacy policy

Information we collect and why

Organizer accounts contain an email address, optional name, authentication information, and plan and billing references. Email/password accounts store a password hash. Google or Microsoft sign-in supplies account identity information. We use this information to provide account access and manage sheets, organizations, and purchases.

Participant signups collect a name, email, selected slot and quantity, and optional phone number and notes. Waitlists collect a name and email. We use these details to record commitments, send service emails, enable private signup management, and help organizers coordinate their events. Support emails contain the information you choose to send.

We also store event details, organization membership, uploaded images, and technical information needed to operate, secure, and troubleshoot the service.

Who can see signup information

Anyone with an unprotected shared sheet link can open it. Organizers can require a shared sheet password. Sheet passwords are stored as plain text so the organizer and authorized organization members can view and share them from Event settings. Successful entry remembers access in that browser for seven days. Organizers, authorized organization members, and participants using valid private management links retain their access. Protected calendar links grant access to one slot’s schedule and should be kept private. Changing the password revokes prior browser access and calendar links. Event titles may still appear in organization hubs, and image URLs shared separately are not password protected. Treat information you share with participants as information they can pass on.

Event organizers and authorized organization members can access participant details, including contact information and notes, and can export or print rosters. Hiding names from public view does not hide details from organizers. Organizers are responsible for their use of information and any copies they export.

Keep confirmation and management links private: anyone with a valid management link can manage that signup. Canceling a spot does not itself erase its stored record.

Service providers and external requests

We use hosting, database, storage, and email services, including AWS when configured, to operate Signup Giant. Stripe handles payment entry and billing; card entry takes place on Stripe-hosted pages. We store billing references and purchase status rather than full card details.

Google and Microsoft process sign-in when you choose those options. If enabled, Cloudflare Turnstile processes browser and network information for bot protection. Themed pages load fonts from Google Fonts, which receives the browser requests needed to serve those fonts.

If AI schedule parsing is configured, schedule prompts are sent to Google Gemini. When PostHog is also configured, prompts, generated responses, and usage diagnostics are recorded there. Avoid including sensitive or participant information in prompts; review generated schedules before publishing.

Cookies, analytics, and diagnostics

Signup Giant displays no banner ads or video popups. We use cookies for organizer sessions and authentication flows. When browser analytics is enabled, cookies or browser storage may also support usage measurement and conversion attribution.

When configured, PostHog product analytics, error reports, and operational logs help us understand usage and diagnose problems. Organizer activity may be associated with an account ID, email, optional name, and plan. Product events include signups, waitlist joins, cancellations, swaps, and checkout activity.

Optional browser PostHog and the production Google Ads tag measure visits and successful organizer actions, including registration, sheet creation, checkout, and purchases. Google processes information for advertising measurement and attribution. These tools may process browser and device information, campaign or click identifiers, and account or transaction identifiers. Browser analytics includes shared signup pages and excludes participant management links and password-reset pages. When enabled in PostHog, session replay records page layout, visible text, interactions, and ordinary form inputs on eligible pages. Password inputs are masked. Replay console logs and network capture are disabled. Automatic interaction event capture is disabled. Clicks on selected marketing-page buttons are recorded with a fixed button identifier only.

Pageviews are collected only through browser PostHog on eligible pages; the server does not collect pageviews. Private management links are excluded from pageview collection; their product events and error reports may still be processed.

Retention and requests about your data

Event records are not automatically erased when an event ends or a signup is canceled. To request access, correction, or deletion, email info@signupgiant.com with your account email or the relevant event address. Do not include private management tokens. We may need to verify your identity and coordinate with the event organizer.

Some records may need to be retained for billing, security, dispute handling, or legal obligations. Organizer exports and copies held by others are outside the website's deletion controls. Ask the organizer about their own retention and handling of participant information.

School and child information

The service is intended for adult organizers and parents or guardians coordinating events. Children should not submit personal information themselves. Avoid entering student records, health details, or other sensitive information in public sheets, signup notes, or AI prompts. Schools and organizations should assess their requirements before using the service.

If you believe a child has submitted personal information, contact info@signupgiant.com so we can review it.

Policy updates

We will publish revisions on this page with an updated date. For questions about the current policy or a change, email info@signupgiant.com.