NeuTargetNeuTarget/Legal
Back to Home

Security Policy

Last updated: 14 November 2026

1. Product controls and their scope

NeuTarget includes password and session authentication, configured multi-factor and organization SSO flows, workspace membership and role checks, scoped internal endpoints, and server-only financial integration credentials. These controls reduce specific risks; they do not establish that every deployment or customer configuration is secure or compliant.

  • Pending MFA tokens are isolated from full access and are limited to completing the configured challenge.
  • Organization SSO uses browser-bound, one-use handoff codes; changing identity or workspace requires the applicable live access checks.
  • Website credentials are available to authorized integration operators and must remain on the customer backend. Browser revenue calls do not authenticate a payment.
  • Lifecycle controls can stop collection, preserve paid history from ordinary trial cleanup, and track asynchronous erasure status.

2. Data minimization and identifiers

The analytics server processes IP addresses and User-Agent information for request handling, geographic enrichment, and approximate weekly network/browser groups. Raw IP is not a field in the analytics event table, but operational access and security logs may retain it. These network groups are not verified people.

The current browser SDK first requests the site collection and privacy policy. If consent is required, it waits for the customer’s consent flow to grant collection; denying or withdrawing consent clears its session context and stops further tracking writes. Once collection is allowed, it uses a random per-tab session nonce, with a 30-minute inactivity window, and sessionStorage for session and campaign context. Storage restrictions or older tags can reduce continuity. Optional site-scoped customer digests can link declared customer activity across sessions; a 64-character hash is pseudonymous data and can remain personal data.

New websites default to minimal mode, which drops optional declared customer and advertising identifiers, diagnostic error details and precise city/region. Existing websites retain a labelled legacy mode until an admin reviews it; identified mode requires an explicit processing-instructions acknowledgement. Server controls strip URL queries/fragments, reduce referrers to origins, bound text and redact common sensitive patterns, but cannot detect every form of personal information. Paths, UTM values, referrers, click destinations, custom-event fields and error text can still contain customer information if your application puts it there. Keep names, emails, payment credentials, account tokens and sensitive information out of those fields. Hashing identifiers does not remove the need to control collection and access.

Minimize identifiers and event content at the source. Customer-defined paths, errors, identifiers and provider records need appropriate handling; hashing is not a substitute for access control, retention or lawful collection.

3. Deployment evidence

Hosting regions, network boundaries, encryption of database volumes, key management, access logging and provider configuration depend on the deployment. Request the current infrastructure, subprocessor and processing-region record for an assessment. This page does not assert a particular cloud, region, WAF, managed-key service or multi-zone production setup.

The code includes protected integration-secret storage and HTTPS-oriented public endpoints. Those implementation capabilities are separate from proof that all storage, backups and internal network paths use a particular encryption standard in production.

4. Logs, backup and recovery

Operational and security logs may contain request metadata, including IP addresses. Operators must configure access, redaction, retention, backup storage and restoration procedures for the deployed system. Request the current record; no fixed log lifetime, continuously monitored service level, recovery-time or recovery-point objective is asserted here.

Backup and restore tooling is a capability, not evidence of a provisioned backup destination, completed production restore drill, or achieved disaster-recovery objective.

5. Security review and incidents

Security reports are assessed and handled according to their impact, the applicable agreement and legal requirements. Current dependency checks, vulnerability remediation, audit evidence and incident procedures should be requested for the deployment being reviewed. This page does not claim an annual independent penetration test, a certification, or a measured patch/notification service level.

6. Reporting a concern

Use support@neutarget.com to report a security concern with reproducible steps and the affected component. Avoid sending credentials, private erasure tokens or other customer data. Do not access or modify another customer’s data or disrupt the service while investigating. Coordinate further disclosure with the support team.

7. Privacy and contractual records

The Privacy Policy explains collection and retention. The DPA describes processing responsibilities. A cloud provider’s certifications do not certify NeuTarget; request current, applicable assurance records rather than relying on a badge or generic compliance claim.