Where your content lives, how to get it out, and what we commit to if Duggie ever shuts down.
Effective August 18, 2026
If you build a site for a client and put its content here, you are asking that client to depend on a service you do not run. It is a fair question to ask what happens to their site if we stop, and you should not have to take our word for the answer. Most of this page describes things you can check for yourself today.
Every published asset in a project is retrievable right now, as JSON, from the same public API that serves your live site. It is the endpoint your site already calls on every page load, and the key you already hold is the one that reads it. There is no separate export to request and nothing to wait for.
That means the content behind a site you have handed off is never locked inside an interface. It is a normal HTTP request returning a normal JSON document, and anything that can read JSON can read it. Our API reference shows the exact call.
A project can be transferred to the person who owns the site. Ownership moves, billing moves with it, and the site keeps serving throughout: no downtime, no key rotation, nothing to reconnect. You can stay on as an admin so you can still help, or leave entirely.
This matters for continuity as much as for billing. A client whose project is in their own account is not depending on your relationship with us, or on you still being reachable in three years.
When a paid project slot is cancelled, the project it was paying for moves back to the free tier rather than being switched off. It keeps serving content, on free tier limits. A project is only archived when there is no free tier place left for it to occupy, and the account owner is emailed before that happens, with the name of the project and the date.
We will email every account owner at least 90 days before the Service stops. For the whole of that period everything keeps working as it does today: your projects stay published, your API keys stay valid, and your content stays retrievable through the public API.
This is a term of the agreement rather than a statement of intent. It is written into section 6 of our Terms of Service, which is the binding version of it.
We would rather be exact than reassuring, so it is worth being clear about the edges of this. We do not commit to a guaranteed uptime level, and we do not currently publish a self-hostable version of the delivery API. If the Service ended, your content would be yours and retrievable, but you would need somewhere else to serve it from.
If that changes we will say so here. If you are weighing this up for a particular client and want to talk it through, get in touch.