AdSignalIQ Security Overview

AdSignalIQ uses a layered security approach intended to reduce risk across the public website, authenticated application, network edge, application services, integrations, and customer data.

Encrypted HTTPS connections are used for traffic to the AdSignalIQ website and application; the AdSignalIQ domain is proxied through Cloudflare for edge security and traffic protection; Cloudflare SSL/TLS is configured in Full (strict) mode so encrypted connections are validated between Cloudflare and the origin; the AdSignalIQ application is hosted using managed cloud infrastructure, including Netlify for the current web application deployment; security rules are used at the network edge to help identify or block common malicious requests and automated abuse; and dynamic and customer-specific application content is intended to bypass shared edge caching so authenticated customer information is not served as public cached content.

Encryption in Transit: AdSignalIQ uses HTTPS/TLS to protect information transmitted between users and the Services. The current public application is configured to use Cloudflare with Full (strict) TLS validation and a valid origin certificate.

Sensitive Credentials: sensitive service credentials, private API keys, access tokens, and payment secrets should be maintained in protected server-side configuration or environment variables and should not be exposed in browser-delivered code. AdSignalIQ's integration architecture is designed around server-side handling of sensitive credentials where applicable.

AdSignalIQ is designed around authenticated customer accounts and organization or workspace-level access. Access to customer-specific functionality should require appropriate authentication and authorization.

Authentication endpoints are protected with edge rate limiting to reduce automated abuse and brute-force activity; suspicious authentication traffic may be subject to Cloudflare security challenges; customer access is intended to be scoped to the appropriate organization or workspace; administrative and privileged functionality should be restricted to authorized users; and invited users should receive access based on their assigned organization and role rather than receiving independent access to another customer's data.

AdSignalIQ is a multi-tenant SaaS platform. Customer information should be logically separated by organization or workspace, and application authorization controls should prevent one customer from accessing another customer's data.

Tenant isolation is a critical application requirement. Authorization checks should be enforced on the server side and should not rely solely on hidden interface elements or client-side state.

AdSignalIQ currently uses Cloudflare in front of its public domain. Edge protections include controls intended to reduce common automated attacks and malicious scanning: Cloudflare proxy protection for the public domain; Full (strict) TLS between Cloudflare and the origin; rate limiting for authentication-related traffic; blocking of common exploit-probing paths that are not part of the AdSignalIQ application, such as exposed environment files, Git metadata, WordPress administration paths, XML-RPC paths, and phpMyAdmin probes; Managed Challenge capability for suspicious authentication traffic; and modern transport protocols and HTTPS enforcement where configured.

Security rules are intentionally designed to avoid interfering with legitimate machine-to-machine traffic such as payment webhooks, OAuth callbacks, and authorized advertising or CRM integrations.

AdSignalIQ's application security model is intended to include: server-side authorization for protected application and API resources; validation of incoming requests and parameters; secure handling of OAuth authorization flows and callback routes; protection of integration credentials and refresh tokens; verification of webhook authenticity where supported by the sending provider; idempotent processing of payment and integration events where duplicate delivery is possible; appropriate cache controls for authenticated, private, billing, API, webhook, and integration-related content; and logging and diagnostic information to support troubleshooting and security investigation.

AdSignalIQ is designed to connect to advertising, analytics, CRM, call-tracking, and related business platforms. Connections should use provider-supported authentication methods, such as OAuth, where available.

Access to third-party data is limited by the permissions granted by the customer and the capabilities of the connected provider. Customers can control which supported accounts and data sources they choose to connect. Third-party platforms maintain their own security and privacy practices, which are outside AdSignalIQ's direct control.

AdSignalIQ uses a third-party payment processor for subscription and payment processing. Payment card information should be collected and processed through the payment provider's secure payment infrastructure rather than stored directly by AdSignalIQ.

AdSignalIQ may retain payment-related metadata necessary to administer subscriptions, such as customer identifiers, subscription identifiers, payment status, card brand, last four digits, and billing dates. Full card numbers and card security codes should not be stored in AdSignalIQ application databases.

AdSignalIQ may use artificial intelligence and automated processing to analyze customer-authorized data and generate insights, summaries, recommendations, alerts, or other outputs.

