Electronic Policy Acceptance & Recordkeeping Procedure
Effective policy version: 2026-09-10.1
This procedure establishes PullUp Rideshare’s standard for presenting, accepting, recording, retaining, and re-presenting legal terms and policy acknowledgements. It is intended to create a consistent electronic record showing that a user was presented with the applicable PullUp policy set and affirmatively accepted it.
1. Covered Participants
This procedure applies to riders, drivers, delivery partners, enterprise or organization representatives, fleet administrators, parents or legal guardians, community or program partners, and other participants when acceptance of PullUp terms is required.
2. Required Acceptance Record
For each completed acceptance, PullUp should retain, to the extent available and lawful, the participant’s name, account or contact identifier, role, policy version, date and time of acceptance, acceptance method, applicable policy set, and the electronic signature or affirmative consent record. Technical audit information such as submission ID, browser or device details, and IP-derived security metadata may also be retained when collected by the form or platform in accordance with the Privacy Policy and applicable law.
3. Affirmative Consent Standard
Acceptance should require an affirmative action, such as selecting required acknowledgement checkboxes and submitting an electronic signature or equivalent confirmation. Pre-checked boxes or passive continued browsing should not be treated as the preferred method for material legal consent where stronger clickwrap acceptance is reasonably available.
4. Policy Presentation
Before acceptance, the participant should be given a reasonable opportunity to review the Terms of Service and the policies applicable to that participant’s role and service. The acceptance interface should identify the policy version and provide working links to the governing policies.
5. Role-Based Terms
In addition to the general Terms of Service, the acceptance process should present or identify role-specific policies when applicable, including Rider Terms, Driver Terms, Delivery Terms, Enterprise Terms, Minor & Guardian Transportation Policy, Community Guidelines, Safety Policy, Non-Discrimination Policy, Accessibility & Service Animal Policy, Cancellation & Refund Policy, Rewards & Offers Policy, and the Privacy Policy.
6. Electronic Signature and Records Consent
The participant should consent to electronic records, electronic notices, and an electronic signature for the acceptance transaction. The acceptance process should make clear that the participant may retain or print copies of the policies and confirmation record.
7. Re-Acceptance After Material Changes
When PullUp makes a material change to governing terms, creates a materially different service category, or determines that renewed consent is appropriate, the affected participant should be presented with the revised policy version and required to affirmatively accept the new version before continuing the affected service when legally and operationally appropriate.
8. Organizational and Guardian Authority
Enterprise representatives, fleet administrators, partners, parents, and legal guardians must certify that they possess the authority they claim. Acceptance by one representative does not bind another person or organization beyond the authority legally held by that representative.
9. No Personal Guarantee
The acceptance record should identify PullUp Rideshare as operated by Onyx Repository Foundation and should not be interpreted as creating a personal guarantee by Rodney Addison, Amanda Dixon, or another director, officer, founder, employee, volunteer, contractor, agent, or representative merely because that person develops, communicates, administers, oversees, or enforces PullUp policies. This does not limit liability that applicable law does not permit to be limited.
10. Record Retention and Access
Acceptance records should be maintained in a secure administrative system with access limited to personnel with a legitimate operational, compliance, legal, safety, audit, or support need. Records should not be altered to change the substance of what the participant accepted. Corrections or annotations should preserve the original record where practicable.
11. Disputes and Audit Trail
If acceptance is disputed, PullUp should preserve the relevant policy version, acceptance record, timestamps, submission identifiers, notices, and other available evidence sufficient to reconstruct what was presented and accepted. No employee or representative should manually fabricate or backdate a consent record.
12. Privacy and Data Minimization
The acceptance process should collect only information reasonably necessary to identify the participant, establish authority, document acceptance, and maintain the audit trail. It should not request Social Security numbers, payment card numbers, full driver license numbers, unnecessary medical information, or other sensitive information solely for policy acceptance.
13. Current Acceptance Method
PullUp’s current supplemental electronic acceptance form is the PullUp Electronic Policy Acceptance & Consent Record. Until equivalent acceptance is fully integrated into the PullUp application and account workflows, this form may be used to document affirmative acceptance for onboarding, enterprise participation, guardian authorization, driver compliance, or policy re-acceptance.
Open PullUp Electronic Policy Acceptance & Consent Record
Administrative note: This procedure supports evidence of consent and consistent operations. It does not replace jurisdiction-specific legal review or any consent method that applicable law specifically requires.