Privacy

Breakpoint Engine is owned and operated by GraphGrid, Inc., which is the data controller for the services described here. The governing policy is the GraphGrid, Inc. Privacy Policy; this page summarizes how it applies to Breakpoint Engine.

Breakpoint Engine is a computation service. The capitalization table and valuation assumptions you send are read for the call that uses them and held in memory while the engine works — an interactive scenario holds that working state in memory for the life of the transaction. Your cap table and your valuation source documents stay in your custody, where you own and manage them. What the service keeps afterwards is listed below.

The result of a call you were charged for

Every billed solve is written to storage before your account is charged: the exact result that was handed back, together with the settlement it was billed under. That is what stands behind the billing guarantee on Pricing. Ask the identical question again in the same session — or retry after a dropped connection — and the stored result is returned under the original charge, so one answer costs one engine run and one settlement.

Because what is kept is the computed answer, it names the share classes your question named and carries the values the engine worked out for them. The arguments you sent are recorded next to it as a digest: a fixed-length fingerprint computed from them, which is what lets the service recognize an identical request.

Each stored result is associated with the account identifier that was billed for it, and it is served back to that account. It answers requests for 48 hours; after that it reads as absent, and the storage bucket holding it deletes objects on a two-day rule.

Your MCP session

The hosted service runs across several instances, and your AI client's follow-up requests can arrive at any of them. The parameters your client sends when it opens an MCP session — protocol version, client name and version, and the capabilities it declares — are stored so the session can be rebuilt on whichever instance receives the next request. That is what keeps a working connection alive across scale-outs, restarts, and deploys. It lives in the same storage as delivered results and is deleted on the same two-day rule.

Account, billing, and operations

Signing in creates an authentication record with Auth0, the identity provider for Breakpoint Engine. Your account there carries the Stripe and Metronome customer identifiers that connect you to your credits. Buying a credit pack creates a Stripe customer and the payment records that go with it. Each billed call adds an entry to the Metronome usage ledger — the account, the job identifier, a timestamp, and the work units and cents charged — which is what your usage data is drawn from and what makes any charge auditable back to the call that produced it.

The service also writes operational logs: startup and configuration events, storage and billing failures, and request-level errors. These are how a healthy service is told from a broken one, and how a billing incident gets reconstructed. Security logging covers authentication decisions, including a request that presents a valid token for one account while asking to use an MCP session that belongs to another. Requiring a funded balance before any solve runs is the service's primary abuse control.

Authentication records, billing records, and operational and security logs are retained under the governing GraphGrid, Inc. Privacy Policy and the retention practices of the providers named above.

Contact: privacy@graphgrid.com