INTERLOCK

A CLEARER VIEW OF PRIVACY

Share the time.
Keep the context.

Where your busy time goes, what Interlock can access, and how to manage your data.

Effective .

Who operates Interlock

Interlock is a product of Provisio Insights, LLC, Austin, Texas, branded Interlock by Provisio Insights. Email hello@interlock.nexus for privacy, support, calendar access or account removal requests. We may verify control of your Interlock account before acting on a request. Do not send passwords, verification codes, tokens or meeting content.

Availability, without the meeting

Interlock is designed to block busy time on the calendars you choose using separate appointments labeled Blocked and the source account. That account label can be visible to people with permission to see the destination appointment. Each busy block is marked Private. It has no attendees and sends no invitations. Original titles, notes, attendees, locations, attachments and meeting links are not copied. Your original meetings stay unchanged. Busy blocks created by Interlock are not shared onward as new busy time.

Optional meeting details in your signed-in view

Where this feature is assigned to your account, you can choose to view original calendar events inside Interlock. The policy for each connected tenant controls whether titles, joining links, organizer and attendee information, notes, attachments and details of Private events are available. Your provider access still applies. A feature assignment does not override those restrictions.

Interlock requests permitted details when you open this view and clears them from the view when it closes. They are not saved in the Busy-time display cache or added to shared Busy blocks, public booking pages, support capture or the OpenAI/MCP connection. Attachment downloads are separate actions and remain on your device if you save them. Some provider attachments can only be opened with that provider.

Booking meetings and guest information

Booking is separate from Busy time synchronization. If you use a booking link, Interlock processes the guest name, email address, time zone, chosen time and answers submitted to the host’s questions, along with the meeting title and selected location or connection details. Guest contact information and answers are stored encrypted on Interlock’s service. Anyone with an unlisted booking link can see the host’s published profile, meeting description and offered times. Keep sensitive information out of that published content. Do not put passwords, payment details or protected health information in booking answers.

Confirming a booking can create a meeting on the host’s chosen calendar and send an invitation to the guest. That meeting includes the title, guest name and email, time and selected video, saved meeting link, phone or in person location. Booking answers are not copied into the provider event. The calendar and conferencing providers handle the resulting meeting and invitation under their own access rules. A booking is a new meeting with its own attendees and contact information.

A private management link can let anyone holding it view, reschedule or cancel that booking, subject to its current status. Keep the link private. Management access expires 30 days after the meeting ends unless revoked earlier. Revoking access or closing an account does not itself delete calendar invitations or provider copies.

Comparing your calendars while booking

You can separately choose to compare a host’s available times with calendars you authorize. Google comparison asks for sign-in identity, calendar list access and read-only event access. Interlock requests scheduling fields such as event times and your attendance status to calculate availability. Google’s permission allows access to more meeting details than those requested fields. Microsoft comparison asks for identity and basic calendar read access. These comparison connections do not request offline access or calendar write permission. Interlock processes the selected calendar labels and merged busy intervals to calculate bookable times. The host is not given the names, event details or busy intervals from your other calendars.

A temporary comparison expires after 30 minutes. Its encrypted access credential expires no later than that comparison, and no refresh token is retained for it. Expired comparison records and credentials are handled by cleanup in limited batches, so expiry does not promise immediate physical deletion from every copy.

Signing in or creating an account is a separate, optional choice; booking and calendar comparison do not automatically create an Interlock account or save a permanent calendar connection. Where account creation is available, it requires your explicit consent, email verification and a passkey. Private testing still requires an invitation. After signing in, a separate Keep connection choice can save your provider and selected calendars for future comparisons, along with only the existing expiring credential for up to one hour. Saved choices are encrypted and remain until you forget them or close your account. This does not grant ongoing background access. After the credential expires, you must reconnect with the same provider identity to use those choices again.

Booking data retention

Booking confirmation codes expire after 10 minutes. Ordinary verification records become eligible for cleanup 24 hours after expiry; records for uncertain email delivery are retained for seven days after expiry before cleanup. Cleanup runs in limited batches.

Private-test invitation checks are separate. They use an encrypted email address and a code that expires after 10 minutes. Verified guest access lasts up to 30 minutes, and the admission record expires no later than 40 minutes after the request. Expiry stops access immediately. Expired admission records are removed in limited batches when new guest requests are handled.

Booking records, encrypted guest responses and records of requested calendar changes are retained to manage the meeting, reconcile unresolved changes and handle support or security needs. The booking records themselves do not currently have an automatic deletion period. Contact Interlock Help to request deletion or minimization and an explanation of any records that must remain. Calendar invitations, email and conferencing copies have their own provider retention and removal rules.

Google Calendar data

