Where each piece of data lives
Everything Uniloom keeps is on your Mac, in Uniloom's data folder: ~/Library/Application Support/dev.uniloom.app/. No server holds your workspace. A shared workspace sends only what sharing lists.
Your data#
| What | Where | Shared? |
|---|---|---|
| Personal workspace | workspace.db. You can move it: see Your data and export | Only if you share Personal |
| Each shared workspace | Its own file in the data folder | Yes, see sharing |
| Docs, memories, sessions, automations | Inside their workspace's file | With their workspace, except what sharing withholds |
| Images in docs | Files beside the database, in the files folder | With a shared doc that names them |
| This computer's settings, the telemetry id and switches, and the list of workspaces on this Mac | machine.db | Never |
| Token use per session (Activity): times, token counts, model, cost. Never prompt or reply text | machine.db | Never |
| Tasks from your integrations: one line each, never a description, comment or message text | The workspace's file | Never |
| An agent run's drafts (pull request text, ticket update, review comments), so you can read them before you approve | The workspace's file, removed 30 days after the run closes | Never |
| Receipts: per session, the last reply's first paragraph, commands with their result counts, edited files and commits | The workspace's file | Never |
| Uniloom's own cost: CPU, memory and wake counts every 15 minutes | uniloom.log in ~/Library/Logs/dev.uniloom.app/ | Never sent |
| Your agents' sign-ins | Not in Uniloom. Each agent keeps its own | Never |
Credential files#
Uniloom keeps these files in its data folder, readable only by your user. None of them is inside a database, so exporting a workspace never hands anyone a live credential. They stay in the data folder when you move Personal.
| File | Holds |
|---|---|
cloud-session.json | Your Uniloom sign-in |
uniloom-server-token | The key every local caller presents to Uniloom's local server. Kept across launches. No agent's setup holds it (how) |
uniloom-mcp-token | A second key that opens only Uniloom's MCP server. Uniloom gives it to the sessions it starts; no agent's config file holds it |
work-gateway-auth.json | The token an integration you connected from Uniloom issued to Uniloom. Sent only to that server |
work-token-auth.json | A token you pasted for an integration. Sent only to that server, never logged, removed on Disconnect |
oauth-pending.json | A sign-in to an integration still in progress. Removed when used, or after 15 minutes |
Back to Privacy and security.
Last updated