Security

Security and data handling at TailyX

TailyX handles website enquiry and qualification data for service businesses. This page explains the public, buyer-facing security posture that is supported by the current product.

What data TailyX handles

TailyX collects information submitted through configured website qualification flows, including contact details, qualification answers, lead scores, widget settings, follow-up status and recorded commercial outcomes where a customer chooses to record them.

Account access

Customer areas require sign-in. Protected self-service signup uses email confirmation before meaningful product activation, while existing invited, paid and beta-code account paths remain supported.

Tenant separation

Product records such as users, leads, widgets, subscriptions and qualification surfaces are associated with a Company record. Customer-facing controllers use the signed-in user's company when reading and writing product data.

AI-assisted qualification

TailyX uses structured questions, scoring rules and AI-assisted interpretation where enabled. Qualification evidence remains visible to the customer rather than being treated as an unexplained final decision.

Human control

TailyX helps customers qualify, prioritise and review website enquiries. It does not automatically approve recommendations, change a customer's website, launch experiments or record commercial outcomes without a human action in the product.

Due-diligence boundaries

TailyX does not currently publish SOC 2, ISO 27001, residency, penetration-testing, backup, retention-period or encryption-at-rest claims on this page. Buyers who need those details should ask TailyX directly before relying on them in a procurement process.

Policies and questions

Review the Privacy Policy and Terms of Service. For security, privacy or data-handling questions, use the contact page.