Privacy Policy

1. Controller

The controller responsible for data processing on this website and in the Market Jury apps is:

JLS Capital GmbH
Postgasse 8b
1010 Wien
Austria
Email: team@marketjury.com

2. Hosting and server log files

This website runs on servers operated by us at the hosting provider Hetzner in Germany. On every visit, the server automatically collects technical data (IP address, date and time of the request, page accessed, amount of data transferred, browser type and operating system, referrer URL). These server log files are used for technical security and error analysis and are automatically deleted after a short time. The legal basis is our legitimate interest in a smooth and secure operation (Art. 6(1)(f) GDPR).

3. Account and registration

A user account is required for certain features (e.g. viewing your own analyses, your analysis quota). When registering by email and password, we store your email address and a password hash (never plain text). If you register via Google, Apple, or LinkedIn instead, we receive your email address, name, and profile picture, if provided, from that provider. The legal basis is the performance of our usage agreement with you (Art. 6(1)(b) GDPR).

For sign-in we use a technically necessary session cookie that authenticates you after login. It is not used for advertising or tracking purposes.

4. Analysis feature (asking the agents)

When you ask our AI agents a question about a security, that question, together with the selected instruments, is transmitted to the AI model providers listed below to generate an answer. We permanently store the question and answer in our database so you can revisit them later.

In the community view, other users' analyses are visible, but only with the question, instrument, and answer, without indicating which user submitted the analysis.

5. Service providers used (processors)

To provide the platform, we use the following third-party providers. Data processing agreements under Art. 28 GDPR are in place with all relevant providers where required. For the Meta Pixel, a joint controllership arrangement under Art. 26 GDPR applies instead (see section 8).

6. Traffic analytics with Umami

To understand how Market Jury is used and to improve it, we use Umami. We run Umami ourselves on our own server (insights.marketjury.com); the data is not shared with third parties. Umami does not set cookies and runs for all visitors, regardless of your choice in the cookie banner. It records page views and individual interactions (e.g. starting an analysis, clicking a purchase button) together with technical information such as browser, operating system, device type, screen size, language, referrer, and approximate location (e.g. country or city). Your IP address is used only to determine this approximate location and to generate a session identifier, and is not stored.

We also offer Umami's session recording. It reconstructs how you move through the site (e.g. clicks, scrolling, mouse movements, and the page content displayed) so that we can identify usability problems. Input into password fields is not recorded. You enter payment details exclusively on Stripe's checkout page, which is not part of the recording. Unlike the plain pageview count above, this session recording only runs if you consented to the "Statistics" category in the cookie banner (via "Accept all" or individually in Settings). Without that consent, we record nothing.

If you are logged in, we link the recorded usage data and, with consent, recordings to your account (user ID, email address, name, and role) so that we can understand how individual users use the product and support you specifically if problems arise. Without login, we do not attribute the data to any person. Completed purchases (plan or credit pack, amount, order reference) are also sent to Umami by our server once Stripe confirms them, linked to your user ID for logged-in purchases.

The legal basis for the pageview count is our legitimate interest in traffic analytics and improving our offering (Art. 6(1)(f) GDPR); insofar as information in your browser is processed for this purpose, we rely on Section 25(2) TDDDG. For the session recording, the legal basis is your consent (Art. 6(1)(a) GDPR, Section 25(1) TDDDG); you can withdraw it at any time with effect for the future via the "Cookie settings" link in the footer by deselecting the "Statistics" category or choosing "Reject". You can also object to the count itself at any time on grounds relating to your particular situation (Art. 21 GDPR); to do so, write to the email address given below.

7. Google Tag Manager and Google Ads

Our website includes Google Tag Manager. It is a management tool through which we load marketing services (currently Google Ads and the Meta Pixel). The Tag Manager script is retrieved from Google's servers on every page view; for technical reasons, your IP address is transmitted to Google in the process. The Tag Manager itself does not set cookies and does not analyze usage data. The legal basis for loading it is our legitimate interest in simple management of the integrated services (Art. 6(1)(f) GDPR).

We use Google Ads to measure whether our ads lead to registrations, started analyses, clicks on our Telegram links, or purchases (conversion tracking). For this we use Google's Consent Mode: by default, all Google signals are denied, and the Google Ads tags only fire if you consent to the "Marketing" category in the cookie banner (via "Accept all" or individually in Settings). Without this consent, we do not transmit any data to Google Ads. With consent, Google sets cookies and processes online identifiers, device and browser data, your IP address, and the measured event (for purchases: plan, amount, and order reference). We do not pass your email address, name, or user ID to Google.

The legal basis for Google Ads is your consent (Art. 6(1)(a) GDPR, Section 25(1) TDDDG). You can withdraw it at any time with effect for the future by deselecting the "Marketing" category or choosing "Reject" via the "Cookie settings" link in the footer.

Google may also transfer data to servers in the USA. For the USA, there is an adequacy decision of the European Commission (EU-US Data Privacy Framework), under which Google is certified.

8. Meta Pixel (Facebook and Instagram)

We also advertise on Facebook and Instagram. To measure whether these ads lead to sign-ups, started analyses, clicks on our Telegram links, initiated checkouts or purchases, we use the Meta Pixel of Meta Platforms Ireland Limited, Merrion Road, Dublin 4, D04 X2K5, Ireland ("Meta"). The Meta Pixel is loaded via Google Tag Manager and only fires if you consent to the "Marketing" category in the cookie banner (via "Accept all" or individually in Settings). Without this consent, the Meta Pixel is not loaded and no data is transmitted to Meta.