Customer data provided for analysis should be transmitted to service providers only as necessary to provide configured functionality and subject to applicable contractual and security controls. Unless expressly agreed otherwise in writing, AdSignalIQ does not use Customer Data to train general-purpose AI models for the benefit of unrelated customers.

AI-generated outputs should be treated as decision-support information and reviewed by an appropriate person before material business actions are taken.

AdSignalIQ may maintain operational, authentication, integration, error, performance, and security logs to help operate and protect the Services. These records may be used to detect suspicious behavior, investigate incidents, troubleshoot errors, monitor system health, and enforce applicable terms.

Controls may include rate limiting, request filtering, security challenges, automated alerting, and other technical measures appropriate to the threat and the affected service.

AdSignalIQ is designed to use managed cloud infrastructure and service providers that support scalable and resilient operation. The platform's architecture should minimize synchronous dependence on advertising-platform APIs for normal dashboard loading by using synchronized data, background processing, and appropriate caching where implemented.

No online service can guarantee uninterrupted availability. AdSignalIQ may experience downtime caused by maintenance, software defects, third-party provider outages, network events, security incidents, or other circumstances.

AdSignalIQ's development practices are intended to reduce the risk of introducing security vulnerabilities into production. Depending on the component and stage of development, practices may include code review, automated testing, dependency management, environment separation, controlled deployment, rollback capability, secret management, and security-focused review of sensitive changes.

Security-sensitive areas include authentication, authorization, tenant isolation, billing, webhooks, OAuth integrations, administrative functions, data exports, and AI or automation features.

Security issues identified through internal review, automated tooling, service-provider notifications, customer reports, or other sources are evaluated based on severity and potential impact. AdSignalIQ intends to prioritize remediation of material security vulnerabilities according to risk.

Customers or security researchers who believe they have identified a security issue should report it privately and should not attempt to access, modify, destroy, or exfiltrate data belonging to other customers.

If AdSignalIQ becomes aware of a suspected security incident, we intend to investigate the event, contain and remediate identified risks, preserve relevant information as appropriate, and assess whether customer or regulatory notification is required.

Where applicable law or contractual commitments require notification of a qualifying data breach or security incident, AdSignalIQ will provide notice in accordance with those requirements.

AdSignalIQ retains information according to operational needs, customer agreements, security requirements, backup practices, and applicable law. Following account termination or expiration, customer information may be deleted or de-identified according to applicable retention practices and contractual commitments.

Backups and disaster-recovery copies may persist for a limited period after information is removed from active systems.

AdSignalIQ is not intended to receive protected health information (PHI) through ordinary product features unless AdSignalIQ and the applicable customer have entered into any required Business Associate Agreement (BAA) and the relevant functionality or environment has been expressly designated for that use.

Customers should not connect, upload, map, or transmit PHI or patient clinical information to AdSignalIQ unless applicable contractual and technical requirements have been satisfied. Additional security and compliance controls may apply to any future HIPAA-enabled functionality.

Security is a shared responsibility. Customers are responsible for: protecting user credentials and maintaining appropriate account access; removing access when personnel no longer require it; connecting only systems and data they are authorized to use; configuring third-party integrations and permissions appropriately; avoiding unnecessary submission of sensitive or regulated information; reviewing AI-generated recommendations and automated outputs before taking material actions; and promptly reporting suspected unauthorized access or security issues.

AdSignalIQ does not claim a security certification, audit, or regulatory compliance status unless that status has been formally achieved and is expressly identified by AdSignalIQ in writing. This Security Overview should not be interpreted as a representation that AdSignalIQ is currently certified under SOC 2, ISO 27001, PCI DSS, HIPAA, or another security or compliance framework.

As AdSignalIQ grows, its security program, documentation, controls, vendor management, testing, and independent assurance activities may evolve.

If you believe you have discovered a vulnerability, unauthorized access, or other security issue involving AdSignalIQ, please contact us privately:

AdSignalIQ LLC

Security contact: [email protected]

Website: adsignaliq.com

Please include enough information for us to understand and reproduce the issue. Do not include passwords, full payment-card information, PHI, or unnecessary personal information in an ordinary email.

AdSignalIQ may update this Security Overview as its infrastructure, product architecture, integrations, security controls, and compliance program evolve. The date at the top of this document indicates the most recent revision.