Skip to content
Home ยป Privacy Policy

Privacy Policy

Last updated: 12 October 2026

This policy explains what personal data Prixl collects through the prixl.io website, the Prixl Warden server agent and the Prixl Guard app, why we collect it, where it is kept, how long we keep it, who else handles it, and what you can ask us to do with it. We have tried to write it in plain English. If anything is unclear, write to our Grievance Officer (section 1) and we will explain.

1. Who we are and how to reach us

CompanyPrixl Technologies Pvt Ltd (“Prixl”, “we”, “us”)
General contactThe contact form
Grievance OfficerOur Grievance Officer, through the contact form
Products coveredThe prixl.io website; Prixl Warden (Windows server agent, local dashboard and emails); Prixl Guard Secure Access (Windows app for staff)

The Grievance Officer handles every question, request and complaint about personal data. We acknowledge a grievance when we receive it and resolve it within one month, as Rule 5(9) of the Information Technology (Reasonable Security Practices and Procedures and Sensitive Personal Data or Information) Rules, 2011 requires. The same person answers questions about our processing under the Digital Personal Data Protection Act, 2023 (DPDP Act).

2. Our role: when the data is ours and when it is yours

The DPDP Act separates a Data Fiduciary (who decides why and how personal data is processed) from a Data Processor (who processes it on the fiduciary’s behalf).

  • Prixl is the Data Fiduciary for data about website visitors, people who fill in our forms or write to us, and the administrators and billing contacts of our customers.
  • Prixl is a Data Processor for the data the Warden agent and Guard collect on a customer’s servers: the user names, IP addresses and sign-in records of that customer’s staff and of anyone who tries to sign in. The customer firm decides to install Warden and is the Data Fiduciary for that data. We process it to provide the service to that customer. The one exception is the de-identified statistics described in section 3.7, which we produce only where the customer’s licence terms allow it.

Section 8(2) of the DPDP Act lets a fiduciary use a processor only under a valid contract, and Rule 6(1)(f) of the DPDP Rules, 2025 expects that contract to cover security safeguards. A Data Processing Agreement (DPA) is available on request through the contact form.

3. What we collect and why

3.1 Visiting prixl.io

  • Request data. Your IP address, browser, the page requested and the time. Cloudflare (which sits in front of the site) and our hosting provider process this to deliver the pages and to stop abuse.
  • Google Analytics 4. We use it to see which pages get read. It records the pages you view, how you arrived, your device and browser type, an approximate location and a random visitor ID kept in a cookie. Google says Google Analytics 4 does not log or store IP addresses. We do not send Google your name, email address or anything you type into our forms. Google Signals is switched on, so if you are signed in to a Google account and have allowed ad personalisation, Google can link visits across your devices for its reports; we see only totals. We do not run ads, and our consent settings tell Google not to use the data for ads.
  • Country check. To decide whether to show the analytics banner, the page asks Cloudflare which country your connection comes from. The answer is kept in your browser for the session only.
  • Free tool download. Our free RDP Attack Report tool is downloaded from GitHub, which sees your IP address and request details. The tool runs on your own computer and sends nothing to Prixl.

How consent works today. Visitors from the European Economic Area, the United Kingdom and Switzerland see a banner, and analytics stays off unless they choose “Allow”. For visitors from everywhere else, including India, analytics is on by default and no banner is shown. Anyone can switch it off at any time with the “Privacy choices” link in the site footer. Choosing “No thanks” stops Google Analytics using cookies or a visitor ID for your visits and remembers your choice for a year; the page still sends Google a basic signal that a page was viewed, without any cookie or visitor ID. Section 7 lists the cookies.

3.2 Free trial and contact forms

  • Free trial form: your name, email address, organisation name, country and (optionally) city.
  • Contact form: your name, email address and message.
  • Spam check: Cloudflare Turnstile checks your browser to tell people from bots; our service sends Cloudflare your IP address with the check result to confirm it. Your IP address is also used to limit repeated submissions; those counters delete themselves automatically.