When you connect Google Calendar, Interlock uses your Google account identifier and email address to identify that connection. It reads your calendar list, calendar names and access roles so you can choose calendars. Normal source-calendar processing requests event identifiers, start and end times, status, transparency, event type, limited attendee self/response-status fields and Interlock ownership markers. Safety checks on destination events can request additional event fields to determine whether an event is a valid Interlock Busy block. Calendar names, connection labels and identifiers support calendar selection and safe synchronization. With your approval, Interlock creates, updates and removes its own blocks on selected destination calendars.

The default Google event permission covers calendars you own. Reading shared calendars or writing blocks to a shared destination requires the corresponding permission, requested when you choose that feature. Calendar permissions can allow access to more event content than Interlock requests.

How Google data is used and shared

Interlock uses Google data to provide and improve the calendar features you choose. At your direction, availability-derived Busy blocks are sent to the Microsoft 365 or Google Calendar destinations you approve. Those providers and people with permission to view a destination can access the resulting blocks under that calendar’s access rules. Cloudflare hosts Interlock’s processing, encrypted credentials and synchronization state. Google and Microsoft receive the API requests needed for your selected features.

Interlock does not sell Google data, use it for advertising, creditworthiness or lending decisions, or use it to create, train or improve general-purpose AI models. Transfers are limited to the user-facing features you authorize, necessary security purposes, applicable legal requirements, or a merger, acquisition or asset sale with your explicit prior consent.

People may read Google Calendar data only with your documented affirmative permission to view specific data, when necessary to investigate a security issue such as a bug or abuse, when required by law, or when aggregated and anonymized data is needed for lawful internal operations. Employees, agents, contractors and successors must follow these restrictions.

Interlock’s use and transfer of information, including raw and derived data, received from Google APIs complies with the Google API Services User Data Policy, including its Limited Use requirements.

Connecting an AI app

Interlock does not run an AI model to synchronize calendars. Its optional Model Context Protocol (MCP) connector lets compatible, authorized clients request limited information after you approve access. These can include AI apps such as ChatGPT. MCP is a connection protocol; it does not itself run an AI model. The connector returns merged busy-time intervals from your selected calendars, the requested time window, completeness information and calendar sync status. These results can include information derived from Google Calendar data. Meeting titles, descriptions, attendees, locations, calendar names, event identifiers and provider credentials are not included in these tool results. The connector cannot book meetings, edit calendars or change sharing.

The connected client receives these results to provide the functionality you request. Its own privacy policy, plan and account settings govern how it processes and retains that information. Use this connection only with a receiving service and configuration that exclude Google data, including derived availability, from training or improving general-purpose AI models. Do not submit conversations containing that data as model-training feedback or opt them into data sharing for training. For an AI client, Interlock does not receive or independently verify your subscription tier, model selection or training settings; approving a connection does not change those settings. A particular user’s plan or opt-out setting is not a service-wide protection.

You can disconnect an app in Interlock’s Connected apps settings. Disconnecting stops future access through that connection; it does not remove information already received by the connected app. Our Google Limited Use commitments above also apply to Google-derived MCP results.

Your accounts connect independently

Your passkey signs you into Interlock. Connect each provider account with its own sign-in and consent, then choose its calendars. Shared or delegated calendars need the appropriate provider access. You approve individual directions and inspect a preview before enabling sharing. A route from A to B does not approve B to A or any other route. Provider app approval and access policies remain authoritative.

How we protect Google Calendar data

Connections to Interlock’s production service and the Google APIs used by Interlock use HTTPS. Saved Google access and refresh tokens are encrypted using AES-256-GCM, with encryption keys configured as server-side Worker secrets. Encrypted records are bound to their owner, connection and purpose to protect them against unauthorized changes or use in another record’s context. The service can decrypt those credentials to process availability and run authorized synchronization on the server.

Interlock checks the signed-in session and account ownership for user-requested operations. Before changing Busy blocks, it checks the recorded authorization, calendar permissions and validated Interlock ownership. Operational error reporting uses an allowlisted diagnostic format that excludes Google account identities, credentials and calendar content, as described below.

These protections do not make Interlock end-to-end encrypted or prevent the service from accessing information allowed by a provider grant. Provider calendar permissions can allow reading calendar content and changing appointments beyond the fields Interlock normally uses. Scheduling-field requests and blocks without meeting details are product controls, not a provider-enforced guarantee that the service or its operators cannot access calendar content. Endpoint compromise, service compromise and authorized code changes remain risks. Human access remains subject to the restrictions above.

Pausing and disconnecting

Pausing stops future sharing updates and can leave existing Busy blocks in place. Disconnecting has separate cleanup choices. Cleanup changes only records with validated Interlock ownership. Lost access or uncertain ownership can leave cleanup pending. Incomplete calendar reads remain unknown rather than being treated as an empty calendar.

