Legal
Privacy.
The desktop app keeps everything on your computer. ReDock Web keeps the minimum a dashboard needs. Both are listed here, item by item.
LAST UPDATED 30 SEPTEMBER 2026
The desktop app: what leaves your machine, and when
- Nothing, by default. Sites, databases, files, agent conversations and AI keys live on your own computer. The app works without an account.
- Sharing and deploys. When you share a site or deploy one, traffic flows through Cloudflare because you asked it to: a tunnel for a share link, Cloudflare's edge for a deploy. Stop sharing and it stops. A named share address is registered to your account so it can be yours.
- Cloud AI models. Only if you connect one, and only what you send in a conversation. With a local model from ReDock's catalog, prompts and content never leave the machine.
- Anonymous error reports. When something in ReDock breaks, the app sends a short report: an error code, a redacted message, which part failed, the app and system version, and the processor type. Never your sites, files, site names, paths, keys or account. First-run setup says so; the switch is in Settings, under Advanced, and turning it off also deletes anything still waiting to send. Reports are kept for 90 days.
- Update checks. The app asks our public release feed whether a newer version exists. That request carries the version and platform you are on, and nothing about you or your sites.
ReDock Web: what we store
| What | Why | How long |
|---|---|---|
| Your email address, a name if you gave one, and a hashed password, or the identity Google, GitHub or your own single sign-on provider handed us | To sign you in and to reach you about your account | Until you delete the account |
| Your workspaces, their members, roles and pending invitations | So the right people can reach the right sites | Until removed, or until the workspace is deleted |
| The address, title and favicon of each connected site, and its pairing key, encrypted | To reach the site on your behalf | Until the site is disconnected |
| What each site reports: plugins, theme, users, PHP and WordPress versions, health checks, the latest full scan's findings, and a plugin snapshot taken before an update | The dashboard, the alerts and the one-press restore | Refreshed on each check, and each full scan replaces the last; snapshots swept by the site's own store |
| The activity log: who did what, by name, on which site, and what was refused | Accountability, exports and the monthly report | 400 days, then swept |
| AI app approvals and API tokens you created | So an app or script can reach your sites until you revoke it | Until revoked |
| Your plan and, once a payment provider is connected, a customer reference at that provider | Billing | Until the account is deleted |
| Emails we sent you: alerts, reports, sign-in links, billing notices | Delivery records | Briefly, at the email service, for delivery |
Payment card details are held by the payment provider, never by us. We do not read the content of your WordPress sites except to carry out the action you or your AI app asked for, and the request and its result are written to the activity log under the name of whoever asked.
Where it lives
ReDock Web, its database and the sharing service run on Cloudflare's network. Transactional email is sent through an email delivery service that sees the address and the message. If you sign in with Google or GitHub, that provider knows you signed in. To check a connected site from outside, ReDock Web asks Google PageSpeed Insights to measure the page speed of the site's public address, and asks Cloudflare's and Google's public DNS resolvers about the site's domain for the mail and DNS checks. They see the site's address or domain, never anything about you. We use no other processor for your data.
When you open a site's Attacks view, the page lists the addresses that failed to sign in to that site and the usernames they tried, read from the site as the view opens. Your own browser then asks GeoJS (geojs.io) which country each public address is in, with no cookie and no page address attached. It keeps the answers in the browser for 30 days, and clears them when someone else signs in on that browser. ReDock's servers never contact GeoJS. ReDock Web never stores these addresses or usernames, except an address you or a teammate unlocks or blocks, which the activity log keeps with that action.
This website
What we do not do
- No selling or sharing of personal data, and no advertising on anything we make.
- No analytics embedded in your local sites or your connected sites.
- No reading of your project files off your machine.
- No opening of your WordPress admin without being asked to in writing.
Your rights: export and deletion
Write to hello@tryredock.com from the address on your account and ask for an export or a deletion. An export arrives within two working days as files you can open. A deletion removes your account, your personal workspace, the sites paired to it and their keys, your approvals and tokens, and your email from our lists; workspaces you own are deleted with it unless you hand them to another owner first. Activity records that name you in a workspace you do not own are kept for that workspace's log, with your name replaced. The desktop app needs no request: everything it holds is on your computer, and Uninstall removes it after showing you the list.
You can also export a workspace's activity yourself, as CSV or JSON, from the Activity page.
Children
ReDock is a tool for people who run websites. It is not directed at children, and we do not knowingly collect data from anyone under 16.
Changes
When this page changes, the date at the top changes with it, and a change that matters is emailed to workspace owners before it applies.
Contact
Questions about privacy go to hello@tryredock.com. ReDock is made by UXBD; the studio's address is hello@uxbd.net.