Privacy policy

When you use Calfolio with Google, we receive data only through Google OAuth and Google APIs, and only for the purposes described below. We request the minimum scopes needed for each surface.

Data accessed

Depending on what you connect and which product surface you use, Calfolio may access:

• Identity from Google — for example your verified Google email address and Google account identifiers (such as OpenID Connect subject) used to link your Google sign-in or Google Calendar connection to your Calfolio workspace.
• Google Calendar content and metadata — for calendars you choose to connect and include, this can include calendar list entries, event identifiers, event titles, start/end times, recurrence-related identifiers, organizer fields when present, and other fields returned by the Google Calendar API needed to sync, categorize, and display events in Calfolio.
• Google Workspace add-on execution context— when you open the Calfolio add-on inside Google Calendar, Google sends the add-on runtime information needed to render the add-on (including identifiers for the open event when applicable). The add-on uses Google-issued tokens as described in Google's Workspace add-on documentation so Calfolio can show summaries and links tied to your workspace.
• Optional Google Sheets / Drive (only if you use export) — if you explicitly use a feature that creates a Google Sheet, Calfolio may request additional Google OAuth scopes limited to creating or updating files the user selects or that the app creates (for example drive.file / Sheets-related scopes as shown on the consent screen for that flow).

Scopes (web / Chrome extension — Google Calendar connection): Calfolio's dedicated Google Calendar OAuth flow requests calendar.readonly, userinfo.email, and openid(exact URLs as shown on Google's OAuth consent screen). Optional export flows may request additional scopes only when you start an export that needs them.

Scopes (Google Workspace Marketplace Calendar add-on): the Marketplace add-on uses the scopes configured on the add-on's OAuth consent screen (for example Workspace add-on execution and user email as shown at install/consent time). Calendar data shown in the add-on reflects your Calfolio workspace's synced calendar data and policies, not a second copy of Google outside that contract.

Data usage

We use Google user data only to provide and improve the Calfolio product experience, including to:

• authenticate you and connect the correct Google account to the correct Calfolio workspace;
• sync selected calendars into your workspace so events can be categorized, reviewed, and reported on;
• show in-product summaries (including in the Chrome extension and Calendar add-on) such as alignment, goals, uncategorized counts, and event context;
• operate exports you request (for example to Google Sheets) where applicable;
• maintain security, prevent abuse, and troubleshoot service issues.

AI / ML training: Calfolio does not use Google user data obtained through Google APIs to develop, improve, or train generalized artificial intelligence or machine learning models.

Data sharing

We do not sell Google user data. We do not share Google user data with advertisers.

We share data with service providers (subprocessors) that help us run Calfolio — for example cloud hosting, database/authentication providers, logging, and billing/payment infrastructure. Subprocessors process data only under our instructions and appropriate agreements, and only to the extent needed to provide the service.

Data storage & protection

Google-derived data and OAuth tokens needed for sync are stored using industry-standard practices: data is encrypted in transit (HTTPS), access is authenticated and authorized at the workspace level, and secrets are handled with restricted access appropriate to production systems. Exact retention for specific logs may vary as needed for security and operations.

Data retention & deletion

We retain Google-derived workspace data while your workspace is active and while you keep Google Calendar connected, subject to product features (for example disconnecting Google Calendar stops further sync).

You can request deletion of personal data or close an account/workspace by contacting support@alpinebluelabs.com. We will respond consistent with applicable law and verify ownership as needed.

Calfolio connects to the Google Calendar account you choose to use with your workspace.

To generate categorization, uncategorized review, workload views, and exports, Calfolio needs access to selected calendar event data within the product's supported planning and history windows.

This may include information such as:

• calendar names you choose to include
• event titles
• start and end times
• event timing needed for charts, workload, and capacity views
• event records needed for categorization, review, and export

Calfolio is intentionally narrow: Google Calendar in, structured insight out.

Calfolio stores workspace-level data that helps turn raw calendar events into something more useful for reporting and review.

This can include:

• workspace details and settings
• selected included calendars for analytics
• categories created by the workspace
• category rules and matching logic
• manual event overrides
• capacity-related settings or flags
• reporting and export preferences

In plain terms: Google Calendar provides the event stream, and Calfolio stores the structure you add around it.

Calfolio is a layer on top of Google Calendar, not a replacement calendar.

Calfolio is not designed to replace Google Calendar.

Google Calendar remains the source of truth for scheduled events, timing, and the day-to-day calendar workflow your team already uses.

Calfolio's role is to help workspaces:

• categorize time more clearly
• review uncategorized or messy event patterns
• understand capacity and workload
• create cleaner exports and reporting views

That means the product is built as a layer on top of your existing calendar workflow, not as a second calendar you have to maintain.

The Chrome extension is intended to bring lightweight Calfolio actions closer to where users already work inside Google Calendar.

Examples may include:

• categorizing an event faster
• including or excluding an event from analytics or capacity views
• jumping into related Calfolio insights
• reviewing cleanup actions with less context switching

Exports are intended to help workspaces take categorized calendar data into practical follow-up workflows, such as:

• CSV export
• Google Sheets export
• internal reporting or review

Exported data reflects the event and categorization data included in the selected export view.

Calfolio is designed so workspaces can control what is included in their reporting scope.

That includes choices such as:

• which calendars are included for analysis
• which categories and rules are active
• when manual overrides are applied
• what gets included in exports
• how workload and capacity views are configured within the product

The permissions you grant and the OAuth scopes we request should always be clear in the product when you connect Google Calendar.

This gives teams a clearer and more intentional view of time without asking them to abandon the calendar workflow they already trust.

This policy describes Calfolio's handling of Google user data in connection with Google Calendar, Google OAuth, the Chrome extension on Google Calendar, and the Google Workspace Marketplace add-on.

Calfolio does not replace Google Calendar; Google Calendar remains the scheduling system of record. This page does not describe unrelated Google products unless you choose integrations that explicitly use them (such as optional Sheets export).