Privacy Policy

Effective date: June 18, 2026

Last updated: October 19, 2026

1. Who operates the service

Meet for Coffee is provided by the Build It Faster project, based in the United States. Contact us at support@bif.dev.

This policy covers the public site at start.coffee, the standalone web app at app.start.coffee, and the Google Meet add-on. The app connects through an automatically created guest session. No separate Google sign-in is required. The Google Meet integration also uses meeting and activity context to connect people to the same board.

2. Information collected

• Information you provide when contacting support, such as your email address and message.
• Your chosen display name, and a display name or avatar if supplied by the Meet integration.
• Google Meet add-on context needed to display the app during a meeting.
• Board content, such as agenda topics, notes, and votes. This content is encrypted in participants’ browsers and sent through InstantDB to other participants during the session.
• Guest authentication identifiers and live presence details, including display names and randomly generated connection identifiers, processed by InstantDB to connect participants.
• Usage analytics, such as visits to fixed page categories, approximate location, browser, and device information.
• Limited technical logs, such as IP address, device, browser, and diagnostic data.

3. Google Meet context and board content

The Meet add-on uses the meeting ID and activity starting information to connect participants to the same board. It derives an opaque room identifier from the meeting context. A display name or avatar supplied to the integration may be shown in the panel. Board access uses an InstantDB guest session rather than a separate Google account login.

Board content is encrypted before it leaves your browser. InstantDB passes encrypted updates between participants; it does not receive readable board content or save a board history. Display names, connection identifiers, and message metadata are separate from the encrypted content and are visible to InstantDB. Guest identifiers, support correspondence, and limited technical logs may be retained as needed to operate, secure, debug, and support the service. Google user data is not shared with advertisers or sold. Users can request deletion by emailing support@bif.dev.

Meet for Coffee's use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

4. How information is used

We use information to provide the web app and Meet add-on, authenticate users where needed, sync encrypted board updates between participants, respond to support requests, maintain security, debug issues, and improve reliability.

5. Data sharing and subprocessors

We use InstantDB for guest authentication, live participant presence, and delivery of encrypted board updates. Board updates are sent as live messages, rather than saved database records. Participants’ browsers hold the board and supply its current state to people joining the session.

We may share data with service providers that host the application, process support requests, or provide security and diagnostics. These providers may process data only as needed to deliver services for Meet for Coffee.

6. Analytics

We use Google Analytics to count visits to fixed page categories, such as the homepage, privacy, terms, and support pages. The website and app use separate analytics properties. Before sending a page view, we remove query parameters, invite details, dynamic paths and fragments, page titles, and incoming referrers. We send a fixed site title instead. We do not send board content, names, email addresses, or profile information to analytics.

Google Analytics receives technical information such as browser and device details and approximate location, and may use cookies or similar identifiers. Automatic enhanced measurement and Google signals are disabled. We do not configure user IDs or cross-site identity linking, or use analytics for advertising or remarketing.

Google explains how it uses information from sites and apps that use its services at policies.google.com/technologies/partner-sites.

7. Data retention and deletion

Guest authentication records and support correspondence may be retained as needed to operate and support the service. Technical logs are retained for a limited period needed for security, debugging, and compliance. Boards are held in participants’ browsers and are not saved as a server-side history. Once everyone closes the board, it cannot be recovered from the service. Copy the board as Markdown before leaving if you need a record. Display names and session identity details may also be kept in browser storage; these are separate from board content. Users may request account and data deletion by contacting support.

8. Security measures

We use HTTPS, access controls, least-privilege permissions, logging, and operational review practices designed to protect user data.

9. User choices and rights

You can export a board as Markdown, clear browser storage to remove locally saved display names and guest sessions, or uninstall the Meet add-on. Contact support to request access, correction, or deletion of information retained about you. Support cannot recover a board after all participants have left.

10. Children's privacy

Meet for Coffee is not directed to children under 13, and we do not knowingly collect personal information from children under 13.

11. Policy changes

We may update this policy as the service changes. Material changes will be reflected by updating the date at the top of this page.

12. Contact information

Email support@bif.dev for privacy, support, or deletion requests.