FAQ
Common creator questions.
Short answers about protected slots, customer activation, dashboard control, archive behavior, and limits.
Basics
What is Flowye Licensing?
A protection and licensing system for VRChat avatar creators. It adds protected avatar content, license activation in Unity, and Creator Dashboard visibility around the avatar you release.
Do I sell my avatar through Flowye Licensing?
No. Your store stays yours. Flowye Licensing protects the avatar release and license flow around the way you already sell.
What does Avatar Protection cover?
Protected avatar content, license activation, package integrity checks, server validation, and invalid license attempts. Direct package sharing is made much harder, but it is still protection for the release, not a storefront listing or lifetime protection forever.
What does a Protected Avatar Slot include?
A Protected Avatar Slot is the capacity for one Avatar Identity or Protected Product. The base slot includes setup/protection and a 12-month Active Term unless the checkout or manual offer says otherwise.
When does the Active Term start?
Checkout reserves or purchases the slot and starts setup/provisioning. Unless the offer says otherwise, the Active Term starts when Flowye marks the first protected build, review, slot, or protected release as finalized, ready, active, or delivered.
Setup and activation
How does package preparation work today?
Today, protected releases can go through guided preparation and review before the customer gets a simple Unity activation flow.
What does my customer do in Unity?
They import the protected package, open the activation window, enter their license key, and continue with the avatar.
Does my customer need a Flowye Licensing account?
Your customer does not need a full Flowye Licensing creator account. They activate with a license key inside Unity.
Control and limits
Can Flowye Licensing stop every leak or rip?
No. Once avatar content is materialized inside Unity or exists on VRChat, platform-level limits still apply. Flowye Licensing adds useful protection and checks, not perfect guarantees.
What can I control from the Creator Dashboard?
You can work with protected avatars, licenses, customers or users, access controls, and license and build checks. If access is disabled, future license checks can be denied.
What happens if a protected slot expires?
Expired slots are archived, not intentionally broken. Existing protected releases should not be intentionally broken only because the creator does not renew, but new provisioning, new managed downloads, rebuilds, managed distribution, monitoring, and dashboard actions may pause after expiry.