Skip to policy content
Signup Crew — Plan more. Do more. Together.
PrivacyTermsAccessibilitySecurity

Signup Crew policy information

Privacy Policy

How Signup Crew handles personal information and privacy requests.

Draft / Pending Legal ReviewNot yet effective

This draft is provided for review and is not a final or effective published policy.

Version
Draft 0.1
Effective date
Not yet effective
Last updated
September 6, 2026

1. Who we are

Just Walking Ventures, LLC, doing business as Signup Crew, provides an online service that helps organizations plan Events, manage Volunteer opportunities, accept RSVP registrations, communicate with participants, track attendance, and administer related customer accounts.

Signup Crew is an active Florida fictitious name registered with the Florida Department of State under registration G26000112669 on August 20, 2026. This registration is not presented as a trademark registration.

In this policy, Signup Crew, we, us, and our refer to Just Walking Ventures, LLC, doing business as Signup Crew. Questions or privacy requests may be sent to support@signupcrew.com.

2. Scope

This policy explains how Signup Crew handles information when:

  • a customer creates or uses a Signup Crew account;
  • an organization configures or administers Signup Crew;
  • a Volunteer signs up for an opportunity;
  • an RSVP participant registers for an Event;
  • a person receives communications sent through Signup Crew; or
  • someone contacts Signup Crew for support.

Organizations decide which Events to create and what appropriate Event information to request from their participants. Signup Crew processes that information to provide the service.

3. Information we handle

The information involved depends on how a person or organization uses Signup Crew. Not every Event or feature collects every category below.

Account and authentication information

We may handle:

  • name, email address, profile information, and account timestamps;
  • organization memberships, roles, invitations, and Event assignments;
  • authentication identity and sign-in provider information;
  • session and account-recovery information; and
  • multi-factor authentication status for accounts where it is used.

Supabase provides Signup Crew's authentication service. Password credentials are handled through Supabase authentication; Signup Crew's application database does not store plaintext passwords. Customers may also be able to use Google as an optional authentication provider.

Organization and customer information

We may handle:

  • organization name, public contact information, logo, and other branding;
  • organization settings, membership, roles, and permissions;
  • Event descriptions, schedules, locations, capacity, and configuration;
  • communication settings and templates;
  • subscription plan, billing cadence, subscription status, and related provider identifiers;
  • support notes and customer-service references; and
  • administrative, authorization, billing, lifecycle, and audit history.

Volunteer information

Organizations may use Signup Crew to collect or maintain Volunteer information such as:

  • name, email address, and optional phone number;
  • selected shifts or assignments;
  • appropriate answers to organizer-defined Event questions;
  • signup, cancellation, reassignment, and attendance information;
  • check-in and check-out history;
  • directory or profile information and organizer notes;
  • historical participation or service information; and
  • communication and delivery history.

Volunteers generally do not need a Signup Crew account to participate.

RSVP information

Organizations may use Signup Crew to collect or maintain RSVP information such as:

  • a primary registrant's name, email address, and optional phone number;
  • party size and guest names when an Event permits guests;
  • appropriate answers to organizer-defined Event questions;
  • registration, cancellation, confirmation, capacity, and waitlist state;
  • attendee check-in and check-out information; and
  • reminder, Event communication, and participation history.

RSVP participants generally do not need a Signup Crew account to register.

Billing information

Stripe provides hosted Checkout, subscription billing, payment processing, and the Customer Portal. Signup Crew may retain Stripe customer, Checkout, subscription, product, price, invoice, and event identifiers, together with a projection of subscription status and relevant billing dates.

Payment-card and payment-account entry occurs through Stripe-hosted interfaces. Signup Crew does not store full card numbers, CVV security codes, bank-account credentials, or reusable payment credentials.

Communications and support information

When Signup Crew sends or helps an organization send an email, we may store the subject, message content, sender, intended audience, recipient information, delivery status, provider identifiers, delivery attempts, bounces, complaints, suppressions, unsubscribe choices, and related history. Private attachments may also be stored when an organization uses an attachment feature.

We may store information a person provides when contacting support, including the message, relevant account or organization references, and actions taken to resolve the request. Please do not send passwords, full payment-card details, or other unnecessary sensitive information to support.

Technical and operational information

