Privacy Policy
Last updated November 16, 2026
501Go is trip-planning software for churches and mission-sending organizations, operated by 501Go, LLC (“501Go,” “we”). Churches trust us with information about the people they send, including passport details and information about minors. This policy explains what we collect, why, who can see it, and the choices you have.
The short version: each organization’s data is walled off from every other organization. Passport and emergency information is visible only to the trip leaders a church chooses. We don’t sell personal information, we don’t use it for advertising, and we don’t share it between churches.
1. Who is responsible for your information
Trip and traveler information. When a church or organization (a “Customer”) uses 501Go, the Customer decides what to record about its trips and travelers. For that information the Customer is the controller, and 501Go processes it on the Customer’s behalf and under its instructions, as set out in our Data Processing Agreement. If you’re a traveler, your church is your first point of contact for questions about your information; we’ll help them respond.
Account, billing and website information. For information about the people who sign up and manage an organization’s account, and for visitors to our website, 501Go is the controller.
2. Information we collect
Account information: your name, email address, and the organizations and trips you belong to.
Settings saved on your account: which one-time tips and tours you’ve seen (a short list of tip names) and how your Summary card is arranged. We use them only to show 501Go the way you left it. Only you can change them, and the demo never saves anything to an account. They’re kept until you delete them or your account is deleted.
Private sign-up links: if 501Go sends you a private sign-up link, we keep the email address it was made for, a short internal note from our staff, the link’s expiry and whether and when it was used.
Sign-in information: you sign in with your email and a password, or with Google or Apple. Your password is kept only as a one-way hash by our sign-in provider (Supabase); no one at 501Go can see it. To reset your password, or to create one, we email you a link. If you use Google or Apple, we receive your name, your email address (with Apple, possibly a private relay address that forwards to you) and an account identifier, and from Google a link to your Google profile picture, which our sign-in provider stores with your account and 501Go never uses or shows. Nothing else comes from that account. With Apple, we also keep a sign-in token from Apple, encrypted, only so we can ask Apple to remove 501Go’s access when you delete your account or remove Apple sign-in; it is deleted once Apple confirms. We also keep when and how you signed in, to keep your account safe. We never use phone numbers or text messages to sign you in.
Organization information: the organization’s name, logo, brand colors, home airport and billing contact, and, for donation receipts, its legal name and EIN.
Trip information that your team enters or imports: destinations and dates, the itinerary, flights and seat assignments, lodging, local contacts, a prep checklist, the budget, expenses (including receipt details) and funding records.
Traveler information: each traveler’s name, email address, gender, role on the trip, travel plans (for example, the airport they fly from) and which flights they’re on.
Sensitive traveler information, visible only to trip leaders: legal name, date of birth, phone number, home address, emergency contact, parent or guardian details for travelers under 18, medical and dietary needs, medicines (name, dose, the times to take them and whether a leader hands them out), passport number, expiry date and photo, visa records and photos, citizenship, place of birth, frequent-flyer and Known Traveler numbers, seat preference, T-shirt size, work, skills, languages, home church, past trips, scholarship answers, social media links (adults only) and the contact details of a reference they name. A traveler can also see and update their own. Customers decide whether to collect this.
Applications and waivers: when a church opens applications for a trip, anyone with the link can apply without an account; the answers (the same details as above, plus the church’s own questions) go only to that trip’s leaders. When someone signs a trip waiver, we keep the exact text signed, the typed signature, the signer’s email, the emergency contact they name, the time, their browser type and a one-way hash of their IP address (never the address itself), so the church has a reliable record, and we email the signer a copy as a PDF. A parent or guardian who co-signs for a minor from an emailed link is included. When a waiver is signed again because it changed, the earlier signature is kept as part of that record.
Fundraising pages and donations: a traveler’s page shows their name, story, goal and the amount raised to anyone with the link, and their photos only when allowed: an adult can turn them off, and for a traveler under 18 they show only after a parent or guardian says yes. When someone gives, we keep their name, email address, donation amount, optional note and whether to hide their name, and, for a cash or check donation a leader records, the donor’s postal address for the church’s receipt. The church’s trip leaders see all of it (to thank and receipt givers); the traveler sees names (except givers who chose to hide theirs), amounts and notes but not emails; the public page shows givers’ names (or “Anonymous” if they chose to hide it), amounts and notes. Card and bank details go directly to Stripe and never reach 501Go. When you give or pay online, you pay the organization (for example, the church), not 501Go. Stripe processes the payment on the organization’s own Stripe account under Stripe’s privacy policy. Payment links expire after 30 days. The church’s trip leaders can edit how a giver’s name shows on the public page and hide a giver’s message from it. Each change is logged with who made it. The giver’s receipt and the church’s records keep exactly what the giver entered.
Monthly donations: a giver can choose to give every month until a date before the trip. We keep the plan’s amount, schedule and end date, the exact authorization text the giver agreed to and when they agreed, and the brand and last four digits of the card. The card itself is saved on the organization’s own Stripe account, never with 501Go. The giver manages the plan in the donor portal: they can update the card, change the amount, skip a month or stop. If a charge is declined, it is tried again twice, 3 days apart, and then the giver is emailed.
In honor or in memory of: a giver can dedicate a donation to someone. The name they enter shows on the public fundraising page next to the donation, even when the giver chose to hide their own name. The giver can add a message of up to 300 characters, which the church’s trip leaders see and which goes in the card. The giver can also enter that person’s name and email address so the church can send them 1 card by email. The card never shows the amount. We delete the email address once the card is sent, or 3 to 14 days later if it never sends, and we never add it to any list. The name stays with the donation record. Enter details only for someone who would welcome the card.
Pledges: a giver can pledge an amount by a date. We keep their name, email address, the amount and the date, send 1 reminder email with a link to pay, and then delete the email address. The name and amount stay with the pledge record; if it’s unpaid 30 days after its date, the name is deleted. A trip leader can also record a pledge a person made to the church, with their email address if they gave it. We send that person 1 reminder and then delete the email address.
Donor question: a trip can ask givers 1 optional question. Only the church’s trip leaders see the answers, which stay with the donation record.
Encouragement emails: a traveler, and for a traveler under 18 a parent or guardian, gets an email when their fundraiser reaches 25%, 50% and 100% of its goal. After 14 days with no donations they get 1 email and an in-app card with a ready-made message to send, at most once every 14 days and never in the 7 days before the trip. They can turn these off in Settings, Your account, Preferences, or with the unsubscribe link.
Photos you add: passport and visa photos, photos of travel documents added to a trip requirement (such as a signed parental consent letter or a vaccine card), receipts, lost-luggage photos, photos of your own and the team’s bags, and a photo of a driver or greeter so the team knows who to look for. Each is seen only by the people the trip already allows to see that kind of information. Profile and fundraiser photos are stored privately and open through short-lived links; we remove location and camera details from them when they’re added.
Payment information: handled by our payment processor, Stripe. We receive a customer ID, plan and payment status, never your full card number.
Technical information: basic logs (IP address, browser type, pages requested, errors and timestamps) used to run, secure and fix the service. When something goes wrong, we also record a crash report: the error message, the page it happened on, the app version and the browser or phone type, tied to your account ID when you’re signed in or to a one-way hash of your IP address when you’re not, and kept for 30 days. The app doesn’t collect your location. It may ask your phone or browser, only on your device, whether you’re back in the United States, to decide when to upload receipts; that is never sent to us. A trip leader’s iPhone may also use its location, only on the phone and only while the app is in use, to remind them to tip a driver on arriving at the drop-off; that is never sent to us either. The website stores a sign-in session and a few preferences in your browser, all listed in our Cookie and Storage Policy. We use only essential cookies and storage: no advertising, analytics or cross-site tracking.
Testing versions of our website: when we test two versions of a page, your browser keeps which version you see (“psg-ab” in the Cookie and Storage Policy), and if you then sign up, that version is saved with your account. We count only daily totals per version (views, sign-ups and first payments) on our own servers, with no cookie or third party; the totals hold nothing that identifies you (a one-way hash of your IP address limits repeat counts and is deleted within a day). When your browser sends Global Privacy Control, you see our usual page and aren’t counted.
Planning guide requests: when you ask for a free planning guide on our website, we keep your email address, which guide you asked for and when, and, unless your browser sends a Global Privacy Control signal, how you found us (the page, the referring site and campaign tags). We email you the guide. If you confirm with the link in that email, we send a few planning emails over the next 30 days. Each has a one-click unsubscribe, and they stop when you unsubscribe or create a 501Go account. We keep the request for 24 months, or 30 days after you unsubscribe, unless you ask us to delete it sooner; a record that you unsubscribed stays so we never email you again.
Reports and requests: when you report content (“Report this”) or make a privacy request, we keep what you sent, your email if you give it, and a one-way hash of your IP address to stop abuse. Trip leaders see a report but not who sent it.
Support requests: when you ask us for help in 501Go, we keep your message and any screenshots you attach. Only 501Go staff open the screenshots, through links that work for 2 minutes.
Tester feedback: if we invite you to test 501Go, your personal link lets you send notes and screenshots without an account. We keep them with your name, email, device and app version, take location and camera details out of the screenshots, and only 501Go staff open them.
Your calendar link: if you add a trip to your own calendar, we make a personal calendar-feed link: a private web address that Google, Apple or Outlook calendars can read, with your flights and seats, the schedule you’re part of, the hotel stays and adult teammates’ birthdays during the trip. Anyone who has the link can read it, so keep it to yourself. It stops working 30 days after the trip ends, and making a new link stops the old one.
Affiliates: if you apply to our affiliate program, we keep your name, email address, how you plan to share your link, the date and version of the Affiliate Terms you agreed to, your mailing address for payouts, your sign-in, and which churches signed up through your link and whether they have paid. We keep these records for 7 years after your last payment, for accounting and tax. If you earn $600 or more in a year, we ask for a Form W-9. It holds your taxpayer number, which is stored privately, opened only by 501Go staff for tax reporting with every view recorded, kept for 4 years after the year of our last payment to you, and then deleted. We use it to file Form 1099 with the IRS. We share your details with the IRS for that. We never sell it or use it for advertising.
Churches that signed up through an affiliate: we record which affiliate a church came through. The affiliate sees only the first word of the church’s name and whether it has paid, never amounts, people or contacts.
3. Children and students
Churches, Christian schools and colleges use 501Go for trips that include minors, such as youth and student trips. 501Go is designed for adults to use; the church or school decides what information to add and is responsible for having a parent or guardian’s permission to add a minor’s details. For information about children and students, we commit to the following:
- No sign-in for children under 13. A traveler whose birth date shows they’re under 13 can’t sign in to 501Go. A parent or guardian signs forms and waivers for them, and we don’t knowingly collect personal information directly from a child under 13.
- The church or school stays in control. We use student and child information only to run that organization’s trips. The organization decides who can see it, and we don’t use it for any other purpose.
- No selling, advertising or profiling. We never sell student or child information, use it for advertising, or build profiles of students, and we don’t show ads in 501Go.
- Private details stay private. Passports, birth dates, health and allergy notes, medicines, insurance and emergency contacts are visible only to the trip’s leaders, the organization’s owner and the administrators the owner allows (and the traveler, when they’re old enough to sign in). A minor’s details go to that owner and those administrators, and to the trip’s leaders once they’ve cleared any background checks the organization requires for that trip, never to the organization’s other staff or to other travelers. Other travelers never see a minor’s email, gender or photo.
- Photos on fundraising pages. Photos of a traveler under 18 appear on a fundraising page only after a parent or guardian says yes, and they can withdraw it at any time.
- Deletion on request. A parent or guardian can ask the trip’s leaders, the organization, or us at info@501go.org to delete their child’s information. The trip’s leaders erase it in 501Go (passport, birth date, health details, medicines, contacts, photos, fundraising page and application answers), and the request is recorded and answered within 30 days. Records the organization must keep (payments and signed waivers) stay, without the child’s other details. Deleted information leaves our backups within 7 days.
- Schools with student-records obligations. Where a school is covered by FERPA or a state student-privacy law, we act as a service provider under the school’s direction and will sign a data privacy agreement on request.
4. How we use information
Health details (medical needs, allergies, medicines, insurance, physical ability, food needs and other requests, such as a CPAP) are collected only with a separate consent from the traveler, or a parent or guardian for a minor. Only the trip’s leaders see them (and the organization’s admins if its owner allows it). They are never sold or used for advertising, and the stored fields are never sent to AI (see OpenAI under Service providers). Taking consent back (in My profile or My consents, or by a parent or guardian through a privacy request) stops leaders from adding more health details. What was already saved stays until it is deleted: ask in My profile or through a privacy request, and we delete it within 30 days. For a traveler under 18, only the parent or guardian can take back a consent the parent or guardian gave. A trip leader can record a consent given on paper; the screen shows who recorded it and when.
Age. Only adults (18 or older) can set up an organization. People aged 13 to 17 may have an account only when a trip leader adds them, with a parent’s or guardian’s agreement. We do not allow accounts for children under 13; a parent, guardian or leader enters a child’s details.
- To provide 501Go: store and display your trips, keep your team in sync, send invitations and password emails, and show live flight status, weather and currency conversions.
- To send trip emails on the church’s behalf, from the trip leader’s address: application notices, task and waiver reminders, and signed waiver copies. For a traveler under 18, we copy the parent or guardian on pay links, autopay codes and reminders, and for a child under 13 we email only the parent or guardian.
- To provide optional AI features you choose to use, such as reading confirmations, receipts and passports, and drafting briefings, packing lists and trip reports (see section 7).
- To bill for subscriptions and prevent misuse of accounts.
- To keep the service secure, diagnose problems and improve it.
- To contact account administrators about the service, billing and important changes.
- To comply with the law.
We don’t sell personal information, share it for targeted advertising, or use traveler information for marketing.
Unsubscribing. Emails other than receipts, waivers and reminders about your own trip include a one-click unsubscribe and our postal address: 501Go, LLC, 5441 S Macadam Ave, Ste R, Portland, OR 97239. We honor unsubscribes immediately and keep a record so we don’t email you again. That includes the list of addresses that unsubscribed from the supporter emails 501Go used to send for travelers.
5. Who can see what
- Other organizations can’t see your data. Each organization’s information is isolated at the database level, not just hidden in the app.
- Within a trip, each traveler sees only their own account: their own details, fundraiser, flights and hotel, never other travelers or the team list. A parent also sees the children linked to them, and a bus captain the first names, last initials and allowed profile photos of the riders on their vehicle; a minor’s photo shows only with a parent’s or guardian’s photo release. Email addresses, phone numbers and other contact details are visible only to Trip Leaders and the person themselves. Only Trip Leaders (and the organization’s administrators) can see the budget. Passport, visa, medical, medicine and emergency contact information is visible to that trip’s Trip Leaders, the organization’s account owner and any administrators the owner allows. For travelers under 18, or whose birth date isn’t on file, the trip’s Trip Leaders see it once they’ve cleared any background checks the organization requires for that trip. Each traveler can also see their own. Only Trip Leaders can change the trip’s plan.
- Family tracking link. If a trip leader turns on the family tracking link, anyone with the link can see that trip’s name, destinations, flights and how many travelers are on each flight, never their names. It’s off by default, and leaders can turn it off or reset the link at any time.
- 501Go staff access customer data only when needed to provide support you request, keep the service secure, or comply with the law.
- Support visits: an organization’s owner can let 501Go staff view its account to help, in Settings, or by saying yes to our email asking for 1 visit. Staff can only view and change nothing, and never see passports, birth dates, health notes, emergency contacts, minors’ details, waivers, receipts, photos or donors’ details. We record each visit (who, when, why and how long), and the owner gets an email after every visit. Our support tools show the owner’s name, email and city from our main database when staff need them, and don’t keep a separate copy. Staff notes about an organization are deleted when the organization is deleted. A log of support actions is kept for 24 months, and the organization’s name and any email addresses in it are removed when the organization is deleted. Backups age out within 14 days. Records of fees we pay keep the amounts, dates and payment IDs, without church names, for at least 7 years for accounting and tax. Screenshots you send us are private and are opened by staff through links that work for 2 minutes.
- Unusual access is flagged. Every time someone other than the traveler views, prints or downloads travelers’ private details (passport, visa, health, medicine, emergency contact and application details, their photos, and signed waivers), we log who, when and what; repeat views by the same person within 10 minutes count once. The organization’s owners can see the log, each traveler sees who viewed theirs in Download my data, and repeated or unusual access is emailed to the owners and to us.
6. The iPhone app
The 501Go iPhone app shows the same trips, under the same rules, as the website. A few things work differently on the phone:
- Face ID, Touch ID or your passcode. The app asks you to unlock it each time it opens, so no one else can see passports, medical details or emergency contacts on a borrowed or lost phone. Your iPhone checks your face, fingerprint or passcode itself; 501Go never receives them, only whether the phone was unlocked. If a phone has none of these set up, you choose a 501Go PIN, which is kept only on that phone.
- Trips saved on the phone. So your trip works with no signal, the app keeps a copy of the 5 trips you opened most recently on the phone, including the private details you’re allowed to see, encrypted with a key held in the iPhone’s secure Keychain for that phone only. Changes you make with no signal wait on the phone until there’s a connection. On a phone with no passcode, the saved copy leaves out passports and medical details. Signing out, or deleting your account, erases the saved trips from the phone. The saved copy shows when it was saved. When the phone is online again, anything you are no longer allowed to see is removed from it.
- Reminders. Flight, schedule, ride, task, medicine and countdown reminders are set on the phone itself, so they arrive with no signal. Your reminder settings stay on the phone. Medicine reminders only remind you of what you or your leader entered; 501Go doesn’t give medical or dosing advice.
- Siri. You can ask Siri about your trip (where someone is staying, your next flight, today’s plan, who to call in an emergency). The app keeps a short, encrypted summary of those trip facts on the phone for this, and Siri answers from it on the phone itself, only while the iPhone is unlocked. It never includes passports, medical details or money. You can turn Siri off in the app’s Settings, which deletes the summary; signing out deletes it too.
- Flight on the lock screen. A few hours before your flight, the app can show a countdown on the lock screen and in the Dynamic Island (flight number, airports, departure time, gate and status). It’s made on the phone itself; nothing extra is sent to us or to Apple. You can turn it off in the iPhone’s Settings under 501Go > Live Activities.
- Camera and photos. The app uses the camera or your photo library only when you choose to take or pick a photo, and the iPhone asks your permission first. Only the photo you choose is uploaded.
- No location, tracking or ads. The app doesn’t collect your location (see Technical information in section 2), doesn’t track you across other apps or websites, and contains no advertising or analytics companies’ code.
- Crash reports from Apple. If you’ve agreed to share analytics with app developers in your iPhone’s settings, Apple may send us anonymous crash reports, under Apple’s privacy policy.
7. Service providers
We use a small number of providers to run 501Go. They may process personal information only to provide their service to us:
- Supabase: database, sign-in, file storage and server functions (hosted in the United States, in Virginia). It holds all account and trip information.
- Vercel: website hosting and delivery. It receives your IP address and request logs, and fetches past exchange rates for us from jsDelivr, so your browser doesn’t contact it.
- jsDelivr: serves an open archive of past exchange rates to Vercel. No personal information.
- Stripe: processes 501Go’s own subscription payments. Donations and trip payments are processed by Stripe on each organization’s own Stripe account, where Stripe acts for that organization. Card and bank details go directly from the payer’s browser to Stripe; 501Go never receives or stores full card or bank numbers. From Stripe, 501Go receives each payment’s status and amount, refund and dispute status, and the brand and last four digits of a card saved for automatic payments or monthly donations.
- Google (Workspace): 501Go’s own email, such as info@ and support@. When you write to us, or reply to an email from us, your message is kept in our Google mailbox.
- Resend: invitations, password emails, reminders, donation receipts, pledge reminders, in honor or in memory of cards and fundraising encouragement emails to travelers.
- Google and Apple: only if you choose to sign in with them. They confirm who you are and send us your name and email address, under their own privacy policies.
- Cloudflare, Inc. (Turnstile): checks that sign-in and public forms are used by people, not bots. It processes the visitor’s IP address and browser signals for that check only; 501Go stores no Turnstile data. Upload limits keep a one-way hash of the IP address for one day.
- OpenAI: used only by trip leaders. It reads flight, hotel and transport confirmations, receipts, adult travelers’ passport photos (only after a trip leader confirms each time) and roster spreadsheets, so they don’t have to be typed. It drafts briefings, prep lists and trip reports from the trip’s details (travelers’ names go with confirmations, to match seats, and with briefings), and checks current entry requirements for the trip’s countries with OpenAI’s web search. It turns a route a leader types into stops, and answers help questions typed into search when 501Go can’t answer them on the device. 501Go never sends the health details stored in a traveler’s record (medical needs, allergies, medicines, insurance, physical ability, food needs and other requests) to OpenAI, refuses insurance documents, and never sends a passport of anyone under 18. Health columns and passport numbers are removed from rosters, and emails and phone numbers from typed routes and questions, before they’re sent. What a leader types into an AI box, a route or a question goes to OpenAI as written, and so do event titles and open checklist items in a daily briefing. We try to remove sentences that pair a team member’s name with a health word, but we can’t catch everything. Files and text go to OpenAI, our AI provider, only so it can read them; 501Go doesn’t keep the copy it sends (a receipt photo you attach to an expense is saved with that expense). OpenAI doesn’t use data sent through its API to train its models. Every request asks OpenAI not to store the response (“store: false”). OpenAI keeps what it receives for up to 30 days, only for abuse checks, unless the law requires longer; 501Go has no zero-data-retention agreement with OpenAI. Please don’t upload medical records or insurance documents, and don’t type anyone’s health details into an AI box: the stored health fields stay out of AI requests, but text that is typed or inside an uploaded file can’t be fully filtered out.
- AeroDataBox, through RapidAPI: flight numbers and dates, to look up live flight status. Our server sends them to AeroDataBox through RapidAPI’s marketplace.
- Google (Routes API): the map coordinates of two stops on a trip (a town or an airport, never a street address or a person), to look up the road distance and drive time between them. Our server sends only the coordinates; Google does not receive names or any traveler’s details.
- Open-Meteo: weather, time zones and place lookup. Your browser, or our server when it builds a calendar link, sends the trip’s city or coordinates (not your own location); your browser’s requests include your IP address.
- ExchangeRate-API: today’s exchange rates. Our server fetches them; no personal information.
- Dropbox: only if your organization connects its own Dropbox, receipt photos are uploaded directly to your Dropbox account, under Dropbox’s terms.
- Planning Center: only if your organization connects its own Planning Center account. 501Go reads the people on the list you pick, or the names you search for (names, emails, phone numbers, addresses, birthdays, a minor’s parents in their household, and the custom fields whose names match 501Go’s, such as allergies or emergency contacts), over Planning Center’s API, under your organization’s agreement with Planning Center, and keeps the connection key, encrypted, until you disconnect. Nothing is written back.
- Google, Apple and Outlook calendars: only if you add your calendar link to one of them. That calendar’s servers read the link (see Your calendar link in section 2), under its own privacy policy.
We may also disclose information if required by law, to protect someone’s safety, or as part of a merger or sale of 501Go, in which case this policy continues to apply.
8. Security
Data is encrypted in transit (TLS) and at rest (AES-256) by our database host. On top of that, passport numbers, health insurance details, medical and physical-ability notes and medicines are encrypted field by field inside the database, with a key kept in a separate key vault, so a copy of the database or a backup on its own doesn’t reveal them. Access rules are enforced in the database itself, and we regularly test that one organization can’t reach another’s data and that travelers can’t use leader-only actions. Two-step sign-in uses a 6‑digit code from an authenticator app, never a text message. The code at sign-in is off by default; an organization’s owner can turn it on for everyone in that organization, and every change is logged. Online, opening private traveler details needs the code, unless the person has confirmed in 501Go that their organization allows opening them on their devices without one. We record that confirmation with the date and the wording shown, and the person can withdraw it in Settings. For a trip saved on the iPhone, the offline copy opens with Face ID, Touch ID or the passcode, without the code, only while there is no signal, and shows when it was saved. Once signed in, the people running a trip open its private details without another code, and each time private details are opened is logged. Passport and visa photos are stored privately and shown to trip leaders through links that work for 2 minutes. Signing out removes the person’s data from that browser or phone. No system is perfectly secure; if we learn of a breach affecting your information, we’ll notify the affected Customers (their owners, admins and the security contact they set) without undue delay and, where required, individuals and authorities.
9. How long we keep information
- Trip and traveler information stays for as long as the Customer keeps it in 501Go. Deleting a trip removes it immediately. Our database host keeps daily backups for 7 days, so deleted information leaves the backups within 7 days.
- Applications a trip declines or that are withdrawn stay with that trip and are deleted with it. A leader can delete an application that is spam, a test or a duplicate.
- When a person deletes their account, or a trip’s leaders erase a traveler’s information at their (or their parent’s or guardian’s) request, we delete their private details, medicines, photos, fundraising page and application answers at once. They come off trips that haven’t started; on past trips they’re listed only as “Former traveler”. We keep, without their other details: payment and donation records for 7 years (accounting and tax), signed waivers (for the period below), and records of consents.
- If an organization’s plan lapses or its account closes, it keeps full access for 7 days, then it is locked until it renews, except for view-only access while one of its trips is under way; from the locked screen its administrators can ask for an emailed copy of its data. A locked organization’s public fundraiser pages, payment links and family tracker stay open, so givers and families aren’t cut off. After 90 days, we email its admins a copy, send its owner a private link to download every trip’s signed waivers (it needs the owner’s sign-in and works for 7 days), and permanently delete its data, signed waivers included (and from backups within a further 7 days). Nothing is deleted while one of its trips is in progress. The lock and deletion start only once 501Go turns on billing enforcement. After the 7 days, a lapsed account’s email to its travelers and families, flight lookups, uploads, AI, road distances and public forms (trip applications included) are off until it renews, whether or not enforcement is on; it can still see and change everything else. Billing, security and account notices still reach its admins. An organization that signs up but never pays is treated the same way: the same 7 days of access, then, once billing enforcement is on, locked for 90 days, counted from the day it signed up, and then it is deleted. If an organization’s owner asks us to delete it, we do so 7 days later, after emailing its administrators a copy; the owner chooses then whether to get the signed waivers link too, and any of its administrators can cancel before then.
- Billing records are kept as long as tax and accounting law requires. After an organization is deleted, we keep a record of each card or bank payment (amount, fees, date and payment ID, with no names, emails or messages) for 7 years for accounting.
- Monthly donation plans and their authorization record are kept with the donation records for 7 years. A plan’s saved card is removed from the organization’s Stripe account within 2 days after the plan stops.
- The email address of a person receiving an in honor or in memory of card is deleted once the card is sent, or 3 to 14 days later if it never sends. The honoree’s name and the optional message stay with the donation record.
- The email address on a pledge is deleted after the reminder is sent.
- If you used a private sign-up link, we keep the email address it was for, the church, the dates and the terms you agreed to, for as long as needed to enforce 1 link per email and per church and to keep a record of your agreement (at most 7 years).
- Technical logs are kept for up to 90 days, and crash reports for 30 days. The log of who viewed travelers’ private details, and of changes to a traveler’s email address, is kept for 2 years.
- Signed waivers, including earlier signatures, are kept for 7 years after the trip ends, or until the youngest traveler they cover turns 21, whichever is later, and then deleted. The organization keeps its own copies: its trip leaders and administrators are reminded to download them after the trip, and again 30 days before we delete ours. When the organization’s account closes, we delete ours with it (above).
- Privacy requests are kept for 24 months after they’re closed, as a record that we answered them.
- Affiliate business records (an affiliate’s details, the churches that signed up through their link, payments, earnings and payouts) are kept for 7 years after our last payment to the affiliate, for accounting and tax.
- An affiliate’s Form W-9 is kept for 4 years after the end of the year of our last payment to them, and then deleted.
10. Your choices and rights
We keep a record each time you agree to our Terms or Privacy Policy, give or take back consent for health details or photos, or confirm your age: what you agreed to, which version, when, and a one-way hash of your IP address (never the address itself). These records are kept as proof of consent; if you delete your account, they stay without your name or email. If a sign-up is never finished, so no account is made, its consent records are deleted after 30 days. You can see yours in Settings > Account > My consents.
You can view and update your name and travel details in the app. Download my data (Settings, Account) gives you a file of the personal information we keep about you: your account, your organizations and trips with your private details, medicines, requirements, applications and signed waivers, your payments, donations and fundraiser, your consents, reminders, email preferences, your account settings, invitations, support, privacy and feature requests, crash reports and AI tool use, and who viewed your private details. Photos you added for a trip requirement come with it in a ZIP. Other people’s details and private links are left out. Delete my account (Settings, Account, on the website and in the iPhone app) deletes your sign-in and, on every trip, your private details, medicines, photos, fundraising page and application answers, straight away. You come off trips that haven’t started; on past trips you stay only as “Former traveler”. Payment and donation records and signed waivers stay with the organization as its records (see How long we keep information). While you’re on a trip that’s under way, deletion waits until it ends, in case your leaders need your details in an emergency. Travelers should contact their church to access, correct or delete trip information, and we’ll support the church in doing so. Depending on where you live (for example California or the European Economic Area and UK), you may have rights to access, correct, delete or receive a copy of your information, and to object to or restrict some processing. We won’t discriminate against you for exercising your rights.
Privacy requests. You can ask us to see, correct, delete or give you a portable copy of your personal information, or to opt out of its sale or sharing. Signed in, use Settings > Account > Privacy requests (you can also download your data there at any time). Or write to privacy@501go.org.
We answer within 30 days of receiving your request. If we need more time, we tell you why before then and may extend once, to 45 days from receipt, or, where the law allows, to at most 90 days. We confirm your identity before acting: a request made while signed in is already confirmed; for one sent by email or from our website we ask you to reply from the same address. An authorized agent or a parent or guardian may make a request for you.
For trip records kept by your church, school or group, that organization decides on your request; we pass it on, help it respond, and tell you the outcome. If we deny a request, we tell you why, and you can ask us to reconsider by replying, or contact your state attorney general or data-protection authority.
Do Not Sell or Share My Personal Information. 501Go does not sell or share personal information (as defined under California law), and we honor Global Privacy Control signals. When your browser sends one, we treat it as an opt-out of sale and sharing for that browser; because we do neither, nothing changes for you.
To report a photo or page, or an intimate image shared without consent, see our Copyright and Content Policy (copyright@501go.org).
11. International use
501Go is operated from the United States, and information is stored there. Trips go all over the world; when your team uses 501Go abroad, information travels to our US servers. Where the law requires, we use appropriate safeguards for these transfers.
12. Changes to this policy
We’ll post any changes here and update the date above. If a change is significant, we’ll let account administrators know by email before it takes effect.
13. Contact us
501Go, LLC, an Oregon limited liability company, 5441 S Macadam Ave, Ste R, Portland, OR 97239. Email: info@501go.org; privacy requests: privacy@501go.org.
