Latently
Sign inStart now

Security and access

How Latently keeps context scoped: explicit source selection, project boundaries, separate OAuth systems, and read-only MCP access.

Source selection

  • -

    Latently processes the sources you select, connect, or upload for a project.

  • -

    Connecting an account does not mean Latently indexes the entire account by default.

  • -

    Removing a source removes it from active Latently context without deleting the original provider object.

  • -

    You are responsible for choosing source material you are allowed to use with Latently.

Project boundaries

Customer-visible context is organized by project. When an AI client asks Latently for context, it should resolve the relevant project before reading the sources attached to that project.

MCP access

  • -

    Latently MCP tools are read-only in V0.1.

  • -

    Google Drive OAuth and MCP OAuth are separate connection flows.

  • -

    An AI client can receive project context from Latently after you authorize that client.

  • -

    After an AI client receives context, that client is governed by its own terms, privacy policy, and data handling behavior.

Data use

Latently stores the project and source context needed to provide the service. Latently does not use customer project content to train AI models.

For broader policy details, read the Privacy Policy and Terms of Service.