Privacy Policy

• Your charts stay on your device. Layouts, drawings, settings, alerts and your journal are saved in your browser. They reach our servers only if you sign in to sync them, or if you share a chart or layout.
• Market data comes straight from the exchanges. To draw a chart, your browser connects directly to exchanges such as Binance, Bybit and Hyperliquid. They see your IP address and which markets you load.
• Account (optional): if you sign in, we keep your email address, a display name, the data you choose to sync, and a record of when you use the App and which parts of it while signed in. You can delete it all from the App at any time; we then keep only your email address and the date you deleted it, for up to 12 months (section 7).
• Scripts you publish are public. If you publish a script, other people see it with your username, never your email address.
• Email list: if you join, we keep your email address, when you joined and the page you joined from. We use them only to email you about Pravex and product updates. You can unsubscribe at any time.
• Analytics: we run our own analytics, in our own Cloudflare account. For a few weeks from 27 October 2026 the Site and the App also send the same page views and events to PostHog and Umami, both in the EU, without cookies, so we can check our own numbers (2.3). We record which pages you open, which parts of the App you use, when a page is open, in use and closed, your browser and device, and your approximate location. If you are signed in, this is linked to your account. We set no analytics cookies. Outside the EU, EEA, UK and Switzerland your browser keeps a random visitor ID; inside them it keeps none.
• Hosting: our host, Cloudflare, processes technical data such as your IP address to deliver and protect the Site.
• No selling: we do not sell your personal data or use it for advertising.

The Site is run by Pravex, operated by Saurav Wagh, India ("Pravex", "we", "us" or "our"). Saurav Wagh is the data fiduciary under India's Digital Personal Data Protection Act, 2023 ("DPDP Act") and the controller under the EU and UK General Data Protection Regulation ("GDPR"), where those laws apply.

Website: https://pravex.app. Contact for anything about your personal data: [email protected].

2.1 Email list

• What: your email address, the date and time you joined, and the page you joined from.
• Why: to email you about Pravex and product updates, and to keep a record of your consent.
• Basis: your consent (DPDP Act section 6; GDPR Article 6(1)(a)). We keep the date, time and page because we must be able to show that you consented (DPDP Act section 6(10); GDPR Article 7(1)).

2.2 Emails you send us

• What: your email address, any name you give, and what you write.
• Why: to read and reply to your message and keep a record of it.
• Basis: you gave it to us for this purpose (DPDP Act section 7(a)); our legitimate interest in answering you (GDPR Article 6(1)(f)).

2.3 Our own analytics

• Who runs it: we do. The Site and the App send analytics only to our own service at pravex.app, which stores it in our Cloudflare account (section 5). We copy it to our own computer to study it. Apart from the short comparison with PostHog and Umami below, no analytics company receives it, and we do not use Google Analytics or any service like it.
• What, on every page: that the page was opened; its address without the query, apart from campaign (UTM) tags and our own short link codes; the referring site (its domain only); your browser and its version, operating system, device type, language, time zone, screen and window size; and your approximate location (country, region and city), which our host works out from your IP address. While the page is open, it records once a minute whether the page is visible and whether you used it in that minute, when it goes to the background or comes back, and when you close it, with how long it was open. On the blog it also records how far you read a post, and on the sign-up form that you joined, never the email address you typed. On the home page it records which buttons and sections you open, by their place on the page, never by their text.
• What we do not keep: your IP address. Your browser's full description (its user agent) is kept with the page record, unless your browser sends a Global Privacy Control signal.
• Why: to know how many people visit, which pages and sources help, whether people come back, and what to improve.
• Basis: our legitimate interest in understanding and improving the Site and the App (GDPR Article 6(1)(f)).
• A short comparison with PostHog and Umami: from 27 October 2026, for a few weeks, the Site and the App also send the same page views and events (2.3, 2.8) to PostHog (PostHog Cloud EU) and Umami Cloud (EU region), the services we used before our own analytics, so we can check that our own counts are right. On the site pages PostHog also records when you leave a page and script errors. Umami gets each page view and four signals with no details of their own: that the chart was used, that sign-in was opened, that a sign-in was completed, and on the home page a click on a button that opens the App. They are sent through our own domain and hold what a page record in 2.3 holds: the page address with its campaign tags, the referrer, your browser, device, operating system, language, time zone, screen size and approximate country. Neither sets a cookie or stores anything in your browser: PostHog works out a visitor hash on its own servers from your IP address, browser details and a value that changes every day, and Umami counts visits without an ID. They get no email address and no account ID, and nothing goes to them under Global Privacy Control or from our own visits to Umami. We will stop sending to them when the comparison ends and update this policy.

