Privacy Policy

Leborix website is owned by Leborix Innovations, which is a data controller of your personal data.

We have adopted this Privacy Policy, which determines how we are processing the information collected by Leborix , which also provides the reasons why we must collect certain personal data about you. Therefore, you must read this Privacy Policy before using Leborix website.

We take care of your personal data and undertake to guarantee its confidentiality and security.

Personal information we collect:

When you visit the Leborix , we automatically collect certain information about your device, including information about your web browser, IP address, time zone, and some of the installed cookies on your device. Additionally, as you browse the Site, we collect information about the individual web pages or products you view, what websites or search terms referred you to the Site, and how you interact with the Site. We refer to this automatically-collected information as "Device Information." Moreover, we might collect the personal data you provide to us (including but not limited to Name, Surname, Address, payment information, etc.) during registration to be able to fulfill the agreement.

Why do we process your data?

Our top priority is customer data security, and, as such, we may process only minimal user data, only as much as it is absolutely necessary to maintain the website. Information collected automatically is used only to identify potential cases of abuse and establish statistical information regarding website usage. This statistical information is not otherwise aggregated in such a way that it would identify any particular user of the system.

You can visit the website without telling us who you are or revealing any information, by which someone could identify you as a specific, identifiable individual. If, however, you wish to use some of the website's features, or you wish to receive our newsletter or provide other details by filling a form, you may provide personal data to us, such as your email, first name, last name, city of residence, organization, telephone number. You can choose not to provide us with your personal data, but then you may not be able to take advantage of some of the website's features. For example, you won't be able to receive our Newsletter or contact us directly from the website. Users who are uncertain about what information is mandatory are welcome to contact us via IT-Team@leborix.com.

Your rights:

If you are a European resident, you have the following rights related to your personal data:

* The right to be informed.

* The right of access.

* The right to rectification.

* The right to erasure.

* The right to restrict processing.

* The right to data portability.

* The right to object.

* Rights in relation to automated decision-making and profiling.

If you would like to exercise this right, please contact us through the contact information below.

Additionally, if you are a European resident, we note that we are processing your information in order to fulfill contracts we might have with you (for example, if you make an order through the Site), or otherwise to pursue our legitimate business interests listed above. Additionally, please note that your information might be transferred outside of Europe, including Canada and the United States.

Links to other websites:

Our website may contain links to other websites that are not owned or controlled by us. Please be aware that we are not responsible for such other websites or third parties' privacy practices. We encourage you to be aware when you leave our website and read the privacy statements of each website that may collect personal information.

Information security:

We secure information you provide on computer servers in a controlled, secure environment, protected from unauthorized access, use, or disclosure. We keep reasonable administrative, technical, and physical safeguards to protect against unauthorized access, use, modification, and personal data disclosure in its control and custody. However, no data transmission over the Internet or wireless network can be guaranteed.

Legal disclosure:

We will disclose any information we collect, use or receive if required or permitted by law, such as to comply with a subpoena or similar legal process, and when we believe in good faith that disclosure is necessary to protect our rights, protect your safety or the safety of others, investigate fraud, or respond to a government request.

Contact information:

If you would like to contact us to understand more about this Policy or wish to contact us concerning any matter relating to individual rights and your Personal Information, you may send an email to IT-Team@leborix.com.

FieldOps Privacy Policy

Effective date: November 15, 2026

This section explains how FieldOps, provided by Leborix Innovations LLC, handles personal information. It covers the FieldOps mobile app and supporting service. The website privacy policy above continues to cover use of the Leborix website.

1. FieldOps and your organization

FieldOps is workplace software for employees of organizations that use the service. There is no public sign-up. Your organization creates your account and decides how its employees use FieldOps.

Leborix provides the service and processes workplace information on your organization's behalf. Your organization controls documents filed in its Microsoft 365, including access and retention.

2. Information FieldOps collects

Account information: your name, employee ID, username, organization, team, manager and role. For Microsoft sign-in, this also includes your work email address and Microsoft account and directory identifiers.

Microsoft passwords are entered on Microsoft's sign-in page; FieldOps does not receive them. Passwords for local employee accounts are stored as one-way hashes, not readable passwords.

Work submissions:

