Legal
Privacy Policy
This Privacy Policy explains how Brew studio [sole proprietorship] (Brew Studio, we, us, our) collects, uses, discloses, and protects personal information when you visit brew.studio, use our applications and services (together, the Services), or otherwise interact with us.
Brew Studio provides AI-assisted impact analysis for software teams by helping you analyze the “blast radius” of change requirements across UI, code, and data, and by integrating with developer tools such as GitHub to link multiple repositories into a single project. (brew.studio)
If you do not agree with this policy, please do not access or use the Services.
1) Who is responsible for your data?
Controller: For website visits, account signup, billing, marketing, and support data, User of Brew studio is the data controller under GDPR.
Processor: For repository/source-code content that customers upload or sync to Brew in connection with a paid workspace, we act primarily as a data processor on your instructions (see §6).
Contact: support@brewstudio.in
2) Scope & audience
This policy covers:
Site visitors to brew.studio and related pages,
Users of Brew web apps and APIs,
Workspace owners/admins and their team members,
Individuals who contact us for support, events, or sales.
Regional disclosures are provided for GDPR (EU/UK) and India’s Digital Personal Data Protection Act, 2023 (DPDP Act). The DPDP Act received Presidential assent in Aug 2023, and draft implementing rules were published in Jan 2025; final rules were expected around late September 2025. We will follow applicable provisions as they come into force.
3) What we collect
A) Account & contact data
Name, email, password (hashed), profile photo (optional), organization, role/title, authentication logs, and communications with us (support, feedback).
B) Workspace & team data
Workspace name/ID, plan, members and roles (RBAC), invitations, audit logs, settings, and usage metrics (e.g., features used, performance telemetry).
C) Repository & project data (“Developer Content”)
Repository metadata (repo names/IDs, branches, file paths, commit hashes), pull/merge request metadata, issue/PR links, and code graph adjacency.
Source code that you instruct us to sync for analysis.
We do not intentionally ingest environment variables or external secrets/config files; our sync only reads source code and selected metadata necessary for analysis. (You can restrict scopes in your Git provider.)
Connection details and tokens required to integrate with GitHub or other developer tools (stored encrypted; rotated per best practice).
D) Device & usage data
IP address, device/OS/browser type, pages viewed, timestamps, referrers, basic telemetry, and coarse geolocation derived from IP, collected via cookies or similar technologies (see §10).
E) Billing data (if applicable)
Billing contact, company details, tax/VAT, and transaction identifiers via our payment provider(s). We do not store full payment instrument numbers on Brew systems.
F) Support & survey data
Issue reports, reproduction steps, email or chat transcripts, satisfaction ratings, and interview notes when you consent to research.
G) Job applications (if applicable)
Resume/CV, links you provide, and information shared during interviews.
We do not seek to collect sensitive personal data (e.g., health, religious, biometric) and do not knowingly collect children’s data (§17).
4) Sources of data
Directly from you (forms, settings, API calls),
From your organization admin (provisioning users),
From integration providers you authorize (e.g., GitHub) to pull code/metadata needed for impact analysis,
From cookies/telemetry (site/app analytics).
5) Purposes & legal bases (GDPR)
| Purpose | Typical data | Legal bases |
|---|---|---|
| Provide & secure the Services (auth, RBAC, audit logs, code sync, analysis runs) | A–D | Contract (Art. 6(1)(b)); Legitimate interests in security & service quality (Art. 6(1)(f)) |
| Run analysis and deliver insights (impact graphs, change risk) | C | Contract; Legitimate interests |
| Customer support, incident response | A, F | Contract; Legitimate interests |
| Improve performance & reliability; detect abuse | B–D | Legitimate interests |
| Billing & account management | E | Contract; Legal obligation |
| Product updates, service notices | A | Legitimate interests; Contract |
| Marketing communications (opt-in/opt-out) | A | Consent; Legitimate interests |
| Compliance (tax, legal, audits) | A–E | Legal obligation; Legitimate interests |
Where consent is used, you can withdraw it any time via in-product settings or by contacting us.
6) Developer Content & repository data
We only access repositories and code that you explicitly connect and authorize.
Code and repository metadata are processed to provide impact analysis and related features you request.
We do not use your private code to train general-purpose AI models without your explicit permission.
Config files and environment variables: Brew’s sync is designed to read source code; we do not intentionally ingest env/config/secrets from external stores.
You can disconnect integrations at any time; upon disconnection or workspace deletion, we cease new syncs and follow the retention policy (§12).
7) Security measures
We apply administrative, technical, and physical safeguards appropriate to the risk, including:
Authentication & session protection (OWASP ASVS A2/A3): JWT-based auth, secure cookie flags, session hardening, MFA options where enabled.
Access control (A4): Role-based access control (RBAC) for teams, least-privilege service roles, and scoped API tokens.
Input validation (A5) and secure defaults to mitigate injection and deserialization risks.
Data protection (A8): TLS in transit; encryption at rest for personal data and Developer Content; key management with strict separation of duties.
Configuration (A14): Infrastructure as code, secrets management, image-scanning, and baseline hardening.
Network boundary & monitoring: We operate in a VPC with egress controlled; public access is fronted by AWS CloudFront and AWS WAF; rate-limiting, anomaly detection, and audit/event logs support monitoring (SOC 2 CC6/CC7 alignment for logical access, change management, and logging).
Third-party security: Due diligence and contractual controls for vendors; subprocessors listed in §9.
8) International transfers
We may process data in countries where we or our subprocessors operate. Where GDPR applies and data is transferred outside the EEA/UK, we use appropriate safeguards such as Standard Contractual Clauses (SCCs). For India, we monitor DPDP Act rules on cross-border transfers and will comply as they come into force.
9) Sharing & subprocessors
We share personal data only as necessary to provide the Services, comply with law, or with your direction:
Cloud infrastructure & security (e.g., Amazon Web Services for hosting, CDN, and WAF).
Authentication / email / observability / analytics providers (limited to what’s necessary).
Payment processors (for subscriptions).
Integration providers you connect (e.g., GitHub or Jira)—data exchange is per your authorization.
Professional services (legal, accounting) under confidentiality.
Change of control (merger/acquisition) with notice where required.
We maintain a Subprocessors page and Data Processing Addendum (DPA) for customers upon request.
10) Cookies & analytics
We use necessary cookies, and may use privacy-respecting analytics to understand product usage. You can control cookies via your browser. If we use third-party analytics, they will be listed on our Subprocessors page (§9).
11) Your rights
Depending on your region (e.g., EU/UK GDPR; India DPDP Act), you may have the right to:
Access, correct, or delete your personal data,
Port your data,
Restrict or object to certain processing,
Withdraw consent (where used),
Lodge a complaint with a supervisory authority (e.g., your local data protection authority).
Requests can be made via support@brewstudio.in or in-product controls. For Developer Content where we act as processor, please contact your workspace admin first; we’ll support them in fulfilling your request.
12) Retention & deletion
We retain personal data only as long as needed to provide the Services, fulfill contractual/legal obligations, resolve disputes, and enforce agreements. Typical examples:
Account data: kept for your subscription and a short period after closure (90 days) unless legal retention requires longer.
Developer Content: retained for the duration of the workspace; upon deletion request or contract end, we delete or irreversibly anonymize within 7 days, subject to backups that age out on a rolling schedule [up to 30 days].
Audit logs & security telemetry: retained 6 months for security and compliance.
13) Data we don’t sell
We do not sell personal data. We do not serve interest-based advertising in our product.
14) Automated decision-making
We do not engage in solely automated decisions that produce legal or similarly significant effects. Our AI features provide assistance and insights; humans (you/your team) decide what to adopt.
15) Legal disclosures & requests
We may disclose data where required by law or valid legal process, after assessing the request and notifying affected customers where legally permissible.
16) Marketplace & integrations
If you install a Brew integration from ecosystems like Atlassian Marketplace or connect third-party tools, the provider’s terms and privacy notices also apply. We encourage reviewing each provider’s permissions and scopes.
17) Children’s privacy
Our Services are not directed to children under the age of 16 (or as defined by local law). We do not knowingly collect data from children. If you believe a child has provided personal data, contact support@brewstudio.in for deletion.
18) Changes to this policy
We may update this Policy to reflect changes to our practices or legal requirements. We will post updates here and revise the “Last updated” date. For material changes, we’ll provide additional notice (e.g., in-app or email).
19) Contact us
Brew studio (sole proprietorship)
Address: A2/401, Kumar shantiniketan phase 1, Pashan, Pune, Maharastra, India - 411021
Email: support@brewstudio.in
For GDPR requests: include “GDPR Request” in the subject line.
For DPDP requests: include “DPDP Request” in the subject line.
Security & compliance mapping (informational)
OWASP ASVS: A2 (Authentication), A3 (Session Management), A4 (Access Control), A5 (Validation), A8 (Data Protection), A14 (Configuration) reflected in §7 controls.
SOC 2 (CC6/CC7): Logical access, change management, monitoring/logging addressed via RBAC, key management, rate-limiting, audit logs, and SIEM/monitoring (§7).
GDPR/PII: Data flows documented (§3–6), legal bases (§5), retention (§12), user rights (§11); encryption at rest/in transit and access logs (§7).
India DPDP Act, 2023: We’ll comply with operative provisions as notified (consent, notice, rights, breach reporting, cross-border transfer).

