Sharing and advanced workflows
Know what you are sharing, and what a connection can see.
Collection visibility is not image visibility
Public collections can appear on the curator’s profile. The current web implementation treats a private collection as unlisted: a signed-in person with the link can view it. Private collections are excluded from indexing, but should not be treated as an owner-only vault.
The collection page separately filters private samples from other viewers. Changing a collection’s visibility does not automatically change each sample’s visibility. Review both before sharing.
Your personal AI connection
A personal Taste connection can read permitted account context, including private and public collections. Choosing one collection in a prompt narrows the work, not the underlying authorization. Review the consent screen and disconnect clients you no longer use from Account → AI connections.
Portfolio: your own work
Use portfolio projects for work you made and want to present, rather than treating every inspiration save as your own work. Portfolio access varies with the connected server’s available tools. Ask the client to report its live capabilities before depending on portfolio access; saved designs and collections are the starting point for reference context.
Organize your own work into portfolio projects and review project and item visibility before sharing. An inspiration collection and a portfolio project serve different purposes: references you admire versus work you are presenting as your own.
Renting taste
Creator listings can share selected taste context through a creator-specific connection. That connection is distinct from your personal Taste server. Availability depends on the listing, its selected content, and your access grant. Check the creator named in the authorization screen.
Creator access should not be assumed to include private designs, private collections, interviews, or every personal tool. Use the creator’s connection instructions and ask which content is available.
Use Your taste library to review active access, expiry or renewal information, and available connection instructions. Paid subscriptions and free installs have different management actions. Follow the displayed cancellation or disconnect flow and confirm its resulting status; removing an MCP client alone is not a subscription cancellation.
Previews and experimental capabilities
Preview workflows are limited and depend on the connected server, account, and client support. Treat them as optional. Do not assume connecting Taste means every client can generate or display an interactive preview. A generated preview also needs review before becoming production code.
Check the policy and the actual permissions
Read Taste’s privacy policy for data handling, and your AI tool’s policy for the context you send into that tool. Disconnecting a client stops future access through that connection; it does not erase context already included in a conversation.