Privacy Policy

At RuahSoft, developers of DailyVerse, we respect and protect your privacy. Most of the app (daily verse, personal notes, saved verses, challenges, personal finance tracking, and preferences) works completely offline, and that data never leaves your device.

However, DailyVerse includes a section called "Community", a public prayer wall where users can post prayer requests, comments, and testimonies visible to other people in the community. Taking part in Community does not require creating any account — you simply choose a display name the first time you post or comment. (The only exception is DailyVerse's own administrators, who sign in with a WordPress.com account to access moderation tools — see section 2.1 below.) That content — along with the data needed to moderate it — is processed on external servers. This policy explains clearly what happens in each case.

1. Data we do NOT collect

Outside of the Community section, DailyVerse does not collect, store in the cloud, process, or share any personal data. We don't use advertising, we don't use third-party analytics or crash-reporting tools, we don't send push notifications, and the app has no purchases or subscriptions. Any content you create outside of Community (notes, saved verses, preferences, challenge progress, personal finance records, etc.) is kept only in your device's internal storage, and is automatically deleted when you uninstall the app.

2. Data we do process — only within Community

The data below is only generated if you choose to take part in Community. If you never use this section, nothing in this part applies to you.

2.1 Identity: guest participants and administrators

DailyVerse uses two different kinds of identity in Community, depending on who you are:

• Everyone (guest identity, no account): the first time you post or comment, the app asks you to choose a display name (free text, no password, no email, no sign-up). At the same time, your device generates a random identifier (a UUID) that stays only on your device and is sent to our backend along with your posts and comments, so we can recognize which content is yours — for example, to let you edit or delete your own posts, and to enforce daily posting limits. This identifier is not linked to your name, email, phone number, advertising ID, or any other account; it exists solely to operate Community.
• Administrators only: DailyVerse's own administrators sign in with a WordPress.com account (their own, free of charge) to access moderation tools (pinning, blocking users, managing reports). We never see or store their password — authentication is handled directly by WordPress.com. Regular users never need to create or use a WordPress.com account to participate in Community.

2.2 Content you post

• Prayer requests, comments, and testimonies you post in Community are stored on a WordPress.com blog (owned by Automattic Inc., used as our publishing infrastructure) and are publicly visible to other people in the app's community — this applies whether you post as a guest or as an administrator.
• Please do not post sensitive information you don't want made public (other people's full names, addresses, phone numbers, etc.) — our Community Guidelines explicitly ask you to avoid this.

2.3 Moderation and safety

To keep Community a safe space, our backend (hosted on Cloudflare Workers, with storage in Cloudflare KV) temporarily stores:

• Content reports: who reported what, and why — used only so an administrator can review the case.
• A list of accounts/devices blocked for violating the community guidelines — for a guest, this block is tied to their device identifier, not their chosen name, so changing names does not lift a block.
• A daily count of posts/comments per guest device or administrator account, to prevent spam.
• An internal mapping that links each post to the real identity of whoever wrote it (device identifier for a guest, or user ID for an administrator) — since all Community content is technically published through a single shared administrator account on WordPress.com, this mapping is what lets us attribute posts to their real author and apply moderation precisely.

This moderation data is kept only as long as needed (some entries automatically expire after 30 days; blocks remain in place until an administrator reverses them) and is not used for advertising purposes, sold, or shared with any third party other than those named in this policy.

2.4 Local "muting"

In addition to the blocking an administrator can apply, any user can "mute" another author within Community. This feature is purely local: your list of muted people is stored only on your own device, tied to the other person's real identity (not just their display name, so it keeps working even if they change their name), is never sent to our servers, and the muted person is never notified.

3. Third-party services involved

• WordPress.com / Automattic Inc.: hosts Community's public content, and handles sign-in for our administrators. We recommend reviewing Automattic's privacy policy.
• Cloudflare, Inc.: hosts our backend (Cloudflare Workers and KV), which processes and stores the moderation and guest-identity data described in sections 2.1 and 2.3, acting as our infrastructure provider.

We do not share your data with any other third party, use it for advertising, or sell it.

4. Data security

We apply reasonable measures to protect the information processed within Community, including encrypted communication (HTTPS) with our backend and with WordPress.com. No system is 100% foolproof, but we never store passwords (regular guest participation has none to begin with) or any kind of financial or payment data.

5. Your rights

• You can delete any of your own posts or comments directly from the app, at any time.
• You can stop using Community at any time without affecting the rest of the app, which keeps working 100% offline.
• You can delete your account and all Community-related data yourself, instantly, right from the app: go to the Community tab, tap the "⋮" menu at the top, and select "Delete account". This immediately removes all your posts and comments; for a guest, it also deletes your locally stored display name and device identifier, so the next time you take part you start with a brand-new identity. See the full detail of what gets deleted (and what doesn't) on our account deletion page.
• If you just want to use a different display name going forward, without deleting your existing posts and comments, you can do that from the same "⋮" menu with "Change name" — nothing is deleted.
• If for any reason you can't use that button, you can also request deletion by writing to the email address listed at the end of this policy.
• When you uninstall the app, all content stored locally on your device is automatically deleted (this does not include content you've already made public in Community, which remains until you delete it yourself with the button described above, or until it expires on its own 24 hours after being posted).

6. Users in the European Union (GDPR)

If you are located in the European Union and use Community, the data described in Section 2 is processed based on your consent (given when you accept the Community Guidelines and post or comment) and on our legitimate interest in keeping the community safe and free of spam or abuse. You may exercise your rights of access, rectification, or objection by writing to our contact email, and your right of erasure using the "Delete account" button described in section 5, or also by email if you prefer.

7. Changes to this policy

We may update this policy as the app adds new features. If changes are significant, we will update the date at the top of this document and, where appropriate, notify you within the app.