Privacy is treated as product scope, not legal decoration.

Core principle

We try to request only the permissions required for the feature being used. A feature that does not need calendar access should not ask for calendar access.

TimeBridge Assist

The current Assist beta does not require users to connect a calendar. It is designed as a suggestion-and-preparation layer that helps users work with timezone context directly while writing.

• No calendar connection required for the Assist beta flow
• No automatic sending of messages
• No backend scheduling automation in the current Assist beta posture
• No passive usage tracking in the first Assist public beta
• If a user explicitly sends QoS feedback, only the selected answer is submitted

TimeBridge Insight

Insight is being designed around the minimum Google Calendar access needed to avoid bad scheduling suggestions. The intended current direction is free/busy-style availability only.

• Busy/free availability access only
• No event titles
• No event descriptions
• No guest lists
• No attachments
• No Gmail message content accessed through Google for this flow

Who defines calendar access

Akiwaki defines the permission scope requested by the product. Google then displays that requested access to the user during the consent flow and asks the user whether they want to approve it.

User control

Users can choose whether to connect a calendar, and they can disconnect the calendar-based layer when they no longer want to use it. The product should make those controls visible and explicit.

Data use position

Calendar availability, when connected, is used to power scheduling suggestions. It is not intended for advertising, data sale, or cross-product profiling.

Contact

For privacy questions, write to privacy@akiwaki.com and include Privacy in the subject line.