With your consent, the Meta Pixel sets cookies in your browser (_fbp and, if you reach us via an ad, _fbc) and transmits to Meta online identifiers, device and browser data, your IP address, the page visited and the measured event (for purchases, amount and currency) as well as a technical event ID. We do not pass your email address, name or user ID to Meta. If you are logged in to Facebook or Instagram, Meta can link the data to your account. According to Meta, it also uses the data for its own purposes, for example to deliver ads and to improve its advertising services.

In addition, our server transmits the sign-up and purchase events directly to Meta (Conversions API), also only if you have consented to the "Marketing" category. This includes your IP address, your browser identifier (user agent), the Meta cookie identifiers _fbp and _fbc and the event (for purchases, amount and currency), but no email address, name or user ID.

We are jointly responsible with Meta for collecting the data on our website and transmitting it to Meta (Art. 26 GDPR). The details are set out in a joint controllership agreement (Controller Addendum, available at https://www.facebook.com/legal/controller_addendum). Under this agreement, Meta provides you with information about the processing at Meta and handles your rights regarding the data stored by Meta; you can, however, also contact us. Meta is solely responsible for any further processing after transmission. More information is available in Meta's Privacy Policy at https://www.facebook.com/privacy/policy.

The legal basis for the Meta Pixel is your consent (Art. 6(1)(a) GDPR, Section 25(1) TDDDG). You can withdraw it at any time with effect for the future by deselecting the "Marketing" category or choosing "Reject" via the "Cookie settings" link in the footer.

Meta may also transfer data to servers of Meta Platforms, Inc. in the USA. For the USA, there is an adequacy decision of the EU Commission (EU-US Data Privacy Framework) under which Meta Platforms, Inc. is certified.

9. Origin of your registration (campaign analysis)

If you reach us via a link with campaign parameters (e.g. from an ad or a newsletter), we store where you came from in your user account when you register: the parameters utm_source, utm_medium, utm_campaign, utm_content, and utm_term, the click identifiers gclid (Google) and fbclid (Meta), and the page you landed on. We use this to analyze which campaigns and channels lead to registrations. We use this information only for our own analysis and do not pass it on to Umami, Google, or Meta.

Without consent, we store nothing in your browser for this; the parameters are only passed along in the address of the registration page. If you consented to the "Marketing" category in the cookie banner, we additionally remember the origin in your browser's sessionStorage for the duration of your browser session, so that it is retained if you visit other pages before registering. The sessionStorage is cleared when you close the tab or browser.

The legal basis for storage in your user account is our legitimate interest in evaluating our advertising (Art. 6(1)(f) GDPR); for storage in your browser, it is your consent (Art. 6(1)(a) GDPR, Section 25(1) TDDDG). We store the origin data for as long as your account exists.

10. Cookies, local storage, and consent

Technically necessary cookies or entries in your browser's local storage (e.g. your session cookie after login, your light/dark display setting, your cookie decision itself) are required to operate the platform and run without consent, based on our legitimate interest in a functioning offering (Art. 6(1)(f) GDPR, Section 25(2) TDDDG).

Anything beyond that which sets cookies or stores data in your browser runs only with your consent, which you grant on your first visit via the cookie banner, or choose individually for the Statistics and Marketing categories via "Settings" ("Accept all", "Reject", or an individual selection). Statistics covers Umami session recording (see section 6), Marketing covers Google Ads (see section 7), the Meta Pixel (see section 8) and storing the origin data in sessionStorage (see section 9). Plain pageview analytics with Umami does not set cookies and does not depend on this choice (see section 6).

You can change your decision at any time via the "Cookie settings" link in the footer; a withdrawal applies to the future.

11. Retention period

We store account data, including the origin data of your registration, for as long as your account exists. We permanently store analyses and debate content as a historical record, even after your account is deleted, but without personal reference (see section 4). Server log files are automatically deleted after a short time. The sessionStorage entry for the origin is cleared when you close the tab or browser. Cookies set by Google are subject to Google's retention periods. The Meta Pixel cookies (_fbp, _fbc) have a lifetime of up to 90 days; Meta's retention periods apply to the data stored by Meta.

12. Your rights

You have the right, at any time, to:

• Access to the data stored about you (Art. 15 GDPR)
• Rectification of inaccurate data (Art. 16 GDPR)
• Erasure of your data (Art. 17 GDPR)
• Restriction of processing (Art. 18 GDPR)
• Data portability (Art. 20 GDPR)
• Objection to processing (Art. 21 GDPR)
• Withdrawal of consent you have given, with effect for the future (Art. 7(3) GDPR), e.g. via "Cookie settings" in the footer

To exercise these rights, contact team@marketjury.com. You also have the right to lodge a complaint with a data protection supervisory authority; the competent authority is the Austrian Data Protection Authority (Datenschutzbehörde, DSB).

13. Using the Market Jury app (iOS/Android)

In the app you sign in the same way as on the web, by email and password or via Google, Apple, or LinkedIn. Instead of a cookie, the app uses a technical access token for this, stored locally on your device, which authenticates you on every request to our server. You can delete your account at any time directly in the app under "Profile"; the same retention periods apply as on the web (see section 11).

If you enable watchlist or portfolio notifications, your operating system generates a device token for this (via Apple on iOS, via Google on Android), and we store this token to deliver the notification to you. We do not send push notifications unless you enable them; you can disable them at any time in your device settings or in the app, which deletes the stored token.

If you take out the Pro subscription in the app, Apple (App Store) or Google (Play Store) processes the payment through their in-app purchase system. We ourselves do not receive any payment data, only a confirmation of the purchase and its status (active, renewed, cancelled).

The app does not integrate any third-party advertising or tracking services. For the analysis feature and the other product features, the app uses the same processors listed in section 5 as the website.

14. Changes to this policy

We update this privacy policy whenever our services or the legal situation change. The current version can always be found on this page.