NextScalp
Explore BotExplore Journal

Legal

Privacy Policy

Last updated: 18 August 2026

The two NextScalp products handle data very differently. The Bot runs on our infrastructure and stores your Telegram id and your settings (sections 4 to 6). The Journal is self-hosted software that runs on your own machine: your exchange API keys, your fills and your P&L stay on your box and never reach us (sections 7 to 11).

1. What this policy covers

This policy explains how personal data is handled in four separate contexts, deliberately kept apart:

  • This website, nextscalp.com (section 3).
  • The NextScalp Bot, the @nextscalp_bot Telegram bot that runs on our infrastructure (sections 4 to 6).
  • The NextScalp Journal application, which you host yourself (section 7).
  • Buying a Journal licence through this website (sections 8 to 11).

Nothing from the self-hosted Journal application reaches this website, the Bot, or the purchase records.

2. Who is responsible

The data controller for the website, the Bot and Journal purchases is NextScalp, an independent trader based in Warsaw, Poland. Contact: support@nextscalp.com for the Bot, security and general enquiries, or journal@nextscalp.com for Journal purchases and licences.

For the self-hosted Journal application there is no controller on our side at all: that data lives in your database, under your control.

3. This website (nextscalp.com)

When you browse this website, limited data may be processed:

  • Email you send us. If you write to us with a question or a support request, we keep your email address and your message for as long as we need it to answer you and to keep a record of the exchange. We do not sell or share it.
  • Server and CDN logs. Our host may log standard request metadata (IP address, user agent, timestamp) for security and operational purposes, retained for a limited period.
  • Rate limiting. The checkout link and the licence key page count requests per IP address to block abuse. That counter is held in server memory only, is not written to any database, and disappears within a minute.
  • Privacy-friendly analytics. We use a self-hosted Umami instance to count page views and referrers. It is cookieless, sets no persistent identifiers, does not track you across sites, and collects no personal data - which is why this page shows no cookie banner. It runs on the content pages of this website and on the public read-only demo at demo.nextscalp.com, which is a marketing surface rather than your data. It does not run on this policy page or the Terms page, and it never runs inside the copy of the Journal you install: that build carries no tracker at all, and its security policy does not even permit one to send anything.
  • Sensitive query parameters are stripped before sending. Analytics keeps the campaign parameters of an address (the utm_ ones) so we can tell which channel brought you here. Everything sensitive is deleted first: the tracker runs a before-send hook that removes session_id, key, token, email and license from both the address and the referrer of every page view. That matters on the purchase confirmation page, whose address carries the checkout session identifier: the identifier never reaches analytics, from that page or from the next one you visit.
  • The not-ready-to-buy form. The Journal page offers an optional one-click answer about why you are not buying. We store the option you picked and, if you wrote one, your free-text note. We do not store your IP address, your email, a name, or anything that links the answer back to you or to a page view - it is an anonymous count with an optional sentence attached, kept until it stops being useful for product decisions.

4. NextScalp Bot: what we collect and why

The Bot runs on our infrastructure, so unlike the Journal it does store data about you.

  • Telegram account data. When you start the bot, Telegram passes us your numeric Telegram user id and, optionally, your first name and username. We store the Telegram id as your primary identifier. We do not store your phone number, email address, or any other Telegram profile data beyond what you voluntarily share in bot commands. Legal basis: contract performance (Article 6(1)(b) GDPR) - the id is needed to route alerts to you.
  • Watchlists and preferences. Pairs you add, symbols you blacklist, price alert thresholds and bot settings (signal types, tier, notification preferences) are stored linked to your Telegram id. Legal basis: contract performance.
  • Payment records. Premium subscriptions are paid through Crypto Pay, operated by Telegram. We store invoice ids, amounts, currency, timestamps and the subscription period. We never see or store your wallet address or private keys; Crypto Pay handles the transaction layer under its own privacy policy. Legal basis: contract performance and legal obligation (record-keeping).
  • AI co-pilot usage. When you use the on-demand AI features we log a token-usage event (timestamp, approximate token count, feature name) for quota management and abuse prevention. We do not persistently store the content of your messages or the AI responses beyond the Telegram conversation itself. Legal basis: legitimate interest (quota enforcement and abuse prevention).
  • Signal lifecycle events. Each signal generates an anonymised event log (signal type, symbol, timestamp, whether it passed or was suppressed) used for self-evaluation and quality auditing. These records contain no personally identifiable information beyond the fact that a signal was delivered to a given tier. Legal basis: legitimate interest (product quality and self-auditing).

