This Privacy Policy (the “Privacy Policy”) describes how Blueprint X Labs Inc. (“Key,” “Key.ai,” the “Company,” “we,” “us,” or “our”) collects, receives, uses, processes, stores, shares, transfers, retains, and deletes personal data in connection with the Key platform, including its websites, applications, communities, Event Manage dashboard, AI-assisted functionality, connected communication channels, and integrations (collectively, the “Platform”).
This Privacy Policy forms part of, and should be read with, our Terms of Use. If any general statement in this Privacy Policy or the Terms of Use conflicts with the Google API Data protections in Section 5, the more restrictive Google-specific protections apply to that data. Connecting a Google service requires a separate authorization process; merely using Key does not authorize us to access Gmail, Calendar, or Contacts.
1. Scope and Application
This Privacy Policy applies to information processed in connection with: (a) account access, authentication, and profiles; (b) Organizations, communities, Events, and communication features; (c) interactions with Key and AI-assisted features; (d) data received from public and third-party sources; and (e) integrations a user or authorized Organization administrator enables.
Third-party services, including Google and WhatsApp, may maintain their own independent data-processing practices, governed by their respective notices. This does not relieve Key of its obligations for data it obtains or processes through those services.
2. Categories of Information We Collect
2.1 Information you provide
We process information you provide, including name, email address, phone number, credentials or authentication identifiers, profile and professional information, Organization and Event configuration, guest information, user instructions, messages, files, feedback, and communications with Key.
2.2 Information collected automatically
We process device, browser, operating-system, approximate location derived from network information, IP address, session and usage metadata, security events, application diagnostics, and necessary cookies or similar technologies, subject to applicable settings and law.
2.3 Information from public and third-party sources
We may obtain professional, organizational, and other information from public sources or service providers as otherwise described in this Privacy Policy. Such information may not always be complete or current.
2.4 Connected Integrations and Google API Data
Where a user enables a Connected Integration, we process information necessary for the enabled features and within the permissions granted. Examples include connected account identifiers, authorization records, activity or event metadata, and content requested through the integration.
For Google services, the specific categories and purposes are:
- Google Sign-In: basic identity information, such as name, email address, and profile information, to authenticate a user. Sign-in does not itself authorize Gmail or Calendar access.
- Gmail: when a user separately connects Gmail, we process relevant messages, threads, message bodies, headers, drafts, and message or sending status to enable user-requested searches, contextual answers, summaries, and email drafting. The
gmail.readonlypermission supports retrieving message content;gmail.composesupports creating and managing drafts and permitted message-sending actions. Gmail authorization and API operations are handled by Key's native backend services, not Composio. - Google Calendar: we may process available calendar identifiers and lists (
calendar.calendarlist.readonly), free/busy availability (calendar.freebusy), event information, descriptions, times, and attendee details (calendar.events.readonly), and event creations, modifications, or cancellations (calendar.events), in connection with user-authorized scheduling workflows. We request read or manage permissions as required by the relevant feature and authorization flow. Google Calendar authorization and API operations use Composio Cloud as a third-party integration service. - Google Contacts: when an event organizer deliberately opens the guest-invitation workflow in the Event Manage dashboard and authorizes access,
contacts.readonlypermits retrieval of names and contact details for manual invitee selection. The contact list is retrieved in the browser; only selected invitee details are submitted for invitation workflows. Kai does not independently search Google Contacts, and the contact list is not supplied to AI models for general search or inference. - Google Meet: meeting identifiers and, if a user separately enables meeting assistance or notes, the related meeting information or media required for that feature, subject to applicable notices and permissions.
“Google API Data” in this Privacy Policy means user data obtained through Google APIs, including information obtained through sensitive or restricted Google scopes and data derived from that information, such as user-facing summaries or meeting-related responses. The restrictions in Section 5 apply regardless of whether the information appears in raw, summarized, cached, or derived form.
3. How We Use Information
Subject to the Google-specific restrictions in Section 5, we use information to operate and secure the Platform; authenticate users; support Organizations, events, messaging, and community features; deliver user-requested AI-assisted features; provide customer support; diagnose and prevent misuse; comply with law; and, for information not subject to the Google Limited Use restrictions, perform lawful service improvement and analytics as described in this Policy.
Advertising: Key does not currently use personal data for advertising. If we introduce advertising using eligible, non-Google information in the future, we will update applicable disclosures and provide required choices. Google API Data, including information derived from it, will never be used for advertising, retargeting, profiling for advertising, sale to data brokers, creditworthiness assessments, or lending purposes.
Broad descriptions elsewhere in this section of analytics, product improvement, derived information, or AI Features do not authorize any use of Google API Data prohibited by Section 5.
4. Artificial Intelligence and Automated Processing
4.1 User-facing AI processing
Key's AI-assisted functionality may process user instructions, relevant authorized integration results, and other contextual information to answer requests, retrieve information, summarize messages, and support scheduling and communication. Users may access authorized integration functionality through supported Key interfaces, including the web application and connected communication channels such as WhatsApp. Google connectors are authorized separately from basic sign-in.
For Google API Data, AI processing is limited to providing or improving the specific user-authorized, user-facing feature. Where a Google message or event is needed for a request, relevant content may be sent to an AI inference service to produce the response. We minimize the data included and do not use Google API Data to build general training datasets, train a generalized AI model, or improve a model for unrelated users.
4.2 AI and infrastructure providers
We use Google Cloud Vertex AI as our inference platform for models including Google Gemini and Anthropic Claude accessed through Vertex AI. Model routing may vary according to the requested feature. Authorized Google API Data may be included in the relevant, minimized inference context for the particular user's request. Our Google integration does not rely on direct API calls from Key to Anthropic for this workflow. Applicable inference providers must process this information under contractual and data-use restrictions compatible with Google's Limited Use requirements. Neither Key nor providers processing Google API Data on Key's behalf may use that data to create, train, or improve generalized or non-personalized AI or machine-learning models.
We use temporary request context and, only where separately enabled by the user, limited personalized context necessary for an authorized feature. Google-derived context is subject to the retention, deletion, and Limited Use requirements in Section 5 and does not become a permanent general-purpose model-training corpus.
4.3 AI output limitations
AI-generated outputs can be incomplete or inaccurate. Users should review consequential communications, meeting changes, and other actions. The Platform requires explicit, action-specific user confirmation before sending an email or modifying a Calendar event through the connected assistant.
5. Connected Integrations and Google API Limited Use
5.1 Authorization, purpose, and minimum permissions
Connected Integrations are optional. Google services are connected through explicit OAuth authorization, and requested permissions are limited to the functionality selected by the user. For example, Gmail permissions support reading messages and managing drafts and sending; Calendar permissions support reading schedules or, where separately enabled, creating or changing events; Contacts permission supports guest selection in Event Manage.
Google Login is distinct from Gmail, Calendar, and Contacts connector authorization. We do not request expanded permissions at sign-in merely because other integrations are available. Background or proactive access to email is disabled by default and occurs only after the user separately enables the applicable feature.
5.2 How integration data is used
We use Google API Data only to deliver or improve the user-facing feature for which the user authorized access. This may include showing a user a relevant email, creating a draft, sending a confirmed message, checking availability, creating or changing an event, selecting a guest for an invitation, or generating a context-specific answer or summary through an authorized interface.
Use is limited to the permissions granted and is not expanded for unrelated profiling, marketing, general data enrichment, or development of generalized AI models.
5.3 Transfers to service providers and user-selected channels
To deliver the Google integration features users authorize, we disclose only the information needed to service providers and communication channels necessary for those features, subject to applicable consent, contractual safeguards, and Google's Limited Use requirements:
- Google Cloud / Vertex AI: to process minimized, relevant Google content for user-requested inference, summaries, and other authorized features, including through Gemini and Anthropic Claude models offered through Vertex AI, subject to applicable service and data-use terms.
- Composio Cloud: to facilitate Google Calendar OAuth authorization, custody of Calendar connection credentials, connected account management, Calendar API execution, and delivery of event-related webhooks or notifications. Composio Cloud may process connected account identifiers, calendar titles, event details and descriptions, attendee email addresses, requests and results, and event or RSVP data in order to perform those functions. This is a cloud-hosted service, not a self-hosted Key data plane. Key's native Gmail integration does not route Gmail messages or credentials through Composio.
- Meta WhatsApp Cloud API: when a user chooses WhatsApp as an authorized interaction channel, to deliver the requested response or notification. A response may contain a summary or other information derived from the user's authorized Gmail or Calendar data. We transmit the composed response, not a wholesale copy of the user's mailbox or calendar.
- Recall.ai: where a user enables meeting-assistance features, to process meeting media or related information necessary to provide those features, subject to separate notices and controls.
- Security and infrastructure providers: for hosting, secure operations, monitoring, and incident response. Our application logging and tracing controls exclude Gmail message bodies, Calendar event descriptions, OAuth credentials, and private AI prompt and response content from operational telemetry.
We do not transfer Google API Data to advertising networks, data brokers, information resellers, or other third parties for their independent commercial purposes. Disclosures are limited to those permitted by Google's applicable policies and by the user's authorization or other recognized legal basis.
5.4 Google API Services User Data Policy — Limited Use
Key.ai's use and transfer of information received from Google Workspace APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements, and the Google Workspace user data and developer policies. This commitment applies to raw, aggregated, anonymized, and derived Google API Data.
For Google API Data, including data derived from sensitive and restricted scopes, Key commits that:
- We use the information solely to provide or improve the authorized user-facing functionality for which access was requested.
- We do not sell the information, provide it to data brokers or information resellers, use it for advertising, retargeting, lending, or creditworthiness decisions, or use it for unrelated profiling.
- We do not use the information to create, train, or improve generalized or non-personalized AI or machine-learning models, and we require equivalent restrictions of providers acting on our behalf. Any permitted AI processing supports the particular user's authorized feature.
- We transfer the information only to provide or improve authorized user-facing features with the user's consent, for permitted security purposes, to meet applicable legal requirements, or in other circumstances expressly allowed by Google's policies, including any required prior consent for a corporate transaction.
- We do not allow employees, contractors, or other persons to read Google API Data except with the user's documented affirmative permission for specific information, for permitted security or legal purposes, or where the information is appropriately aggregated and anonymized for permitted internal operations.
- We apply these protections to summaries, generated responses, metadata, and other identifiable or derived information obtained from Google APIs, not only to original API responses.
These restrictions override any broader rights or permissions granted elsewhere in this Privacy Policy or our Terms of Use, including provisions relating to analytics, advertising, product development, sublicensing, AI, and derived data.
5.5 Google data storage, retention, and deletion
We process Gmail message content on demand for the requested function rather than maintaining permanent copies of email bodies. Transient Calendar and Gmail results are limited to the request or the separately authorized user feature. Gmail authorization credentials are handled by Key's native services; Calendar connection credentials are managed through Composio Cloud. We apply, and require relevant providers to apply, protective storage and access controls appropriate to their roles. Temporary caches, event messages, and operational records expire under defined retention schedules. Google-derived conversation context is private to the relevant request and is not incorporated into general long-term AI memory. Persistent user-specific context is maintained only for separately enabled features and remains subject to the deletion controls below.
Users can disconnect integrations through Key's connected-account controls or revoke Key's access in their Google Account. When an integration is disconnected, we stop synchronization, revoke or delete relevant authorization credentials, remove applicable subscriptions and triggers, and delete associated Google-origin content and identifiable derived records from active systems, except where narrowly permitted retention is necessary for security or legal compliance. These processes include Gmail-related drafts, tracking, and derived context; and Calendar-related activity, RSVP tracking, and Calendar-only derived records. Users may also request deletion of Google-derived information under Key's control.
Messages delivered through WhatsApp may also exist in Key's conversation history, which is otherwise retained for up to 90 days. If such history contains identifiable Google-derived content, our deletion processes remove that content from Key-controlled active history upon the relevant disconnection or deletion request. Copies already delivered to WhatsApp recipients or held by Meta are governed by the recipients' actions and Meta's separate practices; Key cannot remove every copy outside its control.
Residual copies in protected backups expire under a defined backup lifecycle and are not used for active product features. Our restoration and deletion procedures prevent deleted Google-derived records from being reintroduced into active use. Any narrowly necessary exceptional retention is limited to what applicable law and Google policies permit.
5.6 User controls and additional consent
Users choose whether to connect Gmail, Calendar, or Contacts and can revoke that authorization. Separate authorizations are provided for Calendar read and manage capabilities, and user opt-in controls govern proactive email access and other optional functions. In-product notices explain when information from an authorized Google connector may be processed by an AI service or delivered through a user-selected channel such as WhatsApp. Each requested external write is subject to explicit user confirmation.
If we introduce a materially different use of Google API Data, we will first update our disclosures and obtain any additional consent required by Google's policies or applicable law. We will not request Google scopes solely for unimplemented features.
6. Legal Bases for Processing
Where legally required, we process information on an appropriate basis, including performance of a contract, legitimate interests in providing and protecting our services, compliance with legal obligations, and consent where required. Connecting a Google integration involves the user's separate authorization and, where applicable, consent to specified processing or transfers. Revoking authorization may prevent the connected feature from operating but does not require the user to stop using unrelated Platform features.
7. Disclosure of Information
Outside the specific Google API limitations in Section 5, we may disclose information to hosting and infrastructure providers, security and support vendors, AI providers, professional advisers, regulators and law-enforcement bodies as lawfully required, counterparties to a corporate transaction, and other users or the public when the user affirmatively publishes or shares information.
We do not sell personal data for monetary consideration. Any information received from Google APIs is governed by Section 5 regardless of whether a general disclosure category in this section would otherwise apply. A sale, merger, acquisition, or asset transfer does not independently authorize the transfer of Google API Data without satisfying the applicable Google policy requirements and necessary prior user consent.
8. Public Content and Public Profiles
Content that a user deliberately publishes through a public profile or community feature may be indexed, copied, cached, or redistributed by third parties outside our control. Unpublishing content may not remove independent copies.
Google API Data is not made public by default. We do not treat a user's Gmail or private Calendar content as public profile material or use it to populate a public directory absent a separately authorized, user-directed sharing action consistent with Google's policies.
9. Retention of Information
For information not subject to the special Google restrictions, we generally retain account data during the account's lifetime and, where appropriate, for up to 24 months after account deletion, subject to legally necessary retention, security, dispute resolution, and deletion rights. Other data may be retained for the documented period necessary for its purpose. We may retain appropriately de-identified, aggregated information to the extent permitted by applicable law.
Google API Data is subject instead to Section 5.5. The ordinary 24-month post-deletion period, broad derived-data provisions, and any permission to retain anonymized information indefinitely do not automatically apply to data from Google APIs. Such data and its derivatives are kept only for permitted user-facing purposes or narrowly permitted exceptions, with disconnection, deletion, and backup-expiry controls.
For messages sent through Key's WhatsApp interface, Key-controlled conversation history may otherwise be retained for up to 90 days; Google-derived portions are subject to the stronger Section 5 deletion requirements. Retention practices of Meta or other independent communication services are governed by their own policies.
10. International Data Transfers
Key is based in the United States and primarily processes information there, but service providers and infrastructure may process information in other jurisdictions, including where global cloud model endpoints or messaging providers operate. Where required, we use recognized contractual or other legal transfer safeguards. We do not promise that every AI inference or external integration is confined to a particular geographic region unless expressly confirmed for that feature.
Transfers of Google API Data must additionally satisfy Section 5 and applicable Google policy restrictions, regardless of location.
11. Security
We use technical and organizational measures designed to protect personal data, including encryption and access controls for integration credentials, managed cryptographic keys where applicable, service authentication, user-specific authorization checks, and operational monitoring. Key manages native Gmail credentials and Composio Cloud manages Calendar connection credentials under their respective operational controls; token access is limited to authorized workflows. We redact sensitive fields from logs and traces and exclude protected message and prompt contents from operational telemetry. We maintain procedures for credential revocation, security response, retention, and deletion.
No technical system can be guaranteed completely secure. Where a breach triggers notification obligations, we will notify affected persons or authorities as legally required. This security statement does not limit our obligations under Google's security and restricted-scope requirements.
12. Your Rights and Choices
Subject to applicable law, users may have rights to access, correct, delete, export, restrict, or object to processing of personal data. Requests may be sent to support@key.ai; we may verify identity before acting.
Users may manage or disconnect Google integrations through the Platform or revoke access directly through their Google Account security settings. A disconnection stops future authorized retrieval and initiates applicable deletion controls for information held by Key. Users may separately request deletion of stored information, including Google-derived information under our control. Information that has been independently delivered to another recipient or retained by a third-party communication service may remain subject to that recipient's or service's controls.
California residents: Subject to the California Consumer Privacy Act and related law, eligible individuals may have rights to know, delete, correct, and opt out of certain uses of personal data, and not to be discriminated against for exercising applicable rights.
Singapore residents: Eligible individuals may exercise rights under the Personal Data Protection Act 2012 (Singapore), including applicable access, correction, and withdrawal of consent rights. Our designated Data Protection Officer may be contacted at chris@key.ai with the subject “PDPA — Data Protection.”
13. Children's Privacy
The Platform is not directed to persons under 18 years of age. We do not knowingly collect personal data directly from children under 18. If we learn that we have done so contrary to applicable law, we will take appropriate steps to delete or otherwise lawfully handle that information.
14. Changes to this Privacy Policy
We may update this Privacy Policy as our services and legal requirements evolve. Material changes will be communicated in the manner required by law. If we intend to use Google API Data for a materially different purpose, we will update relevant notices and obtain any new authorization or consent required before that use begins.
The effective date appears at the top of this Privacy Policy.
15. Contact
For questions about this Privacy Policy, our data practices, or a privacy rights request, contact support@key.ai.
Blueprint X Labs Inc. — Key.ai