INTERLOCK

INTERLOCK TRUST

Trust and privacy.

Sync busy time across the calendars you choose without copying source meeting titles, attendees, notes or links. See what appears on another calendar, what access Interlock needs, and how to stop sharing.

Interlock is a product of Provisio Insights, LLC, Austin, Texas. Separate Busy blocks reserve your time without copying the original meeting to another calendar. Provider permissions can still let the service access calendar content, so review the access and processing details below.

What appears on another calendar

For the sharing directions you approve, Interlock creates separate Busy appointments marked Private and labeled “Blocked · source account.” Original meeting titles, notes, attendees, locations, attachments and meeting links are not copied. Your original meetings stay unchanged, and Interlock’s Busy blocks do not become new sources for onward sharing.

The source account label can be visible to people allowed to see the destination appointment. The destination calendar’s access rules determine who can see a block.

Calendar access and processing

Your passkey signs you into Interlock. Each Microsoft 365 or Google account connects through its own provider sign-in and consent. You select calendars, inspect a preview and approve individual sharing directions. Your organization’s app approval, access policies and calendar permissions continue to apply.

Cloudflare hosts Interlock’s processing, encrypted provider credentials and synchronization state. The service can decrypt those credentials and process availability on the server. Calendar permissions can allow access to more content and actions than the scheduling fields Interlock uses. These product controls still depend on the security of the service, authorized operators and connected accounts.

Google data and provider reviews

Interlock uses Google data for the calendar features you choose. At your direction, availability-derived Busy blocks go to the Microsoft 365 or Google calendars you approve. Interlock does not sell Google data, use it for advertising, or use it to train or improve general-purpose AI models. The privacy policy explains the restrictions on use, transfer and human access, including Google’s Limited Use requirements.

Provider setup as of (America/Chicago):

  • Google Calendar access is approved for the current Interlock setup. Additional applications, permissions or data uses need separate approval.
  • Microsoft publisher verification is incomplete.

Provider approval does not grant access to your calendars or replace your organization’s policy. Feature availability is shown in the app. See the IT admin guide for application identities and exact permission requests.

Pausing and removing access

Pausing stops future sharing updates; a change already sent to a calendar provider may still finish. Existing Busy blocks can remain. Cleanup acts only on records with validated Interlock ownership; lost access or uncertain ownership can leave it pending. Incomplete reads remain unknown rather than being treated as an empty calendar.

Disconnecting Google clears saved token values from Interlock’s active connection record but does not currently revoke Google’s authorization. To remove that authorization, use Google Account connections. Choose cleanup first if you want Interlock’s blocks removed: revoking access does not remove appointments and can affect other connections using the same Google project.

Retention and account closure

Account closure pauses sharing and asks whether to remove Interlock’s Busy blocks or leave them. Final closure retires Interlock sign-in and clears saved credentials from active connection records. Necessary ownership, repair, authorization, support, security, financial and referral records can remain.

The retention policy gives periods, approved targets and exceptions. Unresolved operations, legal or security preservation, recovery copies and external service copies can require separate handling. Closure does not promise complete erasure.

Beta scope and support

Feature availability is shown in the app. Provider outages, permission changes and unresolved operations can interrupt synchronization. This beta offers no uptime guarantee or security certification and is not approved for protected health information. Do not use PHI.

For support, privacy, calendar access or account removal requests, email hello@interlock.nexus or use Interlock Help. Please do not send passwords, verification codes, tokens or meeting content.