Lantern

PRIVACY

Privacy Policy

Effective 13 September 2026

Lantern is a conversation memory and follow-up prototype. This policy explains the information Lantern handles when you sign in, connect a device, process a conversation, or connect Google Calendar.

Information Lantern handles

  • Your Google account identifier, email address, and display name.
  • Audio you choose to capture, transcripts, summaries, contacts, commitments, and follow-up drafts.
  • Google Calendar authorization tokens, granted scopes, availability, and events you explicitly approve.
  • Paired device identifiers, firmware version, connection status, battery level, and operational logs.

How information is used

Lantern uses this information to authenticate you, keep your workspace separate, transcribe and summarize conversations, prepare follow-ups, show device status, check availability, and create an approved Calendar event with its invitation and Google Meet link.

Google user data

Lantern requests Calendar event access so it can create or update only the meetings you approve. It requests free/busy access to check whether a proposed time is available. Google credentials are encrypted before storage and are tied to the Lantern account that granted access. Lantern does not sell Google user data or use it for advertising.

Lantern's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

Processors and sharing

Lantern uses service providers to run the product: Supabase for account and database storage, Vercel for hosting, Agora for live audio transport and speech services, and OpenAI for transcription and structured meeting understanding. When Exa is enabled, Lantern sends public company names for research; it does not send recordings, transcripts, or contact email addresses to Exa. Calendar data is sent to Google only to complete the Calendar features you request.

Storage, security, and retention

Workspace rows are partitioned by user ID. Recordings are stored in a private bucket and played through short-lived links. Calendar tokens are encrypted on the server. Lantern keeps account and workspace data while the prototype is operating or until deletion is requested, subject to necessary backup and security retention.

Your choices

You can decline Calendar access and still sign in. You can revoke Lantern in your Google Account permissions. To request access, correction, export, or deletion of your Lantern data, email nathanhor2001@gmail.com.

Contact and changes

Questions can be sent to the address above. Material policy changes will be reflected on this page with a new effective date.