Security
Your commercial terms are among your most sensitive data. We treat them that way.
Scales, negotiated rates, turnover per supplier: Palier isolates every account at database level, records every action and gives its AI assistant no write access at all.
Account A · Distributor
- Owner
- Purchasers
- Viewers
Supplier contact
sees only its own supplier
Account B · Buying group
- Owner
- Purchasers
- Viewers
Supplier contact
sees only its own supplier
Row-level security (PostgreSQL). Every table carries the account id; the database itself refuses any read outside the session’s account.
Account isolation
- Account id on every business table, access always scoped by account
- PostgreSQL row-level security policies: the application connects with a role that cannot bypass them
- Automated cross-account leak tests on every code change
- A supplier contact belongs to a single supplier and sees only its data
Authentication and sessions
- Passwords hashed with argon2id, today’s recommended algorithm
- Server-side, revocable sessions in an HttpOnly, Secure, SameSite cookie
- Attempts limited per IP address and per email, temporary lockout after repeated failures
- Members and suppliers join by invitation only
Permissions
- Four fixed roles: owner, purchaser, viewer, supplier
- Permission matrix in code, checked by tests on every route
- Reopening validated data reserved to the owner, with a mandatory reason
Traceability
- Audit log of every creation, change and transition: author, date, values before and after
- Validated data is frozen; a correction goes through a recorded reopening
- Finalised results reopened as numbered revisions
Artificial intelligence
- No write access: the assistant only produces recommendations
- Every approved action goes through the same service as a human click, with that person’s permissions
- Read-only tools scoped to the account, no web browsing
- Protection against instructions hidden in supplier messages
- No model training on your data; trace content switchable by the owner
Application security
- Strict security headers: content security policy, HSTS, no framing
- Request and upload sizes bounded, Excel workbooks read with zip-bomb limits
- Heavy requests throttled so that one user cannot saturate the service
Operations
- Container runs unprivileged, with a read-only file system
- Database on an internal network, no exposed port
- Full backups verified by checksum, with an optional off-site copy
- Secrets kept out of the image and the code repository
Software supply chain
- Pinned dependencies with tracked updates, vulnerability scans on every change
- Secret scanning across the whole code history
- Over 90% of the code covered by tests, on every change
Questions about security
Can another Palier customer see our data?
No. Every account is isolated twice: the application scopes every access by account, and the database itself enforces row-level security policies that refuse any read outside the session’s account.
Do our suppliers see other suppliers’ terms?
No. A supplier contact belongs to a single supplier of the account and sees only its own agreement, declarations, results and negotiation.
Can the AI assistant change our data?
No. It can only create recommendations. Every action needs the approval of a person allowed to take it, and is executed by the same service as a manual action, recorded in that person’s name.
Can you answer our security questionnaire?
Yes. Send it from the demo page: we answer it and can set up a call with your security team.
See Palier on your own tier scales
30 minutes through declarations, validation, calculation and negotiation of your rebates. Send us a scale and we will set it up for the demo.
- Demo on your sample data
- In English or French
- No commitment