2.4 Visitor IDs and Global Privacy Control

• Outside the EU, EEA, UK and Switzerland: the first time a page reports, our service gives your browser a random visitor ID, which your browser keeps as pravex.vid (section 3), so we can tell a returning visit from a new one. The ID holds no name or email address. It is linked to your account only if you sign in on that browser (2.9).
• In the EU, EEA, UK and Switzerland: your browser keeps no analytics ID. To count you once a day, our service calculates a code from your IP address, your browser details and a random value that changes every day and is deleted with that day's raw records (section 7). The IP address itself is not kept.
• Global Privacy Control: if your browser sends this signal, the Site and the App send only error reports (2.8): no page views, no feature use and no visitor ID. The report is not linked to an account, and its user agent is not kept. For a signed-in account, 2.9 says what is still kept.
• Our own visits are marked and left out of our numbers.

2.5 Technical request data

• What: IP address, browser and device details, the page or file requested, the referring page, date and time, and security signals.
• When: on every request to the Site. Cloudflare, our host, processes this data and keeps technical, security and bot-traffic logs.
• Why: to deliver the Site, keep it secure, stop bots and abuse, and fix problems.
• Basis: our legitimate interest in running a secure website (GDPR Article 6(1)(f)) and, where the DPDP Act applies, the uses it permits without separate consent (section 7).

2.6 Using the App

• What: your layouts, drawings, settings, watchlists, alerts, notes and journal (trades and day notes), and pictures you add with the Image drawing tool.
• Where: in your browser's storage on your device (see section 3). Without an account, none of it is sent to us. CSV and spreadsheet files you import into the journal are read in your browser and are not uploaded.
• Region check: to pick a data source that works where you are, the App asks our host, Cloudflare, for the country of your connection. The answer is used in your browser and the chosen source is remembered there for 24 hours.

2.7 Market data from exchanges

• What: to load prices, charts and lists of markets, your browser connects directly to Binance, Bybit, OKX, Coinbase, Kraken and Hyperliquid, depending on the market and where you are. Coin icons load from CoinCap (assets.coincap.io). These services receive your IP address, browser details and which markets and timeframes you request.
• Who is responsible: these are independent companies, not our processors. We do not receive or control what they collect, and their own privacy policies apply.

2.8 App analytics and our visit counter

• What: besides what 2.3 records on every page, the App records "chart active" once per visit, after you use the chart or keep it open for 30 seconds, with the symbol, timeframe, data source and how long the first candle took to load. It also records the steps of signing in: that the sign-in window was opened, that the email was sent or could not be sent, and that a sign-in was completed. It never records your email address.
• Feature use: the App also records which parts of it are used, so we know what to improve. It records which built-in indicators, drawing tools, chart types, timeframes, symbols, views (such as the Calculator), themes and layouts you use, and which buttons, menus and settings you click or change. A button is identified by the name it has in our code, never by the text it shows. Each use is recorded with when it happened, your local hour and weekday, and once per visit a summary of your chart: which built-in indicators are on it and how many drawings of each kind. The App does not send anything you type or name. That covers your scripts and their names, the text and position of your drawings, your layouts, watchlists, alerts, notes, journal and the numbers you enter in the Calculator. A script you wrote is counted only as "a custom script", and a script published in the community by its public ID.
• What we do not do: the App sets no cookies and does not record your screen, your pointer or what you type. If your browser sends a Global Privacy Control signal, the App sends only error reports (2.4), and for a signed-in account 2.9 says what is still kept. Outside the EU, EEA, UK and Switzerland, the App also keeps the date of your first visit in your browser so we can tell new visits from returning ones, and the short name of where that visit came from (for example "google" or "chatgpt", never a full address), which 2.9 uses if you make an account.
• Visit counter: the App also sends a small request to our own counter at pravex.app/k. It stores only totals per day (for example, how many charts were opened and from which campaign). It stores no IP address, browser details or ID.
• Live count: while the chart is open, one tab of your browser keeps a connection to our account service at pravex.app open, so we can see how many people are using the App right now. It carries the country of your connection, the kind of page (the App or an embedded chart) and the same short source name as the visit counter. So that one person counts once, it also carries a random code for the open tab, made anew each time the page loads, and, if you are signed in, a one-way code made from your account, so the same account on your phone and your computer counts once. Neither code is stored. It sends nothing but a short "ping" every 30 seconds. We keep only how many people were on, every five minutes: for nine days in the live count itself, and as part of each day's totals (section 7) for as long as we need them. It is not used for our own test visits: our own devices carry a mark that leaves them out. It is not used at all if your browser sends a Global Privacy Control signal.
• Data source check: when a chart opens, the App tells our server at pravex.app which market data source it started with, which one drew the chart and how long that took. Our server adds this to daily totals for your country and your network operator's number (the public number that names an internet provider's network), keeps the totals for 8 days, and uses them to start the next chart on your network with a source that works there. It keeps no IP address and no ID. If the App started with a source chosen this way, it may also check once, in the background, whether its usual source answers again, and that answer goes into the same totals.
• Error reports: if the App crashes or a chart fails to load, it sends our own service a report: the error and where in our code it happened, the App version, the symbol, timeframe and data source, and your browser, device, operating system, language, time zone and screen size. A report is kept with the visit it came from, like the rest of 2.3, and sets no cookie. We use it only to find and fix faults. If a script you wrote or added fails or is stopped for taking too long, the App sends only a count of that: what happened, how many bars the chart had and its timeframe. It never sends the script, its name or its error text.
• Why: to know how many people use the App and which features and sources help.
• Basis: our legitimate interest in understanding, in aggregate, how the App is used (GDPR Article 6(1)(f)).

