DMELOG FIELD COMMAND CENTER

Security & Privacy

How DMElog protects beta-user accounts and field information.

Your account boundary

Account-isolated data
Routes, visits, mileage, photos, OCR, Office Passports, reports, and Bret context are queried using the authenticated user ID.

Passwords are not recoverable
Passwords are stored using modern one-way password hashing, not readable encryption.

Encrypted in transit
HTTPS protects information moving between your device and DMElog.

Private photo delivery
Visit photos should be served through authenticated ownership-checked endpoints, not public directory links.

Healthcare caution
The closed beta is intended for referral-relationship information. Do not enter or photograph patient-identifiable information.

Session protection

Secure, HttpOnly, SameSite cookies; session-ID rotation at login; idle timeout; login rate limiting; CSRF protection; and account-status revalidation are enabled.

Your control

Contact the beta administrator to request an export or deletion of your beta account data.