Privacy Notice

Who we are

This notice describes how the Pipavue brand (unincorporated, operated by its founder) ("Pipavue", "we") handles personal data when you use dash.pipavue.com and its API ("the Service").

• Data controller: the Pipavue brand (unincorporated, operated by its founder)
• Privacy contact: [email protected]
• Privacy and legal contact: [email protected]
• Business address: none yet — updated when an entity is formed.

Pipavue is a research tool — not a bank, broker, exchange, or adviser. It does not hold money or connect to a trading account.

What this notice covers

It covers data collected when you browse the preview, create an account, use the workspace, journal trades, buy a pass, or contact us. Third-party services (your broker, Google, Flutterwave, Binance) have their own policies.

No separate cookie notice is needed: the Service uses only strictly necessary cookies plus one pseudonymous browser ID, listed below.

Information we collect

We collect only what the features below actually need. We do not ask for your phone number, date of birth, ID document, precise location, or broker login.

Account information

• Your email address, which also acts as your username.
• Your password as a salted hash. The plain password is never stored or logged.
• A two-letter country code that you type at registration. Google-authenticated accounts store the placeholder code "ZZ" until a feature needs the value.
• The date and time your email was verified, and the version of this notice and of the Terms that you accepted.
• Short-lived verification codes, stored only as salted hashes with an expiry time and an attempt count.

If you sign in with Google

• The stable Google account identifier for your account, and the verified email address Google returns.
• We do not receive or store your Google password, and we request no Google scopes beyond identity.

Market workspace settings

• Your watchlist, evaluation profile, forecast horizon, analysis posture, trading-session delivery filter, chosen signal channel (timeframe and strategy), and whether the optional AI assessment is switched on.
• Which published signals you opened or acted on inside the workspace, recorded as selections against your account.
• Which instruments you ask the system to monitor, recorded as monitoring demand.

Trading journal content

• Account entries you create: a label, a venue label you type yourself, an optional capital figure, and at most the last few characters of an account reference. We store no account number, no username, no password, and no API key.
• Trade and fill records you enter, order plans, ideas, notes, tags, checklists, review periods, and your free-text commentary, including notes about your own emotions and mistakes.
• Journal content is visible to you and to staff only when needed to provide support, and every journal read or write is scoped to your account.

Billing and referral records

• Your plan code, price book, currency, amount, provider name, provider subscription or invoice references, paid-through date, trial dates, cancellation flag, and provider-confirmed payment, refund, and chargeback events.
• Card and bank details are not collected by us. Card payments run on Flutterwave-hosted pages; crypto payments run through Binance Pay invoices.
• For referral payouts: your referral code, whose code you used, the commissions earned, your wallet balance, withdrawal requests, and the payout address, asset, and network you save. Payout transactions and the staff member and time of approval are recorded.

Technical records

• A session identifier and a cross-site request forgery token, both kept in HttpOnly or SameSite-protected cookies while you are signed in.
• One year-long pseudonymous browser identifier in a cookie named pipavue_visitor, used to remember preview settings for people who have not created an account.
• A failed-login counter keyed by a one-way hash of an email address, used only to throttle brute-force attempts.
• Ordinary request records held by our hosting infrastructure, such as the address a response was sent to and the requested path. The application itself does not read, store, or analyse your IP address.

What we do not do

• No advertising IDs, social media trackers, or third-party analytics scripts run in the Service.
• We do not sell your data, rent it, or use journal content to train machine-learning models.
• We do not profile you for credit, employment, insurance, or any decision with legal effect.

Why we use it

• To create and secure your account, and to sign you in.
• To show market research, signal records, and the workspace settings you asked for.
• To keep your journal and analytics available to you across devices.
• To charge for passes, confirm payment, prevent duplicate trials, and answer billing questions.
• To administer referral credits and process payout requests.
• To stop abuse: shared credentials, scraping, referral fraud, and password guessing.
• To meet accounting, tax, refund, and chargeback obligations.
• To contact you transactionally about your account when delivery is configured.

No marketing lists exist today. Any future promotional email will be opt-in and disclosed here first.

Permission to process

Pipavue does not assume one country’s law. In general terms, we process your data because it is necessary to perform the contract you accept at signup, because it is necessary for our legitimate interests in operating a secure and paid product, because you consent to specific optional settings, or because financial record-keeping obliges us to.

• Necessary for the contract: account, security, workspace settings, journal storage, billing.
• Legitimate interests: abuse prevention, service reliability, limited logging, responding to support requests.
• Consent: creating an account with Google, switching on optional AI assessment, and any future non-essential cookies or marketing.
• Legal obligation: retaining transaction records, and handling refund, chargeback, or tax requests.

The descriptions above map onto contract performance, legitimate interest, consent, and legal obligation under applicable data protection law (including GDPR and CCPA).

Who sees the data

We share with providers that operate parts of the Service, staff who work on it, and as required by law.

• Our own infrastructure: the PostgreSQL database, Redis cache, and application containers we administer ourselves on a shared hosting platform.
• Email delivery through Resend, which receives the address and the message content needed to send verification and password codes.
• Card and bank subscription payments through Flutterwave, which receives the amount, plan, your email, and a reference; the result returns to Pipavue.
• Crypto payments through Binance Pay, which receives an order reference and amount.
• Google, for sign-in when you use it, and for the webfont files that the dashboard stylesheets request.
• Market data sources: a cTrader Open API connection and a public Dukascopy feed for forex prices and candles, and public exchange endpoints reached through CCXT for crypto prices. These are outbound requests that carry the instrument and time range you asked about, not your name or email.
• A large-language-model provider configured by us, for optional assessment; see the AI section.
• Staff and contractors bound to confidentiality, limited to what support or review requires.

