Developer · ASG Help
Account, device, and data security
Practical controls for a service that combines GHL, Android phones, carrier SIMs, APIs, and client access.
Before making production changes: exact screen names and platform behavior can change as GoHighLevel, Android, carriers, and the underlying messaging platform evolve. Test changes on a controlled deployment first.
Recommended controls
- Enable 2FA wherever supported.
- Use unique passwords and a password manager.
- Keep API keys server-side.
- Restrict who can access master agency credentials.
- Use screen locks on gateway phones.
- Keep Android updated when practical.
- Remove former staff/client access promptly.
Encryption
The underlying platform advertises AES-256-GCM protection for supported phone/server communication. Encryption is one layer; account access, device security, and operational controls still matter.
Incident response
If a device or credential is lost, disable/revoke access, preserve logs, rotate secrets, and verify no unauthorized messaging occurred.
Still not working? Contact ASG with the device name, carrier, GHL location, approximate timestamp, and the exact step that failed.