Privacy
This page explains which data we use for your account, personal briefings and operation of the website. You do not have to provide a first or last name.
Account and personal briefings
We process your email address, optional first and last name, sign-in and consent records, interests, optional personal context, language, reading length, technical depth and delivery preferences. We also store personal editions, delivery status, feedback and bookmarks. These data provide and personalise the service (Article 6(1)(b) GDPR). Briefing delivery is based on your consent (Article 6(1)(a) GDPR). You can stop delivery using the unsubscribe link or your account. No payment data are collected and no payments are processed in the Open Beta.
Website, hosting and security
The application and its databases run on a Contabo server; deployment is managed with Coolify. Website requests involve technical connection data such as IP address, time and requested address. Sign-in, session management and abuse prevention also process security data. The purpose is reliable and secure operation, based on our legitimate interest in this (Article 6(1)(f) GDPR). We use a technically necessary session cookie for signed-in accounts (normally up to 14 days) and a cookie protecting against forged requests (CSRF). The application may keep preference drafts in local browser storage; you can remove them by clearing website data.
Optional usage analytics and technical logs
When usage analytics is enabled, we ask for your separate consent. Only then does PostHog receive page views, selected actions and where a visit came from: the address of the referring website without path or parameters, and campaign tags (utm_source, utm_medium, utm_campaign, utm_content, utm_term). The legal basis is your consent (Article 6(1)(a) GDPR, Section 25(1) TDDDG). To recognise returning visits, we store a random identifier in your browser’s local storage; we do not use cookies for this. It remains until you withdraw consent or clear website data; withdrawal removes it. Anonymous visits and signed-in activity are not linked: signing in and signing out each start with a new identifier. Signed-in activity is linked to your account using a pseudonymous technical identifier; email, name, profile and feedback text are not transmitted. Other URL parameters, sign-in tokens and session recordings are excluded. We store your choice in your browser. You can change it and withdraw analytics consent through Privacy settings. Separately, we may send fixed technical server events with method, status, route template and duration, or rendering and error categories, to PostHog. Request content, headers, user identifiers and raw error text are excluded. Transmission involves technical connection data at PostHog. Deleting your account does not automatically delete data stored there; contact us for access and deletion requests.
Operational logs and backups
Access logs contain the IP address, request method, path, status and a fixed category of the requesting software (such as search engine crawler, AI crawler or browser) derived from the user agent; the user agent itself and URL query parameters are not stored in the access log. Container logs rotate by file size (at most three files of 10 MB per container); this does not set a fixed retention period in days. System logs rotate weekly with four archived generations. The system journal has no fixed time-based deletion period. Hatchet task data are configured for 30 days of retention. Coolify deployment logs are cleaned up after 60 days, with ten older entries retained. The application and Hatchet databases are backed up daily on the same Contabo server. Backup rotation is configured for 30 days and at most 31 copies per database; time-based rotation is measured from the latest successful backup. Older copies may remain longer if subsequent backups do not succeed. Account deletion does not retroactively alter existing backups.
Email delivery
Account emails and briefings are sent through Resend, which receives the recipient address and the message content. We store the associated edition and technical delivery information. Acceptance by the delivery service does not prove that a message reached your inbox. Unsubscribe and feedback links are associated with the edition or account.
Optional Telegram
When Telegram is offered and you explicitly link your account, we store the bot and chat identifiers, displayed name and linking time. Telegram processes the messages you send and the briefings and answers we transmit. Unvalidated draft text may already appear there while an answer is generated. You can disconnect through your account or by sending /stop to the bot; this stops future Telegram delivery but does not delete messages already held by Telegram. If Telegram was your only delivery channel, email is enabled again. Account deletion removes the Telegram link and stored questions and answers from our application.
AI and public research
Microsoft Azure Foundry processes interests, optional context and preferences to interpret topics, select relevant content and write briefings. Questions in the website FAQ and about your own delivered items are also sent to this service, with item questions accompanied by the stored item and its associated evidence. We do not store a conversation history for website questions. For Telegram, we store the question, associated item, final answer and technical delivery information for the lifetime of the account; previous answers are not sent to the model as conversation history. Please do not submit confidential information about others or particularly sensitive data. For text requests we use GPT-6.1 Sol and for text embeddings text-embedding-3-small directly through Microsoft Azure Foundry. These requests use an EU data zone of a resource in Germany. Optional AI illustrations use GPT Image 2.5 Flare through a global deployment of a resource in East US 2; only public shared news content is sent for this purpose, without private reader profiles or contact addresses. Under its terms, Microsoft does not use inputs and outputs to train generative foundation models without permission or instruction. Storage of inputs and outputs for abuse monitoring is disabled on both our Azure resources; automated safety checks may still occur. This is not a guarantee that Microsoft or other involved services retain no operational metadata. Firecrawl researches public topics and sources for the shared news collection; private reader profiles and contact addresses are not research requests. Hatchet manages background tasks on our own infrastructure.
Optional additional functions
If Google sign-in is offered and you choose it, we receive the Google identifier and verified email address to sign you in or link your account at your explicit request. Google processes sign-in under its privacy terms. Optional voice input uses your browser’s speech recognition. Depending on the browser, audio may be sent to its speech recognition service; you can always type instead. When opening an external source, that website’s privacy terms apply.
Storage and deletion
Account data, preferences and personal editions are stored for the lifetime of the account. You can export your own data and delete your account; this removes the associated personal data in the application. Shared research and published articles remain. Account deletion does not remove delivered messages from your inbox or automatically delete external service logs or data in backups. Sign-in links are valid for 15 minutes. A manual cleanup command removes expired links, security counters older than a day and unconfirmed accounts older than seven days without payment records; this is not a promise of automatic deletion at those times.
Recipients and international processing
In addition to hosting, PostHog when analytics or log export is enabled, Resend and Microsoft Azure Foundry are involved in processing; Google only if its sign-in is used, and Telegram only if the Telegram feature is used. These services may process data outside the European Economic Area. You can request information about the services and transfer conditions at sebastian@simply-understood.com.
Your rights
Subject to the legal conditions, you can request access, rectification, erasure, restriction and data portability. You can object to processing based on legitimate interests for reasons relating to your particular situation. You can withdraw consent at any time for the future, without affecting earlier processing. You may complain to a data protection supervisory authority, in particular the Berlin Commissioner for Data Protection and Freedom of Information (datenschutz-berlin.de). We do not make automated decisions with legal or similarly significant effects on you; personalisation selects and writes content.