Privacy notice. In plain English.

Who we are

One-Touch DVIR is made and run by RAM Venture Solutions LLC, a Washington limited liability company based in Omak, Washington. When this notice says “we” or “us,” it means RAM Venture Solutions LLC.

This notice covers two things:

• This website, onetouchdvir.com.
• The One-Touch DVIR service: the driver app, the mechanic app, the text and email alerts, and the reports we run for school bus garages.

Questions go to Bob McElderry, our founder, at 509-429-9805 or bob@ramventuresolutions.com.

What this website collects

Short version: we don't watch what you do here.

• No analytics and no advertising. We don't run visitor tracking, analytics or ad tools on this site.
• No tracking cookies. We don't set any tracking or advertising cookies.
• No forms. Nothing on this site asks for your name or email address. The pricing calculator works inside your browser, and what you enter isn't sent anywhere.
• Your Night or Day choice stays with you. If you pick a theme, your browser remembers it in its own storage on your device. It isn't sent to us.

Our web host

This site is hosted by Cloudflare. Like any web host, Cloudflare processes standard information about each visit, such as your IP address and browser type, to deliver the pages and protect the site from attacks. In some situations Cloudflare adds its own security features, such as a cookie or a small script that tells people apart from bots. We don't use them to track you.

If you email, call or text us

Email links open your own email app, and phone links open your phone. If you contact us, we use what you send, such as your name, email address, phone number and message, to answer you and follow up on your question. We don't sell it. Our business email is run by Google.

App demonstrations

The app screens on this site are demonstrations filled with sample data. They aren't connected to any garage's records.

Links to other sites

We link to other sites, such as eCFR and the Federal Register. When you follow a link, that site's own privacy practices apply.

The service: your district's records

One-Touch DVIR is made for school districts, educational service districts and school bus contractors. In this notice we call each one “the district.”

Each district gets its own spreadsheet, its own office system and its own web address. No two districts share a database. Records are kept on Google, in an account we manage. On the way there, app traffic passes through a small function on the garage's own app site at Netlify (see Who else handles it).

The district's supervisor has live access to the district's records. A monthly PDF report arrives on the 1st, and the district can get a complete copy of its records whenever it asks.

If you're a driver, mechanic or supervisor with a question about your own information, start with your supervisor. We'll help the district answer.

What the service records

Only what a bus garage needs to record inspections, fix buses and file its reports.

Behind the scenes

• Troubleshooting logs. A copy of each submission as it arrives, with PINs, passwords and keys blanked out, and error reports from the apps. Older log rows may still show the PIN. We use them to find and fix problems.
• Reports. The monthly PDF reports, saved in Google Drive.
• Nightly backups of each district's spreadsheet.

On the driver's phone

The driver app keeps the driver's name, PIN and bus, their last 200 entries, anything still waiting to send, items the office turned back, and the app's settings. Clearing the app's website data in the phone's settings removes all of it, including anything not yet sent, so send first.

What the service never asks for

• Student names or ID numbers
• Student addresses or bus stops
• Drivers' email addresses or phone numbers
• Contacts, photos or messages on the phone

Approximate location

A notice, not tracking. The app notes roughly where a bus was inspected, and nothing more.

• When the app looks Only while the app is open on screen: when it starts, or when the driver comes back to it. It keeps just the latest reading, on the phone.
• When it's saved Only when the driver sends an inspection. The reading is attached to that inspection, with the phone's own estimate of how accurate it is.
• Never Never in the background, never while the app is closed, and never sent on its own. Trips don't record location at all.

It's the location the phone reports. The app asks for a quick, low-power reading rather than the most precise one, but some phones may still report a close location. If a phone can't give a location, or location is turned off for the app, the inspection sends anyway with the location left blank. Location never delays or blocks an inspection.

Who sees it. The location is saved with the inspection record, and defect alert emails include a map link to it. The text alerts don't. The district's supervisor and mechanic can see it, and so can we, because we run and support the service.

The Driver Electronic Signature Agreement in the app includes a shorter location notice. This section is the fuller description. We never sell location or share it for advertising.

Text message alerts

One-Touch DVIR sends text messages to district staff when a driver reports a defect, plus occasional connectivity test messages. Within seconds of a defect report, the mechanic and supervisor get a text saying which bus and what's wrong (unless the district has set quiet hours for texts), and an email with the driver's note and, when the phone gave a location, a map link. Texts are sent through Telnyx. They are work alerts, never marketing.

How phone numbers are added

There is no public sign-up form and no online opt-in. Every number on the alert list belongs to an authorized district staff member, such as the mechanic or supervisor, or to our own support team. District staff give verbal consent in person during onboarding. Before adding a number, the supervisor reads this script aloud:

The staff member must answer “Yes” out loud before their number is entered. The supervisor records the date of consent, the staff member's name and the phone number in the district's onboarding log.

What to expect

• Message frequency varies with how many defects are reported. Typical volume is fewer than five messages per recipient per day.
• Message and data rates may apply from your wireless carrier. One-Touch DVIR doesn't charge recipients anything.
• Quiet hours. A district can pick an overnight window, person by person, when driver-defect texts to that person stay quiet. The email still goes out.
• Carriers. Alerts work with all major US wireless carriers. We aren't liable for messages that a carrier delays or fails to deliver.

• STOPReply STOP to any alert to opt out. You'll get one final confirmation message and no further alerts.
• STARTReply START to turn alerts back on.
• HELPReply HELP for help, or contact your district supervisor.

