Security
Security pages often list badges. This one lists what the IoT app enforces, the audit log you can export, and the certificates we are not claiming.
Each factory has its own account, issued after onboarding. This website does not offer a login. MFA is required for every user. Roles are admin, maintenance and operator. A failed login is written to the audit log. The marketing page is public. The readings are not. The screenshots on this site are the Demo food plant, with simulated telemetry, not a customer’s rooms.
Tap a card to acknowledge it. The person's name is stored on the alert, not a role code. From the same card you can Resolve it, or open Ask about this. A shared login would throw that away, and we will say so if a plant asks for one.
The audit log is append-only and kept for 365 days. A plant can export it as CSV. Command Center exports CSV as well. The parent product describes a separate workspace per company. Read that in their words on factoraerp.com. This page does not upgrade those sentences into a penetration-test report.
The host, the region, and whether an on-premise option exists are not confirmed for the IoT app.
No KEPHIS, KEBS, ISO, SOC or GDP certificate is claimed for FactoraERP IoT.
No uptime percentage is published, and no public status feed is connected.
If a quality agreement needs a supplier questionnaire, a data-processing note, or a description of where readings are stored, ask through the demo form. We will answer from what is true, including where the answer is “not published”. The marketing site’s own privacy note is at /privacy. It covers this website, not the signed-in app.
Report a vulnerability via the contact on security.txt. Please do not include live plant data in the first message.
Book a demo
Region, tenant, and who can export readings. If we cannot answer yet, you will hear that in the meeting rather than in a footnote later.
