Effective September 1, 2026 · Version 2.1

Privacy Notice

This notice explains how AccessRide handles personal information through its public website, Central Texas pilot, provider and healthcare-partner workflows, mobility-request review, AccessRide Academy, community research, protected workspaces, and launch analytics.

Our current operating boundary

AccessRide is in a pilot and network-building stage. A mobility request is reviewed for possible availability; it is not a confirmed booking. Do not use AccessRide for an emergency. Call 911. Until AccessRide activates an approved secure healthcare workflow, do not send diagnoses, medical records, insurance identification numbers, Social Security numbers, payment-card information, or other detailed medical information through a public form or ordinary email.

Information we process

Depending on how you use AccessRide, we may process:

• Contact and account data: name, email, phone, organization, role, account identifier, communications, and consent records.
• Provider and workforce data: service areas, services, fleet and capacity ranges, languages, experience, qualifications, certifications, application answers, review notes, assessment results, Academy progress, and credential status.
• Healthcare-partner data: organization type, work contact details, service area, expected ride volume, payer model, and pilot objectives.
• Mobility-request data: requester type, first name, contact details, pickup area, destination, date, time, recurrence, mobility requirements, language preference, requested companion or interpreter support, and payment preference. These details can reveal health-related or accessibility needs and are treated as sensitive.
• Community-research data: submitted stories, city, state, ZIP code, relationship to the experience, barriers, suggested improvements, follow-up choices, and publication permission.
• Technical and activity data: pages viewed, referring website, campaign tags, CTA clicks, random session identifier, general device category, timestamps, and approximate location signals described below.
• Administrative and security data: review decisions, workflow status, authorized actor, access activity, audit events, support records, and incident or privacy-request records.
• Transaction records if payments are activated: amount, status, processor reference, fees, refunds, disputes, and settlement data. AccessRide does not intend to store full card or bank-account numbers.

Where information comes from

We receive information directly from you or an authorized representative, from signed-in account activity, from organizations participating in a pilot, and from service providers that support hosting, authentication, security, screening, communications, assessment, or payment processing. We may also create internal review, verification, quality, and audit records from those sources.

How we use information

We use information to respond to inquiries; review mobility requests; evaluate provider and partner readiness; coordinate interviews and document requests; administer training and assessments; support protected workspaces; research transportation barriers; improve services; measure launch interest; secure the platform; prevent misuse; keep required business records; and meet contractual, safety, or legal obligations. AccessRide does not use sensitive health-related request data for targeted advertising.

Mobility-request minimization

Echo organizes a request into structured fields and asks the requester to review the result before submitting. For submissions made through Echo v2, AccessRide does not retain the original free-text narrative after submission; it retains the reviewed structured request. Requesters should provide only the transportation and accessibility details needed for review. AccessRide will use a separately approved secure process before requesting detailed health records or insurance identifiers.

Community research stories

Story contributors may submit anonymously or use a first name and last initial. The form collects city, state, and ZIP code to produce protected planning analytics. Maps, location trends, ZIP insights, market scores, and individual submissions remain in the protected administrator workspace and are not published as a public dataset. Stories are not published automatically. A reviewed, de-identified excerpt may be considered for public educational or awareness materials only when the contributor separately grants public-sharing permission. That permission does not authorize publishing an email address, ZIP code, or private detail.

Launch analytics

Public-site analytics may record an anonymous browser-session identifier, pages viewed, referring website, campaign tags, CTA clicks, general device category, and an approximate city, region, and country supplied by the hosting network. When that coarse network location is unavailable, AccessRide may use the browser's time-zone region and language locale as a broader fallback. Visitors may choose to share an approximate service area. With permission, the browser compares the device location with AccessRide planning areas and sends only the matching area name; exact coordinates never leave the browser and are not stored by AccessRide. AccessRide does not intentionally store raw IP addresses or patient information in launch analytics.

Authenticated account activity

When an administrator, provider, Academy participant, or healthcare sponsor accesses a protected AccessRide area, AccessRide may record the account email, a random browser-session identifier, protected area accessed, device category, first and last activity time, activity count, and an approximate regional location for access auditing, security, provider support, and market planning. Regional detail may include city, state, ZIP, county, metro area, browser time zone, and country. A user may directly confirm city and ZIP or consent to a named AccessRide service-area match; otherwise, available network information may provide an estimate with a lower confidence label. Network estimates can reflect a carrier gateway, corporate network, or VPN. AccessRide does not intentionally store raw IP addresses, street addresses, or precise coordinates in authenticated activity records. These records expire after 180 days.

