Privacy policy

This policy explains what CommunitySignUp collects, why we collect it, who can see it, and what you can do about it. It applies to communitysignup.com and the emails we send about sign-up sheets.

Last updated: September 1, 2026.

Information we collect

• Accounts. Name, email, optional phone, a hashed password, language preference, and whether the email is confirmed. SSO sign-in (when configured) stores the provider account identifier needed to recognize you next time.
• Sheets and slots. Titles, descriptions, photos, addresses, layouts, reminder hours, attachments, and whether names are hidden on the public page.
• Participants. The name they typed, email and phone if the sheet asks for them, comments, waitlist rows, and which openings they claimed.
• People and groups. Contacts an organizer adds or imports, group membership, and a disconnect flag if the organizer removes someone from their list (that does not delete the person from the software).
• Messages. Threads you send to site admins, and organizer emails queued to people on their own list.
• Payments. If you upgrade, Stripe processes the card or wallet. We store Stripe customer and subscription identifiers, paid-through date, and billing interval. We do not store full card numbers.
• Technical logs. Time, path, status code, and similar diagnostics so we can fix the site. We do not use logs for advertising.

How we use it

We use this information to run the sheet you see, send confirmations and reminders, let organizers manage events, process Plus subscriptions, and keep the service secure. We do not sell personal information. We do not use participant data to train public AI models. We do not run third-party advertising pixels on public sheets.

Cookies and local storage

We store a session token in the browser so you stay signed in. We do not use advertising cookies. Language in the URL is the main way we remember which public language you asked for.

Who sees it

The public page shows what the organizer chose to publish. Names are omitted when the organizer hides them. Organizers see rosters for sheets they own. Platform administrators can access records needed to operate, restore, or investigate abuse. Stripe sees payment details required to charge you. Email is sent through the mail service configured for this host.

Email

We send transactional mail only: account verification, confirmations, scheduled reminders, organizer notices when someone signs up, group invites the organizer requested, and messages an organizer sends to people on their list. You can stop event mail with the manage link in a confirmation, or by asking the organizer to remove you from the roster or their people list.

Retention

Account and event data stay until the organizer deletes the sheet or the account is closed. Disconnected people remain hidden from that organizer’s list but are not erased from groups or past sign-ups. Backups and logs are kept only as long as needed to run the service.

Your choices

You can update your account, request deletion of an account you own, or ask an organizer to remove you from a roster. Residents of California and similar states have rights to know, delete, and opt out of a “sale” or “share” of personal information. We do not sell or share personal information for cross-context advertising. To exercise a privacy request, sign in and message the site admins, or write the operator published on this host.

Children

The service is not directed at children under 13. Organizers who collect information about minors are responsible for having a lawful basis, including parental consent where required.

Security and international access

Passwords are hashed. Payment cards are handled by Stripe. The site is served over HTTPS. No method of transmission is perfectly secure. If you access the service from outside the United States, you understand the data is processed on servers in the United States.

Changes

If this policy changes we will update this page and the date above. Continued use after an update means you accept the revised policy.