What we store and what we call
InstanceDesk connects to your n8n with an API key you create. It reads workflows and execution status, and writes a workflow only when you press restore. It never reads credentials and never stores the data your workflows process.
The key you give us
You create an API key in n8n under Settings and paste it in once. From then on:
- It is encrypted with AES-256-GCM, under a data key that is separate for each account.
- It is decrypted only inside the background worker, only for the call being made.
- It is never shown again, never sent back to your browser and never written to a log.
- If you delete your account, the key is removed at once.
Give us the smallest key your n8n allows. If n8n lets you choose scopes when you create the key, these are all we need:
| For | Scopes |
|---|---|
| Monitoring and backup | workflow:list workflow:read execution:list execution:read |
| Restore, if you want it | add workflow:update workflow:create |
If your n8n does not offer scopes, the key has full access to the instance. That is n8n's design, not ours, and it is the main reason this page exists. The list below is what we do with it.
Every call we make to your n8n
| Call | When | Why |
|---|---|---|
GET /workflows | On connect, then every 15 minutes | Find new, changed, deactivated and deleted workflows; take a backup when one changes |
GET /executions | Every check interval | Find failed, crashed and long-running executions; learn each workflow's rhythm; see whether a failure has recovered |
GET /executions/{id} | When a tracked run ends | Learn how it ended |
GET /executions/{id}?includeData=true | Never, unless you switch on error capture for that instance. It is off by default. | Read the error message and the failing node's name. Everything else in the response is discarded in memory. |
PUT /workflows/{id} | Only when you press restore | Write the version you chose, as a draft unless you choose live |
POST /workflows | Only when you recreate a deleted workflow | Create it again, inactive |
All calls come from one background worker. The dashboard you look at never contacts your n8n. Before launch we will publish the address the worker calls from, so you can allow it through a firewall.
A restore writes back nodes, connections and settings. Tags and whether the workflow is switched on are not restored; n8n does not allow that through its API.
What we never call
- Anything under credentials. We do not list, read or export them.
- Users, projects, variables, source control or audit endpoints.
- Delete, on anything.
- Activate, deactivate, retry or stop. Version 1 does not change whether a workflow runs. A restore "as live" republishes a workflow that is already active, and only when you ask.
What we store
| Data | Detail | Kept for |
|---|---|---|
| Your account | Email address and plan. No password; sign-in is by emailed link. When billing opens, a Stripe customer reference; never card data. | Until you delete the account |
| Instance | Name, address, the encrypted API key, its expiry date | Until you remove it |
| Workflow backups | Name, nodes, connections, settings and tag names, encrypted. Pinned test data and static data are left out. | 7 days on Free, 90 days on Solo, unlimited on Agency and Studio |
| Execution records | Id, workflow, mode, status, start and stop time. Only if you switch error capture on (it is off by default): the failing node's name and up to 500 characters of the error message. | 30 days; 90 on Studio |
| Incidents and alerts | What went wrong, when, and where each alert was sent | With the account |
| Alert destinations | Email addresses today. Slack and webhook addresses once those channels ship. Stored encrypted. | Until you remove them |
| Audit log | Every connect, key change, restore, export and deletion, with user and time | With the account |
What we never store
- Execution input or output. The data flowing through your workflows, your clients' customer records included, is not kept.
- n8n credentials. A workflow refers to a credential by id and name. That reference is in the backup; the secret behind it is not, and we have no way to read it.
- Pinned data, which can hold personal test data.
Two things you should know
A workflow backup contains whatever was typed into its nodes. If someone pasted a password or token straight into an HTTP Request node instead of using a credential, it is in the workflow, so it is in the backup. This is why backups are encrypted, and why it is worth moving such values into n8n credentials.
Error messages can contain personal data. An error such as "no customer found for [email protected]" would be stored if error capture is on. It is a per-instance setting and it is off unless you switch it on; alerts then name the workflow without the message.
Where it runs
- Hosted in the EU. Alert and sign-in emails are sent through Resend.
- Every database query is scoped to one account.
- Tested so far against self-hosted n8n 2.47.4 Community. n8n Cloud is being tested before launch.
- Outbound calls refuse private, loopback, link-local and cloud-metadata addresses and do not follow redirects to another host.
- A data-processing agreement and a list of subprocessors will be published before launch.
Leaving
You can download every workflow for an instance as a ZIP of JSON files at any time. When you delete your account, API keys are removed at once and everything else within 30 days. If a trial ends or a payment lapses, checks pause and data is kept for 30 days in case you return.
What this page is not
InstanceDesk has not had an independent security audit, and is built and run by one person. If your clients require certified vendors, we are not that yet. If something here is unclear, or you want to see a specific part of how it works before connecting an instance, ask: get in touch through the waitlist form.
InstanceDesk is an independent product for n8n and is not affiliated with n8n GmbH.