May 2026
Our promise
If we ever remove a feature you depend on, we will give you at least 6 months’ notice, keep it working during that time, and help you migrate. We will not leave you stranded.
What this covers
This policy applies whenever we remove a feature from our product, change a feature in a way that breaks how you use it, or discontinue a product entirely.
What counts as a breaking change: Any change to a documented API contract, configuration schema, or product workflow that requires you to take action to continue operating normally.
Not covered: Beta or preview features, which are labeled as such in the product and in our release notes. Security fixes that require us to disable something quickly to protect you are also not covered (see below).
If a feature’s status is unclear, contact your account team.
How much notice you’ll get
We will tell you at least 6 months before a feature stops working. The notice will reach you in three places: an email to your account’s primary contact, a notice on our help site, and a banner in the product itself wherever the feature is used. The notice will include the exact date the feature will be removed, why we are removing it, and what to use instead.
During those 6 months the feature continues to work exactly as it does today. We will not degrade it, and we will continue to fix any bugs that affect you.
Security exception: In rare cases a security vulnerability may require us to disable a feature immediately. We will notify you within 24 hours, explain the reason, and — once the issue is resolved — restore the feature or provide a clear path forward.
How we’ll help you migrate
In most cases, the feature we are sunsetting is being replaced by something better that we are already shipping. We will publish a migration guide and answer your questions directly. If your migration is non-trivial, we will get on a call with you and work through it together. There is no charge for this — it is part of being a good vendor.
If you need more time
Sometimes 6 months is not enough — you may have a long planning cycle, a regulated environment, or a coupled system that needs to change with us. If that happens, contact us as soon as you know. We will confirm in writing within 10 business days whether an extension is possible, and work out a plan with you. This may include keeping the feature running for your account specifically while you complete migration. We have not yet met a customer for whom we could not find a workable answer.
Policy governance
This policy is owned by the ZEDEDA Product Management team and reviewed annually. Enterprise customers may negotiate specific sunset protections in their Master Subscription Agreement (MSA); where an MSA provision conflicts with this policy, the MSA governs. If we make a material change to this policy that reduces customer protections, we will provide 90 days’ notice before the change takes effect.
Questions?
Email us at support@zededa.com or talk to your account contact.