Appearance
KAIDAN continuity, support, and customer exit
This page explains what happens if the company-hosted KAIDAN service has an outage, if you leave the service, or if Unfettered Minds LLC discontinues it. It also tells you which protections are active today and which still require an independent provider.
Operating schedule and controls
Reviewed September 7, 2026 through 09:39:55 UTC. The schedules below are not evidence that each run completed. The dated trust evidence sheet separates the completed O02 technical recovery result, the earlier KAIDAN test-account recovery result, broader Briard recovery, independent succession and external assurance.
- KAIDAN runs on company-controlled hosting and does not depend on the founder's personal laptop.
- The host is checked every five minutes and the public service boundary every ten minutes.
- Production is backed up every day to encrypted off-host storage.
- A network-isolated restore is scheduled every week; each completed run needs a dated, release-bound result.
- Each backup includes the exact deployed application release, database, archived database recovery files, evidence-object storage, cryptographic service state, and non-secret configuration.
- Evidence records and immutable evidence-package objects are retained for 365 days by default. A legal hold may extend retention.
- Authorized users can export custody-verifiable evidence packages.
The backup password and cryptographic recovery material are stored separately from the encrypted backup. A stolen backup by itself is not enough to run the service.
O02 technical production recovery is complete for deployed KAIDAN revision 6b71b4dede46543a030a26f2024a12150c1e057b. CI, Security and production deployment succeeded. At 09:38:44 UTC, encrypted snapshot c76e7184574f33c20a044c8c6f8afd450f2a0329f88aec542d8938c518d4bdd3 recorded schema ID b6d9b467cd2cc2adf9766cfb770a65a5d94573273cc784d47d4d734419ba7e99. A network-isolated restore recovered 2,035 files totaling 255.731 MiB in 8 seconds; release, object-store, OpenBao and continuity-audit checks passed. The fail-safe confirmation negative test passed: the guarded recovery action did not proceed without the required confirmation. A controlled restart, alert and health recovery ran from 09:39:36 to 09:39:55 UTC in 19 seconds, and the final health audit passed.
Recovery targets
KAIDAN currently operates to these objectives after Unfettered Minds LLC declares a company-hosted disaster and begins recovery:
| Objective | Target |
|---|---|
| Maximum intended data-recovery gap | 24 hours or less |
| Intended service recovery time | 24 hours or less |
These are objectives, not measured attainment or a new contractual SLA. The O02 result is one controlled company-hosted rehearsal; its 8-second isolated restore and 19-second restart/alert/health recovery do not prove the targets across every disaster scenario. KAIDAN test-account recovery is already evidenced separately: a July 2026 record retained a successful fresh Entra MFA sign-in and protected case read with HTTP 200. The Entra success was operator-transcribed, not retained as a raw provider export. That test-account result does not prove an Owner role, independent second-person succession or recovery for every customer identity provider. These targets do not include delays caused by your identity provider, network, source product, customer-managed key, authorization decision, or another provider your organization selected.
Support response targets
During the free launch-year window, no service credits apply.
| Priority | Example | Initial response target |
|---|---|---|
| P1 | Confirmed cross-customer exposure, custody-verification failure, or complete company-hosted intake outage | 4 business hours |
| P2 | Material investigation or export feature impaired with a workaround | 1 business day |
| P3 | Non-critical defect or degraded connector | 3 business days |
| P4 | Question, compatibility inquiry, or feature request | 5 business days |
Business hours are Monday through Friday, 9:00 AM-5:00 PM US Central Time, excluding US federal holidays. Automated alerts run continuously; that is not staffed 24/7 human response. A response means acknowledgement and triage, not a guaranteed repair time. A P1 AI alert and a P1 service-support ticket are different records; an alert alone does not promise human intervention.
Report a security issue to security@briard-ai.app. Request product help at support@briard-ai.app. Do not email prompts, responses, credentials, or customer production data.
Planned maintenance
When practical, Unfettered Minds LLC provides at least 48 hours' notice before planned maintenance expected to interrupt access. Emergency security or recovery work may proceed without advance notice.
If your organization leaves
- Export every required evidence package before termination.
- After an ordinary customer-requested termination, a 30-day read-only export window is provided unless access must be restricted for a documented legal, security, sanctions, or future contractual reason.
- The export window does not erase the 365-day retention rule or a legal hold. Approved deletion follows the governed disposition process and leaves a disposition receipt.
- Standard self-service export is included. Custom migration, connector work, and professional incident-response services require a separate written scope.
If KAIDAN is discontinued
If Unfettered Minds LLC voluntarily discontinues the company-hosted KAIDAN service, it will provide at least 90 days' notice when legally and operationally possible and will prioritize customer export during that period.
Source escrow and second-operator status
KAIDAN has encrypted off-host recovery and a documented second-operator recovery procedure. It does not currently have an activated independent source-code escrow agreement or a completed independent human-succession rehearsal. Do not interpret backups as third-party escrow.
The completed test-account and technical recovery checks do not satisfy this separate second-person requirement.
Formal source escrow requires a selected independent agent, approved recurring cost, an executed three-party agreement, a beneficiary model, automated deposits, deposit verification, and enforceable release conditions. Independent operational succession requires a second named human with separate accounts and MFA who successfully completes the recovery rehearsal without using the founder's laptop or credentials.