* Tickets: the photos or PDFs you attach, and the ticket's vehicle or trailer number, net tons, date and time, which the app reads from the photo and you check before sending (section 3). Tickets sent from earlier versions of the app may instead hold a load number, weights, plant and work date, or the files alone.

* Vehicle inspections: whether the inspection is pre-trip or post-trip, the unit and trailer numbers, the checklist (each item marked in order or not, with your comment on any item that is not), the photos you take, and your signature.

* Driver Log Sheets: the week, the unit number and, for each load, its date, plant name, load number, ticket or BOL number, miles and tons; your signature; and any photos you add. Sheets sent from earlier versions of the app are load-sheet photos.

* Fuel receipts: their details and the photo or PDF of the receipt.

Signatures: you sign vehicle inspections and Driver Log Sheets with your finger on the screen. The signature is kept as the lines you drew, stored with the form, and drawn on the PDF of that form filed in your organization's Microsoft 365.

Time-off information: requested dates, working-day counts, reason categories, optional notes, and managers' decisions and responses. A reason such as "Sick leave" can reveal health information.

Account-management activity: changes administrators and managers make to employees, roles and teams.

Device and technical information: sign-in activity, IP addresses, device information recorded in user-agent strings, and server diagnostics. When a device registers for notifications, FieldOps also stores its notification token, platform, app version and operating-system version.

Support information: information you provide when contacting us and our replies.

3. Photos, ticket reading and location metadata

FieldOps accesses the camera or photo library when you choose to take or attach a photo. It uploads the files you select.

Reading tickets on your phone: when you photograph a ticket, the app reads the vehicle or trailer number, net tons, date and time from the photo, so you only have to check them. The reading happens on your phone: the photo is not sent anywhere to be read, and the photo and the ticket's details leave your phone only when you send the ticket.

* On iPhone, the reading is done by the text recognition built into iOS.

* On Android, it is done by Google's ML Kit, which is included in the app. ML Kit sends Google technical information about its use, which Google says it uses for diagnostics and usage analytics: for example the phone's model and Android version, the app's name and version, how long a reading took, the photo's format and resolution, and an identifier for that installation of the app. Google lists no photo or text among the information ML Kit collects.

Photos may contain metadata recorded by your phone or camera, including when and where they were taken. FieldOps does not strip this metadata or use it to track your location. It can remain in the photo filed in your organization's Microsoft 365.

Turning off camera location tagging before taking a photo can prevent location information being added to future photos. It does not remove location information already present in an existing photo.

FieldOps does not request location-service access, access your contacts or microphone, or use an advertising identifier.

4. How information is used

We use information to:

* authenticate users and protect accounts;

* read ticket details from photos on your phone, for you to check before sending;

* process submissions and file documents in your organization's Microsoft 365;

* display submission history and filing status;

* send time-off requests to managers and return their decisions;

* manage employees, teams and roles;

* operate, troubleshoot and secure the service;

* maintain audit and deletion records;

* respond to support and privacy requests.

Push notifications are currently disabled. Notification delivery, when enabled, also depends on your permission and device registration.

FieldOps contains no advertising and no analytics tools of its own. On Android, Google's ML Kit reports technical information about its own use to Google, as described in section 3. We do not sell personal information or use it for advertising or cross-app tracking.

5. Storage and access

FieldOps account records, submission details and audit information are stored in Microsoft Azure's West US region in the United States. Uploaded files pass through temporary Azure storage before filing.

Documents are filed in your organization's own Microsoft 365 SharePoint. Your organization determines who can access those documents.

Information is accessible to authorized people according to their role:

* managers can review employees' time-off requests;

* administrators manage accounts and can view audit records;

* people authorized by your organization can access its SharePoint documents;

* authorized Leborix personnel can access information when needed to operate, support or secure the service.

Microsoft Entra ID handles Microsoft authentication. When notifications are enabled, Google Firebase Cloud Messaging and Apple Push Notification service process notification tokens and notification content. Email notifications, where enabled, use your organization's Microsoft 365. On Android, Google ML Kit receives the technical information described in section 3, never the photo or the text it reads.

We may disclose information when required by law.

6. Retention

