Legal & Policies

Terms of Use

Terms and conditions for using Orcus SDKs and the website.

Orcus provides SDKs for Node.js and TypeScript that allow applications to interact with supported AI provider interfaces. By using Orcus or its documentation website, you agree to use the software lawfully and comply with applicable laws and the terms of any third-party services you access.

Acceptable Use

You are responsible for how you use Orcus, the applications you build, the requests you send, and the data you process. Do not use the SDKs to violate applicable laws, bypass access controls, abuse provider services, or access systems without authorization.

Intended Use and Production Support

Orcus integrations using web-session credentials or web-interface endpoints are intended for personal projects, hobby projects, and experimentation, not production use. For production workloads, use official provider APIs. Orcus may add official API integrations in the future; integrations using those APIs can be used in production according to their respective provider terms and documented limitations.

Future Development

Orcus may expand to support official provider APIs, additional integrations, improved reliability, and production-ready features in the future. Availability will depend on implementation and provider support. Future production use will apply only to integrations that explicitly support it and follow their documented requirements.

Third-Party Services

Orcus integrations may depend on third-party websites, authentication systems, undocumented interfaces, and provider infrastructure. These services are controlled by their respective providers and may change, restrict access, rate-limit requests, or become unavailable without notice. Orcus does not guarantee continued compatibility or availability.

Your Responsibility

You are responsible for protecting credentials, securing your application, obtaining any required permissions, and evaluating AI-generated responses before relying on them. Validate model outputs and tool calls, handle errors appropriately, and avoid sending data you are not authorized to share.

Limitations

Orcus is provided without guarantees of uninterrupted operation, accuracy, availability, or compatibility with third-party services. Models may produce incorrect or incomplete responses, and integrations may stop working when providers change their websites, authentication flows, request formats, or access policies.

To the extent permitted by applicable law, Orcus and its maintainers are not responsible for losses arising from your use of the software, reliance on generated output, interruptions in third-party services, or changes to provider access. You use the software at your own risk.

Changes to These Terms

These terms may be updated as the project and its integrations evolve. Continued use after an update constitutes acceptance of the revised terms to the extent permitted by applicable law.

Privacy Policy

How SDK requests, credentials, and website data are handled.

Orcus SDKs are designed to run within your application and send requests to the provider interfaces configured for the integration. The SDKs are client libraries, not a hosted AI proxy. Unless a specific feature states otherwise, SDK requests are sent to the relevant provider rather than through an Orcus-operated backend.

Data Handling

Depending on the SDK and features you use, prompts, conversation history, files, images, request metadata, cookies, API keys, or other authentication material may be sent to a third-party provider. The provider’s privacy policy and terms govern how it handles the information it receives.

Credentials and Authentication

Some integrations require API keys, session cookies, XSRF tokens, or other authentication credentials. These credentials are supplied and managed by your application. Keep them private and review the relevant provider’s policies before using account-based web sessions.

Data Retention

Data retention depends on your application, the configuration of the services you use, and the policies of the relevant provider or website host. Do not assume that information sent to a third-party service will be immediately deleted or remain only on your device.

Your Responsibility

Avoid sending unnecessary personal, confidential, or sensitive information. Ensure you have the necessary rights and permissions to submit data to a provider, and make sure your application complies with applicable privacy and data-protection laws.

Security

Credential protection, safe integration practices, and vulnerability reporting.

Orcus SDKs run within the environment where you install and execute them. You are responsible for securing that environment, managing credentials, controlling access to your application, and deciding how requests and responses are handled.

Credential Handling

Never commit API keys, session cookies, XSRF tokens, or other authentication material to source control or expose them in public repositories, client-side bundles, logs, or error messages. Use environment variables or a secrets manager, restrict access to credentials, and rotate them if they are exposed.

Request and Application Security

Review the information your application sends to AI providers. Validate inputs and model outputs, apply appropriate authorization checks, and treat tool calls and generated content as untrusted. Do not rely on AI responses as the sole control for security-sensitive decisions.

Web-Based Integrations

Integrations that interact with web interfaces may depend on session credentials, undocumented request formats, and provider-side security controls. Use only accounts and systems you are authorized to access. Follow provider terms and do not attempt to bypass access restrictions or security mechanisms.

Dependencies and Updates

Orcus depends on third-party packages and provider interfaces. Keep dependencies updated, review relevant security advisories, and test integration changes before deploying your application. Upstream changes may affect functionality, reliability, or security.

Reporting a Vulnerability

If you discover a potential security vulnerability in Orcus, report it privately to the project maintainers with sufficient information to investigate and reproduce the issue. Avoid publicly disclosing exploitable details before the issue has been assessed. Do not test against systems you do not own or have permission to test.