Privacy Policy

Last updated:

1. Data Controller

The controller of your personal data (the “Controller”) is:

Indata Consulting Michał Chełmiński · registered office: ul. Boremlowska 20/6, 04-321 Warszawa · Tax ID (NIP): 2810022158 · REGON: 080186028 · e-mail: support@cryptopulsar.ai

For data-protection matters you may also contact the Data Protection Officer at support@cryptopulsar.ai.

This Policy describes what personal data we collect in connection with the use of CryptoPulsar AI available at https://cryptopulsar.ai (the “Service”), for what purposes, on what legal basis, to whom we entrust the data, and what rights you have as a data subject.

The Policy is compliant with Regulation (EU) 2016/679 of the European Parliament and of the Council of 27 April 2016 on the protection of natural persons with regard to the processing of personal data and on the free movement of such data (GDPR) and the Polish Act of 10 May 2018 on the protection of personal data.

2. What data we process

2.1. Account and login data

  • E-mail address (mandatory);
  • Username (login);
  • Password hash (bcrypt/Argon2 — we never store passwords in plain text);
  • Preferred language, time zone, interface settings;
  • For registration via identity providers (Facebook, X/Twitter): provider identifier, e-mail, name and public profile picture — the scope is limited to the fields selected during the OAuth authorisation.

2.2. Subscription and payment data

  • Stripe customer and subscription identifier;
  • Transaction history (date, amount, plan), invoices;
  • Last four digits of the card and card brand (for display in the panel);
  • We do not collect or store full card data (PAN, CVV, expiry date) — they are processed exclusively by Stripe Payments Europe, Ltd. in compliance with PCI DSS.

2.3. Technical data and logs

  • IP address, user-agent, operating system, browser language;
  • API request logs (date, path, response code, duration) — kept for security and abuse-detection purposes;
  • Session identifiers, JWT tokens (access valid for 60 min, refresh valid for 7 days; refresh is blacklisted after logout);
  • Security audit logs (failed logins, password changes, e-mail changes, privilege escalations, administrative actions).

2.4. User-generated content (UGC)

  • Satisfaction survey — ratings on a 1–5 scale and a comment. We use the results internally only, to improve the Service; we do not publish them and do not share them with third parties;
  • Public review of the Service — the review text, rating, signature (first name or nickname), optionally a country or city, and a copy of your profile picture. This data is publicly visible on the site; publication is voluntary and you can change or delete your review at any time in your profile;
  • Support-system messages (tickets);
  • Dashboard configuration (widget layout, watchlists, price alerts).

2.5. Portfolio data (Portfolio)

If you use the Portfolio feature, we process the position data that you enter yourself in order to calculate the value and structure of your recorded holdings:

  • Asset name or symbol (e.g. BTC, ETH);
  • Quantity (number of units) and cost basis in the settlement currency;
  • Acquisition date and optional personal notes;
  • Position change history (successive additions and reductions of quantity with dates);
  • Daily snapshots of the total portfolio value (to display the value-over-time chart);
  • Saved AI comments about the structure of your portfolio.

We process this data on the basis of Art. 6(1)(b) GDPR (performance of contract — provision of the Portfolio feature) and retain it until the given position or your account is deleted.

2.6. Portfolio import and what we do NOT collect

You can enter Portfolio positions manually or import them: from a file (e.g. an exchange export), from a photo of a transaction confirmation or through an exchange API key with read-only permission. A photo of a confirmation is read by an AI model only to suggest how to fill in the form; we do not store it. We accept an API key only once the exchange confirms that it has read-only permissions, we store it in encrypted form and use it solely to read balances. You can delete the key in the Service at any time and also revoke it at the exchange.

Regardless of how the data is entered:

  • we do not collect seed phrases (recovery phrases);
  • we do not collect private keys of wallets;
  • we do not accept API keys with trading or withdrawal rights for the Portfolio.

The Service does not hold custody of assets, and the Portfolio gives no technical ability to dispose of your funds.

2.7. Newsletter and marketing

  • E-mail address and language preferences — only after voluntary subscription and a separate consent that you may withdraw at any time.

2.8. Cookies and analytics

