OpenAB Connect · last updated 21 August 2026
OpenAB Connect collects nothing. There is no account, no analytics, no crash reporting, no advertising and no telemetry of any kind. We operate no server that the app contacts.
That is the whole policy. The rest of this page explains what the app does with the data it necessarily handles, because "collects nothing" is worth substantiating rather than asserting.
Authorization header, and
never anywhere else. The app does not transmit, back up or sync them.Outbound only, and only to endpoints you configure: your own runtime, and — if you use the ECS deployment path — Amazon's APIs on your behalf. The app contacts no other host. It has no update service, no licence check and no beacon.
None. We have no servers, no database and no logs relating to your use of the app. If you email us for support, we receive whatever is in your email and nothing else; see Support.
The app bundles the kubectl and ecsctl command-line tools so it
can deploy into infrastructure you already own. They run inside the app's sandbox and talk
only to the cluster or account you point them at.
The container images the app deploys are built from
openabdev/openab-pty and, for every
variant except native, include a third-party coding CLI whose own terms and
privacy practices are set by its vendor, not by us. What that agent does with your code or
prompts is between you and that vendor.
The app is a developer tool and is not directed at children.
If this policy changes, the date above changes with it, and the previous versions remain in the page's git history rather than being quietly replaced.