Signup Crew and its infrastructure providers may process technical information needed to operate and protect the service, such as session records, request headers, IP addresses, browser or device information, server and provider logs, error information, security events, and administrative audit records.

Signup Crew does not currently operate an analytics platform, advertising pixels, or marketing-tracking system.

4. How we use information

We use information to:

  • create and secure accounts;
  • provide organization, Event, Volunteer, and RSVP features;
  • process registrations, assignments, attendance, and reporting;
  • deliver service, Event, billing, security, lifecycle, and support messages;
  • process subscriptions and maintain billing status;
  • provide customer support;
  • enforce roles, permissions, entitlements, and organization boundaries;
  • prevent abuse, fraud, and unauthorized access;
  • maintain operational and audit records; and
  • comply with legal obligations and establish, exercise, or defend legal claims.

5. Organizations and participant information

Organizations decide what Events to offer, which appropriate questions to ask, how to use participant information for their Events, and which authorized team members receive access. Organizations are responsible for obtaining notices, authorizations, or consent required for their collection and use of participant information. They are also responsible for safeguarding participant information they download or export from Signup Crew.

Signup Crew uses Volunteer and RSVP information to provide registration, Volunteer management, attendance, communications, reporting, support, and related service functions. Communications may be sent by an organization or by Signup Crew on the organization's behalf. Signup Crew may separately send messages needed for security, service operation, support, or legal compliance.

6. How we share information

We disclose information only as reasonably needed to operate the service, support customers and participants, protect Signup Crew and others, or comply with law. Current service providers include:

  • Supabase, for database services, authentication, sessions, multi-factor authentication, and file storage;
  • Stripe, for hosted Checkout, subscription billing, the Customer Portal, and payment processing;
  • Resend, for transactional and organization communications;
  • Vercel, for application hosting, content delivery, functions, and related operational infrastructure; and
  • Google, when a person chooses Google as an optional authentication provider.

We may also disclose information when reasonably necessary to comply with law, respond to valid legal process, protect rights or safety, investigate misuse, or complete a business transaction subject to appropriate protections.

Production AI-assisted Help is not an active core-service feature. If Signup Crew later authorizes such a feature for Production, the providers, information flow, and this policy will be reviewed before activation.

7. No sale or behavioral advertising

Signup Crew does not sell personal information. Signup Crew also does not currently share personal information for cross-context behavioral advertising or similar targeted advertising purposes.

These statements reflect the current Service: Signup Crew has no advertising pixels, behavioral-advertising system, marketing tracking, or implemented analytics platform. We will review this policy before introducing materially different analytics, advertising, or other nonessential tracking practices.

8. Cookies and browser storage

Signup Crew currently uses cookies and limited browser storage for functions such as:

  • authenticating users and maintaining secure sessions;
  • carrying a short-lived, scoped invitation handoff through sign-in;
  • remembering a limited interface preference; and
  • displaying one-time feedback during an application workflow.

Signup Crew does not currently use advertising pixels, marketing tracking, or an implemented analytics platform. A cookie-consent banner is not planned for launch based on this implementation. We will revisit this approach before introducing analytics, advertising, or other nonessential tracking technology.

Blocking necessary cookies may prevent account or application features from working properly.

9. Communications, unsubscribe, and suppression

Recipients may unsubscribe from broad organization updates where that option is provided. Signup Crew also maintains suppression information to honor applicable unsubscribe requests and provider delivery restrictions. Unsubscribing from broad updates may not stop messages required to operate a registration or Event, address security or account issues, provide requested support, or meet legal obligations.

10. Retention, access expiration, and deletion

Access expiration occurs when an organization's paid or complimentary authorization reaches its actual end. Customer access ordinarily continues through that paid or otherwise authorized period. Access expiration starts Signup Crew's current organization lifecycle:

  • public signup and RSVP actions stop immediately at access expiration;
  • during days 1 through 14 after expiration, a public Event page may remain reachable or viewable, but it cannot accept signup, RSVP, check-in, or other participant actions;
  • internal organization users have read-only access during days 1 through 14;
  • after day 14, public Event pages become unavailable and remaining internal organization access is blocked until applicable reactivation;
  • normal operational organization-data deletion is scheduled 60 days after access expiration;
  • an exceptional, reasoned, and audited retention extension may extend that period, but never beyond day 90; and
  • an Organization Owner may request earlier permanent deletion through a verified process.

