TAMS Trust Center

Review the website safeguards, public technical evidence, data-handling boundaries, and direct contact channels that are available before you submit a request.

Reviewed:

Website and form safeguards

These statements describe controls implemented in the public website. They are not a certification of a customer deployment.

Encrypted public access

Public deployments redirect to HTTPS and send HSTS, frame, MIME-sniffing, referrer, and browser-permission protections.

Protected submissions

Forms use antiforgery validation, a server-owned request context, reCAPTCHA verification, required-field validation, and field-length limits.

Controlled proof

Customer proof is not rendered unless an approval record, approval date, and required source details pass startup validation.

Consent-gated analytics

Google Analytics loads only after explicit acceptance. Advertising storage, User-ID, Google Signals, remarketing, form contents, and site-search terms are excluded.

Evidence you can inspect directly

These links provide public, first-hand evidence without implying customer endorsement.

MTConnect adapter catalog

Inspect published machine, controller, and data-source coverage for Model-Aware® adapters.
Filter supported equipment

Online MTConnect Validator

Use the public validator workflow to inspect MTConnect documents and generated findings.
Open the online validator

Technical guides and reports

Review public implementation, adapter-selection, validation, glossary, and workbook resources.
Browse technical resources

Public engineering profile

Visit the public TAMS organization profile and repositories directly on GitHub.
View TAMS on GitHub

Security is scoped to the deployment

TAMS products can be discussed for cloud, on-premises, segmented, or offline environments where the selected product supports that delivery model. A website statement cannot replace a review of the actual architecture.

TAMS engineering services can help customers design and review these IT/OT landscapes, including machine-to-Agent and downstream data flows, network boundaries, service identities, retention, and operational ownership. That experience does not create a DoD authorization or independent certification.

A deployment review should identify:

  • network boundaries and permitted inbound or outbound connections;
  • machine, controller, agent, and downstream data flows;
  • identity, access, service-account, and least-privilege requirements;
  • update, backup, logging, monitoring, and incident-response ownership; and
  • customer-specific regulatory, contractual, export-control, and retention requirements.

No security certification, audit report, uptime guarantee, or response-time commitment is implied by this page. Ask TAMS to review the requirements for the specific product and environment.

Website data handling

The website collects business contact and project details only when you choose to submit them. The application does not provide payment checkout. Essential form-security technology, Google reCAPTCHA, and the deployment’s analytics status are described in the Privacy Policy.

Optional Analytics is limited to page use, approved CTA and download interactions, and successful inquiry categories. The tag sends no data before acceptance, and a footer control lets visitors change their choice. TAMS does not use this property for advertising, identity resolution, customer-list uploads, or form-field analysis.

Do not send passwords, payment-card data, health information, export-controlled information, trade secrets, or other sensitive material through a website form.

Contact and reporting

For a website privacy or security question, technical support request, or sales inquiry, call +1 (317) 907-8897 or email sales@tams.ai. Include the affected page or product and enough non-sensitive detail to route the request.

For other inquiry types, use the TAMS contact page.

Protected Website Forms

HTTPS, antiforgery validation, input limits, and reCAPTCHA protect public form submissions. Review the safeguards.