5. NextScalp Bot: storage and security

Bot data is stored in Supabase (PostgreSQL), hosted in the EU (Frankfurt, AWS eu-central-1). Data in transit is encrypted with TLS 1.2+. Data at rest is encrypted by the hosting provider. Access to the database is restricted to the NextScalp application service and the controller.

6. NextScalp Bot: how long we keep it

  • Account data (Telegram id, preferences): until you request deletion, or 2 years of inactivity.
  • Watchlists and blacklists: until you remove them or the account is deleted.
  • Payment records: 7 years (legal and tax obligation).
  • AI token-usage events: 90 days, rolling.
  • Signal lifecycle events: 365 days, rolling.

7. The Journal application (self-hosted)

The NextScalp Journal application runs on infrastructure that you control. When you use it:

  • Your exchange API keys, trade fills, positions and P&L are stored locally on your machine and are processed there.
  • We (the authors) do not receive, see, or store your keys, your trades, or your P&L. There is no central server that this data is sent to.
  • Read-only API keys are recommended. The journal does not need withdrawal or trading permissions and never initiates trades.
  • If you enable the optional private AI features (per-trade AI audit or AI coach), the specific trade data you choose to analyze is sent to the third-party AI provider you configure, using your own API key. That request is governed by that provider's privacy policy, and it does not pass through us. If you do not enable AI features, no trade data leaves your box.
  • The application does not phone home. It does not check a licence against a server, and it does not report usage to us.

8. Buying a Journal licence: payment is handled by Stripe

Journal payments are processed by Stripe. When you press the buy button you are sent to a checkout page that Stripe hosts on its own domain.

  • You enter your payment details on that Stripe page. Card numbers and equivalent payment credentials never pass through this site or its server, and we never see or store them.
  • Stripe collects your email address and your billing address. The billing address is required, because a payment processor and a seller both need to know where a sale took place.
  • Stripe processes that data under its own privacy policy and its own retention rules. Any payment receipt for the purchase is sent by Stripe from its own systems, to the email address you gave it. We do not send it and we do not email you at all unless you write to us first.
  • After payment, Stripe notifies this site over a signed webhook. That message carries the outcome of the payment, your email, the name and country from the billing details, and payment identifiers. It carries no card data.

9. What we store about a Journal purchase

On a successful payment, two rows are written to our own Postgres database. When you later download a release, a download record is added. This is the complete list.

  • Licence record: the generated licence key (a random uuid), the licensee name taken from the billing details (your email address is used instead if Stripe supplies no name), your email address, the plan, the date the licence was issued, the date your updates run until, the licence status, the Stripe customer identifier, and the country from your billing address.
  • Payment record: the Stripe checkout session identifier, the payment identifier, the identifier of the licence the payment belongs to, whether the payment was a first purchase or a renewal, the time it was paid, the amount, and the currency.
  • Download record: each time a release is downloaded with a licence key, we keep the licence identifier, the version, the time, and the IP address the request came from. We keep this so that if a licence key is leaked or abused, we can see when and from where it was used (legitimate interest).

There is no password, no account, no street address, no card data, and no trading data of any kind in those records. If you are later refunded, the status on the licence record is set to revoked; the record itself stays, because it is also the record of the sale.

10. Your licence key page is a private link

After paying, Stripe returns you to /journal/thanks/ with the checkout session identifier in the address. That page shows your licence key, the email on the purchase, and the date your updates run until.

