Where things live, and who holds the key.

The desktop app

• Everything runs on your computer. Sites, databases, files, agent conversations and the Studio's output live in ReDock's own folder on your machine. There is no account and nothing is uploaded to us.
• AI keys stay in your system's credential store, the macOS Keychain or the Windows credential manager, never on our servers. A cloud model sees only what you send it in a conversation; a local model from ReDock's catalog sees nothing leave.
• The MCP server listens on 127.0.0.1:47200 only. It never listens on the network. An AI app on the same computer can reach it; nothing else can.
• Sharing is a tunnel you start and stop. A shared site is reached through a Cloudflare tunnel from your computer. The tunnel credentials live in your credential store. Stop sharing and the address goes dark; the site keeps running for you.
• The local certificate authority signs only your .test sites and never leaves the machine. Your system asks for your password once to trust it, and uninstalling removes it.
• Every change to your computer is listed before it happens. First-run setup is a numbered manifest; Uninstall previews exactly what it removes.
• Anonymous error reports carry an error code, the failing part, the app and system version and the processor type. Never your sites, files, site names, paths or keys. The switch is in Settings, under Advanced; turning it off also deletes anything still waiting to send. Reports are kept for 90 days.

ReDock Web

• Where it runs. ReDock Web and its database run on Cloudflare's network. It stores your account email, your workspaces and their members and roles, the addresses of the sites you connected, the pairing key for each site in encrypted form, the activity log, the results of health checks and jobs, and the plan on each workspace. Payment details are held by the payment provider, never by us.
• Sign-in. Email and password, a sign-in link by email, Google, GitHub, or single sign-on with the identity provider your workspace already runs (Google Workspace, Microsoft Entra, Okta), connected by the workspace owner for a domain they have proved with a DNS record and required for everyone on it. Sessions are cookies on app.redock.xyz.
• Roles. Owner, Admin, Member and Viewer. A viewer can open every site and press nothing. Only an owner can change the plan. Removing somebody disconnects their AI apps from that workspace in the same moment.
• Every action is recorded with the person's name and the role they held, or the AI app's name, or the job's. Refused actions are recorded too. The log can be filtered and exported as CSV or JSON, and it is kept for 400 days.

How a live site is connected

You install ReDock Connect, a small plugin, on a WordPress site you host. The site and ReDock Web share a key, and every request between them is signed with it; a request that is not signed correctly is refused, and a captured request cannot be sent again. The key is scoped: it can read and write inside the five wp-content folders a site is edited in, and it cannot reach wp-config.php or the site root. It cannot read the other keys on the site, however the question is asked, and it cannot make itself unrevokable.

One site can be paired with more than one client, each with its own key: your desktop app, your workspace, a colleague's. The plugin's settings page in wp-admin lists every client. A key can be made read-only.

How to take access away

1. From the site. On the plugin's settings page in wp-admin, revoke any client. It stops working on the next request.
2. From ReDock Web. On the site's page, disconnect the site. From the AI apps page, revoke any AI app or API token; the next call is refused. Removing a person from a workspace removes their access to every site in it.
3. All of it. Deactivating or deleting the ReDock Connect plugin ends every connection to that site at once.

What AI apps may do

An AI app connects through one door, with a consent screen that names the workspace or the single site it is being approved for. Seven policy switches per workspace, tightened per site, decide what an AI app may do unasked: publishing, the front page, the theme, plugins, settings, the database, users. What you switch off, the app is refused and told to ask a person; you, your team and your jobs are unaffected. Deleting anything always asks.

Reporting a problem

If you have found a way to reach something you should not be able to reach, email hello@tryredock.com with "Security" in the subject. Tell us what you did and what you saw; a way to reproduce it is the most useful thing you can send. We acknowledge within two working days, tell you what we found, and say when the fix shipped. Please give us a reasonable time to fix it before writing about it publicly, and do not test against sites you do not own.

Fixes to the plugin and to ReDock Web are listed on What's new in plain words, including what could have been reached before the fix.