privacy
your code stays on your machine.
last updated june 2026.
the short version: oi runs locally. your code, prompts, and completions never leave your machine. we collect almost nothing — just what stripe needs to process your one-time payment.
what we collect
- your email address — used by stripe to deliver your license key and send a receipt
- your oi pro license key — a signed token stored locally on your device
- stripe payment data — card details are handled entirely by stripe; we never see or store them
what we don't collect
- your code — everything processed by oi's cli and vs code extension stays on your machine
- your prompts or completions — they go to your local ollama / llama.cpp instance, not to us
- usage telemetry, crash reports, or analytics
- any account or login information — oi has no user accounts
local-first by design
oi is a local tool. the cli and vs code extension connect directly to the llm running on your machine (via ollama or llama.cpp). nothing is proxied through ogbuilds servers. your intellectual property stays yours, on your hardware.
license key validation
oi pro license keys are cryptographically signed (ed25519) and verified locally by the cli and extension. validation is offline — your device never phones home to check your license. the key is stored in your local config directory.
stripe & payments
oi pro is a one-time purchase processed by stripe. stripe may collect device and browser data as part of fraud prevention. we receive confirmation that payment succeeded and the email to send your license key to; nothing more. stripe’s privacy policy applies to payment processing.
data retention & deletion
we hold your email and license record to support re-delivery requests (e.g. if you lose your key). to request deletion, email us and we’ll remove your record. deleting oi from your machine removes all local data immediately.
contact
questions about privacy? reach the team via ogbuilds.ai.