You can also stop alerts by asking your district supervisor.

Your mobile information is not shared

Phone numbers in the system are used solely to deliver operational defect alerts and connectivity tests to district staff who have been onboarded to the program by the district supervisor. Telnyx, a licensed US telecommunications carrier, sends the messages as our service provider. It processes them purely for delivery, and it does not receive consent information for marketing purposes. The other companies named under Who else handles it, including the AI assistants we use for support, may see these numbers only to run or support the service, never for marketing.

Who else handles it

We use these companies to run this website and the service. We share information with them only to get that work done.

• GoogleService

  Google holds each district's spreadsheet (Google Sheets), in an account we manage, and runs the office side of the service (Google Apps Script). Monthly reports and nightly backups are saved in Google Drive, and alert and report emails go out through Gmail.

  Google also runs our business email.

• NetlifyService

  Delivers the driver and mechanic apps to phones. App traffic normally passes through a small function on the garage's own app site on its way to Google; that function logs only timings and error reasons. Netlify's own request log keeps the web address of each request for about a day, and a few of those addresses carry a driver's PIN (while the driver sets up the app) or a mechanic app password. To keep the apps quick, Netlify briefly keeps a copy, for a minute or so, of the open-defect list (which includes driver names and notes), the bus list and the Out of Service list. Records are kept at Google, not at Netlify.

• TelnyxService

  Sends the text message alerts. It handles the phone numbers on the alert list and the words of each alert, which include the bus and the defect.

• CloudflareThis website

  Hosts this website. It doesn't handle district records.

• AnthropicSupport

  We use its AI assistant, Claude, for support and troubleshooting. It can read a garage's records while doing that work.

• xAISupport

  We use its AI assistant, Grok, for support and troubleshooting, including drafting replies to support emails, which we review and send ourselves. It can read a garage's records and support emails while doing that work.

• GitHubOur files

  Keeps our code in a private repository, along with working copies of some garage spreadsheets, which can include driver names.

Like any web service, the companies that deliver the apps and this website see standard technical information, such as IP addresses, when a phone or browser connects. We don't store IP addresses in district records.

There's no AI in the inspections themselves. The AI assistants above help us with support.

Never for advertising. We don't sell personal information, and we don't share it for advertising or marketing.

When the law requires it

We may disclose information when the law requires it, for example to answer a court order or subpoena. If someone asks us for a district's records, we tell the district so it can respond, unless the law forbids it.

A public school district's records may be public records under Washington's Public Records Act, chapter 42.56 RCW. The district answers public records requests for its own records.

How long we keep it

• Inspection and trip records stay for as long as the district uses the service. The service never deletes an inspection on its own.
• The district's own rules. The district decides how long it must keep its records. Washington public school districts follow the Washington State Archives retention schedule for public schools. Where the federal inspection-report rules apply, they call for keeping reports for three months.
• Nightly backups are each kept for 30 days.
• Troubleshooting logs stay in the district's spreadsheet alongside its records, and are deleted with them when an agreement ends.
• Alert phone numbers and email addresses are kept while that person is set up to receive alerts, and taken off the alert list when the district removes them. Past alerts in the troubleshooting logs and the settings change log still show the number or address until the district's records are deleted.
• When an agreement ends, the district has 30 days to take a complete copy, at no charge. We delete its records from the service within 60 days of the end date (sooner if the district confirms it has its copy), and backups within 90.
• Emails you send us are kept in our business email account.

How we protect it

• Every connection between the phone, the office system and the alert services uses HTTPS encryption.
• Each district has its own spreadsheet, office system and web address. No shared database.
• Each inspection is signed with the driver's PIN on file, a PIN the supervisor assigns. The office checks the PIN against the driver's name, and marks any inspection where they don't match.
• Every change in the mechanic app needs a password, and a phone is locked out for 15 minutes after five wrong tries. Some lists, such as the open-defect list, open with the garage's app key alone. See Sign-in and safeguards.
• The app only ever adds inspection records. It never edits or deletes one.
• We give access to a district's records only to the district's own staff, the people at RAM Venture Solutions who set up and support the service, and the service providers listed above.

No system is perfectly secure, and we don't claim ours is. If we confirm a security incident affecting a district's records, we tell the district within the time its agreement sets, and we help it meet its own notice duties under Washington law.

Students and children

One-Touch DVIR is a work tool for adult school transportation staff. Neither the service nor this website is meant for children.

The service never asks for a student's name, ID, address or bus stop. The Mileage & Pupil Tracker records how many students rode: a number, not a name.

Notes are free text, so drivers and mechanics should never type a student's name. If one ends up in a note anyway, we treat it as the district's confidential information: used only to run the service, never sold, and never used for advertising.

Your choices

Visiting this website

You can browse without telling us anything. You can block or clear cookies and site data in your browser. The site still works; your theme choice just resets.

Drivers, mechanics and supervisors

• See, correct or remove your information: the district is in charge of its records, so start with your supervisor. We'll help the district with any request.
• Leaving the district: your supervisor removes you from the system. The district may still need to keep inspection records you signed, under its own retention rules.
• Location: if location is turned off for the app on a phone, inspections still send, with the location left blank.
• Text alerts: reply STOP to any alert, or ask your supervisor.

Changes to this notice

When we change this notice, we'll post the new version on this page with a new “last updated” date, shown at the top of the page. Each garage's driver app site also carries an older privacy page, dated May 17, 2026. Where the two differ, this notice is the current one.