Privacy Policy

Last updated 16 August 2026. This policy covers the website at calyirex.com.

The short version

This website sets no cookies. None at all, of any kind. Nothing is written to your browser's storage either.
We count visits, and that is the whole of it. We use Cloudflare Web Analytics, which is cookieless: it tells us how many people read a page, roughly where in the world they were, and what they came from. There is no Google Analytics, no tag manager, no advertising pixel, no session recorder. You are not profiled and you are not followed between visits, because the tool holds nothing that could recognise you the second time.
We collect personal data in exactly two places: the enquiry form, and the demo booking.
We use it to reply to you. We do not sell it, rent it, or use it for advertising.
You can ask us to delete it at any time by writing to [email protected], and we will.

1. Who we are

Calyirex Technologies Private Limited is a private limited company incorporated in Karnataka, India.

Corporate Identity Number (CIN): U62091KA2024PTC193211
Registered office: 1st Floor, Kailasa Mithila Farms, Gardady, Belthangady, Dakshina Kannada, Karnataka 574217, India
Email: [email protected]

For the personal data described in this policy, we are the Data Fiduciary under India's Digital Personal Data Protection Act, 2023 (the "DPDP Act"). That means we decide why and how it is handled, and we are answerable for it.

2. What this policy does and does not cover

It covers this website only: calyirex.com and the enquiry and booking routes on it.

It does not cover our products. When an organisation uses Calyirex Kautilya, Payroll, POS, Nazar or any other product of ours, that organisation is the Data Fiduciary for the records inside it, and we act as their processor on their instructions under a separate agreement. If you are an employee, officer or customer of one of those organisations and you have a question about your records, ask them first. We will help them answer you, but the data is theirs to control, not ours.

3. What we collect, and why

3.1 The enquiry form

What	Required	Why we ask
Name	Yes	So we can address you properly in a reply.
Work email	Yes	It is where the reply goes. Without it there is no way to answer.
Organisation	Yes	So we can route your enquiry to whoever knows your sector.
Phone number	No	Only if you would rather be called than emailed.
Which product	No	To send your enquiry to the right person the first time.
Your message	No	Whatever you choose to tell us.

Purpose: to answer your enquiry and, if you want one, to arrange a conversation about our products. Nothing else. Please do not put anything sensitive, confidential or unnecessary in the message box; a form on a website is not the place for it.

One thing we derive rather than ask you for. When the form is submitted we also store a one-way hash of your IP address, salted with a secret key of ours. We keep it for one reason: to notice a single address flooding the form, which is close to the only defence a public form has against abuse. We do not store the IP address itself. We should be straight about the limit of this, though: because the salt is ours, a given address could in principle be checked against the hash, so we treat it as personal data rather than pretending it is anonymous. It is deleted with the rest of the enquiry.

3.2 The demo booking

The "Book a demo" button hands you over to Google Calendar appointment scheduling. Google collects the name and email address you enter there, creates the appointment, and issues a Google Meet link. That happens on Google's systems under Google's Privacy Policy, not ours, though we receive the booking and use it to meet you.

3.3 What we do not collect

No cookies. This site sets none, of any kind, including analytics and preference cookies.
No tracking analytics. No Google Analytics, no Tag Manager, no Meta pixel, no Hotjar, Clarity, Segment or Mixpanel. We do measure page views, using Cloudflare Web Analytics, and section 3.4 says exactly what that does and does not involve.
No session recording or heatmaps. We do not watch what you click.
No advertising, profiling, tracking or automated decision-making. We build no profile of you and we make no automated decisions about you.
No browser storage. Nothing is written to localStorage, sessionStorage or IndexedDB.
One third-party script, named. The page loads its own code and its own font. The single exception is the Cloudflare Web Analytics beacon described below. Nothing else is loaded from anywhere else, and the page's Content-Security-Policy is written as a list of exactly what is permitted, so an unlisted script cannot run even if something tried to insert one.

3.4 Measuring visits

We use Cloudflare Web Analytics to see whether anything we publish is read. It records a page view: which page, the referring site, approximate country, and device type, along with page-loading speed.

It is worth being exact about why this does not contradict the rest of this policy. In Cloudflare's own words, they "don't use any client-side state (like cookies or localStorage) for analytics purposes" and do not track users "over time via their IP address, User Agent string, or any other immutable attributes." There is no identifier stored on your device and none derived from you, so nothing links one visit of yours to the next. A "visit" in the dashboard is counted from the referring site, not from recognising a person.

The practical consequence: we can tell that a page was read two hundred times. We cannot tell that you read it, we cannot tell that you came back, and we could not single you out if we wanted to.

If you would rather not be counted at all, any content blocker that blocks static.cloudflareinsights.com stops it, and nothing on the site breaks when you do.

3.5 Server logs

Like nearly every website, the infrastructure that serves these pages keeps ordinary technical logs, which can include your IP address, the time of the request, the page requested, and your browser's user-agent string. These exist to keep the site running and secure, not to identify you, and we do not use them to build any profile. They are kept only as long as our hosting and security providers retain them in the normal course.

