Deleting your account.

From the app

Open Settings and tapDelete account. That is the whole thing — there is no form to fill in and nothing to wait for.

It removes the lot: the account, its hooks, its devices, and the requests they hold, including any request bodies kept in object storage. Deleting a hook stops its URL working, so anything still posting to it will start getting an error rather than reaching anybody.

If you cannot open the app

Write to[email protected]from the e-mail address attached to the account. We will delete it and reply when it is done.

If you never attached an e-mail address, we cannot do this for you, and we would rather say so than pretend otherwise. zhooky lets you start without signing up: that account's only identifier is the installation on your phone, so an e-mail from anybody — including you — carries nothing we could match it against. Deleting the app does not delete the account either; the data stays until something deletes it.

Two ways out. Reinstall the app, open it, and if your account comes back, delete it from Settings. Or attach an e-mail address while you still have the app — that is what gives you a route that does not depend on the phone.

Deleting part of it, without deleting the account

You do not have to choose between everything and nothing, and all of this is in the app:

• Delete a hook and its requests go with it, stored bodies included. Its URL stops working at the same moment.
• Remove a device and its push token is deleted, so nothing can reach that phone again.

What we keep, and why

Everything attached to the account goes with it: the hooks, the devices, the requests and their stored bodies, the usage counters, and the subscription record.

One thing stays, on purpose: the log of what a payment provider told us. Every notification a provider sends — RevenueCat for purchases made in the app, Polar on the web — is recorded once when it arrives, so that a billing question months later has an answer rather than a shrug. Deleting your account clears those rows' reference to it, but the provider's own message is kept as it arrived, which means it still contains whatever identifiers the provider put in it. Only an administrator can read that log, and only for that purpose; nothing a user sees touches it.

That log has no expiry — nothing deletes it on a schedule, so treat it as kept indefinitely. If you never paid for anything, there is no such record and nothing is kept.

Requests expire on their own even without a deletion: 7 days on the free plan, longer on a paid one — the pricing page carries the figure. Deleting a hook, or the account, removes them at once instead of waiting for that.

See the privacy policy for what we collect in the first place and why.