1. Information we collect
Account information
Your name, email address and profile picture from the sign-in provider you choose (Slack, GitHub or Google), and for Slack sign-in, your Slack workspace and member IDs.
Workspace data (Customer Data)
When a workspace admin connects a tool, we receive the data that connection allows: messages in Slack channels the bot is added to, repositories, pull requests and commits, issues, documents, meeting transcripts and calendar events, and files on a development machine you connect. This includes names, handles and messages of your teammates. From it we derive tasks, business rules with their sources, meeting decisions and per-person meters (contradictions, missed deadlines, reply rate).
Billing information
Your plan and subscription status. Payments are handled by Polar, our merchant of record, which collects your payment details, billing address and tax information under its own privacy policy. We never see or store full card numbers.
Secrets you give us
Access tokens for connected tools and any AI provider keys you bring.
Usage and device data
IP address, browser and device type, pages and features used, and error logs, collected when you use the Service.
Cookies
We use essential cookies to keep you signed in and secure. We don't use advertising cookies.
2. How we use it
- To provide the Service: read connected tools, file and schedule tasks, check asks against your business rules, open pull requests you approve, and show your team's dashboards.
- To sign you in, secure accounts and prevent abuse.
- To bill you and meet tax and accounting obligations.
- To provide support and send service messages (receipts, security and policy notices).
- To find and fix bugs and understand which features get used.
We process Customer Data on behalf of, and as instructed by, the workspace that connected it. We do not sell personal data, do not use it for advertising, and do not use Customer Data to train AI models, ours or anyone else's.
3. Who we share it with
We share personal data only with service providers that help us run the Service, under contracts that limit their use of it to providing services to us:
| Provider | What it handles | Location |
|---|---|---|
| Anthropic (Claude API) | Prompts built from Customer Data, to classify asks, check rules and write code | United States |
| Vercel (hosting) | The app, API and logs | United States and global edge |
| Supabase (database) | The database holding accounts and Customer Data | Japan (Tokyo region) |
| Polar Software Inc. (payments) | Checkout, payment details, billing address, invoices and tax (merchant of record) | United States (cards processed by Stripe) |
We also share data:
- with the tools you connect, when the Service acts there for you (for example opening a pull request on GitHub or posting in Slack);
- with other members of your workspace, who can see the workspace's tasks, rules and, depending on admin settings, the Team meters;
- when required by law, court order or a government authority, or to protect the rights and safety of users and the public;
- with a buyer or successor if our business is merged or sold, who must keep this policy's protections.
4. How we disclose it
Data sent to service providers and connected tools moves over encrypted connections (TLS 1.2 or higher) through their authenticated APIs, and only the data needed for the task is sent: for example, the AI model receives the specific messages and rules it is asked to assess, not your whole workspace. Data provided to authorities is sent only in response to a valid legal request, limited to what the request requires. Some providers process data outside India; we transfer it only as permitted under Indian law.
5. How we protect it
We follow reasonable security practices in line with Rule 8 of the 2011 Rules and international standards such as ISO/IEC 27001, including:
- Encryption in transit (HTTPS/TLS) for all traffic.
- Encryption at rest for databases and backups, and additional application-level encryption (AES-256-GCM) for AI provider keys.
- Read-only access to connected tools by default; write actions, such as opening a pull request, only after a member approves the task. Code is never merged without a human.
- Workspace isolation: every request is checked against the signed-in member's workspace, and only admins can change connections and settings.
- Least-privilege access for our staff, multi-factor authentication on our infrastructure, and audit logs.
- Regular dependency updates, monitoring, and an incident response process that includes notifying affected users and the Data Protection Board of India and CERT-In where required.
6. How long we keep it
We keep Customer Data while the workspace is active. When a workspace admin disconnects a tool, we stop collecting from it; when a workspace is deleted, we delete its Customer Data within 30 days, and from backups within 90 days. Billing records are kept for as long as tax law requires (generally 8 years in India).
7. Your rights
You can ask to access, correct, update or erase your personal data, withdraw consent, or nominate someone to exercise these rights for you. Email support@bruh.computer. If your data is in a workspace another company controls, we'll work with that workspace's admin on your request. Withdrawing consent may mean we can't provide parts of the Service.
8. Children
The Service is for businesses and is not meant for anyone under 18. We don't knowingly collect data from children.
9. Grievance Officer
Akshit Gupta, Akshit Gupta (sole proprietor, trading as bruh.computer). Email support@bruh.computer. We acknowledge complaints within 24 hours and resolve them within 15 days. If you are not satisfied, you may complain to the Data Protection Board of India.
10. Changes
We'll post changes here and update the date above. For material changes we'll also notify you by email or in the app before they take effect.