YardVis Executive Series · 04
Platform Overview
Secure by default. Simple to deploy. Built to earn operational trust before it earns anything else.
YardVis LLC · 2026
Introduction
This is not a marketing overview. It is the operational architecture, security model, and data practices behind YardVis — written for the people who decide whether a pilot gets approved.
We wrote this document because we understand that before an operations team adopts any new software, someone in IT, legal, or leadership needs to understand how it works, what it touches, and how it handles data. This document is written for that person.
Platform Philosophy
YardVis was designed around six operational principles:
Simple to deploy
No hardware. No IT project. No integration required to start. YardVis runs in any modern browser and is live within hours.
Secure by default
Authentication, role-based access, row-level data isolation, and encryption are built into the platform — not added as optional features.
Least privilege
Every user role in YardVis has access to the data they need for their function — and no more. Drivers see check-in flows. Dock coordinators see assignments. Leadership sees operational summaries.
Customer owns the data
Your receiving records are yours. YardVis does not sell, share, or use customer operational data for any purpose other than powering your dashboard and reports.
Operational reliability
The platform is designed to be available when receiving operations are active — including early morning, overnight, and weekend shifts.
Continuous improvement
Security, access controls, and operational reliability are reviewed and improved on an ongoing basis as the platform evolves.
System Design
YardVis is a cloud-hosted web application. There is no on-premise component. The platform architecture follows a standard secure web application model:
Drivers interact with YardVis through a QR code check-in flow — a mobile-optimized web page that does not require app installation. Dock coordinators and operations managers access the platform through any web browser. All data flows through encrypted connections to the YardVis cloud platform and is stored in a secure, isolated operational database.
Data Protection
YardVis applies seven data protection controls to every customer environment:
Authentication
All platform access requires verified credentials. Unauthenticated access to operational data is not possible.
Role-based permissions
Access to features and data is controlled by user role. Drivers, dock coordinators, and administrators each have scoped permissions appropriate to their function.
Facility-level isolation
Data from one facility is not accessible to users of another facility, even within the same customer organization, unless explicitly configured.
Row-Level Security
Database-level row-level security ensures that each user's data queries are automatically filtered to the scope of their permissions — enforced at the data layer, not just the application layer.
Encryption in transit
All data transmitted between users and YardVis servers is encrypted using TLS.
Encryption at rest
All stored operational data is encrypted at rest.
Private BOL / document storage
Bills of lading and receiving documents are stored in private, access-controlled storage. Documents are not publicly accessible.
Compliance Roadmap Note
Third-party penetration testing and formal compliance certification (including SOC 2 Type II and ISO 27001) are on our roadmap. They are not current certifications, and we do not represent them as such.
Operational Integrity
Beyond data protection, YardVis is designed to maintain accurate operational records:
- Receiving records are immutable once completed — they cannot be silently edited or deleted by end users.
- Timestamps are server-generated, not client-reported, to prevent manipulation.
- Dock assignment changes are logged with a new record rather than overwriting the original.
- Document uploads are linked to specific receiving records and stored with version history.
- All actions by authenticated users are tied to their user account and timestamp.
- Audit trails are available for facility administrators upon request.
Privacy & Data Ownership
| Topic | YardVis Position |
|---|---|
| Who owns the data? | The customer. YardVis holds data on behalf of the customer and does not claim ownership. |
| Is data sold to third parties? | No. YardVis does not sell, license, or share customer operational data with any third party. |
| Is data used for training AI models? | No. Customer operational data is not used to train any machine learning or AI system. |
| Can data be exported? | Yes. Customers can export their receiving records in standard formats upon request. |
| What happens to data after a contract ends? | Customer data is retained for 30 days post-contract termination, then deleted. Export is available during this window. |
| What personal data is collected from drivers? | Only what is required for the check-in flow: name and carrier affiliation. No financial, biometric, or sensitive personal data is collected. |
Deployment & Pilot Readiness
YardVis is designed to be deployed at a facility without an IT project, integration effort, or hardware procurement. The standard deployment process:
Account setup
Facility configured, docks mapped, user accounts created — completed by the YardVis team
QR signage
Printed check-in QR codes placed at driver entry points — no app required for drivers
Team onboarding
Dock coordinators and supervisors walk through the platform in under 30 minutes
First truck
First live receiving record created on Day 1
Active pilot
Full 30-day pilot period with weekly reviews and an end-of-pilot executive summary
Frequently Asked Questions
Does YardVis require integration with our WMS or TMS?
No. YardVis operates independently and does not require integration with any existing system to function. Integration options are on the product roadmap for future phases.
Does YardVis require app installation on employee devices?
No. YardVis runs in any modern web browser. Drivers use a QR-code-based mobile web flow. No app installation is required for drivers or dock staff.
Where is data stored?
YardVis data is stored in cloud infrastructure hosted in the United States. Data does not leave U.S. jurisdiction.
Can we control who at our facility has access to YardVis?
Yes. Facility administrators control user accounts, roles, and access levels. YardVis staff have access to platform infrastructure for support and maintenance purposes only.
What happens if YardVis is unavailable?
YardVis is designed for high availability during operating hours. In the event of an outage, receiving operations can continue using existing manual processes. YardVis does not sit in the critical path of physical receiving — it captures and analyzes what happens, but the operation does not depend on it to function.
Is YardVis HIPAA-compliant?
YardVis does not process protected health information (PHI). HIPAA compliance is not applicable to the YardVis platform.
Can we run a pilot without a long-term commitment?
Yes. The standard YardVis engagement begins with a 30-day pilot. No long-term contract is required to start.
Who do we contact if we have a security concern?
Security questions and concerns can be directed to akshay@yardvis.com or naman@yardvis.com. We take security feedback seriously and respond promptly.
Questions
If you have questions about YardVis architecture, security, or data practices that are not addressed here, reach out directly:
Akshay Kalia akshay@yardvis.com
Naman Sharma naman@yardvis.com