Your data. Your vault. Our zero-knowledge guarantee.

    Oyster is built so core claim data stays in your pocket instead of in a centralized claim database. This page explains the privacy architecture in plain language. If you are looking for the formal legal policy, use the Privacy Policy.

    Quick answer

    Core claim data is designed to stay on your device.
    Secrets are stored in local AES-256 secure storage.
    Oyster does not sell personal claim data.
    Privacy architecture matters as much as privacy policy language.

    Does OysterClaim sell my data?

    No. Oyster does not sell personal data, and the product is designed so that profile information, claim IDs, and email discovery results live in a local AES-256 vault on your device rather than in a central Oyster claim database.

    Unlike products that collect claims into the cloud, Oyster's architecture keeps the sensitive layer local. That means there is no central pool of private claim data for Oyster to package, resell, or leak.

    The three pillars of Oyster privacy

    This is less about legal trust and more about technical design. The goal is to make unnecessary data collection structurally harder, not just contractually discouraged.

    Local-Only Processing

    Your phone is the server. Whether Oyster is scanning Gmail metadata for settlements or checking breach exposure with privacy-preserving techniques, the sensitive computation happens on your device. OAuth tokens stay local and raw personal data is not sent to Oyster for central storage.

    Encryption at Rest

    Your Secrets Vault is protected by AES-256 platform-backed secure storage. The useful outputs such as claim IDs and saved filing details are stored locally, and the protection keys remain on your device rather than in a shared cloud database.

    Data Minimization

    Oyster is a utility tool, not an identity graph. It does not require a social profile, does not ask for irrelevant data just to open the app, and only keeps the filing information you choose to reuse for official claim forms.

    Why we don't use ads or subscriptions

    Funding model is part of privacy design. If a product makes money by profiling users, privacy becomes a slogan instead of an architecture.

    No ad-tech business model

    Oyster is not designed around selling behavior to advertisers or data brokers. The public website does not use third-party marketing or analytics trackers. Oyster does not monetize private claim data or build a surveillance-style claims business.

    Open source first, ads never

    Oyster is open source and is not designed around selling your behavior. Voluntary contributions may help pay for infrastructure, but you never have to pay to use core filing, and you can inspect the code on GitHub. That structure reduces pressure to build for advertisers instead of users.

    Open-source audit

    Privacy claims are not meant to be accepted on vibes alone. Oyster's code can be inspected publicly so the architecture can be checked against the promises.

    We don't just have a privacy policy you are supposed to trust. We have a privacy architecture you can inspect. By moving core claim data from shared servers to your pocket, Oyster reduces the risk surface that usually turns user data into a product.

    Set it and forget it. Automated. Private. Free.

    Automated class action filing—official forms in-app, set it and forget it, open source, $0.

    Claims tied to your email

    Check what Oyster can already match and what may be worth watching.

    Related guides