Last updated: October 9, 2026
This Privacy Policy explains how Adanos Software GmbH processes personal data in connection with the public website at adanos.com, the market sentiment APIs at api.adanos.com, API-key registration, paid-plan checkout, support, related public pages and embedded Adanos widgets on other websites (together, the "Service").
For visitors to websites that embed our widgets, see Section 12: Adanos Widgets on Third-Party Websites.
The controller is:
Adanos Software GmbH
Käthe-Niederkirchner-Str. 30
10407 Berlin, Germany
Email: contact@adanos.com
Phone: +49-30-54906997
When you request or manage an API key, we may process your name, email address, optional company name, intended use, plan, API-key identifier, account status, registration source and timestamps. API keys are stored in hashed form rather than as retrievable plaintext.
When the API is used, we may process the API-key identifier, request time, endpoint, request method, status code, usage count, rate-limit information, response time, IP address, user agent and security or error signals. Routine usage records are designed to measure access and reliability, not to build advertising profiles.
If you contact us or use a public form, we process the information you provide, including name, email address, message, support history and technical anti-abuse data. We also process delivery and subscription status for transactional, account, security, billing and permitted product communications.
For paid plans, we process plan, price, billing interval, transaction and subscription identifiers, payment status, checkout attribution, invoice-related data and limited billing contact information. Stripe processes payment-card details; Adanos does not store complete card numbers or card verification codes.
Professional endpoints may process text or other Customer Input submitted for analysis. The content is processed to generate the requested response and may pass through the infrastructure used for sentiment inference. Full request bodies are not intended to form part of routine endpoint-usage counters. Limited content or metadata may be processed where necessary to investigate an error, abuse or security incident.
We process page paths, referrer origin, browser and device categories, selected interaction events and technical connection data used to derive a server-side pseudonymous identifier. Section 5 explains this cookieless configuration in more detail.
To create market analysis, Adanos processes public-source data from services and publishers such as Reddit, X, financial news sources and Polymarket. Depending on the source and endpoint, this may include public usernames or handles, post, comment, article or market identifiers, limited text snippets or headlines, source links, publication times, engagement values and market metadata.
This information may concern people who do not have an Adanos account. We use it to identify financial instruments, measure public market discussion, calculate aggregates, improve data quality and provide source-level context where the applicable endpoint permits it.
We process personal data for the following purposes and legal bases under Article 6 GDPR:
Where a processing activity is necessary both to perform a contract and to protect the Service, the applicable basis depends on the particular purpose and context.
We do not sell personal data. We do not use account, API-usage or public-source data to create third-party advertising profiles or for cross-site behavioural advertising.
Adanos uses PostHog for first-party website and selected product analytics. The current public website is configured in cookieless mode: it does not store an analytics identifier in cookies, local storage or session storage.
For cookieless event association, the visitor's IP address, raw user-agent string and requested host may be processed to derive a server-side pseudonymous identifier. Before analytics events are sent, the public website removes URL query strings, fragments and common advertising identifiers, reduces the referrer to its origin and limits captured events. Automatic element-level autocapture is disabled.
We use these analytics to understand page traffic, conversion steps, errors and feature use, and to distinguish likely automated traffic from regular traffic. We do not use the resulting identifier for cross-site tracking or third-party advertising.
Personal data is disclosed only where necessary for the purposes described above, where you request it, or where required by law. Current provider categories may include:
When a third-party embed is loaded, that provider may receive technical connection data such as IP address, browser information and the requested page. Links to an external site are governed by that site's own privacy information.
We primarily use infrastructure and storage in the European Union. Some providers or subprocessors may process data outside the European Economic Area. Where required, we rely on an adequacy decision, EU Standard Contractual Clauses and supplementary safeguards appropriate to the transfer.
We keep personal data only for as long as necessary for the relevant purpose, subject to legal retention duties and the need to establish, exercise or defend legal claims. Current criteria include:
Backups are deleted or overwritten on their normal rotation schedule. Data subject to a legal hold is restricted from ordinary use and deleted when the hold ends.
We use technical and organizational measures appropriate to the risk, including encryption in transit, hashed API keys, access controls, least-privilege practices, monitoring, backups and incident-response procedures. No internet service can guarantee absolute security.
Subject to the conditions of applicable law, you may have the right to:
To exercise a right, request correction of public-source data or submit a source-content objection or takedown request, email contact@adanos.com. Please identify the relevant account, source URL or record so that we can locate it. We may request proportionate verification before acting.
Our lead supervisory authority is:
Berliner Beauftragte für Datenschutz und Informationsfreiheit
Alt-Moabit 59-61
10555 Berlin, Germany
The public API does not require analytics cookies. The first-party analytics configuration described in Section 5 does not store an analytics identifier on your device. Strictly necessary storage or security mechanisms may be used where required to provide a feature or protect a form.
Selected pages may load external charts, logos or other embedded resources. Those providers may set or access storage or receive connection data according to their own configuration and privacy terms. Some resources load automatically when a page or widget is displayed, before any interaction. Preventing those requests requires blocking or deferring the relevant resource loads, not merely avoiding clicks. Adanos widgets on other websites are described separately in Section 12.
This section applies when another website (the publisher) embeds an Adanos Ticker Tape, Top Movers, Stock Sentiment Card or Retail Sentiment Gauge using our standalone widget script. Technical data is processed when the widget loads, even if you do not have an Adanos account.
In the standard integration, your browser requests the widget script from adanos.com/embed/adanos-widgets.js and market data from public endpoints on adanos.com. Cloudflare handles delivery and network security for these requests. The Adanos data proxy communicates with api.adanos.com server-side; the widget does not connect your browser directly to Reddit, X, news publishers or Polymarket to retrieve sentiment data.
These requests expose technical connection data to the receiving service, including your IP address, request time, requested resource and parameters (such as ticker and source), browser information or user-agent, and any origin or referrer sent under your browser's and the publisher's policies. This can reveal which site or page contains the widget. Receiving these data is distinct from retaining them in logs.
Widgets displaying company logos also request images directly from cdn.brandfetch.io. Brandfetch and its delivery infrastructure receive connection data for those requests and the requested logo identifier. Ticker Tape, Top Movers and the Stock Sentiment Card load logos by default. All three support show-logos="false", which stops all Brandfetch requests from that widget. The Retail Sentiment Gauge does not load company logos.
The current widget bundle uses system fonts and does not load Google Fonts. Further information about provider processing is available in the Cloudflare Privacy Policy and Brandfetch Privacy Policy.
The standalone widget script does not itself read or write cookies, local storage or session storage, initialize the PostHog browser SDK, or send browser analytics events. It keeps market-data responses in a page-memory cache for reuse for up to five minutes, without a stored visitor identifier. Ordinary browser HTTP caching and any storage or security mechanisms used by the publisher or resource providers are separate from this in-memory cache.
This widget configuration is distinct from the website analytics described in Section 5 and from analytics the publisher may install independently. The absence of widget analytics cookies does not mean that no personal data is processed.
For Adanos' own processing, we use technical request data to deliver the embedded market information, maintain availability, diagnose errors and protect the Service against abuse. Our basis is Article 6(1)(f) GDPR: our and the publisher's legitimate interests in providing a reliable market-information feature and securing its delivery, subject to the applicable balancing of interests. This does not replace any consent required for a particular integration or device-access activity under applicable law.
Where Adanos retains widget-related security or diagnostic records, the retention criteria in Section 8 apply. The five-minute cache validity is not a server-log deletion period. Providers may have separate retention practices for their own processing, as explained in their privacy information.
CDN and logo-delivery infrastructure may involve processing outside the European Economic Area; an Adanos domain does not guarantee EU-only processing. Section 7 explains the safeguards for international transfers for which we are responsible. You may contact contact@adanos.com for information about applicable safeguards or to exercise the rights described in Section 10.
A direct embed starts resource requests when the script runs and the widget connects to the page, without requiring a click. The widget does not include a consent-management interface. Merely avoiding interaction does not prevent these requests; where prior consent is required, the publisher must prevent the relevant resources from loading until consent has been obtained.
Adanos is responsible for its own processing described above. The publisher is responsible for its choice and configuration of the embed, its privacy information, and any consent or other requirements applying to its website. Publishers should link to this widget notice and assess the actual resources loaded by their implementation. This notice does not certify every integration as GDPR-compliant or consent-free.
The Service is not directed to children under 16. We do not knowingly register children under 16. If you believe that a child has provided personal data, contact us so that we can investigate and take appropriate action.
We may update this notice to reflect changes in processing, providers, law or the Service. We will publish the revision date and provide additional notice where a change materially affects registered Users or where applicable law requires it. A Privacy Policy explains processing; it is not accepted merely through continued website use.
Questions, objections and data-protection requests may be sent to:
Adanos Software GmbH
Käthe-Niederkirchner-Str. 30, 10407 Berlin, Germany
Email: contact@adanos.com
Phone: +49-30-54906997