Core principle: The ReportMedic tools are designed to process the files and report data you provide locally in your browser. In ordinary use, the contents of your files stay on your device and are not transmitted to any server as a condition of using the tools.
This Privacy Policy is a legally operative notice describing how information is handled when you access and use the ReportMedic website and its browser-based tools (the Service). It is written in strong, formal language to reduce ambiguity, to establish enforceable expectations, and to emphasize confidentiality through local-only processing.
If you want a privacy-forward workflow that keeps custody of sensitive exports on your own machine, the Service is designed to support that outcome. You can compare, validate, convert, and summarize locally, then decide what to share, if anything.
This Policy applies to the Service, including tool pages, documentation pages, and all interfaces that present or execute browser-based functionality. It governs how information is handled in connection with the Service, with particular emphasis on the local-only processing design that keeps User Content within your device boundary in ordinary operation.
This Policy governs only the Service. It does not govern third-party websites, applications, or services that you may access through links. Those third parties operate under their own terms and privacy notices, and you remain responsible for reviewing them before you provide information to those third parties.
This Policy is intended to be read as a clear notice. It does not require you to create an account to benefit from local processing. It is drafted to make explicit that the Service is engineered so that you can obtain results without routinely transmitting your report files to remote storage.
For avoidance of doubt, “local-only” in this Policy refers to the ordinary operation of the tools where User Content is processed in the browser and remains on the Device. It does not prevent a User from independently sharing outputs or excerpts through external services under the User’s control.
The Service is designed so that tool computations occur in your browser on your Device. When you load User Content into a tool, the browser reads that content locally, performs the requested processing locally, and renders results locally. The Service is intended to function without requiring upload of User Content to remote processing infrastructure in ordinary tool use.
In ordinary tool operation, the Service does not transmit the contents of your files to any server. This includes the underlying bytes of your files, any extracted text, any calculated metrics, any intermediate processing artifacts, and any Derived Output produced during the session. The ordinary operating model is local-only: you load, process, review, and export on your Device.
Because User Content is not transmitted in ordinary operation, the Service does not, as a functional requirement, store your input files on remote servers for processing. This structural property materially reduces exposure associated with centralized repositories of user documents and reduces the operational need for server-side retention decisions regarding your files.
Ordinary operation includes using drop zones, file selectors, paste areas, tool buttons, previews, and download actions that are executed locally by your browser. Ordinary operation excludes any feature that is expressly presented as sending information to a remote recipient at your direction. Any such user-directed transmission is a Voluntary Submission and is addressed in this Policy.
User Content. User Content is processed locally. The Service is designed so that User Content stays on your Device during ordinary operation. The Service does not require centralized storage of User Content for the core local-processing workflow.
Derived Output. Derived Output is generated locally and displayed within your browser. If you choose to download an output file, your browser saves that file according to your browser settings and operating system configuration. Creating Derived Output does not require remote retention of User Content.
Temporary session memory. During an active session, your browser holds portions of User Content in memory to perform processing and render results. This is inherent to local execution. The Service is designed so that processing artifacts remain within the browser environment on your Device.
Local convenience state. Some tools may offer optional convenience behavior such as remembering a setting, restoring a draft, or persisting a small amount of interface state. If present, such state is stored locally under your browser profile on your Device. You are responsible for controlling Device access and deciding whether to use shared Devices for sensitive work.
A typical local processing session follows a consistent sequence. Your browser loads the tool page and executes the tool logic locally. You provide User Content by selecting a file, dragging and dropping a file, or pasting content. The tool processes that content locally on your Device and renders results within the page. If you choose to export results, your browser generates the output locally and saves it to your Device.
Under this local-only design, the tool can deliver practical troubleshooting value without requiring a file upload. This reduces exposure compared to server-centered tools that require uploads. It reduces the need for server-side storage, server-side indexing, server-side access controls, and server-side retention decisions about user files, because the Service is designed to avoid receiving those files in ordinary tool use.
This design also supports repeatable verification. You can run the same tool with the same inputs locally to confirm results, validate changes, and produce a clear explanation without transferring the underlying source files to remote infrastructure.
When you download an output file, your browser writes that file into a location determined by your Device settings. The Service does not control your file system. You remain responsible for managing downloaded outputs, including retention, deletion, access permissions, and any synchronization or backup services you have enabled on your Device.
When you copy content, it becomes part of your Device clipboard. Your operating system and applications on your Device may provide clipboard history or clipboard synchronization. The Service does not control those Device-level features. If you handle sensitive material, you should manage clipboard usage accordingly and clear clipboard history where appropriate.
If you print a page or capture a screen, those actions occur within your Device environment. You control the destination and distribution of any printed material or captured image. Local-only processing does not prevent user-initiated sharing, and the Service does not represent that it can control what you do with outputs after you generate them.
The Service may provide optional channels for a User to request help, provide feedback, or otherwise transmit information. If you choose to transmit information through such a channel, you are intentionally sending that information. Any Voluntary Submission is limited to what you choose to provide. You control the scope and content of your submission.
You represent and warrant that any Voluntary Submission is lawful, that you have the right to transmit it, and that it does not violate any duty of confidentiality, contract, policy, or law. You agree to submit only the minimum information necessary for your request and to avoid including sensitive or regulated data unless you have determined that submission is appropriate and lawful in your context.
The local-only tools are designed so that you can often generate a reduced artifact on your Device, such as a minimal excerpt, an anonymized example, or a summary of expected versus actual behavior, before deciding whether to transmit anything.
You retain all rights, title, and interest in and to your User Content. The Service is a local processing utility designed to help you generate Derived Output on your own Device. Because User Content is not transmitted in ordinary operation, we do not take possession of it, store it, or index it as part of standard tool functionality.
As a structural consequence of local-only processing, we do not access, inspect, or disclose the contents of files you process locally during ordinary operation. We do not have routine visibility into the content of your reports because those contents are not transmitted as part of normal tool use.
This design supports confidential workflows. It allows you to compare reports, validate exports, identify mismatches, and generate explanations while keeping the underlying source files on your Device.
The Service is designed with protective intent. The primary security feature is architectural: local processing keeps file contents on your Device in ordinary operation. This reduces exposure associated with server-side retention of sensitive documents, centralized storage, and broad administrative access patterns found in many upload-based systems.
Data minimization is a security measure. By avoiding routine transmission of file contents, the Service reduces the amount of information that must be handled externally and reduces the number of systems that can access the content. This can reduce the practical impact of server-side incidents that involve centralized repositories of user files.
Integrity is supported by delivering code in a manner intended to preserve correct execution. Local-only processing reduces the number of systems that handle your file contents, which can simplify integrity considerations for confidential data handling. Outputs can be reproduced locally by rerunning a tool with the same input, supporting verification and confidence.
Local-only processing depends on the security of your Device and browser environment. You are responsible for controlling access to your Device, maintaining appropriate authentication measures, applying current security patches, and using secure browsing practices. If a Device is compromised, any locally processed content may be at risk on that Device regardless of whether a Service uploads files.
For sensitive workflows, use a trusted Device, avoid shared Devices, employ full-disk encryption where available, secure your browser profile, and manage downloads carefully. Evaluate browser extensions because extensions may have broad access to page content. These practices strengthen the local-only boundary by hardening the Device on which processing occurs.
In ordinary use, we do not retain your file contents because they are not uploaded. Any retention that occurs is local on your Device, under your control, and depends on your browser configuration and operating system environment. If you store outputs or drafts locally, you are responsible for retention and deletion decisions on your Device.
If you make a Voluntary Submission, retention of that submission is limited to what is reasonably necessary to address your request, maintain records of the interaction, and protect the Service and its Users, subject to applicable law.
Depending on your jurisdiction, you may have rights concerning personal information, including rights of access, correction, deletion, and objection. Because the Service is designed to keep User Content local, many privacy controls are exercised directly by you through your Device and browser settings, including deleting local files, clearing site data, and controlling what information you choose to transmit.
If you transmit a Voluntary Submission and later wish to request access, correction, or deletion of that submission, you may contact us through the contact methods made available on the site. You should provide sufficient detail to identify the submission and your request.
The Service is frequently used to troubleshoot reports that may contain business-sensitive information. The local-only model is intended to support careful handling by enabling you to work on your Device without routine uploads.
If you handle regulated data, you are responsible for ensuring that your use of the Service complies with applicable law, contractual obligations, and internal policies. The Service provides a local processing pathway, but it does not replace your compliance obligations, your internal approvals, or your contractual commitments.
We implement administrative, technical, and organizational safeguards designed to protect the Service and to reduce unnecessary data exposure. A central safeguard is architectural: ordinary tool operation is designed to keep User Content on your Device through local processing, which materially limits external handling of file contents.
Security is supported by multiple factors, including your Device security posture, your browser configuration, your network environment, and your own sharing decisions. The Service is designed to operate as a local processing utility so that you can obtain results without routinely transmitting file contents to remote storage.
The Service is not responsible for third-party components you install in your browser, for Device-level clipboard or synchronization features, or for user-directed sharing actions you take outside the local-only processing flow.
Local-only processing is a design pattern where computation occurs on the User’s Device rather than on a centralized server. Under this model, the primary privacy benefit is boundary control: User Content remains in the environment that the User directly controls. This reduces uncertainty for Users who must handle sensitive business metrics, customer identifiers, proprietary calculations, or internal operational numbers. The Service is designed to deliver diagnostic value while preserving this boundary in ordinary use.
In a server-upload model, a User must trust the processor with the file, the processor must store the file at least temporarily, and the processor must implement retention and deletion. Local-only processing reduces dependency on those external controls because the Service does not need to receive the file to compute results. It reduces the number of systems that can access the content and reduces the number of entities that could be compelled to disclose stored files, because ordinary operation avoids server-side file storage.
Local-only processing supports proportionality. In many troubleshooting cases, the full source file is not necessary to communicate the conclusion. A User can generate a diff locally, isolate the relevant rows or fields, and then share only the minimal excerpt required for internal discussion. The Service is designed to enable that workflow by providing local comparisons and local exports. The User retains custody of the full file, and the User chooses whether to share a reduced artifact or to keep the result private.
From a confidentiality perspective, local-only processing is materially different from a cloud upload. When a file stays on the Device, confidentiality depends primarily on Device access controls rather than on remote storage policies. The Service supports confidentiality by minimizing external handling of User Content. For many Users, the ability to obtain tool results without uploading the underlying source file is the decisive privacy feature.
The Service also supports repeatable verification. If you want to confirm a result, you can rerun the same tool locally with the same inputs and observe whether the output is consistent. This repeatability supports confidence in decision-making, particularly when a reporting deadline is near and the cost of an incorrect export is high. Local repeatability also supports internal quality controls by enabling the User to reproduce the same diagnostic steps without exposing the file to external storage.
Local-only processing is a design pattern where computation occurs on the User’s Device rather than on a centralized server. Under this model, the primary privacy benefit is boundary control: User Content remains in the environment that the User directly controls. This reduces uncertainty for Users who must handle sensitive business metrics, customer identifiers, proprietary calculations, or internal operational numbers. The Service is designed to deliver diagnostic value while preserving this boundary in ordinary use.
In a server-upload model, a the User must trust the processor with the file, the processor must store the file at least temporarily, and the processor must implement retention and deletion. Local-only processing reduces dependency on those external controls because the Service does not need to receive the file to compute results. It reduces the number of systems that can access the content and reduces the number of entities that could be compelled to disclose stored files, because ordinary operation avoids server-side file storage.
Local-only processing supports proportionality. In many troubleshooting cases, the full source file is not necessary to communicate the conclusion. A User can generate a diff locally, isolate the relevant rows or fields, and then share only the minimal excerpt required for internal discussion. The Service is designed to enable that workflow by providing local comparisons and local exports. The User retains custody of the full file, and the User chooses whether to share a reduced artifact or to keep the result private.
From a confidentiality perspective, local-only processing is materially different from a cloud upload. When a file stays on the Device, confidentiality depends primarily on Device access controls rather than on remote storage policies. The Service supports confidentiality by minimizing external handling of User Content. For many Users, the ability to obtain tool results without uploading the underlying source file is the decisive privacy feature.
The Service also supports repeatable verification. If you want to confirm a result, you can rerun the same tool locally with the same inputs and observe whether the output is consistent. This repeatability supports confidence in decision-making, particularly when a reporting deadline is near and the cost of an incorrect export is high. Local repeatability also supports internal quality controls by enabling the User to reproduce the same diagnostic steps without exposing the file to external storage. This statement is intended to be read as an affirmative description of the Service design and the expected default handling of User Content.
In professional settings, report mismatches can trigger operational risk and internal escalation. Users often want clarity without introducing new uncertainty about where sensitive exports went. The local-only design addresses this by keeping report content inside the User’s environment. A User can run comparisons and validations locally, identify the mismatch, produce a concise explanation, and share only what is necessary for resolution.
Local-only processing can simplify internal documentation. When User Content remains on the Device in ordinary use, there is often less need to document external file processors in data flow diagrams for routine tool operation. This can reduce administrative overhead in environments with strict vendor management, because ordinary tool use does not depend on transferring file contents to a remote processor.
Local-only processing also reduces the risk of accidental retention. In upload-centric systems, a file may be retained longer than intended because of backups, logs, caching layers, or operator error. Local-only processing avoids that category of risk for ordinary operation because the Service does not receive the file contents in the first place. The User remains in control of retention on the Device, including deletion, secure storage, and access permissions.
When a User needs assistance, the local tools allow preparation of a minimal, controlled artifact. For example, a User can summarize the issue as expected versus actual behavior, or produce a minimal dataset that reproduces the problem without including the full confidential export. This approach preserves confidentiality while still enabling effective troubleshooting.
In professional settings, report mismatches can trigger operational risk and internal escalation. Users often want clarity without introducing new uncertainty about where sensitive exports went. The local-only design addresses this by keeping report content inside the User’s environment. A User can run comparisons and validations locally, identify the mismatch, produce a concise explanation, and share only what is necessary for resolution.
Local-only processing can simplify internal documentation. When the User Content remains on the Device in ordinary use, there is often less need to document external file processors in data flow diagrams for routine tool operation. This can reduce administrative overhead in environments with strict vendor management, because ordinary tool use does not depend on transferring file contents to a remote processor.
Local-only processing also reduces the risk of accidental retention. In upload-centric systems, a file may be retained longer than intended because of backups, logs, caching layers, or operator error. Local-only processing avoids that category of risk for ordinary operation because the Service does not receive the file contents in the first place. The User remains in control of retention on the device, including deletion, secure storage, and access permissions.
When a User needs assistance, the local tools allow preparation of a minimal, controlled artifact. For example, a User can summarize the issue as expected versus actual behavior, or produce a minimal dataset that reproduces the problem without including the full confidential export. This approach preserves confidentiality while still enabling effective troubleshooting.
Security is not a single control. It is a combination of design, delivery, and use. The Service emphasizes risk reduction by minimizing external handling of sensitive files. This structural minimization is a meaningful safeguard, but it operates in coordination with User-controlled protections on the Device.
The Service supports confidentiality by avoiding routine server-side file storage in ordinary operation. This reduces exposure to incidents that involve centralized repositories. It also reduces the need for broad server-side administrative access to user files, because the system is designed not to receive those files for standard processing.
The User remains responsible for Device security. If an unauthorized party gains access to your Device, browser profile, downloads folder, clipboard history, or local storage, that party may access locally processed data regardless of whether the Service uploads files. You should therefore implement safeguards that are proportionate to the sensitivity of the data, including strong authentication, limited physical access, and encryption where available.
Browser extensions and plug-ins can materially change the security posture of a browser session. Extensions may have access to content rendered in the page or to clipboard data. For high-confidentiality workflows, you should consider using a controlled browser profile with minimal extensions and a strong Device access boundary.
Security is not a single control. It is a combination of design, delivery, and use. The Service emphasizes risk reduction by minimizing external handling of sensitive files. This structural minimization is a meaningful safeguard, but it operates in coordination with User-controlled protections on the Device.
The Service supports confidentiality by avoiding routine server-side file storage in ordinary operation. This reduces exposure to incidents that involve centralized repositories. It also reduces the need for broad server-side administrative access to user files, because the system is designed not to receive those files for standard processing.
The User remains responsible for device security. If an unauthorized party gains access to your device, browser profile, downloads folder, clipboard history, or local storage, that party may access locally processed data regardless of whether the Service uploads files. You should therefore implement safeguards that are proportionate to the sensitivity of the data, including strong authentication, limited physical access, and encryption where available.
Browser extensions and plug-ins can materially change the security posture of a browser session. Extensions may have access to content rendered in the page or to clipboard data. For high-confidentiality workflows, you should consider using a controlled browser profile with minimal extensions and a strong Device access boundary.
This Policy is intended to be interpreted in a manner consistent with the local-only design. Where the Policy describes ordinary operation, it describes behavior that is intended to occur without requiring a User to transmit file contents to a remote processor. This notice is designed to establish clear expectations about custody and control of User Content.
If you transmit a Voluntary Submission, you authorize us to receive and process that submission solely for the purposes associated with your request and for operation and protection of the Service, subject to applicable law. You agree that you will not transmit information you are not authorized to share.
The Service cannot control what you do with your outputs. If you download a file, email it, upload it to another service, or share it through a messaging platform, those actions are outside the local-only boundary and are governed by the tools and services you use. You remain responsible for those decisions.
If any provision of this Policy is held invalid or unenforceable, the remaining provisions remain in effect to the maximum extent permitted by law. Headings are provided for convenience and do not affect interpretation. The terms “including” and “without limitation” are illustrative.
This Policy is intended to be interpreted in a manner consistent with the local-only design. Where the Policy describes ordinary operation, it describes behavior that is intended to occur without requiring a User to transmit file contents to a remote processor. This notice is designed to establish clear expectations about custody and control of User Content.
If you transmit a Voluntary Submission, you authorize us to receive and process that submission solely for the purposes associated with your request and for operation and protection of the Service, subject to applicable law. You agree that you will not transmit information you are not authorized to share.
The Service cannot control what you do with your outputs. If you download a file, email it, upload it to another service, or share it through a messaging platform, those actions are outside the local-only boundary and are governed by the tools and services you use. You remain responsible for those decisions.
If any provision of this Policy is held invalid or unenforceable, the remaining provisions remain in effect to the maximum extent permitted by law. Headings are provided for convenience and do not affect interpretation. The terms “including” and “without limitation” are illustrative.
Practical takeaway: Load your files, run the tool, review the result, then decide what to share, if anything. The Service is designed so that your report data stays local unless you choose to share something.
The local-only design is intended to reduce exposure by keeping file contents within your Device boundary during ordinary operation. This is a meaningful safeguard because it removes the need for routine server-side storage of your input files. In practice, this helps you run diagnostics without creating a new remote copy of a sensitive export.
For the strongest confidentiality posture, pair local-only processing with Device safeguards. Use a trusted Device, restrict access to your browser profile, and store downloads in locations with appropriate permissions. If you use synchronized storage, treat the sync destination as part of your storage boundary and apply protections accordingly.
The Service is designed to support careful decision-making. You can run the same check repeatedly, confirm the output locally, and produce a minimal summary for communication. This reduces the need to circulate full source files and helps keep sensitive information contained.
The Service is structured so that the core diagnostic purpose can be achieved without routine transmission of User Content. This supports minimization and proportionality: the tools aim to produce the smallest necessary output for the task while leaving the underlying source files on your Device.
When you choose to share something, you control what is shared. You can share only a reduced excerpt, an anonymized sample, or a narrative explanation, and you can keep the original file local. This Policy is intended to make that boundary explicit.