Privacy Policy

Version: 2026-10-08 (draft) · Applies from: 2026-10-11

This policy explains how PIP Trading handles personal data on its website and member area: the public pages, sign-up and login, your account, the Academy, the community (Living Room), the Kasandra scanner inside PIP, PIP Kuhinja, and the marketer and staff areas.

1. Who is responsible#

The controller is Kasandra Technologies, 1032 East Brandon Boulevard, Florida, USA. Privacy contact: support@kasandra.app.

2. Summary#

• We collect what you give us at sign-up, what you do in PIP, some technical data for security, and – if you trade with a partner broker through a PIP link – volume and commission data from the broker's partner reports.
• We use it to run your account and our services, to keep PIP safe, to run the invite and marketer program, and to see who is active.
• We do not sell personal data and we do not use advertising trackers.
• Your data is stored on our servers. Some service providers process it for us (section 7).

3. What we collect#

3.1 Sign-up and profile#

First name, last name, e-mail address, password (stored only as a one-way hash, never readable), country, phone number, Telegram username, WhatsApp number (optional), language, your confirmation that you are 18 or older, the version of the terms you accepted and when, whether you want news about lessons and tools (optional), your login name, your personal invite code, your status (trial, pending, active, premium, expired), trial and access dates, and notes or tags the team adds to your record.

3.2 How you found us#

The invite or marketer link you came through, who invited you, the first and the latest invite link your browser opened in the last 30 days, campaign tags in the link (utm), the referring website (domain only) and the first page you landed on.

3.3 Security and misuse prevention#

• Your IP address at sign-up and at your latest login or visit (updated at most every 5 minutes), and the country our network provider derives from it.
• The device type (for example "Android" or "Windows"), derived from your browser's user-agent string.
• A random browser ID that our pages keep in your browser's local storage (see the Cookie and Storage Notice).
• Login history: time, IP address, browser string, success or failure.
• Session records: a hash of the session ID, device type and expiry time.
• Automatic flags: when a new account shares an IP address (within 30 days), the browser ID, a phone number or a Telegram name with another account, or uses a throw-away e-mail domain, the account is flagged for the team. A flag alone never refuses a sign-up. When a new account has an inviter and any of these flags fires (for example "possible self-referral" when it shares these details with the inviter), it does not count for the inviter until the team checks it.
• Automatic refusal: a sign-up or broker account number that matches the e-mail, phone, Telegram or broker account of a person banned from PIP is refused.

3.4 Your broker account#

The partner broker you choose, the account number or broker user ID ("Broker UID") you send us, the status of our check (pending, approved, rejected), the date, who decided and any note.

3.5 Data from partner brokers' reports#