2.9 Your Pravex account and sync (optional)

• What: your email address, a display name (taken from the first part of your email address until you change it), a user ID and when you joined. When you ask to sign in, we store a hashed copy of the one-time link and code, your email address and your IP address, to check the code and to stop abuse. For each signed-in browser we store a hashed session token, when it was created and last used, and a short description of the browser (its user agent).
• Synced data: while you are signed in, your layouts, drawings, alerts, watchlists, settings, notes and journal (trades, day notes and settings, including a Hyperliquid address if you added one) are copied to our database so they appear in your other browsers. If you lock your journal with a passphrase, it is encrypted in your browser before it is saved or synced. So that you can set a new passphrase if you forget yours, we also keep a reset key for the journal. That key is stored encrypted, and we release it only to your signed-in browser after you enter a code we email to your account address. Image drawing pictures never leave your device.
• Account activity: while you are signed in, the App tells our account service every few minutes that it is open, and counts which parts of the App you used, by the same code names as in 2.8: symbols, timeframes, built-in indicators, drawing tools, chart types, views and buttons. It never sends what you type or name. A script you wrote is counted only as "a custom script", and a script from the community only as "a community script". For each day we store, linked to your account: the minutes the App was open and in use, when you were first and last active, the country of your connection, and those counts. Once, we also store where you came from when you first visited, by the same short source name as the visit counter (for example "google" or "chatgpt", never a full address); if your browser did not keep it (2.8), where the visit you signed in on came from. Only we can see it. It is not shown to other users, not sent to any other company, not sold and not used for advertising. If your browser sends a Global Privacy Control signal, only the time and the country are kept, not what you used or where you came from.
• Your analytics record: while you are signed in, what 2.3 and 2.8 record from your browser is linked to your account, together with which of your signed-in browsers it came from. So for your account we can see when you were online, which pages you opened and closed and for how long, what you used (by the code names in 2.8), on which of your signed-in browsers, from which country, region and city, and the errors you met. Only we can see it, by the same rules as account activity. If your browser sends a Global Privacy Control signal, nothing in 2.3 or 2.8 is linked to your account.
• Why: to sign you in, keep you signed in, sync your data, prevent abuse and send you sign-in emails. We do not use your account email for marketing, and we do not add it to our email list. We use account activity to see which accounts are active, to help you when you write to us, and to decide what to improve. When you delete your account, we keep a record that it was deleted (section 7), to know who left and to answer questions about the deletion.
• Basis: to provide the account you asked for (DPDP Act section 7(a); GDPR Article 6(1)(b)), and our legitimate interest in keeping accounts secure (GDPR Article 6(1)(f)). For account activity: our legitimate interest in running and improving the service for the people who hold an account (GDPR Article 6(1)(f)). You can object to it at any time (section 9). We then stop keeping account activity for your account and delete what we kept. The same goes for your analytics record: we stop linking it to your account and delete what was linked. For the record of a deleted account: our legitimate interest in knowing who left and in showing that we deleted the account (GDPR Article 6(1)(f)); ask us and we delete it (section 9).

2.10 Shared charts and layouts