There is no login on it. Anyone holding the full link can open it and see those same details, so treat it as a private link: do not paste it into a public issue, a chat channel, or a screenshot. The page is marked not to be indexed by search engines, our analytics is configured not to record the query string, and requests are rate limited per IP address - but the link itself is the only thing guarding it.

Your licence key is not emailed to you, so save it while it is on screen. If you lose it later, email journal@nextscalp.com from the address you bought with and we will look it up for you.

11. Why we hold purchase data, and for how long

We hold the purchase records to perform the contract you entered into by buying: to issue your licence, to know what that licence covers, to honour a renewal, and to handle a refund. Where the law requires a seller to keep records of a sale for accounting or tax purposes, that legal obligation is the basis for keeping the invoicing data, and it takes precedence over a deletion request for as long as it applies.

  • Licence and payment records are kept while the licence exists, and after that for as long as tax and accounting law requires a record of the sale to be kept. That period is set by law, not by us.
  • Download records are kept while the licence exists, as part of protecting it against leaks and abuse.
  • Email correspondence is kept while it is useful for support, and deleted on request.
  • Server logs are kept briefly, for security and operations.
  • Analytics is aggregate and is not linked to you.

Stripe keeps its own copy of the payment under its own rules. We cannot delete that on your behalf; requests about it go to Stripe.

12. Third-party processors

  • Supabase Inc. - database hosting for the Bot.
  • Telegram Messenger Inc. - message delivery and Crypto Pay for the Bot.
  • Anthropic PBC - AI inference for the Bot's on-demand AI features, with no persistent storage. For the Journal, any AI provider is one you configure with your own key, and we are not part of that request.
  • Stripe - payment processing for Journal purchases.
  • Umami (self-hosted) - website analytics, no cookies, no cross-site tracking.

We do not sell, rent, or share your personal data with advertisers or data brokers.

13. What we do not do

  • We never see, receive, or store card numbers or payment credentials.
  • We do not create an account or a password for you, and we do not profile you.
  • We do not custody funds. The Bot never asks for exchange API keys at all, and we never have access to your exchange account beyond the read-only scope you grant to your own local Journal install.
  • We do not sell or rent personal data.
  • We do not run invasive third-party advertising trackers on this site.

14. Your rights

For the data we hold about you - your Bot account and its records, your Journal purchase record, and any email you sent us - you have the following rights:

  • Access - request a copy of the personal data we hold about you.
  • Rectification - ask us to correct inaccurate data.
  • Erasure - request deletion of your account and associated data, subject to the retention obligations for payment records described above.
  • Restriction - ask us to limit processing while a dispute is resolved.
  • Portability - receive your data in a machine-readable format.
  • Objection - object to processing based on legitimate interest.

To exercise any right, email support@nextscalp.com (Bot) or journal@nextscalp.com (Journal purchases). We will respond within 30 days, and we may ask you to confirm which account or purchase is yours. If you are in the EU, the EEA, or the UK you also have the right to complain to your national data protection authority.

Because your journal data lives on your own machine, you control that part directly - delete the local install and the data is gone.

15. Data transfers outside the EEA

Anthropic PBC is based in the United States. When you use the Bot's AI features, your request content is sent to Anthropic's API for inference and is not retained by Anthropic beyond the duration of the request under their API terms. This transfer relies on Standard Contractual Clauses where applicable. Stripe also processes payment data outside the EEA under its own safeguards. For the Journal's optional AI features, the transfer is between you and the provider whose key you configured.

16. Children

NextScalp is not directed at individuals under 18 years of age. We do not knowingly collect data from minors. If you believe a minor has provided us data, contact us and we will delete it promptly.

17. Changes

We may update this policy as the products evolve. Material changes are reflected by the “last updated” date above, and material changes affecting Bot users are announced in the bot.

18. Contact

Bot, security and general questions: support@nextscalp.com (see security.txt). Journal purchases and licences: journal@nextscalp.com.