PRIVACY POLICY FREIGHT FLOW Last updated: October 14, 2026 App: Freight Flow Android application ID: com.emetsystems.freightflow Publisher: EMET SYSTEMS INC Privacy contact: info@emetsystems.com Developer Support: ansxxi@gmail.com This Privacy Policy applies to the Freight Flow Android mobile application. It describes how information is accessed, processed, stored, shared, retained, and deleted when the app is used. The statements below describe the current local-first app and should be reviewed if future features change its data practices. 1. WHO IS RESPONSIBLE FOR THE APP Legal entity and publisher: EMET SYSTEMS INC Application: Freight Flow Privacy contact: info@emetsystems.com Privacy questions and requests concerning information voluntarily sent to the publisher may be directed to the address above. The publisher generally cannot access or delete information stored only on a user's device. 2. PURPOSE OF THE APP Freight Flow helps carriers, drivers, dispatchers, and other freight-transportation professionals create and manage shipment orders, record pickup and delivery appointments, attach and scan freight documents, use optical character recognition (OCR) to assist form entry, collect pickup and delivery signatures, record shipment status, and create, view, and share shipment and invoice PDFs. The current app is primarily local and does not require an EMET SYSTEMS INC cloud account for normal use. The publisher does not operate a cloud shipment database that automatically receives routine records entered in the app. 3. INFORMATION ENTERED BY USERS Users may enter or store: - Company name, business address, phone, email, USDOT and MC numbers; - Driver names and phone numbers, truck and trailer numbers, equipment and seal information; - Shipper, consignee, receiver, customer, broker, billing and other contacts; - Pickup and delivery addresses, appointment numbers, dates, times, windows and instructions; - Load, BOL, PO, PRO, shipper, shipping, account, order and other reference numbers; - Commodity, freight descriptions, quantities, weights, dimensions and additional stops; - Shipment status, notes, expenses, linehaul, fuel and other charges; - Invoice numbers, billed customers, amounts and paid or unpaid status; - Names and drawn signatures of people signing pickup or delivery records; and - Any other content users choose to add through document imports or free-text fields. The app uses this information to provide shipment, document, signature, PDF, invoice, and backup functions. 4. CAMERA, PHOTOS AND DOCUMENT IMPORTS When the user chooses to scan paperwork, the app may access the camera to capture a document image. Users can also select supported PDF, image, or text files through Android's file picker. Access is limited to the selected documents and the permissions or selection mechanisms made available by Android. Documents may contain personal information, commercial terms, addresses, signatures, phone numbers or confidential shipment details. Imported and scanned documents are saved locally for use with associated shipment records. The app does not automatically upload these documents to an EMET SYSTEMS INC server. 5. OPTICAL CHARACTER RECOGNITION (OCR) Freight Flow uses on-device Google ML Kit text-recognition components to recognize printed text in scanned images and PDF pages. The app may suggest shipping names, contact details, addresses, appointment data, shipment references and other form values from OCR output. OCR results can be incomplete or inaccurate. Users should review and correct recognized information before storing, exporting, or relying on it. Routine OCR processing is designed to occur on the device; the publisher does not automatically receive recognized shipment text. Applicable Google and Android platform handling is subject to those providers' policies. 6. ATTACHMENTS AND DOCUMENT VIEWERS Shipment attachments may include bills of lading, rate confirmations, appointment sheets, pickup or delivery paperwork, photographs, receipts, and other supported documents. They may be viewed inside the app and shared only when the user selects a sharing action. Attachments may remain in local storage or in copies saved to other destinations chosen by the user. External recipients and applications may retain copies beyond the app's control. 7. OPTIONAL LOCATION INFORMATION The app has an optional setting for recording location information with signatures or shipment-completion evidence. When enabled, and when the appropriate Android permission has been granted, the app may read the device's available location, including a last-known location, and save coordinates in the relevant record. Last-known coordinates may be older than the signing or completion event and do not guarantee the person's precise location at that moment. Location records may be displayed in generated PDFs. Location access can be disabled in the app or revoked in Android settings. Freight Flow is not designed to continuously track background location or automatically transmit location history to the publisher. 8. DATE, TIME AND EVENT STAMPS The app may use the device's date and time to record signatures, pickup, transit and delivery events, and document generation. Users may choose whether a PDF-generation timestamp is included on exported documents. That display setting does not necessarily erase event or signature timestamps saved in a shipment record. Users are responsible for verifying appointment times, manually entered dates, and device clock accuracy before relying on records as evidence. 9. SIGNATURES The app allows a driver, sender, consignee, customer, or other authorized person to draw a pickup or delivery signature on the device. When saved, signature information may include the drawn image, signer name if supplied, timestamp, and optional available location information. Signatures are stored locally as part of the shipment record and may appear in shipment PDFs. They are disclosed outside the app if a user intentionally exports or shares the relevant content. The publisher does not automatically collect signed shipment documents. Users must obtain any required consent or authority to capture other people's signatures. Freight Flow does not independently verify signer identity. 10. BILLING AND INVOICES Freight Flow stores user-entered freight charges, invoice numbers, customer and broker information, amount due, and paid or unpaid bookkeeping status. The saved Company Profile may be used as sender information on invoices. Freight Flow is not a bank, money transmitter, or payment processor. Routine invoice functions do not require full payment-card numbers, card security codes, or online banking login details. Users are responsible for verifying billing information and meeting accounting, tax, and payment obligations. 11. GENERATED PDFs AND SHARING The app generates shipment and invoice PDFs from saved information. A PDF may contain company profiles, addresses, contact details, commodity descriptions, business references, rates, timestamps, optional location data and drawn signatures. When users select View, Share, Save, Email, Print or another available option, Android or a compatible application may receive the document. The user controls the intended recipient and destination. Once transferred, the receiving service's privacy policy and retention practices apply. Users should verify recipients before sending confidential records. 12. LOCAL STORAGE Freight Flow may locally store shipment orders, company profile settings, invoices, scanned or attached files, OCR text, signature images, generated PDFs, timestamps, optional location evidence, saved preferences and temporary preview files. Routine operational records are not automatically synchronized to a publisher-operated cloud database. The operating system, local device security, user-selected external storage, and backups may affect the availability and security of stored information. 13. BACKUP AND RESTORE Users may export and restore supported app data, including shipment and invoice information, using Android document controls. The current JSON backup may include references to local document files and should not be assumed to contain the binary content of every PDF, attachment or signature image. Users choose where to save a backup and are responsible for securing it, verifying what it includes, and protecting documents stored separately. A selected cloud-storage provider or synchronized folder operates under its own terms and privacy policies. EMET SYSTEMS INC does not automatically receive the backup file. 14. PERMISSIONS AND DEVICE ACCESS Depending on the Android version and selected functions, Freight Flow may request or use: CAMERA: Capture shipping paperwork for attachment or OCR. FILES/DOCUMENT PICKER: Import supported PDFs, text files and images, save or open documents, and export or restore backups. LOCATION: Optional location evidence when enabled and permission is granted. INTERNET OR PLATFORM SERVICES: Operating-system or third-party functions when applicable, such as opening external links or services chosen by the user. Users can manage permissions in device settings. Some features may not work when the relevant permission is denied. 15. NOTIFICATIONS The app may store an on/off notification preference. In the current version this preference alone does not mean that scheduled freight reminders or push notifications are implemented. If notification functionality or external push services are added later, the policy should be updated to describe how notification information is handled. 16. SUBSCRIPTIONS AND APP-STORE PURCHASES This policy does not describe an active Freight Flow subscription or payment-card collection feature in the current Android app. If a future version introduces Google Play subscriptions or in-app purchases, the relevant purchase, renewal, verification and privacy practices will be disclosed before release. 17. INFORMATION NOT AUTOMATICALLY SENT TO THE PUBLISHER The current app is not designed to transmit routine complete shipment databases, OCR document text, scanned paperwork, attached files, generated invoices, signature images or continuous location history to EMET SYSTEMS INC servers. It is also not designed to collect contact address books or online banking credentials for its normal shipment workflows. This does not cover information deliberately sent by users to the publisher for support, or information independently processed by Google, Android, external recipients or user-selected providers. 18. CUSTOMER SUPPORT COMMUNICATIONS If users contact EMET SYSTEMS INC, the company may receive the email address, name, message, screenshots, documents, app version, device details or other information voluntarily supplied. It may use these materials to respond, troubleshoot, resolve disputes, maintain necessary records, and comply with legal obligations. Users should remove unnecessary customer information, shipment contents, signatures, location evidence and financial records before submitting support materials. 19. DATA SHARING AND THIRD PARTIES EMET SYSTEMS INC does not sell locally stored freight, invoice or signature information for targeted advertising. Third-party processing may occur through Google/Android operating-system features, OCR software components, user-selected sharing, printing, email or cloud providers, and legally required disclosures. Third parties manage information according to their own privacy policies. The publisher cannot control files after users transmit them to recipients or external services. 20. ADVERTISING, ANALYTICS AND CLOUD SERVICES The current app is not designed to display third-party advertising or run a publisher-operated freight analytics or cloud synchronization service. Android, Google Play and other distribution platforms may independently provide installation, crash or performance information under their own policies. If future releases add advertising, analytics, crash-reporting SDKs, remote OCR, accounts, cloud synchronization, server storage or payment features, this policy and applicable app-store disclosures will be updated before the changed version is released. 21. RETENTION AND DELETION Locally stored information generally remains until deleted using available app features, Android app data is cleared, or the app is uninstalled, subject to operating-system backup and retention behavior. Exported PDFs, cloud-synced copies, backups, emails and shared documents must be deleted separately at their respective destinations. Because routine data are kept on the device rather than a publisher-operated user account, EMET SYSTEMS INC cannot generally delete those local records remotely. Support correspondence may be retained as reasonably needed for service, recordkeeping or legal obligations. 22. SECURITY Keeping routine freight records on-device limits automatic publisher-server access, but no storage or transmission method is completely secure. Users should secure devices with a passcode or biometric lock, protect local and cloud backup locations, review file-sharing destinations, and confirm that documents are sent to the intended recipients. 23. INFORMATION ABOUT OTHER PEOPLE Users may store personal information about shippers, receivers, brokers, customers, drivers, employees, signers and other contacts. Users are responsible for obtaining any permissions or lawful basis required to collect, use, share or retain this information, and for complying with applicable freight, privacy, employment, electronic-signature and records laws. 24. CHILDREN'S PRIVACY Freight Flow is intended for business users and is not directed to children. EMET SYSTEMS INC does not knowingly seek personal data from children through the app. Anyone concerned about information a child has voluntarily sent to the publisher may contact info@emetsystems.com. 25. UNITED STATES AND INTERNATIONAL USERS EMET SYSTEMS INC is a United States business. Communications sent to the publisher for support may be processed in the United States. Users operating in other regions should ensure their use of the app complies with applicable laws concerning shipment, financial, location and other personal information. 26. GOOGLE PLAY DISCLOSURES The Google Play Data safety form and app listing must accurately reflect the exact submitted release, its permissions, libraries and real data handling. This policy should be checked against the production build when any data collection, sharing, cloud, analytics, purchase or notification functions change. 27. CHANGES TO THIS PRIVACY POLICY This policy may be updated to reflect changes in app functions, permissions, practices, service providers or legal requirements. The revised version will show a new Last updated date. 28. CONTACT App: Freight Flow Application ID: com.emetsystems.freightflow Publisher: EMET SYSTEMS INC Privacy inquiries: info@emetsystems.com Developer Support: ansxxi@gmail.com