Starforge Defense
Privacy Policy
Last updated: 3 November 2026
1. About this policy
Starforge Defense is a ship-building arcade game provided by IberWolf Studios. This policy describes the current browser preview and Android test builds, including local saves, shared online progression, co-op and ranked play. Earlier installed builds can retain the legacy controls described below. The Google advertising and consent sections apply to Android only; browser advertising and purchases are disabled. The game is intended for people aged 13 and older and is not directed to children under 13. Contact wolf.gamer9k@gmail.com for support or privacy requests. Last updated: 3 November 2026.
2. Local saves and shared progression
The game stores ships, blueprints, module levels, infusion inventory and equipment, salvage, expedition progress, settings and recent expedition reports in app storage on your device. At startup, the current browser preview and Android test builds attempt to connect to the configured online progression service. This can create or authenticate a pseudonymous pilot profile before you enter a multiplayer match. A limited one-time import transfers eligible local campaign ownership, module levels and salvage to that profile; later online collection, wallet and reward changes use the shared hosted records described below. Connected play uses the server-held collection and wallet for that device profile. The browser and Android app use separate device profiles; connecting to the same service does not automatically link their wallets or progression. Collection is shared across online modes for that profile, while expedition progress and preferences remain on that device. Full server checkpoint recovery is not available.
The sign-in credential is kept on your device and used to authenticate the profile over the secure connection; the service stores a hash of it. These versions do not add email-based recovery or cross-device profile merging. Browser storage and Android storage are separate; connecting to the same service does not automatically link profiles on different devices. Real-money purchases are disabled in all of these versions.
Browser saves and access: local saves and the online sign-in credential use the game’s site storage, including localStorage with a browser-managed filesystem fallback. Storage belongs to the game’s site and browser profile. Switching to a different game site, browser, browser profile or device does not automatically transfer those saves or link the hosted profile. Private browsing, storage restrictions or clearing site data can remove or prevent saved data, including the credential needed to access the hosted profile. Clearing browser site storage does not delete the hosted profile. Keep the deletion-only code privately before clearing site data if you want to request hosted deletion later.
The current browser preview and recent Android test builds have no manual save export or import controls. The browser preview maintains an internal local save backup in the same browser storage; it does not recover the hosted-profile credential. Older browser previews and Android test build 5 may still include manual export/import controls. Previously exported files remain where you saved them; this update does not delete them. We do not receive those files automatically, and a local save export does not recover the hosted profile.
Android saves and access: Android test builds keep local expedition progress, preferences and the online sign-in credential in app storage on the device. Recent Android test builds also use app storage for their internal local save backup. That save backup does not recover the hosted-profile credential or provide complete cloud or cross-device recovery. The Android app requests that automatic app-data backup be disabled; device manufacturers may provide their own backup or transfer behavior.
3. Android Google advertising services
The Android test builds described here use Google AdMob demo ad units. These display test creatives rather than revenue-generating ads. An optional rewarded test ad can revive an expedition once, and occasional full-screen test ads appear at natural breaks between waves. Persistent rewarded placements for salvage, materials, ship trials, fabrication refreshes and extra arena entries are unavailable in these test builds; real-money purchases are disabled. Test ads and SDK diagnostics still make network requests to Google. The browser build has advertising and purchases disabled and does not load the Android advertising or consent SDKs.
On Android, the shipped Google Mobile Ads SDK can process IP addresses, approximate location inferred from IP, device or account identifiers where available, app and advertising interactions, and diagnostic/performance information for advertising, analytics and fraud prevention. Test-ad settings do not mean that no information is processed. No separate studio gameplay analytics or crash-reporting service is connected.
The Android test profiles apply under-age-of-consent restrictions to advertising requests, disable personalized-ad profiling through those SDK restrictions and cap ad content at the SDK’s Teen rating. These Android test builds do not ask for or store a birthday or age profile. Adult testers receive the same conservative restrictions. Live advertising, persistent ad rewards, purchases, recovery accounts or other material changes require an updated policy and appropriate configuration before activation.
See Google’s privacy policy, how Google uses information from partner apps and Mobile Ads data disclosure. Google’s documentation describes general SDK practices; the exact information processed depends on the SDK version actually shipped, settings, device, consent and region.
4. Android ads, consent and player choices
The Android test builds described here use Google’s User Messaging Platform to check whether ad requests are permitted. They show any required consent form and provide an Ad privacy options entry in Options in recent builds, or Settings in older Android build 5, when Google requires one. Available options vary by region and request restrictions. You can also manage advertising identifiers through Android and Google settings.
You can decline optional rewarded-ad offers and finish an expedition without reviving. Ad Test Tools in Android test builds can request test creatives or open Google’s ad inspector. They cannot grant persistent ad currency or start checkout.
5. Local ad spacing
The game stores operational visit counts, last-played timestamps and ad-spacing state locally to limit interruptions. On Android, between-round ads use minimum time, wave-spacing and session caps. This is not a studio-uploaded retention or analytics feed. The Android Google advertising SDK performs its own processing as described above. The browser build does not show ads.
6. Online profiles, co-op and ranked play
The browser build and Android test builds connect to IberWolf Studios’ shared progression, PvP and co-op service hosted by Railway, including the startup connection described above. The service receives network connection information, persistent profile/session identifiers, the device-held authentication credential, the chosen pilot alias, selected ship, gameplay commands and match state. It does not ask you to provide an email address, password or birthday to create this pilot profile.
The service stores a pseudonymous profile identifier, the credential hash, pilot alias, owned ships and blueprints, module levels, infusion inventory and equipment, salvage, arena rating and results, tickets, daily mission progress, co-op completion/contribution records and reward-delivery records. These shared records support progression across solo rewards, co-op and ranked play, authenticate players, maintain rankings, and prevent duplicate entries, refunds or reward claims. They persist beyond a single match. Persistent ad-reward placements remain disabled in the Android test builds described here, and browser ads are disabled, as described above.
Your pilot alias and relevant match information are visible to your squad or opponent. Public ranked standings expose the alias, rating, placing and match/win counts, with a pseudonymous profile identifier used by the ranking service. Do not use private information in your alias. The service stores progression on its persistent hosting volume. Railway processes network information to deliver and protect the service; its infrastructure may retain security and operational logs under its own policies.
In the current browser preview, Solo (AI) Practice runs a separate temporary match on the device. Its AI results are not submitted as multiplayer results or used to award persistent online rewards. Multiplayer Practice uses the existing device profile, chosen owned ship and queue/room/match messages through the online service. Practice has no Ranked ticket, rating or persistent payout effects.
The current browser preview and recent Android test builds use IberWolf Studios’ official encrypted WSS services and do not include a server-address setting. You can change your pilot name in Options. Your alias and the public information described above remain visible in online play and rankings. Older clients, including Android test build 5, may still provide a custom-server setting. An independent server operator controls information sent to that server and its retention; contact that operator about deletion. The studio does not receive data sent only to an independent server.
7. Support and website visits
If you email wolf.gamer9k@gmail.com, we receive your address, message and any attachments you choose to send. We use them to answer enquiries, investigate problems and respond to privacy requests. Support messages, screenshots and exported save files are sent only when you choose to send them; online progression and match records are processed separately as described above. Do not include passwords or payment details.
The studio uses Gmail for support and Railway to host its website. Hosting infrastructure may process IP addresses, browser details and request logs to deliver and protect website pages. Opening an in-game website link contacts that site. See our website privacy information. Service providers may process information outside your country under their own terms and safeguards.
8. Retention and deletion
Delete your shared online profile: in the current browser preview or a recent Android test build, open Options → ONLINE PROFILE / DELETE. Earlier browser previews kept this control under Online / Co-op. Android test build 5 uses Online / Co-op → RAID PROFILE / DELETE. You can also visit our Starforge Defense profile deletion page. Android test build 5 uses the older “Raid profile” label; these controls delete the shared online profile’s collection, wallet and progression across online modes. The page accepts the deletion-only code shown in the game. Keep that code privately if you want to delete after uninstalling. It cannot sign in to your profile. If you no longer have the code, request help or deletion by contacting wolf.gamer9k@gmail.com; we may need to verify profile ownership. You do not need to reinstall to contact support.
The service retains hosted profile and progression records until deletion. A successful automatic deletion removes the active profile, credential hash and stored progression, its ad-reward offers and associated ad transactions, and reward records whose contents identify that profile. It also removes that profile and its matching reward records from the retained legacy raid ledger and its legacy backup. Pending duels involving the profile are cancelled. Some pseudonymous match-participation and in-game receipt references remain in operational records after profile deletion. Any separate server backups are outside this automatic deletion operation. Contact support for retention or further deletion requests concerning those records or backups; this control is not a promise that every copy or record has been erased.
Deleting the hosted profile does not clear local campaign saves, settings or exported files. Clear Android app storage to remove local progress and preferences; exported backup files must be removed separately. For the browser version, clear the game’s stored site data in that browser profile to remove local saves and credentials; this can lose access to a hosted profile. Keep the deletion-only code privately before doing so if you want to request hosted deletion later. Uninstalling or clearing local storage alone does not request hosted-profile deletion. Reconnecting without an existing credential can create a new profile and import eligible local progression again.
Infrastructure security logs follow Railway’s retention practices. Google controls its separate advertising records. Independent server operators control profiles created through older clients that use their servers. We keep support correspondence only as needed to resolve enquiries, investigate outstanding issues and meet applicable legal obligations. Request access, correction or deletion of information you sent to the studio by contacting wolf.gamer9k@gmail.com. Rights and exceptions depend on applicable law.
9. Security and changes
Local saves rely on device and app-storage protections. The app does not ask for contacts, camera, microphone, real name or precise location. On Android, Google documents TLS encryption for Mobile Ads SDK traffic. The browser and Android versions use WSS for the configured online service and HTTPS for the deletion website. Do not put private information in your pilot name, and keep your deletion-only code private. Independent server operators control profiles created through older clients that use their servers. No storage or transmission system is completely secure.
If a parent or guardian believes a child under 13 has sent information to the studio, contact wolf.gamer9k@gmail.com. We will update this page when information practices change and provide additional notice or choices where required. The policy date appears above.