Privacy policy
Effective date: August 22, 2026. Draft, pending legal review.
This policy explains what Modern Holding collects through this website and through the RideWise product, and how that information is used. It is written in plain language and is currently a draft: it has not yet been reviewed by counsel and may change before it is finalized.
What the website collects
When you submit the demo request form, we collect the information you enter: your name, company, email, phone number, fleet size, what you use today, and any message you add. We also keep basic server logs for this site, such as IP address, browser type, pages visited and timestamps, which is standard for any website and is used to keep the site running and secure.
How we use it
We use the information from the demo form to schedule your demo, prepare for the call, and follow up by email or phone. We do not sell this information, and we do not share it with third parties except the tools we use to run our own business, such as email and scheduling software.
How the RideWise product handles your data
If you become a RideWise customer, the ride, rider, driver and document data your agency enters into the product is processed under a business associate agreement with your agency. It is encrypted at rest and in transit, hosted in United States data centers, and deleted according to the retention setting your agency configures. We do not put patient data in email.
Google account access
Some of our internal operations tooling signs in to Google accounts we own, using Google OAuth. It requests a single scope, gmail.modify, and it is used only against our own business mailboxes. No customer, prospect or patient mailbox is ever connected.
What it does with that access: it reads message headers and bodies so it can build a daily digest of mail from a short list of senders we are expecting to hear from, it runs searches we ask it to run, and it applies labels. It does not send mail on our behalf.
Where the data goes: the digest is written to a private operations folder on our own server, reachable only over our private network. OAuth refresh tokens are stored on that server, readable only by the account that runs the tool. Message content is not copied into any third party system, is not used for advertising, is not sold, is not shared, and is not used to train any machine learning model.
Our use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. Access can be revoked at any time from the Google account's own permissions page, which immediately stops the tool.
Cookies and tracking
This website does not use advertising or tracking cookies. The only outside connection this site makes is to Google Fonts, to load the typefaces used on the page.
Your choices and contact
To ask a question about this policy, or to request that we delete information you submitted through the demo form, email us at [email protected].
Changes to this policy
We may update this policy as the product and the business change. Once it is out of draft, we will post the current version here with a new effective date.