Skip to main content
Reprieve
  • Reprieve
  • Homebase
  • Support
  • Privacy
Homebase LoginBecome a Pathfinder

Privacy Policy

How Reprieve handles personal information across its website, resident app, and Homebase services.

Last updated: August 28, 2026

About This Policy

This Privacy Policy describes how Reprieve ("Reprieve," "we," "us," or "our") collects, uses, discloses, retains, and protects information when you use the Reprieve website, the resident-facing Reprieve application, Reprieve Homebase, and related communications and services (collectively, the "Services").

Recovery, wellness, housing, communication, location, and payment information can be especially sensitive. We limit our collection and use of that information to operating, securing, supporting, and improving the Services, carrying out user and organization instructions, and meeting legal obligations. The Private Recovery Data described below is excluded from the information Reprieve collects or receives.

Information We Collect

The information we collect depends on how you use the Services and may include:

  • Account and profile information. Name, email address, chosen username, confirmation that you meet the minimum age, profile image, account settings, and authentication records. We do not receive or store your password in readable form.
  • Website and waitlist information. First and last name, email address, requested username, product interest, confirmation status, feedback preference, and any optional phone number, organization name, organization role, or recovery-residence information you submit. When you reach a signup page through a campaign link, we may also retain limited campaign and content attribution labels with your request so we can understand which outreach leads to signups. People creating or sharing campaign links should use opaque, non-identifying labels and should not include names, email addresses, recovery status, health details, or other sensitive information in those labels.
  • Recovery-related information you intentionally submit.Information you separately choose to send through a connected feature, such as a community post, private message, meeting or organization check-in, housing record, or support request. This category does not include Private Recovery Data, which Reprieve does not collect or receive.
  • Community and communication information. Forum posts, replies, chosen username, optional profile image, Community Guidelines acknowledgment version, opaque community-author identifier, content reports, private blocked-member records, bulletin posts, private messages, participants, and related timestamps and moderation records.
  • Location and check-in information. With device permission, location is used only after you initiate a supported meeting or curfew check-in. Check-in records may retain the result, method, date and time, related meeting or house, and review status; they do not retain the device's exact latitude or longitude. A manual meeting check-in may also retain the meeting name, date, time, and description you submit so authorized staff can review that entry.
  • Residence and organization information. Organization and house details, addresses, descriptions, images, bed availability, staff roles and assignments, invitations, resident contact and housing records, move-in or admission information, status or phase, check-in history, bulletin content, rent settings, balances, ledgers, and organization listing information.
  • Transaction and subscription information. Purchase or payment amount, status, date, method category, account-connection status, transaction identifiers, rent and fee information, reports, and subscription entitlement information. Payment providers receive the financial details needed to complete a transaction; Reprieve does not store full card or bank-account numbers.
  • Technical and usage information. IP address, device and browser type, operating system, app version, requested pages, access time, device or app identifiers, security and integrity signals, crash diagnostics, and similar operational information. Release app builds may associate crash diagnostics with an account identifier to help diagnose and secure a reported failure.
  • Support and feedback information. Messages, attachments, survey responses, feature requests, and other information you provide when you contact us or ask for help.

Information Provided by Organizations and Other People

A recovery residence or its authorized staff may create a resident record, send an invitation, assign a house, record rent or payment activity, publish a bulletin, or otherwise provide information about a resident. Other users may send messages, participate in community discussions, or report content. Organizations and users are responsible for having the authority to provide that information and for keeping it accurate.

The Services may also display meeting, resource, news, public listing, and support information obtained from public sources or content providers. Visiting an outside website or service is governed by that operator's own privacy practices.

Private Recovery Data That Stays on Your Device

Your private diary, daily recovery check-ins and tracker history—including mood, cravings, physical steadiness, and connection—and sobriety start date are "Private Recovery Data." They are encrypted and stored only on your device. Reprieve does not receive, upload, sync, analyze, sell, disclose, or make this data available to Homebase, a recovery residence, service providers, advertisers, or other users. Private Recovery Data is used only on your device to show your own diary, trends, and sobriety progress.

If you separately choose to send a message, publish a post, or submit a meeting, curfew, or organization check-in, that separately submitted information follows the rules for that feature. Reprieve does not automatically copy Private Recovery Data into those features.

Private Recovery Data has no Reprieve cloud backup or recovery copy. Clearing app storage, deleting the app, removing the device security key, losing or replacing the device, or certain device failures may permanently erase it. Reprieve cannot restore Private Recovery Data that is removed from the device.

How We Use Information

The uses in this section apply only to information Reprieve receives. They do not apply to Private Recovery Data, which remains on your device and is not available to Reprieve for diagnostics, product improvement, advertising, legal requests, staff access, or provider processing.

