Collection
Enquiry forms collect contact details, the selected service, source page and the business problem you choose to describe.
Data handling
How PowerFlux approaches data and AI risk
AI systems should be designed around the sensitivity of the data and the impact of the action. We document the flow before production and keep people responsible for high-impact judgment.
Last updated 5 September 2026Website
Current website data flow
Storage
Enquiries are stored in the managed PowerFlux lead database. The public website does not expose the lead dashboard.
Access
Lead management requires authenticated administrative access. Access is intended for people handling PowerFlux enquiries.
Analytics
Google Analytics records website usage and conversion events so we can understand page and campaign performance.
Principles
Project data-handling principles
Classify before connecting
Identify personal, confidential, regulated and sensitive information before selecting models or integrations.
Minimise the data
Use only the fields and context required for the workflow. Avoid copying full datasets when a smaller input is sufficient.
Choose providers by risk
Assess model, hosting and integration providers against the project’s privacy, retention, access and reliability needs.
Keep humans in control
Define approval, escalation and exception paths for financial, customer, legal, safety or brand-sensitive actions.
Separate test and production
Use suitable test data, credentials and environments. Production access should be limited to the people and systems that need it.
Plan for failure
Document fallback, logging, error handling and a safe manual path where a workflow is business-critical.
Scope
What this page does and does not claim
- PowerFlux does not claim a security certification that has not been independently obtained and published.
- Specific model providers, data locations, retention periods, service levels and subprocessors depend on the agreed solution and should be documented before production.
- High-risk, regulated or sensitive-data use cases require a separate assessment and may be declined or referred for specialist advice.
This page describes our current practices in plain language. Specific client projects may have additional contractual data-handling terms.
Questions or requests
Need a project-specific data flow?
Tell us the workflow, systems and data categories involved. We can identify the questions that should be resolved before a pilot.