UniloomDocs
Privacy & trust

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#

WhatWhereShared?
Personal workspaceworkspace.db. You can move it: see Your data and exportOnly if you share Personal
Each shared workspaceIts own file in the data folderYes, see sharing
Docs, memories, sessions, automationsInside their workspace's fileWith their workspace, except what sharing withholds
Images in docsFiles beside the database, in the files folderWith a shared doc that names them
This computer's settings, the telemetry id and switches, and the list of workspaces on this Macmachine.dbNever
Token use per session (Activity): times, token counts, model, cost. Never prompt or reply textmachine.dbNever
Tasks from your integrations: one line each, never a description, comment or message textThe workspace's fileNever
An agent run's drafts (pull request text, ticket update, review comments), so you can read them before you approveThe workspace's file, removed 30 days after the run closesNever
Receipts: per session, the last reply's first paragraph, commands with their result counts, edited files and commitsThe workspace's fileNever
Uniloom's own cost: CPU, memory and wake counts every 15 minutesuniloom.log in ~/Library/Logs/dev.uniloom.app/Never sent
Your agents' sign-insNot in Uniloom. Each agent keeps its ownNever

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.

FileHolds
cloud-session.jsonYour Uniloom sign-in
uniloom-server-tokenThe key every local caller presents to Uniloom's local server. Kept across launches. No agent's setup holds it (how)
uniloom-mcp-tokenA 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.jsonThe token an integration you connected from Uniloom issued to Uniloom. Sent only to that server
work-token-auth.jsonA token you pasted for an integration. Sent only to that server, never logged, removed on Disconnect
oauth-pending.jsonA sign-in to an integration still in progress. Removed when used, or after 15 minutes

Back to Privacy and security.

Last updated