Privacy Policy

1. Who is the data controller

Kenfield is developed and operated by Emre Cengiz as an individual. References to "we" / "us" in this document refer to this person. For any privacy-related request, question, or complaint, you can reach us at [email protected].

2. What data we collect

Account data: your email address and password (your password is hashed and salted by our authentication provider, Supabase Auth; we never see your plaintext password).

Profile data: your display name, your profession (chosen during onboarding), your weekly goal -- these are used to personalize the tone of weekly reports and the recommendation pool.

Your notes ("seeds"): the full text of every learning note you write in the app.

Review/recall data: your FSRS state generated during Root Test (stability, difficulty, repetition count, lapse count) -- used to calculate when your next reminder is due.

Gamification data: your XP, level, streak, and badges -- these are computed server-side and cannot be changed by the client.

Weekly report contents: the text of the synthesis (digest) and recommendation reports, stored so you can access them across devices.

Membership and usage data: your membership status and its period end date; and, if you use the Kenfield key, the number of calls, tokens and the cost incurred that month. These numbers exist to enforce the fair-use share and contain no note content.

Notification preferences: which notifications you want to receive (streak reminder, weekly report, badge) and your quiet-hours setting -- stored with your account so they work consistently across your devices.

Device-local settings: some data such as your chosen model and the "has this device already told you about this" notification dedup markers are kept only in your device's local storage and never reach our servers.

3. AI generation: two keys, two different paths

Weekly digest and recommendation reports, per-note branches, Root Test questions and reading articles are generated by a language model, and your notes' semantic similarity vectors (embeddings) are produced the same way. This sends the content of your notes to the model. Which key is used is your choice in Settings, and that choice changes the data flow, so both are written out separately below.

If you connected your own key (BYOK): your OpenRouter API key is stored only in your operating system's secure credential store (Keychain on macOS, your phone's own secure key store on mobile); it is never sent to or seen by our servers. Your note content goes directly from your device to OpenRouter and the model you chose. We do not sit in the middle of that exchange and cannot see its content.

If you use the Kenfield key (the default on the trial and on a membership): the call, including your note content, is forwarded to OpenRouter through our server (a function running on Supabase). So in this flow your note content passes through our infrastructure. We do not store that content: no copy of the request is kept once it has been forwarded, and the only thing that remains on our side is accounting data (call count, token counts and cost). We keep those numbers to enforce the fair-use share and to watch our own spend. On our organisation's OpenRouter account, zero data retention is on, prompt logging is off, and training use is off.

In both cases this use is subject to OpenRouter's and your chosen model provider's own privacy policies. We ask for your explicit consent before any data goes to an AI provider, and you can withdraw that consent in Settings at any time; without it, no note content is sent.

4. Who we share your data with

Supabase -- our infrastructure provider hosting all of your account, note, review, and gamification data (database, authentication, server-side functions).

OpenRouter and your chosen model provider -- directly from your device when you use your own key; through our server when you use the Kenfield key. The full distinction is in section 3 above.

Lemon Squeezy -- our payment provider, acting as merchant of record. If you paid through them, they collect and hold your payment and billing details; your card details never reach us. All that comes back to us is your membership status and its period end date.

Apple (App Store) and Google (Google Play) -- if you bought the membership through the store on your phone, the store takes the payment; your card details never reach us. All that comes back to us from the store is the subscription's status, product and period end date. At purchase time the store is given your Kenfield account's identifier (never your email address), so the subscription can be tied to the right account.

Resend -- to send you an email notification when your weekly report is ready (only your email address is used for this purpose).

Sentry -- app crash/error reporting, currently active only on the desktop app. Only technical diagnostic data (stack traces, OS and app version) is transmitted; your note content is never included.

PostHog -- product analytics, currently active only on the desktop app. Only anonymous/pseudonymous usage data such as screen views and feature usage counts is collected; your note content is never included.

We never sell your data, transfer it to ad networks, or share it with third-party ad trackers.

5. How we protect your data

Your OpenRouter API key is kept in your operating system's secure credential store and is never written to the local storage where settings are kept.

Every table in Supabase is protected by row-level security (RLS): only you can access your data. "Score"-like fields such as XP, level, streak, and badges cannot be changed by the client; they can only be written by a server-side trigger.

All data transfer happens over encrypted connections (HTTPS/TLS).

6. How long we keep your data

Your data is kept for as long as your account is active. When you delete your account (Settings → Account), a real deletion happens server-side; your data is permanently removed.

7. Your rights

Access and portability: with Settings → "Export your data" you can download all your notes and data to your device as JSON or CSV.

Deletion: you can permanently delete your account and all your data via Settings → Account.

Correction: you can update your profile information (name, profession, goal) directly from within the app.

Objection: you can reach us at the contact address above to object to our data processing activities or ask questions.

For residents of the European Economic Area (EEA): under the GDPR, in addition to the rights above, you also have the right to lodge a complaint with the competent data protection authority in your country. These rights follow from where you are, not from our choice of law, so the "Governing law" section below does not limit them.

For users in Turkey: you can exercise your rights under Law No. 6698 on the Protection of Personal Data (KVKK), such as requesting information, correction, deletion and objecting to processing, through the contact address above.

8. Children's privacy

Kenfield is not directed at individuals under the age of 16 and does not knowingly collect data from them. If we become aware that someone under 16 has provided us with data, we will delete it upon request.

9. Local storage

Kenfield is an app, not a website, so we do not use advertising cookies or cross-site tracking mechanisms. Some preferences (such as your chosen model, notification badges, session preference) are kept only in your device's local storage and never transmitted to any server.

10. Changes to this policy

We may update this policy from time to time. We will notify you of material changes in-app or by email. The current version always lives on this page.

11. Governing law

This policy is governed by the laws of the Republic of Turkey. This does not in any way limit your GDPR/KVKK rights set out in section 7 above.

12. Contact

For questions: [email protected]