SourceLace Docs
FAQOpen the app

Security questions

Direct answers to the questions in vendor security reviews and questionnaires (such as SIG Lite or CAIQ), grouped the way those questionnaires are. Each answer describes what SourceLace does today; where something is not in place yet, it says so. The full detail is on Security and privacy. For anything not answered here, or to arrange a review call, email security@sourcelace.com. Shorter answers, by topic, are in the frequently asked questions.

Organization and certifications

Does SourceLace hold SOC 2, ISO 27001 or any other certification?

No. SourceLace does not yet hold any security certification or attestation: no SOC 2 report, no ISO 27001 certificate, and no HIPAA attestation. Please do not record SourceLace as holding one in your vendor register.

Is SourceLace working towards SOC 2?

Yes. SOC 2 is an independent audit of a company's controls against the AICPA's Trust Services Criteria. SourceLace has engaged an independent CPA firm for a SOC 2 Type 2 examination covering Security and Privacy. The observation period began on 1 November 2026, and we expect the report in 2027. SourceLace does not hold a SOC 2 report yet. The report date is not fixed, so there is no date to put in your vendor register. Many of the controls such an audit checks are already in place and are described on this page: single sign-on, access by group, encryption, the tamper-evident audit trail, logging and threat detection in the hosting environment, reviewed and tested changes, backups and a written incident response process. What is not in place yet is listed in the next answer.

Do you have written security policies, staff background checks or security training?

Partly. These are written down and approved by SourceLace's owner, each reviewed yearly: information security (including how information is classified), access control, change management and secure development, risk management, business continuity and recovery, incident response, requests about people's own data, security and privacy training, and vendor management (for incident response, see Incident response and breach notification). Not yet in place: staff background checks and a penetration test by an outside firm. Ask security@sourcelace.com for company details a questionnaire needs, such as the contracting entity and address.

What can we request for a security review?

Email security@sourcelace.com for any of these:

  • This page and Security and privacy: the answers most questionnaires need, including what is not in place yet. The short version is on the security page of our website.
  • The subprocessor list: who handles your data and what each receives, in Hosting and subprocessors and in our privacy policy.
  • How incidents are handled and reported to you: the summary in Incident response and breach notification.
  • Your own security questionnaire, filled in by SourceLace, or a review call.
  • The security review pack: more technical detail on encryption, key handling and hosting, shared under a non-disclosure agreement (NDA).
  • Your own evidence: your admins can export your organization's audit trail with its proof at any time (see Can we see and export it?). The hosting provider's own independent audit reports are available from that provider.

There is no SOC 2 report, ISO 27001 certificate or penetration test report to request yet.

Hosting and data location

Where does SourceLace run, and where is our data?

SourceLace's cloud is hosted in the United States, with a major cloud provider named in our privacy policy: the application, its database, the short-term store for query results and the backups. Backup copies are kept in a second US region. Data is hosted in the United States only today; there is no EU or other regional hosting yet.

How is the hosting environment protected?

  • Private network. SourceLace's servers and database run in a private network. The database and the short-term store cannot be reached from the internet at all; only SourceLace's own entrance can be.
  • A web application firewall in front of SourceLace blocks common attacks and known bad addresses, and limits how many requests one address can send.
  • HTTPS only, with TLS 1.2 or later; plain HTTP is redirected.
  • Threat detection and configuration checks run continuously, and serious findings alert SourceLace's staff within minutes.
  • Every administrative action in the hosting environment is recorded, and those records, with the firewall and network logs, are kept for at least a year.
  • Fixed outbound addresses. SourceLace calls your systems from addresses that do not change, so your firewall can allow just those (see What your network needs).

Will the hosting provider change?

It may. If it does, this page will change, and the subprocessor list on Security and privacy will be updated before any new provider handles your data.

Can we keep our data in our own network?

SourceLace is offered only as a cloud service. On the Enterprise plan, a SourceLace Runner can run chosen AI agents inside your own network: people keep using SourceLace's cloud, and those agents use your own AI key and keep their results in your network. Runners are offered on request, with an annual runner fee on top of your subscription, a one-time onboarding fee (installation help and a security review), Premium support and a minimum contract term of one year. See SourceLace Runner below and Runners.

