Trekit privacy policy

Effective 13 November 2026.

Trekit records conversations on your iPhone or Mac, transcribes them, and labels who said what. All of that happens on a Mac you own. We run no Trekit cloud service, and we do not receive your recordings, transcripts, calendar events or location. This page lists what the software stores, which few things leave your devices, and who receives them.

What Trekit records and stores

Audio from the microphone, in chunks of about 30 seconds. On the Mac you can also switch on system audio capture (the sound your Mac plays, such as the other side of a call). It is off until you turn it on, and the app shows whether it is recording while you record.
Transcripts, speaker labels and session titles, produced from that audio.
Voiceprints. When you tag a stretch of speech as a person, Trekit computes a numeric voice signature for that person from the tagged audio and uses it to suggest names in later recordings. You can delete a person, which removes their voiceprints.
Location. If you allow it, each chunk carries location fixes from your device. Trekit also stores a place name and, when the fix is precise enough, a street address for the session.
Calendar events, on the Mac, if you allow calendar access. See below.
Files you import. If you import an audio or video file, Trekit keeps the original and the transcript made from it.

All of it is stored by the Trekit server that you run. On a Mac, that is a SQLite database and audio files in a folder on that Mac, and the optional bundled server is off until you turn it on. Someone who runs the server themselves can instead point it at an S3-compatible bucket they control for the audio files; the database still stays on the server's disk. The iPhone app keeps a local copy of recent lists and transcripts so it still opens offline, and can delete a recorded chunk from the phone once the server confirms it has it.

The Trekit server can listen on your local network, over HTTPS by default. Phones and apps connect to it with a pairing code that contains a secret token and the server's certificate fingerprint; the apps accept only that certificate. Anyone who holds the token can read your recordings, so treat the pairing code like a password.

What leaves your devices, and to whom

The apps contain no analytics, advertising, tracking or crash reporting code. The only counting is on our website, described under update checks below. Four things use the internet or a server outside the app:

Speech models, downloaded once. The first time the server runs, it downloads its transcription, speaker-separation and voice-matching models (a few gigabytes) from Hugging Face, which hosts the model files. Hugging Face sees the request, including your IP address and which model files are fetched. Your audio and transcripts are not sent there; the models run on your Mac. If you turn on the optional Whisper model for languages the default model does not cover, it is downloaded the same way when first needed. Once a model is on disk, the server does not fetch it again.
Place names, from Apple. To turn a location into a place name, the app on the device that recorded sends the coordinates to Apple's geocoding service (Core Location's reverse geocoder). Apple handles that data under its own privacy policy. Trekit sends only the first location fix of each session, once. If you do not allow location, nothing is sent.
Update checks, on the Mac app downloaded from our site. That build uses Sparkle to check trekit.bronsonhill.com.au/appcast.xml for new versions, and downloads updates from dl.trekit.bronsonhill.com.au. Both are hosted on Cloudflare. A check discloses your IP address and the app version to the feed host, and sits in that host's ordinary server logs. Separately, a download and update counter on trekit.bronsonhill.com.au counts update checks and downloads per day, by app version only. It stores no IP addresses, device identifiers or other personal data. Updates are verified against a signing key before they install. Builds distributed through TestFlight are updated by Apple instead.
Apple services. TestFlight and the App Store collect their own data under Apple's terms. Trekit does not add to it.

Your recordings and transcripts are never sent to us. They reach another company only through a tool you connect yourself, such as the MCP server described next.

AI assistants through the MCP server

Trekit offers an optional program, trekit-mcp, that lets an AI assistant such as Claude or another MCP client read your recordings. You install it, give it your server address and a token, and register it with the assistant yourself. When the assistant calls it, it can read session titles, times, place names and addresses, labels, transcripts, speaker names, and search results. The stored calendar details are not among the fields it returns today. Whatever the assistant receives is then handled by that assistant's provider under its own terms; Trekit does not control that. Do not connect an assistant if you are not comfortable with it seeing the transcripts it asks for.

Calendar data

On the Mac, if you grant calendar access, Trekit reads your calendars with read-only access. It never creates, edits or deletes an event. It uses the events to show a notification shortly before a meeting that has a meeting link or other invitees, with a button to start recording. Nothing records until you press that button.

When you start a recording from such a notification, Trekit copies that one event to your server and stores it with the recording: the title, start and end time, location, link, notes or description, the organizer, and the attendee names and email addresses. Notes are cut at 20,000 characters and the attendee list at 500 people. The copy is a snapshot taken at that moment. The app does not display these details yet, and the search feature does not index them. Calendar events you do not start a recording from are not sent anywhere. You can revoke calendar access at any time in System Settings, and deleting a recording deletes its stored event.

Other people's voices

A recording of a meeting or conversation captures other people: their voices, what they say, and, through calendar events, their names and email addresses. You are responsible for telling them and getting their consent where the law of your location, or theirs, requires it. Laws on recording conversations differ by country and by state, and some require every participant to agree. Trekit does not seek anyone's consent for you.

If you tag someone, Trekit builds a voiceprint of their voice. Treat that as personal information about them, and delete it when they ask.

Retention and deletion

Trekit keeps your data until you delete it; there is no automatic expiry. Deleting a recording in the app removes its audio, transcript, speaker segments, tags, calendar copy and queued processing from the server. Deleting a person removes their voiceprints and the evidence behind them; their audio stays in the recordings. Forgetting a server in the app clears the offline copy it keeps on that device. Removing the Mac app does not remove the server's data folder (~/.local/share/hindsight/ by default, whose name predates the Trekit brand); delete that folder to erase everything the server holds. Backups or exports you make are copies under your control, and deleting a recording does not reach into them. The model files downloaded from Hugging Face live in a cache folder on your Mac and hold no personal data.

Children

Trekit is a tool for adults and is not directed at children. We do not knowingly collect information from children, and we hold none, since we receive no recordings, transcripts, calendar or location data.

Changes to this policy

We will update this page whenever the software changes what it stores or sends, and change the effective date above. Paid sync or cloud features do not exist yet. If we ship them, this policy will change before they do.

Contact

Questions or requests about this policy: contact@bronsonhill.com.au.

This page describes how the software works. It is not legal advice and makes no claim of compliance with any particular privacy law.