The forms send your details straight from your browser to our own service on Amazon Web Services in Mumbai, not to WordPress. For a free trial we email you a link to verify your address, then set up your trial and send the welcome email with your installer and organisation key. We also email a copy of each submission to our team mailbox so we can reply. When you sign up for a trial, your address is also recorded as subscribed to our product and security emails; every such email has an unsubscribe link.

3.3 Customer accounts and billing

  • Organisation name, the administrator email addresses and alert recipients you add, your plan and licence dates.
  • Billing details: billing name and address, GSTIN if you give one, invoices and payment records.
  • Records of acceptance: when the licence terms were accepted on a server, and approvals you give in the dashboard, with the Windows user name of the person who gave them.
  • Anything you send us in support emails.

We use this to run your account, send the emails you signed up for, renew and invoice your licence, answer support requests, and keep the records tax law requires.

3.4 What the Warden agent sends from your server

Warden runs as a Windows service on the server it is installed on. It reads the Windows Security and System event logs, the Windows Firewall log of dropped connections, and the Windows settings its security audit checks. It sends the following to the Prixl cloud so we can send alerts and summaries and keep your history:

DataWhat it containsWhy
Sign-in eventsAccount name (for example DOMAIN\user), whether it is an admin account, source IP address, workstation name, logon type, session ID, Windows failure status codes, the program Windows names for a failed sign-in, and the timeTo spot password guessing, sign-ins outside working hours, admin sign-ins and suspicious successful sign-ins
Session summaries (paid plans)Sign-in and sign-off times, session length, time locked, and whether the sign-in was outside working hoursFor the weekly user activity report
Account and group changesWho made the change, the account changed, group names, the member added or removed, and the changed account settingsTo alert you to new accounts and new admins
Services and scheduled tasksService name, its program path and the account it runs as; scheduled task namesTo alert you when something new is set to run on the server
Policy, firewall and log eventsFirewall turned off, firewall rule changes, audit or account policy changes, audit log clearedTo alert you to tampering
Raw event fieldsFor high and critical alerts only, the named fields of the original Windows event; long values are shortened before storageSo the alert and any support investigation have the full context
Firewall drop summariesCounts of blocked inbound connection attempts per port, and the source IP addresses behind themTo show which ports are being attacked
Blocking recordsIP addresses you or auto-block blocked, and the reasonTo show and undo blocks
Security audit resultsThe result and current value of each of the 29 checks, including the names of enabled local accounts and when their passwords were last setFor the Hardening tab, the security score and audit emails
Device and agent detailsDevice ID, device and computer name, agent version, last contact time, your trusted IP addresses, and a copy of your dashboard settingsTo show the agent is alive, keep trusted IPs consistent, and restore your settings if the server’s local copy is lost
Dashboard actionsWhat was changed (fix applied, IP blocked, setting changed) and the Windows user name of the person who did itEvery change is emailed to your administrators as an audit trail
Diagnostic logsCopies of Warden’s own log files (up to 8 files, the last 256 KB of each), sent at most once a day or when support asks. They can contain user names and IP addresses from eventsTo diagnose faults

On the server itself, Warden keeps its working files under C:\ProgramData\Prixl\warden\ and its program files under C:\Program Files\Prixl\Warden\. Its settings and credentials there are stored encrypted. Uninstalling Warden deletes the C:\ProgramData\Prixl\warden\ folder.

3.5 What Prixl Guard sends

  • For the office server: its WireGuard public key, public IP address and port, local network addresses, and the tunnel address range.
  • For each invited person: the name the administrator typed for the invite, their email address if the administrator entered one (we email them the invite), their assigned tunnel address, the WireGuard public key their app created, when they last connected and how (direct or relayed).
  • While a connection is being set up: the public IP address and port of each end, kept briefly so the two can find each other.

