Security & Data Practices

Last updated: September 12, 2026

Security approach

AvertSignal uses HTTPS and secure transport for its public service surfaces. Account access is protected through authentication, and responsibilities are separated across customer-facing, agency, and internal operating surfaces.

Connections and access

Customer-configured provider connections are handled through controlled service boundaries. Access is designed to be limited to the role and purpose needed to operate, support, and secure the service.

Payments

Payments are handled through payment providers using hosted payment experiences. AvertSignal does not ask customers to enter payment-card numbers into the public marketing site.

Data practices

We aim to use information needed to provide the service, investigate service issues, and protect accounts. Monitoring and incident handling are intended to distinguish available evidence from assumptions and to avoid presenting an unverified recovery as confirmed.

Service data, not a customer database

AvertSignal monitors supported system health, availability, configuration, performance, and operational signals. It is not designed to serve as a CRM, customer database, data warehouse, or duplicate repository for a business's customer lists, profiles, conversations, payment-card information, purchase histories, or files.

AvertSignal maintains account, configuration, monitoring-result, alert, integration-state, security, and operational information needed to provide the service.

Security contact

If you believe you have identified a security issue affecting AvertSignal, use the support method available to you through the service or the customer support channel shown on this site. Please do not include sensitive credentials in an ordinary support message.