Stripe Billing
Vannus has not established which model this vendor runs, and does not infer one. Every finding below is quoted to the vendor’s own document, or marked not disclosed where the vendor publishes nothing.
Usage-based billing infrastructure — metering, invoicing, and subscription management for hybrid pricing models with action-based tiers, inference credit tracking, and enterprise contract support
AI models trained on billions of data points across Stripe's payments network
Training and retention posture varies by plan. What we publish above describes the vendor’s default plan; enterprise, team and API agreements frequently differ, often materially, and a contract can override the published default entirely. Check your own plan and contract before relying on this row.
This is a separate question from the grade above. The grade measures resilience — whether the tool endures and whether you could leave it. This describes who controls the vendor. A tool can score modestly on one and strongly on the other, and many do.
On U.S. CLOUD Act reach specifically: the statute reaches a provider subject to U.S. jurisdiction over data in its possession, custody or control. Corporate control is a strong indicator of that and it is what we can evidence from published documents — but it is not the whole test. A company founded outside the U.S. can still contract through a U.S. entity or run substantial U.S. operations. Treat this as a starting point for your own review, not a legal determination, and take advice on anything that matters.
The vendor's published or catalog-recorded posture — the concrete facts this grade is built from. A full audit verifies each against the vendor's current documentation.
Stripe Billing publishes a list of the other companies it uses to process customer data. It names 50 of them in 51 entries, because some appear more than once under different locations, each shown below with the location the vendor lists it under, in the vendor’s own words.
Taken together those entries name at least Australia, Belgium, Canada, Colombia, Germany, Hong Kong, India, Ireland, Japan, Luxembourg, Malaysia, Philippines, Poland, Sweden, United Kingdom, United States. That is what our place list could match in the vendor’s own words above, so treat it as a floor rather than the whole of it — the entries themselves are the record.
These are other companies, not Stripe Billing. Where a sub-processor is listed as operating is a fact about that company. It is not a statement about where Stripe Billing keeps your data, which Vannus publishes separately and only from a document in which the vendor says so.
The same document also lists 31 companies in Stripe Billing’s own corporate group. Those are the vendor itself rather than onward processors, so they are not among the entries above and are not counted in them.
Read from stripe.com on 2026-09-16. Every entry above is a verbatim span of that page.
This is the vendor’s own disclosure, reproduced. Vannus has not audited what any of these companies do with your data, and a list can change without notice. Treat it as a starting point for your own review, not a legal determination, and take advice on anything that matters.
Taken from the vendor’s own published material. Vannus does not hold these reports and has not reviewed their scope or dates — ask the vendor for the current report before relying on any of them.
Vannus publishes a nine-dimension trust framework — data sovereignty, training privacy, compliance posture, operational resilience, exit portability, and more. The heaviest criterion asks whether the tool builds its own AI or resells someone else's model; where the vendor discloses it, the grade cites the vendor's own documentation. No paid placements — scoring is walled off from affiliate revenue. See the methodology →