Privacy

Effective 19 September 2026.

Why Locus asks Google for access

Locus is local software. With your permission it reads Gmail and Calendar so it can organize correspondence and events into an attention summary on your computer. You decide which Google accounts to connect, and you can disconnect them. Locus does not use this connection to send email, change labels, delete messages, or create or edit calendar events.

Google’s permission screen may name the client OPENCLAW. That is the consent-screen name of the Google login client this Locus install uses for that read-only access.

What is stored locally

After a successful read, Locus keeps copies of the selected mail and calendar data on the operator’s computer, along with the summary it builds. This website cannot see that store.

Revoking access in your Google Account stops future authorized reads. It does not delete copies already on the computer. Those copies remain until the operator removes them and manages any backups.

External AI services

Selected Gmail and Calendar content — potentially including full messages and attachments — may be sent to external AI services the operator has configured, such as OpenCode Go and OpenAI/Codex, so Locus can interpret and summarize that material. Those providers’ own terms govern whether they retain prompts or use them for training. This page makes no promise about provider retention or training.

Mail and calendar do not stay only on the local machine when those services are enabled.

This website

These pages are static files hosted on Cloudflare. Cloudflare may process standard request metadata, such as IP address, for hosting and security. We have not added site analytics, cookies, or forms. This site does not receive Gmail, Calendar, or Google tokens.

Other products

Locus may also use sources that are not Google. Those are outside this Google connection. SessionOS is a different application; this policy does not describe it.

Contact

Software questions: github.com/Niko96-dotcom/locus.