Security Overview

Last updated: 2026-02-17

Security is a priority for UseLocalGuide. This page summarizes how we protect the Service and what customers can do to keep accounts safe. This overview is informational and does not create contractual obligations beyond our published legal terms.

1. Encryption

• In transit: We use HTTPS/TLS to protect data between your browser and our servers.
• At rest: Sensitive values such as OAuth tokens are encrypted at rest.

2. Access Controls

• Role-based access controls and least-privilege access for administrative actions.
• Production access is limited to authorized personnel as needed for support and maintenance.
• Audit-style logging for critical actions (where available).

3. OAuth & Google Account Safety

When you connect Google, access is granted via OAuth and limited to the scopes you approve (for example, Business Profile management). You can disconnect at any time inside your dashboard and can revoke access in your Google Account Security settings.

4. Application Security

• Input validation and protection against common web vulnerabilities.
• Dependency management and security updates where feasible.
• Rate limiting and abuse prevention controls for sensitive endpoints.

5. Incident Response

We monitor for security events and respond to incidents. If we become aware of a confirmed security incident that materially affects your data, we will take reasonable steps to contain and remediate the issue and communicate as appropriate.

6. Shared Responsibility

• Use strong passwords and do not share credentials.
• Limit dashboard access to trusted team members.
• Review automation settings and approvals before publishing content.
• Revoke Google access if you suspect compromise.

7. Reporting Security Issues

If you believe you have found a security vulnerability, please contact support@uselocalguide.com with details. Please do not publicly disclose vulnerabilities until we have had a chance to investigate.

Also see: Privacy Policy • Security & Compliance