At a glance

Last updated: 31 August 2026. This notice describes the current website and operational baseline. It remains pending qualified legal review.

  • We collect only the information needed to publish the site securely, operate authorized accounts and research-agent access, and review inquiries.
  • We do not sell personal information or share it for cross-context behavioural advertising.
  • We do not run advertising pixels, third-party audience analytics, or marketing cookies on public pages.
  • We do not add inquiry senders to a marketing list.
  • A stored inquiry is copied to the monitored work mailbox, then a separate transactional acknowledgment is sent to the submitted work email after administrator delivery succeeds.
  • Automated research provenance may be published with an article; private account, submission-ledger, and inquiry data are not public.

1. Scope and operator

PRO QUANT TRADE operates quantrade.pro as a public quantitative-research publication and institutional contact surface. This notice covers the public website, inquiry service, authenticated content-management system, and research-agent API.

The operating legal entity, governing jurisdiction, and dedicated privacy contact are not yet configured. Until they are, send a privacy request through the Contact page, select Other institutional inquiry, and begin the message with Privacy request. These missing operator details must be completed before formal legal approval.

2. Information we handle

Public website and service security

When a request reaches the service, the web server may process the network address, request time, host, method, path, response status, request identifier, referrer, and browser or device user-agent. This information is used to deliver the site, limit abuse, diagnose failures, and investigate security events. The site does not build a cross-site browsing profile.

Institutional inquiries

The inquiry form collects the sender's name, organization, optional professional role, work email, inquiry type, message, and acknowledgment. The application also stores a one-way keyed hash of the network address, a clipped user-agent, and a referrer with its query and fragment removed. The public receipt never echoes the message or an internal record identifier.

After the private record is stored, a background job sends the submitted contact fields and message to the monitored administrator mailbox. That email does not include the stored source metadata, network-address hash, referrer, or user-agent. It uses the sender's work email only as its reply address.

Once the administrator notification is accepted, a separate job sends a transactional acknowledgment to the submitted work email. The acknowledgment confirms receipt but does not repeat the organization, submitted message, source metadata, or an internal record identifier. Each delivery stores limited state, attempt times, and a message identifier for operational accountability. Acknowledgment failure does not alter or resend an administrator notification that was already accepted.

Do not submit account credentials, confidential datasets, material non-public information, government identifiers, payment data, health information, or another person's information without authority.

Authorized CMS and research-agent access

Human administrator and editor accounts contain identity, role, authentication, session, and security-audit information. Machine clients contain client identity, credential state, ownership, request identifiers, submission-ledger data, and research provenance. Credentials and private workflow records are not published.

Published research

An article may intentionally publish an author's name, biography, citations, source attribution, dates, methodology, disclosures, and automated-system provenance. Publication is separate from private inquiry and account processing.

3. Why we use information

We use personal information to provide requested pages and account functions, assess and respond to an inquiry, protect the service, attribute editorial and security actions, preserve research provenance, comply with law, and establish or defend legal claims.

Where a law requires a legal basis, the basis may be steps taken at the sender's request, legitimate interests in operating and securing a professional research publication, performance of an applicable agreement, or compliance with a legal obligation. We do not rely on the inquiry checkbox as consent for advertising or unrelated reuse.

4. Who may receive it

Access is limited to authorized administrators and editors who need the information for their role. Information may also be handled by infrastructure or professional service providers acting for the site, disclosed when required by law or necessary to protect rights and security, or transferred as part of a genuine business reorganization subject to appropriate safeguards.

Hostinger Email is currently the configured transactional email host. It processes the inquiry copy, sender reply address, administrator recipient address, acknowledgment recipient address, and ordinary delivery metadata only to transmit and operate those messages. Precise processing locations and any required transfer mechanism remain part of the qualified legal review.

We do not sell personal information. We do not disclose it to data brokers, ad networks, or third parties for targeted or cross-context behavioural advertising.

5. Cookies and tracking

Public reading and inquiry pages do not currently use advertising cookies, marketing pixels, third-party audience analytics, browser fingerprinting, or local-storage tracking. Authenticated CMS users receive strictly necessary first-party authentication and security cookies. Those cookies are not used for advertising.

Because the site does not sell or share personal information for behavioural advertising and does not perform cross-site tracking, browser Do Not Track or Global Privacy Control signals do not change the public-site behaviour. If non-essential tracking is proposed later, it must not be activated until this notice and any required consent mechanism are updated.

6. Retention

  • Inquiry content and associated source metadata: while the inquiry is active and for up to 24 months after the last substantive interaction, unless a shorter period is appropriate or a longer period is required for an agreement, legal claim, or security matter.
  • Spam and routine abuse indicators: ordinarily up to 90 days; evidence connected to an active incident may be preserved longer.
  • Routine access and security logs: ordinarily up to 90 days; incident records may be retained for the life of the investigation and related obligations.
  • Human account and audit information: while the account is active and, for security and accountability records, ordinarily up to 24 months after closure.
  • Agent submissions and research provenance: for as long as the associated research record is maintained, because provenance is part of publication integrity.
  • Verified database and media backups: a 30-day rolling period; a deleted live record can remain in an encrypted or access-controlled backup until that backup expires.

Records may be retained longer where preservation is required by law, a litigation hold, fraud prevention, security investigation, or a binding agreement. They should be deleted or de-identified when the applicable purpose and retention condition end.

7. Security

Controls include encrypted transport, least-privilege roles, separate human and machine identities, hashed or redacted credentials, private inquiry records, bounded requests, abuse controls, audit records, restricted production secrets, and verified backups. No security system is infallible, and this notice does not promise absolute security.

8. Your choices and rights

Depending on applicable law, a person may request access, correction, deletion, restriction, objection, or a portable copy of personal information, and may complain to the relevant supervisory authority. A person may also withdraw consent where processing actually relies on consent. The site will not discriminate against a person for making a valid privacy request.

Requests may require proportionate identity verification. A request may be limited where disclosure would expose another person's information, security controls, legal privilege, or where retention is required by law. The site does not offer a sale/share opt-out because it does not sell or share personal information for behavioural advertising.

9. International use

The site can be accessed internationally. Personal information may be processed where the operator, infrastructure, or authorized service providers are located. Where applicable law requires safeguards for a cross-border transfer, the appropriate legal mechanism must be used. Precise operator and processing-location disclosures remain part of the qualified legal review.

10. Children

The site is directed to professional research audiences and is not designed for children. A person under 18 should not submit an inquiry or create an authorized account. If personal information from a child is identified, it should be deleted unless law requires otherwise.

11. Changes and contact

This notice will be updated before personal information is used for a materially different purpose. The revision date will change when the notice changes.

For now, use the Contact page for privacy requests. A monitored privacy email, the operating legal entity, its jurisdiction, and any legally required representative details must be added before this notice can receive qualified legal approval.