Security › How we handle your data

    How we handle your data

    What we collect when you run a check, and how long we keep it.

    ON THIS PAGE

    This page explains what LetMeCheck collects when you run a check, what we keep and how you can remove it. The privacy policy has the full legal detail.

    What we collect#

    Data
    When
    Required?
    Stored?
    Account details (email, name)
    When you sign up
    Yes
    Yes
    GitHub installation details
    When you connect GitHub
    Only for full checks
    Yes
    Repository metadata
    Full checks
    Only for full checks
    Yes
    Source files
    Full checks
    Only for full checks
    Excerpts in reports
    Your site's public pages
    Quick checks
    Yes, for quick checks
    Findings only
    Findings and scores
    Every check
    Yes
    Yes, in reports
    Pull requests and branches
    Not accessed
    No
    No

    What happens during a check#

    1. You choose what to check. A website address for a quick check, or one of the repositories you shared for a full check.
    2. We fetch what we need. For a quick check, we load your public site like a browser would. For a full check, we fetch a copy of the repository files from GitHub.
    3. Checks run on our scanning servers. Automated tests look for exposed keys, open database rules, risky packages and similar problems.
    4. Explanations are written. To turn findings into plain English and fix prompts, short excerpts around each finding may be sent to an AI provider.
    5. Your report is saved. Findings, scores and the excerpts needed to explain them are saved as a report in your account.

    Your code after a check#

    Three different things can happen to parts of your code, and it helps to keep them apart:

    • Working copies of your files exist only on our scanning servers while a check runs.
    • Excerpts around each finding may be sent to an AI provider so it can write an explanation. This is not the same as storing your code in our database.
    • Reports keep your findings, scores and the excerpts needed to explain them.

    How long we keep it#

    • Working copies are used only while a check runs.
    • Account details are kept while your account is open.
    • Reports stay in your account until you delete them or close your account.
    • Disconnecting GitHub stops future full checks straight away. Past reports stay until you delete them.
    • A free website check that you never save to an account is deleted after 30 days.

    Who can see your reports#

    Reports are private to your account unless you choose to share one.

    Delete your data#

    You can delete individual reports, or close your account. The privacy policy explains what happens to your data after that. If you need help, contact us.

    Who handles your data#

    We use a small number of services to run LetMeCheck:

    Service
    What it does
    Provider
    Database
    Stores accounts and reports
    Supabase
    Scanning servers
    Hold working copies of your files while a check runs
    Blaxel
    AI
    Writes plain-English explanations and fix prompts from short excerpts
    Anthropic, OpenRouter
    Payments
    Processes paid plans. We never see full card numbers
    Razorpay
    Email
    Sends sign-in, billing and product emails
    Resend
    Hosting
    Serves the website and the app
    Vercel, AWS
    Repository access
    Gives the app access to the repositories you choose
    GitHub

    The Security page shows the same list.

    Last updated

    Need help?

    Stuck on something? Our team will help.

    Contact support →

    What's new?

    New checks, improvements and fixes.

    See the changelog →

    Was this page helpful?