Privacy Policy

Effective date: 12 August 2026 (last updated 12 August 2026)

Enkel ("we," "us") operates enkelapp.com. This policy explains what happens to information when you use the service. It is written to describe what Enkel actually does today, not what it might do later — if that changes, this policy will be updated and the date above revised.

The short version

Enkel does not require an account for anything — accounts exist but are optional, and nothing is gated behind one. We do not store your task descriptions, and we do not sell or share your information for advertising. Task descriptions are sent to Google's Gemini API to generate your step breakdown, and are not retained by us or, per our configuration, by Google.

What we collect

Task descriptions and answers you type. When you enter a task and answer follow-up questions, that text is sent to our server and forwarded to Google's Gemini API to generate your step-by-step breakdown. We do not store it in any database. Once your response is generated and returned, we do not retain a copy.

Standard server logs. Our hosting providers (Vercel for the website, Render for the backend) automatically record technical information common to all web services: IP address, browser type, timestamps, and which pages or endpoints were requested. These logs exist for security and reliability purposes and are handled under those providers' own policies.

Feedback you choose to send. If you answer the optional question on the completion screen ("Did the steps feel right?"), we record your answer together with structural information about that breakdown: a randomly generated task identifier, the task category, whether the session was scoped, how many steps it contained, and how long it took against the estimate. Your task description and your answers to follow-up questions are not included — the feedback record is built from a fixed list of fields that does not contain them. If you also type an optional note, that note is recorded as written, so please do not put anything in it you would not want kept. Feedback is stored in our database and kept for up to 24 months. Answering is entirely optional and nothing about the product changes if you skip it.

If follow-up questions were asked, the completion screen also asks whether those questions felt worthwhile. That answer is recorded with the same structural information plus how many questions were asked — never the questions themselves, since a follow-up question is generated from your task description and would reveal it.

Anonymous usage events. To understand where people get stuck, we record a small, fixed set of events as you move through a task: that a task was submitted, that follow-up questions were shown and answered, that a breakdown was shown, that the first step was completed, that a step was skipped, and that a task was finished. Each event records only a random identifier for that one attempt, the task category, how many steps or questions were involved, and the time it happened.

These events contain no task content and nothing that identifies you. No task description, no answers, no step text, no IP address, no device or browser information, no advertising identifiers. The random identifier is created fresh each time you start a task, is held only in your browser's memory, and is discarded when you reload the page or begin another task — it is not a cookie and it is not stored on your device. Because of that, we cannot connect two of your tasks to each other, or any task to you. Usage events are deleted after 180 days.

Account data, if you create an account. Accounts are optional and nothing requires one. What is held, by whom, and how deletion works is set out in "If you create an account" below.

Local browser storage and cookies. Enkel stores your light/dark preference in your browser's local storage; it stays on your device and is never transmitted to us.

Separately, our authentication provider Clerk sets its own cookies and local-storage entries as soon as the page loads, whether or not you sign in — they are how a signed-in browser is told from a signed-out one. These are functional, not advertising cookies. We set no advertising or cross-site tracking cookies of any kind. All of it can be cleared through your browser settings.

What we do not collect

• We never store names, email addresses, or passwords ourselves. Accounts are optional and handled entirely by Clerk — see "If you create an account" below.
• We do not use advertising trackers or third-party analytics. Our authentication provider's SDK reports anonymous usage statistics to its vendor by default; we have turned that off.
• We do not sell, rent, or share personal information with third parties for their own marketing.
• We do not build profiles about you. Signing in necessarily identifies you to Clerk while you stay signed in, but we do not use that to build a profile, and we never link it to your task activity.

If you create an account

Accounts are optional and gate nothing. The whole task flow works signed out, and account creation is only offered *after* you have finished a task — never as a condition of starting one.

Clerk is our authentication provider and the system of record for your identity. When you sign in by email or with Google, Clerk holds what it needs to authenticate you: your email address, and any name or profile image your sign-in provider supplies. That information lives in Clerk's systems under Clerk's own privacy policy. It is not copied to us.

