Trust
How MachineDock protects your organization's work: how it is secured, where data lives, how long it is kept, and which companies help us run the service.
At a glance
- Data is stored and processed in the United States.
- Every connection uses TLS; files and secrets are encrypted at rest.
- Your computers make only outbound connections: no open ports, no VPN, no public endpoints.
- Every command is signed by MachineDock and checked by the computer before it runs.
- Cloud computers hold no cloud credentials and accept no inbound connections.
- We do not use your files, commands or chats to train AI models.
Security practices
- Encrypted in transit. Every connection uses TLS: your AI app to MachineDock, MachineDock to each computer, and every file upload and download.
- Encrypted at rest. Files in storage are encrypted with AES-256. Secrets such as API keys are encrypted and sealed to the one computer that uses them. The AI only sees their names.
- Keys that stay on the computer. Each computer makes its own key when it joins, and its credentials are sealed to that key. Updates to MachineDock are signed with an offline key and checked before they install.
- Your work stays yours. The activity log records what ran, not what was in it: no command text, file contents or output. Full logs, with secrets removed, stay off until an owner or admin turns them on.
- Spending limits. Anything paid needs approval in the chat. Owners set monthly budgets, a cap on running machines and the largest size anyone can start.
- Signed commands and approvals. Every command is signed and verified on the computer. Require a person's approval for commands or changes, per project.
- Audit history. A record of every action across the organization. Turn on full tool logs, with secrets redacted, when you need an audit trail.
- No credentials on cloud computers. Cloud computers hold no cloud keys, accept no inbound connections, run behind deny-all firewalls and use encrypted storage.
- Roles and access. Owners, admins and members, with project access you grant. A member's own computer stays private unless an owner or admin shares it with the organization.
- Files stay with the project. Results are kept with the project, on its computer and in storage, ready for the next person and the next run.
Where data lives
| Data | Where |
|---|---|
| Accounts, organizations, projects, approvals and activity records | Neon Postgres on AWS in Oregon (us-west-2) |
| Project files and file transfers | Google Cloud Storage in Oregon (us-west1) by default, and a bucket in the same region as each cloud computer: Google Cloud in Nevada (us-west4) and Iowa (us-central1), AWS in Oregon (us-west-2), Virginia (us-east-1) and Ohio (us-east-2) |
| Cloud computers and their disks | Google Cloud and AWS, in the six regions above |
| The Console, the MCP server and the MachineDock Assistant | Vercel in Portland, Oregon |
| Commands and results between MachineDock and your computers | Synadia Cloud (NATS), encrypted in transit and signed end to end |
| Files on your own computers | On those computers. They leave only when you or your AI moves them. |
How long data is kept
| Data | How long |
|---|---|
| Your account | While the account is open. Deleted within 30 days after it is closed, except what the law requires us to keep. |
| Project files | Until the project is deleted. When a file is replaced, the previous version is kept 30 days. |
| Files in transit (uploads, exports, large command arguments and results) | 1 day. |
| Upload links | Expire after 24 hours by default and 7 days at most. |
| MachineDock Assistant chats | 30 days, attachments included. The chat's scratch computer is kept 7 days after its last use, and deleted with the chat. |
| Activity records (what ran, who asked, when; no contents) | Tool calls 30 days, command records 90 days. |
| Full tool logs (off unless an owner or admin turns them on) | 30 days. |
| Cloud computer disks | While the workspace exists. A cloud computer stopped for 30 days is retired and its disk kept as a snapshot: 30 days after the workspace is deleted, or 90 days after the computer was retired. |
| Files on your own computers | On your computers, under your control. MachineDock does not copy them unless you or your AI moves them. |
Subprocessors
These companies process data for us to run MachineDock, under contracts that limit their use of it to providing their service. We update this list before a new subprocessor starts processing Customer Content. To be told of changes in advance, email legal@smartspatial.com.
| Company | What it does | Where |
|---|---|---|
| Vercel, Inc. | Hosts the website, the Console, the MCP server and the MachineDock Assistant. Its AI Gateway routes the Assistant's requests to model providers, Vercel Sandbox runs the Assistant's scratch computer, and Vercel Workflow stores the Assistant's chats. | United States (Portland, Oregon) |
| Neon (a Databricks company) | The database: accounts, organizations, projects, computers, approvals and activity records. | United States (AWS, Oregon) |
| Synadia Communications, Inc. | Carries signed commands and results between MachineDock and your computers (NATS), encrypted in transit. | United States, with servers in other regions |
| Google LLC (Google Cloud) | Stores project files and transfers, and runs cloud computers. | United States (Oregon, Nevada, Iowa) |
| Amazon Web Services, Inc. | Stores files next to cloud computers on AWS, and runs cloud computers. | United States (Oregon, Virginia, Ohio) |
| Resend | Sends email: approval requests, invitations and replies to early access requests. | United States |
| vTilt | Website analytics and the support chat on the website and in the Console. | United States |
| Slack Technologies, LLC | Only when your organization installs the MachineDock Slack app: messages to and from it. | United States |
| AI model providers, through Vercel AI Gateway | Only for the MachineDock Assistant: the provider of the model your organization uses (for example Anthropic, OpenAI, Google or xAI) processes the chat. Owners can allow only providers that keep no data. | United States and other regions, by provider |
Certifications and reviews
MachineDock is in early access and does not yet hold a SOC 2 report or ISO 27001 certification. The providers it runs on do: Vercel, Google Cloud, AWS and Neon publish their own. We answer security questionnaires and offer a Data Processing Addendum, including the EU Standard Contractual Clauses. Email legal@smartspatial.com to start a review.
If something goes wrong
If we confirm a security incident that affects your organization’s data, we notify your organization’s owners without undue delay, and within 72 hours for personal data, with what we know, what we are doing and what you can do.
Reporting a vulnerability
Email legal@smartspatial.com with the details and how to reproduce it. We will reply, keep you informed and credit you if you wish. We will not pursue anyone who researches in good faith: who avoids other people’s data, avoids disrupting the service, does not use more access than needed to show the issue, and gives us reasonable time to fix it before telling others.