BagoBoothDownload Windows 2.6
← Back to download pageBAGOBOOTH · NATIVE WINDOWS

Your photos & privacy

How the native Windows app stores information and what leaves your computer.

Photos and layouts stay on your PC

The native app stores events, captures and artwork in your Windows studio folder, normally %LOCALAPPDATA%\BagoBooth. Activation keys and the optional QR sharing connection token are encrypted for your Windows account. Testing a QR connection only contacts the local sharing service; it does not upload photos. The separate browser edition stores its local workspace in the browser profile.

Photoman, Chroma key and Flipbook

Photoman reads JPEG/PNG photos from the transfer folder you choose while receiving is started. Original files stay there. Imported pictures and their deduplication fingerprints are saved in the local studio. Chroma backgrounds are copied into local Templates; Flipbook animation and printable frames are saved in Photos. Backups include those files. These features do not automatically upload photos.

Activation and license checks

The native app sends the requested activation action, installation ID and activation key to the license service for trial and subscription checks. The service is hosted using Supabase and receives connection information such as your IP address. This information is used to validate installation access and expiry. Product and activation support is available from @kennethantonil.

Sharing is your choice

Choosing Share with QR and confirming sends the selected capture to your configured cloud bridge. Get the guest's consent first. Anyone with a guest link may access the shared file. Cloud storage and retention depend on the configured sharing service. Deleting a local capture does not delete an already shared cloud copy.

Telegram and payment requests

The app's plan link includes your installation ID and selected plan. Opening it does not send a message or pay automatically. If you submit a request, information you send in Telegram is handled through Telegram and the activation bot. Keep payment references, activation keys and migration exports private.

Backups and deletion

Browser migration exports can contain activation keys. Portable native studio backups exclude activation credentials. Local files can be managed from Local workspace; removing the app executable does not automatically delete its studio folder. Contact the owner about questions or requests concerning activation information.

About & release details · Privacy · Payments & support

Contact @kennethantonil