Private keys never leave the device that created them. The traffic inside the tunnel, including the Remote Desktop session, is encrypted end to end between the staff member’s computer and the office server, and Prixl cannot read it. When a direct connection is not possible, the encrypted packets pass through a Cloudflare relay, which also cannot read them.

If you are a staff member using Guard or a server Warden monitors: your employer decides how these tools are used. Your employer can see your sign-in records and, with Guard, whether and when you are connected, and can revoke your access. Neither your employer nor Prixl can see what you do inside the tunnel through Prixl. Questions about your employer’s use of this data should go to your employer first; we will help them answer.

3.6 What we never collect

  • Passwords, password hashes or other sign-in secrets.
  • The contents of files, documents, accounting data (including Tally data), email or browsing on your servers or staff computers.
  • Keystrokes or screenshots.
  • The contents of network traffic, including traffic inside a Guard tunnel.

3.7 Statistics about attacks

We may combine data from many monitored servers into statistics about attacks, for example how many password attempts reach servers or which ports are targeted, and publish them in research reports. We do this only under licence terms that allow it, and only in a form that does not identify any customer, server or person: no customer names, no user names, and no figures that could point to one firm. When we produce these statistics, Prixl is the Data Fiduciary for that purpose.

4. Where your data is kept

Customer data from Warden and Guard, your account records and form submissions are stored in India, on Amazon Web Services in the Mumbai region (ap-south-1). Our emails are sent through Zoho ZeptoMail and our mailbox is Zoho Mail, both on Zoho’s Indian service. Prixl Warden and Prixl Guard are offered in India today; if we offer them outside India, we will tell customers where their data is stored before they sign up.

Some data is processed outside India: Google Analytics data (Google processes it in the United States and other countries), the data Cloudflare handles at its nearest network location, encrypted Guard packets when they go through the relay, and requests to download the free tool from GitHub. The DPDP Act (section 16) allows transfers outside India except to countries the Government restricts by notification. The companies that handle customer data, and where, are on our sub-processors page; the website tools are described in section 3.1.

5. How long we keep it

DataHow long
Warden event dataDeleted automatically from the live database about 35 days after it reaches us
Monthly archive of event dataEach month a copy of the event database is exported to storage in Mumbai and archived there. It is used for investigations, not for the dashboard or emails. We are setting a fixed period after which archived copies are deleted, and will state it here
Diagnostic log uploads30 days
Guard recordsWhile you are a customer, including records of revoked people and expired invites so you keep an access history; connection set-up records are short-lived
Account, licence and consent recordsWhile you are a customer, and afterwards only as long as needed for tax, legal or dispute purposes
Invoices and payment recordsAs long as tax law requires; for GST, at least 72 months (CGST Act, section 36)
Trial sign-ups never verifiedDeleted automatically after the 24-hour verification link expires
Emails and form messages to usAs long as needed to deal with them and any follow-up
Website and cloud service logsCloud service logs: the main service’s logs are deleted after 90 days; some background jobs’ logs have no deletion period yet, and we are setting one. Website request logs: kept by Cloudflare and our hosting provider under their own terms
Google Analytics dataUp to 14 months, the longest period Google Analytics 4 allows (a setting in our Google Analytics account)

Two laws set minimum periods. The CERT-In Directions of 28 April 2022 require logs of ICT systems to be kept for a rolling 180 days within India. From mid-May 2027, Rule 8(3) of the DPDP Rules, 2025 requires personal data, traffic data and logs of processing to be kept for at least one year from the processing. We are reviewing our retention periods against these rules and will update this table when they change.

6. Who else handles your data

We do not sell personal data and we do not share it for advertising. To run Prixl Warden and Prixl Guard we use a small number of service providers (sub-processors): Amazon Web Services, Zoho (ZeptoMail and Zoho Mail) and Cloudflare. Each one gets only what it needs for its job. The sub-processors page lists what each one does, what data it sees and where. The website also uses Cloudflare, Google Analytics, our hosting provider and GitHub, as section 3.1 describes. We update that page before we add a new one.

