Privacy Policy

MK Builds LLC · Effective 29 July 2026

The short version

Your contacts are not ours. They live in a spreadsheet in your own Google Drive, which you own and can export or delete without asking us. On our side there is one row per account: an opaque id, your phone number and your Google token, both encrypted, and the id of your spreadsheet. No names, no notes, no transcripts.

What we collect

Your phone number
Encrypted, and looked up through a keyed hash so we can find your account without the number being readable in our records. We need it to know whose rolodex a call belongs to and where to text back.
Your Google account
Your email address and a refresh token, both encrypted. The token is what lets Bridget write to the one spreadsheet it created.
Your spreadsheet id
Which file to write to. Not its contents.
Timestamps
When the account was created and last used.

What we do not collect

We keep no copy of your contacts, your notes, your call transcripts, or your messages. Those are written to your spreadsheet and read back from it when you ask a question. We do not sell data, we do not share it for advertising, and we do not build a profile of you.

What Bridget can see in your Drive

The permission requested is drive.file, which grants access only to files this app itself created. Bridget cannot read your other documents or spreadsheets, and cannot be granted that access without asking you again. You can revoke it at any time from your Google account permissions page and keep the spreadsheet.

Recordings

When you call, Twilio records the message and we fetch it to transcribe. We do not store the audio. The transcript is written to your own spreadsheet. Twilio retains recordings under its own policy; if that matters to you, configure deletion in your Twilio account.

Who else processes your data

GoogleStores your rolodex, in a spreadsheet in your own Drive that you own.
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.
RailwayRuns the server.

Each receives only what its job requires. Their own privacy terms apply to what they hold.

Security, and its limits

Everything identifying in our records is encrypted with AES-256-GCM under a key unique to your account, which is itself wrapped under a master key held only by the server. Someone reading our database sees opaque ids and ciphertext.

That protects our side. It does not protect your spreadsheet, which is stored in Google Drive under your own account and governed by your Google security settings. Anyone you share that file with can read it. No system is perfectly secure, and we do not claim otherwise.

Deleting your data

Settings has a "Disconnect Bridget" button. It revokes our access to your Drive and erases your registry row, which is everything we hold about you. Your spreadsheet stays in your Drive, because it is your file and deleting it is not ours to do. You can delete it yourself at any time.

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 lives in your own Google Drive. Bridget stores only the link to it, encrypted.