FLY BOX FLY LLC / AXLE
Privacy Policy
Effective date: October 30, 2026.
1. Scope and availability
Fly Box Fly LLC operates Axle. This policy covers the Axle product website and Founding Carrier Beta inquiries, and explains the separate synthetic hackathon demonstration. A native Muse connector is proposed; approval, compatibility, and availability have not been verified. It is not currently offered through this website.
2. Website information
The application requires your name, company name, email, phone, equipment types, and freight sources. You may also provide requested help and operational responsibilities. We store these details with a creation timestamp, request identifier, submission fingerprint, and notice version. Do not include passwords, financial account numbers, sensitive documents, or confidential freight information in the inquiry form.
3. How we use application details
We use application details to evaluate beta participation, contact you about next steps, and understand the carrier capabilities applicants request. Applying does not connect carrier accounts or authorize access to financial information, operating records, or freight platforms. Any future access or actions require separate authorization and applicable beta terms.
4. Storage, providers, and access
Application records are held in PostgreSQL on our Hostinger VPS, with daily database backups kept locally on the VPS and in Cloudflare R2, plus separate weekly Hostinger VPS backups. The owner of Fly Box Fly LLC is the sole applicant reviewer. We do not maintain separate applicant exports or copies outside this database and its backups. Hosting and backup providers process information as part of operating those services. Contacting us by email also involves email delivery and storage services.
5. Technical information and security
The application uses validation, same-origin checks, restricted database permissions, and a rate limiter. The limiter stores a keyed hash of the email address and a global counter rather than raw email addresses or IP addresses. Application storage errors are logged using generic messages without submitted details. Hosting, proxies, and other infrastructure may process IP addresses, request details, timestamps, and access or security logs. Application-level non-storage does not mean zero infrastructure logging. No security measure guarantees absolute protection.
6. Cookies and browser events
The website application does not set cookies or persist application details in browser storage. Form details remain in page memory while the page is open. It emits local conversion events containing event names, without applicant details; we do not currently use an external analytics service on the Axle website. This description does not establish that infrastructure or services outside the application never use cookies or technical identifiers.
7. Retention and deletion
We manually review applicant records six months after submission or the last substantive beta contact and delete records no longer needed. An active beta relationship may justify continued retention. This is a review checkpoint, not automatic deletion at six months. Expired rate-limit buckets are removed during subsequent new submissions. Coolify is configured to retain local database backups for seven days (also limited to seven backups and 5 GB) and remote database backups for 30 days. These are configured retention settings, not a guarantee of deletion at an exact time. The R2 bucket has no separate expiration rule for completed backup objects. Hostinger also creates weekly VPS backups, with older restore points replaced automatically; an exact maximum retention period has not been established here. Deleting an active record does not immediately erase backup copies. Backup copies may remain until they expire or are replaced. Infrastructure logs and service-provider records can follow separate retention practices.
8. Separate synthetic evaluation demonstration
The protected local demo is for synthetic data only. It processes screenshot pixels, extracted freight facts, confirmed carrier requirements, and evaluation results. Images are normalized and embedded metadata is removed before pixels are sent to Meta for interpretation; visible information in pixels is not removed by that step. Application code does not save uploaded screenshots or shared conversation history. The separately deployed deterministic evaluation API performs no model calls or application-level storage. These statements do not establish zero retention by Meta, hosting, proxies, or logs. The planned local-to-remote browser adapter has not been live-verified. Do not submit real personal, customer, or confidential freight information to the demo.
9. Proposed connector
The proposed Muse connector is not an approved or available integration. Its final data flows, permissions, providers, security controls, and deletion behavior must be verified and documented before release. This policy does not authorize new account access or describe proposed functionality as live. Meta processes synthetic screenshots in the separate local demo; website beta applications are not sent to Meta by the intake application.
10. Requests and changes
For access, correction, or deletion requests, or privacy questions, email contact@flyboxfly.com. Identify the application using the email you submitted; do not send passwords or sensitive documents. We may request proportionate information to verify the request and will explain any retention limitations. Requests sent by email create correspondence separate from the original application. We may update this policy as practices change, show the updated date here, and provide additional notice or obtain permission where required. Contact us if you need clarification before submitting information.
Contact: contact@flyboxfly.com