Data Processing Agreement
Last updated November 16, 2026
This Data Processing Agreement (“DPA”) is part of the Terms of Service between 501Go, LLC (“501Go”) and the church, school or organization that uses 501Go (the “Customer”). The Customer accepts it when it signs up.
1. Roles
For personal information about the Customer’s trips, travelers, applicants, families, references and givers (“Customer Personal Data”), the Customer is the controller (or “business”) and 501Go is its processor (or “service provider”). For account, billing and website information about the people who manage the Customer’s account, 501Go is a controller, as the Privacy Policy explains.
Schools and FERPA. FERPA applies only to schools that receive U.S. Department of Education funds. Such a school may disclose education records to 501Go as a “school official” only if the conditions in 34 CFR 99.31(a)(1)(i)(B) are met: 501Go performs a service the school would otherwise use its own employees for, is under the school’s direct control for the use and maintenance of those records, and uses and re-discloses them only as 34 CFR 99.33(a) allows. The school decides, in its annual notice to families, what counts as a legitimate educational interest. This DPA supports those conditions (the school directs the processing, 501Go uses student information only to provide the service, never re-discloses it except to subprocessors that provide the service, and gives the school access, correction, deletion and export), but it doesn’t by itself make 501Go a school official. 501Go never uses student information for advertising or to build profiles of students.
2. What is processed, and why
- Purpose: only to provide, secure and support 501Go for the Customer, as the Terms describe and as the Customer instructs through its use of the service.
- People: travelers (including minors), their parents or guardians and emergency contacts, applicants and references, trip leaders and staff, givers, and local contacts.
- Information: names, contact details (including home addresses), trip and travel details, roles, payments and donation records, signed waivers, and the other traveler details the Privacy Policy lists, and, when the Customer collects them, passports and visas, dates of birth, and health details (medical needs, allergies, medicines, insurance, food needs and other requests), which are collected only with a separate consent, given in 501Go or on paper and recorded by a trip leader.
- Duration: for as long as the Customer uses 501Go, then until deletion as set out in section 8.
3. 501Go's commitments
- Process Customer Personal Data only on the Customer’s documented instructions (these terms and its use of the service), and tell the Customer if we believe an instruction breaks the law.
- Not sell or share it (as California law defines those words), not use it for advertising or profiling, not use it for any purpose outside providing the service, and not combine it with information from other sources except as the service needs.
- Never send the health details stored in a traveler’s record (medical needs, allergies, medicines, insurance, physical ability, food needs and other requests), insurance documents or a minor’s passport to AI providers, and send other information to them only as the Privacy Policy describes.
- Make sure everyone who can access it is bound to confidentiality, and give access only to those who need it.
- Comply with the laws that apply to us as a processor, and tell the Customer if we can no longer meet them.
4. Security
501Go keeps technical and organizational measures appropriate to the risk, including:
- encryption in transit (TLS) and at rest (AES-256) by our database host;
- passport numbers, health insurance details, medical and physical-ability notes and medicines 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;
- each organization’s data walled off by access rules enforced in the database, tested automatically;
- two-step sign-in (a 6‑digit code from an authenticator app, never a text message): signing in is protected by two-step verification where the Customer’s owner turns it on (every change is logged, and the database enforces it). Once signed in, the Customer’s owners, admins and trip leaders open private details without another code, and the code is asked again before major account changes. The Customer decides who holds these roles, removes people who leave and is responsible for the devices its people use. The iPhone’s encrypted offline copy opens with the phone’s own lock and shows when it was saved;
- passport and visa photos and people photos in private storage, opened through short-lived links;
- a log of every view, print and download of travelers’ sensitive details and signed waivers by anyone other than the traveler (repeat views within 10 minutes count once), which the Customer’s owners can see, kept for 2 years, with alerts for unusual repeated access;
- 501Go staff can view the Customer’s account only when the Customer’s owner allows it, view-only, never including passports, birth dates, health details, emergency contacts, minors’ details, waivers, receipts, photos or donors’ details, with every visit recorded and emailed to the owner;
- a written security program and incident-response plan, reviewed at least yearly.
5. Subprocessors
The Customer authorizes the providers listed in section 7 of the Privacy Policy. Each is bound by written terms that protect the data at least as well as this DPA. We’ll give at least 30 days’ notice (by email to the Customer’s owners and on that page) before adding or replacing one. If the Customer objects on reasonable data protection grounds and we can’t address the objection, it may cancel and we’ll refund any prepaid, unused time. We remain responsible for our subprocessors. Services the Customer connects to its own account (such as Planning Center or Dropbox) and the calendar apps a person adds a calendar link to work under the Customer’s or that person’s own agreement with them; the Privacy Policy lists them so it’s clear what they receive.
6. Helping with requests from people
When a person asks to see, correct, delete or receive a copy of their information, the Customer decides. 501Go gives the Customer the tools to do it in the app (editing and deleting travelers and trips, data downloads), passes on any request we receive about the Customer’s data within 5 business days, and helps with anything the tools don’t cover. We also help with data protection impact assessments and regulator questions, as far as they concern our service.
7. Security incidents
If 501Go reasonably believes that a breach of security has led to unauthorized access to, or loss of, Customer Personal Data, we’ll notify the Customer without undue delay, and within 72 hours of 501Go’s reasonable belief that a qualifying incident occurred, by email to its owners, admins and security-notice contact (set in Settings). The notice itself contains no travelers’ sensitive details. The notice says what happened, what information and people are affected, what we’ve done and what the Customer should do, and we’ll keep the Customer updated. We’ll help the Customer meet its own duties to notify people and authorities. Telling the Customer isn’t an admission of fault.
8. Deletion at the end
When the Customer deletes a trip, a traveler or its account, we delete Customer Personal Data, and it leaves our backups within 7 days (our database host keeps daily backups for 7 days). When the Customer’s plan ends or lapses, and billing enforcement is on, we lock the account and, at any time before deletion, send the Customer’s administrators a copy of its data on request. We delete the data 90 days after the 7-day grace period, or after a trip under way or an active pass ends, whichever is later, and from backups within a further 7 days. We keep only what the law requires (for example, anonymized payment records for 7 years) and protect it under this DPA while we do.
9. Audits
On request, once a year (or after a security incident), we’ll answer a reasonable written security questionnaire and give the Customer the information it needs to show it is meeting its own duties. Where the law requires an on-site audit, it’s arranged with 30 days’ notice, during business hours and under confidentiality, at the Customer’s cost.
10. Where data is kept
Customer Personal Data is stored in the United States. 501Go hasn’t signed the EU or UK Standard Contractual Clauses or any other transfer safeguard with any customer. A Customer whose law requires safeguards for transfers to the United States must tell us before putting that personal data into 501Go, so we can agree in writing on the safeguards first.
11. The Customer's commitments
The Customer is responsible for having a lawful basis, notices and consents for the information it puts into 501Go (including a parent’s or guardian’s permission for a minor’s information), for its instructions being lawful, and for deciding who in its organization may see what.
12. General
Liability under this DPA is subject to the limits in the Terms, except where the law doesn’t allow them. If this DPA and the Terms conflict about personal data, this DPA wins. We may update this DPA as the Terms describe; changes that reduce the Customer’s protection don’t apply without its agreement. Questions: privacy@501go.org or info@501go.org. 501Go, LLC, an Oregon limited liability company, 5441 S Macadam Ave, Ste R, Portland, OR 97239.
