Last updated: September 24, 2026
Dinghy is an AI assistant you text over iMessage (and, for older accounts, Telegram). When you connect accounts, it can read and summarize your email and calendar, draft emails and events, and send or create them only after you confirm. Dinghy is operated by Biscayne Ventures (“we”). Web pages at getdinghy.sh let you connect accounts and read this policy.
Your chat identity: the phone number or Apple ID handle you text Dinghy from (or your Telegram ID), your name if you give it, and your timezone.
Messages: your conversation with Dinghy, so it can keep context. Dinghy may also save short notes it learns about you (for example preferences you tell it) so it can help later.
Connected account tokens: when you connect Google, GitHub, Oura, WHOOP or PayBox, we store OAuth access and refresh tokens, encrypted with AES-256-GCM, plus the email address of each connected Google account.
Files and reminders you ask Dinghy to create.
If you connect a Google account, Dinghy asks for these permissions:
How we use it: only to provide the features you use in Dinghy, at your request or on a schedule you turned on (like the morning briefing). Dinghy never sends email or calendar invites without showing you the exact draft and getting your yes first.
What we store: your encrypted tokens and the account email. Email and calendar content is fetched when needed to answer you. Dinghy’s replies to you (which may quote or summarize that content) are kept in your conversation history. We do not keep a separate copy of your mailbox or calendar.
First look when you connect: when you connect Google, Dinghy takes one first look at your calendar and inbox headers (who you write to, subjects, and calendar titles and times, never message bodies). No AI model reads that first look. We keep a short summary in your account to show you in your first reply, and a few notes so Dinghy knows who matters. Say “forget” and a name to remove a note, or disconnect Google and Dinghy stops reading.
Who sees it: to answer you, the relevant email or calendar content is processed by the AI model provider behind Dinghy (currently Anthropic, through our own inference gateway). It is used only to generate your reply. We do not sell Google user data, do not use it for advertising, and do not use it to train AI models, ours or anyone else’s. People at Biscayne Ventures do not read your Google data, except with your permission, when needed for security or to investigate abuse, or to comply with the law.
Dinghy’s use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
We use these providers to run Dinghy. Each handles data only to provide its service to us:
OAuth tokens are encrypted at rest with AES-256-GCM. Connect links are single-use and expire. Access to production systems is limited to the people who run Dinghy.
We keep your data while your account is active.
Dinghy is not for anyone under 13, and we do not knowingly collect their information.
If we change this policy we will update this page and the date above. If a change affects how we use Google user data, we will tell you in Dinghy before it applies.
Questions or requests: halsey@biscayneventures.xyz. See also our terms of service.