Privacy

This privacy page describes the limited data posture of this static procurement software for purchase order management support site. The pages are published as static HTML, CSS, and image files, with no user accounts, checkout, comments, newsletter signup, or embedded lead form.

The site itself is not designed to collect names, email addresses, phone numbers, company files, software exports, passwords, API keys, billing details, or internal business records. Visitors should avoid sending sensitive information through public browser interactions.

Basic hosting or CDN logs may be created by the infrastructure provider that serves the files. Those technical logs can include IP address, user agent, requested URL, timestamp, referrer, or error status for delivery, security, debugging, and abuse prevention.

The pages link to third-party websites, including the main LeStallion article and possibly software vendors. Once a visitor follows an external link, that third party controls its own cookies, analytics, forms, advertising tags, trials, and privacy practices.

This Privacy page is intentionally different from About and Contact. It explains what this static site does and does not collect, while About covers editorial purpose and Contact covers correction scope.

If this static site is updated later, the privacy goal should remain simple: explain the limits of collection here, avoid overstating control over third-party platforms, and keep readers aware when they leave the support resource.

The page also keeps a practical boundary for readers: private company records, credentials, exports, billing details, employee information, customer files, and supplier documents should remain inside secure internal systems or vendor support channels, not in a public static resource. That boundary is part of the editorial quality check for this cluster.

This Privacy page is reviewed as its own page, not copied boilerplate. For procurement software for purchase order management, the page text must match its role: editorial scope for About, communication limits for Contact, and data handling for Privacy.

For added clarity, each trust page avoids pretending that this mini-site has account access, private support tools, testing labs, direct vendor relationships, secure intake systems, live chat, or private implementation files, correction logs, or unpublished vendor terms. Its role is to make the surrounding buying content easier to interpret and safer to use during early research.

The content is intentionally plain-language because comparison pages are most useful when teams can turn them into real questions for demos, stakeholder review, procurement notes, security checks, and rollout planning without mistaking them for a private support desk or a formal compliance opinion.