Privacy Policy
Effective Date: 1 January 2026 · Last Updated: 21 April 2026
NeuTarget ("NeuTarget," "we," "us," or "our"), operates the website and analytics platform available at www.neutarget.com, along with related communications and contracted professional services (collectively, the "Service"). This Privacy Policy explains how we collect, use, disclose, and safeguard information when you visit our website, use our Service, or contact us about our products or services.
NeuTarget processes account information and website analytics, including pseudonymous session and customer identifiers where configured. This policy describes those data flows, their purposes, customer choices, retention and request mechanisms.
1. Definitions
- "Customer" - an individual or entity that creates an account on NeuTarget to track analytics for their website(s).
- "Prospect" - an individual who contacts NeuTarget to learn about our products, pricing, or professional services.
- "End-Visitor" - a person who visits a Customer's website where the NeuTarget tracking script is installed.
- "Personal Data" - any information relating to an identified or identifiable natural person, as defined under the Digital Personal Data Protection Act, 2023 (India), GDPR (EU), or applicable law.
- "Processing" - any operation performed on Personal Data, including collection, storage, retrieval, use, disclosure, or erasure.
2. Data We Collect from Customers (Account Holders)
When you create an account or use the Service, we may collect:
| Data Category | Examples | Purpose |
|---|---|---|
| Account Details | Full name, email address, company name, phone number | Account creation, authentication, communication |
| Billing Information | Company name, tax identifiers, billing address (payment details are processed by the applicable payment provider and never stored by us in full) | Invoicing, tax compliance, payment support |
| Website Data | Domain names you register | Providing the analytics Service |
| Usage Data | Login timestamps, feature usage, support interactions | Service improvement, support |
| Ad Integration Data | Connected Google Ads or Meta Ads account metadata, campaign IDs, campaign names, spend, clicks, impressions, mapping status, and encrypted authorization credentials/tokens where applicable | Ad spend sync, paid acquisition reconciliation, campaign mapping, confirmed ROAS reporting |
| Communication Data | Emails, WhatsApp briefing preferences, phone number for briefings | Delivering daily briefings, support |
| Sales and Services Inquiry Data | Contact form submissions, company details, reasons for reaching out, project requirements, budget or timeline context, and meeting notes | Responding to inquiries, qualification, proposals, and follow-up |
| Service Delivery Data | Project briefs, technical contacts, repository or environment access details, implementation requirements, support threads, and deliverable feedback | Delivering contracted professional services, onboarding, troubleshooting, and security |
3. Website analytics and integration data
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.
Analytics may include timestamps, page and campaign context, device/browser categories, geographic estimates, engagement metrics and observed custom events. Financial integrations process order/event references, exact amounts and currency, delivery status and optional attribution context. Signed provider records can contain additional fields before processing; review the enabled integration’s data flow rather than assuming every record is anonymous.
4. Roles and collection choices
NeuTarget uses account, billing and security information to operate its service. Customers instruct processing of their website analytics and determine its purposes. Contract administration, legal requirements and permitted security or operational purposes can apply to NeuTarget’s own records; they do not establish a blanket lawful basis for every customer’s tracking.
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.
5. How We Use Your Data
- To create and manage your NeuTarget account.
- To provide, maintain, and improve the analytics Service.
- To connect third-party advertising accounts you authorize, import campaign-level spend, and reconcile paid acquisition spend with your NeuTarget attribution and confirmed revenue data.
- To deliver WhatsApp daily briefings (if enabled).
- To process subscriptions and payments through the applicable payment processor.
- To send transactional emails (verification, password reset, billing receipts).
- To respond to product, partnership, and professional services inquiries.
- To prepare proposals, statements of work, onboarding materials, and related commercial records.
- To deliver implementation, integration, advisory, engineering, architecture, audit, or other contracted professional services.
- To respond to support requests and communicate about the Service.
- To detect, prevent, and address fraud, abuse, and technical issues.
- To comply with legal obligations and enforce our terms.
5A. Ad Account Sync
If you connect Google Ads, Meta Ads, or another supported advertising account through NeuTarget, we process the minimum account and campaign information needed to provide ad spend sync and reconciliation features. This may include ad account identifiers, account names, campaign identifiers, campaign names, spend, clicks, impressions, mapping status, and encrypted authorization credentials or tokens.
We use this data only to sync campaign-level reporting data into NeuTarget, reconcile paid acquisition spend with your UTM campaigns, and improve confirmed ROAS and revenue intelligence reporting. NeuTarget does not use this access to create campaigns, edit campaigns, manage bids, manage creatives, or otherwise operate your advertising accounts.
You can disconnect an advertising account at any time from your NeuTarget dashboard. Disconnecting stops future sync activity, although previously imported reporting data may remain in your account history unless deleted through the product or required by law.
5B. Sales Inquiries & Professional Services
If you contact us about implementation, engineering, architecture, marketing technology, audit, or other professional services, we may process the information you share to scope the engagement, prepare proposals, deliver the agreed work, manage project communication, and protect the security of any systems or environments you ask us to review or support.
Where a professional services engagement involves Customer-provided materials or Personal Data, we will process that information only as reasonably necessary to deliver the contracted work and in accordance with applicable law, our contractual commitments, and our DPA where applicable.
6. Data Sharing & Third Parties
We do not sell, rent, or trade your Personal Data. We share data only with:
- Payment Processor(s): To process subscription payments or other authorized charges. The applicable payment provider's privacy policy governs payment data it processes.
- Hosting and operational providers: Infrastructure providers and processing regions depend on the deployed service and enabled integrations. Request the current subprocessor and region record before relying on a residency requirement.
- Email Delivery Service: Configured delivery providers process recipient addresses, message content and delivery information needed to send transactional communications.
- WhatsApp Business API: If you enable daily briefings, your phone number is shared with the WhatsApp Business API provider solely for message delivery.
- Authorized Service Providers and Contractors: Where reasonably necessary, we may share limited data with vendors, subprocessors, or contractors who help us operate the Service or deliver contracted professional services, subject to confidentiality and data protection obligations.
- Connected Ad Platforms: If you choose to connect Google Ads or Meta Ads, NeuTarget receives account and campaign reporting data from those platforms under the permissions you authorize. Their own privacy terms also apply to your use of those services.
- Legal & Regulatory: When we are legally compelled to disclose data by an Indian court, the Data Protection Board of India, or other competent authority.
7. Retention, expiry and erasure
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.
Contact, sales and professional-services records are kept for the purposes of the interaction, service, security, accounting or dispute handling, subject to applicable requirements. Ask support for the current retention record and deletion process for a particular category.
8. Your Rights
Depending on your jurisdiction, you may have the following rights:
| Right | DPDP Act (India) | GDPR (EU/EEA) | CCPA (California) |
|---|---|---|---|
| Access your data | ✓ | ✓ | ✓ |
| Correct inaccurate data | ✓ | ✓ | ✓ |
| Erase / delete your data | ✓ | ✓ | ✓ |
| Data portability | - | ✓ | - |
| Object to processing | - | ✓ | - |
| Withdraw consent | ✓ | ✓ | - |
| Non-discrimination | - | - | ✓ |
To exercise any of these rights, email us at support@neutarget.com. We will respond within 30 days (or sooner where required by law). For DPDP Act requests, you may also contact the Data Protection Board of India if unsatisfied with our response.
9. International Data Transfers
Hosting locations, support access and processing by connected providers are deployment-specific. We do not represent that every copy or provider operation remains in a single country. Request the current subprocessor, processing-region and transfer-safeguard record for your deployment and agreement before making a residency or transfer assessment.
10. Children's Privacy
The Service is not directed to individuals under 18 years of age. We do not knowingly collect Personal Data from children. If you become aware that a child has provided us with Personal Data, please contact us at support@neutarget.com and we will take steps to delete such information.
11. Security Measures
The Service includes authentication, workspace and role checks, scoped integration credentials and lifecycle controls. Deployed encryption, log handling, backups and external assurance depend on the current operational setup. See the Security Policy for the distinction between product controls and deployment evidence.
12. Changes to This Policy
We may update this Privacy Policy from time to time. Material changes will be notified via email to registered Customers at least 15 days before they take effect. Continued use of the Service after the effective date constitutes acceptance of the updated policy. The "Last Updated" date at the top reflects the most recent revision.
13. Privacy requests and grievances
Use the existing support contact for privacy questions and grievances. Request the current designated contact and handling process where your applicable requirements call for one.
NeuTarget Team | support@neutarget.com
We will provide the applicable request process and status; this page does not assert an independently verified response-time guarantee.
14. Contact Us
For any questions about this Privacy Policy or our data practices, contact us at:
NeuTarget Team | support@neutarget.com
Website: https://www.neutarget.com
