Privacy Policy
aiAdFlux is built for local, privacy-first analytics. This page explains what information is collected through the website and platform, what stays on-device, and how operational data is used under a DPDP Act 2023 and GDPR aligned privacy-first model.
Privacy Summary
At a glance
1. Information we collect
We collect information that you provide directly when you contact aiAdFlux, request a demo, create an account, or communicate with our team.
- Name, email address, company name, and similar business contact details.
- Deployment information such as number of screens, venue type, and requested integrations.
- Account activity and administrative data needed to secure and operate the platform.
2. On-device analytics
aiAdFlux is designed so audience analytics operate locally on supported edge devices. The goal is to turn live visual input into aggregate insight without using footage as a cloud data stream.
- Analytics outputs may include aggregate dwell time, counts, traffic patterns, or anonymized demographic ranges.
- The platform is not intended to create a database of identified individuals.
- Venue operators remain responsible for lawful notices, signage, and configuration in each deployment environment.
3. How information is used
Information is used to respond to inquiries, provision accounts, support pilots and live deployments, improve platform reliability, and communicate about service operations.
- We may use submitted information to tailor demo flows for airport, transit, mall, or retail deployments.
- Technical logs may be used to diagnose incidents, maintain uptime, and improve security controls.
- Theme preferences and similar local browser settings may be stored in your browser for site usability.
4. Sharing and vendors
We do not sell personal information. Information may be shared with service providers that support hosting, communications, analytics, security, or customer support under appropriate confidentiality obligations.
- We may disclose information if required by law, legal process, or to protect rights and security.
- Business transfers or restructuring events may involve transfer of relevant operational data.
- Customers should avoid uploading personal data into campaign metadata unless they have a lawful basis to do so.
5. Retention and security
Information is retained for as long as reasonably necessary to fulfill operational, legal, support, or contractual requirements. We apply administrative, technical, and organizational safeguards that are appropriate to the nature of the information.
- Access to dashboards and sensitive settings should be limited to authorized users.
- Password resets, account changes, and support events may be logged for security review.
- You can also review the platform commitments described in our Terms and Conditions.
6. Your rights and contact
Depending on your location, you may have rights to request access, correction, deletion, or limitation of certain personal information. To raise a privacy request or security concern, use the contact form on the home page.
If your deployment is in transport infrastructure, you may also want to review theairport page orbus stands page for venue-specific context.
Built for low-data workflows
The site and platform messaging are aligned around local analytics instead of sending raw video upstream.
Venue-specific planning
Airport and transit deployments often need policy review before launch. The dedicated pages help frame that setup.
Account support
If you lose access, use the recovery link on the login page or contact your workspace administrator.

