Privacy Policy

Effective 23 October 2026

Draft. This document has not yet been reviewed by a lawyer and may change before RevenShield is offered to the public.

This policy explains what personal data RevenShield collects, why, and the choices you have. We collect only what the Service needs to protect your trading accounts.

1. Who is responsible

RevenShield is responsible for your personal data in the Service (the “controller”). For any privacy question or request, write to support@revenshield.com.

2. What we collect

Your account. Your name, email address and password. The password is stored only as a salted one-way hash; we cannot read it. If you sign in with Google, we receive your name and email address from Google.

Your trading data. When you connect a platform, we read, with your permission: the accounts you choose to share (number, broker, demo or live, currency), balances, and your closed trades (time, instrument, size and result). cTrader gives us an access token for this, which we store encrypted. For Match-Trader you type your platform email and password once: the password is used for that sign-in only and is never stored; we keep the sign-in itself and each account’s read token, encrypted.

Your settings and history. Your protection rules, your time zone and day-start hour, cooldowns with their start, end and reason, and a record of important actions (for example a rule change or a device removed).

Your protected devices. For each browser extension or Windows helper you connect: a name, the browser or operating system, its version, which cooldowns it applies, whether its permissions are in place, and when it last checked in. The device’s key is stored only as a one-way hash.

Lockdown mode, if you choose it. When you agreed to the Lockdown statement, which version of it, and the browser you agreed in; when you approved or refused a PC, with the PC’s name; and the PC’s Lockdown state (on, turning off, off). Nothing from your files, passwords, keystrokes or screen.

Technical data. Information needed to run and protect the Service, such as your IP address for limiting repeated sign-in attempts, and error logs. Logs are written so that they do not contain passwords, tokens or keys.

Messages. What you send us when you contact support.

3. What we do not collect

  • Your cTrader password: cTrader accounts connect through cTrader’s own sign-in page.
  • Your Match-Trader password is not stored: it is used once to sign in and then discarded.
  • Your browsing history. The extension looks only at the trading websites it protects, and only to see which account is open there; it does not send page addresses or page content to us.
  • Keystrokes, screen content, location, contacts or files.
  • Payment card details (no payments are taken today; a future payment provider would handle cards directly).

4. How we use your data

  • To provide the Service: check your rules against your trades, start and end cooldowns, and tell your protected devices.
  • To show you your dashboard, history, reports and coaching about your own trading behaviour.
  • To keep the Service secure, prevent abuse and fix faults.
  • To contact you about your account, important changes and support requests.
  • To improve the Service, using aggregated information that does not identify you.

6. Who we share it with

We do not sell your personal data and we do not show advertising. We share data only with:

  • Trading platforms you connect (for example Spotware for cTrader), to read your accounts with your permission;
  • Google, if you choose to sign in with Google;
  • Service providers who host or support the Service for us, under contracts that oblige them to protect the data;
  • Authorities, when the law requires it.

Currency exchange rates are fetched from a public rates service; only currency codes are sent, never your data.

7. International transfers

Our providers may process data in other countries. Where that happens, we use safeguards required by the applicable law (such as contractual clauses) so that your data keeps a comparable level of protection.

8. How we protect it

Passwords are stored as salted hashes, sign-in sessions and device keys as one-way hashes, and platform access tokens are encrypted. Access to data is limited to your own account on every request. Read more on our Security page. No system is perfectly secure; if a breach affects you, we will tell you as the law requires.

9. How long we keep it

We keep your data while your account is open. When you delete your account, we delete or anonymise your personal data, except records we must keep by law or for security, such as the record that a cooldown existed and when it ended. Connected platform tokens are deleted as soon as you disconnect the platform.

10. Your rights

Depending on the law that applies to you (for example Singapore’s PDPA, or the GDPR in the EU and UK), you can ask us to:

  • give you a copy of your personal data;
  • correct data that is wrong;
  • delete your data, or limit how we use it;
  • send your data to you in a common format;
  • stop using it where you gave consent, or object to a use based on our legitimate interests.

Write to support@revenshield.com. We answer within one month. You may also complain to your local data protection authority.

11. Children

The Service is not for anyone under 18, and we do not knowingly collect data from children.

12. Cookies

We use only the cookies and stored settings needed for the Service to work. See the Cookie Policy.

13. Changes to this policy

If we change how we use your data, we will update this policy and its effective date, and tell you in the app or by email before a material change applies. For example, if a future way of connecting a platform needs more information from you, we will explain it before you use it.

Questions about this document? Write to support@revenshield.com.