Back

Transparency

AI transparency disclosure

How the portal describes AI-assisted workflows, platform boundaries, data storage, and subprocessors.

AI-assisted vs. human-touched work

Last Mile Strategies uses software and AI-assisted workflows to make vendor, invoice, benchmark, and savings review faster. AI may help extract text from customer-provided materials, classify spend, summarize supplier context, compare options, or draft internal review notes.

AI assistance does not replace Last Mile's responsibility for the product experience. Customer-impacting recommendations, supplier introductions, savings opportunities, and support responses are designed to remain human-touched before they become business guidance or customer commitments.

Models in use

The portal may use hosted AI models and supporting automation services for narrow product tasks such as document extraction, classification, summarization, and analysis. These services receive only the context needed for the workflow they support.

Model providers and model configurations can change as reliability, security, cost, and product requirements change. When a model or AI subprocess change materially affects customer data handling, Last Mile treats that change through the same operational review path used for other subprocessors and platform dependencies.

Where customer data lives

Portal account, supplier, invoice, benchmark, workflow, and application data lives in Last Mile controlled systems backed by Supabase. Customer-uploaded or generated files may live in Cloudflare R2 object storage.

Last Mile does not use customer portal data to train public foundation models. Customer data is used to operate the portal, provide requested workflows, improve product reliability, and support the customer relationship under Last Mile's applicable terms and privacy commitments.

Platform boundaries

The portal boundary includes Last Mile operated application surfaces, database-backed workflows, object storage, email workflows, analytics, monitoring, and administrative tooling used to provide the service.

Some workflows cross into approved provider systems when needed for hosting, storage, authentication, analytics, email delivery, security, AI processing, or operational support. Customer-controlled source systems and third-party vendor systems remain outside the portal boundary unless a customer authorizes an integration or provides data from those systems.

Subprocessors: what, when, and why

Subprocessors are vendors that process customer data so Last Mile can host, secure, operate, analyze, support, or improve the portal. The canonical customer-facing list remains the Sub-processors page.

Last Mile shares data with subprocessors when the sharing is needed for a product workflow or operational function. Examples include hosting application infrastructure, storing customer files, sending transactional email, measuring product reliability, and supporting AI-assisted document or workflow analysis.

Notification posture

Last Mile maintains a public Sub-processors page and an internal review process for material vendor, infrastructure, and model changes. When a change materially affects customer data handling or customer-facing commitments, Last Mile evaluates the notice path before the change is treated as production-ready.

Customers can use the Transparency Disclosure, Privacy Policy, Terms, and Sub-processors page together to understand how the portal uses automation, where data is processed, and which provider categories support the service.