We may use information we receive to:

  • create, authenticate, maintain, and secure accounts;
  • operate community, messaging, meeting, resource, housing, check-in, rent, payment, subscription, and support features;
  • reserve and confirm waitlist usernames and send requested communications;
  • show records to the correct resident, message participants, or authorized organization staff;
  • process transactions, reconcile ledgers, prevent duplicate or fraudulent activity, and resolve disputes;
  • apply Community Guidelines acknowledgments and block controls, investigate reports, enforce our Terms, and protect users and the Services;
  • diagnose failures, maintain reliability, and improve accessibility, performance, and features;
  • respond to support, privacy, legal, and security requests; and
  • comply with law and protect the rights, safety, and property of Reprieve, our users, organizations, and others.

Consumer Health and Recovery Information

Depending on applicable law, information about recovery status, sobriety, meeting participation, residence in a recovery setting, or support needs may be treated as consumer health data or other sensitive information. Reprieve may receive recovery-related information that you separately and intentionally submit through a connected feature, or that an organization provides with appropriate authority. That information is separate from Private Recovery Data.

Reprieve does not collect or receive the contents of your private diary, daily recovery check-ins or tracker history, or sobriety start date. Because Reprieve does not receive Private Recovery Data, Reprieve cannot use or disclose it to Homebase, a recovery residence, staff, message participants, operational providers, advertisers, other users, or third parties responding to requests directed to Reprieve.

Recovery-related information you intentionally submit through a connected feature is used and disclosed only as described for that feature and in this policy. We do not sell consumer health data, use it for cross-context behavioral advertising, or use it to infer an unrelated medical diagnosis. Reprieve does not automatically source connected features from Private Recovery Data.

How Information Is Disclosed

This section applies only to information Reprieve receives. It does not apply to Private Recovery Data, which is not transmitted to Reprieve and therefore is not available for Reprieve to disclose in the circumstances below.

We may disclose information we receive in the following circumstances:

  • At your direction. For example, when you publish a community post, accept a residence invitation, send a message, submit a check-in, or make a payment.
  • Within an authorized organization. Resident, housing, check-in, rent, and payment records may be available to authorized staff according to role and assigned-house scope.
  • With operational providers. We use providers for cloud infrastructure, data storage, authentication, communications, app distribution, payment processing, subscription administration, security, crash diagnostics, and support. They may process information only as needed to provide their service to us, subject to their applicable terms and our arrangements with them. Their records may be retained under their own schedules or where needed for security, reconciliation, disputes, or legal obligations.
  • For legal, safety, and security reasons. We may disclose information when we reasonably believe it is necessary to comply with law or valid legal process, investigate fraud or misuse, enforce our agreements, or protect rights, property, or safety.
  • In a business transaction. Information may be disclosed as part of a merger, financing, acquisition, reorganization, bankruptcy, or sale of assets, subject to applicable law and appropriate safeguards.
  • In aggregate or de-identified form. We may use or disclose information that cannot reasonably identify an individual for product improvement, reporting, research, or other lawful purposes.

Reprieve does not sell personal information and does not share personal information for cross-context behavioral advertising.

Community, Messages, and Organization Visibility

Community posts, messages, and organization records are separately submitted connected-feature records. They do not include Private Recovery Data, and the resident app does not automatically populate them from your diary, daily recovery check-ins, tracker history, or sobriety start date.

Forum posts and replies appear under the username you choose and may also display an optional profile image. Reprieve does not display your legal name or email on forum posts, but a username, image, or the content you share may identify you. Do not publish information you want to keep private.

When released, new community posts and replies require acknowledgment of the current Community Guidelines. New content also uses an opaque community-author identifier so the Android interface can hide new content from a member you have blocked. A block is stored privately for the person who set it and is not displayed to the blocked member. Content created before this control is introduced may require a separate approved migration before it can be hidden in the same way.

Community reports may retain the reason you provide, a limited content preview, and relevant reporter and reported-account snapshots so Reprieve can assess the report. Community spaces are not emergency services. We do not promise proactive screening, that blocking will prevent every harmful interaction, continuous monitoring, a particular moderation response, or removal of reported content.

Private-message content is available only to the participants included in the thread, subject to organization membership and house scope. Reprieve and its operational providers may access content when reasonably necessary to deliver the feature, investigate abuse or security issues, comply with law, or provide requested support.

When released, new private messages are rejected in both directions when either participant has blocked the other. This does not promise that a block erases, hides, or changes historical messages or content already created before the control applies.

When a resident accepts a Homebase invitation, authorized organization staff may access housing, check-in, rent, and related administrative records within their role and assigned-house scope. The organization may independently control records it created and may have its own legal retention, notice, and disclosure obligations.

