core

Public pages and private decisions are different systems

Marketing and educational pages are public on purpose. Your analyses, verdicts, and outcomes are not. That boundary is part of the product.

Workspace privacy

Decisions live behind an account. They are not written into the public sitemap. A guessable URL is still not a public document; the app requires a session.

What we do not rely on

robots.txt can ask a crawler not to fetch /app. It is not a security control. Do not put secrets in public pages. Do not expect Disallow to hide an unauthenticated leak.

Transport and cookies

The site uses HTTPS. Session cookies authenticate the app. You can sign out. You should treat shared computers as shared.

Models and your content

Analysis uses model providers. Do not paste secrets you would not send to those providers. Minimize personal data in decision text.

Related pages

core

Privacy

This page explains what the product is designed to collect. It is not legal advice. If you need a contract or a DPA, ask us in writing. Do not treat a marketing...

feature

Decision history

Each decision in Argumont keeps its analysis and later steps together. That is the product's memory. It is not a public page and not a dump of every token.

learn

Audit trail

Regulators and boards sometimes require a trail. Operators need one even when nobody is asking, because memories of meetings are fiction.

core

About

Argumont is for people who have to defend a choice after the meeting ends. It is a decision intelligence platform, not a writing assistant and not a consensus t...

Read the privacy notice

Argumont challenges assumptions, researches evidence, compares competing approaches, and identifies the strongest decision.

Read the privacy notice