Operational deletion is irreversible. If an organization reactivates before deletion, access to retained data may be restored under the applicable lifecycle rules. Previously public Events are not automatically republished. Queued or scheduled communications stop after the authorized period and do not automatically resume.

Payment failure and payment suspension are different from access expiration. A failed renewal payment receives the accepted seven-day payment grace period. If the failure remains unresolved, commercial access may be payment-suspended. Payment suspension does not by itself start the 60-day organization-deletion lifecycle unless and until the paid or complimentary authorization actually expires under the accepted commercial rules.

Operational deletion may remove, as applicable, Events and schedules, Volunteer and RSVP operational data, attendance and check-in records, organization settings and memberships, organization communication content and history, application support notes tied to the organization, and files or attachments covered by the organization purge. It does not mean that every record in every system disappears on day 60.

Limited residual records may remain where reasonably necessary. Depending on their purpose, these may include unsubscribe or suppression records, provider receipts or delivery evidence, billing or accounting records, audit records, fraud or security records, legal or compliance records, and certain platform or customer-support communications. An ordinary email sent to support@signupcrew.com is not automatically deleted merely because an organization reaches its operational deletion date.

Retention periods for those residual categories, provider logs, and backups may vary according to their purpose and applicable requirements.

11. U.S. state privacy rights and requests

Depending on where a person lives, and subject to applicable law and exceptions, the person may have rights concerning personal information, such as the right to:

  • access certain personal information;
  • correct inaccurate personal information;
  • request deletion;
  • obtain a copy of personal information or use an applicable portability right;
  • exercise applicable opt-out rights; and
  • appeal a decision where applicable law provides an appeal right.

This section does not state that Signup Crew is subject to every U.S. state privacy statute or that every listed right applies in every circumstance.

Account holders, Volunteers, and RSVP participants may contact support@signupcrew.com with an access, correction, deletion, portability, opt-out, appeal, or other privacy-related request. Signup Crew may need to verify the requester's identity. When a request concerns Volunteer or RSVP information collected through an organization's Event, we may coordinate with that organization as appropriate.

Some information cannot always be immediately deleted because operational, legal, billing, security, audit, suppression, or shared-identity records may require separate handling. We will evaluate requests according to the person's relationship with Signup Crew, the organization involved, and applicable law.

12. Children and minors

Signup Crew is a general-audience business service and is not directed to children under 13. Signup Crew customer account holders must be at least 18 years old.

Organizations may use Signup Crew for activities involving minors. The organization is responsible for obtaining any required parent or guardian authorization, notice, or consent. Signup Crew does not currently provide a dedicated age, guardian, or parental-consent workflow.

Signup Crew does not claim COPPA, FERPA, HIPAA, or other specialized regulatory compliance merely because a customer might use the service in a setting where such laws could be relevant. Whether a particular organization's activities involving children trigger additional legal obligations depends on the facts and applicable law; this policy does not state categorically that COPPA or another law can never apply.

13. Sensitive information

Organizations and users should not enter unnecessary highly sensitive information into custom questions, notes, attachments, support messages, or other fields. Examples include Social Security numbers, passwords, payment-card or banking credentials, government identification numbers, and detailed medical records. Organizations should request only information that is reasonably necessary for Event administration.

14. Information security

Signup Crew uses administrative, technical, and organizational measures intended to protect information. No online service can promise absolute security. More information about currently implemented practices will be available in the Signup Crew Security Statement at the intended future URL https://signupcrew.com/security.

If Signup Crew determines that a security incident involving personal information requires notification, Signup Crew will notify affected individuals and/or applicable authorities as required by applicable law. This statement does not promise a universal notification deadline or create an incident- response guarantee beyond applicable legal requirements.

15. Policy changes

We may update this policy as the service, providers, or legal requirements change. When a change is material, Signup Crew will provide notice appropriate to the nature of the change and applicable law. The effective date and version will identify the policy then in force. We do not promise individualized notice for every typographical or immaterial revision.

16. Contact

Questions, privacy requests, or concerns may be sent to:

Just Walking Ventures, LLC, doing business as Signup Crew

Email: support@signupcrew.com

Questions or assistance? Email Signup Crew Support.

Signup Crew homeSupport