Information we handle
We store account details, your selected nonprofit, conversations, usage counts, subscription status, donation records, referral attribution, and impact cards you choose to publish. Clerk handles sign-in. Stripe handles payment details, so GiveGPT does not store full card numbers.
Public impact pages
Impact cards, cause-team totals, and completed donation receipts are public by design. They show the selected nonprofit and verified aggregate or settlement information, but not your name, email address, chat content, or payment details. You can delete an impact card link from your dashboard. Financial records may remain public in de-identified form when needed to preserve settlement verification.
How information moves
Chat prompts and recent conversation context are sent to Groq to generate responses. Nonprofit searches use Every.org data. Application data is stored in our PostgreSQL database hosted through Supabase. If you allow analytics, PostHog receives product usage events but not chat content.
Why we use it
- Provide chat, history, billing, charity selection, and impact records.
- Protect the service, troubleshoot failures, and understand product performance.
- Meet legal, accounting, fraud prevention, and donation-record obligations.
Your controls
Settings lets you download a copy of your GiveGPT data or request account deletion. Paid plans must be canceled first so an open allocation is not lost. Some transaction records may be retained when required for financial or legal obligations.
Contact
Questions and privacy requests can be sent to hello@givegpt.ai.