Privacy Policy

1. Who this policy concerns

This draft Privacy Policy concerns visitors to the Quantilyx corporate website and people contacting Quantilyx about its work. It explains the implemented website flow and the handling considerations for subsequent inquiry correspondence. Use the website contact form for questions about this policy.

This policy is not a blanket notice for every product or customer database. Where Quantilyx processes information under a customer’s instructions, the service agreement, the customer’s notice and any required product-specific protections govern that separate activity. The legal operator identity and provider arrangements require confirmation before this draft is approved.

2. Information you choose to provide

The inquiry form asks for your name, email address, service of interest and project brief. Company is optional. Country and a local callback number are requested only when you choose a callback. These fields help explain the request and how you can be contacted. Do not include passwords, personal identifiers, confidential records or sensitive information that is unnecessary for an initial conversation.

When you submit the form, the information is sent to the Quantilyx application server and stored in its inquiry database. A one-way hash derived from the requesting network address may be retained for abuse prevention, together with limited browser metadata and the submission time. Form drafts are not stored in local or session storage. Your browser may retain autofill or history under its own settings.

3. Career profiles and résumés

The careers form collects your name, email address, current location, area of interest, experience range, short introduction and résumé. A phone number and portfolio or LinkedIn URL are optional. Submit only your own professional information and do not include identity documents, financial records, passwords or unrelated sensitive information.

Applications and résumés are stored in private server storage for assessment against current or future opportunities. A submission does not guarantee an interview or engagement. Access should be limited to people involved in recruitment, and retention or deletion requests may be submitted through the website inquiry form subject to applicable obligations.

4. Form delivery and later communications

Selecting “Send request” submits the information shown in the form to the configured form-delivery provider. Do not submit the form until the details are correct and limited to what is useful for the inquiry.

The inquiry service may notify the Quantilyx mailbox so the team can respond. The database remains the authoritative record if an email notification is delayed or unavailable. Later discussions may include further information needed to understand the project or administer an agreed relationship.

5. Technical information and hosting logs

A browser request for a page or asset necessarily provides connection information to the systems delivering the website, such as an IP address and request headers. Hosting, network or security services may maintain access and error logs according to their configuration.

The website records limited operational events such as page views and API requests to support reliability, abuse prevention and service reporting. These records include the page or API path, time, response status, duration, limited browser metadata and a one-way hash derived from the network address. Form contents, passwords and resume contents are not copied into activity logs. The site does not use this operational log for advertising profiles.

6. Purposes and applicable grounds

Information sent in an inquiry is used to understand the request, communicate with the sender and discuss a possible engagement. Information in a service relationship may be needed to perform the agreed work, manage communications, address issues and meet applicable recordkeeping or legal obligations.

The applicable ground and any consent requirement depend on the activity, context and law in force. Where consent is required, it should be specific to that activity and capable of withdrawal as applicable. Making a service inquiry does not sign you up for marketing; this website has no newsletter subscription or marketing-consent field.

7. Recipients and disclosures

People responsible for responding to an inquiry may need to access the correspondence. Email, hosting and other providers involved in delivering communications or an agreed service may process information within their respective roles. Provider names, access arrangements and contractual safeguards need to be confirmed for the production operation.

Information may also need to be disclosed where required by applicable law or a lawful process, or to address a relevant legal or security issue. Disclosures should be assessed for necessity and scope. This notice does not authorize unrestricted reuse or sharing of client information.

8. Retention and deletion

The inquiry database, receiving mailbox and subsequent business records may retain information while it is useful for the discussion or engagement, applicable recordkeeping duties, unresolved issues and the need to establish or defend legal rights.

No fixed retention period is claimed in this draft. The owner must confirm database, mailbox, backup and hosting-log schedules and how deletion requests are handled across those systems. You can ask about a particular record or request deletion using the contact channel below; legal obligations or other applicable exceptions may affect what can be removed.

9. Accounts and signed-in activity

When you create an account, we store your email address or mobile number and a salted password hash. We send a short-lived verification code by email or, for mobile registration, through the configured MSG91 WhatsApp service. The server stores only a keyed hash of the code; expired registration challenges are deleted. An essential HttpOnly session cookie keeps you signed in for up to seven days. Signing out revokes that session. Please choose a unique password and never share your password or verification code.

