Privacy.

1. Who this is and where we operate

KNEEL ("KneelDaily", "we", "us") operates kneeldaily.com and the KNEEL application. We are the data controller for the information described here. You can reach us at privacy@kneeldaily.com.

KNEEL is operated from, and hosted in, the United States, and the service is directed at users in the United States. We do not currently offer it to residents of the European Economic Area or the United Kingdom, and we have not appointed a representative under Article 27 of the GDPR. If that changes, this page changes with it. We still apply the standards below to everyone, wherever you are.

2. What we collect

If you join the waitlist

Your email address and the date you signed up. That is the whole record. We use it to send you one welcome email and to tell you when training opens.

If you create an account

• Your email address.
• A bcrypt hash of your password. We never store the password itself and cannot recover it.
• Your preferred Bible translation, and your tradition if you choose to give one.
• Whether you have finished onboarding, and the date your account was created.
• Encryption material for your vault: a random salt, and two wrapped copies of your vault key. See section 3 for what that means.

What you write

Your journal entries, your prayer list, and the daily prompts and prayers the AI Prayer Partner writes back to you. These are stored encrypted. See section 3.

If you reset your password

A SHA-256 hash of the reset token and its expiry time. The usable token exists only in the emailed link, so reading our database is not enough to reset your password.

Analytics, only if you agree

If you accept analytics cookies, Google Analytics records the pages you visit, roughly where in the world you are, and what kind of device and browser you used. If you decline, none of that is collected. See section 6.

We do not collect payment details, we do not buy data about you from anyone, and we do not run advertising.

3. Encryption, and its limits

Your journal entries, prayer list, and AI-written content are encrypted in your browser with a key derived from your password, before they are sent anywhere. What reaches our database is ciphertext. We hold your vault key only in wrapped form, which is useless without either your password or your one-time recovery code. Neither of those is ever sent to us.

In practice that means our engineers cannot read your journal, our database administrators cannot read your journal, and we cannot produce readable copies of it in response to a request from anyone, including law enforcement. We would have nothing to hand over but ciphertext.

The one exception you should understand

The AI Prayer Partner has to be able to read your writing in order to respond to it. When it generates your daily prompt, a reflection, or a written prayer, your browser decrypts the relevant content and sends it to our server, which passes it to our AI provider (see section 7). This is limited to:

• up to your five most recent journal entries, individually truncated;
• up to five active prayer list items;
• how many days it has been since your last entry, and your translation and tradition.

That decrypted text is held in memory for the length of the request and then discarded. It is never written back to our database in readable form. The response comes back to your browser, is encrypted there, and only then is it stored. If you never use the AI Prayer Partner, your writing is never decrypted outside your own browser.

If you lose both your password and your recovery code

Your content cannot be recovered. Not by you, and not by us. That is the direct cost of us not holding a key, and we would rather say it plainly than surprise you later.

4. Why we are allowed to use it

• To provide the service you asked for — your account, your content, the daily prompt. Without this we have no product to give you.
• Our legitimate interest in keeping the service secure, preventing abuse, and fixing things that break.
• Your consent — for analytics cookies, and for the waitlist email. You can withdraw either at any time.

5. How long we keep it

• Waitlist emails: until launch, or until you ask us to remove you.
• Account and content: until you delete your account, at which point your entries, prayer items and prompts are deleted with it.
• Password reset tokens: they expire automatically and are single-use.
• Analytics: retained by Google for the period set on our property, currently two months, which is the Google Analytics default.

6. Cookies

We use as few as we can get away with.

• Strictly necessary. A session cookie that keeps you signed in, and kneel_consent, which remembers your answer to the cookie banner for 180 days. These are set without asking, because the site cannot work without the first and cannot honour your choice without the second.
• Analytics. Google Analytics cookies, set only after you press Accept. We use Google Consent Mode v2 with analytics storage denied by default, so nothing is stored and no analytics identifiers are created until you agree.

We set no advertising cookies at all. You can change your answer at any time: reopen your cookie choices.

7. Who else touches your data

We keep this list short deliberately, and we will update it here when it changes. All of these are service providers acting on our instructions.

• Vercel — hosts the application. United States.
• Neon — runs our PostgreSQL database, where your ciphertext lives. United States.
• Resend — sends transactional email: the waitlist welcome and password resets. Receives your email address only.
• Gloo AI — generates the daily prompt, reflections and written prayers. Receives the decrypted excerpts described in section 3.
• Google Analytics and Google Tag Manager — measurement, and only if you accepted analytics cookies.

We do not sell your personal information, and we do not share it for cross-context behavioural advertising.

8. Your rights

You can ask us to:

• give you a copy of the data we hold about you, in a portable format;
• correct anything that is wrong;
• delete your account and everything attached to it;
• restrict or object to how we are using it;
• withdraw a consent you previously gave.

Email privacy@kneeldaily.com and we will respond within 30 days. Note the limit set by section 3: we can delete your encrypted content, but we cannot produce a readable copy of it, because we cannot read it. You can export it yourself from inside the app, where it is decrypted.

If you are in a jurisdiction with a data protection authority and you think we have handled your data badly, you have the right to complain to them. We would rather you told us first.

9. Children

KNEEL is not intended for anyone under 13, and we do not knowingly collect data from children under 13. If you believe a child has given us information, email us and we will delete it.

10. Security

Passwords are hashed with bcrypt. Journal content is encrypted client-side with AES-256-GCM under a key derived from your password using PBKDF2-SHA256 at 600,000 iterations. Traffic is served over HTTPS. Password reset tokens are stored only as hashes and expire.

No system is perfect, and we will not pretend otherwise. If we ever suffer a breach that puts you at risk, we will tell you.

11. Changes

If we change this policy in a way that materially affects you, we will update the date at the top and, for anything significant, tell you by email.

12. Contact

privacy@kneeldaily.com