Privacy Policy

Last updated: November 13, 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 Windows desktop-customization application coordinating wallpaper, taskbar appearance, desktop widgets and groups, and cursor themes into reusable scenes. Basic customization works offline without a BitingGoat Software account. Cloud-assisted desktop icon grouping is now available as an optional feature requiring separate consent and Microsoft sign-in. Deskloom does not replace classic Windows desktop-system icons.

  • 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.
  • Display settings may retain a monitor manufacturer, product code and usable EDID serial number locally to recognize a previously configured screen after its connection changes. Missing or ambiguous identity requires explicit reassociation, not a guess by screen name or resolution. This evidence is not sent to a service or included in logs, crash summaries, diagnostic exports or shared theme packages.
  • Deskloom has no advertising, behavioral analytics, global application-use monitoring, cloud sync or community uploads. Optional cloud organization, official scene downloads and voluntary failure-summary submissions have separate purposes and controls; diagnostics are not uploaded automatically. This website's consent-based Google Analytics does not run in the Deskloom app.
  • When you enter Scenes, including when Deskloom launches directly to that page, the native client automatically requests the public curated theme catalog from themes.bitinggoatsoft.win, hosted on Cloudflare. Bounded, paginated metadata requests do not block local scenes; scrolling or Load more can request further pages. Scene cards approaching the viewport may also automatically fetch size-limited preview images from the same service, verified and cached locally. A separate explicit download action retrieves a complete bundle. No account is required, and no desktop evidence, file contents or Microsoft token is sent. Cloudflare processes ordinary connection information, including IP address, for delivery and abuse limiting. Reading Privacy or opening Storage alone does not fetch the catalog or online previews. This is independent of the Cloud organization switch.
  • The browsing-preview cache is limited to 64 MiB and 128 files, including metadata. Verified previews imported with downloaded themes stay with local content and remain available offline and in saved scene copies. Light and dark catalog sessions are cached in memory and considered fresh for fifteen minutes from their first successfully validated page; re-entering Scenes reuses a fresh session without another catalog request. There is no background catalog-refresh timer. Preview failures or cache eviction can show placeholders; navigation does not automatically retry failed previews, while explicit Refresh can retry.
  • The distribution service temporarily stores random download-lease identifiers, package version and expiry so active downloads can finish before an old version is removed. These records expire and contain no account, desktop inventory or personal file paths. Download statistics use Cloudflare's native resource metrics. Completed themes, bound descriptive metadata, source receipts and bounded download history remain local. Cancellation and manual retry do not authorize scene application or data upload.
  • Storage management inspects local downloaded content and can remove safely verified, unused bundle data only after confirmation; original user files and built-in themes are excluded. Network requests run only in the native service; the control center and HTML wallpapers remain blocked from network access. Downloaded content is validated and imported locally before use, not streamed as remote wallpaper or applied automatically.
  • 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 streaming images from the catalog. 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.
  • Offline classification still uses the bundled catalog and local rules, without a local AI model. Imported assets are validated locally and are not uploaded for cloud malware scanning. Optional cloud organization is the separate network feature described below, not a prerequisite for local organization.
  • Optional Cloud organization sends application names, publisher/product metadata and public application identifiers for desktop applications needing recognition to Deskloom's Cloudflare-hosted service; reliably recognized local applications do not need a model request. Where further classification is needed, the service forwards the allowed application metadata to Typesafe. Files, folders, document contents, private paths, shortcut arguments, notes, screenshots, custom group/scene names, desktop layout and Frequent history are excluded. It does not upload desktop files or a list of every application installed on your computer. Typesafe handles interactive classification; the separately described, consent-gated second pass uses OpenAI.
  • For a new local configuration, Deskloom checks its fixed service at most once before cloud consent, without sign-in credentials, cookies, application/desktop information or a permanent device identifier. It reads only a short-lived service observation of already authorized upstream requests, without making a new model request or accessing the application database. Cloudflare processes the connection IP and ordinary network/security metadata. This observation cache holds only a fixed result and time, not account, IP, country, application or User-Agent records; the evidence is usable for at most five minutes and may disappear sooner. The attempted state is saved before sending, so interruptions or upgrades do not trigger automatic retries. The bounded outcome stays in local configuration until cleared; retaining configuration on reinstall does not repeat the check. Recommendation freshness expires and does not survive restarting the app. This check is not permission for cloud classification.
  • Cloud organization starts off for new profiles; existing saved choices are preserved and you can enable it manually in settings. After the first successful manual scene application, a one-time recommendation may propose the cloud switch On only if a still-fresh observation of actual upstream success was obtained during this app session. Reaching the edge alone, expired or restored outcomes, failures, unknown or in-progress results propose Off. This evidence lasts at most five minutes, may disappear sooner, and does not guarantee the next request, account, quota or database availability. The local scene is applied before this optional recommendation. You can change the proposal; late check results do not change it or reopen the prompt. A proposed On switch is not consent and does not open login or upload application metadata. Before agreement, Deskloom explains the purpose, recipients, excluded data and controls. Agree and sign in with Microsoft, Agree and enable, or Agree and organize in the cloud grants the corresponding consent. Declining or dismissing leaves local organization available and does not undo the local scene; it does not withdraw consent or sign out an account you already explicitly authorized. Turning cloud organization off revokes authorization for new requests, cancels pending desktop work and prevents late results from changing the desktop. Data already sent cannot be recalled. Review records have no account identifier, so this control cannot remove earlier records by account. Re-enabling or a materially revised disclosure requires confirmation again. This choice is independent of Windows-integration permissions, Support diagnostics and Microsoft Store Health.
  • Microsoft handles cloud sign-in. Only an explicit sign-in action may open interactive Microsoft login; opening settings, a recommended On switch and ordinary organization do not open it automatically. Cloud organization requires sign-in and valid identity proof before capturing application metadata; a locally cached account is only a status hint, not that proof. Deskloom stores an encrypted application token cache using Windows protection, without a plaintext fallback. The service validates Microsoft identity proof and uses a pseudonymous account identifier for quotas and request deduplication; it does not send sign-in tokens or account identity to Typesafe or OpenAI. Closing Deskloom, dismissing a scene recommendation or disabling cloud organization does not sign out the account. The separate Sign out action removes this application's cached sign-in state, not necessarily browser sign-in or Microsoft sessions.
  • Deskloom's service does not persist raw classification request bodies by default. It keeps evidence digests, bounded classification results, quota/request records and aggregate catalog-hit counts needed to operate the service. Successful inference-cache results expire after seven days and unknown results after one hour; request replay records become eligible for deletion after 48 hours and quota counters retain approximately three UTC days. Expired records are removed in bounded batches, so deletion may occur later while the service is idle. These are not local application-launch histories. Cloudflare and the model provider process requests under their own terms; this policy does not promise third-party processing has no retention or training use. Ordinary network/security processing may include connection metadata such as IP addresses.
  • With explicit cloud-organization consent, when a provider outage leaves an application unrecognized, the service may retain its public application IDs and native product/publisher metadata for BitingGoat Software's manual review. The queue excludes your renamed shortcut labels, private paths, arguments, desktop references, account or request identifiers, and raw request bodies. Candidates are deduplicated by exact public evidence, not fuzzy matching. The queue is limited to 1,000 candidates and 4 MiB of evidence, with at most 8 KiB each. Candidates expire 30 days after first receipt; repeat observations do not extend that date. Expired candidates are excluded from review and removed in bounded batches, which may occur later while the service is idle. Manual review does not automatically publish offline classification rules. The service may decline new candidates when full without preventing local organization. This review queue is separate from the inference cache described above.
  • Only a new explicit decision on the updated cloud-organization agreement (disclosure version 4) and a fresh eligible observation permit the service to send public application IDs and native product/publisher metadata to OpenAI for a second cloud classification. Version-3 records retained only for manual review are excluded, and later observations do not upgrade their purpose. A high-confidence accepted result deletes the corresponding queue record and may be retained separately for 90 days from classification, with a limit of 1,000 results. It contains the category, exact-evidence digest, taxonomy/rubric versions, model and timestamps, not the underlying application metadata or account identifiers. These results can classify matching evidence in later cloud requests; they do not automatically change the reviewed offline catalog. The 90-day result store is separate from the ordinary seven-day/one-hour inference cache and the 30-day review queue. Provider processing follows the applicable provider terms; we do not promise that it has no retention or training use.
  • 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 community uploads, 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 profiles, time zones, permissions and caches are also excluded. Imported themes use the recipient's default weather location, without attaching weather-rendered thumbnails or desktop captures. This weather-specific protection does not identify or remove personal information you wrote into an original wallpaper or other content yourself. 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, available cover thumbnail and supported playback controls locally while a visible widget needs them. Thumbnails are resized and kept in memory only; no online cover search occurs. It does not read audio, save playback history or send media metadata or covers to a service. Playback controls act only on the session shown when you select them.
  • Optional Weather offers offline major-city search, manual coordinates and Use current location. Only clicking that location action requests Windows permission and obtains one position; opening Deskloom or its editor, applying a scene and refreshing weather do not acquire a position. Deskloom reduces coordinate precision on this device before returning or saving the automatic result. Windows location may use Microsoft services and is governed by Microsoft's location privacy rules. Location permission does not enable online weather. Windows location privacy
  • Online weather is off by default and requires a separate, explicit MET Norway weather choice. Once a widget is enabled with valid local consent, the native client sends its selected coordinates, rounded to two decimal places, directly over HTTPS to MET Norway (api.met.no). The service receives your network-exit IP and a generic Deskloom application identifier and may record coordinates and IP in its service logs. Reduced precision is not anonymity. Requests do not pass through BitingGoat Software's services; your normal system proxy or VPN can still apply. MET Norway's privacy statement applies. The bundled control-center and HTML wallpapers retain their network restrictions. MET Norway privacy statement
  • Weather profiles, the default weather location, permission choices and forecast caches are local private data. City searches use a bundled index without uploading search terms. Weather locations, city/search/profile/time-zone identifiers and location-bearing request logs are not sent to Deskloom's services, analytics, failure-summary submissions or diagnostic ZIP exports. Raw Windows position objects and automatic location history are not stored. Widgets and the editor share local forecast caching and provider-request limits, with at least ten minutes between requests for the same coordinates; provider expiry and rate-limit information can extend that interval. Expired and cached data are identified in the interface.
  • You can turn off a widget's weather requests, revoke this device's MET consent, clear weather cache, or clear the automatic-location result. Revocation stops new weather requests across this device and cancels pending work; an existing cache may remain visible with an offline label. Clearing cache retains your chosen city and permission, while clearing an automatic result leaves its references awaiting configuration without locating again. A separately selected manual place remains independent. Consent, clearing and Set as default take effect immediately; widget configuration follows the normal Add/Apply flow. Cancelling an editor cannot undo a permission or request already completed. Unsaved new locations are discarded. Deskloom can clear only data it manages locally, not records already processed by Windows or MET.
  • 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.
  • The minimal local FATAL and scene-operation summaries below are separate. Deskloom does not create its support incident journal or detailed diagnostic log unless you explicitly enable Support diagnostics. The support 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. Enabling Support diagnostics does not authorize any upload.
  • 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.
  • Minimal FATAL crash summaries are stored locally by default and can be disabled or cleared in Privacy & local data. They contain record time, random report ID, app/Windows versions, architecture, process role, fixed failure boundary, optional exit code and bounded exception types/HRESULT/method-only frames. Optional exit observations include a fixed exit reason, last observed cleanup phase/outcome, observation time, elapsed time, display ordinal and failed-phase count. A display ordinal is a screen's order number, not its name or hardware identity. Summaries exclude exception messages, personal paths, desktop/file/note contents, credentials, screenshots and memory dumps; exit observations add no process ID, account or device identity. The whole store is limited to 256 KiB and eight reports. Reports older than 14 days are removed on startup or record access; files can remain while the app is closed. Clearing or expiring reports does not erase bounded session/control markers; one exit observation can remain until a later exit replaces a known valid format, without forming a history. An unfinished session may reflect Windows shutdown/restart, forced termination, cleanup timeout or power loss, rather than a proven crash. A record may be created on the next launch; its creation and last-observation times are not the exact termination time.
  • A failed manual scene attempt, or one completed with safely isolated adjustments, also creates a small scene-operation failure summary locally by default. This is separate from a crash and does not indicate that Deskloom terminated. It records random report/attempt IDs, record time, app/Windows versions, fixed operation/section/step and outcome, language and regional-format tags, bounded elapsed time, scene kind, an audited built-in scene identifier when known, and bounded exception types/method frames and checked HRESULT/Win32 codes. Private scene identities/names, scene contents, resource hashes, exception messages, personal paths, file/desktop/note contents, credentials, screenshots and dumps are excluded. Both summary types share the local recording switch; an existing Off choice remains Off. Operation summaries are limited to four reports and 64 KiB including metadata/temporary writes; records older than 14 days are removed on startup or access. Together with the separate FATAL store, summary storage is bounded to 320 KiB. Nothing is uploaded automatically. Review is offered after recovery settles; recovery never waits for a user decision or network request. A local write failure may lose optional evidence without changing the desktop result. Fixed technical markers may identify a wallpaper request kind, desktop-read or taskbar-readiness stage, or coarse duration bucket; they do not contain raw commands, payloads, desktop item names or identities. A wallpaper import input refusal before scene effects, without an observed cleanup failure, shows local input guidance and does not create an operation report.
  • A result dialog or next-launch notice lets you review an individual summary. Only after a preview, checking the consent box and choosing Agree and upload this report does Deskloom attempt to send that one report to BitingGoat Software through Cloudflare. No account or permanent device identifier is required, and no automatic upload or retry occurs. The optional service may be unavailable or decline reports when capacity is full. The interface gives a neutral thank-you for your willingness to help; it does not confirm that the service stored the report. Unconfirmed reports remain under the local limits, and choosing to submit stops repeated reminders for that report. Only a matching server acknowledgment permits removing its local copy; full support-diagnostics ZIP files and memory dumps are not attached.
  • Cloudflare processes connection metadata such as IP for delivery and abuse limiting; the dedicated diagnostic-report database does not store IP, account information or User-Agent. Accepted reports are retained for at most 30 days from receipt and may be deleted earlier after processing or a privacy request; hourly cleanup removes expired live records. Cloudflare D1 automatically maintains recovery history for seven days on its Free plan or thirty days on its Paid plan. Deleting a live record does not immediately erase all provider recovery copies; restored data is subject to expiry cleanup before reuse. Clearing local summaries does not erase an already submitted record. Contact this page's support address with the random report ID for privacy/deletion enquiries. See Cloudflare D1 recovery documentation.
  • 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.
  • A one-time Microsoft Store rating invitation stores only local first-use and invitation-consumed timestamps. Microsoft handles any stars or review you submit; Deskloom does not read, store or upload your rating or review text. If in-app rating is unavailable, the Store-page alternative opens only after you click it. This is independent of Support diagnostics and feedback; declining does not affect features.
  • Obtaining Deskloom through Microsoft Store is handled by Microsoft under its Store terms and privacy statement. Cloud Microsoft sign-in is separate from Store acquisition; the app currently has no supporter account, in-app purchase or BitingGoat Software online license-verification service. Basic desktop customization does not require a cloud sign-in.
  • 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.
  • Bundled stickers ship with the app; compatible parties send sticker IDs, not repeated image uploads. Sticker messages use the same short in-memory history as other chat, not a separate cloud message or image cache.
  • Desktop close-to-tray is on by default: party and voice continue, and microphone transmission follows the current mute and Push-to-Talk settings. Explicitly leave, mute or choose Quit RallyTone to stop the corresponding activity, or disable close-to-tray in Settings. This desktop option does not change the browser rule that background tabs stop voice.
  • 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.
  • The Linux desktop client is distributed only through Snap Store with strict confinement. Snap installation and updates may contact Canonical's Snap Store under its own privacy disclosures, not upload RallyTone chat or voice. Configuration, avatars and trusted Server identities stay in revision-scoped local Snap user data; shared data is used only for disposable cache. Automatic migration of existing non-Snap profiles is not promised.
  • The Linux Snap uses the system audio service for playback and capture, not direct access to raw audio devices. The audio-record permission must be connected and does not auto-connect by default. Missing permission or a failed permission check produces guidance, not a silent bypass. File selection and exports use system dialogs and desktop portals; access to a selected file does not grant its whole parent directory. Network and listener permissions serve party communication, discovery and desktop hosting.
  • 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 compatible desktop Host or standalone Server's LAN Web 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.
  • Supported browsers may request a screen wake lock during a joined, visible session. Leaving the party, hiding the page or navigating away releases it. Denial or lack of support does not block joining or enable background voice. This feature does not collect screen contents.
  • 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].