• What: when you share a chart image (Copy link, Open in new tab or Tweet image), we store the image and its symbol, timeframe, label and time. When you turn on sharing for a layout, we store the layout and its drawings. Anyone with the link can see them. We do not store your IP address with them.
• Abuse checks: before an upload, Cloudflare Turnstile may check that you are a person. It processes your IP address and browser signals, and we pass your IP address to Cloudflare to verify the result and to rate-limit uploads.
• Why and basis: to host what you chose to share (GDPR Article 6(1)(b)) and to stop abuse (GDPR Article 6(1)(f)).

2.11 Importing journal trades from a Hyperliquid wallet

If you enter a wallet address in the journal, your browser sends it to Hyperliquid's public API to fetch that wallet's trades. Wallet addresses and their trades are public on the blockchain. The address is saved in your journal settings, and synced if you are signed in.

2.12 Alerts and notifications

Alerts are checked in your browser. If you allow notifications, your browser shows them; nothing about your alerts is sent to us unless you are signed in and sync them.

2.13 Scripts you publish (optional)

• What is public: when you publish a script, people using the App can see its title, description, release notes, version and publishing date, your username and how many boosts it has. If you publish it as Open source, they can also read its code. Your email address is never shown.
• What we keep: the script and its earlier versions, your username, the boosts and the reports each account gives (a report includes the reason written with it), and for an Invite-only script the usernames you let in and until when.
• Your username: publishing needs a username. We suggest one made from your display name, and you can change it.
• Why: to host and show what you chose to publish, to let you decide who may use it, and to handle reports.
• Basis: to provide the service you asked for (DPDP Act section 7(a); GDPR Article 6(1)(b)), and our legitimate interest in handling reports and stopping abuse (GDPR Article 6(1)(f)).
• Removing it: unpublishing hides a script from everyone else. Deleting your account erases your scripts and their versions, your boosts, your reports and your access lists.

2.14 Feedback you send (optional)

• What: when you use Send feedback in the App, we store what you wrote and its kind, the name and email address if you gave them, the page you were on, your browser type and, if you are signed in, your user ID. We do not store your IP address with it.
• Why: to read it, fix what you reported and reply if you asked us to.
• Basis: our legitimate interest in improving the App and answering you (GDPR Article 6(1)(f)); in India, the purpose for which you gave it (DPDP Act section 7(a)).

You do not have to give us any personal data. You can read the Site and use the App without an account and without joining the list. If you do not join the list, you will not receive our emails.

We do not ask for sensitive personal data such as passwords, exchange API keys, financial account or card details, health information or biometric data. Please do not send it to us or type it into the App.

We use only the cookies and browser storage listed below. We set no analytics cookies. The only analytics storage is the visitor ID in 2.4, kept only outside the EU, EEA, UK and Switzerland. The rest is strictly necessary, or makes a feature you use work.

• pravex.vid in localStorage (analytics, on the site pages and in the App): the random visitor ID in 2.4. Kept only outside the EU, EEA, UK and Switzerland, and never under Global Privacy Control. It stays until you clear your browser's data for the Site.
• __cf_bm cookie (Cloudflare, security): set only when Cloudflare's bot protection runs, to tell people from bots. It expires after 30 minutes of inactivity.
• cf_clearance cookie (Cloudflare, security): set only after you pass one of Cloudflare's security checks. It lasts for the period set in Cloudflare's security settings.
• PostHog and Umami (2.3, during the comparison): set no cookie and store nothing in your browser, on the site pages or in the App.
• Your theme choice in localStorage (strictly necessary): the Site follows your device's light or dark setting until you use the theme toggle. Then we store your choice in your browser, in the same setting the App uses, so the next page and the App open in it. It is not sent to us and stays until you change it or clear your browser's data for the Site.

In the App (no cookies; everything below stays in your browser until you clear it or delete it in the App):

• localStorage entries starting with pravex.: your settings, language, watchlists, layouts, drawings, alerts and alert log, notes, Calculator inputs, the data source chosen for your region, and caches of market lists. If you sign in, also your session token, user ID, email address and display name. If you share layouts, the links and the keys that let you delete them. Outside the EU, EEA, UK and Switzerland, pravex.seen keeps the date of your first visit, and on our team's own devices pravex.internal keeps our visits out of the numbers.
• IndexedDB databases: pravex-journal (your journal), pravex-images (Image drawing pictures) and, only when signed in, pravex-sync (a local copy of synced data).
• Service worker and Cache Storage (pravex-v3): a copy of the App's own files so it opens quickly and works offline. It holds no personal data.