Our own database stores two things about an account: an opaque Clerk user ID and the time it was first seen. Nothing else, permanently. There is no email address, no name, no display name and no avatar URL in our database. That is a deliberate design decision rather than a gap waiting to be filled: a Clerk user ID is a meaningless string without Clerk, so a breach of our database would expose nothing about any person.

Your account is not linked to your tasks. The anonymous usage events described above carry a per-attempt identifier that is never joined to an account, so signing in does not create a task history — there is nothing on our side for an account to be connected to.

Deleting your account. You can delete it at any time from your account settings, which are handled by Clerk. Clerk removes your identity data and notifies our server, which deletes the single row we hold. Because that row is everything we store about an account, deletion is finished when it is gone — there is no cascade of other records, and nothing is kept afterwards.

Third-party processing

Google Gemini API. Your task description and follow-up answers are transmitted to Google to generate the breakdown. We have deliberately disabled request storage for this API, meaning Google is not retaining the contents of these requests for observability purposes. Google's own terms govern their handling of API requests.

Clerk (authentication). Clerk provides sign-in and holds the identity data described above for anyone who creates an account. Its SDK loads on every page — including for signed-out visitors — and sets the functional cookies described above. We have disabled the anonymous usage telemetry its SDK would otherwise send to Clerk, so the only requests it makes are the ones needed to establish whether you are signed in. Clerk's own privacy policy governs what it collects and retains for account holders.

Hosting providers. Vercel and Render process requests in order to serve the site, and maintain standard operational logs as described above.

Sensitive information

People sometimes describe personal circumstances when entering a task — health situations, financial matters, legal issues. Please avoid entering information you would not want transmitted to a third-party AI service. While we do not store task contents, they do pass through Google's API in order to be processed. Enkel is not a medical, legal, or financial service and should not be used to handle confidential records.

Children

Enkel is not directed to children under 13, and we do not knowingly collect information from them. If you believe a child under 13 has provided information through the service, contact us at the address below.

Do Not Track signals

Some browsers can send a "Do Not Track" signal indicating you do not wish to be tracked across websites.

Enkel records the anonymous usage events described above, so it would be inaccurate to say we collect nothing. But those events use no cookies, no device or browser fingerprint, and no identifier that outlives a single task, and they are never shared with anyone. There is no third-party analytics or advertising service involved, and nothing that could follow you to another website or link one visit to another. Signing in does involve cookies, but they are functional ones set by Clerk to keep you signed in, not tracking cookies, and they are not shared with anyone else. There is therefore no cross-site or over-time tracking for a Do Not Track signal to disable, and Enkel behaves the same way whether or not you send one.

California residents

Enkel is operated from California. We do not sell or share personal information as those terms are defined under California law, and we do not disclose personal information to third parties for their direct marketing purposes.

The California Consumer Privacy Act (CCPA/CPRA) applies to businesses meeting certain size or data-volume thresholds. Enkel does not currently meet those thresholds. Regardless, we store no task contents and build no profiles. The only account data we hold is an opaque identifier issued by Clerk, which means nothing without Clerk; your name and email address, if you provided them, are held by Clerk rather than by us, and a request to access or delete them is handled there. Deleting your account removes both — Clerk's copy and our single row. If any of this changes, this policy will be updated before the change takes effect.

Your choices

Enkel does store feedback and anonymous usage events, and neither is tied to you — including if you have an account. They are never stored alongside your IP address or your account, and the identifier attached to usage events is discarded when you reload or start another task. That means we have no way to find "your" records in order to show or delete them — not as a matter of policy, but because the link genuinely does not exist.

If you have an account, you can delete it at any time from your account settings; that removes your identity data from Clerk and the one row we hold, as described above. You can clear browser-stored preferences at any time through your browser. If you have a question about data handling, contact us.

Changes

This policy may be updated as Enkel adds features — particularly as saved tasks or payments are introduced. Material changes will be reflected in the "last updated" date above, and where appropriate, noted in the app.

Contact

Questions about this policy: support@enkelapp.com