Privacy Policy

Overview

Purchase With Purpose collects and uses information needed to operate account onboarding, provider discovery, purchase reporting, business review, contribution status, beneficiary payout, tax, support, fraud, and compliance workflows.

Information users provide

Depending on role and workflow, users may provide account contact information, service addresses, purchase report details, invoice or reference numbers, business claim information, beneficiary profile information, payout setup information, tax setup information, support messages, and consent or terms records.

Provider directory and Google data

Purchase With Purpose may use Google Maps Platform to search for and display provider information. Google-sourced provider information can include place identifiers, business names, addresses, location, distance, categories, business status, ratings, review counts, and other place details returned by Google for the requested directory experience.

Google-sourced content is displayed with Google attribution. Purchase With Purpose does not use this integration to let businesses manage their Google Business Profile.

Payments, Stripe, and evidence

Stripe may be used for provider commission invoices, Stripe Connect evidence-only verification, payout or tax reporting workflows, and related operational evidence. Purchase With Purpose stores only the payment and account evidence needed for approved workflows and avoids storing raw card numbers or unnecessary processor payloads.

Role-based access

Account, report, provider, beneficiary, payment, payout, tax, and support information is limited by role and scope. A person with multiple roles may see different information in each role context.

Retention and support

Information may be retained for operational, financial, legal, security, fraud prevention, support, audit, and compliance purposes. Support and administrative actions should be recorded with history and resolution evidence.

Client/legal approval required

This page is a draft implementation surface. It should not be treated as final privacy language until reviewed and approved by the appropriate client, legal, privacy, and compliance owners.