Privacy Policy
Introduction
This Privacy Policy applies to all users of RubixKube™ services, including our website, platform, APIs, and integrations. By using RubixKube™, you agree to the practices described in this document.
What Information We Collect
Personal Information
- Name, email, job title
- Organization name
- Login credentials, preferences
Usage & Technical Data
- IP address, browser, OS
- Pages visited, session time
- Infra metadata (e.g., logs)
Third-Party Integrations
- GitHub tokens
- Prometheus, CI/CD events
- System logs & telemetry
How We Use Your Data
| Purpose | Description |
|---|---|
| Service Delivery | Operate and improve RubixKube™ functionality |
| Account Management | Authenticate, notify, and support your usage |
| AI Operations | Feed anonymized data to improve agent behavior |
| Security Monitoring | Detect unauthorized access or misconfigurations |
| Analytics & Insights | Product usage patterns to guide UX & features |
| Legal & Compliance | Fulfill legal obligations and audits |
Data Protection & Security
Security Measures
- End-to-end encryption for data in transit
- At-rest encryption for sensitive data
- Regular security audits and penetration testing
- Access controls and authentication
Data Retention
- Account data: Until account deletion
- Usage logs: 90 days
- Analytics: 2 years (anonymized)
- Legal compliance: As required by law
Your Rights & Choices
Access & Control
You have the right to:
- Access your personal data
- Correct inaccurate information
- Request data deletion
- Export your data
- Opt-out of marketing communications
Contact Information
For privacy-related questions or to exercise your rights, contact us at:
Data Protection Officer
Rubix in Slack
When your organization connects Slack, the Rubix app reads only what it needs to answer: the message that mentions it or is sent to it directly, the recent messages of the thread it was mentioned in (read at that moment, at most fifteen), the name of the person who asked, and RubixKube incident links pasted in Slack. It does not read channels it was not invited to, does not join channels on its own, and stores no Slack messages.
What you say to Rubix, and the thread messages sent along as context, become part of that conversation in your RubixKube organization, kept for as long as your organization keeps the conversation and deleted with it. Rubix writes one thing into Slack: a conversation identifier in the metadata of its own replies. Approvals and questions you answer in Slack are recorded in your organization's activity log with your Slack name.
Rubix answers with the model your organization chose in RubixKube (our hosted models, or your own provider). No Slack data is used to train models. To remove Rubix, disconnect Slack in the console or remove the app in Slack; either stops all reading at once. Data requests go to the address below.
Policy Updates
We may update this policy periodically. Significant changes will be communicated via email or platform notifications. Continued use of RubixKube™ after changes constitutes acceptance of the updated policy.
Contact Us
If you have any questions about this Privacy Policy, please contact us:
Email: [email protected]
Address: RubixKube Intelligence Private Limited