Privacy Policy

1. Scope

In short: This policy covers the PleasePray and RezaPorMi websites, our iOS mobile app (Android to follow), and the Beth SMS/WhatsApp assistant.

This policy applies to:

• The websites at pleasepray.app (English) and rezapormi.com (Spanish), including subdomains.
• The PleasePray and RezaPorMi mobile apps (currently iOS, with Android planned), which are native apps that present the PleasePray experience and add device features such as importing contacts to your prayer list and finding nearby parishes.
• The Beth assistant available over SMS and WhatsApp.
• Any related features such as Prayer Circle pages, prayer logging, donations, comments, prayer requests, community support ("Lend a Hand"), push notifications, and email communications.

It does not apply to third-party services we link to or that you choose to use independently (for example, Stripe's payment forms or your mobile carrier).

The Service is intended for users 18 years of age or older. See Section 8.

2. Information We Collect

In short: We collect information you provide (like your name, email, phone, prayer intentions, photos), information generated by your activity on the Service (prayers, comments, donations), contacts and location you choose to share through the mobile app, and a small amount of technical information your browser or device sends automatically.

2.1 Account information

When you create an account or sign in, we collect:

• Email address and/or phone number
• Password (stored hashed by our authentication provider — we never see your plaintext password)
• First name, last name, and an auto-generated username
• Optional profile photo
• Optional location (free text), country, timezone
• Optional parish, favorite saint, and how you heard about us
• Phone verification status and channel preference (WhatsApp, SMS, both)
• Opt-in flags for SMS and WhatsApp messaging

2.2 Prayer Circle and prayer-list content

When you create or interact with a Prayer Circle, or manage your personal prayer list, we collect:

• The circle title, intention or story you write, and any photos you upload
• The saint or Marian advocation you select as intercessor
• The circle type (intercessor, rosary, personal, or my-holy-rosary), prayer goal, dates, and category. (A former "pilgrimage" circle type was retired in September 2026; it is unrelated to the live walking pilgrimages described in Section 2.12.)
• The people and intentions you add to your prayer list — including a name, and (if you provide it) the phone number or email of the person you are praying for, so you can pray for them and optionally invite them
• For circles that collect prayer requests (personal and my-holy-rosary circles, and legacy circles of the retired pilgrimage type): prayer requests submitted to you by family and friends, including the requester's name, email, phone, and intention text — with their chosen anonymity and privacy flags
• Your prayer activity (prayers logged, comments, offerings, rosary progress, daily streaks)

If you log prayers as a guest (without an account), we generate a random session identifier so we can associate your prayers with your browser. This identifier is not tied to your real-world identity unless you later create an account.

2.3 Photos and media

Photos you upload (profile pictures and circle cover images) are stored in our hosting provider's object storage. Media you send to Beth over WhatsApp may be downloaded and attached to a Prayer Circle you are creating.

2.4 SMS and WhatsApp messaging

When you opt in to messages from Beth (our prayer assistant), we collect:

• Your phone number and the channel you chose (SMS, WhatsApp, or both)
• The exact consent text you agreed to, the time and method of your consent, and the page where you opted in (these records are kept for compliance)
• The content of messages you send to and receive from Beth, the conversation state (for example, which step of the circle-creation flow you're on), and a count of AI tokens used to process each message
• A suppression record if you reply STOP, so we know not to send you further messages

2.5 Payment information

When you make a donation or set up a creator fundraising account, payment data flows through Stripe. We do not store your full card number, CVC, or bank account number. We do store:

• The Stripe payment ID, donation amount, tip amount, fees, and the connected account (if applicable)
• For creators using Stripe Connect Express: the connected account ID and KYC/payout status flags returned to us by Stripe

Stripe collects identity and payment information directly through its own forms, governed by Stripe's Privacy Policy.

2.6 Communications and notification preferences

• Email address(es) you give us, and the per-circle notification settings you choose (frequency, quiet times, locale, channel)
• Web push subscription data (the push endpoint URL provided by your browser, plus the public keys needed to send you a notification)
• Logs of which transactional emails, push notifications, SMS, and WhatsApp messages we have sent you and whether they succeeded

2.7 Technical, device, and analytics information

When you visit the Service, we automatically receive:

• Your IP address (used to derive an approximate country code via the x-vercel-ip-country header for UI defaults and to determine which privacy-consent options to show you — we do not store the IP itself)
• Browser user-agent and device type (recorded with push subscriptions)
• Aggregate, privacy-friendly traffic analytics via Vercel Web Analytics (page views and referrers; no cross-site tracking)

Analytics consent. For visitors in the European Economic Area and the United Kingdom, non-essential analytics do not run until you agree via a consent banner. If you decline (or before you choose), we do not collect these analytics. Your choice is remembered in a cookie for about six months, and you can change it at any time. Visitors outside the EEA/UK are not shown the banner; if we cannot determine your region, we treat analytics as requiring consent by default.

2.8 AI processing inputs

When you use AI-assisted features, the following content is sent to our AI provider, Anthropic, for processing:

• Story enhancement: the raw story text you wrote and the cause category you selected
• Beth assistant (SMS/WhatsApp): the messages you send Beth, recent conversation history, and draft fields like the beneficiary's first name and intention text. Your phone number is included in system context but is not used by Anthropic to identify you
• Beth journal milestones: your first name, locale, and a short description of the milestone

Anthropic processes this content under its API terms and does not use it to train its models.

2.9 Serendipity Network identity, permissions, and people suggestions

If the Serendipity Network integration is enabled, we send first-party identity and provenance events to the PivotNorth event hub. These events may include a stable app account identifier, verified email or phone anchors used for identity resolution, the returned Serendipity global user identifier, event type, timestamp, and minimal structured metadata about Prayer Circle and prayer activity. Prayer text, Prayer Circle story text, comments, Beth messages, and prayer-request text are not sent in these Serendipity provenance events.

If you choose to connect Gmail or Outlook for people suggestions, you are redirected to the Serendipity Network / ConnectionFinder permission flow. PleasePray does not store your provider OAuth tokens. The Serendipity Network may process the mailbox or contact data you authorize through the provider permission screen to create user-scoped people suggestions and graph signals for the sharing action you requested.

Separately, our mobile app can add contacts you personally select from your device's address book to your prayer list — this is a different feature, described in Section 2.11.

2.10 Lend a Hand (community support)

If you or someone in your community turns a prayer intention into a "Lend a Hand" campaign (community support alongside prayer), we may additionally collect:

• The ways to help you enable (prayer, a monetary "Give" goal, meal sign-ups, and/or time-and-talent offers), and a short funding purpose or task description
• For meal sign-ups: the beneficiary's contact name and phone number, a drop-off address, dietary notes, and, from a helper, what they plan to bring and which day
• For volunteer/offer sign-ups: the day and time window a helper commits to and an optional note

Sensitive details such as the drop-off address and contact name/phone are stored in access-restricted tables and are shown only to the campaign creator and to helpers who have signed up for that specific need — never publicly and never to the wider parish feed. Monetary meal donations are processed through Stripe as described in Section 2.5.

2.11 Mobile app device permissions (Contacts and Location)

Our mobile app asks for two optional device permissions. Both are used only when you tap the relevant button, and you can decline either one and still use the app.

• Contacts. If you choose to add people from your phone's address book to your prayer list, the app opens your device contact picker. For each contact you personally select, we store their name and phone number as a prayer-list entry, so you can pray for them and, if you choose, send them an invite from your own phone. We only access the specific contacts you pick — we do not upload your entire address book, and we do not read your contacts in the background.
• Location. The app asks for location for two separate things, and you can decline either one on its own.
  • Finding a parish. If you tap "Use my location" to find nearby parishes, the app requests your device's approximate location. We send those coordinates to look up parishes near you and then discard them — we do not store them. You can decline and search by ZIP code instead.
  • Live pilgrimages. If you start a pilgrimage, the app records your precise location continuously — including while your phone is locked and in your pocket — until that pilgrimage ends. This is the one feature for which we store your location, and starting a pilgrimage is always something you do deliberately. It is described in full in Section 2.12.

2.12 Live pilgrimages (location while you walk)

A pilgrimage is a walk you start on purpose and end on purpose. While it is running, we collect and store:

• Your precise location — latitude, longitude, accuracy, and a timestamp — sampled every few seconds and uploaded in batches, including while your phone is locked
• The public place you chose as your starting point (a church, park, plaza, shrine, or trailhead — never a home address)
• Distance walked, how long you walked, and the route you took
• Photos you add to your pilgrimage, if you choose to (see "Photos" below)
• A short caption and the place where you finished, if you choose to add them to your finished pilgrimage's post (see "A caption and where you finished" below)
• Whether you chose to show your name on someone else's post, if you walked with them in person (see "Your name on someone else's post" below)

When recording starts and stops. Your location is not shared with anyone until you reach the starting place you picked. If you tap Start at home and walk to the church, that first leg is never shown to anyone — our servers discard those points rather than relying on the app to hide them. Recording ends when you tap End, automatically after 30 minutes without movement, or at 12 hours, whichever comes first. Sharing stops the instant the pilgrimage ends.

Who can see your live location. Only the people who were already in a Prayer Circle you chose before you set out, and people you chose from your prayer list to walk with you once they have confirmed the phone number your text was sent to (see below). Someone who joins one of those Prayer Circles after you start cannot see your map, and neither can someone who was merely forwarded the text. If you turn off "Let people walk with me in person," nobody sees the map at all — the people you chose can pray along, but not follow you. Everyone's access to your live location ends the moment the pilgrimage ends.

Your finished route on the Home feed. When your pilgrimage ends, a post about it appears on the Home feed of the same people who could follow it (those already in a Prayer Circle you chose before you set out, the people you chose from your prayer list, and you). The post shows a map of the route you walked, with the first and last few hundred meters left off, so it never shows where you set out from or where you stopped. The map image is drawn by Google Maps (Section 4.1) when someone opens the post. You are told this before you tap Start. Pilgrimages you walked before this feature existed stay private to you. The post also shows how far you walked and, if you ended the walk yourself, how long you walked. (If the walk ended on its own, no walking time is shown.)

A caption and where you finished. After your pilgrimage ends, you can add two optional things to its post. Only you, the pilgrim, can add them, and they are shown only to the people who can see the post — never to anyone you have blocked or who has blocked you.

• A caption, up to 280 characters. You can add or change it for seven days after the walk and remove it at any time. Anyone who sees it can report it; we review reports, and a caption reported by more than one person is hidden right away while the rest of the post stays. A caption that has been hidden can be removed but not replaced.
• The place where you finished. This is never taken from your GPS. You pick a public place (such as a church, park, plaza, or shrine) from a list of nearby places or by searching for it, and it has to be near where your recorded route ended. We check the place with Google Maps and store only Google's identifier for it and its name — no coordinates. To suggest nearby places, or to search near where you finished, our server sends the point where your recorded route ended to Google Maps (Section 4.1). That point is not sent to your phone or browser, or to anyone else's; you see only each suggested place's name, address, and how far it is from where you finished. You can add or change the place for seven days after the walk and remove it at any time. Naming a place tells the people who see your post roughly where your walk ended, which the trimmed map on its own does not — so leave it off if you would rather they not know.

Photos. When your pilgrimage ends, you — and anyone who met you in person during it — can add up to five photos each to its post, for up to seven days afterwards. Before a photo is stored, we remove its hidden details (such as the GPS location where it was taken). Photos are kept in private storage and shown only to the people who can see the post, through links that expire after an hour. The feed doesn't name who added a photo. You can remove any photo on your own pilgrimage, and anyone can remove their own. Anyone who sees a photo can report it; we review reports, and a photo reported by more than one person is hidden right away.

If you join someone else's walk. When you choose "Join the walk," the app uses your location on your phone only, while that screen is open, to show how far away the pilgrim is. We don't store or share it.

Your name on someone else's post. A pilgrimage post says how many people walked with the pilgrim, but it does not name them unless they say so. If you met a pilgrim in person during their walk, you get a switch afterwards: "Show my name on {pilgrim}'s post." It is off unless you turn it on, it applies to that one walk, and you can turn it off again at any time. People who only prayed along are never offered it and are never named. While it is on, your name is shown:

• to the pilgrim, on their own copy of the post; and
• to people who can see the post and already know you — someone whose prayer list you are on after accepting their invitation, someone you have added to your own prayer list, or someone in the same organization or private group Prayer Circle as you. Belonging to the same parish is not enough.

Everyone else who sees the post reads only a number ("with 2 companions"). Your name is never shown to anyone you have blocked or who has blocked you, and it is not shown to anyone if either you or the pilgrim has blocked the other.

We never show your live location publicly, share it with anyone outside the audience you picked, use it for advertising, sell it, or record your location when you are not on a pilgrimage.

Texts to people walking with you. If you choose someone on your prayer list who does not use the app to walk with you, we send that person one text message on your behalf when your pilgrimage starts, to the phone number you added for them. The text contains your first name but not your location. Its link lets them set up an account and pray for you. If you turned on "Let people walk with me in person," they can also see your live map, but only after confirming, with a code sent to that same number, that they are the person you texted. They can reply STOP to stop further texts (Section 5.4).

Keeping and deleting it. Your finished route is kept indefinitely on your You tab — it is a record of a devotion, so we do not expire it on your behalf — and, from a pilgrimage that ends with a post, shown on that post as described above. Your live position is deleted when the walk ends. You can delete any pilgrimage yourself at any time; that deletes the whole walk — its route and location points, its photos, its caption and the place you finished, its card on your You tab, and its posts on the Home feed. Deleting your account deletes all of it. If you walked with someone else, deleting your account also removes your name from their post, along with your choice to show it. Everything in this section — including a caption, the place you finished, and whether you chose to show your name on someone's post — is included in your self-service data export (Section 5.2).

Maps. Map display (including the route map on a finished pilgrimage's post), the public-place search for starting points and for the place you finished (including the nearby suggestions described above), and the travel-time estimate shown to someone walking to meet a pilgrim are provided by Google Maps Platform (Section 4.1).

2.13 Security verification (Cloudflare Turnstile)

We use Cloudflare Turnstile to verify that sign-in requests come from a person rather than an automated system. In our mobile app, this check runs invisibly, with nothing displayed on screen. Cloudflare's handling of this data is described in the Cloudflare Turnstile Privacy Addendum.

3. How We Use Your Information

In short: To run the Service, send the messages and notifications you ask for, process donations, help you and your community pray and support one another, prevent abuse, and improve PleasePray.

We use the information described above to:

• Create and maintain your account and authenticate you
• Operate Prayer Circles, prayer logging, prayer lists, comments, offerings, and prayer requests
• Add people you select from your device contacts to your prayer list, and help you invite them from your own phone
• Find Catholic parishes near you when you ask
• Record a pilgrimage you start, show it live to the people you chose, post the finished route, any photos, and the caption and finishing place you choose to add to their Home feed, show your name on a post for a walk you joined if you turn that on, and keep the route for you (Section 2.12)
• Coordinate "Lend a Hand" community support (prayer, giving, meals, and volunteer offers)
• Send you the messages, push notifications, and emails you've signed up for (milestones, daily digests, comments on your circle, prayer-request lifecycle updates, donation receipts, transactional auth emails)
• Process donations and, for eligible creators, payouts via Stripe
• Generate AI-assisted story enhancements and run the Beth assistant
• Detect and prevent fraud, abuse, spam, and violations of our Terms
• Comply with legal obligations (including TCPA recordkeeping for SMS opt-ins)
• Understand aggregate usage and improve the Service (subject to the analytics consent described in Section 2.7)
• Record first-party provenance events in the Serendipity Network when that integration is enabled
• Show people suggestions from the Serendipity Network after you grant optional provider permissions

3.1 Legal bases for EEA, UK, and similar privacy-law users

Where GDPR, UK GDPR, or similar laws apply, we rely on the following legal bases:

• Contract: to create and operate your account, authenticate you, run Prayer Circles, process donations, and provide requested features
• Consent: for optional SMS, WhatsApp, push notifications, optional communications, optional Gmail/Outlook permissions for people suggestions, mobile contacts and location access, and non-essential analytics
• Legitimate interests: to secure the Service, prevent abuse, understand aggregate usage, and maintain first-party provenance records, unless your rights override those interests
• Legal obligations: to keep required tax, payment, accounting, fraud-prevention, and messaging consent records

4. How We Share Your Information

In short: We share data with the service providers that power PleasePray, with people you choose to share your Prayer Circle with, and when the law requires it. We do not sell your data, and we do not share your mobile information for marketing.

4.1 Service providers (processors)

We share information with vendors that help us operate the Service. Each one is bound by contract to use your data only to provide its service to us.

4.2 Public Prayer Circles

If you mark a Prayer Circle as public, the circle title, story, photos, intercessor, prayer count, comments, offerings, and the creator's display name and avatar are visible to anyone who has the link or finds the circle through Explore. Comments and offerings posted publicly are visible to other supporters; you can post anonymously where the option is offered.

For circles that collect prayer requests, requests submitted by family and friends are filtered through our prayer_requests_public view, which respects the requester's is_anonymous and is_private flags before showing anything publicly.

4.3 People you invite and community helpers

When you add someone to your prayer list with a phone number or email and choose to invite them, we send that one person an invitation on your behalf. If you choose someone who does not use the app to walk with you on a pilgrimage, we also send them one text when it starts (Section 2.12). For "Lend a Hand" meal sign-ups, the drop-off address and beneficiary contact details are shared only with the campaign creator and with helpers who sign up for that need, so a meal can be delivered — never with the public or the parish feed.

4.4 Legal compliance

We may disclose information if we believe in good faith that disclosure is required by law, legal process, or a valid government request, or to protect the rights, property, or safety of PleasePray, our users, or the public.

4.5 Business transfers

If PleasePray is involved in a merger, acquisition, financing, or sale of assets, your information may be transferred as part of that transaction. We will notify you (for example, by email and a notice on the Service) before your information becomes subject to a different privacy policy.

4.6 SMS data — no sharing for marketing

No mobile information (including your phone number, SMS opt-in status, and the content of text messages) will be shared with third parties or affiliates for marketing or promotional purposes at any time.

4.7 We do not sell your personal information

We do not sell your personal information, and we do not share it with third parties for cross-context behavioral advertising. This is true regardless of where you live, including for users covered by the California Consumer Privacy Act (CCPA/CPRA).

5. Your Rights and Choices

In short: You can access, download, correct, or delete your data, and you can opt out of messages and analytics at any time.

5.1 Account controls

You can review and update most of your information at any time from your profile and settings pages. You can delete your account directly from within the app (Settings → Delete Account) or by emailing cespinoza@pleasepray.app. When you delete your account, we delete your profile, prayer content, prayer-list entries, comments, and the photos, images, and videos you uploaded, and we de-identify or remove associated personal data within a reasonable timeframe consistent with applicable law — except where we are required to retain certain records (see Section 6). If the Serendipity Network integration is enabled, account deletion also clears local Serendipity identity fields and queues a minimal deletion request so the downstream network can process erasure for records tied to your Serendipity global user identifier.

5.2 Download your data (self-service export)

You can download a copy of the personal data we hold about you at any time from Settings → Download Your Data. This produces a machine-readable JSON file that includes your profile, campaigns, prayer intentions and prayers, comments, donation metadata, notification and consent records, your pilgrimages (Section 2.12), and related data. Payment card details are held by Stripe and are not included. This satisfies your right of access and data portability.

5.3 Email preferences

Lifecycle and notification emails include an unsubscribe link. Transactional messages required to operate your account (such as security and authentication emails, and donation receipts) cannot be turned off while your account is active.

5.4 SMS and WhatsApp opt-out

Reply STOP to any message from Beth at any time to opt out of all further messages on that channel. Reply HELP for help. Once you opt out, your number is added to our suppression list and will not receive further messages unless you opt in again. You can also turn messaging off in your settings.

The exact consent disclosure shown to users when opting in is:

"By providing your number, you agree to receive messages from Beth by PleasePray. Up to 4 msgs/month. Msg & data rates may apply. Reply HELP for help, STOP to cancel."

Message frequency is up to 4 messages per month. Message and data rates may apply.

5.5 Push notifications

You can revoke web push permission in your browser at any time, disable notifications for the mobile app in your device settings, or turn push off in your in-app settings. We mark inactive push subscriptions as inactive automatically after extended non-use.

5.6 Device permissions (mobile app)

You can grant or revoke the mobile app's access to your Contacts and Location at any time from your device's system settings. Revoking access does not remove prayer-list entries you have already added; you can delete those individually in the app. Revoking location while a pilgrimage is running stops your location from being recorded or shared right away, and the pilgrimage then ends; your finished route is kept and posted as described in Section 2.12.

5.7 Analytics consent

If you are in the EEA or UK, you can accept or decline non-essential analytics through the consent banner, and change your choice later. See Section 2.7.

5.8 EEA, UK, and similar privacy rights

If you are in the European Economic Area, the United Kingdom, Spain, or another location with similar privacy rights, you may request to:

• Access the personal data we hold about you (you can also self-serve this via Section 5.2)
• Correct inaccurate personal data
• Delete personal data, subject to legal retention exceptions
• Restrict or object to certain processing
• Receive a portable copy of personal data you provided to us (see Section 5.2)
• Withdraw consent where processing is based on consent
• Lodge a complaint with your local supervisory authority, including Spain's Agencia Espanola de Proteccion de Datos (AEPD)

To exercise these rights, email cespinoza@pleasepray.app from the email address associated with your account, or include enough information for us to verify your identity.

5.9 California privacy rights (CCPA/CPRA)

If you are a California resident, you have the right to:

• Know what personal information we have collected, used, and disclosed
• Correct inaccurate personal information
• Delete your personal information, subject to certain exceptions
• Limit use of sensitive personal information (we do not use sensitive personal information for purposes that trigger this right)
• Opt out of sale or sharing — as described in Section 4.7, we do not sell or share personal information for cross-context behavioral advertising
• Be free from discrimination for exercising any of these rights

To exercise these rights, email cespinoza@pleasepray.app from the email address associated with your account, or include enough information for us to verify your identity.

5.10 Other state privacy laws

Residents of other US states with comprehensive privacy laws (for example, Virginia, Colorado, Connecticut, Utah, Texas) have similar rights to access, correct, delete, and port their personal information, and to opt out of targeted advertising and sales. We do not engage in either. To exercise your rights, contact us at the email above.

5.11 Authorized agents

You may use an authorized agent to submit a request on your behalf. We may require the agent to provide proof of authorization and may require you to verify your identity directly.

6. Data Retention

In short: We keep most data for as long as your account is active, and we keep a few specific records (like SMS consent and opt-out lists) longer because the law requires it.

When you delete your account, we delete or de-identify your personal data on the schedule above, including your uploaded media in storage. Backups are rotated on a regular cycle and any residual copies are removed in the normal course.

7. Security

In short: We use industry-standard safeguards. No system is perfect.

We use technical and organizational measures to protect your information, including encryption in transit (HTTPS), authenticated access to our database, row-level security and role-based access controls, deny-by-default isolation of sensitive fields (such as home addresses and beneficiary contacts), masking views for shared prayer requests, signed webhooks, rate limiting, and least-privilege keys for our service providers. Stripe handles cardholder data in a PCI-compliant environment that we never touch.

No method of transmission or storage is 100% secure. We cannot guarantee absolute security, but we work to mitigate risk and respond promptly to any security incident we identify.

8. Children's Privacy

In short: PleasePray is intended for adults 18 and older.

The Service is intended for users 18 years of age or older. We do not direct the Service to, and do not knowingly collect personal information from, anyone under 18. If you believe a child under 18 has provided us with personal information, please contact us at cespinoza@pleasepray.app and we will delete it.

9. Child Safety Standards

In short: Zero tolerance for child sexual abuse and exploitation. We remove it and report it.

PleasePray has zero tolerance for child sexual abuse and exploitation (CSAE). Content that sexualizes, exploits, or endangers minors in any way is strictly prohibited on our platform and will result in immediate content removal and account termination.

Reporting. If you encounter content on PleasePray that you believe violates this policy, contact us directly at support@pleasepray.app. We investigate every report promptly.

Legal compliance. PleasePray complies with all applicable child safety laws and reports confirmed CSAE content to the National Center for Missing & Exploited Children (NCMEC) and other relevant authorities as required by law.

Age requirement. PleasePray is intended for users 18 years of age or older.

10. International Users and Data Transfers

In short: PleasePray is a US-based service. If you use it from outside the US, your data is transferred to and processed in the US.

PleasePray is operated by Deo Duce Ventures Inc., a Delaware corporation in the United States. We process and store data in the United States and in the regions our service providers operate. If you use the Service from outside the United States, you understand and agree that your information will be transferred to, stored in, and processed in the United States.

When GDPR, UK GDPR, or similar laws apply, we handle service-provider processing and international transfers under applicable data-processing and transfer requirements.

We currently support sign-in and Beth messaging in countries our SMS provider permits (currently the United States, Canada, and Honduras). Creator fundraising and "Lend a Hand" community support are currently available only to creators in the United States; this list may expand over time. Donors may contribute regardless of country.

The Service is offered in English at pleasepray.app and in Spanish at rezapormi.com.

11. Changes to This Policy

In short: If we make material changes, we will tell you.

We may update this Privacy Policy from time to time. When we make material changes, we will update the "Last updated" date at the top and, where appropriate, notify you by email or a prominent notice on the Service before the change takes effect. Your continued use of the Service after the effective date of an updated policy constitutes acceptance of that policy.

12. Contact Us

In short: Email us.

If you have questions about this Privacy Policy or want to exercise any of your rights, contact:

Deo Duce Ventures Inc. (d/b/a PleasePray)

Email: cespinoza@pleasepray.app

For SMS-program-specific questions, you can also reach us at support@pleasepray.app.