Your HighLevel account deserves careful access.

Journey Monitor is designed to diagnose customer journeys without changing the HighLevel records it examines.

Read-only, by design and by enforcement

When you connect a HighLevel location, GoCheckLog requests six scopes. Every one of them is read-only.

The application also checks what it was granted. If a connection comes back carrying any permission outside that list, GoCheckLog refuses it rather than proceeding — so the read-only boundary does not depend on a setting staying the way it was configured.

Contacts — read only

contacts.readonly

Identify the contact being investigated.

Opportunities — read only

opportunities.readonly

Examine opportunity records associated with the journey.

Conversations — read only

conversations.readonly

Locate relevant conversations.

Messages — read only

conversations/message.readonly

Examine message activity and available delivery information.

Calendar events — read only

calendars/events.readonly

Examine appointment activity and outcomes.

Pipelines — read only

pipelines.readonly

Show pipeline and stage names instead of their identifiers.

GoCheckLog does not need — and does not request — permission to create, edit or delete these HighLevel records.

We verify. We don’t pretend.

When the available HighLevel data does not provide enough evidence to establish something conclusively, Journey Monitor does not manufacture a successful result. It says what it could not establish.

HighLevel exposes no history or audit data on these objects, so earlier states of a record are not recoverable. A result is a reconstructed snapshot of what the records show now — not an audit trail, and not proof that every part of your configuration is working.

Accounts, credentials and isolation

Your account

You sign in to GoCheckLog with an email address and a password, and confirm your email address before the account is usable. Sessions are held in HttpOnly cookies, and access decisions verify the session signature rather than trusting what the browser sends.

Your HighLevel credentials

The tokens GoCheckLog receives from HighLevel are encrypted with AES-256-GCM before they are stored, using a key held only by the running application. The database never sees the key. You can disconnect a location from your account page, which deletes the stored credentials.

Disconnecting removes GoCheckLog’s copy of your credentials. It does not uninstall the app inside HighLevel — to remove access completely, also remove the app from the location in HighLevel.

Separation between accounts

Every record GoCheckLog stores is owned by one account and isolated at the database level by row-level security, so one account’s data is not reachable from another. Which HighLevel location an inspection reads is decided on the server from your authenticated session — nothing the browser sends can change it.

What is not stored

Inspection results are not stored. Journey Monitor reads from HighLevel when you run an inspection and returns the result to your browser.

No system can be guaranteed secure. This page describes how GoCheckLog is built and what it does with your data; it is a description of our practices, not a warranty.

Independence

GoCheckLog is an independent product from GoCrewIT LLC and is not affiliated with, endorsed by, or sponsored by HighLevel.