Subprocessors
To run LongTable we rely on a small set of trusted third-party companies (our subprocessors) that process personal information on our behalf, under contracts that limit them to working for us. This page names those companies and what each one does. It is the list our Privacy Policy refers to, and we keep the two in step: the categories below are exactly the ones the Privacy Policy discloses.
The short version
- LongTable uses a handful of well-known providers for hosting, payments, messaging, AI processing, document storage, product analytics, and website analytics, not a long chain of data brokers.
- Each provider is contractually limited to processing your club's data only to provide its part of the service.
- We never sell personal information, and our contracts limit what subprocessors may do with it. Where a provider also uses data for its own purposes, such as Stripe's fraud prevention, the table below says so.
1. Current subprocessors
These are the third-party service providers that process personal information to help us deliver LongTable.
| Subprocessor | What it does | Where |
|---|---|---|
| Amazon Web Services (AWS) | Cloud infrastructure and hosting (the servers, storage, databases, and content-delivery network the service runs on), including transactional and club email delivery, SMS (text-message) delivery for clubs on plans with texting, and AI infrastructure for the LongTable assistant. Only the slice of club data needed to answer an AI request is sent, and your club's data is never used to train models. | United States |
| Stripe, Inc. | Payment processing for LongTable's own subscription billing, and for dues and event fees, which run through each club's own Stripe account. Card details go directly to Stripe; we never receive or store full card numbers. Stripe also uses payment data for its own fraud prevention and legal compliance, under its own privacy policy. | United States |
| Google LLC | Document storage for clubs that turn on Google Drive. LongTable creates and administers a shared drive for the club inside a Google Workspace that LongTable owns; club documents stored there are held in Google's infrastructure. Clubs do not connect their own Google account and need no Google Workspace subscription. Google Maps Platform address suggestions are a separate feature for which Google acts under its own terms rather than as our subprocessor; see the Privacy Policy. | United States |
| PostHog, Inc. | Product analytics for the LongTable service: which features clubs use, so we can see what works and what to fix. PostHog reads our first-party usage events from our own storage when we run a report, and keeps the reports it builds. The events contain no member names, emails, or phone numbers. The LongTable service runs no PostHog script, so PostHog receives nothing directly from your browser. | United States |
| Google LLC (Google Analytics) | Marketing-website analytics: how visitors find and move through our marketing sites, so we can understand site traffic and what clubs need. Google signals is used only for aggregate demographic and cross-device reports, ad personalization is turned off, no advertising account is linked to it, and it is never used to track visitors across websites other than our own. Google signals draws on Google's own data about signed-in Google users, which Google holds under its own terms, not as our subprocessor. Visitors who send a Global Privacy Control signal are not measured, and visitors in regions that require prior consent are not measured beyond strictly necessary logging unless they opt in. A club's own Google Analytics on its club website is not listed here: Google processes that data for the club, not for LongTable (see the Privacy Policy). | United States and other countries where Google or its subprocessors have facilities |
LongTable itself, operated by LongTable Systems LLC, processes your club's data as described in the Privacy Policy; the providers above process it under our contracts with them, with the exceptions noted in the table.
2. How this list changes
We update this page when we add, remove, or replace a subprocessor, and we revise the "Last updated" date at the top when we do. Because a single canonical list keeps our disclosure consistent, this page and the categories named in the Privacy Policy are maintained together. For material changes to how we use subprocessors, we give clubs notice as described in Changes to this policy. This page does not offer a subscribe-to-changes notification; check back here for the current list.
3. Contact
Questions about our subprocessors or this disclosure: our contact form