Security & privacy
Transfer pricing documentation is built from sensitive financial and organizational data. This page describes, in plain terms, how TP Model protects that data today.
Customer data is isolated at the database level
TP Model is a multi-tenant service: many organizations use the same infrastructure. Each customer's data is isolated at the database level. PostgreSQL row-level security is enforced on every tenant table, so one customer can never see another's data, even if application code has a bug.
Sign-in without stored passwords
Sign-in and session management run through a dedicated authentication provider (Clerk). We never store passwords.
Encryption in transit and at rest
All traffic to TP Model is encrypted in transit with TLS. Stored data is encrypted at rest with AES-256 by our database and file-storage providers.
Credentials for accounting integrations are additionally encrypted by the application before they are stored, and are used only to retrieve the data you authorize.
Built for the GDPR
TP Model has a privacy policy that sets out what personal data we process and why, and how you can exercise your data-subject rights, such as access, rectification and erasure. We have data processing agreements with all our subprocessors, incorporating the EU Standard Contractual Clauses.
The full list of subprocessors and the details are in our privacy policy.
Your documents are not used to train AI models
TP Model uses an AI provider to extract data from your documents and to draft parts of your documentation. Your documents are not used to train AI models: our AI provider's commercial terms prohibit training on customer content.
Certifications
TP Model does not yet hold its own ISO 27001 or SOC 2 certification; our infrastructure providers are independently audited.
Reporting a security issue
If you believe you have found a security issue in TP Model, please e-mail us at info@tpmodel.ai.
See also our privacy policy, terms and conditions and company information.