Deprecation policy.
How much warning you get before something changes under you. Written as notice periods rather than intentions, because an intention is not something you can plan a sprint around.
Effective 10 October 2026. These terms take effect when OpenPush opens to the public. They are published now so you can read them before deciding whether to sign up, and so any change between now and then is visible rather than sprung on you. If you need contractual certainty sooner, email legal@openpush.ai and we will deal with you directly.
These notice periods are proposed, not yet ratified. They are the windows we intend to commit to, published now so you can tell us if one of them would not work for your team. They become binding on the effective date at the top of this page.
The notice periods
| Change | Notice | How you hear |
|---|---|---|
| Removing or renaming an API endpoint or field | 90 days | Email to account admins, changelog, and a deprecation header on the response |
| Breaking change to existing API behaviour | 90 days | Email, changelog, and a dated entry here |
| Retiring a console feature | 60 days | Email and an in-product notice |
| Moving a feature between the free and paid tiers | 90 days, and never for an account already using it | Email to account admins |
| Tightening a published rate or fair-use limit | 30 days | Email to affected accounts only |
| Adding a subprocessor | 30 days, with a right to object | The subprocessors page and email |
| Discontinuing OpenPush entirely | 180 days, with export working throughout | Email, this page, and the console |
What we will do without notice
Ship fixes, add things, and act immediately on a security or abuse emergency. Adding a field, adding an endpoint, or making something faster does not need a 90-day countdown, and neither does closing a hole someone is actively exploiting. If we take emergency action that affects you, you hear about it as soon as the emergency is over rather than before.
What never changes without your account being carried over
The binding parts of the free-forever pledge in the Terms are not on this table, deliberately. The 1M MAU per-app ceiling does not shrink for an account already using it, we do not start charging per subscriber, and export stays free. A deprecation policy is for features. Those are not features.
How to be told
Account admins are emailed automatically — you do not have to subscribe to anything. If you want deprecation notices going to a shared inbox or an on-call rota instead of a person, email hello@openpush.ai and we will point them wherever you like.
If a notice period here would genuinely not be enough for your release cycle, tell us that now rather than during a migration. We would rather set the number correctly once.
SuperTuned Inc
1 Sansome Street, San Francisco, CA 94104, USA
Privacy: privacy@openpush.ai · Legal: legal@openpush.ai · Security: security@openpush.ai