Privacy Policy

Last updated November 4, 2026.

Laplace Systems Inc ("Laplace", "we", "us") provides connections and tools that let you use your applications and accounts from compatible AI assistants and other clients. This Privacy Policy explains how we process information when you use our website, connections, and related services. It also covers application-building and commerce features where those features are available to your account.

Information we process

  • Account and organization information: your name, email, profile information, sign-in and session records, organization membership, roles, and account settings.
  • Connection information: the service and account you connect, account identifiers and display names, granted permissions, connection status, and credentials needed to maintain the connection. Depending on the provider, credentials include OAuth access and refresh tokens, API keys, or other secrets you supply.
  • Requests and connected-service data: the requested tool or action, its parameters, and information returned by the connected service. Depending on the connection and request, this may include documents, messages, calendar events, analytics, business records, or other information you authorize us to access.
  • Operational information: tool-call counts, timestamps, execution identifiers, success and error status, security records, and bounded summaries of action inputs and results. These summaries can contain connected-service information; action history is not limited to anonymous usage counts.
  • Other information you provide: support messages, contact inquiries, billing and subscription identifiers, and, when you use the relevant features, application prompts, source code, files, shared records, saved secrets, and browser-session information. Commerce workflows may process products, listings, orders, fulfillment details, inventory, and synchronization records.

We receive information from you, the clients and services you authorize, and service providers that help us operate Laplace.

How we use information

We use information to authenticate users, maintain connections, execute authorized requests, return results, enforce account and organization permissions, operate subscriptions and usage limits, provide support, diagnose failures, prevent abuse, and meet applicable legal obligations. Synchronization and workflow features use the connected-service information needed for those features.

We do not sell personal information. We do not use Google API data for advertising or to develop, improve, or train generalized artificial intelligence or machine-learning models.

Connected accounts and AI assistants

You choose which supported services to connect. The provider's authorization screen describes the permissions requested. Those permissions determine what the connection can access; an individual action may use only part of the access you granted. Some connectors support changes to data as well as reading it.

When you authorize a client, including an AI assistant using the Model Context Protocol (MCP), Laplace makes the permitted connections and tools available to that client. When the client requests an action, Laplace sends the necessary parameters to the connected service and returns the result to the requesting client. Results may include personal or confidential information. Organization membership, the client's authorization, and connection permissions determine the available access.

The assistant or client you choose processes results under its own privacy policy and settings. Review those settings, including retention and model-training controls, before authorizing it. A response can remain in the client's conversation history or other storage after you disconnect that client from Laplace.

Where you use Laplace's application-building or other AI features, prompts, relevant files, and workflow context may be sent to the model providers used by that feature to generate the requested output.

Google and YouTube data

Laplace uses Google OAuth and YouTube API Services for its separate YouTube and YouTube Analytics connections. Google sign-in information, including an account identifier, email address, and profile information, lets us identify and display the connected account. OAuth tokens let us make authorized requests and refresh access without asking you to sign in for each request.

The YouTube connector accesses channel, video, playlist, playlist-item, comment, rating, and caption information. Depending on the action you request and permissions you grant, it can upload, update, or delete videos; create, update, or delete playlists and playlist items; post comments and replies; change ratings and thumbnails; and retrieve or manage caption tracks. These requests may include video or caption files, media source URLs, titles, descriptions, tags, language settings, and content visibility choices. Content you instruct Laplace to publish is sent to YouTube with the requested settings. Private account resources require authorization, and some caption operations require permission to edit the video.

The separate YouTube Analytics connector requests read-only access to YouTube account information, non-monetary analytics, and monetary analytics. YouTube account read access is required by Google's reports endpoint. Laplace uses this access to retrieve reports for the channel or content owner you are authorized to use, for the requested dates, metrics, and dimensions. Reports may include views, watch time, video performance, and estimated revenue. This connector does not upload, modify, or delete videos.

Results from both connectors are returned to the requesting user or authorized client. Laplace may also retain YouTube information in action-history summaries and temporary execution records, as described below. Upload and caption workflows can temporarily process media or caption files to complete a requested transfer; copies returned to a client are governed by that client's controls as well.

