1. Information We Do Not Collect

FluidWeb does not have a backend server of its own. There is no FluidWeb account, no sign-in, and no user profile stored anywhere outside your device. Specifically, we do not:

• Collect analytics, usage statistics, or crash reports

• Use advertising or tracking SDKs of any kind

• Sell, rent, or share your data with third parties, because we do not collect it in the first place

• Have any way to see your browsing history, bookmarks, downloads, or settings — these never leave your device through us

2. Information Processed on Your Device

The following data exists only locally on your device, stored by the App itself:

• Browsing history and bookmarks — saved locally so you can revisit and search them. Never transmitted anywhere by the App.

• Downloaded files — saved to your device's storage (via Android's MediaStore, in the appropriate Downloads/Movies/Pictures folder depending on file type).

• App settings — including preferences like ad-blocking, search engine choice, and default download behavior — stored locally.

• Backup files — if you use the backup/export feature, a JSON file containing your bookmarks and settings is written to your device's own Downloads folder (or wherever you choose to save it). This file is never uploaded anywhere by the App; if you enable automatic backups, they are saved to the same local folder on a schedule you choose. You are responsible for that file if you choose to move, share, or upload it yourself.

• Temporary camera capture files — see Section 6 below.

Uninstalling the App removes this locally-stored data, subject to how your device handles app data on uninstall.

3. Browsing Activity

FluidWeb is a web browser. When you visit a website, standard browser behavior applies, the same as with any other browser:

• The website you visit can see information your browser normally sends (such as your IP address and the pages you request), governed by that website's own privacy policy — not this one.

• Cookies and site data are stored locally by the browser engine to keep you logged into sites you use, exactly as they would in Chrome, Firefox, or any other browser. This data stays on your device and is not sent to us.

• You can clear this data at any time through the App's settings.

4. Location Permission

FluidWeb requests location permission only when a website you're visiting asks for your location (for example, a maps or local-search site) and you explicitly choose to allow it in that moment. This is never requested just for having the App installed.

• If you allow it, your location is provided directly to the requesting website through your browser, the same as it would be in any browser. FluidWeb itself does not collect, store, or transmit this location data separately.

• You can block location access for all sites by default in the App's settings, in which case sites are denied before the App ever requests this permission from Android.

5. Camera and Microphone Access (Video/Voice on Websites)

Some websites use your camera and/or microphone directly within the page itself — for example, a video-calling site, a voice-input feature, or an in-browser QR/document scanner. This is different from attaching an existing or newly-captured photo/video to an upload, which is covered separately in Section 6.

• FluidWeb requests Android's Camera and/or Microphone permission only when a website actively asks for this kind of access, and only for whichever of the two the website actually requested — a site asking only for the microphone is never asked to also grant camera access, and vice versa. This is never requested just for having the App installed.

• Before Android's own system permission prompt appears, FluidWeb first shows its own Allow/Block prompt naming the requesting website, so you always know which site is asking before any system-level permission is touched.

• If you allow it, your camera and/or microphone stream is provided directly to the requesting website through your browser, the same as it would be in any other browser with this feature. FluidWeb itself does not separately record, copy, store, or transmit this stream anywhere — it does not pass through us in any form.

• The App does not currently remember a website's earlier Allow/Block choice across separate requests, so you may be asked again later, including by the same website in the same browsing session. This can happen more than once per site depending on how that site's own page is built.

• If you decline, the website does not get camera or microphone access. FluidWeb does not access your device's camera or microphone at any other time, for any other purpose.

• On a device with no camera and/or no microphone, this feature is simply unavailable for the missing hardware.

6. File Uploads and Camera Access

FluidWeb supports uploading files to websites that request it — for example, attaching a photo to an email or posting a photo or video on a social media site. This is separate from the live, in-page camera/microphone access described in Section 5 above.

• Choosing an existing file. When you tap an upload button on a website, FluidWeb opens Android's own file picker (or, on supported Android versions, the system's native Photo Picker) so you can choose an existing photo, video, or other file already on your device.

