Skip to content
cogitto

Cogitto / Policies

Privacy Policy

Version October 21, 2026 · public website access update · Effective on publication

How the public Cogitto website, customer account and authorized reference service handle information.

Operator and contact

Adelard Banza operates Cogitto from 5050 Hacienda Dr., Dublin, CA 94568, United States. For privacy questions or requests, email support@cogitto.com with the subject “Cogitto privacy”.

This notice covers the current service, not planned products or the separate websites linked as reference sources. Do not send patient information to Cogitto.

Information we process

Account and access information includes your email address, identity-provider identifiers, sign-in and verification status, session records, workspace membership and authorization records. Microsoft processes your password and verification factors; Cogitto’s application does not receive your password or email verification code.

Reference requests include the selected ingredient identities and the workspace needed to authorize the request. The service processes these selections to retrieve the corresponding reference. They must not be accompanied by patient, dose or treatment information.

Operational information includes request timing, service status, security and audit events, software versions and credential-renewal health. Hosting and identity providers also process connection information, including IP addresses and browser information. Our application telemetry is designed to exclude tokens, passwords, raw request bodies and patient or reference-query content.

Reference issue reports contain the selected category, record and version identifiers, optional source identifier, authenticated account/workspace identifiers and receipt time. Handling records include access and status changes, the operator, any hold reason and a review-record hash. The reporting form accepts no patient narratives, free-text clinical content, screenshots or attachments.

If you email us, we receive your email address, message and any attachments you choose to send. For report follow-up, send only the receipt ID; do not send patient information or clinical attachments.

Why we use it

We use this information to authenticate users, enforce access restrictions, operate workspaces and reference lookups, investigate errors and abuse, respond to inquiries and maintain the service.

We do not sell personal information, share it for cross-context behavioral advertising, or use optional advertising or audience-analytics cookies in this release. We do not use customer lookup content to train an AI model in the current reference workflow.

Service providers and external sources

Microsoft Azure hosts the application, databases and operational telemetry. Microsoft Entra External ID handles customer identity, verification and account recovery. Microsoft services also process mail sent to the support address. Authorized operators may access information when needed to provide support, maintain security or meet legal obligations.

Opening a publication or label link takes you to another provider, which receives connection information and applies its own privacy practices. Cogitto does not control those websites. We may disclose information where required by law or necessary to protect legal rights and security.

The main application resources are hosted in Azure’s West US 2 region. Identity, edge delivery and support services may process information in other locations; this is not a promise that all information remains in that region.

Retention and protection

Customer sessions expire after at most 12 hours, with a 30-minute inactivity limit. An unfinished sign-in flow expires after 15 minutes. Expiry prevents use; it does not promise immediate removal of every related server record or backup.

The application’s Azure telemetry workspace is configured for 90-day default retention. Identity-provider records, security records, account/workspace records and support correspondence have separate retention needs. We do not yet publish a fixed deletion period for each of those categories.

Reference issue reports and their handling history remain while open or on a documented safety/legal hold. Closed, unheld reports become eligible for removal after 90 days. An hourly application sweep removes eligible records while the service is running; downtime or a maintenance failure can delay removal until service is restored. Database backups and support emails have separate retention. A report receipt is not a clinical review or a promise to change content.

We retain account and workspace information while needed to operate the authorized service, handle requests and meet security or legal needs. Contact us to request deletion or learn what can be removed; retained audit records or backups may require separate handling.

We use encrypted transport, restricted access and managed infrastructure controls. No system is completely secure, and this notice does not claim end-to-end encryption, healthcare compliance certification or clinical validation.

Your choices and requests

You can sign out, use the hosted password-recovery flow, and contact us to request access, correction or deletion of your information. Applicable rights depend on your circumstances and law. We may need to verify your identity without asking you to email passwords or codes.

Cookie preferences explains the current necessary-only configuration. The application does not change its behavior in response to a browser Do Not Track signal; it does not conduct cross-site advertising tracking in this release.

Account and workspace services are intended for adults. The current internal QA reference content is available only to specifically authorized users, not children. If you believe a child has submitted personal information, contact us so we can investigate and address it.

Updates

We will update this notice when information handling changes and identify the version date. Where required, we will provide additional notice before a material change takes effect. Expanded product access or new tracking must be reflected in these disclosures before use.