OctynX1. Scope
This notice applies to the OctynX website, request-access form, dashboard, and private-alpha API. It does not cover third-party websites, AI providers, or tools that may be linked from OctynX.
2. Information we collect
- Contact and alpha request details: name, email address, company, and the message submitted through the request-access form.
- Account and access information: administrator session state, API key identifiers, authentication events, and related access-control metadata.
- API request metadata: timestamps, route, selected model, status, token counts or similar usage indicators, and operational error categories.
- Technical information: IP address, user agent, logs, and security signals needed to operate, debug, protect, and rate-limit the service.
3. Prompt and response content
OctynX is designed to provide request visibility without turning prompt and response bodies into a default analytics surface. During the alpha, we aim to avoid storing prompt bodies and model response bodies in dashboard logs unless a future feature, debugging workflow, or explicit customer configuration requires it.
Early testers should not submit secrets, regulated production data, or sensitive personal data unless a separate written agreement and deployment review allow it.
4. How we use information
- Respond to alpha access requests and communicate with selected testers.
- Provide, secure, monitor, debug, and improve OctynX.
- Enforce authentication, rate limits, abuse controls, and approved model access.
- Understand which governance and visibility features are most valuable for alpha users.
- Comply with legal, security, and operational obligations.
5. Sharing and processors
We do not sell personal information. We may share limited information with infrastructure, hosting, security, communications, and AI-provider services when needed to operate OctynX. These providers are expected to process information only for the service purposes we authorize.
The alpha catalog is intentionally limited to approved providers and models. Provider and hosting details may change as the alpha evolves; material changes will be reflected in this notice or in customer-specific documentation.
6. Retention
We keep alpha-request records, access logs, and operational metadata only as long as reasonably needed for private-alpha operations, security, debugging, and governance-readiness work. We may delete or anonymize records when they are no longer useful for these purposes.
7. Security
OctynX uses access controls, API-key authentication, dashboard gating, rate limits, and operational logging to protect the alpha environment. No online service can be made risk-free, and alpha testers should treat OctynX as an early controlled environment rather than a production compliance system.
8. Your choices
- You can choose not to submit the request-access form.
- You can ask your OctynX contact to update or delete alpha request information associated with you.
- You can stop using alpha API keys or request that a key be revoked.
9. International operations
OctynX is European-oriented in product direction and governance posture. This notice does not promise that all processing occurs only in the European Union or that any specific compliance certification is already complete.
10. Contact and updates
For privacy questions, use the request-access form or your existing OctynX contact. We may update this notice as the private alpha changes; the “Last updated” date will show when the page was revised.