Security & Trust

Clear about what we do — and what we don’t do yet.

Our assistants talk to your customers, so we hold ourselves to plain, verifiable statements. Here is where we stand today.

To verify with the clientThis page launches only if its content can be backed up. Otherwise the essentials move to the footer and legal pages.Owner: CEO

CURRENT STATUS

Developing our security and privacy framework.

We don’t claim certifications or compliance we haven’t achieved. We will publish each control as it is in place.

//01 Trust

Our AI assistant handles the routine work. You stay in control.

It works inside the boundaries you set. When a request needs judgment, it escalates rather than guessing or making a promise you didn’t authorize.

On its own, it…

  • Answers common questions from your approved information
  • Explains services, published prices, business hours and policies
  • Collects contact details and requirements, with notice
  • Organizes inquiries and routes them to the right place
  • Recognizes when a request is beyond it and directs the customer to a person

It never…

  • Invents prices, availability, policies or commitments
  • Says a booking, cancellation or update succeeded unless your system confirms it
  • Goes beyond the permissions and rules you set
  • Diagnoses conditions, prescribes treatment or replaces a professional’s judgment
  • Discloses customer information or uses it for anything you haven’t authorized
  • Carries on when a request needs human judgment

Developing our security and privacy framework. No certifications claimed.

Security & Trust
To verify with the clientPlease confirm these lists. We’ll present them as promises only once the permissions, hand-over to a person and activity records behind them are built and tested.Owner: CTO
//02 For your customers

What customers are told in every chat.

TopicWhat customers are told
AI disclosureThey are talking to an AI assistant, not a person.
What’s collectedName, contact details, messages and appointment details.
WhyTo answer questions, handle inquiries and support bookings or follow-ups.
Who sees itThe business they contacted and authorized service providers.
Sensitive informationNot to share medical, financial or other sensitive details in chat.
Retention[Retention period or criteria]
Content neededRetention period or criteriaOwner: Legal counsel
Their rights[How to request access, correction or deletion]
Content neededHow to request access, correction or deletionOwner: Legal counsel
Talking to a personHow to ask for a person when the assistant can’t help.
To verify with the clientHealthcare customers have extra obligations. A chat notice does not replace a practice’s own HIPAA Notice of Privacy Practices. Dental practices wait for the healthcare review.Owner: Legal counsel
//03 Your data

Where data sits and who can reach it.

Hosting and storage

[Hosting provider and data storage location.]

Content neededHosting provider and data storage location.Owner: CTO

Access

[Who can access customer data (US and India teams), and the safeguards in place.]

Content neededWho can access customer data (US and India teams), and the safeguards in place.Owner: CTO

Records

[What each conversation and action writes to the record, how long it is kept, and who can read it.]

Content neededWhat each conversation and action writes to the record, how long it is kept, and who can read it.Owner: CTO
//04 Responsible AI

Our principles.

These principles describe how we build and run our assistants. Where a safeguard is still being put in place, we say so.

01

Transparency

Customers always know when they are talking to AI.

02

Human oversight

Assistants handle routine work; sensitive or consequential decisions involve a person.

03

Privacy and security

Collect only what’s needed and protect it with appropriate safeguards.

04

Accuracy

Answer from approved information, and escalate when unsure.

05

Accountability

Clear owners for monitoring performance and handling concerns.

06

Continuous improvement

Review and improve as technology, needs and regulation change.

To verify with the clientMark which principles are already in practice and which are planned, and list exactly which actions need a person’s approval.Owner: CTO + CEO + Legal counsel
//05 Common questions

What security reviewers ask us.

Straight answers to the questions practices and procurement teams ask first.

Is Cognelith HIPAA compliant?

Not yet. HIPAA readiness has not been independently evaluated. Please don’t use the assistant to collect protected health information. We’ll assess HIPAA requirements before offering healthcare-specific products.

Do you have SOC 2 or ISO 27001?

No. We have not completed a SOC 2 examination or started ISO 27001 certification.

Do you take card payments?

Not in Capista at launch. If payments are added later, a third-party payment processor will handle card details.

Where is our data stored, and who can access it?

[Answer to come from the CTO — see “Your data” above.]

To verify with the clientThese answers use your own status: no certifications, no independent audits, HIPAA readiness not yet assessed, and no card payments in Capista at launch. Confirm you’re comfortable saying this publicly.Owner: CEO + CTO + Legal counsel
//06 Security reviews

Need documentation for a review?

Practices and procurement teams can ask for what we have so far.

Contact us
To verify with the clientProposed contact: security@cognelith.com. Confirm the inbox, and which documents can be shared with reviewers.Owner: CTO