Privacy Policy

Last updated October 13, 2026

1. Who we are

Good Bunny is run by AK | Web development, Kam 53, Ramat HaHayal, Tel Aviv, Israel ("we", "us"). For data about your account, we decide how it's used. For data you or your clients put into the hub, we handle it on your behalf (see our DPA). Questions go to hello@goodbunny.co.

2. What this policy covers

• the website goodbunny.co;
• your account at app.goodbunny.co (the hub);
• the Good Bunny WordPress plugins, where they talk to our servers;
• emails we send you.

3. What we collect

Early-access list. Your email address, the agency name if you give it, which list you joined (launch or AI fix) and when.

Your account. Your email address, your name if you add it, your agency name and logo, the sign-in links we send (stored scrambled and valid for 15 minutes), your active sessions, and a shortened version of the IP address each session started from. Also the page that sent you to sign up (the ref tag in the link), so we know which pages work.

Your sites. For each site you activate: its host name and REST address, WordPress and plugin versions, a fingerprint of the site's connection key, when it last checked in, and counts (guest links created, changes waiting for review, edits applied), the licence status and your guest-link settings. The paid plugin sends these once a day and when you open its licence screen.

Guest links you create from the hub. The page's title, address and WordPress ID, the label you give the link, its expiry date, who requested it, and any client names or emails you type in. The link itself is stored encrypted for at most 24 hours so we can show it to you, then removed.

Billing. Paddle tells us your plan, subscription status, and a Paddle customer ID. Paddle collects your payment details and billing address. We don't receive your card number.

Emails. A log of account emails we sent you (sign-in links, licence, trial and billing notices), so we can see what was delivered.

Support. Whatever you write to hello@goodbunny.co.

Server logs. Cloudflare, which hosts the site and hub, processes IP addresses and request details to deliver pages and block abuse. Our own application logs leave out request bodies and guest-link addresses.

4. What we don't collect

In the current version of Good Bunny, the following are kept on your site and never sent to us:

• the text, links and images on your pages;
• the changes your clients propose, and the before and after text;
• guest names, guest email addresses entered on the site, and notes;
• screenshots attached to issues.

Reports, screenshots, change text and the notices about them go from your own WordPress site, to destinations you or your team set up: e-mail to your team (and a note to a client who left an address for one), your Slack, your Asana, your webhook. None of it reaches us. A site connected to the hub also shares the site records and guest-link details described above.

The main cases:

• E-mail, a report: when the sender ticks Email on it, or when an admin has turned Email on by default under Connections. A report from someone with no destination switches (a client on a guest link, or a signed-in user who cannot review) is e-mailed as well. The screenshot rides inside the message.
• E-mail, a notice to your approvers when a new text change is waiting, whatever the Email switch says. It carries who sent it, the page title and address, how many changes, a link to your inbox, and a guest's typed name if they gave one. Not the change itself.
• E-mail to a client: a note when a change they left an address with goes live. It carries the page address and the name saved under Brand, no change text, no staff names.
• E-mail to the person who made a guest link: one message when someone holding a link asks for a new one. It carries the link's label, the page title and a link to the new-link form.
• Slack, once connected: ticked by default on each report; a reviewer can untick it on the report. Reports from signed-in users who cannot review follow that default. Guest reports never go to Slack. The screenshot rides in the message only when the channel belongs to one company; a shared channel gets the page link only.
• Asana, once connected: a report becomes a task, with the screenshot, when someone who manages Asana sends a report there, or, if you chose "As soon as a report arrives", for each report, guest reports included, before anyone reviews it.
• Webhook, if you set one: a signed-in user's report is posted as JSON to your https address when it is ticked on the report, or, for a sender with no destination switches, when the webhook is on by default. Guest reports are not posted. No screenshot, only whether one was attached.

Sending limits can hold back a message; the report stays in your inbox either way. Slack, Asana and your webhook receive this under your own accounts and setup. None of this passes through our servers.

The free plugin from WordPress.org makes no calls to our servers at all.

5. Hub approval, if you turn it on later

We plan to let you approve changes from the hub as well as from WordPress. That feature needs to store some change content on our servers. It is off until you turn it on for a site, and we will update this policy and ask you on the Connect screen first. When it is on:

• change text (the before and after wording) is deleted 90 days after the change is closed; changes left open are removed from the hub after 180 days;
• screenshots and images your clients upload are deleted 30 days after the change is closed, and never kept longer than 90 days from upload;
• the history of what happened (approved, rejected, undone, and when) is kept without any of the text;
• the record your site needs to undo a change stays on your own site, never on ours.

6. Cookies

goodbunny.co sets no cookies and runs no analytics or advertising scripts. We count visits from Cloudflare's server-side statistics, which don't use cookies.

The hub sets one cookie, to keep you signed in. It is strictly necessary, expires after 14 days of inactivity and 30 days at most, and is not used for tracking. The sign-up and sign-in pages use Cloudflare Turnstile to check that you're human.

7. Who we share data with

We use these service providers (subprocessors). Each one gets only what it needs for its job.

We don't sell personal data, and we don't share it for advertising. We'll disclose data if the law requires it, and we'll tell you when we're allowed to.

8. How long we keep it

Paddle keeps billing records according to its own obligations as merchant of record.

9. How we protect it

Sign-in links and licence keys are stored hashed. Guest-link addresses are encrypted at rest. Files are stored privately and served only after a check that you're allowed to see them. Our logs don't record request bodies. Access to production systems is limited to Alon Katziri.

10. Your choices and rights

You can ask us to show you, correct, export or delete the personal data we hold about you, or to stop using it. Email hello@goodbunny.co and we'll answer within 30 days. You can also complain to the data-protection authority where you live.

Every email we send for the early-access list has an unsubscribe link. Account emails that you need to use the service (sign-in links, billing notices) can't be switched off while your account is open.

11. Your clients' data

Your clients reach Good Bunny through guest links you send. What they type is stored on your WordPress site, which you control. You are responsible for telling your clients how their information is used. If a client asks us about their data, we'll pass the request to you.

12. Children

Good Bunny is a business tool and isn't meant for anyone under 18. We don't knowingly collect data from children.

13. Changes to this policy

If we change this policy in a way that matters, we'll email account owners before it takes effect and update the date at the top. We will update it before any change to what the hub stores, including hub approval (section 5).

14. Contact

AK | Web development · Kam 53, Ramat HaHayal, Tel Aviv, Israel · hello@goodbunny.co