IT services that keep your business running.

Last updated:

1. Introduction

This Privacy Policy explains how MARCOSJF I.T. SERVICES (“MARCOSJF”, “we”, “us”, or “our”) handles information when you visit or interact with this website. It is written to be practical, transparent, and easy to understand. By using this website, you acknowledge that you have read this Privacy Policy. If you do not agree, please discontinue use of the website and do not submit information through the forms.

2. Scope

This Privacy Policy applies to information processed through this website, including information you provide in forms, information generated by your interactions with page elements, and certain technical data needed to operate the website reliably. This website is a pure front-end portal. In typical use, form entries and operational logs are stored locally in your browser storage on your device. That means the information generally remains under your control on the device you are using unless you choose to export it or share it.

3. Information We Process

MARCOSJF may process the following categories of information depending on how you use the website: (a) identifiers and business contact details you submit, such as your name, email address, and organization name; (b) message content you type into the contact form; (c) selection data such as your chosen service topic; (d) technical context like browser type, approximate device characteristics, and page URL; and (e) operational events such as button clicks that open dialogs or submit the form. The goal of processing is to provide the portal experience and allow you to request information about services.

4. Purpose of Processing

MARCOSJF processes information for specific purposes: operating the website; recording your request so it can be reviewed; improving clarity and usability; maintaining security and integrity of the portal experience; supporting troubleshooting when errors occur; and maintaining a minimal local record of interactions if you choose to view logs. The website is designed with privacy in mind and aims to minimize data collection.

5. Local Storage and Device Control

Because this website is a pure front-end portal, information may be stored in your browser local storage on your device. MARCOSJF uses local storage to save operational logs, remember your preference regarding acceptance of this Privacy Policy, and store the content of form submissions locally so that you can confirm what was entered. You can remove this information at any time by clearing site data in your browser settings, using private browsing, or using built-in controls on this website that clear logs.

6. Cookies and Similar Technologies

This website may use local browser mechanisms such as cookies or local storage to remember preferences and to support basic functionality. If you block cookies, some features may not work as expected. You can control cookies and local storage through browser settings. Where possible, MARCOSJF uses simple storage keys and avoids unnecessary tracking.

7. Sharing and Disclosure

MARCOSJF does not sell personal information. The website is designed to keep your submitted information on your device by default. If you export logs, you create a file on your device that you control. If you share that file, the recipients may store it. MARCOSJF may disclose information only if legally required or if necessary to protect rights, safety, and security in the event of misuse. Because deployments differ, hosted environments may generate standard server access logs, but this website itself is designed to operate without requiring a backend.

8. Security

MARCOSJF uses reasonable safeguards to help protect information within the limits of a browser-based portal. However, no system is perfectly secure. You should protect your device, keep your browser updated, avoid untrusted extensions, and avoid entering secrets such as passwords, verification codes, financial account details, or private keys into the message field. If you accidentally store sensitive data locally, clear site data in your browser and remove exported files from your device.

9. Retention

MARCOSJF aims to retain only what is necessary for the portal features. Operational logs are capped to a reasonable number of recent entries. Locally stored form submissions are also capped. Retention is primarily controlled by your device: data remains until you clear it, reset it, or your browser removes it based on its own policies.

10. Your Choices and Rights

You can choose not to submit information through the form. If you do submit, you can later clear local storage to remove the information from your device. Depending on applicable law, you may have rights to access, correct, or delete personal information. Because the portal is designed to store information locally, many of these controls can be exercised directly in your browser. If you need assistance, you can contact MARCOSJF through the contact details listed on this site.

11. Children’s Privacy

This website is intended for business users. MARCOSJF does not knowingly request information from children. If you believe that a child has submitted personal information through this portal, clear local storage and contact MARCOSJF so guidance can be provided.

12. International Use

This website can be accessed from different locations. Because the portal stores information locally by default, the primary processing location is your device. If you choose to share exported logs or copied form contents, you control where that information is sent. MARCOSJF encourages careful handling of exported files and use of secure channels.

13. Updates

MARCOSJF may update this Privacy Policy to reflect improvements or changes in practices. The “Last updated” date will be revised. Continued use of the website after changes means you accept the updated Privacy Policy. If changes are significant, the website may show a notice.

14. Extended Transparency Notice

The following extended notice provides additional clarity in plain language. It is intentionally detailed so the policy is self-contained and practical. MARCOSJF believes that privacy works best when users understand what is happening. When you load this website, your browser downloads HTML, CSS, JavaScript, and image assets, including the MARCOSJF logo. Your browser may cache these resources to speed up future visits. When you click buttons, open dialogs, or navigate between sections, the website may record simple operational events in a local log. These logs are designed for troubleshooting and for your own review. When you submit the contact form, the website records the values you typed into local storage to show a confirmation state and to demonstrate that the portal works without a server. This means that your message is not automatically transmitted to MARCOSJF through the portal. If you want MARCOSJF to receive your request, replace the demo form logic with a real submission endpoint in your deployment. Until that change is made, the portal stores entries locally on your device.

MARCOSJF recommends that you treat any exported file as sensitive. If you choose to export logs, your device will download a text file that may include timestamps, event names, and any data attached to those events. Exported logs can also include technical context such as browser user agent strings and page URLs. Before you share an exported log file, review it carefully and remove anything you do not want to disclose. If you are unsure, keep the file on your device and use it only for your internal troubleshooting. If you share the file, recipients may keep copies. That sharing is under your control.