Is customer data separated between organizations?

Yes. Everything SourceLace keeps for your organization is tied to it, every request is checked against the signed-in person's organization, and each organization's secrets, chats and agent data are encrypted with that organization's own key (see Encryption at rest). An email address belongs to one organization only.

Events from connected systems

Does SourceLace keep the events it receives from Salesforce?

No. An event that starts an agent reaches that run as data about what happened, and is kept only with the run, encrypted with your organization's key, until the run's normal deletion. SourceLace keeps no copy of the events themselves. The audit trail records what happened to each event (the runs it started, or that it was filtered out or was a duplicate), with ids and counts only and never the event's content. An agent's connection to Salesforce events uses the owner's own sign-in, and stops if that sign-in expires. See Start when Salesforce sends an event.

What is read from our message queues, and what is kept?

Only the queues you connect for an agent, and only while an agent listens to them. The message body must be JSON, or a CloudEvent, and it reaches the run as data about what happened, never as instructions. It is kept only with that run, encrypted with your organization's key, until the run's normal deletion. SourceLace keeps no copy of messages. A message is removed from your queue only after its runs have started, so a message that is not delivered stays in your queue. The audit trail records what happened to each message (the runs it started, or that it was filtered out, refused or a duplicate), with ids and counts only and never the message's content. The keys for a queue are encrypted with your organization's key, never shown again, and never written to the audit trail or a log. Queues are read with your organization's own keys, or, for Amazon SQS, with a role in your AWS account that SourceLace assumes with your organization's external ID, so no keys leave your account; never with any person's sign-in. Queues inside your network (IBM MQ) are read by the on-site SourceLace Agent, through its outbound connection: only the queues its own configuration lists, with a password that never leaves your network. See Start agents from your message queues.

What does an agent that starts from new Gmail emails read?

