Isolation and retention

What stays inside your enterprise, what a model is and is not shown, how long run history is kept, and what closing an enterprise deletes.

One enterprise, one tenant

Each enterprise is its own tenant. What it holds is visible only inside it:

What Stays inside the enterprise
Memory A run and the API read only their own enterprise's memory. Another enterprise's notes are never loaded, whatever a request asks for.
Runs and executions Their inputs, logs, results, events and costs.
Credentials Model connections, tool connections, the webhook secret and API tokens. None can be read back once saved, in the portal or over the API: a new webhook secret or API token is shown once, when it is made.
Mail Each member's inbox. A run reads only its own member's mailbox.

Inside an enterprise, memory is shared. Teams, roles and tasks are labels on one memory, not private stores, so never train a secret into it. See Memory.

A task you clone or copy from Catalog brings its definition and nothing else: no credentials, no memory, no run history. See Tasks.

Throwaway run environments

A run that works on files (a clone of a repository, tests, a build) does it in a workspace made for that run alone. It is not shared with any other run or enterprise, and it is destroyed when the run finishes; a run waiting at a gate keeps its workspace until it carries on. Anything the run did not push or publish goes with it.

What the model sees

The model a run uses is given the job: the task's goal, success metric, guardrails and skill, the run's input, and the tools it may call, each as a name, a description and the arguments it takes. What a tool returns during the run (a file, an issue, an answer from memory) is read by the model too.

A run also knows the date and time, with no tool to call. Its first message, ahead of its input, gives the moment the run started to the minute, with the weekday, in UTC and in your enterprise's timezone. That timezone is named in the message and its offset from UTC is shown, daylight saving included. A skill can say "due in the next four weeks", "today" or "older than a week" and rely on it, and "today" and "here" mean your enterprise's timezone. If the enterprise has no timezone the OS knows, the time is given in UTC only. A run that is retried, recovered or resumed is told the moment it resumed, not when the work first started. A run is told the time only when it starts or resumes, not again at each step, and chat states it on every message. The time is never in the skill, so what a task sends the model ahead of it stays the same from run to run.

It is never given where a tool lives or how it signs in. Server addresses, tokens and other credentials stay with the OS, which makes each call on the model's behalf, after the task's checks and any gate. An argument a connection fixes (an organisation, a workspace) is taken out of what the model is shown, so it cannot ask for another.

The model provider sees what a run sends it, on the model connection you chose.

How long run history is kept

Executions and their runs are kept for your plan's period, counted from when the whole execution finished:

Plan Executions and runs kept for
Free 7 days
Starter 7 days
Company 30 days
Scale 30 days
Enterprise 365 days

After that, the execution is deleted whole: every run in it, with its logs, events and results. An execution is never split, and one with a run still open is never deleted, however old its first run is. A clean-up runs every hour.

Memory is kept until someone removes it. Removing a note hides it from every run at once; the record of it stays for audit.

Mail retention by plan

A member's mail is kept for your plan's period, then deleted: received mail and the member's own sent copies alike, with their attachments, once they are older than it.

Plan Mail kept for
Free 7 days
Starter 7 days
Company 30 days
Scale 30 days
Enterprise 365 days

The clean-up runs every hour, so mail goes within the hour of passing the period. Deleted mail is gone from the inbox, from the member's tasks and from file storage. A move to a plan that keeps mail for less time deletes what is older than the new period at the next clean-up after the move; Billing says so before you change plan.

Mail past the plan's daily inbound cap is held until the mailbox has room, and kept no longer than this period. The cap, and the other rules of a member's inbox, are on Members and inboxes and Member mailboxes.

Planned

Retention you set

You will set how long your enterprise keeps run logs, memory and assets, within what your plan allows. Custom retention is part of the Enterprise plan.

Planned

Support access

Zero Human staff will not read your memory, logs, assets or secrets by default. When you need help, you will grant support access yourself: for a limited time, and recorded, so you can see who looked and when.

Closing your enterprise

Deleting an enterprise happens in two stages. It is closed at once, and its subscription is cancelled at once. Then, once its plan's retention has passed, everything it holds is erased. The erasure cannot be undone.

Who can delete it

Only the enterprise's owner, signed in to the portal. At the end of Enterprise, the owner uses Delete enterprise in the Danger zone and confirms by typing the enterprise's name exactly: the same letters, in the same case, with nothing before or after. A member who is not the owner is not offered it, and is refused if they ask. An API token or a connected app cannot delete an enterprise. Who deleted it, and when, is recorded.

