Kipby is our desktop launcher, previously called recompnode. Its existing Microsoft Partner Center registration remains under RecompList. This notice covers desktop previews 0.1.0, 0.2.0, 0.3.0 0.5.x, 0.6.x, 0.8.x, 0.9.x, 0.10.x, 0.11.x, 0.12.x, 0.13.x, 0.14.x and 0.15.x. Updated 4 November 2026.
The records on your computer.
When you add an executable, Kipby records its game ID, title, full path and SHA-256 fingerprint. Version 0.2 also saves launch arguments, working folders, version labels, favourites, wishlist, hidden games, collections, notes, backlog status and artwork you select. Full paths and notes can contain personal information. Selected executables and managed engine files are read locally to calculate and recheck fingerprints.
Version 0.4 also stores your personal tags, smart-collection rules, release read markers, download speed limit and local download time window. Bulk library edits update these local records. The release feed uses the bundled snapshot and release cache; weekly playtime insights are calculated from retained completed sessions. Tags, notes, collection rules and play history are not sent to GitHub. Time windows and queued transfers only run while the application and computer remain running; they do not install a background service.
For processes started by Kipby, version 0.2 records launch count, last-played time, tracked duration and up to 30 recent sessions per game, including timestamps and an exit code when available. Tracking stops when Kipby closes. A tracked process is not proof of active gameplay. No other running applications are scanned.
Library, preference, release-cache and download-queue records are stored in the application-data directory for com.recompulist.launcher. Selected artwork is copied into its local covers folder. Imported game files remain in their original folders. Managed engine versions, partial downloads and retained versions use separate local folders.
Public community charts.
Version 0.15 reads public aggregate charts from the Kipby service without a profile, community token or library upload. A chart records website release interest or observed upstream publication dates. It does not measure your native installs or playtime. The app keeps up to 12 dated public chart documents in a local cache limited to 4 MB. Offline and connection-fallback views identify their original capture time. Chart filters, rank calculations and paging run locally against those public documents. Sharing a chart exposes its public snapshot, filters and page, rather than your library or account.
Preparing original game data.
Version 0.3 can run the bundled, fingerprint-checked OpenGOAL extractor against a PS2 ISO you choose through a native file picker. It reads that file locally and creates private game data in the managed installation folder. Your ISO is not uploaded. Preparation is tracked separately from playtime, can be cancelled, and stops when Kipby closes. A local preparation log is limited to 2 MB and may contain the selected file path or project diagnostics.
The separately labelled BLiNX 2 build wizard is a project program you can choose to launch. Its own setup process may download build tools and create a private game in folders you select. Those generated files are not owned or automatically removed by recompnode. Consult that project’s instructions and data practices.
Optional GitHub connections.
Version 0.1 makes no release-check or download requests. Versions 0.2, 0.3 and 0.4 start in offline mode. Enabling online features allows requests to the bundled projects’ official GitHub repositories for reviewed stable, prerelease or nightly release metadata and supported Windows engine packages. Checks happen when you request them, or on startup if you separately enable that option. Downloads start only after your install action. Turning online features off pauses managed downloads.
GitHub and its release-content hosts receive your IP address, request time, requested repository or release asset, and the launcher’s versioned user-agent string. Your local library, notes, executable paths, executable contents and original game files are not uploaded. GitHub handles its connection records under its own privacy practices. Cached release notes and download records remain local. Version 0.3 also bundles a dated, reviewed release snapshot so supported packages can be browsed before any network request. Library update checks refresh this information only when online features are enabled.
Discovery and notification history.
Version 0.8 stores your wishlist priority, wishlist-added dates, ignored projects, explicit follows, discovery preferences, viewed-project history, queue position and home-shelf order locally. Recommendations use this local information; there is no cloud recommendation profile. Checking followed projects contacts the same reviewed GitHub repositories described above. The local notifications-v1.json file keeps up to 200 native download outcomes, checked-release notices and achievement alerts, together with read state, category preferences and deduplication identifiers. Existing activity is baselined on first use. No notification history, discovery choices or wishlist priorities are uploaded.
Accounts and diagnostics.
Version 0.5 adds an optional cloud collection, using the website’s Clerk account in your browser. A one-time code links the launcher for up to eight hours; its scoped credential stays in memory and clears on exit. The collection service stores your selected achievement IDs and completion times, card quantities, earned badges, a public collector code, trading preference and offer history. Version 0.6 automatically reads supported local save formats every five seconds while the app is open. You can choose a game-specific save folder. Readers never modify saves. Detected unlocks and their detection times, adapter ID and adapter version are recorded locally with a SHA-256 digest. When connected and online, game/achievement identifiers and adapter metadata sync automatically; save contents, hashes and paths are not uploaded. Packs, crafting and trades send only the relevant game/card identifiers, quantities and collector codes. Trading starts off. Disconnect revokes the current launcher session. No original game files, executable paths, notes, play history or saves are uploaded. Earlier self-reported claims are archived and do not count as automatic unlocks. Saved progress is not an anti-cheat or server attestation. The desktop app has no advertising or application analytics. Catalogue records and artwork are bundled. Windows and Microsoft Edge WebView2 provide the operating system and display runtime; their diagnostics, updates and privacy settings are separate from recompnode.
Optional community profiles.
Version 0.9 adds account profiles. Profiles start private. If you publish, your display name, unique handle, avatar, bio and self-declared creator label become publicly visible and searchable. Your email and internal account ID are not included. Profile text and visibility are stored in the cloud. Avatars you choose are uploaded, decoded, cropped to a 256-pixel square, stripped of metadata and stored in private cloud storage; the image proxy checks profile visibility on every request. Changing a profile back to private prevents new anonymous reads, but cannot remove copies someone already saved.
Desktop profile access requires an explicitly approved one-time code from the People page. Existing collection-only connections do not gain profile permissions. This connection can read and edit your profile, change its avatar and send private profile reports; it does not grant messaging or marketplace permissions. The credential stays in memory for up to eight hours and clears on exit. Disconnect through Collectibles to revoke the current session. Report reasons are visible only to moderators; moderation decisions and their audit records are stored in the cloud. A creator label does not verify selling rights. To request removal of cloud profile data, use the contact form linked below.
Community discussions.
Version 0.10 adds public project discussions, questions and bug reports. Posting requires a public, active profile. The service stores post text, project, type, optional engine version and platform, timestamps and edit revisions. Replies and quoted excerpts are public. Making your profile private hides its name, handle and avatar from new public discussion responses; it does not remove posted text or quotations that other members already made.
Following and read markers are private to your account. Opening a page marks its loaded replies as read. Private reports include the selected content and your reason; only authorised moderators can see the report queue. Moderation actions and their reasons are audited. Deleting your post removes its text, while removed-reply markers and moderation records can remain. Content and account records are retained until deleted or a removal request is processed; contact us using the link below for account-data requests.
Desktop discussion access requires a new, explicit community permission code from Discussions. Old collection and profile connections are not upgraded. The new code includes collection, profile and discussion access, lasts up to eight hours in memory, and can be revoked by disconnecting the app. It grants no direct-message, marketplace or payment permissions. Discussion search, posting and visible activity checks contact Kipby’s cloud service; your IP address and ordinary hosting request logs can be processed by the hosting provider. Local library records, game files and saves are not attached.
Private friends and requests.
Version 0.11 adds an account-private friends list, incoming and sent requests, blocks and contact reports. Sending a request deliberately shares your contact name and handle with that recipient; accepting shares the recipient’s contact identity in return. Private full-profile pages, bios and avatars remain private. A reciprocal invitation does not automatically accept. The service stores the two participants, request direction, acceptance state, timestamps, revisions and request identifiers used to recover interrupted actions.
Blocking removes the friendship and pending requests and stops new friend requests between those accounts. Unblocking does not restore them. Your blocked list keeps the name and handle known when you blocked a member so you can recognise the record if their profile later becomes private. Current private identity changes are not exposed through that blocked record. Friends lists, requests, block lists and request receipts are visible only to the relevant account or participants. Contact reports, their reasons and moderation audit records are available to authorised moderators. Removing a connection does not erase a previously submitted report or its action receipt.
Desktop Friends access requires a new, explicitly approved code from the Friends page. Older collection, profile and discussion credentials are not upgraded. The current grant also includes those existing features, lasts up to eight hours in memory and is revoked by disconnecting the app. It does not include private messaging or commerce access. Contact lookups, selected profile links and actions contact Kipby’s cloud service and may appear in ordinary hosting request records; local game files, paths, saves and play history are not attached. Use the contact link below for account-data removal requests.
Private conversations.
Version 0.12 adds optional private messages in the browser and launcher. Kipby stores conversation participants, message text, optional catalogue project context, timestamps, delivery/read positions and account-owned request receipts in its cloud database. Only participants can read a conversation through the app. Your inbox can be closed, open to accepted friends, or open to anyone who can find your profile. The current preference applies to existing conversations too. Removing a friendship stops further messages to a friends-only inbox; existing history remains available to its participants.
Starting or replying to a conversation deliberately shares your contact name and handle with that member. Your private bio and avatar remain private. Blocking stops new messages and requests in both directions, preserves existing participant history, and masks later private identity changes using the known contact name saved when you blocked them. Unblocking removes only your current block, restores no friendship, and does not override another member’s inbox preferences or their block.
Sent means the server saved the message. Delivered requires the other participant’s client to acknowledge receiving it. Read requires an acknowledgement from their visible, focused conversation. Background polling alone does not mark a message read, and no online or typing status is inferred. A private report shares only the selected message, its project context and timestamp, and your reason with authorised moderators. Their review queue cannot browse unrelated private history. Review decisions are recorded in an audit trail.
Desktop Messages access requires a newly approved code which explicitly permits reading and sending private messages, delivery/read acknowledgements, contact-block management and selected-message reports. Older collection, profile, discussion and Friends grants are not upgraded. The new connection also includes those existing features, lasts up to eight hours in memory and is revoked by disconnecting. Disconnecting does not erase stored history. Unsent drafts remain in the current window’s memory; navigation and close guards protect them while the app is open. They are not included in library backups. No local game file, save, executable path, note or play history is attached automatically. Use the contact link below for account-data removal requests.
Creator storefronts and teams.
Version 0.13 adds optional creator workspaces, reviewed project associations, storefronts, team invitations and creator updates. Workspaces begin privately. Saving keeps a draft with its team; submitting shares that exact revision and its selected branding with authorised reviewers. Approval publishes it using your explicit consent. Your personal profile can stay private while a separately approved storefront is public. Project-control review is separate from selling or distribution rights. Payments, seller payouts and VIP billing are not configured.
Team creation and invitation acceptance deliberately share your contact name and handle privately with current and future members. Editors can manage drafts, project claims, branding and updates. The owner controls invitations, removal and ownership requests. A transfer needs the recipient’s acceptance; it hides publication and returns existing project-control claims for review. Public team credit needs a separate choice and an active public personal profile. Removing that credit, leaving the team or changing your personal profile to private stops new public credit responses. It does not erase copies already seen.
Chosen logos and banners are uploaded, decoded, cropped and stripped of metadata. Logos become 256-pixel squares and banners become 1200 by 300 pixels. Private cloud storage keeps their processed bytes; source images and local file paths are not retained by the upload service. Members can preview their ready assets. Anonymous reads require a current approved public-page reference. Reviewers can access branding only through a selected submitted page or report. Unused images can be removed after current draft, publication, review and open-report references are cleared. Unpublishing hides new public reads; earlier downloaded copies cannot be recalled.
The service stores draft and publication revisions, project-control evidence you submit, review decisions, roles, invitations, accepted transfers, follows, publication order, read positions and account-owned action receipts. Follows are private to your account. An update edit stays private until explicitly published. Feed read positions advance only for actual fetched updates acknowledged by the client; background polling alone is not a read acknowledgement. Reports share the selected public snapshot and your reason with authorised moderators. Moderation does not grant general access to unrelated private drafts or team rosters. Revision and audit records can remain after withdrawal or archiving; use the contact link below for account-data removal requests.
Desktop Creator workspace access requires a newly approved code that explicitly includes creator permissions. Older grants are not expanded. The connection also includes the collection, profile, discussions and Friends permissions shown in its consent screen; private Messages are a separate optional choice. It replaces the current launcher connection, stays in memory for up to eight hours and can be revoked by disconnecting. Unsaved drafts and original requests used to recover interrupted actions remain only in the current window’s memory. Local game data, saves, executable paths and play history are not attached.
Community curator guides.
Version 0.14 adds optional curator pages within individual or team workspaces. Recommendations, verdicts, testing statements, affiliations, languages and ordered lists are saved as private revisions until separately submitted and approved. Curator publication records the consenting owner; an ownership change hides the old consent. Curator profile credits require their own explicit choice and a public active profile, separate from Creator-page credits. Recommendations grant no project control, game ownership, licence or review copy.
Curator follows, read positions and selected-content reports are stored with your account. The feed and discovery shelf use actual published recommendations from your follows. Local play history, library contents, saves and executable paths are not uploaded to rank them. A visible, focused feed entry or explicit mark-read action can advance its read marker; a discovery excerpt does not. Reports share only the selected public revision and your reason with authorised staff. Revision, consent and moderation records can remain after withdrawal.
Desktop Curator access requires an explicitly approved new code. Older Creator and Message grants retain their permissions. The new Curator consent includes the workspace, collection, profile, discussion and Friends permissions listed on its screen; private Messages are separately optional. Branding reuses the processed private image library, with references protected across creator and curator drafts, publication and selected open reports. Unsaved drafts and interrupted-action recovery stay in the current window.
Backups and links.
Exporting a library creates a file at the location you choose containing executable paths and fingerprints, notes, collections, preferences and play history. Game files and custom artwork are not included. Treat that file as private. Merging a backup keeps existing records and checks executable fingerprints before adding shortcuts; it does not restore authority to delete managed files.
Developer-documentation and privacy links open external websites in your browser. Their privacy practices then apply. The launcher does not attach your library or file paths to these links. Games you launch are separate programs with their own network access and data practices. A fingerprint check does not assess their privacy behaviour.
Removing local data.
Removing a library shortcut keeps game files, notes and history. Uninstalling a managed engine removes unchanged files recorded by the installer while preserving unknown or modified files and saves. Retained version folders and copies created by your own backup tools can still contain records or game data.
To remove all desktop records, close Kipby, open its application-data folder through Settings & storage before closing, and remove the library, preferences, release-cache, download-queue, automatic-progress-v1.json, notifications-v1.json and covers files you no longer need. Keep a backup first if you want to preserve them. Review managed game folders separately so you do not lose saves or original game data. Your backup or sync tools control any additional copies.
The website is separate.
The Kipby website has its own account, submission, community and Test Lab features. Information you choose to submit there is outside this desktop library. The browser preview of the desktop interface stores its trial shelves, notes and display settings in that browser’s local storage; clearing that site’s browser data removes them.
Contact.
For questions about local data, use the Kipby contact form. Include the app version and share only the information you want included in your support request.