Privacy Policy

1. Who we are

OpenABCode provides software and hosted services that help route coding tasks across model providers such as ChatGPT, Claude, Gemini, Azure, and compatible APIs. You can use OpenABCode with your own provider keys ("BYOK") or, where available, with prepaid hosted credits.

If you have questions about this policy, contact us at service@openabcode.com.

2. Information we collect

We collect information you provide directly, including your name, email address, team or organization name, authentication details, billing selections, support messages, and account settings.

When you use the service, we may collect operational information such as API key metadata, team membership, usage events, routing decisions, credit debits, provider/model identifiers, token counts, request timestamps, error logs, device and browser information, IP address, and security audit records.

When you choose hosted model access, OpenABCode may process the prompts, code context, files, messages, tool outputs, and responses needed to complete your request. When you use BYOK mode, model requests are sent using your provider credentials according to your configuration and the provider's terms.

3. Local runtime and code content

OpenABCode is designed to keep local coding execution under your control. Local files, repository contents, terminal output, and tool results are only included in model requests when your client or workflow sends them as part of a task.

We do not claim ownership of your source code, prompts, outputs, or project materials. You are responsible for deciding what code, secrets, credentials, personal data, or confidential information you provide to OpenABCode or third-party model providers.

4. How we use information

We use information to provide, secure, meter, bill, improve, and support OpenABCode. This includes authenticating users, routing requests, enforcing provider and account policy, operating hosted model calls, debiting prepaid credits, generating usage history, detecting abuse, debugging incidents, and communicating service updates.

We may use aggregated or de-identified information to understand service reliability, product usage, cost trends, and model performance. We do not use your private code content to train foundation models owned by OpenABCode.

5. Third-party providers

OpenABCode may send request content and metadata to model providers, infrastructure providers, payment processors, authentication providers, analytics providers, and support tools as needed to operate the service. These providers process information under their own terms and privacy policies.

For BYOK usage, you control the provider account and credentials used for model calls. For hosted usage, OpenABCode controls the provider relationship and meters usage through your OpenABCode account.

6. Billing and payments

Payment information is processed by our payment processor. We may receive and store limited billing information such as customer identifiers, invoice records, subscription status, payment status, tax information, and credit balance records. We do not store full payment card numbers on our servers.

7. Retention

We retain account, billing, security, and audit records for as long as needed to provide the service, comply with legal obligations, resolve disputes, prevent abuse, and enforce agreements. Hosted request logs and diagnostic records are retained only as long as reasonably necessary for metering, reliability, security, and support unless a longer period is required by law or account configuration.

You may request deletion of your account by contacting us. Some records may remain where retention is required for legal, tax, security, fraud prevention, backup, or legitimate business purposes.

8. Security

We use technical and organizational safeguards intended to protect information, including access controls, encrypted transport, audit logs, and separation between account, billing, and model-routing systems. No internet service can be guaranteed perfectly secure, and you should avoid sending secrets or sensitive data unless your workflow requires it and you understand the risk.

9. International processing

OpenABCode and our service providers may process information in countries other than your own. Where required, we use appropriate safeguards for cross-border transfers.

10. Your choices and rights

Depending on your location, you may have rights to access, correct, delete, export, or object to certain processing of your personal information. You can update some account information in the dashboard and can contact us at service@openabcode.com for privacy requests.

11. Children

OpenABCode is not intended for children under 13, and we do not knowingly collect personal information from children under 13. If you believe a child has provided us personal information, contact us and we will take appropriate steps.

12. Changes to this policy

We may update this Privacy Policy from time to time. If changes are material, we will take reasonable steps to notify users, such as posting the updated policy or sending an account notice. Your continued use of OpenABCode after an update means the revised policy applies.