How Papan uses the Google Calendar API and the Gmail API

1. User-initiated consent (Profile → Koneksi Google)

/profile

Every user connects their own Google Account. Nothing is requested until the user clicks Connect, and each connection can be revoked from the same screen. No Google data is read for users who never connect.

• openid
• email
• profile

2. Planner — reading and writing calendar events

Board → bottom navigation → Planner

The Planner sidebar shows the signed-in user's own events on an hourly timeline next to their board. Dragging a card onto the timeline creates a calendar event for that task; changing the card's schedule updates that same event. Without the write scope the drag-to-schedule feature cannot exist; without the read scope the timeline is empty and users would double-book themselves.

• https://www.googleapis.com/auth/calendar.events
• https://www.googleapis.com/auth/calendar.readonly

3. Gmail panel — email into tasks, replies from a card

Board → bottom navigation → Gmail

The Gmail sidebar lists the user's recent messages so they can drag an email onto a list and turn it into a card (subject becomes the title, body becomes the description). From that card the user can send a reply to the same thread. Read access is needed to display and copy the message; send access is needed for the in-card reply. Papan never reads mail in the background and never sends without an explicit user action.

• https://www.googleapis.com/auth/gmail.readonly
• https://www.googleapis.com/auth/gmail.send

4. Where the data lands

Board view

Google data is only used to populate the card the user created and the Planner timeline they are looking at. Message bodies and event details are shown to that user only, are not shared with other board members unless the user puts them into a card, and are never used for advertising, resale, or model training.