We disclose data to a government agency or court only when Indian law requires it, and we tell the affected customer unless the law forbids us to.

7. Cookies

CookieSet byPurposeLasts
prixl_consentprixl.ioRemembers whether you chose “Allow” or “No thanks” for analytics1 year
_gaGoogle AnalyticsRandom ID that tells one visitor from another2 years
_ga_<ID>Google AnalyticsKeeps track of the current visit2 years

Cloudflare Turnstile, the spam check on our forms, does not set a cookie on prixl.io; it reads signals from your browser during the check. If you choose “No thanks” under “Privacy choices”, Google Analytics stops reading or setting its cookies for your visits. You can also delete cookies in your browser settings at any time.

The Warden dashboard on your server sets its own sign-in cookie in the browser on that server. It never leaves the server.

8. How we protect it

Data travels over HTTPS and is encrypted at rest in AWS. Each server authenticates to us with its own secret, and only a few Prixl staff can reach production systems. We look at a customer’s data only to provide support they asked for, to fix a fault or to investigate a security problem. Our Security at Prixl page explains the details, including what the Warden agent can and cannot do on your server.

9. Your rights

You can ask us to:

  • Tell you what we hold: a summary of your personal data, how we process it, and who we have shared it with (DPDP Act, section 11).
  • Correct, complete or update it (section 12).
  • Erase it when it is no longer needed for the purpose you gave it for, unless a law requires us to keep it (section 12).
  • Withdraw consent where we rely on it, as easily as you gave it; for analytics, use “Privacy choices” in the footer; for our emails, use the unsubscribe link (section 6(4)).
  • Nominate someone to exercise these rights if you die or become unable to (section 14).
  • Have a grievance resolved by our Grievance Officer (section 13).

To make a request, use the contact form, giving the address we know you by, or tell us your organisation name so we can find your records. Most of the DPDP Act’s duties start in mid-May 2027; we honour these requests now.

Data on a customer’s server. If your data reached us through Warden or Guard at your employer or another firm, that firm is the Data Fiduciary. Send your request to them; if you write to us, we will pass it to them and help them answer.

Complaints. If you are not satisfied with our answer, you can complain to the Data Protection Board of India once the relevant provisions are in force. The Act asks you to use our grievance process first (section 13(3)).

10. If there is a data breach

  • CERT-In: we report cyber security incidents to CERT-In within 6 hours of noticing them, as the CERT-In Directions of 28 April 2022 require. That deadline is for the report to CERT-In; it is not a promise about when customers hear from us.
  • Customers: if a breach affects data we hold for you, we tell your administrators without undue delay: what happened, what data was involved, what we are doing and what you should do. For agent data, where you are the Data Fiduciary, we give you what you need to meet your own duties.
  • From mid-May 2027: where we are the Data Fiduciary, we will also tell the Data Protection Board and each affected person without delay, and send the Board a detailed report within 72 hours, as Rule 7 of the DPDP Rules, 2025 requires.

11. Children

Prixl is a service for businesses. We do not knowingly collect personal data from anyone under 18 (a “child” under the DPDP Act). If you believe we have, contact the Grievance Officer and we will delete it.

12. Changes to this policy

When we change this policy we update the date at the top. If a change is material, we email customer administrators before it takes effect. Where we rely on your consent, we will ask for it again rather than treat continued use as agreement. Earlier versions are available on request.

13. Law that applies

This policy is governed by the laws of India. Today that means the Information Technology Act, 2000, section 43A and the 2011 rules made under it, and the CERT-In Directions of 28 April 2022. The Digital Personal Data Protection Act, 2023 and the DPDP Rules, 2025 (notified on 13 November 2025, G.S.R. 846(E)) bring in most of their duties in mid-May 2027, and section 43A then stops applying. This policy is written with both in mind.

Questions: our Grievance Officer, through the contact form, Prixl Technologies Pvt Ltd.