Opt in or opt out: budget caps, text watermarks and device checks all start with a default
Serguey Asael Shinder2 min readYesterday's analysis here was about defaults that caused security problems. Three items from the past few days show the other side: features whose value depends almost entirely on whether they are on before anyone thinks about them.
Spending. In a post on 3 October, Simon Willison argues that pay-per-use services need hard budget caps, a limit after which the service returns errors instead of billing, and that they must be on by default. Soft caps that only send a warning email do not help someone whose agent-built service runs all night. Removing the cap should be a deliberate, clearly labelled choice. He notes that AWS began offering monthly spend limits that pause a project to a limited set of customers in September, and that Google Cloud launched spend caps on specific services in July. His case rests on coding agents: they make it cheap to start things that cost money, and the person running them may not know what they started.
Provenance. OpenAI's plan for the EU AI Act chooses defaults by region. ChatGPT and Codex text in the EU will carry an invisible watermark for everyone; in the API, watermarking is off unless the customer opts in. OpenAI is candid that detection weakens quickly when a text is edited, which is a reason to be careful with defaults in either direction.
Access. AWS Client VPN's device-posture checks ship with a monitoring-only mode that logs what a policy would block without disconnecting anyone. That is a default designed for the moment of adoption: it lets a team see the cost of enforcement before paying it.
What connects them. In each case the safe behaviour exists, and the question is who has to act to get it. A cap that must be switched on protects people who already know they need it, which is the group that needs it least. The useful pattern in the AWS VPN feature, a mode that shows consequences before enforcing them, is a reasonable way to make a strict default tolerable rather than leaving the protection to whoever reads the settings page.