System FAQ

Operational guidance for the AeroFind Enterprise ecosystem.

1. How are bugs handled during the trial?

We employ an Agile Hotfix Workflow for all pilot partners.

Critical Bugs: Resolved within 24 hours.
UI/UX Improvements: Batched for 48-hour deployment.
Reporting: A dedicated "Pilot Feedback" channel is established for real-time reporting via encrypted channels.

2. Is live data used during the trial?

For standard trials, no. We recommend a demo-data sandbox model:

The trial should use fictional passengers, fictional bag tags, and demo-only cases unless a signed AVV/DPA and production security sign-off are in place.
Application-level AES-256-GCM field encryption is available for supported sensitive fields. Disk, database, object-storage, and backup encryption at rest must be confirmed with the selected hosting provider.

3. What happens if we decide not to continue after 30 days?

Data Export: You receive a full CSV/JSON export of all processed records and logs.
Zero Lock-in: The local station node is decommissioned with no further charges.
Knowledge Transfer: All training materials and custom documentation remain with your team.

4. Can we customize the delivery rules?

Yes. Station-specific logistics (e.g., specific courier pickup zones or terminal-specific routing) can be configured via the administrative console during the initial setup phase.

5. What are the system requirements?

AeroFind is a web-based middleware. Your team only needs:

Modern web browsers (Chrome/Edge preferred).
Stable secure network connection.
Mobile devices for floor staff (optional but recommended).