Information we collect
Account and sign-in: email address, password or federated authentication (for example Sign in with Apple or Google where offered), OAuth tokens where applicable, and session data handled by our backend and authentication provider.
Profile: name, phone number, date of birth (if you choose to provide it), biography, a general location label, profile photo, and similar fields shown in the app. Images are stored in our file storage and may be visible to other users as the interface indicates.
Listings: descriptions, photos, category and condition, pricing where applicable, and pickup or map-related location details you add so others can coordinate collection. Visibility of precise versus approximate location follows in-app disclosures and technical controls.
Messaging: messages and related metadata in conversation threads tied to listings and handoffs, stored so participants can communicate.
Activity and reputation: information such as completed handoffs, ratings, points, referrals, or program participation when those features are enabled in the product.
Referrals and invitations: referral codes you create or redeem, attribution tied to invite links or deep links, and records needed to run referral or growth programs securely (for example preventing abuse or duplicate redemption).
Safety and moderation: if you submit a content or conduct report, or use blocking features, we process account identifiers, descriptions, and context needed to review reports, moderate, and honor blocks.
Location: if you grant permission, we may read device location while you use the app to suggest an area, show approximate distances, and render map previews. You can also save a preferred region manually; see “Local storage on your device.”
Notifications: if you allow notifications, your platform (Apple or Google), our push intermediary (such as Expo push services where used), and our delivery stack may process device tokens or similar signals needed to send alerts.
Product analytics (mobile app): when analytics is enabled in the build configuration, native apps may send usage and diagnostics to Firebase / Google Analytics (GA4-compatible), including aggregated or pseudonymous identifiers, screen or route signals without passing sensitive query-parameter values where we configure it that way, and product events (for example creating a listing or opening a conversation). Analytics is gated by configuration and helps us measure reliability and product usage; see Google’s disclosures for categories their SDKs may derive.
First-party product analytics in our database: when analytics is enabled in the build configuration and you are signed in, we may also record discrete in-app events in our Supabase-backed database (for example creating a listing, submitting a request, opening a chat, or engaging optional affiliate discovery links), linked to your account id. We store a short event name, coarse metadata such as platform and app version, and a small JSON object of non-sensitive parameters (values are size-limited and truncated). We use these logs to understand how features are used and to improve the product; they are not shown to other users.
Affiliate commerce (optional): if you choose product discovery links (for example “search on a retailer”), your search query may be sent to that retailer or affiliate redirect so you can browse off-platform offers; those third parties operate under their own terms and notices.
Website and landing pages (givehood.com): pages such as invite links, marketing, support, early-access signup, or account-related flows may collect what you submit on each form—for example email, optional city or age-band selections, locale or browser language—and standard technical data (for example IP address and user agent) that web servers and our providers process automatically.
Technical data: app or web client version, diagnostics our infrastructure emits for reliability and security, and identifiers our providers use to operate authentication and APIs.