Privacy Policy
This policy covers VOID Animation Migrator, its VOID HUB licensing pages, and the server APIs used to verify a license and authorize an animation migration.
Effective date:
1. Who operates the service
VOID HUB, operated by voidksa, provides VOID Animation Migrator and its licensing service. Questions and privacy requests can be sent to support@void-hub.vip.
Roblox and Discord are independent third-party services. VOID HUB is not Roblox Corporation or Discord Inc.
2. Information processed by VOID HUB servers
The website and licensing service process the information needed to provide account access, checkout, ownership checks, device binding, abuse prevention, and migration authorization.
- Discord account and entitlement data: your Discord user ID, username, display name, avatar, and locale if returned during sign-in, plus account status, site session, library entitlement, product, license status, and reset history. The current sign-in flow requests Discord's identify scope only and does not request your Discord email. The email field in our identity records remains optional for compatibility and is cleared when Discord returns no email.
- Checkout contact data: you enter an email address and mobile number in the checkout form. VOID HUB sends those values to the payment gateway to start the transaction. The checkout email is not obtained from Discord.
- License material: an encrypted serial, a keyed lookup hash, and a masked serial. The full serial is returned only through an explicit recent-authenticated reveal or the signed Discord delivery route.
- Device identity: the device's Ed25519 public key, a derived device ID and fingerprint, an optional device name, binding and reset timestamps, and activation request status. The matching private key stays on the device and is not sent to VOID HUB.
- Security records: request identifiers, timestamps, replay-prevention values, hashed network identifiers where configured, user agent, rate-limit activity, and license audit events. These records must not contain raw serials, activation codes, private keys, Roblox tokens, or asset files.
- Migration authorization: the application, license and device linkage, device epoch, request status and timestamps, the number of selected asset IDs, and a one-way hash of that ID list. Completion stores counts of requested, migrated, skipped, and failed items and may store an output hash.
3. Information kept on your Windows device
The desktop app stores its device private key, license session credentials, Roblox OAuth tokens, and the Roblox profile returned by OAuth in encrypted local files using the Windows operating-system secure storage available to the signed-in Windows user.
Choosing Disconnect Roblox removes the app's local Roblox token and profile files. You can also revoke the app's authorization from your Roblox account settings. Removing local data does not by itself remove server-side VOID HUB entitlement or security records.
4. Roblox OAuth and asset processing
The app uses Roblox's official OAuth authorization-code flow with PKCE. It requests openid and profile to identify the connected Roblox account, plus asset:read and asset:write so you can read and upload authorized animations.
Roblox access and refresh tokens are exchanged with Roblox from the desktop app and remain encrypted on that device. VOID HUB licensing servers do not receive or store those tokens.
Animation files are downloaded from Roblox or its approved delivery hosts to the desktop app and uploaded from the desktop app directly to Roblox. The files and their contents do not pass through VOID HUB servers. Selected asset IDs are sent briefly to obtain a signed job authorization, but the persisted job record contains only a count and one-way hash of the list.
5. Why we process this information
- Authenticate the Discord account that owns the product entitlement.
- Issue, reveal, validate, bind, refresh, and reset a device-bound license.
- Show enough device information for the owner to review an activation request safely.
- Authorize a specific migration job and record a limited completion result.
- Prevent replay, credential sharing, fraud, and abuse; investigate support or security incidents.
7. Retention and deletion
Activation codes and signed credentials become unusable when they expire or are rotated. Local OAuth and profile files remain until you disconnect Roblox or remove the app's local data.
Entitlement, encrypted license, device binding, audit, and migration-job records may remain while needed to operate the license, enforce reset limits, handle support and security incidents, or meet legal obligations. VOID HUB does not currently publish a fixed automatic deletion schedule for these server records.
You may ask us to access, correct, or delete personal information by emailing support@void-hub.vip. We may verify that the request comes from the Discord account owner, and we may retain records that are required for security, fraud prevention, transaction records, dispute handling, or law. Deleting VOID HUB data does not delete your Roblox account or Roblox-hosted assets.
8. Your choices and rights
- Disconnect Roblox in the desktop app to remove its local Roblox token and profile files.
- Revoke VOID Animation Migrator from your Roblox account settings to withdraw future OAuth access.
- Sign out of VOID HUB, reset an eligible linked device from your library, or contact support about an entitlement or activation you do not recognize.
- Request access, correction, or deletion, and raise a privacy question or complaint at support@void-hub.vip.
9. Security
The implementation uses encrypted-at-rest serials, operating-system encryption for local secrets, short-lived scoped credentials, signed device proofs, replay checks, recent Discord authentication for sensitive owner actions, and no-store responses. No system can guarantee absolute security, so report a suspected compromise promptly and do not share a serial or activation code.
10. Changes and contact
We may update this policy when the app, integrations, or legal requirements change. The effective date on this page will change when the policy is revised. Contact support@void-hub.vip with privacy questions or requests.