Last updated: July 22, 2026
This policy explains how Froggy Works handles data when you use froggyworks.com, the Windows and macOS apps, the iPhone and iPad apps, online multiplayer, and related game services.
At a glance
- You can play without creating a Froggy Works account.
- Offline saves, screenshots, settings, and save thumbnails stay on your device unless you choose to share them.
- When the game is online, we collect limited usage analytics and diagnostic farm snapshots.
- Online farms use our servers for discovery, membership, signaling, and recovery snapshots. Gameplay normally travels directly between players.
- We do not sell personal data or use it for targeted advertising.
Data stored on your device
The web game uses browser storage. Native apps use their application-data folder and platform settings storage. Depending on the features you use, this can include:
- Up to three offline game saves, save-slot details, and farm preview thumbnails.
- Your chosen display name and language.
- Sound, music, graphics, controller, window, accessibility, and interface settings.
- Achievement progress and identifiers used to avoid reporting the same unlock twice.
- A randomly generated multiplayer client ID and device secret used to authenticate your farm memberships and reconnect to online farms.
You can remove browser data using your browser's site-data controls. Native app data can be removed using the app's save controls, by uninstalling the app where the platform removes app data, or by deleting its application-data folder.
Offline games
When you choose Offline or resume a local save, the simulation and save file stay on your device. Local save files are not uploaded as cloud saves, and we cannot recover them for you.
If the game can reach our service, offline play can still send the analytics and diagnostic snapshots described below. These snapshots are not cloud saves and cannot be used to continue an offline save on another device.
Usage analytics and diagnostics
Our web and native clients can send limited gameplay events such as launch, playtime, menu or settings changes, in-game actions, and achievement unlock IDs. An event can include a generated session or player ID, whether play is offline or online, a short event detail, client platform, retail or demo channel, timestamp, and a two-letter country code supplied by our network provider. We use this information to understand feature use, balance the game, diagnose failures, measure reliability, and protect the service.
The game can also send periodic replay snapshots. A snapshot can include the level, generated session and player IDs, platform and channel, entity positions and validated display names, resources, farm tiles, buildings, plants, weather, season, and other compact game-state fields needed to replay or inspect a farm. Analytics events and replay snapshots are normally deleted after 30 days.
Like most online services, our servers and service providers receive request and connection data such as IP address, user agent or app transport information, requested URL, timestamps, response status, and approximate country. We use it to deliver the service, prevent abuse, investigate errors, and understand aggregate traffic. Operational logs are normally retained for up to 30 days, although security incidents and backups may be kept longer when reasonably necessary.
Online multiplayer
When you create, browse, join, or resume an online farm, the game connects to our server using HTTPS and SignalR. We process the farm name, level, public or private setting, join code, selected character, display name, generated client ID, device credential, connection and session IDs, membership, heartbeat and reconnect status, and recovery snapshots. The server stores a one-way hash of the device credential rather than the device secret itself.
Public farms can appear in the public browser with their farm name, level, player count, and related availability information. Private farms do not appear there and require their code or invite link. A join code is a sharing credential: anyone who receives it may be able to request access, so share it only with people you trust.
Multiplayer simulation runs on the players' devices. Game commands and controlled-character state normally travel directly between players over WebRTC. Our server relays connection-negotiation data and stores the latest recovery checkpoint so a farm can survive coordinator changes and resume after everyone leaves. If a direct connection is unavailable, encrypted gameplay traffic can pass through a TURN relay. WebRTC connection setup can expose network-address information to the peer connection and to the STUN or TURN provider.
Other players in the same farm can see your display name, selected character, movement, actions, and shared farm state. Do not use a real name or include personal information in a player or farm name unless you want other players to see it. Paused online farms and their recovery data normally expire after 90 days of inactivity.
Sharing, QR codes, and screenshots
The game can create a join link or QR code containing the farm's invite address and join code. The QR image is generated for display on your device. Copying, sharing, or showing that code gives it to the people or services you choose.
Screenshots are created on your device. Windows can save them locally, while Apple and web clients can pass them to the operating system or browser share sheet. Froggy Works does not receive a screenshot merely because you take one, but the app or person you share it with will handle it under their own terms.
Achievements and platform services
Windows and some macOS builds can report achievement identifiers to Steam. iPhone, iPad, and Mac App Store builds can report achievement progress to Apple Game Center. Those services associate activity with your platform account and handle it under their own privacy policies. The game sends the achievement identifier or progress needed to publish the unlock.
Service providers
We use infrastructure providers to host, secure, and deliver the service. Cloudflare can provide content delivery, security, approximate country information, STUN, and TURN relay services. Storefront and sharing features can involve Apple, Valve/Steam, your operating system, browser, or an app you select. Their handling of data is governed by their policies:
Cookies
We do not use advertising or cross-site tracking cookies for players. The game uses local storage and similar device storage for the functions described above. Restricted administration tools use a necessary, secure sign-in cookie that is not used for advertising.
Your choices and deletion
You can choose Offline to avoid creating an online farm, choose Private to keep a farm out of the public browser, delete local save slots, and clear the game's browser or app data. You can also avoid entering identifying information in display names.
To ask about data held by our servers or request deletion, email us at the address below. Include the farm code and generated client identifier if available, but do not send your device secret. We may need enough information to verify that the request relates to your data.
Security
We use transport encryption, generated device credentials, access controls, rate limits, validation, and storage limits to protect the service. No system is completely secure, and a shared farm code should not be treated as a password for sensitive information.
Children
The game does not require a Froggy Works account or personal profile. We do not knowingly collect personal information from children beyond the limited service data described in this policy. If you believe a child has provided personal information, contact us so we can review and delete it where appropriate.
Changes
Updates to this policy are posted on this page with a revised date above.