2. Local Processing And Data Safety

Understand what EPM Vitals processes locally and how to keep sensitive project evidence out of support requests.

Local processing boundary

EPM Vitals runs locally on the user's machine. Core processing of EPM snapshots, CSV files, Excel grids, metadata packages, configuration workbooks, validation results, conversion outputs, and run history is performed on the local device.

The tool does not require an internet connection to process business files. Typical project files remain on the user's machine unless the user explicitly exports them, copies them, or sends them to someone else.

The Oracle EPM API connector is the exception: it uses the user's Oracle EPM Base URL, username, and password to connect to Oracle EPM and pull selected migration artifacts. EPM Vitals remembers Base URLs only for convenience. Passwords are used for the current connection action and are not stored by EPM Vitals.

Support and sample-file safety

For support and bug investigation:

Do not send production data directly to EPM Vitals support.
Do not send customer production snapshots, real financial data, employee data, customer data, confidential account structures, or sensitive business rules.
Use sanitized sample files whenever possible.
When reporting an issue, provide the smallest reproducible example, a screenshot of the error, the module name, the action performed, and any non-sensitive run summary or log.
Send support questions to support@epmvitals.com.