Data Processing Agreement
Effective Date: 1 January 2026 · Last Updated: 2 November 2026
This Data Processing Agreement ("DPA") forms part of the Terms of Service between NeuTarget ("Data Processor" or "NeuTarget") and the Customer ("Data Controller" or "you"). This DPA governs the processing of personal data by NeuTarget on behalf of the Customer in connection with the provision of the Service.
Important Note
This DPA covers customer-instructed processing of website and integration data, including pseudonymous visitor, session and declared customer identifiers. Such data can be Personal Data; it is not excluded merely because a direct name or email is absent. NeuTarget’s own account, billing and security processing is also described in the Privacy Policy.
1. Definitions
- "Applicable Data Protection Law" means the Digital Personal Data Protection Act, 2023 (India), the General Data Protection Regulation (EU) 2016/679 ("GDPR"), the California Consumer Privacy Act ("CCPA"), and any other data protection laws applicable to the processing of Personal Data under this DPA.
- "Personal Data" has the meaning given under Applicable Data Protection Law and refers to any data processed by NeuTarget on behalf of the Customer that relates to an identified or identifiable natural person.
- "Sub-processor" means a third party engaged by NeuTarget to process Personal Data on behalf of the Customer.
- "Data Breach" means a breach of security leading to the accidental or unlawful destruction, loss, alteration, unauthorised disclosure of, or access to, Personal Data.
- "SCCs" means the Standard Contractual Clauses for the transfer of personal data to third countries as adopted by the European Commission.
2. Scope & Roles
- The Customer is the Data Controller and determines the purposes and means of processing.
- NeuTarget is the Data Processor and processes Personal Data only on behalf of and in accordance with the documented instructions of the Customer.
- The subject matter of processing is the provision of web analytics services as described in the Terms of Service.
3. Categories of data processed
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.
- Website visitors and declared customer IDs: session and campaign context, timestamps, browser/device categories, geographic estimates, page paths, referrers and configured event/error information.
- Customer payment activity: provider/order/event references, amounts, currency, status, source evidence, delivery and optional session/customer context. Provider records can include additional fields depending on the integration.
- Customer personnel: account identity, contact, workspace membership, billing and security records. NeuTarget’s independent administration of these records is covered by its Privacy Policy.
Processing includes receipt, validation, storage, analysis, reporting, authorized delivery and deletion for the configured service. Its duration follows instructions, the applicable retention policy and lawful retention requirements.
5. Subprocessors and locations
Infrastructure, transactional delivery, payment and connected-platform providers depend on the deployment and integrations enabled for the customer. Request the current subprocessor, processing-location and transfer record from support@neutarget.com. A generic provider category or cloud certification is not proof that a particular production deployment uses that provider, region or control.
Authorization, notice, objection and replacement arrangements follow the applicable written processing agreement. NeuTarget remains responsible for the processing obligations it undertakes in that agreement; enabling an integration also requires the customer to assess the provider permissions and data flow.
6. Security controls and evidence
The product includes authentication, configured MFA/SSO, workspace and role checks, scoped credentials and lifecycle controls. Actual network boundaries, encryption coverage, access administration, operational logging, backup configuration and testing require deployment-specific evidence. The Security Policy distinguishes these facts; this DPA does not certify an unverified cloud, training program, audit, penetration test or recovery objective.
7. Incident notification
NeuTarget will handle personal-data incidents and provide the customer information required by the applicable processing agreement and law, including available details needed for the customer’s response. Requirements and deadlines depend on the incident, affected data and applicable provisions; this page does not assert that every jurisdiction has the same notification deadline.
8. Audits & Inspections
- The Customer (or an independent third-party auditor) may audit NeuTarget's compliance with this DPA once per year, with at least 30 days' written notice.
- NeuTarget shall provide reasonable cooperation, including access to relevant facilities, personnel, and documentation.
- Audits shall be conducted during normal business hours and shall not unreasonably disrupt NeuTarget's operations.
- If NeuTarget has obtained relevant certifications (e.g., SOC 2, ISO 27001), providing these reports may satisfy audit requirements.
9. Processing regions and transfers
Data locations and provider access are deployment-specific. The customer should obtain the current processing and transfer record and applicable safeguards before relying on a residency requirement. NeuTarget shall inform the customer if it becomes aware that applicable law prevents it from fulfilling the processing agreement. This page does not assert that all data remains in India or that a particular transfer instrument has already been executed for every provider.
10. Applicable collection requirements
Customers choose the purposes, data fields, lawful basis and visitor notices for their deployment. Where consent is required, control loading of the analytics script and enabled integrations through your consent flow. Using no analytics cookies does not by itself establish an exemption for browser storage, identifiers or subsequent personal-data processing.
Applicable requirements depend on the audience, jurisdiction and configuration. The European Commission explains personal and pseudonymised data, and Your Europe describes online privacy and cookie requirements. India’s 2025 DPDP Rules notification provides phased commencement; publication does not mean every provision took effect at once. This product does not assign a lawful basis or certify a customer’s compliance.
Where the customer acts as a data fiduciary/controller and NeuTarget as its processor, their documented responsibilities follow the processing arrangement and the provisions that apply to that activity. A published policy or a hashed identifier is not automatic compliance evidence.
11. Duration & Termination
- This DPA commences upon the Customer's acceptance of the Terms of Service and remains in effect for the duration of the Service agreement.
- Return/deletion requests follow documented instructions, applicable agreement and lawful retention requirements; subscription expiry and account erasure are separate processes.
- Sections relating to confidentiality, liability, and audit rights survive termination.
Never-paid expired trial websites follow the grace period configured for this deployment. Check the website lifecycle deadline in your dashboard. Collection stops when the relevant entitlement ends. Administrative pauses, holds or extensions can affect the displayed cleanup date; deletion runs asynchronously and may require retries.
Paid analytics follows the retention term assigned to the plan or written agreement. Paid history is separate from never-paid trial cleanup. Explicit deletion and account closure have their own scope. A user account can remain after trial website data is deleted. Deleted history is not restored by a later subscription.
NeuSignal delivery events and attempts follow the separately announced operational-history policy for this deployment. Pending and retrying records are preserved by terminal-history cleanup; applicable holds are honored. Provider delivery also has a separate bounded event-age window, so an older pending event can become ineligible for a new send. This policy does not shorten the separate paid analytics retention term.
Current public policy is loading. Configuration-specific deadlines remain in the website lifecycle view.
Account closure disables the account and starts an asynchronous erasure request for the workspaces explicitly confirmed for closure. Shared or transferred organizations are preserved. The private erasure receipt shows progress, retries and any pending provider cancellation or review; account disablement does not itself confirm an external recurring payment mandate was cancelled.
Website financial receipts follow website analytics retention. NeuTarget subscription invoices and other accounting or legally retained records follow a separate schedule; an erasure response can show a financial retention date. Operational logs and backups follow the deployed retention and deletion procedures, which can be requested from support. A cancelled subscription does not create a universal 30-day export or erasure window.
12. Contact
NeuTarget Team | support@neutarget.com
For a signed, countersigned copy of this DPA, email support@neutarget.com with your account details.