Disconnecting Google clears the saved access and refresh token values from Interlock’s active connection record; it does not currently revoke Google’s authorization. You can remove Interlock in your Google Account connections. Google-side removal can affect other connections using the same Google project. Revoking access does not remove existing calendar appointments, so choose Interlock’s cleanup option first if you want its blocks removed. Recovery copies have separate retention.

Support, diagnostics and your browser

Support and access requests contain the contact information and text you submit. They can be handled through our Microsoft 365 mailbox and, when enabled, HubSpot for customer support. Linear receives fixed bug-triage fields and an opaque case reference. Interlock does not automatically attach calendar content or Google provider responses to either service. Do not include meeting details, credentials, card information or other sensitive material in a request.

Sentry error reporting uses fixed operational categories, counts, service versions, generated diagnostic identifiers and limited source locations. It excludes Google account identities, credentials, calendar content, request bodies and source contents. A diagnostic reference can connect your support case with limited error evidence. Session replay and advertising trackers are not used.

Authentication uses a secure session cookie. Your appearance preference is saved in this browser on this device.

Referral links and optional measurement

If you open a referral link, Interlock can keep its code in this browser tab while you request access and sign in. After joining, you choose whether to apply it in Settings → Referrals. Applying a code records who referred you; it does not connect calendars or change your plan. Rewards are unavailable during the free beta.

Optional interface experiments help us compare onboarding wording. We count first-party exposures and successful first calendar connections using pseudonymous identifiers, without calendar content, account labels or email addresses. Records expire 30 days after an experiment starts. We honor Do Not Track (DNT) and Global Privacy Control (GPC) by excluding those requests from collection.

Account closure and retained records

Start account closure in Settings. Sharing pauses while you choose whether to remove Interlock’s Busy blocks or leave them in place. Cleanup can remain pending if access is lost or ownership cannot be verified. Any subscription must finish cancellation, and uncertain billing operations must be resolved, before closure can finish.

A final passkey confirmation retires your Interlock sign-in, clears saved provider credentials from active connection records, removes saved account identity hints and preferences, and minimizes saved calendar labels. Referral links are disabled and related attributions are closed. Necessary ownership, repair, authorization, support, referral, financial and security records can remain. Closure does not promise complete erasure. Contact us to request deletion or minimization and an explanation of any necessary retention.

Retention periods and targets

Connection and repair state: we keep necessary state while a connection is authorized or cleanup remains unresolved. Our approved target is to remove or minimize unneeded personal data within 30 days after final closure or completion of your choice to remove or leave blocks. This requires review; it is not a universal automated purge of records needed to finish cleanup or prevent unauthorized use.

Support and access requests: ordinary case content has a 180-day period from original case creation; adding a message does not extend it. After expiry, in-app access and delivery stop and eligible records enter cleanup in limited batches. Access-decision history, operations whose outcome is unknown and preservation requirements can retain minimum records longer. Expiry does not establish immediate physical deletion, and mailbox, HubSpot, Linear and previously exported copies require separate disposal.

Routine diagnostics and experiments: our routine Sentry error-event target is 30 days, consistent with the current service plan’s event window. Organization audit history and exported copies are separate. Experiment records expire 30 days after the configured experiment start, not after collection; expired records are excluded from reports and await cleanup in limited batches.

Security records and recovery copies: our approved targets are 90 days after resolution for routine security/abuse evidence and a maximum 30-day recovery window. Minimum records that prevent old permissions being reused, and unresolved repair or security records can require longer retention. The current database recovery facility has a 30-day window; this does not prove physical deletion from every vendor system or independent export.

Financial and referral history: we retain only the fields needed for financial, attribution, dispute and legal obligations. A fixed financial-record retention period has not yet been adopted; ask us for the applicable reason and review status.

A documented legal or security preservation requirement can pause disposal of affected data. We review the purpose, minimum fields and continuing need before disposal resumes. These approved targets do not promise that all service, backup, mailbox or vendor copies disappear on the same day. We will tell you when a deletion request is limited by a necessary record, unresolved operation or provider copy.

Billing and current limits

Paid subscriptions are not available.

Feature availability is shown in the app. This page describes the beta. Provider outages, access changes and incomplete reads can interrupt synchronization. This beta does not offer an uptime guarantee or security certification. Interlock is not approved for protected health information. Do not use PHI.

We will update the effective date and give appropriate notice of material policy changes. A new use of Google data requires the appropriate notice and consent before that use begins. Read the beta terms for the current service scope.

Sign in to Interlock

Your passkey signs you in securely.

Preparing sign-in…

Need help?

Use the device or password manager where you saved your passkey. You can choose another device in the browser prompt. Still stuck? Contact support below.

Lost your passkey? Recover your accountContact support
Have an invitation?