Gatherwise helps event hosts organize attendee information and prepare for conversations. This notice explains how Gatherwise, operated by James Jackson Leach, handles information at gatherwise.app.
Information we handle
- Account information: your email address and sign-in records. If you use another available sign-in method, our authentication service also receives your phone number or the account identifier and basic profile information supplied by Google or X, such as your name, email address and profile image, depending on that provider and your authorization. Gatherwise does not receive your Google or X password.
- Workspace information: workspace and event names, dates, time zones, locations, descriptions and matching goals.
- Attendee information: names, email addresses, job roles, organizations and profile links imported by an event host, along with registration status, saved notes and shortlist choices. Attendees may be included in a host's workspace without creating a Gatherwise account.
- Evidence and questions: any supporting source records held in a workspace, including links, excerpts, candidate professional details and research status, and questions submitted to search those records. When Claude chat is enabled and you submit a question, Gatherwise sends your question, a bounded recent conversation and relevant saved information from the selected event to Anthropic to generate an answer. Imported attendee emails, phone numbers and private host notes are excluded from the automatically assembled context. Information you type into a question is sent as part of that question. Separately, when research is enabled, providers can retrieve and extract information from supplied public pages as described below. Research results are source or provider assertions, not verified identity or accomplishments. Where enabled, connected event services supply event and RSVP information to your workspace according to your connection and synchronization settings.
- Technical information: session cookies and request information needed to provide the website and sign-in service. Services that receive these requests may process IP addresses, browser information, timestamps and operational or delivery logs.
- AI usage information: internal account, workspace, event and request references, model, token counts, estimated cost, timestamps, broad question categories and completion status. We also record limited product-action metadata, such as event/list imports, confirmed research requests and whether a shortlist or note changed. These records support usage limits, reliability, product improvement and account-level reporting. Activity records contain no private note text. The usage ledger does not store question or answer text. Conversation history is held in the page rather than saved as a chat archive by Gatherwise. Switching events starts a new conversation.
- Billing information: payment references, payment status, plan and research-credit records needed to fulfill purchases, reconcile payments and provide support. Payment-card details are entered directly in Stripe's hosted checkout; Gatherwise does not receive your full card number or security code.
- Support messages: information you choose to send when asking for help, a correction or removal.
How we use information
We use this information to create and authenticate accounts, send requested sign-in messages, save event workspaces, organize attendees, apply the host's matching goals, display supporting evidence, respond to support requests and operate the service.
Gatherwise currently does not train its own model on customer conversations. Stored research and product analytics are used to operate and improve the service; any future training use would need a separate disclosed permission and data-rights process.
Imported attendee information is used within the importing workspace. Gatherwise does not publish a shared attendee directory or use these records to send marketing to attendees. The current release does not sell personal information, run advertising or collect payment-card information.
Access and service providers
Workspace records are available to authorized members of that workspace. Host notes and shortlists are associated with the individual user. These access controls do not prevent someone with access from copying information, so hosts should import only information they are authorized to use. The operator may access records when needed to operate the service or handle a support request.
The service uses:
- Supabase for authentication and the PostgreSQL database that stores account and workspace records.
- Render to host the application and process requests to it.
- Stripe processes payments and receives the billing and payment information you enter in its hosted checkout. Gatherwise sends Stripe the selected plan, event identifier where applicable and internal account/workspace references to assign a payment correctly. This billing integration does not send attendee lists or private notes to Stripe. Stripe handles payment information under its own privacy information.
- Resend to deliver requested email sign-in messages, including the recipient address and message content.
- Cloudflare for domain registration and DNS services.
- Google Fonts to load website fonts. Your browser makes requests to Google's font services when loading these fonts.
- Google or X, if you choose an enabled social sign-in method, to authenticate your account. Their consent screens describe the access requested. Gatherwise's sign-in integration does not read your Gmail messages or post to your social account.
- Apollo, when professional research is enabled, to look up candidate professional information using attendee identifiers supplied by the host, such as a professional profile link, a known email address, or a name and company. The returned profile and career details remain provider assertions requiring review.
- Anthropic, when Claude chat is enabled, receives the question, recent conversation and selected-event context described above. It generates answers from that context. Chat does not automatically run new attendee research or spend research credits. Model-generated answers may contain errors; review their supporting sources before relying on a claim about a person.
- Firecrawl, when supplied-page research is enabled, to receive a supplied public URL, retrieve its page content and process that content for structured extraction. This page extraction is separate from answering questions about stored workspace records.
These research connections use provider accounts operated by Gatherwise. Customer workspaces remain separate within Gatherwise, with research results available under the workspace access controls described above.
SMS sign-in is being prepared and is not enabled in this release. We will identify the SMS delivery provider here before enabling phone sign-in. Each provider handles information according to its own applicable terms and privacy notice. Information may be processed in countries other than your own, depending on the service involved.
Cookies
Gatherwise uses cookies to maintain and refresh your signed-in session and complete sign-in. Blocking these cookies can prevent account access. The current application does not include advertising trackers or a separate product-analytics service. Signing out ends the session in the current browser; it does not delete your account or event records.
Storage, corrections and removal
Account and workspace records persist in the current release. There is no automatic event-expiry or self-service account-deletion feature. Suppressing an attendee from matching is not the same as deleting that attendee's registration record.
To ask about your information, request a correction, or request deletion of an account or attendee record, email trygatherwise@gmail.com. Include the relevant account email or event and enough detail to locate the record. Do not send passwords or sign-in codes. Requests are reviewed manually; we may need to verify your identity or authority and coordinate with the event host. We will explain the action taken and any information that could not be removed. Provider logs and backup copies may have separate retention settings.
Changes and contact
We will update this notice as the service changes and show its effective date on this page. Questions about this notice can be sent to trygatherwise@gmail.com.