claimclub.ioCheck what you're owedGet started

Information Security Policy

Effective November 16, 2026 · Reviewed at least once a year

This policy describes how Claimclub protects the information members give us, including bank data received through Plaid. It applies to everyone who works on Claimclub and to every system that stores or processes member data.

1. Ownership and contact

The Founder is responsible for information security at Claimclub: setting this policy, approving access, reviewing risks and leading the response to any incident. Security questions and reports go to privacy@mail.claimclub.io, which is monitored.

2. Data we protect

  • Account and claim data: name, contact details, addresses, claim answers, signed authorizations and uploaded proof.
  • Bank data (from Plaid): account names and masks, transactions and recurring payments, only for members who choose to connect a bank.
  • Payment data: card details are entered directly into Stripe and never reach our servers.

We collect only what is needed to file claims, review charges and show payouts. We do not sell or rent member data.

3. Risk management

The Founder reviews security risks before any major change that touches member data and at least once a year. Each risk is recorded with how it is handled, and this policy is updated when practices change.

4. Access control

  • Members sign in with a one-time code sent to their email. There are no member passwords to steal or reuse.
  • Row-level security in the database lets each member read and change only their own records.
  • Bank data tables can be read only by our servers, never directly from a browser.
  • Staff access to member data goes through the admin console, which is limited to named staff accounts. Access is granted for the job only and removed the same day it is no longer needed.
  • Every account with access to our infrastructure (hosting, database, code repository, payments and Plaid) must use multi-factor authentication.
  • Every change to a claim's status is logged with time and actor.

5. Encryption

  • All traffic to and from claimclub.io uses HTTPS (TLS 1.2 or higher).
  • Stored data is encrypted at rest by our database provider.
  • Plaid access tokens are also encrypted by our own application with AES-256-GCM before they are stored. The key is held separately from the database.
  • API keys and secrets are kept in our hosting provider's encrypted environment settings, never in source code.

6. Infrastructure and vendors

Claimclub runs on established providers that maintain their own security programs, including SOC 2 reports: Vercel (hosting), Supabase (database and sign-in, U.S. region), Stripe (payments), Plaid (bank connections) and Resend (email). We review a vendor's security before giving it member data.

7. Secure development

  • All code is kept in a private repository with change history.
  • Changes are tested before release, and every release can be rolled back.
  • Database security warnings and dependency updates are reviewed regularly, and security fixes are applied promptly.
  • Test data is used for testing. Real member data is not copied into test systems.

8. Bank data handling

  • Members connect a bank only through Plaid's own window, after agreeing to share their data.
  • Bank data is used only to show members their own charges, subscriptions and payouts.
  • A member can disconnect a bank at any time in Your info. This revokes our access at Plaid and deletes the stored accounts, transactions and subscriptions for that bank.
  • We never use bank access to move money.

9. Retention and deletion

We keep member data while the account is open. When a member asks to delete their account, we delete their data within 30 days. Signed authorizations and payment records are kept as long as the law or a settlement requires. Members can request access to or deletion of their data at privacy@mail.claimclub.io.

10. Incident response

  1. Anyone who suspects a security problem reports it to privacy@mail.claimclub.io right away.
  2. The Founder contains the issue, for example by revoking keys or access, and investigates what happened.
  3. Affected members, Plaid and any other affected partners are notified without undue delay, and within the time the law requires.
  4. Afterwards we record the cause and the fix, and update this policy if needed.

11. People

Anyone given access to member data must read and follow this policy, keep data confidential, use only Claimclub-approved tools and report any problem at once. Access ends when their work ends.

12. Reporting a vulnerability

If you find a security issue on claimclub.io, please email privacy@mail.claimclub.io. We will respond and work with you to fix it.