← RigStory home

RigStory pilot · Updated November 17, 2026

Privacy

RigStory makes selected, source-attributed trailer repair and inspection records available by VIN. This notice explains what the pilot handles and what becomes public.

Who to contact

RigStory is a pilot service operated by CT HOLDINGS, LLC. Contact us at rvhistory@layitdownapp.com; include “RigStory” in the subject. This notice covers the hosted RigStory history service, not the separate Lay-It-Down app or a dealer’s private records.

Information the service handles

What becomes public

A released report can be viewed by anyone who has its link or searches its VIN. It shows the VIN, trailer type, contributor’s public business name, dated work or findings, scope, document reference, publication date and any displayed correction context. Reports can be copied, printed or saved by readers.

Account email addresses, approval details, earlier record versions and withdrawal reasons are not part of the public report. Do not put customer names, addresses, contact information, payment details or confidential notes into any public field. Basic format checks do not replace your review.

How information is used

The service uses this information to review contributor access, match records to a VIN, publish the authorized history, prevent duplicate entries, handle corrections and withdrawals, and respond to support requests. Original work orders, inspection reports and permission evidence stay with the contributor; this pilot has no original-document upload feature.

Hosting and sign-in

The pilot uses OpenAI Sites and Cloudflare infrastructure for hosting, authentication or database processing. Those services may handle browser, network, request and sign-in information as part of operating the site. Sign-in is handled by OpenAI. Their own notices also apply to their services: OpenAI Privacy Policy and Cloudflare Privacy Policy.

Corrections, withdrawal and retention

The database retains contributor and approval information, published records, earlier revisions, withdrawal history, and a private record of contributor approval, suspension and rejection actions to operate the network and trace changes. A correction updates the report while preserving earlier versions privately. Withdrawal removes an entry from future public reports; it does not erase its private history or recall copies already printed or saved by others.

Request-count limits use minute, hour or day windows. Expired counters no longer restrict requests and are removed in bounded batches when later requests arrive; physical removal is not guaranteed at a fixed time when the service is idle.

The operator can export private recovery copies of application records, including earlier versions, withdrawal history and access-review actions. Recovery copies are not public reports. A recovery must account for later withdrawals, corrections and access changes before affected reports are made available again. Contact us about information in retained recovery copies.

To request a correction, withdrawal, or review of information associated with you, use Support & corrections. The team may need enough information to verify the request and the affected record. Account or information deletion is not a self-service feature in this pilot; contact us to discuss a request.

Changes

This page carries its update date. Check it before making a new contribution, especially when the pilot adds features or changes how records are handled.

Privacy · Contributor terms · Support & corrections