Agentic Coding Digest

Privacy Policy

Agentic Coding Digest has no accounts, no login, and no user profiles. It collects three things: a notification token, if you turn notifications on; anonymous usage counts from the app; and a count of how often each edition is read on this website. This page explains all three in full.

Last updated 12 August 2026 · Applies to the Agentic Coding Digest iOS app and this website, including the editions published here

1. Who is responsible

The controller for the processing described here is:

Kwandro – Remington Vörtmann
Mesterkamp 36
22083 Hamburg
Germany
Email: kontakt@kwandro.de

For any question about this policy, or to exercise any of the rights in section 9, email the address above.

2. What we do not collect

Stating this plainly, because it is most of the answer:

3. Notification tokens

If you turn on notifications, iOS issues the app a push token — a long random string that identifies your installation to Apple's Push Notification service. We store that token on our server so we have somewhere to send the digest.

Stored alongside the token, and nothing else:

FieldExampleWhy
platformiosWhich push service to send through
environmentproductionSandbox vs production push routing
dailyEditiontrueWhether you want the daily digest
breakingAlertsfalseWhether you want breaking alerts

A push token identifies a device installation, not a person. We cannot use it to learn who you are, and we have nothing to connect it to — there is no account for it to belong to.

Legal basis: your consent, given through the iOS notification permission prompt and the toggles in the app's Settings screen (GDPR Article 6(1)(a)).

How to stop it: turn the toggles off in the app's Settings screen, or switch notifications off for Agentic Coding Digest in iOS Settings. Either way we stop sending to you. To have the token itself removed, delete the app: Apple then reports it as no longer valid, and we delete the record.

Retention: we keep the token while the app is installed. When Apple tells us a token is dead — which happens the first time we try to send to a device that has uninstalled the app — we delete it immediately rather than keep it. Because a send is attempted daily, that is normally within a day of you deleting the app.

4. Anonymous usage analytics

We count which stories get read so we can tell whether the digest is any good. This runs only in the released App Store build — development and test builds send nothing.

Analytics are handled by PostHog, on their European infrastructure (eu.i.posthog.com), acting as our processor.

What an event contains

Each event carries a random identifier that PostHog generates on your device. It is not derived from your hardware, it is not shared with any other app, and we never call the SDK's identify() function — so the identifier is never linked to a name, an email, or any account. Alongside it:

PostHog's SDK also attaches your device model, operating system version, and approximate country, derived from your IP address. Your IP address itself is used in transit and is not stored against events.

The complete list of events

The app can send these events and no others. The list is fixed in the source code — there is no mechanism for the app to invent a new one.

EventSent when
edition_openedYou open a daily edition
item_readA story is on screen long enough to count as read
item_tapped_throughYou open a story's original source
item_savedYou save a story
item_unsavedYou remove a saved story
item_skippedYou scroll past a story without reading it
edition_caught_upYou reach the end of an edition
share_initiatedYou open the share sheet for a story
share_completedYou complete a share
archive_edition_openedYou open a past edition from the Archive
saved_item_openedYou open a story from your Saved list

Legal basis: your consent (GDPR Article 6(1)(a)).

How to stop it: delete the app. Analytics are sent only while it is installed, and nothing is collected in development or test builds. We are working on an in-app switch so you can turn analytics off without uninstalling; this page will be updated when it ships.

Retention: events are kept for 30 days, then deleted.

5. Counting reads on this website

Every edition is published on this website as a web page, readable by anyone with no app and no account. We count how often each edition is read, and how often a shared link is opened. This counting happens on our server, as the page is built, and not in your browser.

That distinction is the whole of it. Nothing is placed on your device for this purpose and nothing about the counting runs in your browser: no cookie, no local storage, no analytics script, no tracking pixel, no fingerprinting. By the time the page reaches you, the count has already happened.

The scripts on the page, and what they do. There are two, both written by us and both served from this domain. Neither sends anything anywhere, neither reads anything about you, and neither has any part in the counting described above.

The first is the light and dark switch in the corner of every page. When you press it, your choice is saved in this website's own local storage, under the name acd-theme, so the next page you open is the colour you picked. That entry holds one word — light or dark — it never leaves your browser, it is never sent to us or to anyone else, and it says nothing about you beyond which of two colours you prefer. Clearing your browser's site data for this domain removes it, and the site keeps working without it: it just goes back to being dark.

The second is on edition pages only, and is included in the page itself rather than fetched. It does exactly one thing: it reveals the "Copy link" and "Share" buttons on a story, but only if your browser actually supports them, so you are not shown a control that would do nothing. When you press one it calls your browser's own clipboard or share feature.

