Privacy Policy

    Applies to saibresecurity.com, Saibre Desktop, and Saibre for Python.

    Effective April 1, 2026 · Last updated September 26, 2026

    Pending legal review. This document accurately describes how Saibre is built and operated, but it has not yet been reviewed by counsel. It will be replaced by a lawyer-reviewed version before Saibre's general availability. If anything here is unclear or appears to conflict with the product's behaviour, the product's behaviour as described on /security is what we stand behind.

    The short version

    Saibre's protection runs entirely on your device. We do not receive your prompts, your files, the content of your AI conversations, or the secrets Saibre redacts — not in transit, not at rest, not for training. There is no Saibre server in that path, which is why this is a description of our architecture rather than a promise about our intentions.

    What we collect

    • Account information — your email address, and your company name if you provide one, when you create an account or contact us about a team rollout. Accounts are handled by our identity provider; the Free plan does not require one.
    • Billing information — handled by Stripe. We receive the subscription status and the last four digits of a card; we never see or store full card details.
    • Aggregate product analytics — privacy-preserving, cookie-free page and event counts (for example, that a download button was clicked) via Plausible. No cross-site tracking, no advertising identifiers, and no Google Analytics.
    • Support correspondence — the messages you send us and our replies.

    What we do not collect

    • Your prompts, or any part of your AI conversations.
    • The secrets Saibre detects. Redaction happens on your machine; the real values are never transmitted to us.
    • The contents of files you upload to AI tools. Masking happens locally, inside the file, before it leaves.
    • Your browsing outside the published AI-domain allowlist. That traffic is never routed through Saibre at all.

    Local logs stay local

    Saibre writes an activity log and an audit log on your own machine. Those logs record detector names, counts, and timestamps — never the content that triggered them. They are yours: you can read them, export them, or delete them, and they are not uploaded to us.

    Data retention and your rights

    Account and billing records are retained while your account is active and for as long as tax and accounting rules require afterwards. Aggregate analytics contain no personal identifiers and may be retained indefinitely.

    You can ask us to export or delete your account data at any time by emailing support@saibresecurity.com. Uninstalling Saibre removes the local service, the proxy configuration, and the certificate from your device.

    Service providers

    We use a small number of providers to run the business rather than the protection: hosting and content delivery, identity and authentication, payment processing, privacy-preserving analytics, and email. None of them sits in the content path of your AI traffic, and we do not sell or rent personal information to anyone.

    Changes

    If this policy changes in a way that affects you, we will post the updated version here and note the effective date. Continued use after a change means you accept the updated policy.

    Questions about this policy: support@saibresecurity.com. See also our Terms of Service.