Summary: Contrax is a multi-tenant SaaS for post-signature renewal ops. This page is the security-review pack for procurement: data classes, controls, subprocessors, and what we do not claim. It is not a certification.
Security review pack
Security contact: Elom E., founder of Contrax. Publisher details are in the legal notice. Use this page with trust & data processing, the privacy policy and Enterprise SSO. Only what is written here and your signed contract are binding; binding terms live in Terms and Licensing.
Contrax has no public SOC 2 report and does not hold ISO 27001, SOC 2 or HDS certification. We do not claim one on this page.
Data Contrax stores
- Contract metadata (parties, dates, notice periods, workflow, notice proof hashes)
- Uploaded PDFs/DOCX you choose to ingest
- Integration secrets you save (webhooks, ERP tokens) — editable by workspace owners and admins only
- Audit export rows (workflow, portal, extraction review, approvals)
Hosting and location
The application runs on Vercel. Application data is stored in a hosted PostgreSQL database, and uploaded files in private Vercel Blob storage. The hosting and database regions are being confirmed and are not yet published on this page. Until they are, we do not claim that your data is stored exclusively in the European Union. Some subprocessors below are based outside the European Economic Area; see the privacy policy for how transfers are framed.
Encryption
- Traffic to the application uses HTTPS (TLS).
- Encryption at rest of the database and file storage relies on our hosting providers; we have not yet documented its details here.
- Integration settings are editable by workspace owners and admins only. API tokens and the webhook signing secret are shown in the app as set or not set, never echoed back. Application-level encryption of integration secrets, with a key kept outside the database, is in progress and not yet in place.
- We do not store card numbers: payments are handled by Stripe.
Access control
- Clerk authentication; Enterprise SSO enforcement for SAML/OIDC IdP logins
- Workspace roles: owner, admin, manager and viewer; viewers cannot edit
- Tenant API routes are scoped to the signed-in member's organization
- Rate limits on sensitive routes
- Audit export v2 (CSV/JSON) on Enterprise, for workspace owners and admins
- Optional shared secret header (
X-Contrax-Signature) on HTTPS webhooks — sent as-is by default, not an HMAC payload signature. Workspaces can explicitly opt in to signed v1 requests; see the webhook documentation. - Pages whose URL carries an access token (approval, vendor portal, invitation) do not load Microsoft Clarity, stop PostHog session recording, and have the token removed from analytics URLs.
Backups
Backup frequency, retention and restore testing are not yet documented on this page. Ask us for the current status during your review.
Subprocessors (typical production)
- Vercel — application hosting, file storage and site analytics
- Clerk — authentication and Enterprise SSO connections
- Hosted PostgreSQL provider — primary data
- Resend — transactional email
- Stripe — billing
- Anthropic — vendor extraction when you run an analysis pass
- Inngest — scheduled jobs (reminders, ETL, warehouse export)
- PostHog — product analytics
- Microsoft Clarity — session analytics, when enabled
- Upstash — rate-limit counters, when configured
Integrations your administrators choose to connect receive the data you decide to send them. Regions for each subprocessor are being confirmed and will be added here.
GDPR and data processing agreement
For the data you put in Contrax, you are typically the controller and Contrax acts as processor. To request a data processing agreement (GDPR art. 28) or to send a security questionnaire, email sales@usecontrax.com. For our own accounts, billing and public site, we are the controller; see the privacy policy.
Reporting a vulnerability
If you find a security issue in Contrax, write to securite@usecontrax.com with enough detail to reproduce it. Do not include other people's personal data, and do not go beyond what is needed to demonstrate the issue. Reports in French or English are welcome. A contact file for researchers is published at /.well-known/security.txt.
Incidents
If a security incident affects your data, we will inform you without undue delay, as the GDPR requires of a processor (art. 33(2)) and as set out in your contract.
What Contrax will not do
- Email opt-out notices to your vendors
- Act as legal counsel or a CLM authoring suite
- Claim review ratings or security certifications it does not hold
Enterprise support: in-app priority ticket (4-hour first-response target, Europe/Paris business hours) or sales@usecontrax.com. Status: status page.
Last updated: 15 November 2026.