Terms of Use
Who we are
Daybook is brought to you by Deep Keep Ltd (16946046), 89 Borough High Street, 2nd Floor, London, SE1 1NL, UK.
Agreeing to these Terms
By using Daybook you agree to these Terms. If you use Daybook on behalf of an organisation, you confirm you have the authority to accept these Terms for it.
Who may use Daybook
You must be 18 or older.
Your account
Keep your info up-to-date, keep your login secure, and do not share your account. Tell us promptly if you think your account has been compromised, because you are responsible for what happens on it.
What Daybook does
Daybook keeps your entries and uses AI to turn them into new questions and reports Daybook does not take actions for you in other services.
Your content
You keep ownership of what you put into Daybook, and you can use what it produces for you as you wish.
AI can be wrong
Daybook's output may be incorrect or incomplete, so check it before you rely on it. You are responsible for how you use it.
Third-party services
Daybook relies on third-party services, including AI models from Anthropic. Their terms may also apply to you, and we are not responsible for them.
Paying
Fees are shown when you buy a Daybook subscription and are charged in British Pounds. Payments are non-refundable, except where the law requires a refund.
Changing prices
We may change our prices at any time.
Alpha or beta features
Some features are experimental and may contain errors or lose data. You use them at your own risk.
Acceptable use
Do not use Daybook unlawfully, or in a way that harms other people, or the service. Do not scrape it, reverse engineer it, or use it or its output to build a competing product or train a competing AI model.
Our property
We own Daybook, including its design and name, and you may not use them without our permission. We may freely use any feedback you give us.
Privacy
Our Privacy Policy explains how we handle your information.
Changes to Daybook
We may change or remove features at any time. Access may be interrupted for maintenance or other reasons.
Ending your account
You can stop using Daybook at any time, and you can export your entries in full whenever you like. We may suspend or close an account that breaks these Terms, and we will let you export your entries first unless that would be unsafe or unlawful.
Disclaimers
Daybook is provided "as is" and "as available", without warranties to the extent the law allows. It is not legal, medical, financial or other professional advice.
Limits on our liability
We are not allowed to limit liability for death or personal injury caused by our negligence, so we do not. For anything else, we are not liable for knock-on losses, and the most we would owe you is what you paid us in the last 12 months, or £100, whichever is higher.
Your responsibility to us
If your content or your breach of these Terms leads to a claim against us, you agree to cover our reasonable costs.
Changing these Terms
We may update these Terms and will change the date below when we do. If a change is material we will make reasonable efforts to tell you, and continuing to use Daybook means you accept it.
Governing law
These Terms are governed by the law of England and Wales. Disputes will be heard in the courts of England and Wales.
Everything else
These Terms are the whole agreement between us, and if part of them is unenforceable the rest still stands. You may not transfer them to someone else without our consent.
Contact
Email us at admin@deepkeep.org.
Updates
Last updated: 12 November, 2026.
Privacy
What is Daybook?
Daybook is a simple tool you use at the start and end of your day. You answer a set of evolving questions that grow out of your previous entries. Over time, you’ll gather a record of the “why behind your work,” providing a rich account of what you’re doing to look back on in future.
Daybook is owned and operated by a UK company called Deep Keep Ltd (16946046), 89 Borough High Street, 2nd Floor, London, SE1 1NL, UK.
You're interacting with an AI system
Daybook uses AI. Questions and reports are generated by a third-party model. You are not talking to a person.
At time of writing, Daybook runs on top of either Claude, or your own local LLM endpoint. You can choose which LLM you prefer in your account settings. That means your entries are processed externally by the LLM service you select.
What we collect
Your account
- Email address, so you can log in via a code sent to your email address
- Nickname, if set
- User ID, timezone, account settings (including your chosen LLM models & endpoints)
- Invite code generated and the user ID of people who accepted them (and the invitee’s nickname, if they have set one)
Daybook content (encrypted at rest)
- Questions shown to you
- Your answers
- Custom prompt text you save
- Any LLM keys and API endpoints supplied by you
- If you Bring Your Own Key from Anthropic or another LLM (BYOK), which models are selected for start / end of day / reporting
Technical
- Session cookie (we need this to keep you logged in)
- Server logs: See “Logs” below
- Payment data: We use Stripe to handle payments, so all Stripe-specific: customer ID, transaction ID, transaction date/time, transaction status, event summary (checkout complete, subscription active, etc.) and event duration
Sensitive information
You can write freely in a Daybook entry, but we encourage you to think carefully about sharing sensitive matters like your health or very personal things. We encrypt every entry in storage, though encryption has limits, which we set out under Limitations below. We never sell your data or use it to train models we own. You can export or delete all your data at any time.
What we do not collect
- We do not use advertising cookies
- We do not collect reports (but may in future if that’s desirable)
How we use your data
- We do not use your Daybook entries to train Daybook, or to train any models we own
- Email address and session data to create and run your account, and send login codes
- Prompts and previous questions & answers to generate questions and reports, using 1) our chosen LLM (Claude, at present), 2) Claude plus your own Claude API key, or 3) your own endpoint
- Server logs and session cookies to keep the service secure
How your inputs reach Claude
- You type your entries in the browser (https)
- Daybook encrypts then prompts/answers and stores them on our disk
- To generate questions or reports, we decrypt the content in memory, send it over https to 1) our chosen LLM (Claude, at present), 2) Claude plus your own Claude API key, or 3) your own endpoint
- The LLM API returns text; we encrypt and store that response
- To display the questions and reports we decrypt them in memory, send it over https to your browser
Anthropic does not use data sent from Daybook to its API to train their models. See Is my data used for model training? in Anthropic’s privacy hub. We do not hold a “session memory” — each call to the API endpoint only lasts for the lifespan of that single call and response.
Our data agreement with Anthropic
Anthropic is a sub-processor. Under Anthropic’s commercial API terms, Anthropic states it does not train on custom content from the API. We have enquired about using Anthropic’s Zero Data Retention, but were deemed ineligible because we’re tiny. For now. Hehe.
Encryption and storage
- Daybook entries, prompts, answers, reports, BYOK keys; encrypted at rest (Advanced Encryption Standard (AES), server key in keyring)
- Hosted in Europe with Hetzner Online; eu-central, Helsinki, Finland
- Hetzner make daily automatic backups, held for 7 days and then deleted
Limitations
- A person with root access to the server can extract the encryption key. Encryption protects against disk theft and casual access
- Content is in plaintext in memory (RAM) while generating a request. We cannot promise an operating system will never write RAM to swap disk
- We will not put questions, answers, reports etc. in the application logs
Logs
- Web server log: the time, the page requested, the status code, the size of the response, the page you came from, your browser, and your IP address. This log does not include your user id, your session id, your questions, your answers, or your API keys. It is deleted after 15 days - standard webserver stuff
- AI cost record: when Daybook calls a model, on our Claude account or on a key you supplied, we record the time, your user id, the model, the number of tokens, whether the call worked, and the kind of error if it failed. The prompt, your questions, your answers, the report, and any API key are not in this record
- We do not log: questions, answers, report text, or API keys
Your data is yours
You have our word: we’re not going to steal yours.
- We offer full data export for any account holder in JSON format
- We do not sell your data, and we do not use your data entries for marketing purposes
Account types and deletion
There are three types of Daybook accounts:
- Active: You’ve subscribed, or you’re within your 30-day free trial. Your data is retained as above
- Dormant: We haven’t received your subscription payment for 3 months, or your free trial has run out and you haven’t subscribed. We will endeavour to email you 30 days before your 3 months is up so you can export your data before the account is deleted. Dormant accounts are read-only (downloads available, no questions or reports or prompts)
- Deleted: You’ve deleted your account, or a dormant account has come to the end of the dormancy period
What happens when you delete your account
- Your Daybook entries, prompts, and reports: These will be deleted immediately you perform the action to delete your account. We will offer the opportunity to export your data before the deletion step. There is a 14-day grace period. If you log back into Daybook within this window, your account will be restored. (It may be dormant if there’s no subscription attached.)
- Your billing information: We are required to keep any billing information relating to your account for six years, in a separate database
- Back-ups: Deleted data will remain in the system back-ups for 7 days after the grace period ends and then be removed. Forever.
- Third-party services: There may be a short residual storage window even after you delete your Daybook account in third-party services
What happens if we delete an account?
- In the case of a Terms of Service violation, an account deletion will set the export clock to start, and we’ll email the address on file to notify you that you have 30 days to download your data
- If we are legally compelled to delete an account, access may be restricted or data deleted without notice, where we are legally required to do so
- Back-ups: Deleted data will remain in the system back-ups for 7 days after the grace period ends and then be removed. Forever.
If the Daybook service discontinues, or ownership changes, all account holders will be notified 90 days in advance and given the opportunity to export before the closure or transition date.
UK GDPR Processing and Controller
Deep Keep Ltd is the data controller for Daybook, because we decide how Daybook is run, what is stored, what gets sent to the LLM models and how long we keep things.
We use your account details, Daybook entries and your archives, and generate questions and reports when you use Daybook.
We also keep a web server log (the time, the page requested, the status code, the response size, the page they came from, the browser, and the IP address, kept for 15 days) and an AI cost record (the time, the user ID, the model, the token counts, and the kind of error if a call failed). Neither includes the text of your entries.
In GDPR terms, we process your Daybook data (Finland) (store it, show it to you, send what is needed to the LLM to generate questions and reports). Deep Keep Ltd (UK) is the controller of that processing. Anthropic (US) processes the generation step for us.
Definitions: https://www.legislation.gov.uk/eur/2016/679/article/4
Legal basis for processing
Your Daybook entries, reports and account data are processed to run the Daybook service you signed up for.
We do some processing on other aspects of the service like server logs so we can make sure we’re managing security monitoring, misuse prevention, or product improvement, because it’s in our interest and doesn’t come at the cost of yours.
We will ask your consent before sending you marketing content off-platform.
Changes to this policy
We may update this page from time to time. Last updated: 17 November, 2026.
Contact Us
You can write to us at admin@deepkeep.org with any comments, compliments, or complaints you may have. You certainly also have the right to complain to the UK Information Commissioner's Office.