SourceLace
Legal

Privacy Policy

Effective 18 November 2026

This policy explains what information SourceLace collects, why, where it is kept and for how long. SourceLace is operated by SourceLace, Inc., a Delaware corporation, 1734 Holmes Dr., Sewickley, PA 15143, USA ("SourceLace", "we", "us"). It covers the website sourcelace.com, the SourceLace app at sourcelace.ai, and the SourceLace MCP connector that people add to AI apps such as Claude or ChatGPT (together, the "Service").

The short version

Who this applies to

Most people use SourceLace through their employer or another organization that has an account (a "Customer"). For data that flows through the Service from a Customer's business systems, the Customer decides what is connected and who may use it, and we process that data on the Customer's behalf and on its instructions. Questions about that data should go to the Customer's administrator first. For our own website and for account and billing records, we decide how the information is used.

What we collect

How we use it

We do not sell personal information, do not use it for advertising, and do not use your data or your systems' data to train AI models.

AI processing

In this policy, "the AI provider" means the provider that writes the answers for your organization: Anthropic, through SourceLace's own account by default, or the provider whose API key or cloud account your organization's admin connected, as described below.

If you use SourceLace from your own AI app (for example Claude or ChatGPT), SourceLace returns results to that app and sends nothing to an AI model itself; your app's own provider and terms apply. The assistant inside the SourceLace app sends your question, the chat so far and the relevant results to Anthropic, which provides the AI model that writes the answer: either through SourceLace's own Anthropic account, or through your organization's own Anthropic API key if your admin entered one, in which case your organization's agreement with Anthropic applies. Under Anthropic's commercial terms, Anthropic does not train its models on data sent through its API. If your admin chooses your organization's own OpenAI API key instead, the same content goes to OpenAI under your organization's agreement with OpenAI, and SourceLace asks OpenAI not to store it for later retrieval (OpenAI's own policies may still keep it for a limited time, for example for abuse monitoring). If your admin chooses your organization's own Google Gemini or Mistral API key, the same content goes to that provider under your organization's agreement with it, and that provider's own terms decide how long it is kept. If your admin connects your organization's own Azure OpenAI resource or Amazon Bedrock account instead, the same content goes to that service in your organization's own Azure resource or AWS account and region, under your organization's agreement with Microsoft or Amazon Web Services.

To answer faster and at lower cost, the AI provider may keep a processed copy of the conversation in its memory for a short time and then delete it. For example, with Anthropic today this is about 5 minutes after your last question, and up to an hour for the fixed instructions that start every chat (SourceLace's and your organization's), and Anthropic states that these caches are never shared between organizations. Other AI providers cache under their own terms, and we update the list of providers on this page before adding one that handles your data.

AI agents work the same way without a person typing: on their schedule, or when something happens in a connected system, SourceLace sends the agent's instructions and the data it reads to the same AI provider, acting as the agent's owner.

Your organization's admins can set data protection rules that hide chosen fields from the AI and replace values such as email addresses, phone numbers and card numbers with placeholders before anything is sent to an AI model, whether from your own AI app, the SourceLace app or an AI agent. What each placeholder stands for is held like a query result, for at most your organization's result time limit, and is never written to the audit trail.

When your organization uses Agent Architect, SourceLace reads the structure of the data sources you choose, works out summary figures, and, if your administrator allows it, reads a small sample of rows, and sends these to your organization's AI provider so it can write agent proposals. If a person shares examples of their work, or adds files to an agent as references, by linking them or uploading them, SourceLace reads those files (linked files with that person's own access) and sends their text and layout to your organization's AI provider, when Agent Architect designs agents and each time such an agent runs. Anything your organization's data protection rules, or any extra masking rules your administrator sets for Agent Architect, mask is replaced by a placeholder before anything is sent, and the AI provider never receives the original value. Pictures cannot be masked: if your administrator allows pictures, a picture a person shares is sent to your organization's AI provider as it is. Data protection covers what your organization has set up, so your administrator should review those rules before allowing sample rows or shared files. Samples, summary figures and the text read from shared files are held briefly and then deleted, and saved proposals contain no sample values. A linked file is kept only as a link with its name and outline. An uploaded file is kept, encrypted with a key unique to your organization, until the person removes it or the agent or conversation it belongs to is deleted.

