Security

Built by someone who has protected data where the stakes are highest.

Our founder spent more than fifteen years in data governance, risk, and AI in financial services, including building a bank's end-to-end privacy-compliance automation with data loss prevention and PII controls, and responsible-AI guardrails based on the NIST AI Risk Management Framework. The same discipline shapes everything we build.

Cartesian Compass · in place today

How we protect your data now.

Available

Separation between organizations

Every organization's documents, search index, and conversations are kept separate. One organization's data can't be searched or read by another.

No secrets in the browser

The public assistant can only answer questions. It holds no keys, and it can't trigger document collection or change any settings.

Locked-down administration

Administrative functions require a separate admin credential. If that credential isn't configured, they refuse all access by default.

Abuse controls

Public chat is rate-limited, unusual traffic raises an alert, and an instant off switch stops public answers without affecting staff access.

Audit trail

Every request is logged in structured form with a traceable request ID. Passwords, tokens, keys, and personal details are automatically redacted from those logs.

Public content stays public

The public assistant works from information your organization already publishes. Nothing internal is needed to start.

Cartesian Compass · on the roadmap

Built for internal records.

These capabilities are designed for internal staff search and are being shaped with public-sector IT teams. We label them clearly because you should know exactly what exists today.

In development

Private deployment in your cloud

For internal records, an option to run inside your own Microsoft Azure environment, isolated on a private network rather than exposed to the public internet.

Sensitive-data redaction before AI processing

Screening content for sensitive values such as Social Security numbers and credentials before it reaches an AI model.

Role-based access for internal records

Not every internal record should be visible to every employee. Access will follow the permissions your organization already uses.

Cartesian Logistix

Your client list stays yours.

Route planning means home addresses, sometimes of people who need extra care. So Logistix was designed from day one to work without keeping them.

Built in

We don't keep your client list

Logistix works from the spreadsheet you already keep. Your list lives only in your open session, and clearing the screen or closing the tab wipes it.

Your records stay in your hands

Plans come back to you as a map, schedules, and an Excel tracker you keep. There's no copy of your clients on our side to lose.

Coming next

Before it handles real client addresses, Logistix will run on its own routing server, so addresses aren't sent to an outside mapping service.

Transparency

The AI services Cartesian Compass uses.

Your IT team should know exactly where data goes. We name the providers we rely on rather than hiding them behind a brand.

Anthropic (Claude): Writes the plain-language answers, using only the sources retrieved from your documents.
Voyage AI: Turns documents and questions into search vectors, so the right passages are found by meaning.

Both are called over secure connections. Wherever the application is hosted, it needs outbound access to these services. We'll always tell you that plainly rather than promise a fully offline system.

Have a security questionnaire?

Send it over. We'd rather answer hard questions up front.