Home / Privacy

Privacy Policy

Last updated: September 25, 2026

Release Shield Network is owned and operated by Cascio360 LLC. This policy describes information handled through our website, accounts, vehicle handoff service, and Release Credit purchases.

The separate Driver Privacy Notice and Verification Consent governs the driver-verification consent workflow. This policy does not replace those notices or consent requirements. Viewing this policy does not provide consent or electronically sign a verification document.

Information we collect

Accounts and organizations

When you register, we collect your full name, organization legal name, business email address, and password. We store a password hash rather than your password. We maintain account and organization identifiers, membership roles, account status, email-verification status, and related timestamps.

Vehicle and carrier information

Release records can include a vehicle’s VIN or other supported identifier, model year, make, model, and trim. Assigned carrier information can include company name, contact name, phone number, email address, MC and USDOT numbers, load or order references, and notes.

Driver information and documents

The service handles driver names, mobile numbers, phone-verification records, the front image of a driver’s license, and Certificates of Insurance submitted for a Release. Uploaded documents may contain additional information visible in those documents.

Pickup and Delivery Contacts

Release records can include contact names, phone numbers, company names, pickup and delivery addresses, and instructions. We also handle recipient email addresses supplied to send contact invitation links.

Handoff photographs

At pickup, the Pickup Contact captures a current photograph of the driver and an exterior photograph of the pickup vehicle and its attached trailer or equipment, when applicable. At delivery, the Delivery Contact captures a current photograph of the driver. These photographs become evidence associated with the Release.

Handoff, signature, and consent records

We maintain pickup and delivery verification status, contact confirmations and decisions, signer names, electronic-signature affirmations and methods, and associated Release and verification-session references. Driver consent records include notice and consent versions, language, text-integrity hashes, and timestamps. Where a drawn-signature record exists, its signature artifact and integrity hash are retained with that record.

Security and operational information

Account security records include sign-in sessions, email-verification and password-reset records, and unsuccessful sign-in attempt information associated with a hashed email identifier. Verification records can include browser user-agent information. Server access logs record technical request information, and the application records operational errors and audit events.

Payments and credits

We maintain Release Credit purchase amounts, credit quantities, payment status, payment-provider references, and related credit, refund, and dispute records.

How we use information

We use this information to operate accounts, associate users with their organizations, control access, verify email addresses and driver mobile numbers, support password resets, and administer the service.

Release information, documents, photographs, and confirmations support human review of the person present, pickup and delivery decisions, and a documented record of each verified transfer of vehicle possession from release through delivery.

Signatures, consent records, timestamps, and audit events document actions associated with a Release. File-integrity hashes support checks that protected documents and evidence match their recorded contents.

We use operational and security records to limit repeated unsuccessful sign-in attempts, investigate errors, and maintain service security. Payment and credit records support checkout, credit allocation, payment reconciliation, and transaction history.

Access to Release information

The service uses organization membership, account permissions, and verification access controls to restrict access to Release information.

Authorized organization users and platform administrators can access information through their permitted service functions. Pickup and Delivery Contacts receive access to the information and actions made available through their verification links, including driver-license review where provided.

Documents and handoff photographs are stored separately from public website assets and served through protected application routes. Authorized reporting and evidence-export functions can include Release information, verification records, and supporting evidence.

Cookies

Account services use a session cookie to recognize a signed-in user and a form-security cookie to help protect against forged requests. Verification workflows also use browser-session controls to associate access with a verification session. Blocking required cookies can prevent these features from working.

Service providers and external lookups

We use Resend to deliver service emails, including email verification, password resets, contact invitations, and Release notifications. Delivery involves sending the recipient’s email address and message content to Resend. Messages can include names, Release information, and links needed to complete the relevant action. We maintain delivery and audit records for service-email operations.

Driver mobile-number verification uses Twilio Verify. The service sends the mobile number to Twilio to request a verification text message and submits the entered verification code for checking. The separate driver-verification notices and consent flow apply to this process.

Release Credit payments use Stripe Checkout. Payment details are entered through Stripe’s checkout. We send purchase and organization references and credit-package details to Stripe and receive payment identifiers and status information to manage purchases and credits.

When VIN decoding is used, the VIN is sent to the National Highway Traffic Safety Administration’s vehicle-information service. Postal-code lookup sends the entered ZIP code to Zippopotam.us to retrieve location information.

Retention

Closing an organization changes its access status and revokes associated sign-in sessions; it does not delete its Release records, protected documents and evidence, audit records, or financial history.

Historical verification and signature records remain part of the recorded handoff history. Signing out does not delete account or Release information. This policy does not specify a fixed deletion schedule.

Driver verification notices and consent

Drivers receive a separate Driver Privacy Notice and Verification Consent within the verification workflow. Those notices explain the verification information and the consent and electronic-signature actions requested from the driver. This policy does not change those notices, recorded consent versions, or consent requirements.

Privacy questions

For questions about this policy or information associated with your account or a Release, contact Release Shield Network Customer Care at (941) 899-3700, Monday through Saturday, 9:00 AM to 6:00 PM Eastern Time.