Founding Provider Survey and provider operations

The Founding Provider Survey collects business contact information, service areas, fleet and ride-volume ranges, capacity, referral sources, software use, business challenges, certifications, feature priorities, and founding-program interest. Identifiable answers and internal lead scores are restricted to authorized AccessRide administrators. AccessRide may use de-identified, aggregated patterns for planning and research and will seek separate permission before attributing a quote to a named company.

The protected Provider Operations Suite may store business contacts, driver-roster details, internal quote templates, generalized pickup and destination labels, service type, dates, times, recurrence, operational status, confirmation drafts, and account activity. Records are separated by signed-in provider account. Providers must use an internal rider reference and must not enter patient names, diagnoses, medical records, insurance identifiers, payment-card data, or other protected health information during the private beta. Confirmation messages are drafts only and are not automatically sent.

Provider sandbox access

After a transportation provider submits a request for more information, AccessRide places a secure, browser-only access token on that device so the provider can open the fictional workflow sandbox. The token is stored as an unreadable hash in AccessRide's database, is connected to the provider inquiry for access control, and expires after 30 days. The sandbox does not store changes made to its sample ride requests and must not be used for patient, medical, payment, or other sensitive information.

Sharing and service providers

AccessRide may disclose information to service providers that support hosting, storage, authentication, security, screening, assessment, communications, payment processing, banking, accounting, insurance, legal, and business operations. Access is limited to the service being provided and is subject to the applicable contract or professional duty. AccessRide may also disclose information to a healthcare or transportation partner when authorized and necessary for an approved workflow; to protect a person, AccessRide, or others; when required by law; or in connection with a business transaction. AccessRide does not sell personal information or sensitive data, and it does not share personal information for cross-context targeted advertising.

Retention and deletion

AccessRide keeps information only for the documented business, safety, contractual, or legal purpose that applies to the record. Current pilot targets include 180 days after closure for mobility-request review records, 180 days for authenticated access activity, 13 months for public-site analytics, and 24 months after last activity for general inquiries. Provider, training, contract, finance, security, incident, and compliance records may be retained longer when needed for an active relationship, dispute, audit, legal hold, or applicable documentation requirement. Records are deleted, de-identified, or securely destroyed when the approved period ends. A legal hold overrides ordinary deletion until released.

Security and healthcare information

AccessRide uses role-based access, data minimization, protected administrator workflows, audit records, and reasonable administrative and technical safeguards appropriate to the pilot. No system is completely secure. AccessRide is preparing for healthcare-partner requirements; whether HIPAA applies depends on the specific service, parties, data, contracts, and business-associate analysis. AccessRide will not represent a workflow as HIPAA-ready until required agreements, vendor safeguards, risk review, and operating controls are approved.

Your privacy choices and requests

You may ask AccessRide to confirm whether it processes your personal data and, where applicable, request access, correction, deletion, or a portable copy. You may also withdraw optional follow-up or public-sharing permission for future use. AccessRide does not currently sell personal data, use it for targeted advertising, or use profiling to make decisions that produce legal or similarly significant effects.

Send a request to admin@joinaccessride.com with the subject AccessRide Privacy Request. Describe the request and the email address or reference number connected to the record. Do not email identification documents unless AccessRide asks you to use an approved method. AccessRide will verify the requester, acknowledge the request, and generally respond within 45 days. If AccessRide denies a request, the response will explain how to appeal. Send an appeal to the same address with the subject Privacy Request Appeal; AccessRide will provide a written appeal response within 60 days.

Report a suspected privacy or security incident

If you believe information was sent to the wrong person, exposed, lost, altered, misused, or accessed without permission, email admin@joinaccessride.com with the subject URGENT - Privacy or Security Incident. Include what happened, when it happened, the affected AccessRide area or reference number, and a safe way to contact you. Do not include passwords, medical records, Social Security numbers, full payment-card numbers, or other sensitive documents in ordinary email. For immediate danger or a medical emergency, call 911.

Children and changes to this notice

The AccessRide pilot is intended for adults and authorized organization representatives and is not directed to children under 13. A parent, guardian, or authorized representative should make a request involving a minor. AccessRide may update this notice as the pilot, vendors, laws, and services change. A material update will receive a new effective date and version.

Contact

Privacy questions, requests, and appeals may be sent to admin@joinaccessride.com.