Privacy Policy

Information we collect

We collect information you provide directly, such as your email address, account credentials, support messages, billing selections, and plan choices.

When you use OB-1 or hosted services, we may process prompts, model requests, repository context you choose to send, command metadata, logs, device and session data, usage events, and error reports.

If you sign in with Google, we receive the account information needed to authenticate you. If you pay for a plan, Stripe processes payment details and sends us billing records such as customer, subscription, invoice, and payment status identifiers.

How we use information

We use information to provide the service, authenticate users, route model and search requests, meter usage, prevent abuse, process payments, provide support, debug issues, improve reliability, and comply with legal obligations.

We do not sell your personal information.

Code and repository context

OB-1 is designed for developer workflows. Depending on how you configure and use it, repository context, file snippets, prompts, command output, or memory records may be sent to hosted services or model providers to complete your request.

Do not send secrets, private keys, regulated data, or content you are not allowed to process through Overbrilliant. Review tool output before committing, deploying, or sharing it.

Sharing and subprocessors

We share information with service providers only as needed to operate Overbrilliant. Current processor categories include model routing, billing, authentication, search, infrastructure, support, and security.

A current list is available on the Subprocessors page.

Retention

We keep account, billing, usage, security, and support records for as long as needed to provide the service, resolve disputes, comply with law, and protect the service.

Local OB-1 project memory, caches, and generated files may also exist on your own machine or repository. You control those local files.

Your choices

You can stop using the service, revoke CLI tokens, delete local project state, cancel paid plans, or ask us about access, correction, deletion, export, or objection rights where available under applicable law.

To make a privacy request, email [email protected].

Security

We use technical and organizational safeguards designed to protect the service, including hashed CLI tokens, signed sessions, provider key isolation, access controls, and abuse monitoring. No system can be guaranteed perfectly secure.

International use

Your information may be processed in the United States and other countries where Neu Software LLC or its service providers operate. Those countries may have different data protection laws than your location.