What we do with your data, in plain language
No jargon and no fine print. Here is exactly what ERPeek reads, sends to the AI, stores, and deletes, and who can ever see it.
- Scoped live reads
- Optional SQL dumps isolated
- Never used to train AI
- Delete anytime
The life of a question
- 1
We read only what a question needs
Through a scoped, read-first connection that you authorize, we fetch the specific records required to answer you. We do not browse your ERP outside the access you configure.
- 2
The AI sees only your project
Your question and the project code, files, and records the AI reads to answer it are what reach the AI. Your credentials and other customers’ data never do. Your data is never used to train AI models.
- 3
We store what the product needs to work
We store your account, your questions and answers, a search index, and SQL dumps only when you choose to upload them. Uploaded dumps are kept in an isolated per-project database so ERPeek can query them for your answers.
- 4
We keep it only as long as it’s useful
You can request a copy or the complete deletion of your data at any time, and we confirm in writing. Payment card details never touch our systems.
Who can reach your data
- You, it’s your data, available to your account.
- Internally, access is limited and scoped to supporting your account.
- Every customer is fully isolated; no one else can see or query your data.
Privacy commitments we can stand behind
Clear operating practices, scoped to the controls ERPeek currently ships.
- We support GDPR and Québec Law 25 data-rights workflows, including access and deletion requests.
- A named privacy contact owns data protection requests and is your direct point of contact.
- Deletion requests are confirmed in writing once the operator runbook is complete.
- Your data is never sold, shared for advertising, or used to train AI models.
Want the full security picture?
See exactly how we protect your data at every layer, or ask us anything.
Reflects ERPeek as of June 2026.