Privacy Policy

Last updated: October 14, 2026

1. Who we are

RQX ACADEMY is run by TEAM RQX (also known as RQX OFFICIAL or simply RQX). We operate the website rqxacademy.in and the RQX ACADEMY channels on Telegram and WhatsApp, which share Indian market news, updates and educational content. We decide why and how the data described below is used, so we are the “Data Fiduciary” for this website under India’s Digital Personal Data Protection Act, 2023.

2. In short

• The website only shows information and links to our Telegram and WhatsApp channels. It has no sign-up or contact form, and we do not ask for or collect your name, email address or phone number.
• We use the Meta Pixel and the Meta Conversions API to measure how our Facebook and Instagram ads perform.
• We do not sell your data.
• You can ask us to delete data linked to your browser at any time (see section 11).

3. What data we process, and why

Data from your browser and device

• IP address, browser and device type (user agent)
• The page you visited (domain and path only; our page removes anything after “?” from the address bar)
• The referring site or the ad click identifier (fbclid), if you arrived from a Meta ad
• How long ago an event happened in your browser (a number of milliseconds), so that we can send Meta the correct event time

Identifiers

• Meta browser identifiers (_fbp and _fbc), set by the Meta Pixel or by our page from the ad click identifier
• A random anonymous ID created in your browser (rqx_ext_id) that contains no personal details

Events

• Page view, when the page loads
• Lead, when you tap our Telegram join button on a mobile or desktop device and your browser then reports that you left our page or that its window lost focus (for example, because the Telegram app opened). This is an indirect browser signal: we cannot confirm that the app opened or that you joined the channel. Tapping the WhatsApp button does not create a Lead event.

What we do not collect

Your name, email address, phone number, Telegram or WhatsApp account details, payment details or precise location. We send Meta only the two standard events above, with no custom parameters.

Why we use this data

• To measure our ad campaigns (for example, how many visitors open our Telegram channel)
• To help Meta show our ads to relevant people, including people who have visited our website
• To avoid counting the same visit twice, and to protect the website from spam and fake events

By continuing to use the website after seeing the cookie notice, you agree to this use. You can withdraw that agreement at any time (see section 11).

4. Meta Pixel and Conversions API

The Meta Pixel runs in your browser and the Meta Conversions API sends the same events from our server. Both copies of an event carry the same event ID so that Meta can recognise them as one event and deduplicate them. Deduplication is carried out by Meta, so an event may occasionally be counted twice or not at all. We send each Lead event to Meta only once and never retry it automatically.

Data sent to Meta can include: event name, event time, event ID, page address (domain and path only), IP address, user agent, _fbp / _fbc values, and your anonymous ID (hashed with SHA-256 before it is sent). Where our network provider supplies it, an approximate country code (hashed) may also be included.

Meta processes this data under its own Privacy Policy and Business Tools Terms. You can control the ads you see in Facebook Ad Preferences.

5. Cookies and local storage

• _fbp, _fbc (cookies, up to about 90 days): ad measurement
• rqx_ext_id (local storage, until you clear it): anonymous browser ID used for event matching
• rqx_fbp, rqx_fbc (local storage): backup copy of the Meta identifiers above
• rqx_lead_ts (local storage): time of the last Lead event we recorded, used to avoid recording repeat taps within 24 hours
• rqx_cookie_ack (local storage): remembers that you dismissed the cookie notice

You can delete these at any time in your browser settings. Blocking them will not stop you from using the website.

6. Data on our server and how long we keep it

• Security files: short-lived rate-limit and duplicate-event files that hold only hashed identifiers. Our server removes them automatically, usually within a few hours and in any case within 24 hours. Our server forwards each event to Meta right away and does not keep a copy of your IP address or user agent.
• Technical logs: short server logs record only the event name, event ID, which join button was used, a coarse device type (iOS, Android or desktop), whether the page was opened inside the Facebook or Instagram app, whether the Meta Pixel script loaded and cookies were enabled in your browser, the names of the data fields sent (not their values) and a success, skipped or error status. They contain no IP address, user agent or other personal data. The live log keeps up to 14 days (and a limited number of lines), and a separate log used only by the site owner for testing keeps up to 24 hours. Older lines are deleted automatically.
• Web hosting: our hosting provider may keep standard server access logs under its own policy.
• Meta: keeps event data according to its own retention rules and settings.
• Your browser: local storage items stay until you clear them.

7. Other services and sharing

• Telegram and WhatsApp: when you tap a join button you leave our website and their own privacy policies apply (Telegram, WhatsApp). We do not receive your phone number or account details from them through this website.
• Google Fonts: the Poppins font is loaded from Google’s servers, which receive your IP address and browser details to deliver it (Google Privacy Policy).
• We do not sell personal data. We share data only with the services named in this policy, or where the law requires it.
• Meta and Google may process data on servers outside India.

8. Children

This website is not directed to children. If you believe a child’s data has reached us, contact us and we will delete it.

9. Security

We use HTTPS, restricted server files and request validation to protect data. No system is completely secure.

10. Changes to this policy

We may update this policy. Changes will be posted on this page with a new “Last updated” date.

11. Your rights and choices

• Withdraw your agreement / opt out: clear cookies and site data in your browser, block third-party cookies, or change your Facebook Ad Preferences. You can also email us and we will stop using data linked to your browser.
• Access, correction or deletion: email rqxacademy@gmail.com with the subject “Data request”. Because we do not collect your name or email, we may ask you for your anonymous ID (the rqx_ext_id value in your browser’s local storage) so that we can find the data. We aim to reply within 30 days, and will remove the data we hold and, where possible, send a deletion request to Meta.
• Nominate someone to exercise these rights on your behalf if you cannot, as the law allows.
• Complaints: write to us first (section 12). If we do not resolve your complaint, you may complain to the Data Protection Board of India.

12. Contact and grievances

Questions, data requests or complaints about this policy:
📧 rqxacademy@gmail.com
💬 Telegram support: t.me/RQX_ACADEMY

Our channels

The official RQX ACADEMY Telegram channel shares news, updates and educational content from TEAM RQX (RQX OFFICIAL).