MARCOSJF minimizes sensitive collection by design. The portal does not ask for passwords. The portal does not require government identifiers. The portal does not require precise location data. The portal does not require payment details. If you type sensitive information into the message field anyway, you should treat it as sensitive and clear it from local storage afterward. You can clear your browser’s site data for this portal, which removes locally stored submissions and log entries. You can also use private browsing mode to reduce persistence, noting that browser behavior varies. MARCOSJF also recommends avoiding use on shared or public computers. If you must use a shared device, do not submit personal information and clear the browser data after finishing.

MARCOSJF may use standard web hosting, and some hosting setups record basic access logs at the server level. These logs, if present, commonly include IP address, request time, requested file, and response status. Such logs are typically used for security monitoring, abuse prevention, and operational reliability. The exact presence and retention of hosting logs depends on how you deploy the static site. The portal’s front-end code does not require server-side tracking, and MARCOSJF encourages a privacy-respecting hosting configuration where feasible.

MARCOSJF builds IT services with accountability. If you contact MARCOSJF through channels outside this portal (such as email or phone), those communications may be processed to provide the requested services. MARCOSJF will use such information to respond, plan, and deliver services. If an incident occurs that affects information security, MARCOSJF will take reasonable steps to investigate and mitigate. Because this portal is static and stores data locally by default, many risks relate to device security. Keep your device secured, keep browsers updated, and avoid untrusted software.

MARCOSJF is committed to purpose limitation: information is processed only for the purposes described here or for compatible purposes. If MARCOSJF changes how the portal works in a way that materially increases processing, this Privacy Policy will be updated to reflect that change. This extended notice is included so that the policy remains complete and sufficiently detailed for informed use.

16. Appendix B: Detailed Operational Privacy Notes

This Appendix B is included to provide additional depth and clarity for users who want a highly detailed explanation of how information is handled in a front-end portal experience. MARCOSJF provides this Appendix B to help users evaluate privacy and security impacts in a practical way. The explanations below are written in plain language and are intended to be self-contained.

When you interact with a browser-based portal, your browser renders the interface and may temporarily hold information in memory to display content. MARCOSJF designs this portal to minimize persistence where possible, but some persistence may be used for convenience and transparency. For example, a record that you accepted this Privacy Policy may be saved so that you are not repeatedly interrupted. MARCOSJF stores such preference records using local browser storage. You can remove them by clearing site data in your browser.

Operational logs are designed to help users and administrators understand what the portal did. MARCOSJF includes a log viewer so that you can inspect what was recorded. A typical log entry can include a timestamp, a level indicator, a short message, and optional metadata. Metadata can include the page URL, and the user agent string that identifies browser and platform. MARCOSJF includes these fields for diagnostic clarity. If you consider user agent strings sensitive, you may avoid exporting logs and may clear logs after reviewing them.

This portal may store form submissions locally. MARCOSJF does this in the default demo configuration to keep the portal purely front-end. In this mode, submission content is saved on your device, not transmitted to MARCOSJF. This design supports offline-style testing and demonstration. If you deploy this portal in production and want MARCOSJF to receive messages automatically, you must integrate a secure server endpoint and update the form submission logic accordingly. MARCOSJF recommends using transport encryption, authentication, and robust access controls for any server endpoint.

If you export logs from the portal, the portal will create a downloadable text file on your device. MARCOSJF does not automatically upload that file anywhere. After export, the file is under your control. If you store it in shared folders, sync it using third-party tools, or email it, other parties may gain access. MARCOSJF recommends treating exported logs as potentially sensitive operational artifacts and restricting access appropriately.

Browser storage is not a secure vault. MARCOSJF uses browser storage for convenience and transparency, not for storing secrets. Do not enter passwords, authentication tokens, private keys, financial details, or confidential credentials into the portal. If you accidentally enter sensitive data, remove it by clearing the portal’s site data and deleting any exported files that contain the data. MARCOSJF also recommends reviewing your browser extension list and removing untrusted extensions because extensions may access page content in some configurations.

The portal’s user interface can display many sections and may include navigation links. Clicking links typically changes the scroll position and may open dialogs. MARCOSJF may record such actions in local logs to make behavior traceable. This trace helps confirm that the portal responded to user actions. It also helps detect UI errors when users report unexpected behavior. MARCOSJF keeps logs limited in size and may keep only the most recent entries.

If the portal is hosted on infrastructure that records access logs, those logs are typically controlled by the hosting operator. MARCOSJF encourages privacy-respecting hosting and recommends minimizing retention. The portal itself is designed to function without requiring behavioral analytics. If you add analytics, you should update this Privacy Policy accordingly. MARCOSJF encourages transparency and does not support hidden tracking in business portals.

MARCOSJF supports a principle of data minimization. The portal requests only basic business contact information and a message, which is generally sufficient to begin a conversation. If additional details are necessary for service delivery, MARCOSJF recommends using secure channels and limiting disclosure to what is required. If a customer engagement requires processing of customer-provided information, MARCOSJF can align processing to contractual terms and applicable laws.

If you want to avoid persistence entirely, you can use private browsing mode and avoid exporting any files. MARCOSJF notes that private browsing behavior varies by browser and operating system. Some traces may still exist, such as in network equipment or hosting logs. For strong privacy assurance, MARCOSJF recommends combining technical controls with sound operational practices, including device security and controlled sharing.

If you have privacy questions, MARCOSJF encourages you to ask. Clarity is a security feature. This Appendix B is intentionally verbose to ensure that users can understand the portal’s behavior without needing external documentation. MARCOSJF may refine the wording over time to improve readability while preserving accuracy.

15. Contact

For questions about this Privacy Policy, contact MARCOSJF using the contact section on this website. When contacting, please avoid sending secrets. Describe your question clearly so MARCOSJF can respond efficiently.