Only the mailbox of the agent's owner, with their own Google sign-in, never anyone else's. Gmail tells SourceLace that the mailbox changed (naming only the address and a change number); SourceLace then reads the new emails in the label the owner chose. Each run gets the email's sender, recipients, subject, date, Gmail's short preview and labels, as data, never as instructions; not the full text or attachments, unless the agent opens the email through the source as its owner. SourceLace keeps no copy of emails, only the run's context, encrypted with your organization's key until the run's normal deletion. To know whose mailbox Gmail's notice is about, SourceLace keeps a one-way hash of the address, never the address itself, and deletes it once no agent watches the mailbox any more (at Gmail's next notice about it), or with your organization. See Start when an email arrives in Gmail.

Encryption

Encryption in transit

SourceLace is served over HTTPS only, with TLS 1.2 or later, and browsers are told to use HTTPS every time. Inside the hosting environment, the database and the short-term store accept only encrypted connections. Connections from SourceLace to your systems use TLS with certificate checks; for databases SourceLace also checks the certificate was issued for the host name your admin entered, and TLS cannot be turned off for a database other than one on the same computer as SourceLace. A runner connects to SourceLace over HTTPS only.

Encryption at rest

Each organization has its own key. These are encrypted with it:

  • each person's sign-ins to your systems (access and refresh tokens, database passwords);
  • your admins' secrets (single sign-on, app registrations, custom connector secrets, Amazon S3 keys) and your own AI key;
  • saved chats and the files made in them, and skills;
  • AI agents' settings, run summaries, triggers, changes waiting for approval, and the progress of runs not yet finished;
  • query results, while they are held in the short-term store.

Other records, such as the names and roles of your people, your source settings, usage and activity counts (counts only, never your data) and the audit trail (which holds metadata only), are kept in SourceLace's database without your organization's key. Everything SourceLace stores, including these records, the file storage and the backups, is also encrypted at rest by the hosting environment, with keys SourceLace controls and that are replaced every year.

Tokens SourceLace issues (to AI apps, runners and on-premise agents) and one-time sign-in codes are stored only as SHA-256 hashes, so a copy of the database cannot be used to sign in.

Who holds the keys?

See Keys: who brings each one, and where it is kept. In short: your organization's key is never stored in readable form, and the key that protects it is never kept in the database. The technical detail (algorithms and how keys are kept) is in the security review pack, which your admin can request from security@sourcelace.com.

Can keys be rotated? Can we bring our own key?

SourceLace's own keys can be rotated without downtime. Rotating an individual organization's key is not yet available. On SourceLace's cloud, a customer-managed key (BYOK or a key in your own key service) is not yet available. You do bring and control your own AI key, if you choose to use one.

Identity and access

How do our people sign in to SourceLace?

With Google, Microsoft, or your own single sign-on: OpenID Connect (Business and Enterprise) or SAML 2.0 (Enterprise), with providers such as Okta and Microsoft Entra ID. SourceLace has no passwords of its own and never sees your people's passwords. You can require single sign-on for your email domains. See Single sign-on.

Do you support MFA?

Through your identity provider. Because SourceLace has no passwords of its own, multi-factor authentication is whatever your Google, Microsoft or single sign-on setup requires. SourceLace has no MFA of its own.

Who can get in?

Only people your admins invite, or people who sign in with a verified address at one of your organization's allowed email domains (public domains such as gmail.com are refused). Removing someone on the People page ends their sign-in and their AI app connections, and deletes their sign-ins to every source. Removing an email domain does the same for everyone who joined through it. See People and sign-in.

What roles are there?

Admin and member. Admins manage people, sources, groups, single sign-on, settings and the audit trail; members use the sources they may use. Every organization always keeps at least one admin. See Roles.

Can access be limited to some people? Do you sync groups?

Yes, on Business and Enterprise. Admins can limit each source to named groups, and with single sign-on, groups are kept in step with your identity provider at each sign-in. Read rules narrow it further, per group and object: which rows a group sees (such as only its own region) and the most rows one answer may return, on every way of asking, with each answer's audit entry naming the rules that applied. See Access by group, Read rules and Group sync.

Does SourceLace use a shared service account to reach our systems?

Not for most systems. Each person connects them with their own login, so the system's own permissions apply to every call and people only see and change what they already could. Some sources use one shared account an admin sets up: Amazon S3, lake tables, Amazon Athena, Gong, Gainsight, ChurnZero, custom connectors, SAP's demo sandboxes for S/4HANA and SuccessFactors, and, if the admin chooses it, Amazon Redshift, REST or SOAP sources, and outside MCP servers. Each source is labelled "Personal sign-in" or "Shared account" in the app and for AI apps; see Personal sign-in and shared accounts.

How long do sessions and tokens last?

What Default Notes
A session in the SourceLace app 7 days
An AI app's access token (MCP, standard OAuth with PKCE) 1 hour Bound to SourceLace's MCP address, so it works nowhere else.
An AI app's refresh token 30 days Replaced each time it is used; an AI app not used for 30 days signs in again. Revoking either token ends both.
A sign-in on a runner's page 12 hours

Admins can make the first three shorter on the Limits page. A removed person is refused at their next request, without waiting for a token to expire.

Can SourceLace change records in our systems?

Only where an admin has turned changes on for named objects of a source. Every change is previewed and sent only after the person confirms it, and previews expire within 10 minutes. Queries are checked to be read-only before they are sent. SourceLace never sends email: mail sources only make drafts. See Reads, changes and query checks.

Who can approve changes, and can we separate duties?

Changes an AI agent proposes wait for approval by the agent's owner or an admin, unless an admin allowed that kind of change without approval. Your admins can add approval rules per system and object: only changes above an amount wait, the approver must be in a named group, and the person who asked (the agent's owner, or whoever started the run) may not approve their own change. Admins can also fix field values that the AI cannot choose, such as Status = Draft. SourceLace checks these rules again at the moment a change is approved or made, not only when it is shown. Approving several changes at once still checks and records each one on its own. Every approval, refusal and change to these rules is in the audit trail. See Approval rules and fixed values.