If your organization runs some AI agents on a SourceLace Runner inside its own network, those agents' AI calls use your organization's own AI key from that network, and their summaries, drafts and changes waiting for approval stay on the runner. SourceLace receives only each run's status, times, the tools and systems used and counts.

If you use voice input in the app, your browser turns your speech into text with its own speech service (in Chrome and Edge that is Google's or Microsoft's; Safari uses Apple's or the device). SourceLace receives only the text.

Data from Google

If you sign in with Google, SourceLace asks only for your name and email address. If you connect Google sources, SourceLace requests only the access each source needs: reading mail and creating drafts in Gmail (it never sends email), reading Google Calendar and, only where your organization's admin turns it on and only after you confirm each one, making, changing and cancelling events you organize, reading Google Drive files (and, only where your organization's admin lets agents save the files they make, adding new files to the folder they name), reading and changing the Google Sheets you name, and running read-only BigQuery queries. SourceLace's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. In particular:

Google data is handled like any other source data: held for up to 30 minutes, and kept longer only inside chats in the SourceLace app and AI agents' run summaries and pending changes, as described above. You can remove SourceLace's access at any time by disconnecting the source in SourceLace, or from your Google Account's third-party connections.

Data from Slack

If you connect Slack, you sign in with your own Slack account and SourceLace acts as you. There is no SourceLace bot in your workspace and no shared account, so SourceLace sees only what you can see in Slack. It asks Slack only for the access it uses: listing the channels, direct messages and group messages you are in; reading their messages, threads and the files shared in them; searching messages; and looking up people's names and email addresses so answers show names and can tell who is outside your organization. Where your organization's admin allows it, SourceLace can also act for you: posting messages, replies and reactions, creating channels and canvases, and uploading files, such as a report an AI agent made. In a chat you confirm a preview before anything is posted; an AI agent posts only where it was set up to deliver.

Slack data is handled like any other source data: held for up to 30 minutes, and kept longer only inside chats in the SourceLace app and AI agents' run summaries and pending changes, as described above. Your Slack sign-in token is encrypted with a key unique to your organization and never shown back. You can remove SourceLace's access at any time by disconnecting Slack in SourceLace, and a Slack workspace admin can remove the SourceLace app from the workspace.

Where it is stored and who helps us

The Service is hosted in the United States. We use these service providers, each bound by contract to protect the data and use it only to serve us:

The business systems you connect, and the AI app you use SourceLace from, are chosen by you or your organization and are governed by your own agreements with them. We will update this list before adding a provider that handles Customer data.

How long we keep it

Security

Data is encrypted in transit (HTTPS) and at rest. Connection tokens and logins, chats, generated files, projects, skills, AI agents' run summaries and pending changes, saved answers, and organizations' own AI keys are additionally encrypted with a key unique to each organization, which SourceLace manages. Every request is recorded in a hash-chained audit trail, so a changed or deleted entry shows. Where you sign in to a system with your own account, you see only what your permissions there allow; for shared-access sources an admin adds, admins can limit who may use them. No system is perfectly secure; if a breach affects your information, we will notify you and your organization as the law requires. SourceLace does not hold any security certification such as SOC 2 or ISO 27001.

Your choices and rights

You can disconnect any system, delete your chats, and ask us for a copy of your personal information, to correct it, or to delete it. Depending on where you live (for example the EU, UK or California), you may have further rights, including to object to or restrict processing and to complain to your data protection authority. If your account belongs to a Customer, we may refer your request to that Customer. Email privacy@sourcelace.com; we answer within 30 days.

If you are in the EU or UK, we rely on contract (to provide the Service), legitimate interests (security and improving the Service) and legal obligation. Where information moves outside your country, we use safeguards such as the European Commission's standard contractual clauses.

Children

The Service is for businesses and is not directed to anyone under 16. We do not knowingly collect their information.

Changes

We will post changes here with a new effective date, and tell account holders by email before a material change takes effect.

Contact

SourceLace, Inc., 1734 Holmes Dr., Sewickley, PA 15143, USA. Email privacy@sourcelace.com. Security reports: security@sourcelace.com.