How DMElog handles account, app, and Google connection information.
Effective Version: V38
DMElog may store account information such as name, email, company, territory, phone number, role, account status, invite status, login timestamps, password reset records, and the user’s Google Apps Script Web App URL.
Visit logs, office notes, contacts, photos, mileage, and reports are sent to the Google Sheet/Drive backend configured by the logged-in user. That data remains controlled by the user’s Google account and Apps Script deployment.
DMElog does not sell user data. DMElog does not share user data except where needed to operate the platform, support the service, prevent abuse, comply with law, or integrate with user-directed services.
DMElog uses password hashing and account sessions. Users should use strong passwords, protect Google account access, and avoid sharing credentials. No web platform can guarantee absolute security.
When Bret AI features are enabled, relevant user account, route, visit, and office memory information may be used to generate coaching or summaries for that logged-in user. AI output should be reviewed before use.
For privacy or account questions, contact the DMElog administrator.
Return to Account