KERN
Deutsch

Privacy Policy

Last updated: October 27, 2026
KERN is an app for inner work - and this is first and foremost about personal things. So we handle your data the way we'd want ours handled: respectfully. This policy tells you in plain language what we store, where it goes, and what we deliberately don't do.

Quick read - you're safe here

Before the details, here's in plain language what happens in the background.

The rest of this page explains it in detail, if you want to look deeper.


1. Who is responsible?

The data controller for this app is:

Dennis Lisk
Brunnenstr. 28
10119 Berlin
Germany

Email: hello@getkern.app

For privacy questions, write directly to: datenschutz@getkern.app

2. What we store

KERN works with three layers of data:

a) What you do in the app (local on your device)

This data always lives on your iPhone - regardless of which backup option you choose:

You don't need any identifiers to use KERN - no email, no name, no phone number. The profile is anonymous on your device (for the optional Apple sign-in, see section b).

b) What our servers see in any case - even without cloud backup

For KERN to work at all (e.g. to generate AI responses, check usage limits), we need a technical identity for you. So on first app launch, KERN automatically creates an anonymous user UUID on our servers in Frankfurt. This UUID:

Alongside this UUID, our server also stores technical data: sign-in timestamps, your usage counters (for the limits of the free version) and your subscription status (whether Premium is active, until when and which plan).

Optional: secure your account with Apple. If you choose to secure your account with "Sign in with Apple" (during onboarding, when restoring, or in settings), KERN asks Apple for your email address and name. We store (in Supabase's sign-in service) the email address Apple sends us and a sign-in identifier assigned by Apple. If you choose "Hide My Email" at Apple, this is an anonymous relay address from Apple. We don't store your name. Purpose: so you can sign in again and restore your account on a new device. Your account is then no longer anonymous but linked to this email address.

c) Cloud backup

During onboarding you additionally choose whether KERN backs up your content (reflections, insights, goals, history) on our servers. The encrypted backup is the default (and preselected in onboarding). You can change this choice anytime in settings.

d) AI responses (when KERN answers you)

When KERN answers you, for example in a conversation, for new perspectives, summaries, reviews or course texts, our server sends the text needed for that to Anthropic (the company behind the Claude AI model): the text in question, plus a short context from your previous entries (e.g. your answers from the start of the app, your "About you" summary, goals, life areas, blocks, your recent insights and excerpts from your recent reflections and thoughts), so the answer fits you. No account identifier is sent - Anthropic does not learn which account the request belongs to. According to the provider's terms, Anthropic does not train on this content and usually deletes it within 30 days. Transmission runs TLS-encrypted. More details in section 4.

3. What we use this data for

We don't use your data for advertising. We don't sell it. We don't train AI on your content.

Legal basis: Art. 6(1)(b) GDPR (contract - you use the app, we provide the function) and Art. 6(1)(a) GDPR (your consent for the cloud choice).

4. Who sees your data?

We work with three processors: Supabase, Anthropic and RevenueCat. These are the only external parties that technically process your data on our behalf. In addition, Apple as the platform provider processes some data under its own responsibility (see below).

Supabase (EU)

Supabase is always active (for your anonymous UUID, see section 2.b). Your content (reflections, insights, etc.) only goes to Supabase if you've enabled cloud backup (then encrypted) or when KERN is fetching an AI response for you.

Anthropic (USA)

If the US transfer feels too uncertain despite SCC, you can continue to use the app, but AI features (KERN's conversation feature, automatic insight extraction, perspective generation) won't be available.

RevenueCat (USA)

Apple (USA)

If you sign in with Apple Sign-In, Apple handles the login. Apple sees only that you use KERN, not what you input. Purchases and subscriptions run through the App Store - your payment details stay with Apple, we don't see them. Details: apple.com/legal/privacy.

Voice input: If you speak instead of typing, KERN uses Apple's speech recognition. Apple handles the conversion to text - depending on your device and settings, directly on your iPhone or on Apple's servers. KERN doesn't store any audio recordings; only the recognized text ends up in your input field. Voice input is optional; iOS asks for your permission for microphone and speech recognition first.

5. What we measure pseudonymously - and what not

🔍 These statements are auditable. Schema, code-of-conduct and all relevant database migrations live in the public kern-legal-docs repository - with full version history and commit reasoning. If anything is different from what's described here, you can see it yourself.

So you know exactly what happens:

What we measure in numbers (pseudonymized, no content):

These numbers help us improve the app (e.g., "is the character cap too tight?", "where do users drop off?"). They land in a separate database table usage_events that by design has no text columns for content - only event type, time, category, numbers and a session identifier that is randomly generated anew each time you open the app. Your user ID is hashed together with a secret key before saving - we see "Hash-User-abc had 5 reflections", not "Anna had 5 reflections". This is pseudonymization, not anonymization: the entries are stored under a pseudonym instead of your user ID, but with the secret key it would technically be possible to check which user ID an entry belongs to. The numbers are collected regardless of your backup choice.

Schema publicly visible in our Legal repo: migrations/0005_usage_events.sql and migrations/0006_telemetry_hash_fix.sql (Repo: kern-legal-docs)

What we deliberately don't do:

6. How long we keep your data

7. Your rights (GDPR)

You have the right, anytime, to:

For all of these: send a short email to datenschutz@getkern.app. We respond within 30 days. Usually much faster.

Inside the app:

8. Right to lodge a complaint

If you believe we're not handling your data properly, you can complain to the data protection authority. For KERN, the responsible authority is:

Berlin Commissioner for Data Protection and Freedom of Information (BlnBDI)
Friedrichstr. 219, 10969 Berlin, Germany
Phone: +49 30 13889-0
Email: mailbox@datenschutz-berlin.de

9. Government requests

We only disclose data to authorities when legally required - i.e. when a German court or competent German authority compels us under valid law. In that case we notify you, to the extent legally permitted.

We do not disclose data to US authorities on US requests, because the data we store ourselves is in the EU and we are not subject to US jurisdiction.

10. Push notifications

If you enable push notifications (optional), they run entirely locally on your iPhone. Content and timing are decided on your device - no server watches along, not even Apple's. Apple sees neither that you use notifications, nor when, nor with what content.

11. Who KERN is for

KERN is meant for adults aged 18 and over. If you are younger, please don't use KERN. We don't ask for your age, and we don't knowingly collect data from anyone under 18. You can delete an existing account at any time at the very bottom of the settings.

12. Changes to this policy

If processing changes, we update this page. The date at the top tells you when the policy was last changed.

13. Contact

Questions? Concerns? Write us: hello@getkern.app

For formal privacy requests: datenschutz@getkern.app