Laplace's use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including its Limited Use requirements. We use Google data for the user-facing features you authorize. We do not sell it, use it for advertising, or use it for generalized model training. Personnel may access Google data only as permitted by that policy, such as with your affirmative permission, to investigate security issues, or to meet legal requirements.

See the Google Privacy Policy for Google's practices. You can revoke Laplace's Google access through your Google Account permissions. YouTube use is also subject to the YouTube Terms of Service.

Sharing and service providers

We share information with the connected services and clients needed to carry out your authorized requests, and with members or administrators who have access under your organization's permissions.

We use service providers for hosting, databases, storage, authentication, payments, email, monitoring, and, where applicable, AI processing and managed connections. They process information needed to provide those services. Connecting a custom service or MCP server can send requests and data to its operator.

We may disclose information when required by law or when necessary to investigate abuse, protect the service, or protect users' rights and safety. Any transfer of Google API data remains subject to the Google API Services User Data Policy and its Limited Use restrictions.

Information may be processed in countries other than where you live, depending on the infrastructure, connected services, and clients involved in your use of Laplace.

Storage, security, and retention

We use access controls, encrypted credential storage, and secure transport to protect information. Our gateway applies redaction and size limits to action-history summaries. No security measure guarantees that every sensitive value will be recognized or that every system is risk-free.

Connection credentials are retained to provide the connection until it is removed or no longer needed. Disconnecting a gateway connection removes its stored credential and prevents subsequent requests through that connection. It does not undo completed actions, delete data at the original provider, or automatically erase previously returned results and action history.

We retain account, connection, usage, support, and operational records for the purposes described in this policy. Retention varies by record and feature: gateway action history is bounded by a configured record limit, while temporary retry records have an expiry. A record limit is not a fixed deletion deadline. Copies already stored by a connected service, client, or organization are governed by that recipient's controls and policies.

You can request deletion of information retained by Laplace using the contact details below. We may need to verify your identity and the account or organization involved. We delete retained YouTube data as soon as possible and within seven calendar days of a deletion request. This request process is separate from disconnecting a connection. Where applicable law requires retaining particular billing, security, or legal records, we retain those records for that purpose.

Cookies and device information

We use cookies and similar storage for sign-in sessions, security, preferences, and remembering cookie choices. Our website provides cookie controls, including an essential-only choice. You can also manage cookies through your browser; disabling necessary cookies may prevent sign-in or other features from working.

Marketing inquiries and previous waitlist submissions

When you submit an inquiry, we store your name, email, company if supplied, inquiry topic, message, source page, and submission time. Authorized staff use these records for manual follow-up.

If you previously joined the Laplace Connect waitlist, we retain your email, optional name, company and tools of interest, source page, submission time, and the time and version of your launch-notification consent. A waitlist submission did not create a product account or connect third-party services. Duplicate submissions did not replace existing details.

These forms do not send automatic receipts or campaigns. Staff can export records for follow-up and availability notifications covered by your consent. Withdrawn waitlist entries are excluded from notification exports. You can request withdrawal, access, correction, or deletion through our contact page. We retain these records to handle your inquiry or previous waitlist participation, subject to deletion requests and applicable obligations.

Your choices and requests

You can manage account details, connected accounts, and authorized clients through Laplace's available settings. Organization administrators can manage membership and access. You can also revoke a provider's authorization using that provider's account settings.

For access, correction, export, or deletion requests, contact arthur@withlaplace.com or use our contact page. For a YouTube data-deletion request, identify the connected channel or account and say that you want the YouTube data retained by Laplace deleted. Deleting Laplace's copy does not delete the original information held by YouTube.

Depending on your location and circumstances, applicable law may provide additional rights over your personal information. We handle requests in accordance with applicable requirements.

Changes and contact

We will post changes to this policy on this page and update the date above. If we introduce a new use of Google data that requires additional consent, we will request that consent before using the data for that purpose.

For questions or complaints about Laplace Systems Inc's privacy practices, contact arthur@withlaplace.com or use our contact page.