With JavaScript turned off, every page reads exactly the same, minus the colour switch and those two buttons; the site is dark, and the plain share links beside the buttons are ordinary links and are always there.

The share links on a story point at X, Hacker News and LinkedIn. They are links and nothing more: nothing is loaded from those companies, and they learn nothing about you unless you actually click one, at which point you are on their site under their rules.

What each event contains

EventSent whenWhat it carries
web_edition_viewedAn edition page is rendered for a readerThe edition's date, its number, and how many stories were in it
share_link_clickedSomeone opens a shared link to a storyThe edition's date, which story, its position in the running order, and the publisher it came from

That is the entire contents. Note what is absent: no IP address, no user agent, no referrer, no session, no country, no device, and nothing at all about you.

Why this is not personal data

We count pages, not readers. Three things are true of every one of these events, and all three are enforced in one place in our code so that no event can be sent without them:

The result is that no event here can be traced back to you, and no two events can be connected to each other, by us or by anyone else. There is no key to join them on. That means these events contain no personal data, which is why reading this website needs no consent from you and why there is no cookie banner in your way.

The price of this, and it is a real one we accept deliberately, is that we cannot tell how many people read an edition, only how many times it was read. We would rather have the weaker number than the identifier it would take to get the stronger one.

How to stop it: there is nothing to stop and nothing to opt out of, because nothing about you is being recorded. If you would rather not be counted at all, do not open the page. A request that never arrives is never counted, and there is no other switch we could honestly offer you, because we would have no way of recognising you to apply it.

Retention: these events are kept for 30 days, then deleted, the same as the app's.

Requests to this website also appear in our hosting provider's standard server logs, which is section 6.

6. Where the data goes

RecipientWhat they receiveWhere
Apple (APNs)Notification content and your push token, to deliver a notificationApple infrastructure
ALL-INKL.COM (Neue Medien Münnich)Every request to this website, in standard server logsGermany
Microsoft AzureOur backend: the stored push tokens, and the rendering of every edition page this website servesWest Europe (Netherlands)
PostHogThe analytics events listed in sections 4 and 5European Union

What one page request actually touches

Worth stating as one path rather than as two systems, because the site is no longer a set of uploaded files. When you open an edition on this website:

  1. Your request reaches ALL-INKL in Germany, which is the only thing this domain points at.
  2. ALL-INKL forwards it to Azure in the Netherlands, which builds the page from the published edition and hands the HTML back.
  3. ALL-INKL returns that HTML to you. Your browser never contacts Azure and never leaves this domain.

Both hops stay inside the European Union. The privacy documents themselves, the pages you are reading now, are the exception in the other direction: they are ordinary files sitting on ALL-INKL and are served without the second hop at all, so they remain readable even when our backend is not.

Each of these acts as a processor on our instructions, under a data processing agreement. Where a transfer outside the European Economic Area occurs, it is covered by the European Commission's Standard Contractual Clauses.

7. Children

Agentic Coding Digest is a technical news digest for professional software developers. It is not directed at children, and we do not knowingly collect anything from a child under 16.

8. Security

All traffic between the app and our servers, and all traffic to this website, is encrypted in transit using HTTPS. Stored push tokens are held in access-controlled infrastructure. No system is perfectly secure, but there is very little here worth attacking: we hold no names, no email addresses, no passwords, and no payment details.

9. Your rights

Under the GDPR you have the right to access your data, correct it, have it erased, restrict or object to its processing, and receive it in a portable form. You may also withdraw consent at any time, without affecting processing that already happened.

An honest limitation. Because there is no account, we usually cannot connect any stored record to you as a person, and we are not required to collect extra information simply to make that possible (GDPR Article 11). In practice the fastest route to erasure is in your own hands: deleting the app removes the push token, and deleting the app stops analytics. If you write to us with the specifics, we will do what we can to identify and delete a record — please tell us roughly when and on which device.

You also have the right to complain to a supervisory authority. In Germany, that is the Hamburg Commissioner for Data Protection and Freedom of Information (Der Hamburgische Beauftragte für Datenschutz und Informationsfreiheit).

10. About the content itself

Agentic Coding Digest summarises publicly available announcements and links to the original source. Summaries are produced with automated assistance and may contain errors — always treat the linked original as authoritative. See the source list for everything the digest reads, and the terms of use for the full position on accuracy and attribution.

Every edition is now published on this website as well as in the app, so a summary of an announcement is public and indexable. If you published something we summarised and you want the summary removed, the route is in the terms of use, and we will not ask you to justify the request.

11. Changes to this policy

If this policy changes materially, we will update the date at the top of the page and, where the change affects what we collect, note it in the app's release notes. Continuing to use the app after a change means you accept the updated policy.