Privacy in this build

Records, activities, tasks, files, imports, workflow runs and audit events are stored in the regional CRM PostgreSQL database. The browser calls that regional service directly. Current workspace permissions determine what a person or agent can read and change.

The free template, pipeline, outreach and forecast tools process selected data in this browser. Explicitly saved drafts are retained in IndexedDB for up to 24 hours and expired entries are removed when storage is next read. You can clear a selected draft or remove this site’s browser data. Downloads are your portable copy; browser storage is not a backup. The optional CRM handoff saves a local reference and sends data to the regional service only after you review and confirm an import. Ordinary page and asset requests still reach our hosting provider.

The local development adapter creates fixture workspace identities and credentials. Its browser credential is stored in this tab’s session storage so OAuth consent can reuse your workspace; sign out clears it. Appearance and density preferences use local storage. Hosted identity, shared membership and billing use central Loamstack when configured. CRM account sign in reports unavailable while that hosted setup is incomplete.

Only connected clients with credentials can access the regional API or MCP service. Scopes, permissions, approval policy and action budgets apply to their actions. No email, calendar or external AI provider integration runs from this local build. If you connect a client yourself, data you share with that client is also subject to its own handling practices.

Error reporting is optional and remains disabled without a CRM Sentry project identifier. Its event filter removes request bodies and URLs, identity, customer fields, credentials, breadcrumbs and original error text. It retains fixed product metadata and code locations. Session replay and tracing are disabled.

Archiving retains a record for later restoration. Authorized deletion and purge actions are separate operations, with dependency checks and any configured approval policy. Audit records document actions and are not removed by archiving a customer record. Local integration fixtures clean up the exact records created for their test run and preserve unrelated workspace data.