Privacy
What we read, what we store, and what we never touch.
SuitePulse analyzes how an ERP environment is configured and how it runs, not the business records it processes. This page states that boundary precisely.
The factual position
- What the analysis reads
- Configuration and code: customizations, scripts, workflows, report and search definitions, file metadata, and execution history.
- What it never reads
- Transaction amounts, customer, vendor and employee records, and the contents of files.
- What we store
- Findings, scores and analysis timestamps, so health history works across analyses. Deleting an analysis removes it.
- What the website collects
- The analysis and partner request forms collect your name, role, company, work email, which ERP you use, and optionally a short description of your problem. It is used to reply to your request.
- Blog images
- Some blog images load from third-party hosts. When they load, that host receives your IP address and browser details.
- Admin sign-in
- Staff who manage the blog sign in with Google. This site has no visitor accounts.
- Analytics
- None is configured on this site at present. If privacy-friendly analytics is added, it will be stated here before it is enabled.
- Encryption
- TLS in transit, encrypted at rest.
The formal document is in preparation
What is above describes how the product behaves and is accurate. It is not the executable agreement, and it has not been through legal review. If you need the current draft for a procurement or security review, request it at hello@suitepulse.com and we will send what exists rather than point you at this page.