4. Consent, and taking it back

When you fill in the enquiry form or book a demo, you are choosing to give us your details so that we can reply. Submitting the form is that consent, and this policy is the notice that goes with it under section 5 of the DPDP Act.

You can withdraw it at any time, and it is meant to be as easy as giving it: email [email protected] and say so. We will stop using your details and erase them, unless a law requires us to keep something, in which case we will tell you what and why. Withdrawing does not make anything we did beforehand unlawful.

5. Who else sees it

Google, in two ways. Our company email runs on Google Workspace, so the notification of your enquiry, and any reply we send you, passes through and is stored in it. Separately, if you book a demo, the appointment is made in Google Calendar.
Our hosting provider, which runs the servers in India that your enquiry is stored on, and which carries the notification email out to us. We will name it on request.
Cloudflare, which serves this website, sits in front of it, and provides the visit counting described in section 3.4.
All three act as our processors, on our instructions, and none of them is permitted to use your data for their own purposes.
Nobody else. We do not sell personal data. We do not rent, trade or share it with advertisers, data brokers or list builders. There is no such arrangement and we do not intend to make one.

If a law, a court or a lawful government demand requires disclosure, we will comply, and we will tell you unless we are prohibited from doing so.

6. How long we keep it

Enquiries: while we are talking to you, and for up to 24 months after the last exchange, so that we can pick up a conversation where it left off. Then we delete them.
Bookings: in our Google Calendar for as long as the record of the meeting is useful, and then deleted.
If you ask us to delete sooner, we delete sooner. That is the whole rule.

7. Your rights

Under the DPDP Act you have the following rights over the personal data we hold about you. Exercise any of them by emailing [email protected] from the address you contacted us with, or by telling us enough that we can find your record.

Right to access: Ask for a summary of the personal data we hold about you, what we are doing with it, and who we have shared it with.
Right to correction and completion: Ask us to correct anything inaccurate or misleading, complete anything incomplete, and update anything out of date.
Right to erasure: Ask us to delete it. We will, unless keeping it is required by law.
Right to withdraw consent: As described in section 4.
Right of grievance redressal: Complain to us about how we have handled your data or your request, using the contact in section 8.
Right to nominate: Nominate another person to exercise these rights on your behalf if you die or become incapacitated.

We aim to answer any request within 30 days. There is no charge. We may ask you a question or two to be sure it is really you before we act, which protects you rather than us.

The DPDP Act also asks something of you: please do not file a false or frivolous complaint, do not impersonate someone else when exercising these rights, and give us accurate details so we can act on them.

8. Grievance Officer

If you have a complaint about how we have handled your personal data, or about a request you made under section 7, write to our Grievance Officer:

Grievance Officer, Calyirex Technologies Private Limited: Email: [email protected] with "Grievance" in the subject line; Post: 1st Floor, Kailasa Mithila Farms, Gardady, Belthangady, Dakshina Kannada, Karnataka 574217, India

We will acknowledge your complaint and work to resolve it. This is the route to use first.

9. Complaining to the regulator

If we have not resolved your complaint to your satisfaction, you may complain to the Data Protection Board of India, the authority established under the DPDP Act. Using our Grievance Officer first is a requirement of the Act, not a way of putting you off.

10. Children

This is a website about enterprise software, and it is not directed at children. We do not knowingly collect personal data from anyone under 18. We do not track children, serve them advertising, or profile them, and we would not, because the DPDP Act forbids it. If you believe a child has sent us personal data through this site, tell us at [email protected] and we will delete it.

11. Where your data is held, and security

The enquiry database is in India. What you type into the form is stored on servers in Mumbai. Our hosting provider operates them, under contract, and cannot use your data for anything of its own.

Email and calendar are not, and we would rather say so than imply otherwise. Our email runs on Google Workspace and demo bookings are made in Google Calendar. Google operates those across data centres in more than one country, so a copy of your name, address and message sits outside India from the moment we are notified. The website itself is served through Cloudflare's global network, which means the ordinary technical logs described in section 3.5 are handled at whichever of its locations is nearest to you.

Section 16 of the DPDP Act permits transfer outside India except to countries the Central Government restricts by notification. At the date of this policy no such restriction affects any of the above. If one ever does, we will change how this works and say so here.

We protect it with reasonable security safeguards: encryption in transit (this site is served over HTTPS), access limited to the people who need it, and the ordinary discipline of keeping systems patched. No safeguard is perfect, and we will not pretend otherwise. If a breach affects your personal data, we will notify you and the Data Protection Board of India as the Act requires.

12. Languages

This policy is published in English. On request we will provide it in any language listed in the Eighth Schedule to the Constitution of India, including Kannada and Hindi. Write to [email protected].

13. Changes to this policy

If we change how we handle personal data, we will update this page and change the date at the top. If the change is significant, and we hold a way to reach you, we will tell you rather than rely on you noticing.

14. Contact

Anything at all, including the things this policy does not answer: [email protected].