Data Processing Agreement
This Data Processing Agreement ("DPA") forms part of the agreement under which Cruzetec Solutions, a partnership firm, Mohali (SAS Nagar), Punjab, India ("Provider"), provides Servertorch to the customer that accepted the Terms of Service ("Customer"). It applies to personal data the Provider processes on the Customer's behalf, and is written to satisfy section 8(2) of India's Digital Personal Data Protection Act, 2023 and Article 28 of the GDPR.
1. Roles
For visitor and security data collected from the Customer's monitored sites, and for personal data that appears in the Customer's code, files or pages that the service reads, the Customer is the Data Fiduciary (controller) and the Provider is the Data Processor. For account, billing and sign-in data, the Provider is an independent Data Fiduciary under its privacy notice.
2. Instructions
The Provider processes Customer personal data only on the Customer's documented instructions (the Terms, this DPA, and the configuration the Customer sets in the console: sites, agent collection settings, retention, IP masking, alert channels, AI analysis and the per-repository AI code check) unless the law requires otherwise, in which case it tells the Customer first where the law allows. The Provider will say if it believes an instruction infringes data-protection law.
3. Confidentiality
Everyone authorised to process Customer personal data is bound by confidentiality and accesses it only as needed to provide or support the service.
4. Security
The Provider maintains the technical and organisational measures in Annex 2 and keeps them appropriate to the risk.
4A. AI processing
AI analysis is off until an owner of the Customer switches it on in the console. Switching it on is the Customer's instruction to process the data described in the notice shown at that moment (recorded with its version): attack requests with the attacker's IP address, a daily sample of unusual requests without IP addresses, excerpts of flagged files, code findings and changed source files, public page text, DPDP report data and console summaries. The per-repository AI code check is on by default for plans that include it, but it runs only while AI analysis is on for the Customer, and the Customer can turn it off per repository at any time. Before anything is sent, the Provider masks secrets, email addresses, Indian mobile numbers, Aadhaar-like and PAN-like numbers and personal request parameters. The AI provider is a subprocessor (Annex 3) and does not use the data to train models under its commercial terms. When the Notice changes to add a kind of data, the new kind is not sent until an owner agrees again. Switching AI analysis off stops all further sending immediately.
Blocking rules written by the AI for an attack on one customer's site may be offered to other customers' sites on the same platform. Only the rule (a pattern, its category and a reason with the origin site's name, IP addresses and personal data removed) is shared. No Customer personal data is disclosed to another customer.
5. Subprocessors
The Customer authorises the subprocessors in Annex 3. The Provider gives at least 30 days' notice (email to company owners) of an addition or replacement; the Customer may object on reasonable data-protection grounds, and if no solution is found may terminate the affected service with a pro-rata refund. Each subprocessor is bound by obligations no less protective than these, and the Provider remains responsible for them.
6. Assisting the Customer
- Rights requests: the console lets the Customer find, export and delete visitor records and shorten retention; requests the Provider receives directly are forwarded to the Customer without delay.
- Breaches: the Provider notifies the Customer without undue delay and in any event within 24 hours of becoming aware of a personal-data breach affecting Customer data, with the nature, extent, timing and likely impact of the breach, the measures taken and a contact, and updates as they come, so the Customer can meet its own duty to inform the Data Protection Board and affected people (DPDP Rules r.7: without delay, detailed report within 72 hours).
- Logs: the service keeps raw traffic for a short window (Annex 1). Where the Customer must keep logs of its own processing for one year (DPDP Rules r.6 and r.8), it keeps its own server logs for that purpose; Servertorch is not the Customer's log of record.
- Assessments: reasonable help with data-protection impact assessments and consultations with authorities.
7. Deletion at the end
During the service the Customer can export its data from the console. On termination, or when the Customer deletes its company, all Customer personal data is erased after a 14-day grace period (and backups roll off on their own cycle), except where the law requires the Provider to keep something, such as tax invoices.
8. Demonstrating compliance
The Provider makes available the information needed to show compliance with this DPA (this page, the security page, and written answers to reasonable questionnaires) and allows an audit by the Customer or an auditor it appoints, at the Customer's cost, on 30 days' notice, no more than once a year unless a breach makes it necessary, under confidentiality and without access to other customers' data.
9. Transfers
Customer personal data is hosted by the Provider's hosting provider and transferred abroad only to the subprocessors in Annex 3 that are abroad. Transfers comply with DPDP s.16 (no transfer to a country the Government of India restricts) and, for data subject to the GDPR, rely on the EU Standard Contractual Clauses (Module 3, processor to processor) incorporated by reference.
10. General
Liability is as limited in the Terms. If this DPA and the Terms conflict on data protection, this DPA prevails. It is governed by the laws of India; the the courts at SAS Nagar (Mohali), Punjab have jurisdiction.
Annex 1: Processing
- Subject matter and duration: monitoring the Customer's websites and servers for as long as the service is provided.
- Nature and purpose: collection (by the guard, plugin or agent the Customer installs), storage, analysis (including AI analysis when switched on), blocking of attacks, display and alerting.
- Data subjects: visitors to the Customer's monitored sites; people who attempt to attack them; the Customer's site users where a username appears in a security event; people whose personal data appears in the Customer's code or public pages.
- Personal data: IP address (optionally masked in display), country and network, request time, method, path and query string, status, response size and time, referrer, user agent, a daily-rotating salted session key, usernames tried in failed logins, short excerpts of malicious input; for code audit and AI checks, masked lines of source code and public page text.
- Special categories: none intended. The Customer must not configure the service to collect them.
- Retention: traffic 14 days, security events 90 days, or shorter as the Customer sets; IP network lookups 90 days; AI site reviews 365 days; code scans 180 days. Data sent to the AI provider is kept by it only as its commercial terms allow and is not used for training.
Annex 2: Security measures
- TLS 1.2+ for all traffic with HSTS; agent requests HMAC-signed with replay protection; signed agent updates.
- Encryption at rest for secrets (agent secrets, 2FA seeds, repository tokens, webhook addresses); passwords bcrypt-hashed; API tokens stored as hashes.
- Tenant isolation enforced per request and by authorisation policies; four-role access model; two-factor authentication and passkeys; password confirmation for sensitive actions.
- Rate limiting and account lockout; security-event logging with alerting; audit log of administrative actions kept one year.
- Strict browser security headers (CSP with nonces, frame-ancestors none, HSTS); outbound requests to customer-supplied addresses resolved, vetted and pinned against SSRF.
- Masking of secrets and personal data before anything is sent to the AI provider.
- Automated retention enforcement; documented breach-response procedure with a breach register and a 72-hour clock.
- Dependency auditing in the release process; least-privilege service accounts; production secrets outside the code repository.
Annex 3: Subprocessors
- Hostinger International Ltd. (VPS data-centre region as provisioned): Hosting of the platform (virtual private server, database, backups) and outgoing email through the SMTP service of the same account. Always.
- Anthropic, PBC (United States): The AI used by the product: reading attacks and writing virtual patches, the daily review of unusual traffic, explaining findings, the AI code check, the AI site review, the AI DPDP assessment, and the console assistant. Only for companies whose owner switched AI analysis on (off by default). The public readiness check at /check never uses AI.
- Razorpay Software Private Limited (India): Payment collection for invoices (cards, UPI, netbanking). When an invoice is paid online. Razorpay's checkout script loads only when you press Pay.
- Team Cymru Inc.; regional Internet registries via rdap.org (United States / registries worldwide): Looking up which network an IP address belongs to (attack attribution, CDN and origin detection). For addresses that appear in security events or traffic on agent-monitored sites.
Signatures
Accepting the Terms of Service accepts this DPA. Customers who need a countersigned copy can sign the download and email it to privacy@dxcslabs.com.
Customer: ______________________ Name / title: ______________________ Date: __________
Provider (Cruzetec Solutions): ______________________ Name / title: ______________________ signatory to be confirmed Date: __________