Privacy Policy / Updated 12 October 2026

Your files stay in your browser.

This policy separates local tool processing from page requests and any email you choose to send.

⚠ Local draft: public operator identification, hosting details and the legal basis/retention for support correspondence must be verified before publication. This page does not claim legal clearance.

1. Local files and tool inputs

Selecting or dropping an image or CSV lets this tab read that selected file. Images are decoded and rendered locally; CSV text is parsed locally. File contents, filenames, settings and results are not transmitted to FieldWise or a conversion service. There are no remote file-upload endpoints.

The checker reads technical properties; it does not send a photo elsewhere to identify a face. CSV diagnostics do not send rows to an AI model. Fonts, icons, styles and scripts are site-local assets.

2. Browser memory and downloads

Inputs and results remain in this tab’s memory during use. Clear removes current references and previews; closing the tab ends the session. Inputs are not saved by FieldWise in cookies, local storage, session storage or IndexedDB. Moving to a different tool does not automatically transfer your file.

Downloads create local copies or text reports. Originals are not overwritten. Your device/browser may retain downloads, cache or history. Clear is not a guarantee of forensic erasure from your computer.

3. Email is a separate, voluntary action

If you email fieldwise.tools@gmail.com, the operator receives your address and whatever message or attachments you choose to send. This is outside the browser-local tools and is handled through your email provider and the Gmail mailbox.

The intended purpose is to reply to feedback, tool issues and privacy inquiries. Do not send passwords, identity documents, private photos or confidential CSV exports. FieldWise does not automatically email or attach your selected files.

Before launch: the operator must confirm the applicable legal basis, a proportionate retention/deletion practice, provider roles and any transfer disclosures for correspondence. No invented retention period or guaranteed response deadline is stated here.

4. Page requests and future hosting

A local preview server receives requests for HTML, scripts and styles. The planned public host is Cloudflare Pages, but there is no confirmed public address or deployed service yet. Actual hosting can receive IP addresses and browser/request details through ordinary infrastructure logs.

Before publication, identify the actual host, relevant logging/security behavior, processing roles, retention information and applicable legal basis. A local-processing claim does not mean that a public host receives no request information. External documentation links are opened only when you choose them.

5. Cookies, analytics and advertising

The current site does not set cookies, persist tool inputs or load analytics/advertising scripts. No consent popup is added for absent tracking. The eventual hosting environment must still be checked for its actual behavior.

Analytics or display advertisements are future possibilities, not active features. They require separate owner approval, an updated policy and appropriate consent/withdrawal controls where required. Advertising may involve third parties even when described as non-personalized.

6. Privacy questions and applicable rights

For a question about data handled outside the local tools, contact fieldwise.tools@gmail.com. Where GDPR applies, relevant rights can include information/access, correction, deletion, restriction, objection, portability or withdrawing consent, depending on the processing and legal basis. The operator must assess and handle requests under applicable law.

FieldWise is a personal project operated by an individual based in Croatia, not a registered business. The public brand is FieldWise; legally necessary controller/operator identification remains a launch-review item. You may contact Croatia’s data-protection authority, AZOP, about concerns within its remit.

7. Changes

Review this policy again before any public hosting, analytics or advertising change. Updated behavior must be described accurately; the current text is not a promise that future third-party infrastructure will work the same way.