SafeSpin24 WDF-Access for technology partners — a physical-access layer, not a competing POS

No. ShiftFree is not a WDF POS, payment processor, card-reader provider, mobile-wallet platform, kiosk provider, merchant-services provider, or payment system of record.

WDF and payment partners continue to manage their core functions, including orders, pricing, payments, production, fulfillment, customer records, transaction history, settlement, and reporting. ShiftFree adds a controlled physical-access, monitoring, and customer-recovery layer around the operator's service experience.

No. ShiftFree is designed to complement WDF software providers, not replace them.

A WDF platform remains the authoritative source for the customer, order, payment, production, fulfillment, pickup, delivery, and communication workflow. ShiftFree helps the operator manage approved customer entry, after-hours drop-off and pickup access, physical-handoff event context, and access-related customer support.

No. ShiftFree is payment-neutral.

It does not replace card readers, payment terminals, mobile-payment apps, kiosks, stored-value programs, loyalty platforms, merchant accounts, payment gateways, processors, transaction ledgers, settlement systems, or payment reporting tools.

A payment provider manages the transaction. ShiftFree helps the owner manage the facility access and customer-support environment around that transaction.

No. Cameras and monitoring support the broader ShiftFree operating model, but the product is not simply a camera system.

ShiftFree combines controlled access, professionally deployed commercial entry hardware, security-event monitoring, two-way audio where deployed, customer support, owner-configured recovery rules, and an operational view for the owner. The purpose is to help the owner operate a more controlled and supportable laundry environment.

ShiftFree's standard WDF Access operation is not designed to receive, store, process, or transmit customer cardholder data.

Payment providers remain responsible for their payment environment, payment credentials, transaction records, authorization, settlement, and applicable payment-security obligations. Any future partner workflow would be separately evaluated, formally approved, and designed around the minimum information needed for a defined operator use case.

Yes — when the laundromat owner has granted permission and established the applicable rules.

FreeByrd can help resolve eligible customer issues, including qualifying transaction refunds, within the owner's approved limits and workflow. The owner determines the refund policy, authorization thresholds, qualifying circumstances, escalation requirements, and exceptions.

FreeByrd does not independently create the owner's refund policy or make unrestricted refund decisions. The underlying payment platform remains the system of record for the transaction and payment activity.

No. ShiftFree can operate alongside an operator's existing WDF software and payment platform without a formal technical integration.

This allows an owner to add controlled entry, approved access windows, monitoring, and customer-recovery support without replacing the systems already in use. Where there is a clear operator benefit, ShiftFree is open to partner-approved workflow and integration discussions.

No. ShiftFree will not claim an integration, compatibility certification, endorsement, or commercial relationship unless it has been formally approved and is actually available.

The initial model is standalone coexistence: owners retain their chosen WDF and payment systems while ShiftFree supports the controlled physical-access and customer-recovery layer. Formal integrations may be considered when a partner and ShiftFree agree on a specific customer need, data boundary, and implementation path.

A future integration could be considered only where it creates a clear benefit for the operator and is approved by the partner.

Potential areas may include an owner-authorized support handoff, a link between an access-related exception and the relevant customer or order record, or a coordinated customer workflow around an approved pickup-access window.

Any integration would preserve the partner's role as the system of record for its core functions. ShiftFree would not seek to create a duplicate payment ledger, WDF order database, production workflow, or customer-management system.

ShiftFree supports the physical handoff environment; it is not a bag-tracking or independent chain-of-custody platform.

A dedicated WDF handoff area may provide relevant event context when an owner reviews a reported issue. That context can help the owner understand what occurred around the physical handoff, but it does not independently confirm bag contents, order completion, customer entitlement, fulfillment quality, or refund eligibility.

The WDF software provider and operator remain responsible for order records, production, fulfillment procedures, and customer remedies.

ShiftFree provides a structured first-response path.

For access-related or routine approved issues, FreeByrd can provide assistance within the owner's established rules. For security events, SpinWatch24 can support live monitoring and two-way audio where deployed. If an issue requires owner judgment, a commercial remedy, order review, production decision, or other exception handling, it is escalated to the owner or designated manager with available context.

The goal is not to remove the owner from every decision. It is to reduce the repetitive, low-value interruptions that currently reach the owner's personal phone.

The operator and its WDF software workflow remain responsible for the order and fulfillment decision.

ShiftFree can help identify an access or handoff-related exception and provide available physical-event context. It does not decide whether an order was correctly processed, whether a garment requires rewash, whether an order is complete, whether a customer is entitled to a credit, or how a fulfillment issue should be resolved outside the owner's approved policies.

The laundromat operator owns the customer relationship.

The WDF platform and payment platform each retain responsibility for the customer information, transactions, and workflows they manage. ShiftFree provides an owner-selected access, monitoring, and support layer that helps the operator serve customers in a more controlled environment.

Yes. ShiftFree is designed for owner-selected operating models, including hybrid, evening-only, overnight-only, and other limited-access approaches.

An operator does not have to convert to a fully unattended store. The owner can decide when access is available, which customers are eligible, what support path applies, how WDF drop-off and pickup work, and when a staffed counter remains necessary.

No. ShiftFree should not be viewed as a guarantee against crime, accidents, disputes, loss, misuse, or operational errors.

It gives the owner more control and visibility through credentialed entry, access-event records, commercial-grade entry hardware, monitoring, alerts, and a structured response path. The owner remains responsible for site policies, local operating conditions, insurance, staffing decisions, customer-service standards, and emergency procedures.

Yes. ShiftFree is open to referral, co-marketing, workflow-alignment, and partner-approved integration conversations with WDF software providers, payment-system providers, and other complementary laundry technology companies.

A referral conversation does not require an immediate technical integration. The first step is to determine whether ShiftFree addresses a real operator need while preserving clear product, data, customer-support, and commercial boundaries.

Start with the operator use case.

The best partnership conversations begin by identifying where an operator experiences friction: after-hours WDF drop-off or pickup, facility access, customer support when the counter is closed, access-related exceptions, or the operational burden of a hybrid or lightly staffed location.

From there, ShiftFree and the prospective partner can determine whether standalone coexistence, referral alignment, workflow coordination, or a later formal integration offers the right path forward.