Legal

Draft, not legal advice; lawyer review before publish. Updated 14/09/2026

NIP 9671492331 · ul. Władysława Pytlasińskiego 16/13, 00-777 Warsaw · VAT PL9671492331

Terms of Service

Company: Beamer, a sole proprietorship registered in Poland ("we", "us", "our") Service: Defusor Website: defusor.beamercloud.com Tax ID (NIP): 9671492331 VAT Registration: PL9671492331

These Terms of Service ("Terms") govern your use of Defusor. By creating an account, purchasing, or using the service, you agree to these Terms.

1. Service Description

Defusor estimates Vacuum Effort (what the work should cost with the right architecture: right domains, right boundaries, no coupling, no coordination) versus current cost under your architecture, and names the sync tax (the difference). Numbers are rolled up by calendar quarter.

You are billed monthly. The report is a quarterly PDF, emailed once per calendar quarter, not each time you are invoiced. The first report is the diagnosis after the first paid invoice and uses up to five years of history. Later reports are once per calendar quarter.

What we do:

Provide an account (Google or email+password). The first signup also creates your company record. The company is the billing customer
Let you confirm a payment method (you are not charged yet), then set up: link GitHub repositories (read-only GitHub App) and enter a loaded engineering hourly rate
Count git contributors who committed to the selected product repositories in the latest month, show you the count and this month’s amount, then charge the subscription and start the first analysis
Email the first PDF after that first paid invoice, then one PDF per calendar quarter while the subscription is active

What we don't do:

We don't write to your repositories
We don't provide consulting or implementation unless separately agreed
We don't guarantee that every coordination cost is captured, or that acting on the report will improve the organization

Analysis typically takes minutes to hours, not minutes guaranteed. The production ceiling for a run is three hours. A run can stop if it stalls or hits an operational analysis spend limit.

2. Customer Obligations

You agree to:

Register with accurate information and keep the account under your control
Ensure the person who links GitHub has authority to grant those repositories
Pay the fees shown at checkout
Not use the service to analyze repositories you do not own or lack permission to analyze
Not attempt to reverse-engineer the analysis methodology

The company is the customer. The person who signs up holds the account (MVP: one user per company). A tech leader typically links GitHub and provides the hourly rate; a CEO typically reads the report. In MVP that is often the same person.

3. Data Handling

3.1 What We Access

After you confirm a payment method and link GitHub, and before the first charge, we select the product repositories from your GitHub grant, then read committer identity data on that subset to count git contributors for billing (identity count only, latest month). No repository history is fetched until the first paid invoice. After that invoice, we fetch git history from that grant (a bare copy of the repository objects, not a checkout of your working files) onto ephemeral disk for the analysis job, then extract analysis data. During the job we process commit history and patches for evolution tracking (including topology and runtime contracts derived from those diffs, such as CI configs, deploy manifests, and API specs), pull requests, reviews, issues, and contributor identifiers. We do not check out or store your current source tree as files. If you grant all repositories, that grant includes repositories created later on that GitHub account or organization.

We do not:

Push, merge, or otherwise modify your repositories
Use GitHub as your product login

Details: Privacy Policy.

3.2 What We Store

We store:

Your account identity (via Clerk) and our user/company records
Stripe customer and subscription identifiers on the company
GitHub installation id and granted repositories
The extracted git dataset, fitted parameters (k), labor rate R, run state, and the detected engineer count used for billing
PDF reports and related analysis artifacts

Working copies of git repositories exist only for the duration of an analysis job.

3.3 Data Retention

Analysis data, PDFs, prompt logs, and account records: for the life of the paid subscription, then 90 days after it ends, then deleted
Payment records: retained by Stripe as required for tax (typically 7 years)
Early deletion: email [email protected]

3.4 Data Security

TLS 1.2+ in transit; encryption at rest on the providers we use
Access to customer data is restricted to authorized personnel
Processors and locations are listed in the Privacy Policy. Data is not stored only in the EU

4. Payment Terms

4.1 Pricing

The service is paid subscription only. There is no free tier. The price is a unit price multiplied by the number of git contributors detected on the product repositories we selected (committers in the latest month), re-measured monthly. The invoice amount varies with the detected count. Contributors do not receive accounts or access. The count measures the people whose commits we analyze, not seats. Amounts are shown to you before the first charge, in the currency shown by Stripe.