PIP has partner agreements with brokers. When you open a trading account through a PIP link (or a PIP marketer's link), the broker sends us partner reports about that account. For each account and day they contain: your name as registered at the broker, your broker user ID, account number, account type and lot type, the instruments traded, the number of deals, trading volume (lots and notional value in USD), the commission the broker pays for that volume and, if present, a campaign source. The reports we receive today do not contain balances, deposits, withdrawals, or profits and losses.

We use this data to:

• confirm the Broker UID you send us and link the broker account to your PIP account;
• work out which commission belongs to PIP and to which marketer;
• compute an internal activity status (active, slowing, inactive, lost), a trend, and a score from 0 to 100 (shown to the team as 0 to 5 lit candles – not your Academy candles), from how much, how regularly and how recently you trade compared with others.

The activity status and score are internal: the owner, the admins and every marketer above you in the invite chain can see them (section 6). They are never shown on member pages and they do not automatically change your access. The broker reports can also include people who opened an account through a PIP link but have no PIP account; we keep those rows as business records of the commission. We keep the report files we receive on our servers.

3.6 Academy#

Lessons you open and read (while you read, the page sends short "still reading" signals and how far you scrolled), lessons marked as read, quiz and level test attempts with answers and scores, levels passed, learning days and streaks, your time-zone offset (so days count in your local time), your certificates (code, level, date) and whether your name is shown on them.

3.7 Community (Living Room)#

Questions, answers, crew posts, "helpful" votes and reports you write; your RSVPs; live-room presence (while a live room page is open and visible it sends a signal every 60 seconds; attendance counts after about 3 minutes); your crew and captain role; notices; which announcements you have seen or dismissed; your learning-board choice; posting pauses and moderation decisions. When our filters hide contact details or hold a post, the original text is kept for the team and erased 30 days after the decision.

3.8 Scanner and PIP Kuhinja#

We check on each request whether you get the live scanner or the delayed demo; the request counters that protect the service from overload are kept in memory only. PIP Kuhinja recipes, drawings and settings stay in your browser; we do not receive them unless you export a file or share a recipe code yourself. Scanner settings are also kept in your browser. Chart layouts, drawings, the watchlist, settings and price alerts you make in PIP Kuhinja are saved to your PIP account, so they follow you to your other devices; Chef recipes stay in your browser.

3.9 Member home#

A small "since your last visit" snapshot: your status, Academy level and candles, invite counts and scanner mode.

3.10 E-mails#

The service e-mails we send you (confirm your e-mail, trial and access changes, broker check results, password reset, password or e-mail changed) and a log of them (address, type, language, subject, time).

We also send the owner notification e-mails about new sign-ups and broker-account requests (name, country, language, how the person found us, any flags and, for a broker request, the account number).

3.11 Invite-link clicks and sign-up records#

When someone opens an invite or marketer link, our server records the click: the link code, the page it leads to, campaign tags, the referring website (domain only), the country (from the IP address), language, device type and a keyed hash of the IP address. Your sign-up is recorded the same way, together with the random browser ID. We do not store the IP address itself for these records.

3.12 Audit log#

Important actions are written to an audit log with the time, the account that acted, its IP address, the action and a short detail: your sign-up, e-mail confirmation, password changes and resets, profile changes and broker-account requests, and every action by the owner, admins and marketers on member records (including staff opening a member record).

3.13 Messages to us#

What you send us when you contact support: your e-mails and their attachments (the Help Center pages collect no messages).

3.14 If you are a marketer or staff#

If you are a marketer: your display name (shown as "Invited by" on the sign-up page of people who open your links and, if the leaderboard is switched on, to other marketers), your links with their codes, labels and channels, and each link's clicks and sign-up funnel. If you are staff: the secret behind your authenticator code, if you use one.

4. Why we use it and on what legal basis#

Where we rely on legitimate interests, you can object (section 9).

5. Automated processing#

• The flags and the automatic refusal in section 3.3 and the community filters (which hide contact details and hold some posts) run automatically. A person on our team reviews flagged sign-ups and held posts.
• The activity score (section 3.5) is profiling for internal use. It does not decide your access.
• You can ask for a person to review any automatic decision about you.

6. Who can see your data inside PIP#

• You: your profile, status, Academy progress, certificates and your own invite numbers.
• The owner: all data.
• Admins: member records, broker checks and activity data. Commission amounts only if the owner switches this on. Admins cannot see owner-only areas.
• Marketers: the people in their branch – those who joined through their links or through anyone below them in the invite chain, up to 12 levels (so every marketer above you sees you). For each person: name and login name, country, language, status, join date, last visit, trial end, how they joined, whether the sign-up is held for a check, the state of the broker check and the dates of e-mail confirmation, broker request and verification (never the account number), Academy level, levels passed, lessons completed, risk certification and last learning day (never answers or scores), and from broker reports: activity status, 0 to 5 activity candles, score, first and last trade date, volume in lots, trend and main instrument. Contact details (e-mail, phone, Telegram, WhatsApp) only if the owner allows it for that marketer. Broker account numbers are masked. Never balances, deposits or profits and losses. Commission amounts only if the owner allows it. In the volume view, people are shown by initials, and broker clients without a PIP account who are counted for the marketer appear only as "Client" with the last three digits of the account number.
• A member (not a marketer) who invited you: only numbers (how many people signed up, confirmed, were verified), no names.
• Other members: in the community, your public name (first name and the initial of your last name), your five candles and your posts. Crew members see each other's public name, candles, certified levels and whether each person learned or attended something in the last 7 days. The learning board shows public names and candles; you can opt out. Anyone who opens your invite link sees your first name (or a marketer's display name) as "Invited by" on the sign-up page, and the person you invited also sees it in their account.
• Anyone with your certificate code: your public name (or "PIP member" if you hide it), the level and the date.

Staff views of member data are logged.

7. Service providers and other recipients#

We may also disclose data to authorities when the law requires it, to our professional advisers, and to a buyer if PIP is sold or reorganised. We do not sell personal data and we do not share it with advertising networks.

8. International transfers#

Our servers are located in Singapore. Cloudflare and Google may process data in other countries, including the USA. Where personal data of people in the EEA, the UK or Serbia goes to a country without an adequacy decision, we use standard contractual clauses.

9. Your rights#

Depending on the law that applies to you, you have the right to:

• access your data and get a copy;
• correct wrong data;
• erase your data;
• restrict some use of it;
• receive your data in a portable format;
• object to use based on legitimate interests, including the activity score;
• withdraw consent (for example to news e-mails) at any time;
• complain to a supervisory authority: the data protection authority of the country where you live.

What you can do yourself: change your phone, Telegram, WhatsApp and language in your account settings, change your password, and log out of all devices. For everything else – including changing your name or e-mail address, stopping news e-mails, getting a copy, or erasing your account – write to support@kasandra.app. We answer within one month.

10. How long we keep data#

11. Security#

Passwords are stored as bcrypt hashes. Session IDs and confirmation and password links are stored only as hashes. Login cookies are HttpOnly and Secure. Staff sessions are short and staff can use an authenticator code. Access is limited by role, staff actions are logged and the data folder is restricted to administrators. No system is perfectly secure; tell us at once at support@kasandra.app if you notice a problem.

12. Age#

PIP is for adults. We do not knowingly collect data of people under 18. If you think a minor has signed up, tell us and we will erase the account.

13. Changes#

We may update this policy. The version and date are at the top. We will tell you about important changes in the app and by e-mail to registered members.

14. Contact#

Kasandra Technologies · 1032 East Brandon Boulevard, Florida, USA · support@kasandra.app

If the language versions differ, the English version prevails.