DID-ACTO / FIELD GUIDE
Privacy, access and operating limits
Know where your data goes and what the current service can handle.
Who can access your workspace?
Each invited analyst has a private workspace. Other analysts cannot browse your uploads or reports. Accounts with administrator privileges can explicitly select and review users’ workspaces, and that review is audited.
Shared samples are read-only and visible to all invited users. Your own analysis of a sample produces records in your private workspace. Administrators can disable access while retaining the user’s files.
Where data is stored and processed
Application storage, login and statistical execution run on the service owner’s infrastructure. When you use an AI assistant, the information returned through the tools can be processed by that assistant’s provider under your account’s terms.
Review what you ask the assistant to access. Avoid uploading unnecessary personal identifiers or confidential columns unrelated to the study. The workspace controls who can access a file; your requests determine which tool outputs are shared with your assistant.
Current pilot capacity
| Limit | Current setting | Practical implication |
|---|---|---|
| Single upload | 200,000,000 bytes | A file may still fail separate parsing or expanded-memory limits. |
| Private workspace | 2,000,000,000 bytes | Uploads, runs, reports and caches share this allocation; usable space is slightly lower. |
| Invited accounts | Up to 10 | Accounts are created by an administrator. |
| Interactive use | Up to 4 analysts at once | A planning conversation is distinct from a heavy computation. |
| Heavy analysis | One fit admitted at a time | Approved analyses queue while another heavy fit is running. |
Retention and recovery
There is no automatic deletion of datasets or reports. A disabled account’s data is retained. The current portal does not provide a general file-deletion or quota-increase workflow; contact the administrator when storage is full.
Encrypted backups are maintained by the service owner on an owner-controlled computer. Ask the administrator for the latest backup date and available recovery point when restoring a file.
Keep credentials out of conversations
Use the browser sign-in flow. Never send passwords, authenticator codes or access tokens to the assistant as research context. If credentials are lost or an account needs recovery, use the administrator’s recovery process.