Privacy
Privacy Summary
This summary explains the prelaunch registry, beta testing, and the data planned for the mobile app. A professionally reviewed final policy will replace this summary before broad public launch or paid subscriptions.
Last updated: July 15, 2026
What We Collect
If you join the registry, Revela may collect your name, email address, optional phone number, contact preference, and what you are hoping Revela helps with. If you request beta access, we may also collect your device, testing focus, why you want to test, and confirmation that you are willing to send feedback.
If you submit beta feedback, we may collect your name, email, device, answers about what you tested, and your written feedback. Please do not submit private journal entries, passwords, security codes, or emergency requests through the feedback form.
If you request a church pilot conversation, we may collect the contact person's name and email, church or ministry name, leadership role, general city/state, estimated adult participant range, timing, goal, and optional organization-level notes. Church affiliation or ministry role may reveal sensitive religious information. Do not submit member names, prayer requests, counseling details, health information, or private pastoral notes.
How We Use It
We use registry information to send launch updates, beta access notes, and release announcements. We use beta access requests to decide who to invite into private testing. We use beta feedback to improve the app. If you provide a phone number, we will use it only for occasional launch-related text updates when you consent.
When you submit a beta access, beta feedback, or church-interest form, we may email you a short receipt and send a limited internal alert so an authorized operator knows the request arrived. Internal alerts omit your written feedback, testing reason, church notes, testimonial, page URL, and browser information.
We use church-interest information only to review fit, reply to the contact person, and plan a possible voluntary adult pilot. A request does not create an account, enroll members, reserve a launch date, or authorize payment.
Waitlist information is stored using our infrastructure providers so we can manage signups securely and keep the list organized during prelaunch.
Mobile App Data
The mobile app can be used in a local guest mode. Guest progress remains on that device. If you create or sign in to a configured Revela account, Revela processes your email address, profile and preferences, selected Path, guided-session and journal history, reset entries, saved Scripture activity, progress, and account-support records for private cloud backup, app functionality, and cross-device restoration.
Reflections, check-ins, journal entries, resets, and prayer-like writing can reveal sensitive spiritual, religious, emotional, or habit-related information. Revela does not sell that content or other personal data, and does not use it for behavioral advertising. Future AI use of private writing must be separately disclosed and opt-in before it is activated.
Subscriptions And Service Providers
Supabase provides account authentication and private cloud storage in configured signed-in builds. If Revela Plus is activated, Apple or Google will process the payment and RevenueCat will process purchase and entitlement information needed to provide, restore, and support Plus access. Revela does not receive full payment-card details from the mobile app stores.
Supabase and our network providers may process limited technical request metadata, such as an IP address, country inferred from network routing, user-agent or app information, and authentication or request timing. This metadata is used for authentication, fraud and abuse prevention, security, and reliable service operation, not for behavioral advertising.
Resend processes email addresses and limited message and delivery information when Revela sends requested registry confirmations or form receipts. If Resend reports a bounce, complaint, or provider suppression, Revela may keep a one-way hash of the address and minimal event metadata so later automated receipts are not repeatedly sent. Revela does not store the provider webhook payload as a shadow copy of an email.
Providers may keep limited security, transaction, tax, fraud-prevention, or legal records under their own obligations. Deleting a Revela account does not by itself cancel an Apple or Google subscription.
If the website Support Revela link is activated, Stripe will host the payment page and process payment, receipt, fraud-prevention, and related transaction information under its own privacy terms. Revela may receive limited payer contact and transaction records needed for reconciliation, support, refunds, fraud response, accounting, and legal obligations, but does not receive full payment-card details through this website.
If a supporter separately asks for public recognition, Revela may review the request against its payment records and publish only the approved display name. Recognition is opt-in. Revela does not publish the payment amount, payer email, receipt, transaction identifier, or other financial information. A supporter may ask to change or remove the display name by emailing hello@userevela.com.
Security
Revela uses access controls, encrypted network connections, provider account security, and per-user database policies intended to reduce unauthorized access. No internet service can promise absolute security. Please do not place passwords, security codes, or information needed for an emergency response in Revela.
How Long We Keep App Data
Signed-in app data is kept while the account remains active so the user can restore their private history. Account deletion removes the Revela cloud account and associated app data we control, subject to limited security, fraud-prevention, financial, or legal records that must be kept. Device-only guest data remains on that device until the user clears it, resets the app, or removes the app and its stored data.
Your Choices
You can ask us to stop sending launch emails at any time by using the unsubscribe option in a launch email once those emails begin.
Signed-in mobile-app accounts include an in-app deletion path. You can also request deletion of registry, beta, feedback, or account information by following the Revela account deletion instructions or emailing privacy@userevela.com from the same email address you used, or by clearly naming that address in your request.
During prelaunch, we aim to process deletion requests within a reasonable timeframe, typically within 14 days.
What We Do Not Do
- We do not sell waitlist information.
- We do not sell mobile-app personal data or private journal content.
- We do not use registry, beta request, or beta feedback information for ads.
- We do not sell or advertise from church-interest information.
- We do not ask church leaders to submit member lists or private pastoral information through the interest form.
- We do not use private reflections, check-ins, resets, or prayer-like writing for behavioral advertising.
- The Free-first app does not request device location, contacts, or health-record permissions.
- We do not collect full payment-card details on this website.
How Long We Keep Waitlist Data
We intend to keep prelaunch, beta, and church-interest data only as long as it is reasonably useful for prelaunch communication, beta coordination, product improvement, pilot review, and early release follow-up. If you request deletion, we will remove it from the active records we control, subject to any legal or security reasons to keep limited records.
Contact
Privacy questions can be sent to privacy@userevela.com.
Support questions can be sent to support@userevela.com.