To stop analytics, turn on Global Privacy Control in your browser (2.4). You can also delete pravex.vid by clearing the Site's data in your browser settings. This does not delete analytics collected before, but you can ask us to delete it (see section 9).

• We do not sell or rent your personal data, or share it for anyone else's marketing.
• We do not show ads, use advertising cookies, or track you across other websites.
• We do not send analytics to any other company, apart from the short comparison with PostHog and Umami (2.3), and account activity never leaves our own service. An analytics record never holds your email address; a signed-in record holds your user ID, which only we can match to your account (2.9).
• We do not open a journal you lock with a passphrase. The reset key we keep for it is used for one thing: letting you set a new passphrase with a code sent to your email.
• We do not make decisions about you by automated means.
• We do not track whether you open our emails. A link in an email we send may carry a campaign tag (2.3, 2.8) that tells us a visit came from an email.

• Cloudflare, Inc. (101 Townsend Street, San Francisco, CA 94107, USA) and its affiliates host the Site and the App, run the sign-up form, store the email list, Pravex accounts, synced data, shared charts and layouts and our visit counter in Cloudflare's D1 database, run Turnstile checks, store our own analytics (2.3) and process technical request data, on our behalf. Cloudflare may also process some network and security data for its own purposes, as its own privacy policy describes.
• PostHog, Inc. (USA) and Umami Software, Inc. (USA), during the comparison in 2.3 only, receive page views and events on our behalf. We use PostHog Cloud EU, hosted in Frankfurt, Germany, and Umami Cloud in its EU region.
• Email providers that run our mailbox and deliver our emails, only for those purposes. Sign-in emails are sent through Resend, Inc. (USA) or Brevo SAS (France), which receive your email address and the sign-in link and code.
• Exchanges and CoinCap receive requests directly from your browser when the App loads market data and coin icons (see 2.7). They act for themselves, not for us.
• X (Twitter), only if you use Tweet image: X opens with the link to your shared chart, and its own privacy policy applies.
• Authorities, courts and professional advisers, where the law requires it, or where needed to establish, exercise or defend legal claims, to enforce our Terms of Use, or to protect the rights, safety or security of anyone, including the Site.
• A successor, if Pravex or the Site is transferred, for example to a company set up to run it. This policy will keep applying to your data unless you are told otherwise.

We are based in India and may access the data from India. Our copy of the analytics (2.3) is kept on our own computer in India. Cloudflare runs a global network, so data it processes may be handled in India and in other countries, including the United States and member states of the European Union. Our sign-in email provider may process your email address in the United States or the EU. During the comparison in 2.3, PostHog stores what it receives in the EU, where its staff or subprocessors may access it from other countries, and Umami Cloud runs servers in the EU and the United States. Exchanges and CoinCap handle the requests your browser sends them wherever they operate. We transfer personal data outside India only as Indian law permits.

Where the EU or UK GDPR applies, our providers' data processing terms offer safeguards for these transfers, such as the European Commission's Standard Contractual Clauses, and Cloudflare and PostHog state that they participate in the EU-U.S. Data Privacy Framework. India does not have an EU or UK adequacy decision.

