Cookies and Browser Storage
Last Updated: 12 October 2026
Daily Selah uses essential cookies for sign-in and browser storage for the journal you choose to keep on your device. This page explains what is stored, how it is used, and how you can manage it.
Essential Sign-in Cookies
Daily Selah uses Auth.js / NextAuth to handle email magic-link sign-in. Its cookies support your authenticated session, protect the sign-in flow, and remember the page to return to after authentication.
The authentication cookies use names such as:
authjs.session-token: Identifies your signed-in session. The account session is configured for up to 30 days and may be renewed as you use the service.authjs.csrf-token: Supports protection against cross-site request forgery during authentication.authjs.callback-url: Remembers where to return after signing in.
On the HTTPS website, Auth.js uses security prefixes such as __Secure- or __Host- for these cookies. Cookie names can therefore differ from the names used in a local development browser. Authentication cookies use HttpOnly and SameSite protections; secure cookies are sent over HTTPS.
The administrator area uses a separate daily_selah_admin cookie with an eight-hour lifetime. It is set only when an administrator signs in, and uses HttpOnly, SameSite, and HTTPS protections in production.
Local Journal Storage
The daily journal uses your browser's localStorage, which is separate from cookies. This storage lets the journal remain available when you return to the same browser profile on the same device.
daily-selah.entries.v1: Your saved daily entries, including writing, dates, prompts, Scripture text and references, and word counts. The journal uses these entries to show your history and progress.daily-selah.preferences.v1: Your chosen local reminder time.cookie-consentandcookie-consent-date: Remember that you have seen the storage notice and when you dismissed it. The key name is retained from an older version of the site.
Local journal entries are not uploaded when you simply write or save on the homepage. For an account copy, sign in, open My journal, and choose Back up privately. Choosing Load account backup brings an account copy into the browser you are using. Signing in alone does not upload local entries.
Local storage normally remains until you delete it or clear site data. Your browser may also remove it, and private browsing can clear it when the browsing session ends. Local entries are not password-protected or encrypted by Daily Selah; someone with access to your browser profile may be able to open them.
Advertising and Analytics
Daily Selah currently does not load optional advertising or analytics scripts or set advertising or analytics cookies. Service providers may process ordinary request information, such as IP addresses, to host and operate the website; see the Privacy Policy for information about service providers.
If optional tracking is introduced, this policy and the site's controls will need to be updated before that tracking is enabled, including any consent choices required by applicable law.
The Storage Notice
The notice explains essential sign-in cookies and local journal storage. Selecting Got it dismisses the notice and remembers that you have seen it. It is an acknowledgement of the information, rather than a setting that enables advertising or analytics.
You can read this page or the Privacy Policy at any time from the website footer.
Managing Your Data
You can export your journal as Markdown from My journal or Settings. Keep an export of writing you want to retain before clearing browser data or moving to a different browser.
Settings lets you clear the journal entries stored in the current browser. This does not by itself delete copies previously backed up to your account. The account backup controls in My journal let you load or back up entries; for an account data request, contact hello@dailyselah.app.
Your browser's site-data or privacy settings let you remove Daily Selah cookies and local storage. Removing authentication cookies signs you out. Blocking essential authentication cookies can prevent sign-in; blocking browser storage can prevent local journal saving and remembering the notice.
Removing local storage can permanently remove local-only journal entries. Export them first if you want to keep a copy.
Contact
For questions about cookies, browser storage, or your account data, email hello@dailyselah.app.
For the broader explanation of personal data, account storage, and optional AI reflection summaries, read the Privacy Policy.