Defined use and ownership
- Named users and accountable owner
- Permitted and prohibited uses
- Measurable acceptance criteria
TRUST CENTER
Cognitivis treats privacy, security, human oversight, and responsible use as product requirements. The exact controls are defined for each system and deployment environment.
DELIVERY PRINCIPLES
This page describes our working approach, not a claim of certification or a substitute for a project-specific security review.
PUBLIC AI ASSISTANT
Answer brief questions about Cognitivis, its published services, responsible AI, and the VeriSight demo. Harmless greetings are welcome.
Before sending a message, visitors acknowledge that the exchange will be stored for up to 90 days. After that acknowledgement, a first-party anonymous chat cookie assigns the browser an internal visitor number so conversations from the same browser can be grouped. The raw cookie value is never stored in the database; only a one-way hash is retained. A different device, browser profile, private-browsing session, or cleared cookie receives a different number.
Database credentials remain server-side, and visitors can permanently delete their current chat. Deleting the chat also clears the anonymous browser cookie on that device.
Abusive or clearly malicious use may be blocked. Suspicious request content is withheld from transcript storage; only a redacted security event is retained. A normal off-topic question is refused without treating a visitor as malicious.
PUBLIC DEMOS
Built-in examples and supported text files are processed in the browser. The public demo does not upload files or perform OCR on PDFs or images.
Your answers and score stay in the browser. No account is required and the assessment is not submitted.
The form creates a local text file or clipboard copy. It does not send or store the entered information.
QUESTIONS
No certification claim is made on this website. Project requirements, deployment controls, and evidence should be reviewed for the specific engagement.
Data handling and provider settings must be explicitly agreed for a project. The principle is to minimize data, use approved providers and configurations, and avoid secondary use outside the agreed purpose.
Deployment options depend on the use case, security requirements, integrations, and approved infrastructure. These constraints are examined during discovery.
No. Human review is a control, not a guarantee. Reviewers need appropriate evidence, instructions, time, and escalation routes, and the system still needs ongoing evaluation.