eyv-newsbot

Privacy Policy

Last updated: 9 November 2026 · Version 8 (contact form)

In short

1. Who is responsible

The controller under the General Data Protection Regulation (GDPR) is:

Eyvind Josefsson Norell
Johann-Sebastian-Bach-Strasse 10A
85521 Ottobrunn, Bavaria, Germany
Email: [contact email]

We are not required to appoint a data protection officer (§ 38 BDSG). For any privacy question or request, email the address above. We answer within one month (Art. 12(3) GDPR).

2. Visiting the website

Server logs. When you open a page or the API, our host Vercel automatically processes what is technically needed to deliver it: your IP address, date and time, the address requested, the referring page, your browser and operating system (user agent) and the response status. We use this to deliver the website, keep it secure and fix errors, and don't combine it with other data.

Legal basis: Art. 6(1)(f) GDPR (our legitimate interest in a secure, working website). Retention: runtime logs are deleted automatically after about 1 hour on our current Vercel plan.

Protection against abuse. To stop password guessing, spam sign-ups and mass reset emails, we count attempts per IP address and per email address. These counters are deleted automatically after 15 minutes to 1 hour.

Legal basis: Art. 6(1)(f) GDPR (our legitimate interest in protecting accounts and the service).

You can read the public pages (home, documentation, legal pages) without giving us any other data.

3. Your account

If you create an account, we store:

Legal basis: Art. 6(1)(b) GDPR (providing the service you signed up for); for the Pro notification, Art. 6(1)(a) GDPR (your consent). Retention: until you remove it or delete your account. Deleting your account removes this data immediately.

Linking Trading 212 (Max, optional). If you link Trading 212 (Max), we store the API key and secret you paste, encrypted with AES-256-GCM, and use them only to read your holdings and pies from Trading 212 when you sync (we ask for read-only permissions and can't place trades). We save the imported holdings and pies (stock, quantity, value and amount invested, in your account currency) like any other pie. Your key is sent only to Trading 212. Unlinking deletes the key and the imported pies at once; you can also revoke the key in the Trading 212 app at any time. Legal basis: Art. 6(1)(b) GDPR.

4. Cookies and local storage

We set one cookie, __Host-eyv_sid, when you sign in. It holds a random session token, lasts 30 days and is deleted when you sign out; we store only a SHA-256 hash of the token. It's technically necessary to keep you signed in, so it doesn't need consent (§ 25(2) no. 2 TDDDG).

In your browser's local storage we keep your appearance setting (so pages don't flash in the wrong colours) and, if you choose it, your decision to load charts. Both stay on your device and are needed for features you asked for (§ 25(2) no. 2 TDDDG). We use no other cookies and no analytics or advertising tools.

5. Emails we send

Password reset. If you use "Forgot password?", we create a random one-time link, store only a hash of it with your email address, and send it to you through our email provider Resend. The link works once and expires after 30 minutes; asking for a new one cancels the old one. We show the same message whether or not an account exists, so nobody can use the form to find out who has an account.

Security notice. When your password is changed, we email you so you'd notice if it wasn't you.

Resend receives your email address and the email's content, and keeps delivery records (for example whether the email was delivered) under its own retention rules.

Product emails (only if you opt in). In Settings → Profile you can choose to get occasional emails about new features and plans. It's off unless you switch it on, and you can switch it off at any time there or with the unsubscribe link in each email. We store when you opted in. Legal basis: Art. 6(1)(a) GDPR and § 7(2) UWG (your consent).

Legal basis: Art. 6(1)(b) GDPR (account security is part of the service) and Art. 6(1)(f) GDPR (our legitimate interest in protecting your account). Retention: the reset link's hash 30 minutes at most.

6. Using eyv-newsbot in Claude

To use eyv-newsbot in Claude, you sign in to your eyv-newsbot account and approve the connection (OAuth). We then store:

Claude's servers (operated by Anthropic) send us requests containing the tool name and its inputs, for example a ticker like "NVDA". We don't store the content of these requests beyond the server logs in section 2. Your conversations with Claude are governed by Anthropic's Privacy Policy.

