Privacy notice
This notice explains what Servertorch does with personal data: what we collect, why, on what legal basis, who else sees it, how long we keep it, and how you can see, correct, erase or complain about it. It is written to meet India's Digital Personal Data Protection Act, 2023 and the Digital Personal Data Protection Rules, 2025 and, for people in the European Union and the United Kingdom, the GDPR.
This notice is in English. You can ask for it in Hindi, Punjabi or any other of the 22 languages in the Eighth Schedule to the Constitution of India: write to privacy@dxcslabs.com or use the request form and choose "The privacy notice in another Indian language". We send the translation within 30 days.
- We collect what is needed to run the monitoring you asked for and to keep the service secure. No advertising, no data sales, no trackers on this website.
- Data about your website's visitors is collected on your instruction. For that data you decide and we act as your processor.
- Every kind of record has a retention period and is deleted automatically by a nightly job.
- Optional uses (product news and AI analysis) are off unless you turn them on, and off again in one click.
- Download, correct or delete your data yourself from Settings, Privacy & data, or send us a request.
1. Who we are
Servertorch is operated by Cruzetec Solutions, a partnership firm based in Mohali (SAS Nagar), Punjab, India, trading as DxCS Labs. For the data described in section 2 we are the Data Fiduciary (DPDP) and controller (GDPR). For the visitor data described in section 3 we are a Data Processor acting for our customer.
- Questions about how we process personal data (DPDP Rules r.9): privacy@dxcslabs.com
- Grievance Officer: Grievance Officerto be confirmed, grievance@dxcslabs.com
- EU/UK representative (GDPR Art. 27): not appointed. We do not target the EU/UK market; write to the privacy address above
2. What we collect, why, and on what basis
| Data | Why | Legal basis |
|---|---|---|
| Account and team: name, email, role, timezone, notification choices; a hash of your password (never the password); two-factor secrets (encrypted) and passkey public keys; that you confirmed you are 18 or older and accepted the terms | To give you an account and run the service your company signed up for | DPDP s.7(a), provided by you for this purpose; GDPR 6(1)(b) contract |
| Sign-in and security records: time, IP address, browser, sign-in method, failed attempts, refused requests; an audit log of changes made in the console | To protect accounts, detect misuse and investigate incidents | DPDP s.8(5) security safeguards and Rules r.6 (logs kept one year); GDPR 6(1)(c) and (f) legitimate interest in security |
| Billing: billing contact name, email and phone, company name and address, GSTIN, PAN where you give it for TDS, invoices, credit notes, payments and payment reminders we emailed. Online payments go through Razorpay; we never see card, UPI or bank details | To invoice, collect payment, remind you of due invoices, and meet GST and income-tax law | DPDP s.7(a) and s.7(b) (legal obligation under the CGST Act and Income-tax Act); GDPR 6(1)(b) and (c) |
| Demo requests: name, work email, phone (optional), company, role, industry, team size, websites and how many, hosting, who manages them, code host and number of repositories, what you want to see, timeline, preferred contact and time, how you heard of us; the IP address and browser the form was sent from; the box you ticked, its wording and when | To arrange and run the demo you asked for, prepare it for your sites, and stop form abuse | DPDP s.6 consent, given by ticking the box on the form; GDPR 6(1)(b) steps before a contract, 6(1)(f) for abuse prevention |
| Readiness check (/check): the website address you type. Your IP address is used only to limit how often checks can be run and is not stored with the result | To run the free check and show you the result | DPDP s.7(a), provided by you for this purpose; GDPR 6(1)(f). The result is kept for one hour, then discarded. The check does not use AI |
| Code audit (customers who connect a repository): a read-only access token; a temporary copy of the repository, deleted when each scan ends; findings with a few lines of code around each, with secrets and personal data masked | To run the code scans you switched on and show you what they found | DPDP s.7(a), provided by you for this purpose; GDPR 6(1)(b) contract. Where the code contains personal data, we process it as your processor under the DPA |
| Browser notifications (only if you turn them on): the push address and keys your browser gives us | To send alerts to your browser | DPDP s.7(a); GDPR 6(1)(b). Remove it by turning notifications off or deleting your account |
| Rights requests and grievances: what you send us and our reply | To answer you and to show that we did | Legal obligation (DPDP s.8(10), s.13; GDPR 6(1)(c)) |
| Public-site statistics: which page or step was reached, the name of the form field where someone stopped (never what was typed), referring site name, campaign tags, device type, the first three parts of the IP address, and a visitor code that changes every day | To see where the website loses people, and to stop scrapers | Legitimate interest (GDPR 6(1)(f)). No cookies, no profile and not linkable across days, so no one can be identified from it |
| Monitoring data about your sites: availability checks, certificates, DNS, headers, server metrics, software inventory, file hashes | The service itself | Contract; mostly not personal data |
| Optional: product news | Occasional product news by email | Consent. Off by default; withdraw in Settings, Privacy & data |
| Optional: AI analysis. When a company owner switches it on, the AI receives: attack requests seen on your sites with the attacker's IP address (to propose a block); once a day, a sample of unusual requests that no rule caught (request line and browser only, no IP addresses); excerpts of suspicious files; code findings and the changed source files most worth reviewing; the text of your public pages; your DPDP report; console summaries; questions typed to the assistant. Secrets, email addresses, phone numbers and ID numbers are masked before anything is sent | Reading attacks and writing narrow blocking rules, the daily review of unusual traffic, the AI code check, the AI site review, the AI DPDP assessment, and the assistant | Consent of the company owner, recorded with the exact notice shown. Off by default; switching it off stops all further sending. Each repository's AI code check can also be turned off on its own |
We do not make decisions with legal or similarly significant effects about anyone by automated means, and we do not build advertising profiles. What the AI suggests is shown to you; blocking rules it writes are tested against your site's normal traffic first, expire on their own, and are applied automatically only if you chose that.
3. Your website's visitors (we are your processor)
When you connect a site with the Servertorch guard, plugin or agent, it reports each request to that site: time, IP address, country, method, path and query string, status, response size and time, referrer and user agent. Security events add the rule that fired and a short excerpt of the suspicious input. This is personal data about your visitors, collected because you asked us to, and you are its Data Fiduciary or controller. Our Data Processing Agreement governs it.
- A visitor session key is a salted hash of IP, browser and date computed on your server. The salt never leaves it, so the key cannot be reversed and does not link a visitor across days or sites.
- You can turn on Mask visitor IPs for your company so the last part of each address is hidden in the console.
- Raw traffic is kept 14 days and security events 90 days, or less if your company sets a shorter window.
- If AI analysis is on, attack requests and a daily sample of unusual requests go to the AI as described in section 2, with personal data masked and, for the daily sample, without IP addresses.
- When the AI writes a blocking rule for an attack on your site, the rule (a pattern, never your visitors' data) may be offered to other customers' sites on the same platform. Nothing that identifies your site or your visitors goes with it.
- The guard and agent never send database contents or credentials. File contents leave your server only as short excerpts of files flagged as suspicious.
If you visited a site monitored by Servertorch and want to exercise your rights, contact that site's owner. If you write to us, we pass your request to them without delay and tell you we have.
4. Who else sees it
We do not sell personal data. These providers process it for us, under contract, only to provide their service:
| Provider | What for | Where |
|---|---|---|
| Hostinger Hostinger International Ltd. |
Hosting of the platform (virtual private server, database, backups) and outgoing email through the SMTP service of the same account. Always. | VPS data-centre region as provisioned |
| Anthropic Anthropic, PBC |
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. | United States |
| Razorpay Razorpay Software Private Limited |
Payment collection for invoices (cards, UPI, netbanking). When an invoice is paid online. Razorpay's checkout script loads only when you press Pay. | India |
| Team Cymru / RDAP registries Team Cymru Inc.; regional Internet registries via rdap.org |
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. | United States / registries worldwide |
Details, including what data each receives, are on the subprocessors page. Alerts go to the Slack, Teams, Telegram or webhook destinations you configure. We disclose data to authorities only where the law requires it.
5. Transfers outside India
The platform is hosted on our provider's servers. Data leaves India only where a provider in section 4 is abroad: AI analysis (United States, and only when your company's owner switched it on) and IP-address network lookups. Under DPDP s.16 such transfers are allowed except to countries the Government of India restricts by notification; we will stop any transfer to a restricted country. For people in the EU/UK, transfers rely on the providers' Standard Contractual Clauses (GDPR Art. 46).
6. How long we keep it
| Record | Kept for |
|---|---|
| Account and team data | While the account exists. Erased when you delete your account (immediately) or your company (after a 14-day grace period, with an email to every owner first) |
| Sign-in history | 365 days |
| Server application and security logs | 400 days, so an incident can be investigated for at least a year (DPDP Rules r.6) |
| Console audit log | 365 days |
| Consent records | While the company exists, as proof of what was agreed; erased with the company |
| In-app notifications | 90 days |
| Mail delivery log | 90 days |
| Demo requests that did not become customers | 365 days |
| Readiness check results (/check) | 1 hour |
| Public-site statistics / rate counters | 90 / 14 days |
| Visitor traffic / security events (section 3) | 14 / 90 days, or shorter per company |
| Network lookups for IP addresses | 90 days |
| AI site reviews and daily AI traffic reviews | 365 days |
| Code scans | 180 days; findings stay while the repository is connected |
| Rights requests and grievances | 3 years after they are closed |
| Data-export download files | 48 hours |
| Payment reminders sent | 3 years |
| Tax invoices and credit notes | 8 years (Indian tax law), even after the company is deleted, with the billing details on them only |
| Deleted sites | 30 days, then all their data is erased |
Backups roll over on their own cycle; erased data disappears from them when they expire. We do not delete an active customer's account for inactivity. If that ever changes, we will email you at least 48 hours before anything is erased, as the DPDP Rules require for the platforms they name.
7. How we protect it
TLS everywhere with HSTS; passwords hashed with bcrypt and API tokens stored only as hashes; two-factor secrets, agent secrets, repository tokens and webhook addresses encrypted at rest; two-factor authentication and passkeys; role-based access with per-company isolation; rate limits and lockouts on sign-in; security events logged and alerted; strict browser security headers; database backups. Our security page has more, including how to report a vulnerability.
If a personal-data breach happens, we inform the Data Protection Board of India and the people affected without delay, and send the Board a detailed report within 72 hours (DPDP Rules r.7). The notice to you says what happened, when, what it may mean for you, what we are doing about it, what you can do, and who to contact. Customers are told within 24 hours about anything affecting their visitors' data.
8. Your rights, and how to use them
- Access: a summary and a full copy of your data from Settings, Privacy & data, Email me a download link (machine-readable JSON, which also serves portability). The summary also lists who we shared it with (section 4).
- Correction, completion and updating: your profile is editable in Settings; ask us for anything else.
- Erasure: delete your account, or (owners) your whole company, from Settings, Privacy & data.
- Withdraw consent: the same switches that gave it, one click each. Withdrawal does not affect what was done before.
- Objection and restriction (GDPR): send a request.
- Nomination: name someone to act for you if you die or become unable to (DPDP s.14) in Settings, Privacy & data, Nominee.
- Grievance redressal: write to our Grievance Officer.
Anyone can use the request form, with or without an account. We answer requests within 30 days and grievances within 30 days, well inside the 90 days the DPDP Rules allow. We may need to confirm it is you first. If you are not satisfied with our answer, you may complain to the Data Protection Board of India, or, in the EU/UK, to your data protection authority.
9. Children
Servertorch is a service for businesses. Accounts are for people aged 18 or over, acting for their organisation, and everyone confirms this when they join. We do not knowingly process personal data of children and do not collect parental consent because we do not offer the service to children. If we learn an account belongs to a child, we close it and erase its data. Customers whose own sites are used by children are responsible for the consents their sites need.
10. Cookies
This website and the console use two strictly necessary cookies (your session and a security token) and remember your light/dark choice in your browser. No analytics or advertising cookies, no third-party scripts or fonts. Razorpay's payment window loads only when you press Pay on an invoice. See the cookie notice.
11. Changes to this notice
When this notice changes, the date at the top changes. If a change is material, company owners are emailed before it takes effect. Where a change adds a use that needs your consent, we ask again and the new use does not start until you agree.
12. Contact
Cruzetec Solutions, Mohali (SAS Nagar), Punjab, India · privacy@dxcslabs.com · Grievance Officer: grievance@dxcslabs.com