The static production build does not need a FlytheBG Python inference service, GPU endpoint, or upload API to remove a background.
Guide · Browser privacy
What browser-only image processing means in FlytheBG.
The current production tools are designed so the selected photo can be processed, edited, composed, and exported inside the visitor's browser. That is different from saying the browser makes no network requests at all.
01 · Image bytes
The photo is not intentionally sent to FlytheBG's hosting or database.
For Remove Background, Crop, and Passport Photo Maker, image pixels are kept in browser-managed objects while the page is being used.
FlytheBG does not intentionally write source photos or generated PNG files to Supabase or another image database in the current production workflow.
Crop rectangles, passport-photo framing, background colors, copy layout, and generated canvases exist in the browser while the tool is active.
02 · Model assets
Browser inference still needs software and model files.
IMG.LY's browser package downloads neural-network and WebAssembly/runtime assets required to perform local inference. Those are software assets, not copies of the selected image.
The browser can contact IMG.LY's configured distribution infrastructure to retrieve model/runtime files. Normal network information is therefore involved in delivering those files.
FlytheBG passes the selected image to the browser package on the user's device and does not intentionally attach that image to model-asset download requests.
Browsers may cache model/runtime software so later sessions do not need to download the same assets again. Cache duration and eviction are controlled by the browser and device.
03 · Cleanup
What FlytheBG clears after download.
The page releases the working references and generated objects it controls after a download starts or when the current tool is reset.
Object URLs, prepared previews, result blobs held by components, crop state, and generated passport-sheet canvases are released or reset by the current flow.
Downloading intentionally creates a file on the user's device. FlytheBG cannot and should not delete the file the user chose to save.
Browser or operating-system caches, screenshots, extensions, security software, backups, copied files, and other device-level data are outside FlytheBG page-state control.
04 · Advertising separation
Operational image screens remain separate from ad serving during review.
The current production layout can expose the public AdSense account identifier for site verification without loading Google-served ad JavaScript into Remove Background, Passport Photo Maker, or other utility/legal screens.
An AdSense publisher identifier and ads.txt seller record are public site identifiers, not passwords, database credentials, or private API keys.
Background removal and passport-sheet creation exist to perform user actions. They should remain focused on those actions rather than becoming ad containers.
Advertising cookies and consent requirements are separate from image processing. The image tools are designed not to depend on optional advertising storage.
Formal details
Need the policy wording?
The Privacy & AI Policy describes the production data flow and its limitations.