• Taking a new photo or video. If a website specifically asks to use your camera (rather than choosing an existing file), FluidWeb hands off to a separate camera app already installed on your device to actually capture it. This hand-off does not use, and is not related to, the Camera permission described in Section 5 — FluidWeb cannot access your camera directly for this flow. The camera app you already have installed handles the capture, using its own permission, not one requested by FluidWeb. Devices with no camera at all are unaffected; this feature is simply unavailable there.

• Where a captured photo or video briefly lives. A photo or video captured this way is temporarily written to a private, app-only folder on your device that no other app can access, just long enough to hand it to the website you were using. This is not a persistent photo library entry and is not something FluidWeb keeps, browses, or reuses afterward.

• In all cases, the file you selected or captured is handed directly to the website you were using — the same as it would be in any other browser. FluidWeb does not separately copy, inspect, retain, or transmit that file anywhere else on its own. What that website does with the file afterward (where it's uploaded, how long it's kept) is governed by that website's own privacy policy, not this one.

7. Notifications

FluidWeb requests notification permission solely to show you the progress of your own downloads (e.g., "Downloading — 45%"). These notifications are generated entirely on your device and are not connected to any messaging or push-notification service.

8. Downloads from Social Media Sites

FluidWeb includes a feature that detects downloadable videos and photos while you browse certain social media sites and adds a download button for them. This works by reading publicly-viewable page content and, where needed, using your own already-logged-in browser session on that site — the same session you'd have anyway — to identify the actual media file address. FluidWeb does not separately collect your login credentials, session tokens, or account information from these sites; that data remains within your browser session, managed the same way it would be for normal browsing.

Downloaded files are fetched directly from the website's or content delivery network's own servers to your device. FluidWeb does not proxy, inspect, or store a copy of what you download anywhere except on your own device.

9. Third-Party Services

FluidWeb relies on a small number of external services to function:

• Ad-blocking filter list. To power the optional ad-blocking feature, the App periodically downloads a publicly available list of ad/tracker domains (an open-source hosts file) from GitHub. This is a one-way download of a static, public list — no data about you is sent as part of this.

• Google Play Billing. If you choose to make the optional one-time "Support development" purchase, that transaction is handled entirely by Google Play. FluidWeb never sees or stores your payment details (card numbers, billing address, etc.) — Google Play only informs the App whether the purchase was successful. Google's own Privacy Policy governs that transaction: https://policies.google.com/privacy

• Camera and file-picker apps. When you use the upload or camera-capture feature described in Section 5, Android's own file picker and, where relevant, a separate camera app installed on your device are invoked to let you select or capture content. These are separate apps with their own privacy policies; FluidWeb does not control, and is not responsible for, what those apps themselves do with data while you're using them.

• The websites you visit. As with any browser, each website you visit is a separate data controller for whatever it collects from you, governed by its own privacy policy.

10. Children's Privacy

FluidWeb is not directed at children and we do not knowingly collect personal information from children. Because FluidWeb is a general-purpose web browser, we are not able to control what content a user chooses to browse to; parents and guardians are responsible for supervising use by children.

11. Data Security

Since your data is stored locally on your device rather than on a server we control, its security depends significantly on your own device security (screen lock, device encryption, and keeping Android up to date). We recommend using Android's standard device protections.

Files temporarily created for camera capture (Section 5) are stored in a private, app-only location that other apps on your device cannot read.

12. Your Choices and Controls

• Clear browsing data, cookies, and history at any time from within the App.

• Disable location access, ad blocking, or other features individually in Settings.

• Allow or block a website's request for live camera/microphone access (Section 5) on a per-request basis — the App never accesses either except in direct response to a specific website request.

• Export or delete your local backup files at any time — they're regular files on your device.

• Decline any upload or camera-capture request a website makes — the App never accesses your files or camera except in direct response to a request you've actively initiated.

• Uninstall the App to remove its locally-stored data from your device.

13. Changes to This Policy

We may update this Privacy Policy from time to time, for example if we add a new feature that changes how data is handled. We will update the "Effective date" above when we do. Continued use of the App after a change constitutes acceptance of the updated policy.

14. Contact Us 

For any privacy-related questions or concerns, please contact us at:

📧 fluidwhirl@gmail.com 

This policy describes FluidWeb version 1.0 and later. For older versions, behavior may differ.