Givenfold Privacy Policy
Givenfold is an iPhone app. It asks a few questions about what you care about, builds a charity portfolio for you, and sends you to Every.org to give. Givenfold is operated by Matthew Stephen Hammond. This page explains what we collect, why, and the choices you have.
What we collect
Account. You can use Givenfold as a guest, or sign in with an email and password, or with Sign in with Apple. For email accounts we receive your email address. For Sign in with Apple we receive the name and email Apple shares with us (this may be an Apple private relay address). Guests get an anonymous ID with no email or name. Sign-in is handled by Firebase Authentication.
Your survey answers. Your chosen causes, whether you prefer local, national or international charities, an optional ZIP code, how many charities you want, how you weigh efficiency, score and proximity, an optional monthly budget, and an optional free-text note about what you care about.
Your portfolio. The charities in your portfolio and how much of your budget goes to each.
Your giving ledger. A record of gifts you made through Givenfold and your recurring gifts: charity, amount, date, whether it repeats, and a charge ID from Every.org. We store this so the app can show your history and yearly totals.
Searches. When you search for charities, the words you type are sent to our server to find charities with a similar mission (see "OpenAI" below). We do not save these searches in your account. If a search finds no results, the search text (up to 100 characters) is included in an analytics event, described next.
Usage analytics. We use Google Analytics for Firebase to learn which parts of the app work and where people get stuck. We record events such as survey steps viewed, portfolio built, gift started or completed (with charity, amount and whether it repeats), notification permission choices, and screens viewed. We do not attach your account ID, name or email to these events. Firebase also collects standard technical data automatically, such as an app installation ID, device model, operating system and app version, language, and an approximate location derived from your IP address. Debug builds used by developers do not send analytics.
Crash reports. We use Firebase Crashlytics. If the app crashes, a report with technical details about the crash and your device is sent to us. We do not attach your account ID to it.
Device check. We use Firebase App Check (Apple App Attest) so our servers can tell a request comes from the real Givenfold app. It uses a device attestation and does not give us your identity.
On your device. Givenfold keeps some settings on your phone, such as notification choices and checkouts waiting for you to return from Every.org (kept up to 7 days). Reminders are local notifications scheduled on your phone. We do not collect a push notification token.
What we do not collect
- We do not use the advertising identifier and do not ask for tracking permission. We do not track you across other companies' apps or websites.
- We do not sell your data and do not show ads.
- We never see your card or bank details. Payment happens on Every.org's website.
- We do not collect your precise location.
Why we use it
We use your data to run the app: to sign you in, build and show your portfolio, record your giving, run search, and send the reminders you turn on. We use analytics and crash reports to fix problems and improve Givenfold.
Who else handles data
Google Firebase (Authentication, Firestore database, Cloud Functions, Analytics, Crashlytics, App Check) stores and processes the data above on our behalf. See Google's privacy policy.
OpenAI receives the text of the searches you type (up to 2,000 characters), so it can turn the text into numbers that match charity missions. Your account ID, email and other data are not sent with it. We do not save the search text on our servers.
Every.org processes your donation. When you tap Give, Givenfold opens an Every.org donate link in Safari. The link includes the charity, amount, whether it repeats, a donation ID, and an ID that ties the gift to your Givenfold account (your account ID and the charity ID). On Every.org's site you enter your own payment and contact details, and Every.org's privacy policy applies: every.org/privacy. Every.org tells our server about completed gifts. We keep only the charity, amount, date, whether it repeats, and the charge ID. We ignore other details in that message, such as donor name or email, and do not store them. Every.org issues receipts and handles refunds and recurring donations.
How long we keep data
We keep your account data, survey, portfolio and giving ledger until you delete them. Analytics and crash data are kept by Google for the periods set in our Firebase settings. Data you gave Every.org is kept by Every.org under its own policy.
Your choices
- Use as a guest. You can use Givenfold without an email or name.
- Export your data. In the app, go to Profile, then Export my data. You get a JSON file with your email, survey answers, portfolio and giving ledger.
- Delete your account and data. In the app, go to Profile, then Delete Account & Data. Guests see Delete Guest Data instead. This deletes your survey, portfolio, giving ledger and sign-in account. If you cannot use the app, email us at privacy@givenfold.com. Deleting your Givenfold account does not cancel a recurring donation. Cancel that with Every.org (see our support page). If Every.org reports a later charge for a deleted account, we do not store it. Analytics and crash data are not linked to your account, so we cannot look them up or delete them for you.
- Notifications. Reminders are off until you allow them. You can change this in the app or in iOS Settings.
Children
Givenfold is not directed at children under 13. We do not knowingly collect data from children under 13. If you think a child has given us data, email privacy@givenfold.com and we will delete it.
Security
Data is sent over encrypted connections, and the database is set up so each signed-in user can read and write only their own records. No system is perfectly secure, and we cannot promise absolute security.
This website
givenfold.com is served by Google Firebase Hosting, which processes your IP address and browser details to deliver the pages. The site sets no cookies and runs no analytics.
Changes to this policy
If we change this policy, we will post the new version here and update the effective date. If a change is significant, we will also tell you in the app.
Contact
Matthew Stephen Hammond
Email: privacy@givenfold.com