Privacy

Signing in uses GitHub OAuth. We store your name, email, and avatar URL as returned by GitHub, plus session data (needed to keep you signed in). We don't see your GitHub password -- GitHub handles authentication directly.

The Studio's "Re-guess with AI" action sends your OpenAPI spec's full text to Anthropic's Claude API to suggest better method names and resource groupings. This is opt-in and manually triggered -- it never runs as part of the default generate/save path.

Before that request goes out, we run an automated best-effort scan for common credential shapes (API-key-like strings, private-key blocks, fields named like password/api_key/secret paired with a real-looking value) and warn you before anything is sent if it finds something, with the choice to strip those values or send the spec as written.

This scan is a heuristic, not a guarantee. It catches recognizable patterns; it will not catch every way a credential or personal detail can appear in spec text. If your spec's examples contain something sensitive in a shape the scan doesn't recognize, it can still reach Anthropic when you choose to proceed. We are not responsible for information embedded in your own spec content that this scan does not catch -- review what you paste, the same as you would before pasting it into any third-party tool.

Credit-pack and subscription purchases are processed by Stripe. We send Stripe only an internal, non-identifying reference to your account; Stripe collects your payment details directly through its own hosted checkout. We never see or store your card number.

Installing the Osmundus GitHub App grants it contents: write, pull_requests: write, and checks: write on the repos you choose. In practice: it reads your spec repo to detect changes, and opens/updates pull requests with generated SDK code on your target repos, posting check-run status as it does. It only acts on push and pull_request events for repos you've explicitly installed it on.

Some internal error conditions (a failed release, a billing anomaly) can trigger an alert to our own operations channel. These alerts carry operational identifiers relevant to debugging, not your account credentials or payment details.