• Email list: until you unsubscribe, ask us to delete it, or we no longer need it for product updates, whichever comes first. We then delete it within a reasonable time. We may keep a minimal record, such as your email address and the date you unsubscribed, where needed to respect your choice, to show that we complied with the law, or where the law requires records to be kept. Indian rules may require certain personal data and logs of its processing to be kept for at least one year.
• Data in the App on your device: until you delete it in the App or clear your browser data. We cannot delete it for you.
• Your account and synced data: until you delete your account, which erases your account and everything synced to it, apart from the short record below. Data you delete in the App is removed from sync, and only an empty marker of the deleted item stays. Sign-in links and codes expire after 15 minutes, and sign-in requests, with the email and IP address stored for them, are deleted after about 2 days. A signed-in session ends after 365 days without use, or when you sign out.
• Account activity: for up to 12 months, and deleted with your account.
• A deleted account's record: when you delete your account, we keep your email address and the date you deleted it, for up to 12 months, to know who left and to answer questions about the deletion, and then delete it. Ask us and we delete it sooner (section 9).
• Shared layouts: until you turn off sharing for that layout. Shared chart images: until you ask us to delete them, or we remove them. Deleting your account does not remove shared links, so turn sharing off first or email us the links.
• Scripts you published: while they are published, and after you unpublish one, hidden, until you delete your account or ask us to erase it. A report is kept while we handle it and until the person who sent it, or the script's author, deletes their account.
• Feedback: as long as we work on what it reports. Ask us and we delete it sooner.
• Visit counter: daily totals only, kept as long as we need them.
• Emails you send us: as long as reasonably needed to deal with your message, keep a record of it and meet legal duties.
• Analytics (2.3): the raw records stay in our Cloudflare account for 40 days. Our own copy keeps each record for up to 12 months and then deletes it. When you delete your account, what was linked to it stays in our numbers without the link: we remove your account from it. When you object (section 9), what is linked to your account is deleted. We may delete it sooner.
• PostHog and Umami: until 27 October 2026 we used PostHog (EU) and Umami Cloud (EU), and we use them again for a few weeks from then (2.3). What they hold stays with them for the retention of our plans there (PostHog up to one year, Umami six months), until we delete those projects.
• Daily totals: each day's totals and breakdowns from our analytics, the visit counter and the live count (pages, sources, countries, devices, events and the like; never a visitor's own record or anything linked to an account) are kept in our own database as long as we need them. Totals from before 27 October 2026 also hold Umami's and PostHog's.
• Technical request data: kept by Cloudflare for the limited periods set by its own policies for running and securing its network. We keep our own copy only if needed to investigate abuse or a security incident, or where the law requires, and then no longer than necessary.

We use reasonable security practices and procedures suited to the personal data we hold. For example, the Site is served only over encrypted HTTPS connections, and our data is stored with providers that maintain their own security controls. No website, transmission or storage system is completely secure, so we cannot guarantee the security of your data. If a personal data breach affects you, we will notify you and the relevant authorities where the law requires.

Depending on where you live and which law applies, you may have the right to:

• get confirmation of whether we hold your personal data, a copy or summary of it, and information about how we use and share it;
• have it corrected, completed or updated;
• have it erased;
• withdraw your consent at any time;
• object to or restrict our use of it, and receive it in a portable format (under the GDPR);
• nominate someone to exercise your rights if you die or become unable to do so (under the DPDP Act); and
• have a grievance addressed by us, and complain to a regulator (see section 11).

If you have an account, you can see and correct your display name, sign out of all browsers, and delete your account and everything synced to it in the account panel of the App. For anything else, or to use any of these rights, email [email protected], ideally from the email address concerned. We may ask you to confirm your identity before we act. Analytics without an account is linked only to a random visitor ID, so to act on a request about it we may need the pravex.vid value stored in your browser. We will respond within one month of receiving your request. Where the law allows more time for a complex request, we may extend this and will tell you why. Withdrawing consent does not affect processing that took place before you withdrew it.

• Emails: use the unsubscribe link in any of our emails, or email [email protected]. We then stop emailing you and handle your data as described in section 7.
• Analytics: turn on Global Privacy Control in your browser; then only error reports are sent (2.4). If you have an account, you can also object to account activity and your analytics record (section 9).
• Account: delete it in the account panel of the App at any time.

Withdrawing consent is as easy as giving it.

Grievance Officer: Saurav Wagh

Email: [email protected] (please use the subject line "Grievance")

The Grievance Officer will address your grievance within one month of receiving it.

A complaint about content that a user published or shared (a script, a chart or a layout) is acknowledged within 24 hours and resolved within 7 days.

If you are not satisfied, you may complain:

• in India, to the Data Protection Board of India, where the DPDP Act applies, after first using our grievance process as that Act requires;
• in India, about our decision on a content complaint, to the Grievance Appellate Committee (gac.gov.in), within 30 days of that decision;
• in the European Union or European Economic Area, to the data protection authority where you live or work, or where you think the problem happened; or
• in the United Kingdom, to the Information Commissioner's Office (ico.org.uk).

The Site is not meant for anyone under 18. We do not knowingly collect personal data from anyone under 18, and we do not track or target children. If you believe a person under 18 has joined our list or created an account, email us and we will delete their data.

The Site links to other websites, and we post on Instagram (@pravex.app). Those services are run by others and have their own privacy policies. If you message or interact with us on Instagram, we see the information Instagram shows us, such as your username and messages, and use it only to reply to you.

Where the DPDP Act requires, you may ask to receive this policy in English or in any language listed in the Eighth Schedule to the Constitution of India.

We may update this policy by posting a new version on this page with a new effective date. If we want to use your personal data for a new purpose that needs your consent, we will ask for it first.

Pravex, operated by Saurav Wagh, India

Email: [email protected]