While you are signed in, page visits, search terms, selected search results, account access and successful form submission events are linked to your account. Form contents, passwords and microphone recordings are not included in these activity records. You can view your own history in your dashboard; authorized administrators can view signed-in user activity for support and website improvement. Activity records are retained for 90 days by default. Contact [email protected] to request an account correction or deletion, subject to applicable retention obligations.

10. AI assistant and human support chat

When you open support chat, an essential HttpOnly cookie identifies your conversation for up to seven days. We store your messages and replies so the assistant and authorized support administrators can continue the conversation. A request for a human places the chat in our team queue; it does not guarantee immediate availability. Conversations are deleted after 30 days without activity through scheduled daily cleanup.

The AI assistant uses public website information and approved support answers. Relevant public sources and recent conversation text are sent to Cloudflare Workers AI to generate a response. Private account activity and credentials are not supplied as knowledge. Chat messages are not automatically used to train or approve new answers. Please do not submit passwords, OTPs, payment card details or sensitive project information. Contact [email protected] for support-data requests.

11. Information security

Information handling should use safeguards proportionate to the information and the risk. Access permissions, account protection and provider configuration form part of that assessment. Specific operational controls must be verified for the relevant service rather than inferred from this public website.

No internet transmission or storage system can be guaranteed completely secure. Please use the initial contact channel to agree a suitable way to exchange restricted project information, and contact us if you believe information connected to your communication has been exposed or misused.

12. Cookies, analytics and third-party content

The website uses Google Analytics 4 with measurement ID G-6XTP8CTP5C to understand aggregate website use. Google Analytics may receive page addresses, device and browser information, approximate location derived from the network address and interaction data, and may set analytics cookies or similar identifiers. Google processes this information under its own terms and privacy information.

We also record first-party page views, search activity and API reliability to understand which pages are useful and to diagnose failures. First-party page-view records contain the page path, a daily rotating one-way network-address hash and a coarse device/browser category. They do not contain query strings or form contents, and activity records are deleted after 90 days.

The site does not embed video players, external fonts or social-media widgets. You can restrict analytics cookies through browser settings or available Google controls. Links to third-party websites load those services when you choose to follow them. Any additional advertising or non-essential tracking should be assessed and disclosed before use.

13. Requests, withdrawal and complaints

You may use the website contact form to ask about information associated with your correspondence or to request access, correction or deletion where applicable. Explain the request and provide enough context to locate the relevant exchange. We may need proportionate information to verify that a request comes from the right person; do not send unnecessary identity documents in an initial email.

Where processing relies on consent and applicable law provides for withdrawal, you may use the same contact channel to withdraw it. Withdrawal may affect the ability to continue the relevant activity and does not necessarily remove records that must be retained on another lawful basis. If you have a concern, raise it with us; applicable statutory complaint routes and rights remain available where in force and relevant.

Rights, procedures and deadlines depend on the law applicable at the time and the role Quantilyx has in the processing. No universal response deadline, designated data-protection officer or claim of global privacy-law compliance is made by this draft.

14. International processing

The corporate contact location is in India. The locations used by the eventual hosting and email providers, their support teams and backups have not been confirmed for this build. This policy therefore does not assert that information stays only in India or name an unverified overseas destination.

Before launch or a service engagement involving international processing, the responsible parties should verify locations, applicable transfer restrictions and appropriate contractual or other safeguards. Customer-controlled processing may need separate instructions and disclosures.

15. Children and customer-controlled data

This corporate website is intended for business information and inquiries, and does not invite children to create accounts or submit school records. If you believe a child has provided information through correspondence, contact us so the situation can be assessed.

A school ERP can involve information about children and other individuals. That use needs a specific assessment of the institution’s role, permissions, notices, safeguards and applicable consent requirements. This corporate website policy must not be treated as authorization for every school’s operational data flow.

16. Applicable law, external sites and changes

India is the principal legal context. The Digital Personal Data Protection Act, 2023 and Rules, 2025 have a phased commencement schedule. Applicability must be checked against the provisions in force, the processing activity and any other relevant law; this draft does not treat every provision as already effective.

External websites and your chosen email application have their own privacy information. Review it before providing data to those services. We are not describing their practices as if they were under this website’s control.

The policy version and an approved effective date will identify future revisions. This version remains a draft pending confirmation of the operator, operational practices, providers and applicable legal requirements. Questions about this draft or privacy matters can be submitted through the website contact form.