What we store and why
We store your account email, authentication records, optional display name, preferences, daily draws, favorites, reading progress, journal entries, and drafts to provide sign-in and synchronization across devices. Your password is handled by our authentication provider; it is not shown to Daypsalm editors.
Who processes this information
Supabase provides authentication and database storage. Cloudflare hosts the website and processes web requests. Resend delivers confirmation and password reset emails. These providers process the information needed to provide their services, which can include email addresses, IP addresses, and technical logs. Their infrastructure may process data outside your country.
Private does not mean end-to-end encrypted
Other readers and content editors cannot access your journal through the app. Authorized service administrators and infrastructure providers may need access for security, maintenance, support, or legal obligations. Connections use HTTPS, but journal entries are not end-to-end encrypted. Avoid storing passwords or information you would not want held by an online service.
AI, advertising, and tracking
We do not send your journal entries to AI services. The current release does not include advertising trackers or sell journal content. Reviewed devotional content was prepared with AI assistance separately from users’ private writing.
Data on your device
Music and Scripture audio files are served by Daypsalm through Cloudflare. Playing them does not contact an external voice service or send journal text for narration. Opening an original source or license link takes you to that publisher’s website.
Browser storage keeps the sign-in session and temporary sign-in preferences. Earlier guest writing from an older version can remain on that device until you remove it; importing it into an account is optional. While writing is pending or an edit is unfinished, a temporary copy of your account writing and its last synchronized version is kept in this browser’s local storage to support recovery and conflict checks. These copies are not encrypted. They are shown only after signing in to the same account, but someone with access to your browser profile may access device storage. Copies are removed after successful synchronization or explicit discard. Signing out removes this account’s device copies after saving, or after you choose to discard pending writing. Clearing site data or closing private browsing can remove them. Use a personal browser and sign out on shared devices.
Exporting and deleting
Me provides an export of your account writing and card history. Delete account removes your active account and its private records from the application database. Downloaded exports, earlier guest writing on a device, provider logs, and backups are separate; provider retention and recovery procedures may apply to those copies. Contact us for questions about access, correction, or deletion.
Changes to this notice
This notice describes the current free release. We will update it before introducing materially different uses of personal data, paid subscriptions, or additional service providers.