Details in section 6 and in the cookie consent panel available in the footer of the Service.

2.9. AI Assistant and tokens

  • Conversation content: the questions you type, the Assistant's answers, optional screenshots, the selected Assistant profile and the conversation language. We store conversations with your Account so that you can return to them. A conversation with no activity for more than 180 days is deleted automatically (we may shorten this period), and a conversation without any answer after about one day. You can also delete a conversation yourself in the Assistant window.
  • Transfer to the AI model: to prepare an answer, we pass to the AI model provider (section 4) the content of the question, the necessary part of the earlier conversation, an attached screenshot and selected Service data, e.g. market data and, for questions about your Account, the necessary Account data (e.g. plan, Portfolio positions). We do not pass on your password, payment data or e-mail address. Before sending, the content goes through a filter that detects confidential data. For questions using web search, the query content is also sent to the model provider's search service.
  • Statistics and security: we record how many tokens a request used, with which model and in which feature. Separately, without any link to your Account, we keep question statistics in shortened form, without addresses or longer strings of digits, stored for up to 30 days. If abuse is suspected, we record a security incident. Authorised persons on the Controller's side may access conversations only to the extent necessary to handle your request, fix errors and prevent abuse.
  • Tokens and purchases: the balance of the plan pool and purchased tokens, the history of usage and pack purchases.

Legal basis: Art. 6(1)(b) GDPR (providing the Assistant feature and token billing) and Art. 6(1)(f) (security, abuse detection, quality improvement). Please do not enter passwords, keys, card data, special categories of data or data of other people in a conversation.

2.10. Push notifications

If you enable push notifications, your browser or device system gives us a technical subscription address with encryption keys and basic information about the browser. The notification is delivered by the push service of the browser or system vendor (e.g. Google, Apple, Mozilla, Microsoft). Legal basis: Art. 6(1)(b) GDPR. You can turn notifications off in the Service settings or in the browser or device settings; subscriptions rejected by the push service are deleted.

Android app widgets. If you link the home screen widgets to your account, we store a hash of a separate widget key (used only to read your data), the phone model name, the app version and the time of the last refresh. When the refresh signal is enabled in the Service, the app also sends us the device identifier in Firebase Cloud Messaging (Google). Through this service we send only a technical “refresh the widget” signal, without the content of messages, alerts or portfolio data; the widget then downloads the data directly from our server. Legal basis: Art. 6(1)(b) GDPR. You can revoke the link in the Service Settings or by removing the widgets or the app; we delete the identifier together with the link or when the service reports it as no longer valid.

2.11. Language, country and device statistics

For traffic statistics and the development of language versions, we record the interface language, the country estimated from the device's time zone (no GPS location), the traffic source and general information about the device and its performance (e.g. device type, operating system, browser). On registration and first sign-in we assign the language and country to the Account, so that we know which language version registrations come from. We analyse the results internally in aggregated form. Legal basis: Art. 6(1)(f) GDPR (legitimate interest: maintaining and developing the Service).

2.12. Cryptocurrency payments, promotions and referrals

  • Cryptocurrency payment: the payment identifier at the operator (NOWPayments), the currency, network, amount and status of the payment and the data needed to issue a payment document. The operator also processes transaction data as a separate controller under its own privacy policy.
  • Promotions and referrals: the code or link you used, the link between the referring and referred Accounts, rewards granted and the information needed to detect abuse of the programme.

Legal basis: Art. 6(1)(b) GDPR (processing payments and rewards), Art. 6(1)(c) (accounting obligations) and Art. 6(1)(f) (preventing abuse).

3. Purposes and legal bases of processing