Legal basis: Art. 6(1)(b) GDPR. Retention: access tokens 1 hour, refresh tokens 30 days, request counts 2 days, app registrations 180 days after last use.

7. Bot alerts and TradingView relay

Webhooks. If you add a webhook, we store its address, the alert level you chose and a signing secret. When an alert reaches your level, we send a signed message to that address. It contains market alert information only, no personal data. Only add addresses you're allowed to receive data at.

Relay link. If you create a TradingView relay link, we store a SHA-256 hash of it with your account. Alerts TradingView sends to it are passed on, with risk information added, to your own webhooks. We don't store the alert content; it's processed in memory while forwarding.

Legal basis: Art. 6(1)(b) GDPR. Retention: until you remove the webhook or link, or delete your account.

8. Market data and news analysis

Our server collects public information to build the news feed and risk scores: the economic calendar, stock prices (Finnhub), news headlines and short descriptions from public news feeds and news APIs (for example Finnhub and Marketaux), and official releases from central banks and statistics offices (for example the Federal Reserve, the European Central Bank, the Bank of England and the US Bureau of Labor Statistics). The only things we send to these sources are the stock symbols to look up, never who asked.

To estimate which stocks a story may move, we use our own rules and, for the most important headlines, Anthropic's Claude API. Only public headlines, their short descriptions, the source name and the stock symbols we tagged are sent to Anthropic. No personal data, no account data and nothing about who reads the story is sent. When you open a headline, you go to the publisher's website, where its own privacy policy applies.

Daily briefing (Max, optional). To write your briefing, we send Anthropic's Claude API the names of your pies, the stock symbols in them with their weights and price moves, and the public headlines about those stocks. We don't send your name, email or any account details. The finished briefing is stored for up to 2 days. You can turn briefings off at any time with the switch on the briefing or in Settings → Content; then nothing is sent. Legal basis: Art. 6(1)(b) GDPR.

9. TradingView charts (only if you choose)

On Home you can choose to load price charts from TradingView, Inc. (USA). Only after you select "Load charts" does your browser connect to TradingView, which then receives your IP address and browser information and may set cookies. We remember your choice in your browser; to withdraw it, clear this site's data in your browser. See TradingView's Privacy Policy.

Legal basis: Art. 6(1)(a) GDPR and § 25(1) TDDDG (your consent). The transfer to the USA relies on your explicit consent (Art. 49(1)(a) GDPR). The USA may not offer protection equivalent to the EU's, for example in access by authorities.

10. Contact form and business enquiries

Contact form. If you write to us through the contact form, we store the topic you pick, your message, the email address you enter, your name if you give it, and, if you're signed in, your account email. We use it only to answer you; we read messages with our own eyv-newsbot connector in Claude (Anthropic), and once our email is set up we also forward them to our own inbox through Resend. To stop spam we count messages per IP address for 1 hour. Legal basis: Art. 6(1)(b) GDPR where your message is about your account or a contract, otherwise Art. 6(1)(f) GDPR (our legitimate interest in answering you). Retention: up to 12 months after our last contact, or until you ask us to delete it.

If you send a Business enquiry, we store your account email, plan, company or brand name, your message and any special requests, so we can review it and reply. We read enquiries with our own eyv-newsbot connector in Claude (Anthropic), which helps us summarise them and prepare an offer.

Legal basis: Art. 6(1)(b) GDPR (steps before a contract, at your request). Retention: up to 12 months after our last contact, or until you ask us to delete it.

Business teams and API. If a Business account adds you to its team, we store which team you belong to, and the team's main account can see your email address. Business accounts can create an API key; we store only a hash of it, its last four characters and when it was made, plus a daily request count for 2 days. Legal basis: Art. 6(1)(b) GDPR.

Sign-up overview. To understand which companies use eyv-newsbot, we look at sign-ups grouped by email domain (for example company.com), inside our own systems. We don't send advertising to anyone who hasn't opted in. Legal basis: Art. 6(1)(f) GDPR (our legitimate interest in understanding our customers).

