Understand what donor data Give Lively captures and where

What Give Lively donation forms and event pages capture

• Donor’s first and last name
• Donor’s email address
• Card details such as brand (Visa/Mastercard etc.)
• Last four digits of credit card number (the rest of the number is hidden)
• Zip code
• Country
• Donation amount and frequency (one-time or monthly)
• Donation date
• Dedicatee's name (only if dedication was made, not available on Event Ticketing pages)
• Type of dedication (only if selected, not available on Event Ticketing pages)
• Phone number (only if donor arrives through Text-to-Donate)
• Text-to-Donate text code (only if donor arrives through Text-to-Donate)
• Campaign or event name, pulled from the page to which the donation was made

What Give Lively event pages also collect

Event Ticketing pages also collect the answers to any additional questions enabled by the nonprofit through the event dashboard, such as:

• Donor company name
• Phone number
• Mailing address
• One custom question

What metadata Give Lively captures and shares with Stripe

When a donation is made via Stripe, Give Lively sets metadata values for corresponding data (e.g. campaign data only gets created for campaign charges; event data only for events). The following metadata is shared by Give Lively with Stripe:

Charge data

• anonymous_to_the_public 
• page_type (type of fundraising page)
• transaction_fee_covered_by_donor
• cart_id
• gl_charge_id (the ID of a one-time charge in the Give Lively database; not relevant for subscriptions/recurring donations)
• client_application_name

Subscription data 

• gl_subscription_id (only for Stripe subscriptions/recurring donations)

Donor data

• user_first_name
• user_last_name
• user_id
• user_email 
• phone_number
• company/organization_name (donor’s company name)
• mailing_address
• postal_code
• zip_code
• country

Tracking data

• referrer_url (only when donors have tracking enabled on their device or browser)
• utm_source
• widget_url
• phone_ref (the ID associated with a user’s phone)
• ref (the ID for the click from a text code that leads to a donation page)
• text_campaign_code

Nonprofit data

• nonprofit_id
• npo_guidestar_id
• payment_platform_account_uuid

Campaign data (also included for peer-to-peer fundraisers)

• campaign_id
• campaign_slug
• campaign_internal_name

Peer-to-peer fundraiser data

• beneficiary_type (the type of page of the beneficiary organization)
• beneficiary_internal_name (the name on the page of the beneficiary organization)
• fundraiser_by_name (full name of peer-to-peer fundraiser)
• fundraiser_by_email (email of peer-to-peer fundraiser)
• fundraiser_slug (slug of peer-to-peer fundraiser page)
• fundraiser_page_url
• team_id
• team_name
• team_slug

Event data

• event_additional_donation (donation beyond ticket purchases)
• event_name
• event_slug
• For each ticket tier connected with the charge, Give Lively associates a version of the tier name with information about the number and price of the tickets, e.g. “early_bird_tickets" with the value "3 X $250.00 = $750.00". 

Answer data

• For each answer associated with the charge, Give Lively associates a version of the question with the answer, e.g. “what_is_your_favorite_color?" with the value “aquamarine”.

Some metadata and general payment information is stored only in (and encrypted by) Stripe

• Card number and verification code
• Card funding type (credit or debit)
• Card expiration date
• Bank account number
• Bank routing number
• Bank account type
• Bank account nickname

Read more on Stripe about what data Stripe accesses.

What data Give Lively shares with Double the Donation

• Donor's first and last name
• Donor's email address
• Donation amount
• Donation date
• Fundraising page name (nonprofit, campaign, peer-to-peer or event)
• Donor company name

What data Give Lively shares with PayPal

• Donor's first and last name
• Donor's email address
• Donation amount
• Donation date
• Fundraising page name (nonprofit, campaign, peer-to-peer or event)

What Give Lively does NOT collect or access

• Nonprofit’s bank account information
• Personal information about any Stripe users (birth dates, social security numbers etc.)
• Donor credit card number and verification code, which is securely encrypted by Stripe
• Donor bank account number, which is securely encrypted by Stripe