Privacy Policy

MK Builds LLC · Effective 4 August 2026

The short version

Bridget holds your contacts and the recordings you dictate, in our database. Every part of them that means anything is encrypted with a key belonging to your account alone, so reading the database is not the same as reading your rolodex. Bridget itself can decrypt it, because it has to in order to file a voicemail and answer a text. You can download all of it as a spreadsheet at any moment, and deleting your account destroys the key along with the data.

What we hold

Your phone number
Encrypted, and found through a keyed hash so your account can be located without the number being readable in our records. It is the whole of your identity here: there is no password and no email address.
Your contacts
Each person's name, company and role, location, the details you mention, and anything you said you would do. All encrypted.
Your call transcripts
The text of what you said, in full, encrypted. This is the most sensitive thing here, because it is everything you spoke aloud before any model decided what mattered. It is kept so that the portal can show you what was actually said when a name comes out wrong.
Timestamps and outcomes
When each call happened, how long it ran, whether it worked, and how many people it filed.

What the database can still see

Being honest about the boundary matters more than sounding absolute about it. Someone holding a copy of the database, and nothing else, can see the shape of your usage even though none of the content is legible to them: how many contacts you have, how often you call, how long the calls run, when you last used Bridget, and which calls failed.

The lookup values are keyed hashes rather than plain text, so they cannot be read back into a phone number or a name. They are consistent for the same input, which is what makes finding your account possible at all. The one for contact names is additionally scoped to your account, so it cannot be used to tell that you and another user know the same person.

What we do not do

We do not sell your data, share it for advertising, or build a profile of you. Your contacts are not used to train anyone's models, including ours. No human at MK Builds LLC reads your rolodex as a matter of course, and the encryption is arranged so that doing so takes deliberate effort rather than idle curiosity.

Encryption, and its limits

Every personal field is encrypted with AES-256-GCM under a key generated for your account and no other. That key is itself encrypted under a master key which is never stored in the database. A leaked database dump, a stolen backup, or anyone with read access to our tables gets ciphertext.

What this does not do is put the key beyond our reach, and no honest description can claim otherwise. A voicemail arrives when you are not there; transcribing it, pulling the people out of it and texting you back all require the plaintext, so the server must be able to decrypt your data without you present. Whoever controls the running service therefore can. Encryption here narrows who can read your rolodex to the people who operate Bridget; it does not narrow it to you.

No system is perfectly secure and we do not claim otherwise.

Recordings

When you call, Twilio records the message and we fetch it to transcribe. We do not store the audio; only the transcript, encrypted. Twilio retains recordings under its own policy, and if that matters to you, configure deletion in the Twilio account that runs this number.

Who else processes your data

TwilioCarries the phone call and delivers the recording.
SendblueCarries the text messages, over iMessage where available.
OpenAITranscribes the recording and extracts the people named in it.
NeonHosts the database the encrypted rows live in.
RailwayRuns the server.

Each receives only what its job requires, and their own privacy terms apply to what they hold. OpenAI receives the recording and the transcript in the clear, because transcribing and reading are the service it provides; it does not receive your existing rolodex except when answering a question, and then only the contacts needed to answer it.

Taking your data with you

Settings has a download link, and so does every page that lists your contacts. It hands you the whole rolodex as a CSV file that opens in any spreadsheet. Nothing is gated behind a request to us, and there is nothing to ask permission for.

Deleting your data

Settings has a "Disconnect Bridget" button. It erases your account, your contacts, your call history and your transcripts, and destroys the encryption key they were held under. Because the key is gone, the data is unrecoverable even from a backup taken beforehand: there is nothing left to decrypt it with. Download first if you want to keep anything.

Server logs record events like "a call arrived" with phone numbers masked, and roll off on their own. They contain no contact data.

Other people's information

Bridget stores notes about people you meet, who have not themselves agreed to anything. You are responsible for what you record about them and for complying with the law where you are. Do not use Bridget to collect sensitive categories of personal information, and record only what you would be comfortable showing the person concerned.

Changes and contact

If this policy changes materially we will say so here and update the effective date. Questions, requests, or a demand to erase everything we hold: legal@mkbuilds.dev.

Your rolodex is encrypted with a key belonging to your account alone, and you can download all of it whenever you like.