
How LongTable keeps your club's records safe
Your roster holds real people's names, emails, and phone numbers. This page explains how we protect them. Each part has a technical detail for anyone who wants the specifics.
The short version
We never see credit card numbers
Stripe takes payments on its own pages, and dues go into your club's own Stripe account.
Every club has its own filing cabinet
Your records are filed under your club alone, and every request is checked against the person's position.
Encrypted on the way and in storage
TLS 1.2 or newer for every connection, and AES-256 for everything stored.
Passkeys a hacker can't steal
A passkey works only on LongTable's real site, so a look-alike page can't collect it. Anyone can turn one on.
Multiple backups, across the country
The database can be rolled back to an earlier moment, and weekly backups are kept in two locations on opposite sides of the country.
The records stay with the club
Download your records whenever you like, or close the club and have them permanently deleted, as our privacy policy describes.
Follow one request from the browser to your records
Say your treasurer opens the roster on a laptop at the coffee shop. Here's what happens before a single name appears, in order.
The front door checks every visit
The treasurer's browser talks to LongTable over an encrypted connection, so someone else on the coffee shop Wi-Fi can't read the roster as it travels. Before the request goes further, a filter turns away known attack patterns and anyone sending far more requests than a person could. Mozilla, the people behind Firefox, scans our site's security settings and gives it an A+ (opens in a new tab).
The technical detail
- TLS 1.2 minimum (CloudFront's
TLSv1.2_2021policy), with TLS 1.3 offered. Plain HTTP redirects to HTTPS. - HSTS tells browsers that once they have connected to LongTable over HTTPS, they must always use HTTPS from then on, for 2 years and on every subdomain (
includeSubDomains,preload). - AWS WAF on every CloudFront distribution, running the AWS Common Rule Set and Known Bad Inputs rule set.
- A per-IP rate limit, with tighter limits in sensitive places. CAPTCHAs are used to secure the site from bots.
- An enforced Content Security Policy (CSP): browsers load scripts and other resources only from places we have approved, which blocks most attempts to slip in outside code. Browsers are also told not to let other sites embed ours, not to guess file types, and to share only limited information about where a visitor came from.
- The API answers only requests that came through CloudFront, which adds a secret origin header.
- TLS 1.2 minimum (CloudFront's
Sign-in proves who you are
LongTable never sees or stores your password. We don't build our own sign-in. The security team behind Amazon manages the sign-in service we use, and it checks your password for us. Once you're in, your browser carries a pass that lasts one hour. It's swapped for a new one as it runs out, and each swap retires the pass before it.
The technical detail
- Identity is Amazon Cognito. Passwords go to Cognito and never reach LongTable's servers.
- Passwords need at least 12 characters, including a lowercase letter and a number.
- Access tokens are RS256-signed JWTs that last 1 hour. Refresh tokens rotate on every use, and revocation is on.
- Nobody can create an account on their own: an account exists only after an invitation, or after someone proves they own the email address when they start a club.
Your position decides what you can open
Being signed in isn't enough. Each time someone opens a page or saves a change, LongTable looks up their membership in that club and what their position allows. A treasurer sees dues, and a member sees the directory. If the position doesn't allow it, nothing is shared: the request stops, and the option to do it is never shown to that person.
The technical detail
- Every click that reaches a club's data is checked against written access rules in an open-source policy language, and Amazon's permissions service makes the decision before anything is returned.
- The sign-in token carries no club and no position. The club comes from the address being requested, and the person's membership record for that club is loaded on each request. Only an active membership counts.
- Roles grant permissions, and the policies decide. A role's name never authorizes anything on its own.
- A route with no specific permission still requires an active membership in that club.
Every club has its own filing cabinet
Everything your club owns, from the roster to the newsletters, is filed under your club's own label in the database, and your files sit in your club's own folder. A request for your club opens only your club's filing cabinet. That's also why we can hand you all of it, or remove all of it, cleanly.
The technical detail
- We partition data by each club's ID number, so every club's records are kept in their own separate section of storage.
- We store each club's files in that club's own folder, kept apart from every other club's. Every action on a file needs a signed-in person, and their signed access token is checked against their position before anything is read, uploaded, or removed. Storage blocks all public access.
- Upload and download links expire after 15 minutes. Members-only page images are shown only with digitally signed and verified access tokens.
- An automated check fails any code change that reads a club's records outside that club's partition.
Your records are locked in storage too
Your club's records are encrypted where they're stored, with the same strong encryption standard banks use. LongTable keeps the key safe in its own AWS account and replaces it on a schedule. No one in your club holds it, and your data is opened only to answer requests that pass the checks above. A copy of the stored data is unreadable without that key.
The technical detail
- LongTable encrypts your club's records and its history with an encryption key that LongTable controls. The key is replaced on a regular schedule.
- Every file is encrypted in storage. Files are protected with the same kind of LongTable-controlled key, and older files are re-encrypted with it the next time they're saved. Until then, they stay encrypted with the storage provider's own key.
- Club archives have their own dedicated key, and so do backups in each region.
- Connection tokens for outside services are encrypted again, with their own encryption context, before they're stored.
Changes are written down
When someone changes a record or signs in, it goes into your club's history. So does a LongTable staff member signing in as one of your members to help. Admins can see who changed what in the last 90 days, including changes made through the assistant. The history is add-only: the service that writes it can't edit or remove an entry, and entries clear on their own after that window.
The technical detail
- History is written to a separate database. The API's access lets it add and read entries, but not update, delete, or scan them.
- Entries expire after 90 days.
- Recorded: successful creates, changes, and deletes; sign-ins; every platform admin action, including failed attempts; staff sign-ins as a member, start and stop; and archive download links. Reading a record is not recorded.
- Our support method: we sign in as a member (impersonation) only after a support ticket from your club gives us permission. The changes we make during that session are in the audit log.
Card numbers never reach LongTable
Payments happen on pages Stripe hosts. Member dues go straight into your club's own Stripe account, so LongTable never holds the club's money.
Stripe holds
- Card numbers, security codes, and expiry dates
- Your club's dues, in your club's own Stripe account
- The payment pages and invoices members pay on
LongTable holds
- Who paid, how much, and when
- Whether each invoice is open or paid
- Stripe's reference numbers, so the two stay matched
The technical detail
- LongTable's own plans are paid through Stripe Checkout and managed in the Stripe Billing Portal.
- Dues and event fees use Stripe Connect. The club is the seller, invoices are Stripe-hosted, and payments settle in the club's account.
- In-person payments run on Stripe Terminal or Tap to Pay, where Stripe's own software reads the card on the device.
- Stripe's messages to LongTable are checked against Stripe's signature before anything in them is read.
Ways to make your own sign-in stronger
Each person chooses these for themselves, from their security settings.
Passkeys and authenticator apps
Use your fingerprint, face, or device PIN, or a six-digit app code. A passkey works only on our real site, so a look-alike page can't collect it.
Google and Apple sign-in
Use the Google or Apple account you already protect, with the security settings and extra checks you already have there.
How long you stay signed in
Pick how long each device stays signed in, from 3 months down to 2 hours. On a shared computer, the shorter the better.
The technical detail
- Passkeys are WebAuthn credentials, with user verification required every time. A passkey can also replace the password entirely.
- Authenticator apps use TOTP. Enrolling a factor makes it required for that account.
- Google and Apple sign-in uses OpenID Connect (OIDC), an open standard for letting one trusted service confirm who you are to another.
- You sign in on Google's or Apple's own page, so your Google or Apple password never reaches LongTable. Their protections apply there, including any two-step verification or passkey you've turned on for that account.
- LongTable receives a signed confirmation of your identity from Google or Apple and checks that signature before it trusts it.
- Signing in this way doesn't skip anything else: your position in each club is still checked on every request.
The assistant sees only what you can see
LongTable's assistant works for the member who's asking, with that member's permissions and no more.
Your permissions, no more
It works with your access only, one request at a time. It can't do anything you couldn't do yourself.
Checked at every step
Each step it takes is checked against the access the asking member has at that moment, exactly as if they had clicked it themselves.
It proposes, you approve
Changes wait until you confirm them.
Money is off limits
We don't let the assistant make money changes. It can't reach invoices, payments, refunds, or billing.
Conversations stay private
Each conversation is saved under the member who had it, only so they can look back at what they asked and did. It is deleted 7 days after the last message.
Not used to train AI
Your club's data is not used to train AI models, ours or anyone else's.
The technical detail
- The assistant is powered by a modern AI model, which we reach through Amazon Web Services from LongTable's backend infrastructure.
- Each time you ask, the assistant gets access that lasts 15 minutes and works only for you, your club, and that one request. Every action is evaluated against the requester's permissions, and those permissions are never increased.
- Conversations are kept separately for each club and member, stored encrypted, and deleted 7 days after the last message.
If something goes wrong
Roll back to any second
The database can be restored to any second within its recovery window.
Weekly backups in two regions
A weekly backup is kept, with a copy on the other side of the country.
Protected from accidental deletion
We turn on protection so the database and the sign-in records can't be deleted by accident or by a mistake. Stored files keep earlier versions, so a bad change can be undone.
The technical detail
- Your club's records and its history can be restored to an earlier point in time.
- Every week we take a backup of your records and files, and keep a copy in a different part of the country.
- Deletion protection is on for your records and the sign-in records. Earlier versions of your files are kept, so a change can be undone.
Taking your records with you, or closing the club
Your club can download its records as spreadsheets at any time. On the Plus plan and up, an admin can download the whole club in one archive. Every file in it can be validated, so you can tell nothing changed on the way.
If your club closes, an admin has 90 days to change their mind and reopen it. After that, LongTable removes the club's records and files. Copies inside backups age out within 35 days after that.
The technical detail
- The archive is a ZIP file you can download. It holds the club's records and files. Its download link lasts 7 days, and every link issued is recorded in the club's history.
- We make sure a club can't be closed by accident: closing takes a deliberate confirmation, and you have 90 days to get the club back. After that, a scheduled job removes all of the club's records and files.
If we need to step in, we ask first
If someone at LongTable needs to connect to your club to help you, we ask for your permission first. While we're signed in, every change we make is written to your club's history, along with when the session started and stopped, so you can see what we did.
Our side of the table
LongTable's founders work in security. Together they bring more than 50 years of experience in IT, software, and security, and they run LongTable to the level of rigor that Fortune 100 companies expect.
- Every change goes through a strict testing and validation process before it reaches your club. Automated tests run on each one and check for the security mistakes we've seen before.
- LongTable staff go through extra steps to get in: a separate sign-in that requires two-step verification, and a fresh sign-in every 24 hours for admin tools.
- When one of us signs in as a member to help with a problem, it's recorded in your club's history. That session can't be renewed and stays in one browser tab.
- Security scanning checks our code on a regular basis for known weaknesses, so we can find and apply patches.
- Passwords and keys for outside services live in AWS's encrypted parameter store, never in our code.
- Every software package is pinned to an exact version, so nothing changes without us knowing.
- Our logs leave out sign-in tokens and remove emails, phone numbers, and IP addresses from error messages.
The technical detail
- Operators sign in with enforced multi-factor authentication, into a separate admin system that member sign-ins can't reach.
- Security scanning runs on our code on a regular basis. It looks for known weaknesses in our code and in the software it depends on, so patches can be applied.
- Secrets are stored encrypted and read at run time. Software packages and automated build steps are pinned to exact versions, and dependency checks run at the high-severity threshold.
- Our logs are monitored automatically with Amazon's monitoring tools. Alarms cover the API, the firewall, payment messages, and scheduled jobs, so we can investigate when something looks wrong.
At a glance, for your IT volunteer
| Area | What LongTable uses |
|---|---|
| Hosting | Amazon Web Services, US West (Oregon). Backup copies in US East (N. Virginia). |
| In transit | TLS 1.2 minimum, TLS 1.3 offered. HSTS for 2 years with preload. |
| At rest | AES-256 throughout. Customer-managed AWS KMS keys, rotated automatically, for the database and newly saved files. |
| Sign-in | Amazon Cognito. Passkeys (WebAuthn), authenticator apps (TOTP), Google and Apple. |
| Permissions | Amazon Verified Permissions with Cedar policies, on every club request. |
| Club separation | One database partition and one storage prefix for each club. |
| Payments | Stripe Checkout, Stripe Connect, and Stripe-hosted invoices. No card data on LongTable systems. |
| Edge protection | AWS WAF managed rules and per-IP rate limits. CAPTCHAs are used to secure the site from bots. |
| Backups | Point-in-time recovery. Weekly backups, copied to a second region. |
| Club history | Append-only, kept 90 days. |
| AI assistant | Claude through Claude Platform on AWS. A per-request grant limited to the member's permissions. Conversations kept 7 days. |
Report a security concern
Think you've found a weakness in LongTable, or see activity in your club you don't recognize? Tell us through our contact form, and choose Security issue or unauthorized access.