Privacy Policy
Last updated: October 11, 2026
Overview
BitingGoat Software ("we", "our") is committed to protecting your privacy. This policy describes how our applications and website handle information.
LANSpeed
LANSpeed is a local area network speed testing tool. It operates entirely on your local network and does not transmit any data to external servers.
- We do not collect personal information.
- We do not transmit data to the internet.
- We do not use analytics or tracking.
- Test results (speed, latency, timestamps) are stored locally on your device only, in a SQLite database.
- Network traffic generated by LANSpeed stays entirely within your local network.
- You can delete all stored history at any time from within the app.
Inkwright
Inkwright (灵犀执笔), published on the Microsoft Store, is a local-first, offline-capable writing application for novelists. Your work stays on your own device by default.
- No account or sign-up is required. We do not collect personal information.
- We do not use analytics, telemetry, tracking, or advertising. The app does not phone home and contains no built-in updater.
- Your manuscripts and story-bible data are stored locally on your device only, as files in per-project folders (a SQLite database). You can move, back up, or delete them at any time.
- Local AI (default): the bundled offline AI model runs entirely on your computer. Text you write or generate is processed on-device and is not transmitted anywhere.
- Optional cloud AI: only if you choose to enable and configure a third-party OpenAI-compatible provider (for example, DeepSeek), the specific text you ask the app to process is sent to that provider's API to return a result, subject to that provider's own privacy policy. This is disabled unless you turn it on. Your API key is stored locally on your device (encrypted with Windows DPAPI on Windows) and is never sent to us.
- Optional model download: if you download a local AI model from within the app, the model file is fetched from a third-party model host (such as Hugging Face or ModelScope), which receives standard request metadata such as your IP address.
- We (BitingGoat Software) do not receive, store, or have access to your documents or any content you create.
Deskloom
Deskloom is a local-first Windows desktop-customization application. It coordinates wallpaper, taskbar appearance, desktop widgets and groups, and cursor themes into reusable scenes. Desktop customization needs no BitingGoat Software account or internet connection. Deskloom does not replace classic Windows desktop-system icons. The details below describe the current application implementation; optional network actions are identified separately.
- Scenes, settings, layouts, Quick Note and Checklist content, imported assets, Windows-integration permissions, and recovery state are stored in local app data within your Windows user profile. Frequent launch history and optional diagnostic records also stay on your device.
- Deskloom does not include advertising, behavioral analytics, global application-use monitoring, cloud sync, an online gallery, or a BitingGoat Software telemetry or diagnostic-upload service. This website's consented Google Analytics does not run in the Deskloom app.
- Images, videos, and self-contained HTML wallpaper that you choose to import are validated and copied into app-managed local storage. Image slideshows also use locally imported images; their order, interval and transition settings stay on your device, without loading an online gallery. Exported theme packages include the imported slideshow images they use, so inspect them before sharing. HTML wallpaper is blocked from network access, downloads, and external navigation.
- To organize the desktop, Deskloom locally reads item type, display name, shortcut target and product metadata. Automatic organization does not scan file contents, move, rename, delete, or upload the underlying desktop files. If you choose Rename, Delete or another file action from an item's Windows context menu, Windows acts on the original item; Remove from group changes only its Deskloom membership. Restoring Deskloom appearance does not undo your file actions.
- Automatically collect new desktop applications is enabled by default, operates only while authorized organized groups are visible, and can be disabled. It reuses local desktop filesystem notifications to add newly appearing, recognized application icons to groups; it does not scan installers or monitor global processes. The first complete inventory establishes a baseline rather than collecting an existing backlog. Bounded item identities and local source paths remain only in the current running session's memory, not persistent installation history, and are not uploaded. Disabling collection or desktop organization resets the observation baseline.
- Desktop classification uses a bundled catalog and local rules; the current app does not run a local AI model or send desktop items to cloud AI. Imported assets are validated locally and are not uploaded for cloud malware scanning.
- The Frequent group adapts only to applications that you successfully open from a Deskloom desktop-group surface. Deskloom stores at most 256 local records containing an opaque application identity, a decaying frequency weight, and the last successful Deskloom launch time. It does not store the application name, path, URL, command line, document, or failed launch; observe launches made outside Deskloom; read Windows UserAssist; or upload this history. You can reset Frequent history from the Desktop page while keeping manual pins, removals, and the current projection. Clearing history does not move items by itself; adaptation resumes after a later successful Deskloom launch.
- Theme sharing currently uses local .deskloom files that you choose to import or export, with no built-in community download gallery, Workshop, or DLC download service. An export contains scene names, appearance and layout settings, and the imported wallpaper assets used by those scenes. It excludes desktop applications or group membership, launch history, original filenames or paths, hardware display IDs, disk selections, note or checklist text, and weather cities or coordinates. Weather network permission is reset to off on both import and export. Review scene names and wallpaper content before sharing a package yourself; Deskloom does not upload theme packages automatically.
- System, battery and local-disk capacity readings used by widgets are processed locally and are not transmitted to BitingGoat Software. The Network widget reads local adapter byte counters; it does not send test traffic or inspect packet contents. Disk choices store drive letters, not file contents, and the disk widget does not query network shares. Quick Notes and Checklists keep their content locally; Calendar is an offline month view without calendar accounts or event synchronization.
- Now Playing reads the current Windows media session's title, artist and supported playback controls locally while a visible widget needs them. It does not read audio, save playback history or send media metadata to a service. Playback controls act only on the session shown when you select them.
- Weather is disabled by default. Only after you explicitly allow weather requests does the native client request forecasts from MET Norway (api.met.no), sending the latitude and longitude you configure, rounded to at most four decimal places. The service also receives your request's IP address and a header identifying Deskloom. The city label is stored locally and is not included in forecast requests. City presets are selected locally, or you can enter custom coordinates; Deskloom does not use GPS, detect your location automatically, or search for cities online. Forecasts are cached in memory across widgets; within a running app session, requests for the same location are at least ten minutes apart and provider expiry/rate-limit headers can extend that interval. Turning the option off stops future requests from that widget; another enabled Weather widget may still use the service. MET Norway's privacy statement applies to its service logs. The bundled control-center and HTML wallpapers remain blocked from network access.
- When an Audio Spectrum widget is active, Deskloom briefly processes the Windows system playback mix in memory to calculate frequency bands. It does not access the microphone, save audio or playback history, identify content, or transmit audio to a service. Capture stops when no visible Audio Spectrum widget needs it; its temporary buffers are cleared on release.
- Quick controls changes volume, mute and supported display brightness only when you operate the control. These settings stay in Windows and are not uploaded. Exiting Deskloom or restoring a scene does not undo these changes.
- You can preview and save a classification diagnostic report for a desktop item you select. Its category and rule details may reveal which app you use. Raw application identity values are excluded by default; you may choose to include them for more detail. Inspect the preview before saving or sharing it. Reports are saved locally and are never uploaded automatically.
- Deskloom does not create its own diagnostic journal or detailed diagnostic log unless you explicitly enable Support diagnostics. The choice is revocable, stops automatically after at most 24 hours, and is applied through a normal application restart so Deskloom and its desktop helpers share the same diagnostic scope. Customer Release builds never include Deskloom's free-text development logger; an opted-in Release session records only a small, size-limited set of fixed technical events such as process role, app and Windows version, operation phase, stable error code, HRESULT/exit code, and bounded method-only stack information. It excludes note text, imported contents, desktop or group item names, custom scene names, private paths, clipboard contents, account data, tokens, and network identifiers.
- Support diagnostics can show that Deskloom did not close normally and help diagnose restore or scene failures. Nothing is uploaded automatically. From Privacy & local data in Settings, you can stop future recording, export a sanitized ZIP from existing records and choose whether to share it, or clear completed failure records. If enabled, Deskloom keeps at most eight diagnostic sessions and approximately 8 MiB of session data, with a 1 MiB limit per session and 256 KiB per process journal, plus a small bounded set of control markers. Stopping diagnostics does not delete existing records; you remain in control of exporting or clearing them.
- For a Microsoft Store installation, Windows and Microsoft may process crash and hang diagnostic data according to your Windows diagnostic-data settings and Microsoft's privacy terms. BitingGoat Software may view eligible crash or hang reports and related diagnostic details in Partner Center. This Microsoft Store Health channel is separate from Deskloom's local incident journal; Deskloom does not send the local journal to Microsoft or BitingGoat Software automatically.
- Settings offers a manual link to Windows diagnostic settings. Opening it does not enable Optional diagnostic data, which is a Windows-wide choice governed by Microsoft. It does not authorize Deskloom's local Support diagnostics or upload any local records. Version 1.0.28 does not automatically ask users to change Windows diagnostics.
- Website, privacy-policy, Reddit community, weather source/license, and Cosmic Game Board story links open your system browser only after you select them. Feedback opens the separately operated board at https://feedback.bitinggoatsoft.win/; direct support opens your mail application. Deskloom does not embed community or feedback content, contact the feedback board in the background, or attach diagnostics or user files automatically. If you choose to post or contact support, you supply that content directly. Those sites' own privacy disclosures apply when you visit them; visits to our website are covered by the website section below.
- Obtaining Deskloom through Microsoft Store is handled by Microsoft under its Store terms and privacy statement. The current Deskloom app has no sign-in, supporter account, in-app purchase, or BitingGoat Software online license-verification service.
- Built-in wallpaper artwork and control-center scripts and assets are bundled with the app, rather than fetched from third-party asset CDNs. Settings → About → Third-party licenses provides an offline reader for the bundled component licenses without contacting their suppliers.
- You can remove imported assets, scenes, notes and checklists, layouts, Frequent history, and completed diagnostic records through Deskloom. Clear failure records only handles diagnostics, not other application data. Deskloom's restore action and true Exit request restoration of Windows appearance changes owned by the current Deskloom session. If Windows prevents immediate restoration, Deskloom preserves recovery state and attempts recovery on the next launch.
Microsoft's handling of Windows and Store diagnostic data is described in the Microsoft Privacy Statement. Questions about Deskloom privacy can be sent to the contact address listed on this privacy-policy page.
LumaShout
LumaShout is a local-first animated text-display application for Windows, macOS, iPhone, and iPad. Creating, saving, and displaying signs works offline on one device and does not require an account.
- We do not collect personal information, sign content, or usage data.
- We do not use analytics, telemetry, tracking, advertising, or cookies in the app.
- Text signs and their display settings are stored locally on your device only in the app's SQLite database.
- Language and appearance preferences are stored locally on your device.
- The app does not upload your signs or transmit them to BitingGoat Software or any third party.
- Saved signs can be deleted from the Library inside the app.
- While display mode is active, the app may ask the operating system to keep the screen awake. This is a local device function and does not send data.
- When you choose to purchase or restore the Pro Effects Pack, the app connects to Microsoft Store or the Apple App Store. The applicable store processes purchase and transaction data under its own privacy policy; BitingGoat Software does not receive your payment details.
- The current Windows, macOS, iPhone, and iPad releases do not include remote-control sessions, cloud storage, image import, camera access, microphone access, or location access.
RallyTone
RallyTone is an account-free, LAN-first voice and text chat application for game parties. Native clients do not require an internet connection or a BitingGoat Software account to create or join a local party. Optional Store operations and the publicly hosted Web client are described separately.
- RallyTone requests microphone access for party voice chat and the local microphone test.
- Microphone audio is captured and processed on your device, then transmitted over encrypted QUIC connections to the party host and eligible participants. LAN parties remain on the local network; if you explicitly connect by IP to a self-hosted server, traffic travels to that server. Voice audio is never recorded or persisted by RallyTone.
- Party control connections use certificate-pinned TLS 1.3. Voice packets are encrypted in transit and are routed only to eligible participants in the speaker's current channel. This is client-to-host transport encryption, not independent end-to-end verification of participant identities.
- Party text chat is authoritative to the local party host and ephemeral. At most 64 recent messages are held in memory, and the history is cleared when the party ends. Messages are not written to disk or sent to a BitingGoat Software server; other participants may still copy content or take screenshots themselves.
- Your nickname, avatar selection, frame and badge preferences, language, appearance, audio configuration, and shortcuts are stored locally on your device. You can clear these settings from within the app. Compatible parties share your effective nickname, avatar, frame and selected decorative badge with members. Cosmetics are not purchase receipts and contain no Store account information.
- Built-in avatars use a small avatar ID. If you explicitly import a custom avatar in a native app, it is cropped and re-encoded locally to remove original metadata; only the processed image is saved in local app data, not the original selected file. Compatible parties receive the processed image through authenticated transfers. It is not uploaded to a BitingGoat Software cloud service.
- Compatible native clients can send chat attachments only after an explicit Send action. The host holds files in bounded memory until they expire or the party ends: desktop Hosts retain them for 30 minutes, and standalone Servers default to 30 minutes with an operator-configurable lifetime. Sanitized image previews do not open the original. Saving an original requires an explicit Save action. RallyTone never automatically opens, executes, or extracts received files, or sends files or hashes to a cloud scanning service. Copies you explicitly save outside the party are not automatically deleted when it ends.
- Desktop-party passwords and session keys are kept only in memory and are discarded when the party ends. A standalone server operator may choose to persist desired party settings, including its configured password, in a private server configuration file. Passwords are transmitted only inside the pinned encrypted connection.
- Active-party discovery uses mDNS to advertise availability, party name, participant count, optional game label and certificate fingerprint to devices on the same local network. This is unauthenticated local discovery, not a private broadcast, and is not sent to a BitingGoat Software server.
- When you save a direct-IP server, RallyTone stores that endpoint and its certificate fingerprint locally so later identity changes can be blocked. Compare the fingerprint with its operator before first trusting it. It never stores the party password in that trust file.
- The optional standalone RallyTone Server beta runs on a Linux host or NAS controlled by its operator. Active party state, chat, and relayed voice remain in memory. Its private configuration volume may persist the server identity and operator-selected settings; the optional token-protected management page is intended only for loopback or a trusted private network.
- The standalone server does not create its own log files. A container supervisor may retain bounded startup, shutdown, or diagnostic output according to the operator's configuration.
- Release builds do not initialize an automatic debug logger. Optional Support diagnostics are off by default; enabling them creates an allowlisted local incident journal for up to 24 hours, excluding chat, audio, nicknames, paths, addresses, passwords and tokens. Stopping ends further writes, but existing records remain until cleared. You may explicitly export a sanitized ZIP and choose whether to share it; feedback does not attach it automatically. Clearing diagnostics does not clear your nickname, settings or saved servers.
- On supported Store distribution channels, optional Supporter Pack product queries, purchases, restoration and license checks use Microsoft Store or Apple StoreKit. Native clients also refresh Store status in the background at startup and after license changes; these operations may contact the relevant Store, but are not required for party communication. The Store handles account, payment and transaction data under its own privacy disclosures. The app uses product and entitlement status, does not upload payment details, Store accounts or purchase receipts to a BitingGoat Software service, and creates no supporter account database. Linux, iOS and Web clients do not provide this purchase entry.
- Notification sounds are bundled, output-only local playback. They do not record the microphone or transmit audio to a party. Resources are not loaded from online image, font or script CDNs.
- Privacy, support and feedback links open your system browser or mail application only after you select them. Feedback opens https://feedback.bitinggoatsoft.win/ without automatically uploading user files or diagnostics; content you submit is supplied by you and covered by that service's privacy disclosures.
- RallyTone Web is a browser/PWA client for a separately enabled LAN Server endpoint. It stores preferences and confirmed Server identities in your browser. Its service worker caches only the static app shell, not invitations, passwords, chat, or voice. Background tabs stop microphone audio. The browser client does not host or discover LAN parties automatically, import custom-avatar files, operate attachments, or provide Store purchasing.
- Loading the publicly hosted Web client contacts our Cloudflare-backed website; invitations may put the Server endpoint and certificate digest in the requested URL. These are not passwords, but the hosting provider receives normal network/request information. Verify invitations before using them, avoid sharing them publicly, and never put party passwords or administrator tokens in URLs. Party voice and chat connect directly to the Server, not through the website host.
- RallyTone does not include automatic crash uploads, usage analytics, advertising, or tracking. Separate operating-system and Store diagnostics follow their own settings and privacy disclosures, not the local Support diagnostics switch. The website disclosures below do not describe telemetry in the native app.
- For Store data handling, see the Microsoft Privacy Statement and Apple App Store privacy disclosure.
Website (bitinggoatsoft.win)
- We load optional Google Analytics 4 (G-M0ZZNNLGBB) only after you accept analytics, and only for this website. Before acceptance or after rejection, we load no Google analytics scripts and send no analytics requests to Google. Rejection does not affect browsing or downloads.
- We manually measure views of a fixed list of public pages (page_view) and store download link clicks (store_download_click, with fixed product, destination store, and button location labels). We do not replay views or clicks from before consent. Enhanced Measurement, advertising features, ad personalization, and Google signals are disabled.
- Page URLs sent to GA4 contain only fixed public paths, without query strings or fragments. Referrers contain only the referring site's origin. We do not add names, email addresses, user content, private paths, or other personal information to analytics events.
- After consent, Google Analytics uses first-party _ga and _ga_* cookies to identify browsers and sessions and may process browser and device information. Google also receives network information such as your IP address when receiving requests, so this analytics data is not guaranteed to be anonymous.
- We save your analytics choice and language preference in this browser's local storage. Use “Analytics settings” in any page's footer to accept or reject analytics. Withdrawal immediately disables analytics, clears accessible GA cookies for this website, and reloads the page. If the browser cannot save your withdrawal, the current page stays disabled without reloading.
- Store links open the respective third-party store; direct downloads are served by our CDN. Those services may process network request information under their own privacy policies.
Third-Party Services
Our website is served via Cloudflare, which may process request metadata (IP address, headers) as part of its CDN and DDoS protection service. Please refer to Cloudflare’s Privacy Policy for details.
Cloudflare may also add a Web Analytics performance beacon as page responses pass through its edge network; that script is not bundled in this website source. When present, it sends page and referrer information and browser performance measurements, such as load times, to Cloudflare. It is separate from Google Analytics and is not controlled by this website’s GA4 consent buttons. Cloudflare states that the beacon does not use cookies or browser storage; this does not mean website requests produce no data. See Cloudflare’s beacon explanation.
Google provides the consented Google Analytics service. See Google’s Privacy Policy.
Children's Privacy
Our apps and website are not directed at children under 13. We do not knowingly collect any information from children.
Changes to This Policy
We may update this policy from time to time. The "Last updated" date at the top of this page reflects when changes were last made.
Contact
If you have questions about this policy, please contact us at [email protected].