Early access · September 24, 2026
Data handling notice.
This notice describes the current VendPatch implementation. Company records, pilot inquiries, customer requests, workforce operations, and agreement records are stored on the server. Demo actions and sample data are stored in your browser.
Pilot inquiries
When you request a pilot, VendPatch stores your name, work email, company, machine-count range, operating goal, optional notes, consent, and limited abuse-prevention metadata. We use this information to evaluate and contact you about the pilot. You may ask us to stop contacting you.
Customer requests
When you submit a request, VendPatch stores your description, machine context, optional name, contact details, and any amount you request. Authorized staff at the vending company can review and update the request. Do not include full payment card details, passwords, or health information.
Workforce operations
A vending company may use VendPatch to store employee names, roles, assignments, acknowledgement and completion records, time entries, correction requests, onboarding checks, manager decisions, and work evidence. Employees can see their own assigned work and time records; authorized owners and managers can review company workforce records. VendPatch does not continuously track employee location, automatically reduce pay, or treat completion speed as proof of misconduct. Companies remain responsible for lawful employment, pay, break, scheduling, retention, and notice practices.
Electronic agreements
VendPatch Sign stores the agreement, signer name and email, electronic-signature representation, consent version, timestamps, hashed network and browser identifiers, document fingerprints, signing events, and completion evidence. Private signing links expire and can be replaced or revoked. Finalized evidence is retained to protect the integrity of the agreement.
Optional product analytics
VendPatch asks before counting a small set of first-party actions, such as starting the demo, selecting a plan, starting signup, and completing onboarding. These events contain no form contents, email address, raw query string, advertising identifier, or cross-site identifier. A random identifier lasts only for the current browser tab, raw events expire after 30 days, and the footer privacy control lets you change your choice at any time.
Tracking and security
Your private tracking or signing token grants access to its associated record. Anyone holding a live link may access those details; keep it private. VendPatch stores token hashes rather than the private token itself. Hashed network and browser identifiers help prevent abuse and support agreement attribution.
Infrastructure and browser storage
VendPatch uses Vercel to host the application, Neon for authentication and company data, Cloudflare R2 for supported private file storage, Stripe for subscription billing, and Resend for configured transactional email. Session cookies keep you signed in. Your browser may store demo data and private tracking links. SMS delivery is not currently enabled.
Questions and data requests
Contact your vending operator for customer request, workforce, or agreement questions. Company users, employees, and pilot applicants should contact the person who provided their VendPatch access for access, correction, or export requests. Agreement and audit evidence may be retained where needed to establish, exercise, or defend contractual rights.