Can other systems start our AI agents? How are their calls checked?

Only systems your agent owners connect, each to one agent's start address. Each call must carry the address's secret (SourceLace keeps only its SHA-256 hash), or the signature or signed token of the system chosen under Who calls it (GitHub, Slack, Stripe, Microsoft Graph, Google, Amazon SNS and others). Keys pasted from those systems are encrypted with your organization's key and never shown again. Wrong secrets, signatures and tokens are all refused the same way, and repeated failures are slowed down. What a system sends reaches the run only as data, never as instructions, and is kept only with the run, encrypted; the audit trail records each call's outcome and size, never its content. Slack and Teams commands start agents only for your organization's own people, found by their verified email, and only agents they may run; nothing is approved or changed from Slack or Teams. See Start from another system.

Can email start our AI agents? What is kept, and how are senders checked?

Only when an agent's owner gives the agent its own email address, made from random letters and digits rather than the agent's name. An email starts the agent only if its sender is on that agent's list of allowed addresses and domains, and only if the email is verified as really coming from the sender's domain, as the domain's owner has set up. Everything else is dropped without a reply: SourceLace never answers or bounces email to the address it claims to come from. The email reaches the run only as data, never as instructions. SourceLace keeps the subject, sender, date and text only as what triggered the run, and readable attachments (with size and number limits) only with the run, encrypted with your organization's key, and deletes them with the run. The audit trail records each email's outcome, size and the sender's domain, never its content. Owners and admins can rotate or turn off an address at any time. See Start by email.

Can SourceLace staff see our data?

SourceLace's staff manage your account (plan, prices and credits, admins, contract, single sign-on, features) on a staff page. Every change they make to your organization, and every time they read or export your audit log to help you, is recorded in your own audit trail under their name; your admins see those entries on their own with SourceLace staff on the Audit log page (What SourceLace staff did). That page and its export never show data from your systems, sign-ins to them, secrets or AI keys.

Behind the scenes, only a small number of named SourceLace staff can reach the hosting environment, each with their own account through single sign-on with multi-factor authentication, and without long-lived personal keys. Every administrative action in the hosting environment is logged. A written access control policy is in place, and access is reviewed every quarter; the first review was recorded on 4 November 2026.

Data stored, retention and deletion

What does SourceLace store, and what does it not?

SourceLace does not copy your records. Query results are held for at most 30 minutes (up to 2,000 rows a query), in server memory or encrypted in a short-term store, and never written to a database or a log. A larger answer is kept for the same time in a short-lived file encrypted with a key of its own, and only in that encrypted form; if your organization keeps results in server memory only, it is never stored outside server memory. Files are read on demand and never indexed, also when a bucket is searched by file contents (each file is read for that search and its text forgotten straight after); a Search index source only sends searches to your organization's own index; and Search everything searches each system live without building an index or copy; for Amazon S3, Azure Storage and Google Cloud Storage, each person's favourite folders are kept as folder paths only, encrypted with your organization's key. The longer-lived exceptions are saved chats in the SourceLace app and AI agents' run summaries and pending changes, both encrypted with your organization's key. The full list is in What SourceLace stores. Every answer is read live from your systems, unless your organization has chosen Saved answers, an optional add-on your admin turns on system by system.

Can we make retention shorter?

Yes. On the Data retention page an admin can shorten how long results are held (1 to 30 minutes), keep fewer rows, set stricter limits for one source, keep results in server memory only, and delete a chat's results as soon as it is closed (on by default). Each result held and each deletion is recorded in your audit trail, with no row values. See Data retention controls.

How long are chats, agent runs and the audit trail kept?

Saved chats and agent runs: 30 days after last use by default, set by your admin from 1 day up to your plan's longest. The audit trail: your plan's audit history, 90 days to 7 years. See How long things are kept.

What happens to our data when we leave?

