Parts Ticket Analytics

1Overview

Parts Ticket Analytics is an operational analytics tool for parts departments. It helps an organization review parts-pulling activity — how many tickets were completed, how long they took, when the workload peaked, and which records may be worth a second look.

The application is an early-stage pilot in use at a small number of organizations. This policy describes how it actually handles information today, not how a larger product might handle it later.

2Uploaded reports

When you choose a report file, the application reads it directly in your web browser. The file stays on your computer.

Report contents are not sent to us, not received by us, and not stored by us. There is no server that accepts report uploads — there is nothing for a report to be uploaded to. All of the analysis you see is calculated on your own machine, inside the browser tab.

This is a consequence of how the application is built rather than a promise about how we behave. The application makes no outbound network requests while you use it.

3Information contained in reports

Reports come from your own systems and may contain:

• Employee names
• Ticket or repair-order identifiers
• Work activity information
• Completion and elapsed times
• Dates and timestamps
• Any other operational fields your organization includes in its export

Because reports can identify individual employees and describe their work performance, the organization using this application is responsible for determining that it has the authority and permission to analyze that information, and for following its own internal policies and any applicable workplace agreements. We never see these reports, so we are not in a position to make that determination for you.

4How report data is used

Report information is used on your device to calculate and display the analytics you asked for: totals and averages, per-employee summaries, the activity timeline, and the Needs Review checks.

We do not use uploaded report contents for:

• Advertising
• Selling data
• Profiling
• AI or machine-learning training
• Marketing
• Analytics unrelated to displaying your own results

None of these are possible, because report contents never reach us.

5Storage and retention

Report contents are not retained on our servers.

While you are using the application, the report exists in your browser's working memory so the charts and tables can be drawn. The application does not write report data to browser storage — it uses no cookies, no localStorage, no sessionStorage and no IndexedDB — and it does not save anything to disk unless you choose an Export option, which writes a file to your own computer.

When you reload or close the page, the application stops holding the data and it is not restored. We cannot promise that every trace is immediately erased from your device; browsers and operating systems manage memory and caches on their own. What we can say is that the application itself neither keeps it nor transmits it.

6Account and website information

This is separate from your report contents, and it is deliberately minimal.

The application currently has no user accounts, no sign-in and no authentication. It does not ask for your name, email address or any other personal detail, and it sets no cookies of its own.

If you are using a hosted copy, the web host that delivers the page may keep ordinary server request logs — typically IP address, date and time, and browser type — as web servers generally do. Those logs concern the request for the page itself. They do not contain your report contents, because report contents are never sent over the network.

7Third-party services

The application does not load or send data to any third-party service. There is no analytics provider, no error-reporting or crash-logging service, no advertising network, no external font or script host, and no AI service embedded in it.

The only third party involved is whoever hosts or delivers the page to you — your web host or your organization's own network. They handle the request for the application file, not your report data.

8Data sales

We do not sell uploaded report contents. We do not receive them, so there is nothing for us to sell.

9Security

The most meaningful protection here is structural. Because report contents are never transmitted to or stored on a server, there is no central copy of your operational or employee data for us to lose. That removes a category of risk rather than managing it.

The remaining risk sits with you. The report file lives on your computer, and anyone with access to that computer, that browser session, or a file you export can read it. We cannot guarantee the security of your device or network, and no system can be guaranteed to be completely secure.

10Changes to this policy

The application is in active development. If its data handling changes — for example if accounts, saved reports, or server-side processing are added — this policy will be updated to describe what actually happens, and the "Last updated" date will change. Where practical, material changes to how report data is handled will be noted here before they take effect.

Last updated: August 11, 2026

11Contact

Privacy questions: mawesupport@gmail.com