LongevLab Care Portal
Calendar privacy policy
Last updated: 31 October 2026
This policy explains how LongevLab handles connected-calendar data from Google, Microsoft and Apple iCloud when you connect your own calendar to the Care Portal.
Who operates the connection
LongevLab operates the Care Portal calendar integration. Contact hello@longevlab.com for support, privacy questions or a deletion request. This policy covers the connected-calendar feature. Your clinic controls its patient records under its own notices and agreements; connecting a calendar does not grant access to patient records.
What we access and why
- Calendar list and account identity: calendar identifiers, names, access roles and available time-zone information let you choose calendars for conflict checks and appointment copies. Provider-specific account identity information binds reconnection to the saved account. Google uses its primary calendar identifier, Microsoft its authenticated default calendar identifier, and CalDAV its authenticated server address and account username.
- Availability: we use event identifiers, start and end times, time zone, cancellation and availability flags, and technical properties needed to recognize copies created by this integration. Google and Microsoft conflict-check requests exclude personal event titles, descriptions, locations and attendees. Apple CalDAV can return complete calendar resources that include those details. The service processes those resources in memory to derive availability; it does not store personal event text as conflict data. The portal receives generic Busy intervals.
- Clinic appointment copies: we create, read, update and delete the integration's own copies on selected writable calendars. Each copy contains the generic title Clinic appointment, start and end times, time zone and a technical synchronization identifier. It is marked private and contains no patient name, service type, clinical notes, description or location. The integration adds no attendees or reminders. Technical event metadata and synchronization status let us update the correct copy and retry failures.
- Google and Microsoft authorization: the provider supplies access and refresh tokens after you approve its permissions. LongevLab does not receive your Google or Microsoft account password. Google permission covers reading the calendar list and reading or editing events. Microsoft permission covers reading or editing your calendars and maintaining authorized access while you are away.
- Apple iCloud authorization: you provide your Apple Account email, calendar server address and an app-specific password. The service uses them to authenticate the CalDAV connection. Do not supply your main Apple Account password. This connection does not use an Apple OAuth permission screen.
The integration uses only calendars selected for conflict checking or appointment copies. It requests no calendar-sharing administration or email-message permission. A selected read-only calendar can be used for conflicts without receiving appointment copies.
How we use and share calendar data
We use connected-calendar data to provide the features you choose: listing calendars, checking conflicts, synchronizing clinic appointment copies, showing connection status, and reconnecting the same account. Authorized staff in your clinic's scheduling workflow can see Busy intervals and appointment information as permitted by their portal role.
Appointment-copy data is sent to the selected provider. It can be seen by people who already have access under the destination calendar's settings; marking an event private is not a guarantee against access by a calendar owner or administrator. The integration does not add attendees or send invitation emails.
Infrastructure providers process data to operate the service under our instructions. Google, Microsoft and Apple process their connected calendars under their own account and privacy terms. We do not sell connected-calendar user data, use it for advertising, send it to AI providers or use it to train AI models. Human access is limited to the user-facing features you authorize, necessary security or support investigation with appropriate authorization, and legal obligations.
LongevLab Care Portal's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.
Storage and protection
Access and refresh tokens, CalDAV credentials including app-specific passwords, connected-account identity, calendar identifiers and calendar names are encrypted in the clinical API's server database. Provider tokens and saved CalDAV credentials are not stored in portal browser storage or included in patient exports. The app-specific password passes through the connection form when you submit it; use only the intended Care Portal connection screen. Connections use encrypted transport. Tenant and staff authorization controls restrict access.
Connection state, calendar selections, synchronization identifiers, copy receipts, error status and audit records are stored to operate the connection and reconcile changes. Personal event text is not stored by the conflict-check feature. Busy intervals are computed for the requested scheduling window.
Disconnect, retention and deletion
In Calendar, open Connect your accounts and choose Disconnect. This stops new copies and queues removal of the integration's clinic appointment copies, including past copies. Tokens or the app-specific password remain encrypted only while that cleanup is unresolved and are removed from the active connection after removal is confirmed. If access has expired or been revoked, cleanup can need a same-account reconnect or manual removal of the copies in the provider calendar.
The portal retains the encrypted account identity to prevent reconnecting a saved connection to another person's account. Connection metadata, calendar records, appointment history, synchronization receipts and audit records can remain after disconnect for reconciliation, security and the clinic's record obligations. Disconnect does not erase the clinic's appointment history or immediately erase protected backups. Backup copies age out under the applicable backup retention schedule.
For deletion of retained connection data, contact hello@longevlab.com. We will identify the account, explain any retention needed for security or legal obligations, and handle the request under applicable data protection law. We do not promise instant deletion of unresolved remote copies or records that must be retained.
You can revoke Google's grant at Google Account connections. For Microsoft, use the app-permission controls available for your personal or work account; your organization's administrator may manage them. For Apple, revoke the app-specific password in your Apple Account. Portal disconnect removes our stored credentials after cleanup; it does not itself revoke the provider's grant or Apple password. If possible, disconnect and let cleanup finish before revoking access.
Your choices and policy changes
Connecting a calendar is optional. You can review Google or Microsoft permissions, manage Apple's app-specific passwords, change calendar selections, disconnect, request access or correction, request deletion or restriction, or raise a privacy concern at hello@longevlab.com. Where applicable, you can complain to your data protection authority, including the CNPD in Portugal.
We will update this page when the feature's data practices change. If a change needs new permission, we will ask before using connected-calendar data for that new purpose. See also the calendar connection terms.