Security

Built to be accountable.

This overview describes how AdHelm approaches access control, data handling, and operational safeguards. It is intended to build practical confidence for both buyers and platform reviewers.

OAuth access

Google Ads access is granted via OAuth. AdHelm does not ask for your Google password.

Tenant isolation

Data is scoped per tenant and access is enforced server-side, reducing the risk of cross-account exposure.

Auditability

Optimization actions are logged, and supported changes can be rolled back. This creates accountability and control.

Operational safeguards

Least-privilege access: request only what is needed for the workflow you enable.
Guardrails and run caps: limits on the volume and magnitude of changes per run.
Explainability: recommendations include reasoning so teams can review before acting.
Rollback metadata: supported changes capture previous state to enable undo.
Notifications: pacing alerts and weekly reporting reduce “silent drift” risk.

Data expectations

AdHelm is designed for marketing performance signals. Do not submit protected health information (PHI) or medical records into the product. If you have special requirements, contact us and we can review the right approach.

Data is transmitted over TLS and stored with access controls designed for tenant isolation. We maintain logs around changes and access to support auditability.

HIPAA posture

AdHelm is not positioned as a HIPAA clinical system. It is designed for ads and operational growth workflows. Do not input PHI (symptoms, diagnoses, treatment history, test results, or clinical notes). If your organization requires a BAA or HIPAA-specific controls, contact us prior to use so we can confirm the right setup.

Questions or security concerns: support@ad-helm.com