What happens at once

From the moment it is closed:

  • The subscription is cancelled now. A paid plan's subscription is cancelled at once, not at the end of the term, with no refund or proration for the period already paid. Only this enterprise's subscription is cancelled, even when the same payer pays for others. If the cancel cannot be confirmed, nothing is closed: the enterprise stays open, the owner is told, and can try again.
  • Nobody can use it. A session open in it, an API token issued for it and a connected app are refused on their next request. People can still sign in: someone who also belongs to another enterprise that is still open carries on in that one, and someone with none left is offered to create one.
  • Nothing runs. No run starts, whoever or whatever asks: a person, chat, the API, a webhook, a schedule or a task that follows another. A run that was waiting in the queue is not picked up, and every run still in progress is cancelled, with its open gates.
  • Mail is refused. Mail to its addresses, on its own domain and on any domain it attached, is refused at the door, so it is never stored.
  • What it published is deprecated. Its tasks, roles and team templates in the catalog can no longer be cloned, copied or synced. What another enterprise already cloned from them keeps working.

The retention

A closed enterprise is kept for its plan's retention, counted from the moment it was closed, on the plan it held before the cancel:

Plan Kept for
Free 7 days
Starter 7 days
Company 30 days
Scale 30 days
Enterprise 365 days

An enterprise closed before deletion went by plan keeps the 30 days it was promised. During the retention:

  • Only Zero Human staff can reopen it, when its owner deleted it. Ask through support. Who reopened it, and when, is recorded. One closed for inactivity is different.
  • Once it is reopened, runs and schedules work again. Schedules carry on from where they stood. Runs that closing cancelled stay cancelled, the subscription stays cancelled, and the catalog entries stay deprecated.
  • Its slug stays taken, so no other enterprise can be created with it.

What is erased after the retention

Once the retention has passed, the enterprise is erased for good. The check runs every hour. Erased from every live store:

What Erased
Runs and executions Every run and execution, with their inputs, logs, events, results and costs.
Memory The enterprise's memory bank, every note in it.
Mail Every member's inbox: the messages, their bodies and their attachments.
Files Everything kept in file storage for the enterprise: run logs, run files and mail bodies.
Secrets Model connections, tool connections, the webhook secret and API tokens.
Catalog What it published that no other enterprise has cloned. An entry another enterprise still clones stays, deprecated, and goes once the last clone has gone.
Everything else Teams, roles, members, tasks, KPIs, the metered usage the usage reports were worked out from, attached domains, the people's access to the enterprise, and the enterprise itself.

Another enterprise's data is never touched, even one the same people belong to. An erasure that is interrupted finishes on the next check.

What is kept:

  • A minimal record of the close: the enterprise's id, who closed it and when, when it was to be erased, who reopened it and when, and when it was erased. It holds no name, no slug and nothing the enterprise held.
  • The slug, retired for good. It is never given to another enterprise, so mail and webhooks meant for this one never reach a stranger.
  • The usage reports: what was billed for each closed period, kept as the financial record. Your invoices stay with our payment provider as its record.
  • People's accounts and sessions. A person outlives any one enterprise: a session that was in the erased enterprise stays signed in, to no enterprise.

Database backups are not edited: they expire on their own rolling schedule.

Closed for inactivity

A Free enterprise nobody uses is closed for inactivity, after notice to its owners, and then erased. A paid plan never closes for silence. The Closes for silence row on pricing gives every plan's rule, and this section is the one place in the docs that gives Free's numbers.

What counts as activity. Anything a person does in the enterprise: a signed-in person using it in the portal, a call with one of its API tokens, or a connected app acting on a person's connection. What happens without a person never counts: a scheduled run, a run the OS starts by itself, a built-in task, a clean-up, or anything Zero Human staff do. Inbound mail never counts either, so an inbox that only receives mail does not keep an enterprise open. The silence is counted from the last activity.

Planned

The notices. Free's schedule, as the plan row states it: notices at 30, 45 and 55 days of silence, closes at 60. Each notice is a mail to the enterprise's owners, and carries Keep my enterprise: one click keeps the enterprise open, and counts as activity, so the silence starts again from there.

The close. On the close day an enterprise nobody has used is closed, the way its owner's delete closes it (see What happens at once), and its owners are told.

The owner's reopen and the erase. Until it is erased, an owner can reopen the enterprise in the portal, without asking support. It is erased 7 days after the close, Free's retention, as What is erased after the retention sets out.