You are billed monthly. Paying a month does not mean a new report that month. Report delivery is described in §1.

4.1.1 VAT and Taxes

EU customers: Prices are subject to Polish VAT (currently 23%). If you are a VAT-registered EU business, provide your EU VAT number and we will apply reverse charge (0% VAT on the invoice) where Stripe Tax does so.
Non-EU customers: No Polish VAT. You are responsible for local taxes.
Invoices include our Polish tax ID (NIP) and EU VAT number where applicable.

Stripe Tax (Basic) calculates tax where we have an active registration. No tax is collected in a jurisdiction until that registration exists.

4.2 Payment Due

Payment is due according to the Stripe subscription (typically monthly in advance). The subscription renews until you cancel.

Linking repositories happens after you have confirmed a payment method and does not itself charge you. We count git contributors on the selected product repositories, show you this month’s amount, then charge and start the first analysis when GitHub is linked with access to all repositories and the hourly rate is set. If you never finish that setup, you are not charged. Each month you can continue or cancel before the next month is billed. There is no minimum term.

4.3 Refund Policy

No refunds for partial billing periods. Cancel anytime in the Stripe Customer Portal; access to paid features continues until the end of the period already paid.

4.4 Failed Payments

If a subscription payment fails, Stripe retries. We stop enqueueing analysis runs while the subscription is not paid. Analysis data and PDFs follow the 90-day retention in §3.3 after the subscription ends.

5. Intellectual Property

5.1 Your Property

You retain all rights to your source code and repositories
You own the reports we generate for you
You can use, share, and distribute your reports

5.2 Our Property

We own the analysis methodology, software, and report templates

5.3 License to Access

You grant us a limited, revocable, non-exclusive license to:

Access the GitHub repositories granted via the GitHub App
Process that data to generate reports and operate the account
Store data as described in Section 3 and the Privacy Policy

This license ends when you uninstall the App, cancel and the retention period expires, or you request deletion.

6. Limitations of Liability

6.1 No Guarantees on Accuracy

Figures are estimates from observable git and GitHub data plus a fitted model. We do not guarantee absolute accuracy or that recommendations will improve the organization. Labor rate R is an input you configure in the app.

6.2 No Liability for Business Decisions

You are solely responsible for decisions made from the reports. We are not liable for organizational changes, personnel decisions, or financial losses arising from the analysis, or for any indirect, incidental, or consequential damages.

6.3 No payment by Beamer

Beamer does not pay the customer. Nothing in these Terms excludes liability that cannot be excluded under mandatory law.

6.4 Service Availability

We do not guarantee uninterrupted service. We are not liable for downtime of GitHub, Stripe, Clerk, cloud providers, or email, for scheduled maintenance, or for force majeure.

7. Cancellation

Cancel anytime in the Stripe Customer Portal. Cancellation takes effect at the end of the current billing period. After that period, we stop further invoices and report emails. Data retention follows §3.3.

We do not provide pro-rated refunds for partial periods.

8. Dispute Resolution

8.1 Informal Resolution

Contact [email protected]. We will work to resolve the issue within 30 days.

8.2 Arbitration

If informal resolution fails, disputes will be resolved through binding arbitration under the Arbitration Rules of the Stockholm Chamber of Commerce (SCC). Seat: Stockholm, Sweden. Language: English.

8.3 Class Action Waiver

You agree to resolve disputes individually and waive class actions or class-wide arbitration.

9. Governing Law

Polish law, without regard to conflict-of-law principles. For EU consumers, mandatory consumer protection laws of your country of residence may also apply.

10. Changes to Terms

We may update these Terms. We will email you at least 30 days before material changes take effect. Continued use after that date is acceptance.

11. Contact Information

Beamer Sole proprietorship registered in Poland NIP: 9671492331 EU VAT: PL9671492331

Email: [email protected]
Privacy: [email protected]
Address: ul. Władysława Pytlasińskiego 16/13, 00-777 Warsaw

12. Entire Agreement

These Terms and the Privacy Policy are the entire agreement for the service. If a provision is unenforceable, the rest remains in effect.