Cookies, Logs, and Tracking Choices

The public website may use essential browser storage and ordinary server logs needed to deliver, secure, and troubleshoot the site. We do not use the website or apps to track your activity across unrelated services for targeted advertising. Browser, device, and application-marketplace controls may allow you to limit certain storage, permissions, or diagnostics, although some features may not work without required permissions.

Retention

Reprieve does not retain Private Recovery Data because Reprieve does not receive it. Private Recovery Data remains on the device until it is removed through app or device actions, and there is no Reprieve cloud copy to recover.

We retain other information for only as long as reasonably necessary for the purposes described in this policy, including while an account or organization is active and for periods needed to complete transactions, maintain business and accounting records, protect security, prevent fraud, resolve disputes, enforce agreements, and comply with law. Retention periods vary by the type of information and the context in which it was collected. We do not promise that session, audit, security, backup, or provider records will be deleted automatically on a particular date.

Organization-created housing, rent, ledger, and payment records may remain under the organization's control after a resident disconnects or deletes an account. De-identified information may be retained where it no longer reasonably identifies an individual. Backups and provider records may be deleted on a delayed schedule or retained where legally required.

When an authorized organization owner deletes a house, Reprieve removes the active house, current nonfinancial resident-management data, house-scoped check-ins, posts, private threads, invitations, and house access. Organization administrators and managers cannot initiate house deletion. Historical rent, payment, and reporting records may remain in the organization's financial reports. Limited financial reconciliation records may also be retained to process pending settlements, reversals, disputes, accounting, security, or legal obligations. Those records may include the resident and house names shown on the transaction, payment amounts, method and status, transaction identifiers, and relevant accounting dates, but they do not retain resident contact details, current profile or management notes, or an active resident-account link.

Account Deletion and Your Choices

The resident app provides an in-app account-deletion control that requires recent authentication. When completed, it deletes the resident account profile and authentication account, account-owned community posts and replies, private messages, submitted meeting and curfew check-ins, memberships, pending invitations, and local Private Recovery Data keys and data on that device. It retires the username and disconnects the Reprieve account from organization-controlled resident records rather than deleting records the organization independently maintains. Minimum financial, reconciliation, moderation, security, backup, or legally required records may remain where appropriate.

A Homebase owner cannot delete an account while it still owns an organization. The owner must first transfer ownership or use the separate organization-closure process, which is scheduled 30 days after the request and may be canceled before it takes effect. Some transaction, accounting, security, dispute, backup, and legally required records may remain after deletion or closure.

You may update available profile information in the Services, withdraw optional device permissions through device settings, unsubscribe from promotional email through the message, and contact us for deletion or privacy assistance. To start a resident account-deletion request outside the app, visit Account Deletionon our Support page.

Privacy Rights

Depending on where you live and subject to legal exceptions, you may have the right to request access to, correction of, deletion of, or a portable copy of personal information; confirm whether information is processed; withdraw consent; restrict or object to certain processing; appeal a denied request; or opt out of sale, targeted advertising, or certain profiling. We do not discriminate against users for exercising applicable privacy rights.

We may need to verify your identity and authority before completing a request. If information is controlled by a recovery residence or other organization, we may direct the request to that organization or assist it in responding. An authorized agent may submit a request where permitted by law, subject to verification.

Reprieve cannot provide or recover a copy of Private Recovery Data in response to a privacy or support request because Reprieve does not receive that data and no cloud copy exists.

Security and Incident Notice

We use administrative, technical, and organizational safeguards designed to protect information, including encrypted network connections, authenticated access, role- and house-based permissions, integrity checks, access controls, and provider security measures. No system can guarantee absolute security, and users are responsible for protecting their account credentials and devices.

Private Recovery Data is encrypted on the user's device and is not transmitted to Reprieve through designed app flows. These protections do not prevent someone who gains access to an unlocked or compromised device from attempting to access information on that device.

If a security incident affects information and notice is required, we will provide notice to affected people and regulators in accordance with applicable law.

Adults Only

The Services are intended for adults age 18 and older. We do not knowingly collect personal information from a child under 13 or knowingly permit a minor to create an account. If you believe a minor has provided personal information, contact us so we can review and take appropriate action.

Changes and Contact

We may update this policy as the Services or law changes. We will post the revised policy with a new effective date and provide additional notice when required.

For privacy questions, rights requests, deletion help, or support, contact[email protected].

Reprieve

Practical tools, trusted content, and a community that walks with you.

Explore

ReprieveHomebaseSupportTrust & data sourcesPathfinder List

Information

PrivacyTermsAccount deletionHomebase sign inContact us

© 2026 Reprieve. All rights reserved.

Reprieve is not emergency, medical, therapy, or crisis care.