The short, plain-English version. The binding documents are the Privacy Policy and EULA, linked at the bottom of this page.
The promises
Enterprise buyers will not adopt a tool that exposes their internal commercial intent. This is the architectural commitment, not a policy choice we could reverse later. The product is built around it.
01
Your project descriptions, scope inputs, requirements, and conversation data are processed to generate your output and nothing else. Not by us. Not by our AI provider.
02
No data brokers. No advertising networks. No third parties paying us for access to who you are or what you are buying.
03
What you are evaluating, what it might cost, who is involved internally. That is sensitive information. We treat it that way, and our subprocessor list reflects that.
04
No precise geolocation. No biometric data. No cross-site tracking. No third-party analytics on our marketing site. Email, password, and what you choose to put in a project.
What we collect
Subprocessors
A short, named list. No surprises. Each one handles only what is necessary to do its job.
| Provider | What they do | What they handle | Location |
|---|---|---|---|
| Anthropic PBC | AI inference (Claude API) | Project inputs and prompts | United States |
| Supabase Inc. | Database, authentication, storage | Account data, project content, usage logs | United States (AWS us-east-1) |
| Vercel Inc. | Application hosting and compute | Request logs, IP addresses | United States |
| Formspree | Access request form processing | Name, company, email, role | United States |
Retention
Your rights
Depending on where you are, you have rights over the personal information we hold about you. Email hello@planwithpario.com to exercise any of them. We respond within thirty days.
Security
Data in transit is encrypted with TLS. Data at rest in Supabase is encrypted with AES-256. Access to production systems requires multi-factor authentication. Row-level security policies isolate every organization's data from every other organization's, enforced at the database layer.
Pario is in beta. We take security seriously and we will not pretend the product is invulnerable. If you find a security issue, please report it to hello@planwithpario.com.
The fine print
This page is the plain-English version of how Pario handles data. It exists to make the substance readable for the procurement, legal, and information security professionals who need to vet us before their organization uses the product.
It is not a substitute for the binding documents. If anything on this page reads differently than the Privacy Policy, EULA, or Terms of Use, the binding documents control.