Ask support@sourcelace.com to close your account. Nobody can sign in from that moment, and 7 days later everything SourceLace stores for your organization is removed for good, including the audit trail and your organization's encryption key. During those 7 days the deletion can be undone. Some records follow their own schedules instead: the locked daily audit records are kept for 400 days, the records of requested web addresses for 365 days, and backup copies expire on the hosting provider's backup schedule (see the privacy policy). If you want your settings and audit trail first, ask for an export before the deletion. See Removing access and data.

Does SourceLace learn from our people's questions? What can our admins see?

Only if your admin turns on Learn from use (off by default). SourceLace then looks at the questions people ask in the SourceLace app, inside your organization only, for questions several people repeat, and suggests a skill or agent for your admin to review. Admins see the words those questions share, how many people asked, how many questions and on which days; they never see who asked, and never the questions themselves unless they also turn on example questions, which shows up to three per suggestion with personal details such as email addresses and phone numbers masked. A pattern is shown only when at least 3 different people asked it. People are counted with a one-way scrambled code that is never stored. Suggestions are encrypted with your organization's key, are deleted when the chats they came from are deleted, and are never shared with other organizations, sent to SourceLace or used to train AI models. See Learn from use.

What does a rating of an answer store, and for how long?

When ratings are on and someone gives an answer a thumbs up or down, SourceLace keeps the thumbs, the person's optional note, who rated and which answer, never the answer itself and never data from your systems. The note is encrypted with your organization's key. A rating is deleted with its chat or agent, and in any case after your retention period for saved chats and agent runs (30 days after last use by default). The examples an agent's owner chooses from well-rated runs go with those runs. The audit trail records that a rating was given or changed, never the note. See Rate answers.

Can a person ask for their own data to be deleted or exported?

Yes. People can delete their own chats and disconnect any source at any time. For other requests about personal information, email privacy@sourcelace.com.

AI and model providers