PurposeLegal basis (Art. 6 GDPR)Period
Account creation and operation, provision of Service featuresArt. 6(1)(b) — performance of contractuntil account deletion + 30-day soft delete
Portfolio feature — calculating the value and structure of recorded holdingsArt. 6(1)(b) — performance of contractuntil the position or account is deleted
Payment and subscription handlingArt. 6(1)(b) — performance of contract; (c) — tax and accounting obligations5 years (invoices) / until end of subscription + complaint period
Complaint and support handlingArt. 6(1)(b) and (c)3 years from case closure (limitation of claims)
Security, abuse detection, auditArt. 6(1)(f) — legitimate interest of the Controllertechnical logs 12 months, security logs 24 months
Statistics and anonymous analyticsArt. 6(1)(f) — legitimate interestup to 24 months
Newsletter, marketingArt. 6(1)(a) — consentuntil consent is withdrawn
Analytical and marketing cookiesArt. 6(1)(a) — consent + Art. 173 of the Polish Telecommunications Actas described in the cookie panel
Compliance with legal obligations (e.g. responses to authority requests)Art. 6(1)(c)period required by law

4. Recipients of the data

Your data may be entrusted to processors acting on our behalf and under data-processing agreements (DPA), including:

  • Stripe Payments Europe, Ltd. (Ireland) — payment and subscription handling;
  • Cloudflare, Inc. (USA) — CDN, DDoS protection, edge security;
  • Railway Corp. (USA) — hosting of the application and database in the production environment;
  • Development and testing environments — we use external platforms for development and staging. We do not transfer personal data of production users to these environments; only technical or test data may be processed there;
  • Functional Software, Inc. d/b/a Sentry (USA) — application error monitoring (with PII masking enabled — IP addresses and user data are not transmitted);
  • Resend, Inc. and the SMTP provider — transactional e-mail delivery;
  • AI model providers — we use both our own closed AI models running on our infrastructure (e.g. a private model hosted on RunPod) and external AI model providers (e.g. Grok, Google Gemini, OpenAI, Anthropic, DeepSeek, Qwen and other current AI model service providers). These providers process only the query content (prompts) necessary to generate a response. We do not pass them login data, payment data or users' private messages. The list of providers may change depending on the models in use; the current list is available on request;
  • Market and macroeconomic data providers — external providers of cryptocurrency and macroeconomic data (exchanges, data aggregators, on-chain and macro data providers); we send them only technical queries (e.g. asset ID), without your personal data. The list of providers changes dynamically; the current list is available on request;
  • OAuth identity providers: Meta Platforms, Inc. (Facebook), X Corp. (X/Twitter) — only if you use social login;
  • Telegram Messenger Inc. / Telegram FZ-LLC (Dubai, UAE) — Telegram channel integration: publishing analytical content, notifications and alerts at the user's request; we do NOT transmit login credentials or payment data to Telegram;
  • Accounting office and the Controller's legal advisors — to the extent necessary to perform legal obligations;
  • Public authorities — only on the basis of applicable laws.

We do not sell your personal data. We do not share it with data brokers or advertising networks.

To the extent described in sections 2.9 to 2.12, recipients of data also include: the cryptocurrency payment operator (NOWPayments), the push services of browser and system vendors and the web search service of the AI model provider. For the AI Assistant, the model provider receives the content of your questions and attached screenshots, as described in section 2.9.

5. Transfers outside the European Economic Area (EEA)

Some recipients (Cloudflare, Railway, Sentry, AI providers, certain data providers) are established in third countries — primarily the United States. The transfer is based on:

  • European Commission adequacy decisions — EU-U.S. Data Privacy Framework (for certified entities);
  • Standard Contractual Clauses (SCC) in the 2021 version for non-certified entities;
  • Additional technical and organisational measures: encryption in transit (TLS 1.2+), pseudonymisation where possible, minimisation of the scope of transmitted data.

The full list of current transfer mechanisms is available on request at support@cryptopulsar.ai.

6. Cookies and similar technologies

The Service uses cookies in three categories:

  • Necessary (always on): session, JWT, CSRF protection, language selection and cookie consent. Without them the Service cannot function correctly. Basis: Art. 173(3) of the Polish Telecommunications Act — necessary to provide the service requested by the user.
  • Analytics (optional, require consent): anonymous traffic and performance statistics;
  • Marketing (optional, require consent): content personalisation and campaign-effectiveness measurement.

Consent for analytical and marketing cookies can be granted, changed or withdrawn at any time via the consent panel available in the footer of the Service.

7. Profiling and automated decisions

