Privacy
notice

Information used to provide the service

Account services use your sign-in email, account identifier, verification and session information. If you choose Google, LinkedIn or another enabled sign-in provider, it supplies the information authorized during sign-in.

Profile information includes the name, town, biography, photo and business affiliations you choose to submit. Events, chapter participation, invitations, registrations, waitlist status, attendance records and support messages are stored as needed for those features.

Hosting and account-service providers also process technical requests, such as IP addresses, browser information and service logs, to operate and secure the website.

Automatic error reports

The site automatically records error categories, page templates, application release IDs, safe build-generated code locations and grouped occurrence counts to diagnose failures. Exception messages, form content, sign-in tokens, cookies and raw page URLs are excluded. Reports are stored privately in Supabase and new-issue alerts are emailed to the site team.

To limit misuse, a daily salted hash of the requesting network address is used for rate limiting. Raw addresses are not stored by this error-reporting feature. Rate-limit hashes are removed after two days; inactive error groups are removed after 90 days. Hosting providers may separately retain their service logs.

Who can see your information

New profiles start with public visibility selected. You can choose public, verified-members-only or private visibility before saving, and change it later in your profile privacy settings. Public profiles are visible without signing in and may be indexed by search engines. Members-only profiles are available to verified signed-in members. Private profiles are visible to their owners through normal profile access. Choose visibility in your profile settings.

Authorized organizers and event staff can access registration and attendance information for their events according to their roles. Authorized site staff can access records needed for support, moderation and administration. Private chapter information is restricted by chapter permissions.

Business affiliations are self-reported. Changing visibility limits future site access, but cannot recall copies already downloaded or cached elsewhere.

Service providers and outside links

The website uses Vercel for hosting and Supabase for account, database and storage services. These providers process information required to deliver their services. External login providers apply their own account policies when you use them.

Following an advertisement, business website or external registration link takes you to another service. The site’s advertising placement system does not provide advertisers with your private profile or attendee roster.

Questions and support

The Help and contact page answers from approved public help content. When AI assistance is enabled, your question and relevant help passages are sent to Anthropic (Claude) to find an answer. The assistant cannot access your account, orders or private profile. Do not enter passwords, card numbers, access codes or other personal details in the question box.

We retain daily counts of broad question topics, not the text of questions, for help-page improvements. A short-lived session cookie and hashed technical identifiers protect the service from abuse. If you choose to send a message to a person, we store your name, email, message, optional page address and any question and answer you attach. Authorized support staff can read these details and use your email address to respond.

Sessions and site functions

Sign-in uses cookies to maintain your session. Blocking them can prevent account features from working. An optional weekly networking planner covers upcoming events in your selected towns and is separate from new-event alerts. Manage or unsubscribe from either in email preferences. Your Privacy choices control optional event measurement, including event-page views, visible listing and sponsor-logo clicks, approximate browser-tab sessions and featured-placement RSVP attribution. For visitors detected in Maine using hosting-provider country and state information, analytics are on by default unless you opt out. Elsewhere, or when location is unknown, analytics start only after acceptance. We do not save the location in analytics preferences. Existing refusals and browser Global Privacy Control or Do Not Track signals keep analytics off. A regional default is recalculated on each full page load and is not saved as an affirmative acceptance. Use Privacy choices to turn analytics off; this stops future collection and clears attribution stored in this browser tab. Your choice is remembered with a preference cookie and browser storage for up to 180 days. Account and admin page browsing is excluded. When analytics are enabled, signup invitation tests use a random browser token to compare messages, clicks and confirmed new memberships. The token can travel in your sign-in link so confirmation in another browser can be attributed. We count new confirmations once, show staff aggregate results, and do not send account identities to Google Analytics. Withdrawing analytics consent stops this attribution for the current browser token. Advertising uses separate aggregate view and click counts without visitor cookies, member identifiers or IP addresses in its reporting records. Tracking failures do not prevent browsing or registration. Results count recorded activity, not exact people, and blockers or declined measurement can reduce coverage. When configured, optional Google Analytics collects sanitized public-page categories, campaign labels, scroll depth, time engaged, event interactions and advertising campaign/creative/placement measurements, using analytics cookies. Names, email addresses, free-text searches, full referring URLs, form values and arbitrary query parameters are excluded from our event payloads. Google processes technical connection information under its own privacy policy. Microsoft Clarity session recordings are currently disabled. Signed-in sessions, public profile pages, forms and URLs with queries or fragments are excluded from recordings. Account, admin and checkout pages are excluded from both providers. Declining or withdrawing stops future collection. Provider projects and switches must be configured before either provider loads; choosing acceptance alone does not connect an unconfigured provider. Provider reports and retention are managed in their dashboards.

Updating information and making requests

You can edit your profile, remove its photo and change its visibility in your account. Use the Contact page to request help accessing, correcting or deleting account information. We may need to verify that a request comes from the account holder.

Some records may need to remain for service operation, security, disputes or legal obligations. A request to hide a public profile is different from deleting account records, event history or provider backups. Ask the team about your specific request.