Accounts and submissions: FieldOps retains these while the account exists. Account deletion removes the account's details and submitted records from the active FieldOps service, normally within minutes, subject to the exceptions below.

Organization offboarding: handling of records when an organization stops using FieldOps is determined by our agreement with that organization. Documents already filed in its Microsoft 365 remain under its control.

SharePoint documents: your organization retains and deletes these under its own policies. FieldOps account deletion does not delete them.

Security audit records: these currently have no fixed retention period. The FieldOps service cannot change or delete audit entries, including during account deletion. Entries may contain names, usernames, work email addresses, employee identifiers, IP addresses, device information, action times and record details. Those details can include time-off dates and reason categories, including sick leave, managers' responses, and receipt amounts and vendors.

Deletion ledger: separate records retain organization and account identifiers, whether deletion was initiated by the user or an operator, and request and completion timestamps. These support deletion tracking and recovery procedures. They do not contain names, email addresses, passwords, photos or submitted document contents. They currently have no fixed retention period.

Recovery and diagnostic copies:

* Routine database backups are retained for 7 days.

* Deleted files in temporary storage may remain recoverable for up to 14 days.

* Server logs are retained for 30 days.

* Application performance data is retained for up to 90 days.

Deleting an account does not immediately erase these recovery and diagnostic copies.

Support correspondence: support requests and our replies remain in our support mailbox and currently have no fixed retention period.

On your device: sign-in information remains until sign-out or removal. Unsent submissions remain until uploaded or discarded. To save typing, the app also remembers, for you on that device, the vehicle or trailer number of your last ticket, the unit and trailer numbers of your last inspection, and the miles you entered for each plant on your log sheets. Another person signing in on the same device does not see them, and they are removed when you delete your account or remove the app.

7. Delete your FieldOps account and data

In the app

Open Profile → Delete account.

The screen explains what will be removed and retained, and shows items that have not yet been filed. You confirm by typing DELETE and re-entering your employee password or signing in to Microsoft again.

Deletion:

* ends access to FieldOps across your devices;

* removes your account details, submitted tickets, receipts, vehicle inspections, Driver Log Sheets (including their signatures), photo sets and time-off requests from the FieldOps service;

* removes associated notifications and device registrations;

* discards your unfiled submissions, your queued work, and the numbers and miles the app remembered for you, on the device where you delete the account.

An empty "Deleted user" placeholder remains so other people's records can still reference actions you previously took. Your records cannot be restored by signing in again.

Filed SharePoint documents (including inspection and log-sheet PDFs that show your signature), audit entries, deletion-ledger records and the recovery copies described above are retained.

Queued work on other devices may remain locally but can no longer be uploaded under the deleted account. Before deleting, upload or discard any waiting work on those devices.

Deleting FieldOps access does not delete your employer's Microsoft account. Managers' team members retain their accounts; your organization must assign a replacement manager where necessary.

Request deletion without the app

Email support@leborix.com with:

* your organization's name;

* your FieldOps username or work email address;

* a statement that you want your FieldOps account and associated data deleted.

Never send your password. We may need information to verify your identity and locate the correct account.

We complete verified deletion requests within 30 days of receiving your request. The retained records and employer-controlled documents described above are not removed by FieldOps account deletion.

For deletion of documents in your employer's Microsoft 365, contact your employer's administrator.

8. Security and your choices

Connections between the app and FieldOps service use HTTPS. Employee passwords are hashed, sign-in sessions use device secure storage, and access is restricted by organization and role.

No system can guarantee absolute security. Report suspected account misuse to your organization's administrator or support@leborix.com.

Camera, photo-library and notification permissions can be changed in your phone's settings. Declining notifications does not prevent use of the app.

Depending on applicable law, you may have rights to access, correct or delete information, or restrict or object to its processing. Contact your organization's administrator or support@leborix.com. We work with your organization to respond within 30 days and explain any information that must be retained.

9. Children and policy changes

FieldOps is workplace software intended for adults, not children. If you believe a child is using the service, contact support@leborix.com.

Updates to this policy will be published on this page with a revised effective date.

10. Contact

Leborix Innovations LLC

FieldOps support and privacy requests: support@leborix.com

Website privacy questions: IT-Team@leborix.com

Services

© 2026 Leborix Innovations. All rights reserved.