1. Who I am
My websites and services β lps.world (including all subdirectories under /k/, /claw/, /christianalbertmueller/) and aros.ai with its subdomains β are run by me, Christian Albert Mueller, an individual based in Munich, Germany. I am the "data controller" under the EU General Data Protection Regulation (GDPR) and equivalent laws.
Schwanseestr. 47
81549 MΓΌnchen, Germany
USt-IdNr.: DE298983586
Email: hello@christianalbertmueller.com
Full contact details are in my Imprint. This policy covers these websites. The MyDays X app has its own privacy policy: mydaysx.club/privacy.
Data Protection Officer
I have appointed an external Data Protection Officer (Datenschutzbeauftragter) you can contact directly with any privacy questions:
DG Datenschutz
Franz-Joseph-Str. 11
80801 MΓΌnchen, Germany
Tel: +49 (0)800 β 6264376
Email: info@dg-datenschutz.de
Web: dg-datenschutz.de
2. What personal data I collect
Data you give me directly
- Email address β when you subscribe to a newsletter (MyDaysX Mag, Claw's Mag, Munich Talk, CTRL & CLAW Capital).
- Optional name β when you provide it in subscribe forms or write to me.
- Message content β anything you type into a contact form or send me by email.
Data collected automatically
- IP address β temporarily, in standard server access logs. On aros.ai the access log stores it shortened (the last number is replaced by 0); the full address appears only in a separate security log for suspicious requests, kept for 7 days.
- Browser type, OS, referring page, page visited, timestamp β standard server logs.
- Cookies set by my hosting/CDN for technical operation (see Cookies section).
- Newsletter open events β when your email program loads the embedded 1Γ1 pixel, my server records a shortened one-way code of your email address (the first 16 characters of its SHA-256 hash), the campaign number and the time. Since 3 November 2026 it no longer stores your IP address or your browser string; entries made before that date can still contain them and are deleted after 12 months. Because I can recompute that code from an address I already have, it counts as pseudonymous, not anonymous. Mailings to the beta list use an equivalent pixel (
aros.ai/o.php) that records only a personal token, the campaign and whether you used a phone or a computer. Apple Mail and most enterprise gateways pre-fetch the pixel before you ever see the message, so opens are a rough engagement signal, not a true read count. - Newsletter click events β links in some of my emails go through my own forwarding address, which records the click and immediately sends you on to the target page. This is either
aros.ai/r.php, which records a personal token, the campaign and whether you used a phone or a computer, or, for older mailings,aros.ai/newsletter/studio/click.php, which records the same kind of shortened one-way code of your email address, the campaign number, the clicked URL and the time. Since 3 November 2026 the older address no longer stores your IP address or browser string either (older entries can still contain them and are deleted after 12 months). The forwarding adds a few milliseconds; I do not modify or inspect the destination. - Page interaction events β anonymous "likes" and play counters on videos and music pages (e.g. The Chill Room on lps.world). When you tap the heart I store no raw IP address and set no cookie: the count uses a non-reversible, salted one-way hash of your IP address combined with the specific track, so one like counts once per person per track. The hash differs per track β no cross-page profile can be built.
Data I do NOT collect
- I do not use Google Analytics, Facebook Pixel, or any third-party advertising tracker on these websites.
- I do not sell your data, ever.
- I do not profile you for advertising.
3. Why I collect it (legal bases)
In plain words: I collect this data to run my sites, to serve you, to improve what I make, to grow it and to add as much value as I can.
Under GDPR, I rely on these legal bases:
- Consent (Art. 6(1)(a) GDPR) β for newsletter subscriptions. You can withdraw consent any time.
- Contract (Art. 6(1)(b)) β to deliver content you've signed up for.
- Legitimate interests (Art. 6(1)(f)) β for security logs, anti-spam, basic engagement metrics. I balance this against your privacy and you can object (see Your Rights).
- Legal obligation (Art. 6(1)(c)) β to retain certain logs where required by law.
Do you have to give me your data? No. Your email address is voluntary; without it I simply cannot send you a newsletter. The technical data in server logs arises automatically when you open a page. I make no automated decisions about you and do no profiling that has legal or similarly significant effects (Art. 22 GDPR).
4. How I collect it
- Subscribe forms on lps.world and its subdomains.
- Email tracking β a 1Γ1 transparent pixel + click-through forwarding links in my newsletters (see Β§ 2 above).
- Server logs: standard access logs at my web hosts (Namecheap shared hosting for lps.world, an Amazon Web Services server for aros.ai).
5. Who I share data with
I use service providers who process data on my behalf β they only get the minimum needed to deliver their service:
- AWS (Amazon Web Services) β email sending (SES), bounce handling (SNS), and hosting of the aros.ai server and database (EC2 in eu-central-1, Frankfurt). Servers in EU. AWS Privacy
- Namecheap shared hosting β primary hosting for lps.world. Namecheap Privacy
- Hetzner Online GmbH β server of the older MyDays X app (mydays.club, Finland, EU). Newsletter sign-ups stored there are copied from it to my newsletter list every day. Hetzner Privacy
- Cloudflare β network, caching and delivery (CDN) and file storage (R2) for lps.world and media.lps.world, plus, on a few pages, a cookie-free visit counter. Cloudflare Privacy
- Anthropic (Claude) β AI assistance for replies to messages you send me (see AI tools). Anthropic Ireland, Limited and Anthropic, PBC (USA) process the text on my behalf. Anthropic Privacy
- Google (Gmail, Firebase) β Gmail is the mailbox in which my e-mails arrive. On some lps.world pages a sign-in widget loads Google's Firebase scripts as soon as the page opens. Google Privacy
- My own MongoDB database (self-hosted on the AWS server) β subscriber list.
- YouTube (Google) β videos embedded on some lps.world pages. I use the privacy-enhanced address (
youtube-nocookie.com). The embedded player can contact YouTube as soon as it loads on the page, not only when you press play. Google Privacy - SoundCloud β audio players embedded on some lps.world pages (for example the music pages under
/christianalbertmueller/). When a player loads, SoundCloud receives your IP address and browser information and may set its own cookies. SoundCloud Privacy
I never share data with advertisers or data brokers.
5b. Where my emails come from
I send via Amazon SES from these verified domains:
aros.aiβ newsletters, support replies, automated mailslps.worldβ personal mails and magazine blastsmydaysx.clubβ MyDaysX product newsletters
The From address per send is chosen by me when composing (e.g. support@aros.ai, chris@lps.world). The Reply-To header matches the From. Mails sent to any @aros.ai address are forwarded by Namecheap to my own inbox.
5c. Bounce & complaint handling
Amazon SES notifies me automatically when an address bounces (hard or soft) or someone clicks "spam". Both events:
- Are recorded in my send-log (SQLite)
- Cause AWS to add the address to its account-wide suppression list β I will never try again
- Cause the address to be removed entirely from my active subscriber list within 24 hours via a daily cron sync β deleted, not merely flagged
- Leave behind only an irreversible one-way fingerprint (a hash of the address) on a small suppression list, so I can be certain never to email or re-import it β I keep no readable copy of a removed address
5d. AI tools
I work with AI tools. When you write to me (e-mail, contact form, comment, message), an AI program may read it and help me sort it, translate it and draft a reply. For replies, the text of your message and the earlier messages of the same conversation are sent to Anthropic, which processes them on my behalf as my processor (Anthropic Ireland, Limited, with Anthropic, PBC in the USA; data processing agreement with the EU standard contractual clauses, Art. 28 and 46 GDPR). E-mail addresses are removed from the text before it is sent. Anthropic's terms say it may not use this content to train its models; I cannot promise more than those terms say.
Replies written by an AI assistant are marked as AI-assisted. Decisions with a legal effect, for example about refunds or deleting your data, I make myself. If you write human only anywhere in your message, it is not given to the AI that drafts my replies, and I answer it myself.
The services between you and me, such as your e-mail provider, a messenger or the hosting companies, may use AI on their own side. I cannot control or rule that out.
Legal basis: answering your request (Art. 6(1)(b) GDPR) and my legitimate interest in answering messages promptly (Art. 6(1)(f)); you can object at any time (Art. 21). In plain words: AI & privacy. The same setup is described for the MyDays X app in its privacy policy (section 3.7).
6. Cookies & tracking
I use the absolute minimum cookies needed for the site to work:
- Strictly necessary cookies β set by the web server for session handling. Lifespan: session.
- YouTube/SoundCloud embeds β these players may set their own cookies (see section 5). I use privacy-enhanced YouTube embeds (
youtube-nocookie.com). - Cloudflare security cookie β a page delivered through Cloudflare can receive a security cookie (
cf_clearance) that Cloudflare uses to tell browsers from bots. Since 4 November 2026 I have switched this off for lps.world and for most invitation pages on media.lps.world; it can still appear on a few pages I have not changed.
You can disable cookies in your browser settings. Most of the site works fine without them.
How I count visits (cookieless analytics)
I measure page views and unique visitors on my own server β no Google Analytics, no Facebook Pixel, no third-party analytics service. For this I store nothing on your device: no cookie, no local-storage identifier.
To count a unique visitor without identifying you, my server derives a short, one-way hash from your IP address combined with a secret salt that rotates every month. Your raw IP address is never stored in this analytics, the hash cannot be reversed back to your IP, and it changes each month so you cannot be tracked over time. I also use Cloudflare's own country signal for rough, country-level geography β so your IP is not sent to any separate location-lookup service. None of this analytics data is shared with third parties.
On a few pages Cloudflare may additionally load its own cookieless "Insights" script (beacon.min.js) for aggregate reach and performance measurement. It sets no cookies and stores no identifier on your device; Cloudflare processes this on my behalf as my data processor (see section 5). Since 4 November 2026 this is switched off for lps.world and for most invitation pages.
I do not use a cookie consent banner because I don't set non-essential cookies and I don't store any tracking identifier on your device. If that ever changes, I'll add one.
Affiliate links
Some links on my sites and in my newsletters are affiliate links β for example via Digistore24, ClickBank, Impact.com, or directly with a brand. If you click one and make a purchase, I may earn a commission at no extra cost to you.
When you click an affiliate link, the partner network may set its own cookie in your browser to attribute a possible sale to me. I do not receive your payment details or your individual purchase data β only aggregate, anonymised commission reports (e.g. "3 sales this month"). The partner network is the data controller for whatever happens after you leave my site; please see their own privacy policy. I only feature products I'd genuinely recommend, and a recommendation is my opinion, not professional advice.
7. How long I keep your data
- Newsletter subscriptions: until you unsubscribe + 30 days (audit window).
- Bounced or undeliverable addresses: removed from my active list promptly (within 24 hours of the bounce, or once verified undeliverable). I keep only an irreversible one-way hash on a suppression list β never a readable address β solely to guarantee I never contact or re-import it.
- Contact form messages: 24 months, then deleted.
- Server logs (aros.ai) β kept for 14 days via standard nginx logrotate, then auto-deleted; the security log with full IP addresses is kept for 7 days.
- Server logs at my web host (Namecheap, for lps.world and mydaysx.club): the host keeps monthly log archives that can contain full IP addresses. For mydaysx.club a job removes lines older than 30 days; for lps.world no deletion job runs at present.
- Email engagement events (opens + clicks) β kept for 12 months on my server in a SQLite database and log files, then automatically deleted by a daily job. The rows are removed entirely; at most summed-up per-campaign totals without any recipient information remain.
8. Your rights
Under GDPR, CCPA, and similar laws, you have the right to:
- Access β request a copy of all data I hold on you.
- Rectify β correct inaccurate data.
- Erase ("right to be forgotten") β have your data deleted.
- Restrict processing β pause how I use it.
- Object β to processing based on legitimate interests.
- Portability β receive your data in a machine-readable format.
- Withdraw consent at any time (e.g. unsubscribe from emails).
- Lodge a complaint with your local data protection authority. In Germany: Bayerisches Landesamt fΓΌr Datenschutzaufsicht (BayLDA).
To exercise any right, email me at the address below. I respond within 30 days.
9. International data transfers
Most of my infrastructure is in the EU (eu-central-1). Where data is processed outside the EU/EEA (e.g. by AWS's US-based parent, or by Google for YouTube embeds, by Anthropic for AI-assisted replies, or by SoundCloud or Cloudflare), the transfer relies on Standard Contractual Clauses (SCCs) and adequacy decisions where available. You can get a copy of these safeguards, or be told where they are published, by emailing me.
10. Children's privacy
My content is intended for adults. I do not knowingly collect data from children under 16. If you believe a child has subscribed, contact me and I'll delete their data immediately.
11. Security
I use TLS (HTTPS) for all traffic. My subscriber database (MongoDB) and send-logs (SQLite) are kept on my aros.ai server in the EU (AWS Frankfurt, eu-central-1). Access to the data is limited to me and protected by passwords and access controls. Admin login to that server is by SSH key only; password login is switched off. No system is 100% secure β I'll notify affected users if a breach occurs that is likely to result in a high risk to their rights and freedoms (Art. 34 GDPR).
12. Changes to this policy
I may update this page when my practices or the law changes. Material changes will be announced in my newsletter. The "Last updated" date at the top always reflects the current version.
13. Contact me
Email: hello@christianalbertmueller.com
Privacy questions: privacy@christianalbertmueller.com
Franz-Joseph-Str. 11, 80801 MΓΌnchen Β· +49 (0)800 β 6264376
info@dg-datenschutz.de
I run this on my own. If you write to me about your data, you'll get a personal reply β usually within 48 hours.
I work with AI, so an AI may read what you send me. AI & privacy · KI & Datenschutz