Does SourceLace send our data to an AI model?

  • From your own AI app (Claude, ChatGPT, Cursor and others): no. SourceLace returns results to your AI app, which sends them to its own provider under your agreement with it.
  • From the assistant in the SourceLace app, and from AI agents: yes. The conversation (or the agent's instructions) and the results of the tools it used, which can include rows from your systems, go to the AI provider your admin chose.

See AI and your data.

Which providers, and can we use our own account?

By default, Anthropic, through SourceLace's own Anthropic account. Your admin can instead enter your organization's own key from Anthropic, OpenAI, Google Gemini, Mistral, Azure OpenAI or Amazon Bedrock, so requests go under your own agreement with that provider and are billed to you. See AI settings.

Do the providers keep or train on our data?

SourceLace does not train AI models on your data and sends it to no AI provider other than the one your admin chose. Under Anthropic's commercial terms, Anthropic does not train on data sent through its API. Requests to OpenAI are sent with its store option off, though OpenAI's own policies may keep data for a limited time, for example for abuse monitoring. For Google Gemini and Mistral, which only an organization's own key reaches, your agreement with that provider applies. How long each provider keeps requests is set by that provider's terms; a zero-data-retention arrangement on SourceLace's own account is not in place.

Can we stop some fields from reaching the AI?

Yes, on every plan. On the Data protection page your admin can hide a field so it never reaches the AI, or mask values (email addresses, phone numbers, US Social Security numbers, payment card numbers, IBANs and your own patterns) so the AI gets a placeholder. The rules apply to your own AI apps, the assistant, AI agents and runners alike, and people you allow still see the real values in the SourceLace app. Everything is off until you turn it on. The rules cannot cover what someone can work out from other information they already have, values typed into your own AI app (in the SourceLace chat the detectors and your patterns also check the question you type), or text inside images and scans; see What is not covered and Data protection.

Can someone talk the AI into revealing secrets or another organization's data?

No. The AI never holds a secret: sign-ins, AI keys and app secrets are never put in its instructions, tool descriptions or tool results. Organizations are kept apart by SourceLace's code, which checks every request against the signed-in person's organization, so no prompt can reach another organization's data. Text inside your data cannot apply a change either: every change waits for a person. See AI safety.

What if a vendor changes a tool behind an MCP connection we allowed?

SourceLace holds it until your admin reviews it. When the description or arguments of an outside MCP server's tool change after your admin allowed it, the AI is not offered the tool and calls to it are refused. Your admins are emailed, see the allowed and new versions side by side, and choose to allow the new version or keep it blocked. Holding a tool and each review are in your audit trail. See Held tools.

Will the AI tell people how SourceLace is built?

No. What SourceLace tells any AI says what it does, not how it is built, and the assistant's answers about SourceLace itself are checked before they are shown. Your admin can request the security review pack for the technical detail.

Subprocessors

Who processes our data?

The cloud hosting provider; Anthropic for the AI included in your plan; the AI provider of your own key, only if your admin enters one; your sign-in provider; and Stripe for billing (never data from your systems). The full list, with what each one receives, is in Hosting and subprocessors; the legal list is in our privacy policy. The systems you connect receive only the calls each person makes with their own login.

Will you tell us before adding one?

The subprocessor list is updated before a new provider handles customer data. A contractual notice period is not yet formalised.

Logging and audit trail

What is logged?

Every tool call, whether it succeeded, was refused or failed, from the SourceLace app, every AI app and admins; every sign-in, including refused ones; every change to people, sources, groups, single sign-on and settings; every AI agent run, step and approval; and each query result held and deleted. A search across systems (Search everything) writes one entry for each system searched. Each entry holds when, who, the tool, the source, the query text, the object and record id, the names of changed fields, how many rows came back, the outcome, the error type and how long it took. Failed sign-in and token attempts are recorded, including ones that cannot be tied to an organization, without the address or token itself; those are kept by SourceLace and are not part of your audit trail. See The audit trail.

What is never logged?

Row values, field values, passwords, keys and tokens. The query text is kept as written, so a value typed into a query (such as a customer name like "Corvanta") appears in the trail your admins read. The trail is stored encrypted with your organization's own key. SourceLace's server logs never contain tokens, passwords or query results. The servers in front of SourceLace do record the web address of each request for 365 days, and on some lists the words typed into the search box are part of that address (see Searching and sorting lists).

Is the audit trail tamper-evident?

Yes. Entries are chained by SHA-256 hashes per organization, so an entry that was edited, removed or reordered breaks the chain and can be detected. SourceLace checks the audit trail automatically every day and alerts your admins if anything does not match. You can also check it yourself at any time and export it with its proof. If an entry cannot be written, the call fails rather than returning data that was not recorded. The JSON export from the Audit log page reports whether the whole trail still verifies and includes each entry's hashes, so your reviewers can recheck them with SHA-256.

Can we see and export it?

Admins read, filter and search the trail on the Audit log page (Business and Enterprise; on every plan every call is still recorded). Export on that page downloads the matching entries as CSV or JSON. On other plans, ask support@sourcelace.com for an export. On Business and Enterprise, admins can also stream the trail as it is written to a signed webhook, Splunk (HTTP Event Collector), or a bucket in Amazon S3, Google Cloud Storage or Azure Storage, in batches that each carry a hash proof linking them to the one before. See Exporting the audit log and Streaming the audit trail.

Vulnerability management and secure development

How is SourceLace built and tested?

Every change is reviewed and runs through automated quality and security checks before it is accepted, including tests for security behaviour such as read-only query checks, access rules and that secrets never appear in results. Every change is also checked against public databases of known vulnerabilities in the libraries SourceLace uses, and a known high or critical issue blocks the release. The hosting environment is changed the same way, so nothing is set up without a record. Each release is checked for known vulnerabilities, and a release that fails its health checks is rolled back automatically.

Do you do penetration tests or run a bug bounty?

Not yet. No independent penetration test report is available, and there is no bug bounty programme.

How do we report a vulnerability?

Email security@sourcelace.com. What to include, what is covered, how to test safely and what happens next are on Report a vulnerability. There is no bug bounty programme.

How are security fixes delivered?

On SourceLace's cloud, fixes are deployed by SourceLace; you do nothing. On a runner, your IT department takes new versions; the Runners page shows a runner that is out of date. A formal patching timeline (for example, by severity) is not yet published.

Incident response and breach notification

Do you have an incident response plan?

Yes. SourceLace has a written incident response process, adopted in October 2026, covering outages, security incidents and data problems:

  • Anyone at SourceLace declares an incident as soon as they see a possible problem, from monitoring alerts, threat detection, the audit trail's own daily check, or a report from you. One person leads it until it is closed.
  • Four severity levels, from critical (the service down for most organizations, or customer data confirmed exposed) to low. The severity sets how fast SourceLace responds and how often it updates you. Critical and high incidents are worked as the top priority until contained.
  • Harm is stopped first, for example by rolling back a release, revoking a credential or pausing agents; then the cause is found. Evidence is kept, not wiped.
  • Your admins are told by email if your organization is affected. SourceLace sends the first notice as soon as possible after declaring the incident, then regular updates until it is resolved. Notices never name another customer.
  • After a critical or high incident, affected customers get a written summary within 5 working days (what happened, the impact, the cause and what SourceLace is changing), and the team writes a blameless review whose actions are tracked to done.
  • Practice: a yearly exercise that walks through a realistic incident, and database restore drills twice a year.

The timing above is SourceLace's own target, not a contractual commitment. A public status page, round-the-clock phone paging and the first practice exercise are not in place yet. To report a suspected incident, email security@sourcelace.com; for anything else urgent, support@sourcelace.com.

Will you tell us about a breach?

Yes. If customer data, and especially personal data, may have been reached, SourceLace tells each affected customer without undue delay, so you can meet your own duties, and as the law requires. A contractual notification time (such as 72 hours) is not yet formalised.

Can you stop access quickly in an incident?

Your admins can, at once: remove a person, remove a source, turn changes off, pause or stop AI agents, and revoke a runner (a run in progress on it stops within about a minute and writes nothing more). People can disconnect any source themselves.

Business continuity and backups

How is the database backed up? What are your RTO and RPO?

SourceLace's database is backed up continuously: it can be restored to any moment in the last 35 days. The backups are encrypted, and copies are kept in a second US region, so the service can be restored there if the whole primary region is lost. The database is protected against accidental deletion. Restore drills (restoring a backup to a new database, checking it and timing it) are run once a year; the first was done in November 2026 and the restore worked. Recovery time and recovery point objectives (RTO and RPO: how long a recovery may take, and how much recent data may be lost) are not yet defined in writing. Two things are true by design: query results are never in the database, so they are never in a backup; and when an organization is deleted its encryption key is deleted too, so anything encrypted for it that remains in a backup can no longer be read.

Is there an uptime SLA or a status page?

Not yet. No uptime commitment or public status page is published. The app's My connections page shows, for your organization, whether the assistant is ready and how each source's calls went in the last 24 hours, and admins also have a Health page: connections, AI agents, the audit trail, usage and sign-in, with the problems first.

What if SourceLace is unavailable?

Your data stays in your own systems, which SourceLace only reads and changes on request; nothing you rely on lives only in SourceLace except saved chats, skills (with their version history, the newest 200 per skill), projects and agent settings.

Healthcare and HIPAA

SourceLace has no HIPAA Business Associate Agreement programme yet and holds no HIPAA attestation. Do not use SourceLace with patient data or other protected health information until a BAA is available and signed with your organization. Ask security@sourcelace.com to be told when it is.

SourceLace Runner

What does a runner keep, and what does it send to SourceLace?

A runner keeps your AI key, each person's source sign-ins and every run's results on your network. It connects out to SourceLace over HTTPS (you open no inbound port) and sends only each run's status, times, one line per step (tool, source, object, row count, outcome) and health counts; SourceLace refuses any report that tries to include a summary, rows, values, drafts or files. See Runners.

Where are a runner's security details?

In Runner security: field by field what a runner sends and receives, sign-in, encryption and who holds the keys, the image, logs and audit trail, retention, who is responsible for what, and the controls by area of the Trust Services Criteria. The network connections it needs are in Runner requirements and planning.