Privacy policy
OMI Second Brain · last updated 17 November 2026
OMI Second Brain ("the application") is a personal, self-hosted application operated by its owner for the owner's own use. It has one user: its owner. This policy describes exactly what it does with data, in plain terms, because the honest answer is short.
1. Who operates it
The application runs on hardware owned and controlled by its operator. It is not a service offered to the public, there are no accounts, no sign-up, no other users, and no third-party customers. Its operator is also its only data subject. Contact: timothy.bannon@gmail.com.
2. What is collected
- Audio from the operator's own wearable microphone, relayed through the operator's own phone.
- Transcripts of that audio, stored as text.
- Derived items the operator asks for — reminders, tasks and calendar entries — and the notes or bookmarks the operator explicitly flags.
- Technical telemetry from the operator's own devices (connection state, buffer counters, battery level).
Nothing is collected from any other person's device, and no browsing, location, contact-list or advertising data is collected at all.
3. Where it is stored
Audio is transcribed and then discarded; it is not written to disk on the server. Transcripts, derived items and telemetry are stored in a database on the operator's own self-hosted server, on the operator's own network. They are not copied into any cloud storage service, and they are not sold, rented, published, or shared with advertisers or data brokers.
4. Third parties the application sends data to
Only to the extent needed to do the job the operator asked for:
- Google — speech-to-text and language processing are performed with Google Gemini models, so transcript text passes through Google's API; and, with the operator's explicit authorization, the application reads and writes Google Tasks and Google Calendar so that items the operator speaks become tasks and events.
- Groq — audio-to-text transcription.
- Telegram — delivery of notifications the operator configured, to the operator's own account.
No data is sent to any other party. There is no analytics, no tracking pixel, no advertising identifier, and no profiling.
5. Google user data — Limited Use disclosure
The application's use and transfer to any other app of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. Specifically:
- Google user data is used only to provide the features the operator requested — creating and reading the tasks and calendar events the operator spoke about.
- Google user data is never transferred to third parties, except as necessary to provide or improve those features, to comply with applicable law, or as part of a merger or acquisition with prior user consent.
- Google user data is never used for advertising, and is never sold.
- Google user data is never used to train, improve or develop machine-learning models.
- No human reads Google user data, except with the operator's explicit permission, for security purposes, or to comply with the law.
OAuth tokens are stored on the operator's own server with owner-only file permissions and are never transmitted anywhere except to Google's own token endpoint.
6. Retention and deletion
Data is kept until the operator deletes it, because it is the operator's own memory store. Anything can be deleted from the store at any time, and the operator can erase everything by dropping the application's database. Requesting deletion is therefore instantaneous and needs no process.
7. Security
Ingest is authenticated, transport is encrypted (TLS for the network leg and an encrypted link for the wearable), credential files are owner-readable only, and the server is reachable only on the operator's private network and through an authenticated tunnel.
8. Children
The application is not directed at children and has no mechanism to create an account.
9. Changes
If this policy changes, the "last updated" date above changes with it. There is nobody to notify but the operator.