11. Service providers and transfers outside the EU

These providers process personal data for us under data processing agreements (Art. 28 GDPR):

ProviderWhat forLocation and safeguard
Vercel Inc., 440 N Barranca Ave #4133, Covina, CA 91723, USAHosting, delivery, server logsUSA; EU–US Data Privacy Framework (adequacy decision, Art. 45 GDPR)
Upstash, Inc., USADatabase (accounts, sessions, webhooks, counters)USA; EU–US Data Privacy Framework (Art. 45 GDPR)
Resend, Inc., San Francisco, USASending password reset and security emails, and forwarding contact form messages to usUSA; EU–US Data Privacy Framework (Art. 45 GDPR) and standard contractual clauses
Anthropic, PBC, San Francisco, USAReviewing Business enquiries and contact form messages (personal data). Writing Max daily briefings (your pies' stock symbols, weights and price moves, without your name or email). News analysis uses public headlines only (no personal data).USA; standard contractual clauses (Art. 46 GDPR)

Data sources in section 8 (Finnhub, Marketaux, news publishers, central banks) aren't our processors and receive no personal data from us. TradingView (section 9) and Trading 212 (section 3) aren't our processors either: they receive data only when you choose to use them. We don't sell your data or share it with anyone else unless we're legally required to.

12. How long we keep data

DataKept for
Account (email, password hash, dates, plan)Until you delete your account
Profile (name, picture, My stocks and optional positions, appearance), Pro notification requestUntil you change or remove them, or delete your account
Daily briefings (Max)Up to 2 days
Content settings and Home layoutUntil you change them or delete your account
Trading pies and their daily valuesUntil you delete the pie or your account (daily values are kept up to 400 days)
Trading 212 API key and secret (encrypted) and imported piesUntil you unlink Trading 212 or delete your account
Webhooks, signing secrets, relay link hashUntil you remove them or delete your account
Session token hash30 days, or until you sign out, change your password or delete your account
Password reset link hash30 minutes, or until used
Claude connection tokens (hashed)Access 1 hour, refresh 30 days; invalid at once if you delete your account
Daily request counts2 days
App registrations (no personal data)180 days after last use
Business enquiries and contact form messagesUp to 12 months after our last contact
Abuse counters (sign-in, sign-up, reset)15 minutes to 1 hour
Server logs (Vercel)About 1 hour
Email delivery records (Resend)Under Resend's retention rules

If the law requires us to keep something longer (for example invoices once payments start, for 8 or 10 years under German tax law), we keep only that and restrict its use.

13. Your rights

Under the GDPR you have the right to:

You can download your data and delete your account yourself in Settings. For anything else, email the address in section 1.

You can also complain to a data protection supervisory authority (Art. 77). The one responsible for us is the Bayerisches Landesamt für Datenschutzaufsicht (BayLDA), Promenade 18, 91522 Ansbach, Germany, www.lda.bayern.de.

14. Do you have to give us data?

No law requires you to. An email address and password are needed only for an account, which the app, the Claude connector and bot alerts require. Without them, you can still read the public pages.

15. Automated decisions

Our scores, stock-effect estimates and briefings describe markets and news, not people. We make no automated decisions about you, and no profiling, within the meaning of Art. 22 GDPR.

16. Security

All connections use HTTPS. Passwords are stored only as salted scrypt hashes; session, reset and connection tokens are stored only as hashes; cookies are HttpOnly, Secure and SameSite; sign-in, sign-up and reset attempts are rate-limited; requests from other websites are blocked; and changing or resetting your password signs out your other devices.

17. Age limit

Accounts are for people aged 18 or older. If you believe a younger person has created an account, contact us and we'll delete it.

18. Changes to this policy

We update this policy when the service or the law changes; the date and version at the top show the latest one. If a change significantly affects how we use your data, we'll tell account holders by email or in the app before it takes effect.