Your data, with
clear boundaries.

GoHighLevel access

DataCharted requests data-read permissions for the supported datasets. The extraction process reads CRM data; it does not create, update, or delete records in GoHighLevel. Authorization also supports the OAuth token management needed to maintain your connection.

Your BigQuery project

Extracted CRM records are written to the Google Cloud project and BigQuery dataset you connect. You control that destination and its access policies. The hosted service processes data during a sync, and stores account settings, encrypted connection credentials, and operational run information required to provide the service.

Choosing a BigQuery region does not mean every component of the hosted service runs in that region. If you have a specific deployment or data residency requirement, discuss it with us before connecting production records.

Connection credentials

The product supports GoHighLevel OAuth and a BigQuery service-account connection, with Google authorization available when enabled. Stored connection secrets are encrypted by the application. Do not share keys or tokens in support emails.

Controls available to you

• Select the locations and streams included in future runs.
• Manage schedules and trigger manual runs.
• Inspect run results and configure outcome notifications.
• Disconnect the BigQuery connection and revoke authorization with the provider when required.
• Contact support to request account or service-data deletion.

Reporting access is a separate decision

A dashboard can expose data to viewers even when those viewers cannot sign in to DataCharted. Configure permissions in BigQuery and your reporting tool for each client. A dashboard filter is not a substitute for an access-control policy.

Need a review before connecting?

Email support@datacharted.com with your requirements. We can discuss processing, retention, permissions, and deployment scope before you begin. Details of our current handling are in the Privacy Policy and Terms of Service.