The cTrader connection is a single staff-run account used for market research only. Its authorisation asks for read-only account scope, it does not accept your broker credentials, and no user account is linked to it.

We may disclose data to comply with a valid legal order, prevent fraud, or in connection with a sale or reorganisation of the product.

The optional AI assessment

Some workspaces offer an AI assessment alongside the deterministic algorithm. It is off by default and you can switch it off at any time in preferences.

• What is sent: market facts about a candidate setup — symbol, prices, levels, timestamps, and computed indicator context.
• What is never sent: your email, name, journal entries, billing records, or any other field that identifies you.
• The model cannot set prices, publish a signal, or place a trade. Code checks and gates decide what is published.
• The provider processes that payload under its own terms and retention settings. The connection is configured by us from the server, so no provider credential is ever exposed to your browser.

Cookies and browser storage

• sessionid — keeps you signed in. HttpOnly, SameSite=Lax, and marked secure whenever the Service is not in preview mode. Required.
• csrftoken — protects form and API writes from cross-site forgery. HttpOnly, SameSite=Lax, secure outside preview mode. Required.
• pipavue_visitor — a signed, random browser identifier that stores preview preferences for visitors without an account. HttpOnly, SameSite=Strict, secure on a secure connection, one year.
• Browser localStorage on the signed-in dashboard: your chosen theme and display timezone, the forecast horizon and the timeframe and strategy you last viewed, your email-alert and sound-alert switches, and an offline cache of your watchlist.
• Browser localStorage on the public preview: watchlist, display timezone, evaluation profile, forecast horizon, the email-alert switch, and the AI-assessment switch, all on your device only.
• Browser sessionStorage on the public preview: the email address you typed mid-signup, so the verification step survives a reload.

There is no tracking, advertising, or analytics cookie to decline. Blocking the necessary cookies signs you out and stops the workspace from saving settings.

How long we keep it

Account, settings, journal, and preference data are kept while your account exists. Verification code records expire within minutes of being issued and are consumed on use. Login-throttle counters delete themselves after their short window.

• Raw market bars and snapshots in the research store carry a retention deadline, 35 days by default, and are pruned by a scheduled job.
• Signal records, outcomes, and research evidence are kept as product records because published analysis must stay auditable; they describe markets, not you.
• Behaviour tied to your account, such as which signals you opened, is kept with your account and removed when you close it.

When you close your account

Closing is available to you in Account settings and is irreversible. It cancels the next renewal with the payment provider first, then removes as much as possible while leaving the small residue that financial records require.

• Erased or unlinked at closure: email address and username, password hash, journal content, watchlist and workspace settings, signal selections, monitoring demand, referral code ownership, Google identifier link, verification codes, and active sessions.
• Kept but detached from your identity: subscription, payment, refund, chargeback, and payout records, retained under an anonymous account reference so we can prove what was bought, paid, or refunded. Consent records (which version of these documents you accepted, and when) are kept for the same reason, along with two append-only logs that the product makes undeletable for everyone, including us: the journal change trail and the history of analysis-posture setting decisions.
• Kept as anonymised attribution: the referral link between you and the person whose code you used, because it is the audit trail for a commission someone else earned.

Backups age out on their own schedule; deleted data is not deliberately rebuilt into a live system.

Your choices and your rights

• Take everything with you. Account settings offer an export that returns the data we hold about you as a JSON file.
• Delete your own writing on request. The journal has an erase-all action, confirmed by typing a phrase, that clears your journal accounts, trades, fills, plans, notes, ideas, tags, checklists, period reviews, and journal preferences. What stays is the activity trail, which records field names and counts rather than your content so the erasure itself is provable.
• Close the account and be forgotten as far as the records allow, from Account settings.
• Correct things. You can change your email address and password yourself; other corrections can be requested through the contact address.
• Switch off the optional AI assessment at any time; the deterministic algorithm keeps working without it.
• Ask us to restrict, object, or explain an automated decision. There is no automated decision with legal or similarly significant effect at Pipavue: signals are information, and passes gate what you can read, not whether you can trade.

Requests go to [email protected]. We respond within 30 days, normally free of charge.

You can also clear this site’s data in your browser at any time. Unresolved concerns may be raised with your local data protection authority.

How we protect it

• HTTPS everywhere in production, secure and HttpOnly cookies, and cross-site request forgery protection on writes.
• Passwords stored only as salted hashes; email verification codes are stored hashed and expire in ten minutes.
• Failed logins are throttled per account, and signup has a hidden honeypot field.
• Every journal and preference query is filtered by the authenticated owner, and privileged operations are checked server-side rather than trusting the interface.
• Server-side authorization is enforced for account changes, payouts, and billing webhooks, with provider signatures verified.

No system is unbreakable. We do not claim certification. If a breach creates a risk to you and the law requires notification, we will notify you and the relevant authority.

Where data lives

The application runs on servers we administer. Ask [email protected] for current hosting location. Third-party providers process data in their own regions; if your law requires transfer safeguards, that is the starting point.

Age

The Service is not directed at anyone under 18. We do not knowingly collect data from children and delete any such account.

Changes to this notice

This page shows its version and effective date. When practices change, we update the document, raise the version, and record the new version against accounts created afterwards. If a change is material — new data, new purposes, or new sharing — we ask you to acknowledge it before continuing, and we tell you before the change takes effect rather than after. Older versions stay available on request from the contact address.

Contact

• Privacy questions and rights requests: [email protected]
• Support and billing: [email protected]

One mailbox ([email protected]) handles all correspondence. If a dedicated legal contact becomes necessary, it will appear here.