The Redemption Project (TRP) respects your privacy. This policy describes what information we collect through the public TRP app and website, how we use it, and the choices available to you.

This policy applies to app.theredemptionproject.news and related public pages. It also covers the native iOS and Android apps published as The Redemption Project (see Native iOS and Android apps below). Store purchases on shop.theredemptionproject.news are processed by Fourthwall, which also has its own privacy practices.

The native apps published as The Redemption Project (iOS bundle and Android package news.theredemptionproject.app) do not require an account.

Version 1 of the native apps does not include advertising, analytics, or crash-reporting SDKs. Website analytics tools described elsewhere in this policy (including Google Analytics 4 and Meta measurement) are not part of the Version 1 native app binary.

The native apps fetch publicly published articles, episode pages, and media over HTTPS. They store saved items, playback position, appearance, text size, and a short content cache on the device only. Those on-device values are not uploaded to TRP servers by the mobile app.

If you choose Watch on an episode that has a public YouTube ID, playback uses YouTube’s embed player and YouTube’s terms apply to that playback.

Privacy, Terms, Support, and other public pages open in the system browser. Prayer and contact flows use the system mail composer or a public HTTPS page; the native app does not operate a private intake API in Version 1.

If you use this website, the website sections of this policy still apply.

Contact and feedback: When you submit store feedback, we may collect your name or alias, email address, feedback text, and optional email opt-in preference. Submissions are stored privately and reviewed before any public display.

Letters to the Editor: When you submit a letter, we collect legal name, preferred published name, email, phone, city/state, optional affiliation, disclosure text, letter content, and consent records. Email and phone are used for verification and editor follow-up only. Legal name and phone are not published. Only accepted letters marked published may appear publicly with preferred name and city/state.

Prayer requests: The prayer form may open your email client with a pre-filled message. TRP does not store prayer content on our servers unless a secure intake backend is explicitly enabled.

First-party usage data: TRP may collect limited interaction analytics such as page views and article, podcast, and call-to-action activity. These events use a privacy-conscious anonymous browser identifier and may include a coarse device category, operating-system family, and approximate country, state/region, and city supplied by the hosting network. TRP does not store a raw IP address, exact coordinates, complete user-agent string, name, email, phone number, private submission content, or browser fingerprint in these first-party analytics events.

Optional third-party analytics: If you choose Allow analytics, TRP loads Google Analytics 4 and Meta website measurement tools. Meta measurement may use both the browser Meta Pixel and a server-side Conversions API event for the same page view, with a shared event identifier so Meta can deduplicate the pair. These tools are not used by TRP application code when you choose Essential only.

Consented Meta server events: A server-side website event may include the page origin/path, standard request IP address and user agent, and Meta browser identifiers such as _fbp or _fbc when present. TRP does not add names, emails, phone numbers, private submission content, subscriber identities, article text, or sensitive classifications to these Conversions API events.

Campaign attribution: TRP may temporarily retain standard campaign parameters such as utm_source, utm_medium, utm_campaign, utm_content, and a Meta click identifier when present. These are used for traffic-source and campaign measurement and are not used as identity or entitlement data.

Standard hosting logs: Hosting providers may retain IP address, user agent, timestamps, and request details briefly for security, fraud prevention, reliability, and troubleshooting.

Respond to feedback, sponsorship inquiries, and support requests.

Improve TRP content, app performance, and user experience.

Measure which public campaigns and distribution channels bring readers into TRP and, where possible, whether they continue to other TRP properties such as the store.

Protect against spam, abuse, and unauthorized access.

Comply with legal obligations when required.

We do not sell or rent personal information to advertisers or data brokers.

We do not send names, emails, phone numbers, private messages, prayer requests, Letters to the Editor verification fields, subscriber identities, article text, or other private submission content to Google Analytics, the Meta Pixel, or the Meta Conversions API.

We do not use analytics data to determine reader entitlements, editorial treatment, political beliefs, religious beliefs, criminal-history status, or other sensitive classifications.

We do not expose server-only credentials such as API keys, service-role keys, social tokens, or Conversions API access tokens in the public app.

We do not send push notifications unless you opt in through a future native app release with explicit permission.

Store purchases are processed on Fourthwall. Podcast and article content may link to Substack, YouTube, Apple Podcasts, Spotify, and other platforms with their own privacy policies.

With your permission, Google Analytics 4 may receive browser-based website usage events and Meta may receive consented website events through the Meta Pixel and server-side Conversions API. Fourthwall may separately process analytics and commerce events for the TRP store according to its integrations and privacy terms.

Command Center integrations fetch and combine public-safe or account-authorized operational metrics without exposing private editorial workflows to the public site.

The public app asks before loading Google Analytics or sending TRP Meta website events. Choosing Essential only keeps those third-party analytics events disabled in TRP application code. You can change your saved choice below at any time.

Changing the setting affects future browser and TRP server-side website measurement. Third-party services may retain previously collected information according to their own retention policies.

Store feedback submissions are retained for review and customer support unless deletion is requested.

The public app may use local or session browser storage and a preference cookie for anonymous first-party analytics, campaign attribution, and your analytics preference.

Visit /account/delete or use the link below to start a deletion, correction, or access request for information you submitted directly to TRP.

You may also contact us at the email below to request deletion, correction, or access to information you submitted.

TRP is intended for a general audience. We do not knowingly collect personal information from children under 13 without parental consent.

We may update this policy as features evolve. Material changes will be reflected on this page with an updated effective date.