MYRIDEPAGE.COM

Privacy

LAST UPDATED 8 SEPTEMBER 2026

This page describes what MyRidePage actually does with your information. It is written to match how the service runs today, not to list every practice a larger company might have.

Who we are

MyRidePage.com builds a custom web page for one vehicle that a private owner is selling. We are based in Las Vegas, Nevada. You can reach a person at oakweb@gmail.com or 702-337-5605. MyRidePage is a subsidiary of Oakweb.AI, a web design and development company.

What we collect, and why

Seller accounts and work in progress
Your email identifies your workspace and receives sign-in links and service updates. We record steps such as requesting and using a sign-in link, starting a draft, adding material, requesting review and starting checkout so we can resume your work and investigate problems.
Buyer inquiries and requested resources
Contact-seller forms collect the details you submit, such as email, optional phone number and message, for the seller and authorized staff. Buyer inquiries, seller-page requests and photo-checklist requests are recorded separately. Requesting a checklist does not create an order.
Private inquiry follow-up
Sellers may save notes about calls or messages, follow-up statuses and dates. These are visible to the listing owner and authorized staff, not automatically published on the listing or included in buyer replies or activity emails. A follow-up status is not a new inquiry or verification of a sale.
Your material
Photos, video, service records and information about your vehicle help us prepare the page. You choose what to publish and which documents to share. Private draft material is accessible to you and authorized staff, not other customers.
Page activity and reports
On instrumented published listings, we also record call-button clicks, text-button clicks and non-autoplay video starts, at most once per action type per page load. A random per-render token is hashed to suppress duplicates; it is not reused across page loads or stored in browser cookies/storage by this feature. These records contain the listing, action, token hash and timestamp, not the destination phone number, message contents, IP address or user agent. Known bots, approved internal devices and signed-in owners/admins are excluded where identifiable; other automation or testing can remain. Earlier activity is unmeasured, and these events do not prove a completed conversation or sale.
We record page loads, dates, referring sites and campaign categories, plus submitted inquiry and document-access activity. Seller dashboards show daily, weekly and monthly traffic, referral sources and inquiry counts. Page loads are not unique people, and an inquiry is not proof of a sale. Enabled email reports go to their configured recipients; delivery logs record sending status, not whether you read the email.
Server logs
The server records request information such as IP address, browser, requested address and time for operation, security and troubleshooting.
Cookies and referral context
Sign-in and anti-forgery cookies support account access and forms. Short-lived workflow context helps distinguish how a service request began. A referral cookie and a referral code bound to an email sign-in token can preserve an eligible referral benefit in another browser. Advertising consent choices and measurement are described below.

Payment

Stripe handles card payment on its checkout page. We do not receive or store your full card number. We keep order, checkout-session, amount, currency and payment-status records to verify payment, publish the approved page and investigate support issues. A checkout visit or cancellation is not recorded as a confirmed purchase.

Files you send us

Portal uploads are stored on our server at Vultr, outside the static public website directory. Access is controlled by the application. Published photographs are public; new PDF uploads start Private. You may explicitly share a reviewed document publicly, behind a PIN or after the page is marked Sold. A shared PIN can be forwarded and does not verify the holder's identity. After-sale sharing is available to PIN holders, not only the eventual buyer.

Buyer-uploaded paperwork stays private to the seller and authorized staff. Staff may view your workspace across MyRVPage, MyRidePage and MyBoatPage through our shared administration tools to help prepare or support your page. Other customers cannot access your private workspace.

Review and redact personal details before sharing records. We do not promise automatic redaction or malware detection. Files sent by email also pass through the email providers involved; you may arrange that intake with Phil.

AI-assisted preparation

Phil may use AI assistance when preparing text or imagery, with human review and your approval before publication. Uploading here does not automatically send your files to an AI provider. If preparation needs an external AI service, Phil will discuss which material to use with you. Do not assume that AI-generated descriptions verify a vehicle's condition or history; check the draft against your records.

Advertising measurement

Where Google Ads measurement is configured, the service's advertising and checkout pages measure visits, checkout starts and confirmed purchases. Checkout starts are separate from purchases; a purchase requires server-verified payment. These events do not include your email address, uploaded documents or full payment-card details.

On pages carrying the Google script, it starts with advertising cookie storage denied. A banner offers a choice. Until you agree, or if you decline, limited cookieless signals may still be sent to estimate results. Agreeing allows advertising-measurement cookies. The consent choice is stored so it can be respected on later visits. Attribution may be limited by browser settings, blocked scripts, different devices or declined consent.

Who else sees your information

We do not sell contact information or enroll you in a marketing list just because you start a workspace, ask for a sign-in link, contact a seller or request a checklist. Necessary account, payment, support and file-retention notices are separate from optional activity reports.

How long we keep it

We retain workspace and order information to provide the service and resolve support issues. File cleanup is separate from account, payment and history records; deleting files does not automatically erase those records. Ask us to review an account-data deletion request separately.

Active listings are excluded from automatic file cleanup. An eligible page recorded as Sold for at least 14 days may enter a manually started 60-day warning period, with email reminders spanning at least six weeks and an exact Pacific Time deadline. Keep requests, contact, new activity, changed files, failed or uncertain notices and a missing final inbox check hold cleanup. Phil reviews replies manually.

Download your private file ZIP while the originals are available. Before eligible originals are removed, checked on-server recovery copies are made and kept for at least 30 more days. A keep request during that period can queue a private restore. Permanent cleanup needs a separate final check. Recovery copies are on the same server, not an off-site backup guarantee. See file-retention terms and contact Phil if you need more time.

Your page is public on purpose

Your approved, published sale page is meant to be shared with buyers. Treat published photos, text and publicly shared documents as public. Keep sensitive originals Private or share reviewed, redacted copies using your chosen controls. We cannot retract copies somebody has downloaded, photographed or forwarded.

Asking us about your information

Email oakweb@gmail.com to ask what we hold, request a correction or deletion, or ask about report recipients. We may verify that you control the account before acting and will explain the scope of the request, including any records retained separately. There is no charge to ask and no special form is required.

Changes

If our practices change, this page changes with them, and the date at the top changes too.