Skip to main content
Annex III to the ohmyho.st DPA. Version: September 13, 2026. The contracted entity and applicable service terms govern each engagement.

​
Customer-workload subprocessors

The selected capabilities determine which providers receive workload data. Provider data-centre, support and onward-processing arrangements are not established solely by selecting a region. Subprocessor changes follow the notice and objection procedure in the DPA.

​
Account, business and customer-selected services

WorkOS supports ohmyho.st account identity and authorisation. Stripe handles enabled payments and billing. GitHub supplies authorised source repositories. They process relevant account/business data in the roles set out in their applicable terms and our Privacy notice; they are not automatically recipients of every customer’s application database or files. WorkOS DPA · Stripe DPA. A customer’s own auth provider, coding agent, automation service or external integration is selected and contracted by that customer unless expressly included in an ohmyho.st order. Transfer safeguards · Privacy notice · Contact form