Your Velvet page is a creator link in bio that earns. One public URL gathers your paid content, subscription, tips, custom requests and wishlist in a single place; share it everywhere and let fans choose how to support you.
Your profile shows uploaded tiles and paid links in a single stream, ordered by a key both of them share. Dragging a link above a photo works because the order is genuinely one list rather than two lists drawn next to each other.
Saving an order restamps every entry evenly instead of squeezing one row in between its neighbours. Reorder as often as you like and the grid never runs out of room and never needs a cleanup pass.
Velvet keeps a reserved list covering every static route in the app, and registration is checked against it. Your page lives at the top level of the domain without anyone ever claiming a name that quietly resolves to something else.
Claim your handle and Velvet builds your public page at your own velvet.fans URL. Everything you enable (PPV links, subscription, tips, requests, wishlist) appears there automatically.
Fans landing from any platform see one clean page with every way to support you, no juggling five different tools and links.
You decide which blocks appear and in what order, what your page says and which content is public versus gated.
Update it once and it's current everywhere, because every bio on every platform points to the same page.
Tips, custom requests, the fan subscription and chat each carry their own switch in your creator settings, and the public page renders whatever is switched on. There is no second place to configure the page, which is why it cannot drift out of step with what you actually sell.
The safety settings work the same way. A social safe-mode flag exists for the version of your presence that social platforms will tolerate, and chat can be closed to subscribers, neither of which asks you to rebuild the layout.
Working shifts are a recurring weekly schedule you set in your own timezone, up to forty of them. They tell a fan when you are usually around, which is a separate claim from the live availability toggle and from actual presence in a conversation.
The conversion into a visitor’s local time happens in their own browser, so a fan five timezones away reads your hours in theirs while you maintain exactly one version of the schedule.
Every purchase made from your page runs through secure payment providers and lands in your Velvet wallet with a full ledger trail.
Every sale from the page clears the same 7-day hold and joins one balance you withdraw from when you choose.
One address in every bio means the next price change, the next drop and the next new offer are published once. Nothing depends on you remembering which platform still points at last quarter’s link.
The show-on-profile switch on each link keeps the two catalogues apart. What you send to one fan in a conversation stays out of the public grid unless you decide it belongs there.
Pinning one item and one link above the grid gives the page an editorial front. A visitor meets this week’s priority first and finds the rest of the catalogue underneath it.
Any monetization tool you enable: PPV content, your subscription, tips, custom requests and your wishlist, plus your bio and links.
Yes. That's the point: one velvet.fans URL replaces a separate link-in-bio tool plus scattered store and tip links.
Yes. You claim a handle and your page lives at your own velvet.fans URL, which you can share anywhere.
Yes. Each link carries its own show-on-profile switch, so a link you only ever send inside a conversation stays out of the public grid while remaining perfectly purchasable.
No. Every static route in the app is on a reserved list that registration checks against, and a test walks the real route tree to catch a new route added without being reserved.
By a single sort key shared between uploaded tiles and paid links. Saving a new order restamps the whole visible list evenly, which is why the order you drag into place is the order that renders.
Yes, with recurring weekly shifts set in your own timezone, up to forty of them. Each visitor’s browser converts them into local time, so you never maintain a second version for another region.