Data and Security

Holarch keeps your projects on the Holarch server. Only members of a project can open it, and each member has a role that sets what they can do. Holarch saves every change, keeps earlier versions of each project and lets you export a copy at any time.

Concepts

• Project data: the model of a project: items, relationships, diagrams, documents, comments, history and settings such as the dashboard. It is stored in the server's database.
• File storage: attachments, images and simulation results, kept on the server separately from the project data. See Attachments, Storage and Limits.
• Member and role: an account with access to a project, as Owner, Editor, Reviewer or Viewer. See Roles.
• Earlier version: an automatic copy of the whole project, kept so you can go back.
• Baseline: a named snapshot you save on purpose. Baselines are part of the project.
• Trash: where a deleted project stays for 30 days before it is deleted for good.
• Browser cache: a copy of the projects you open, kept in your browser so you can keep working when the connection drops.

How to use it

When and why

Read this page when you decide what to put in Holarch, when you set up a project for a team, and when you need to get something back. It answers three questions: where your data is, who can see it, and how to recover from a mistake.

Keep your own copy of a project

1. Open Manage Projects.
2. Open the project's row menu ⋯ and choose Export this project….

   Or, on the project's Dashboard, choose Project ▾ → Export Project….

3. Choose the options and click Export JSON.

   The JSON file downloads. It holds the whole project and can be imported into any Holarch account.

See Back up or move a project for the options and the import.

Go back to an earlier version

1. Click the project name at the start of the top bar and choose Restore Earlier Version….

   You see the saved versions with Saved, Entities, Name and Size.

2. Select a version.

   You see what restoring changes.

3. Click Restore.

   The project returns to that version as one undo step. The state before the restore is kept as a version too.

To find the version that still holds a deleted item, type its name under Find versions containing and click Find. See Restore an earlier version.

Check who can open a project

1. Click Share in the top bar.

   You see every member with their role, and pending invitations.

2. As an owner, change a role or remove a member there.

See Sharing and Working Together.

Work on a shared or public computer

1. Work as usual. Holarch keeps a copy of the open projects in the browser.
2. When you finish, choose Sign Out in the account menu (your initials).

   Signing out removes the cached projects from that browser.

Worked example: recover a deleted function in the CubeSat EO-1 demo

1. Someone deleted a function from the CubeSat EO-1 demo two days ago, and undo no longer reaches it.
2. Open Database, then the Deleted tab in the sidebar.

   If the function is listed under Recently Deleted, click Restore. It comes back with its relationships.

3. If it is not listed, choose Restore Earlier Version… in the project menu.
4. Type the function's name under Find versions containing and click Find.

   The list shows only the versions that contain it.

5. Select the newest match, check the changes, and click Restore.

Tips and good practice

• Export important projects before a milestone, alongside a baseline. A JSON export is a copy you control.
• Give the smallest role that works. Use Viewer for stakeholders who only read, and Reviewer for people who comment and approve requirements.
• Do not put classified, CUIControlled Unclassified Information US government information that is not classified but must be protected or controlled by law, regulation or policy. or export-controlled information in Holarch. AI is turned off for projects with such markings, but the service is not built for that data.
• Sign out on shared computers, so no copy of your projects stays in the browser.

Where data lives

Every request to the server needs a signed-in account. A project you are not a member of answers as if it did not exist.

Saving

• Holarch saves each change automatically. There is no save button.
• The save status in the top bar shows Saved, Saving…, Not saved — retrying, Not saved — changed on the server or Offline – changes kept on this device. See Save status.
• Offline: changes are kept in your browser and sent when the connection is back.
• Changed on the server: when another member, or another window or tab, saved the project first, the Project Changed on the Server dialog asks whether to Load the Version on the Server or Keep This Window’s Version. The version you do not keep stays under Restore Earlier Version….
• Nothing could be saved: when neither the server nor the browser can take the change, a red banner reads "Changes are not saved. Do not close this page." with Retry and Download a copy.
• Shared projects: edits reach the other members within about a second. Clashing edits are kept for review as conflicts. See Edit together.

Earlier versions and baselines

• Holarch keeps automatic versions for the days of the project owner's plan: 7 days on the Free plan, 90 days on Individual and 365 days on Team. Within that time it keeps the last 20 saves and one save per day.
• The version saved just before a restore is never removed.
• Editors and owners can restore. Restoring is one undo step, and everyone with the project open receives the restored state.
• Baselines are part of the project, so version history never removes them. See Requirements.
• Deleted items are listed under Database → Deleted and can be restored with their relationships.

Deleting projects and your account

• Only owners delete a project, with Manage Projects → ⋯ → Delete this project…. It closes for every member and stays in the Trash for 30 days, then it is deleted for good with its versions and attachments.
• To get a project back from the Trash within 30 days, contact support.
• Deleting your account deletes every project where you are the only member. Projects with other members stay with them. See Deleting your account.

Access

• Accounts: sign-in with a password, Google or Microsoft, with optional two-step sign-in and passkeys. A session ends after 14 days without use and after 90 days in any case. See Your Account.
• Roles: set per project by its owners. Being a member of one project gives no access to another, and belonging to an organization gives no access to its projects.
• Organizations can require two-step sign-in for their projects and turn AI off for them. See Administration.

Imports and exports

• Imported files are checked and cleaned. SVG pictures lose scripts, event handlers and external references. Rich text loses scripts and unsafe links.
• Changes from other members are checked before they enter your model. Damaged, oversized or unsafe changes are set aside and listed, not applied.
• CSV exports neutralize spreadsheet formulas, so a cell such as =SUM(A1) is not run when the file is opened in a spreadsheet.

What is sent to AI

• Only on request. Nothing is sent unless you use an AI feature.
• Only to Anthropic, from the Holarch server, under the key in use: the included AI, your own key or your organization's key.
• Only what the feature needs. A requirement tool sends that requirement and its context. Ask AI sends the question, Help topics, the project's entities and relationships (names, numbers, descriptions, attributes), the current page and the recent conversation. The active AI reference files are added where they apply.
• Nothing kept. Holarch stores no prompts and no replies. It records the time, the key, token counts and the result, for usage and limits. Holarch does not use your content to train AI models.
• Restricted markings turn AI off. A project with classification, CUIControlled Unclassified Information US government information that is not classified but must be protected or controlled by law, regulation or policy. or export-control markings cannot use AI, and nothing is sent.

See Privacy: what is sent.

Limits

• Automatic versions: per the owner's plan (7, 90 or 365 days), the last 20 and one per day within that time.
• Trash: 30 days.
• Sessions: 14 days without use, 90 days at most.
• Storage and item limits: see Plans and limits.

Related pages

• Troubleshooting
• Sharing and Working Together
• Attachments, Storage and Limits
• Import and Export
• AI
• Your Account