Loci Privacy Policy

Effective date: July 15, 2026

What Loci Does

Loci records meetings and working sessions that you choose to capture, then creates transcripts, summaries, structured notes, source links for supported outputs, tasks, Project Memory, and chat answers. During beta, Loci is device-token based and does not provide user accounts, team workspaces, or cross-device sync.

Data We Collect

Loci may collect audio you choose to record, transcripts, generated summaries, notes, tasks, chat messages, project context, a per-install device token, app version and diagnostic metadata, optional calendar metadata used for meeting detection, and beta-request information such as email address and optional use-case notes.

How Data Is Used

Loci uses your recordings and related content to transcribe sessions, generate outputs, show session history, answer questions over your transcripts, process deletion requests, provision approved beta seats and download links, and troubleshoot beta reliability issues when you send feedback.

Processing and Subprocessors

Loci's production API and object storage run on Hetzner infrastructure in Germany. Loci uses Deepgram for speech-to-text, OpenAI for generated outputs, and Cloudflare for public website delivery. If enabled, Cloudflare Web Analytics provides cookieless aggregate traffic metrics. Those providers process data according to their own processor terms.

Data Residency and Transfers

The current beta backend and object storage are hosted on Hetzner in Germany. Deepgram, OpenAI, and Cloudflare may process selected data outside that infrastructure according to their own processor terms.

Retention

Retention differs by data type and operational state. Playback audio, transcripts, generated outputs, tasks, Project Memory, beta-request records, and metadata may remain while needed to provide and operate the beta, until you delete them or request deletion, and as required for legal or operational needs. Temporary processing objects may follow separate cleanup schedules.

Legal Basis and Rights

Where applicable, Loci processes beta data to provide the service you request, operate and improve beta reliability, comply with legal obligations, and protect the service from abuse. You can contact Loci to request access, correction, deletion, export, or objection where those rights apply.

Device Identity

Loci uses a server-issued per-install device credential instead of account login during beta. On macOS, the credential is stored in a protected file under Loci's Application Support directory and a non-secret device-id marker is stored in local app preferences. These values are not synced through Keychain or iCloud. Loci does not provide account recovery; replacing a lost credential requires an operator-issued seat and creates a new device identity.

Recording Consent

You are responsible for using Loci only where recording is lawful and appropriate, including obtaining consent from meeting participants when required.

Deletion and Export

You can request deletion of data tied to your device token from Settings > Data and Privacy. Object cleanup may complete separately from the initial request. You can request export or deletion help by contacting feedback@getloci.co.

Diagnostics

If you use Send Feedback, Loci may include app version, build number, environment, last recording id, recent process logs, and MetricKit crash or diagnostic payload references. These diagnostics are used only to investigate beta reliability issues.

Contact

Email: feedback@getloci.co