Content generated within the Service (AI analyses, forecasts, sentiment, signals) is produced in an automated manner; however, we do not make decisions about you that are based solely on automated processing and produce legal effects concerning you or similarly significantly affect you within the meaning of Art. 22 GDPR.

Dashboard personalisation, sorting of asset lists and recommendations of articles to read are based on your own settings and browsing history within the Service.

8. Your rights

As a data subject you have the following rights under the GDPR:

  • Access (Art. 15 GDPR) — you can obtain a copy of your data;
  • Rectification (Art. 16 GDPR) — you can correct inaccurate data or supplement incomplete data;
  • Erasure (“right to be forgotten”) (Art. 17 GDPR) — you can request deletion of data when it is no longer necessary or when you withdraw consent;
  • Restriction of processing (Art. 18 GDPR);
  • Data portability (Art. 20 GDPR) — you can receive your data in a structured format (JSON);
  • Objection to processing (Art. 21 GDPR) — in respect of processing based on legitimate interest;
  • Withdrawal of consent (Art. 7(3) GDPR) — at any time, without affecting the lawfulness of processing carried out before the withdrawal;
  • Lodging a complaint with the supervisory authority — President of the Personal Data Protection Office (PUODO), ul. Stawki 2, 00-193 Warsaw, uodo.gov.pl.

To exercise any of the above rights, write to support@cryptopulsar.ai. We will respond within 1 month (extendable by 2 months in complex cases — with notification). We may ask you to verify your identity to avoid disclosing your data to an unauthorised person.

9. Data security

We apply technical and organisational security measures appropriate to the risk, in particular:

  • TLS 1.2+ encryption (HSTS, managed certificates);
  • Hashing of passwords with secure one-way functions;
  • Short-lived JWT tokens with revocation mechanism (blacklist) on logout;
  • Content Security Policy (CSP), X-Frame-Options, X-Content-Type-Options headers;
  • Throttling and brute-force attack detection;
  • Masking of Stripe identifiers in logs;
  • Sanitisation of all HTML originating from the CMS and UGC (DOMPurify);
  • Audit logs of administrative actions and operations on sensitive data;
  • Regular security updates and vulnerability monitoring.

Despite the measures applied, no system is 100% resistant to incidents. In case of a personal-data breach which may pose a high risk to the rights and freedoms of natural persons, we will notify you and the competent supervisory authority pursuant to Art. 33–34 GDPR.

10. Minors

The Service is not intended for persons under 16 years of age and we do not knowingly collect personal data of such persons. If you find that a child under 16 has created an account without the consent of a parent/guardian, please contact us — we will delete the data without undue delay.

11. Launch waiting list

When we enable site-block or maintenance mode, we display a voluntary "Notify me when it's back" form on the welcome screen.

  • Data scope: only the e-mail address, preferred language (pl/en/ua) and the timestamp.
  • Purpose: to send one e-mail notification when the application is available again.
  • Legal basis: GDPR Art. 6(1)(a) — consent given by entering your address and clicking "Add me to the list" — and Art. 6(1)(f) — legitimate interest in informing you that the service has been restored.
  • Retention: the address is removed from the waiting list immediately after the notification is sent. If the outage lasts longer, the address is deleted automatically after 30 days. After sending we keep only an anonymised historical log (date, language, status), without storing the plain-text address beyond the retention period.
  • Recipients: only our transactional e-mail provider (delivery process). We do not enrol you into any newsletter and we do not share the address with third parties for marketing purposes.
  • Your rights: you can withdraw consent and request deletion at any time by writing to support@cryptopulsar.ai — we will remove it without undue delay. You also have the right of access, rectification, restriction of processing and to lodge a complaint with the supervisory authority.

12. Changes to the Policy

We reserve the right to update this Policy in the event of legal, technical or functional changes. We will notify you of material changes 14 days in advance via e-mail or a notice in the panel. The current version is always available at https://cryptopulsar.ai/legal/privacy.

13. Contact

Indata Consulting Michał Chełmiński · ul. Boremlowska 20/6, 04-321 Warszawa · NIP: 2810022158 · REGON: 080186028

General matters: support@cryptopulsar.ai · Data-protection matters: support@cryptopulsar.ai

This Policy is effective as of 9 May 2026.