Trust center
How public ExactPour content is maintained
Standards for factual scope, transparent calculations, corrections, safe security reporting, and accountable ownership.
Editorial standards
Public educational content should distinguish definitions, formulas, operating suggestions, product behavior, and opinion. A formula states its period and scope. A recommendation explains material tradeoffs and avoids presenting one operating practice as universal.
We do not publish invented studies, customer outcomes, testimonials, credentials, or citations. Product-specific claims should be checked against the current product before publication. Public documentation must not include customer records, tenant data, credentials, access tokens, or internal support details.
Methodology
Our public inventory references begin with auditable conservation formulas: beginning quantity plus inbound movement minus outbound movement minus ending quantity. Sales-based projected usage is calculated separately from recipe quantities and recorded sales, then compared only when period, location, category, and units align. Peer benchmark percentiles use k-anonymity: a cohort aggregate is withheld until enough venues share the bucket, so no single bar can be singled out. That privacy rule used to live on a thin glossary page and now belongs here with the rest of the method.
Interactive tools run transparent arithmetic in the browser. They do not send the entered values to an account, save them, or represent accounting, tax, legal, employment, or security advice. Assumptions and exclusions appear beside each tool.
Corrections and review
Each public guide displays its latest review date. Material corrections should update the page content and review date. Minor typography or layout changes do not require a new methodology review.
To report an error, include the page URL, the statement or formula at issue, your proposed correction, and any primary source that supports it. We review reports for scope, unit consistency, and whether the correction changes the practical interpretation.
Security reporting
Do not place secrets, personal data, exploit details, or customer data in a public issue or public form. Send a concise report privately and include the affected URL or feature, reproduction conditions, potential impact, and a safe way to follow up.
Please avoid accessing data that is not yours, disrupting service, or expanding testing beyond what is necessary to demonstrate the issue. This page does not create a bug-bounty program or promise a reward or response deadline.
Ownership and contact
The ExactPour product team owns the public documentation, glossary, tools, and this trust center. No individual credential or outside endorsement is implied.
Use support@exactpour.com for content corrections, accessibility feedback, privacy questions, and security reports. Put the topic in the subject line so it can be routed correctly.
Data processing & security
ExactPour acts as a data processor for the customer data you enter. Every account is covered by our Data Processing Agreement, accepted and timestamped at signup for all plans. We maintain a current list of subprocessors with at least 30 days' notice of additions and a right to object.
Security measures include encryption of data in transit, platform encryption of data at rest, database-enforced tenant isolation, role-based access controls, and append-only audit logs. Report vulnerabilities privately to security@exactpour.com; DPA execution or enterprise procurement questions to legal@exactpour.com.
Talk with ExactPour
Questions about how ExactPour is run?
For product questions, book a walkthrough. For corrections or security reports, use the contacts on this page or support@exactpour.com.