Overview
This privacy page explains the public-site privacy posture for Preflix AI and the protected boundaries for app workflows.
Public pages are designed for product education, contact routing, and content discovery. They should not request or store protected health information, medical account numbers, insurance member IDs, or uploaded bills.
Information We Collect
On the public site, Preflix AI may collect basic non-sensitive contact information when a visitor chooses to send an inquiry, such as name, work email, organization, role, and a short message. The contact page warns users not to enter protected health information.
In a secure app, bill review may require documents such as itemized bills, EOBs, insurance details, and dispute correspondence. Those workflows should use stronger controls, audit logs, role-based access, and retention rules appropriate for sensitive health-related information.
How Information Is Used
Public contact details may be used to respond to inquiries, route support requests, schedule demos, improve content, and maintain the security of the website. Sensitive documents should only be used to provide the requested bill review, dispute preparation, account support, and legally required operations.
Preflix AI should not sell protected health information. Any third-party service used for sensitive workflows should be reviewed for privacy, security, and contractual fit.
Retention And Deletion
Marketing inquiries should be retained only as long as needed for business follow-up and recordkeeping. Protected app data should follow a defined retention schedule based on user plan, legal requirements, and documented deletion requests.
Users should have clear channels to request deletion or export. Some information may need to be retained for security, legal, billing, or audit reasons, but those exceptions should be narrow and explained.
Your Choices
Visitors can avoid sharing personal information on public pages and can contact Preflix AI through the routing options on the contact page. Users of any secure app should receive account-level privacy controls and support pathways.
Privacy questions should be routed to the privacy contact listed on the contact page, with a reminder not to send medical documents through public email unless a secure channel has been provided.