Data Processing Addendum (summary)
Last updated October 13, 2026
1. Parties and roles
This addendum is part of the Terms of Service between you (the agency, "customer") and AK | Web development ("we"). For personal data you put into the Good Bunny hub, you decide why and how it's used, and we process it only to run the service for you. For data about your own account and billing, see the Privacy Policy.
2. What we process for you
| Category | Examples | Whose data |
|---|---|---|
| Agency users | Email, name, shortened session IP | Your staff |
| Account settings | Agency name, logo | Your business |
| Client contacts you type into the hub | Client names and email addresses | Your clients |
| Site records | Host name, REST address, WordPress and plugin versions, key fingerprint, last check-in, licence status, guest-link settings | Your sites |
| Page references | Public page ID, title and address | Your sites |
| Guest-link records | Label, expiry, requester email; the link itself encrypted for at most 24 hours | Your staff and clients |
| Counts | Guest links created, changes waiting for review, edits applied | None (numbers only) |
Purpose: running the account, licences, guest links, white-label settings and account emails. Nothing else.
3. What is never sent to us
In the current version, these are kept on your site and are never sent to us:
- page content (text, links, images and builder data);
- the changes your clients propose, and the before and after text;
- guest names, emails entered on the site, and notes;
- screenshots;
- the record your site keeps so a change can be undone.
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 page references, guest-link records and counts listed in section 2.
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.
4. If you turn on hub approval later
Approving changes from the hub needs some change content on our servers. It's off by default. Before it can be turned on for a site we'll update this addendum and ask on the Connect screen. When it's on, retention is fixed:
| Data | Deleted |
|---|---|
| Change text (before and after) | 90 days after the change is closed. Open changes leave the hub after 180 days |
| Screenshots and client uploads | 30 days after the change is closed, and no later than 90 days after upload |
| Commands and receipts between hub and site | 30 days |
| History events | Kept, with no text in them |
| Undo record | Never stored by us. It stays on your site |
5. Subprocessors
| Subprocessor | Purpose | Location |
|---|---|---|
| Cloudflare, Inc. | Hosting, database, private file storage, DNS, bot checks, email forwarding | |
| Resend | Sending account emails | |
| Paddle | Checkout, billing and tax, as merchant of record | |
| Asana | Only if you connect it: receives issues from your site | |
| Slack | Only if you connect it: receives reports from your site | |
| Support email to hello@goodbunny.co |
We'll give at least 30 days' notice by email before adding a subprocessor that handles customer data, so you can object. If we add an AI provider for a future feature, it's listed here before that feature handles any of your data.
6. Security
- Sign-in links are single use, valid for 15 minutes and stored hashed.
- Session cookies are HttpOnly and Secure, with a 14-day idle and 30-day absolute limit.
- Guest-link addresses are stored encrypted and removed after at most 24 hours.
- Logos and files sit in private storage and are served only after an ownership check.
- Logs leave out request bodies and guest-link addresses.
- Licences are signed, so the plugin can check them without calling us on every page.
7. Retention and deletion
Retention follows section 8 of the Privacy Policy. When you close your account, we delete the data in section 2 within 30 days. Database backups roll over within 30 days. Changes already applied to your sites stay there; they're your WordPress content.
8. Breaches
If we become aware of a breach affecting your data, we'll tell you without undue delay and within 72 hours, with what we know and what we're doing about it.
9. Your instructions, audits and requests
We process your data only as these terms and your use of the product direct. We'll help you answer requests from people whose data you hold, and give you the information you need to show your own compliance.
10. Contact
AK | Web development · Kam 53, Ramat HaHayal, Tel Aviv, Israel · hello@goodbunny.co