App store guidelines and API terms change. Know before your next review.

The updated terms materially increase financial obligations and reduce advance notice for subscription users. The 48-hour pre-charge window and explicit liability for failed-payment retry attempts mean users have less time to manage their payment methods before charges occur. The new explicit liability for background data fees from system services significantly expands what users may owe if their devices are actively updating or communicating without active user interaction, a cost that may be substantial in regions with expensive mobile data. The backup payment method authorization without explicit prior consent may violate consumer protection standards in several jurisdictions, increasing risk of chargebacks and regulatory scrutiny.

The updated guidelines establish explicit, enforceable content moderation obligations for developers and introduce app removal as a direct consequence of non-compliance. This clarifies Apple's enforcement authority and creates a formal escalation pathway (notice, plan, removal) that developers must respond to operationally. For developers with user-generated content features or child-focused apps, this change requires proactive content governance infrastructure and compliance response processes.

The updated terms establish a new contractual liability framework for autonomous AI actions. Users are now legally bound by AI-driven actions taken according to their configured settings and must actively manage safeguards, monitor settings, and evaluate output. This creates operational and compliance obligations that require developers to implement approval workflows, cost controls, and human oversight before deploying AI features or third-party integrations. The liability disclaimer for AI-driven consequences shifts risk entirely to users and may create conflicts with downstream customer agreements or regulatory frameworks.

The updated terms establish explicit FTC oversight disclosure and introduce a user-accessible opt-out mechanism for third-party data sharing and materially different uses. These additions operationalize user data control rights and clarify regulatory accountability, which may affect how Twilio customers communicate data practices in their own policies and how data subject requests are processed.

The updated terms establish explicit authority for GitHub to use AI outputs and personal data for AI/ML model training and improvement, and to share this data with affiliates including Microsoft for these purposes. This expands the stated scope of data processing beyond prior language and formalizes a use case (AI model training) that some users may not have anticipated when evaluating how their code and data would be used. Organizations that have made representations to their own customers about code use restrictions or data protection measures should evaluate whether this policy change affects those commitments.