Privacy Policy

Images submitted for reverse image search are decoded and processed in memory. We remove metadata before sending the image to our embedding service. Uploaded images and their query embeddings are not saved, published or used to train a model. Description queries use the same service and are not saved as search content. Operational request counts and errors follow the logging rules below.

We cache public catalog thumbnails and store their perceptual hashes and embeddings alongside avatar IDs to support image search. These catalog records are separate from user uploads. Results are checked against the current public catalog before they are returned.

VRChat Legends operates AviSeek at aviseek.vrchatlegends.com. This policy covers the AviSeek website, its installed web app, and API. Your separate VRChat Legends account and external services have their own policies. Contact support@vrchatlegends.com with privacy questions or requests.

VRChat Legends handles sign-in and asks you to approve access to identity, email, VRChat, connection, and supporter information. AviSeek keeps the account identifier, display name, profile-picture URL, public profile link, staff flags, available rank, Patreon-linked status, and the time supporter information was checked. These provide your account, creator verification, access controls, and supporter benefits. We also store a last-seen timestamp for signed-in sessions; the private server stats bot counts unique accounts seen within the last fifteen minutes. Only aggregate counts appear in its stat channels.

Email may be included in the sign-in response but is not retained in AviSeek’s account-session record. AviSeek does not ask for your VRChat or VRChat Legends password. The login exchange uses a VRChat Legends access token to read the approved profile; the current integration does not retain OAuth access or refresh tokens after that exchange. AviSeek stores a hash of its own session token, while your browser holds the session cookie.

We associate favorite avatars and groups, likes, dislikes, extra favorite slots, and preferences with your account. Public avatar counts reflect likes and dislikes; dislikes reduce ranking; your saved collection is an account feature. Preferences control search defaults, layout, motion, links, and tags.

Personalized recommendations use an account-linked interest profile, including weighted tags, creators, search terms, and platforms derived from interactions. This is separate from aggregate view, impression, click, and popular-search counters. You can inspect and reset learned interests on the account page.

Our public world API does not require account linking and does not expose your personal website settings, favorite folders, or credits. World creators manage their own player preferences.

A first-party referral cookie preserves an invitation for up to 30 days while you browse and sign in. It is cleared after successful sign-in. We store credit balances, grants, deductions, ledger entries, extra-slot purchases, referral codes and referral relationships, reward-claim records, and promotion details such as the selected listing, dates, and cost. These records deliver benefits, track balances, resolve disputes, and prevent repeated one-time rewards.

Group rewards use linked VRChat identity and membership checks against the VRChat API. Public group statistics are cached for the homepage. For new VRChat+ gifts to the backend account, AviSeek reads authenticated gift notification IDs, sender and receiver IDs, and gift timestamps. Verified VRChat identity mappings support credit rewards. Pending unmatched gift events expire after thirty days. Accepted gift references and credit records are retained to prevent duplicate rewards; notification messages are not stored. Anonymous or ambiguous gifts do not earn automatic credits. Supporter benefits use rank and connection information supplied by VRChat Legends; AviSeek does not need your Patreon password or payment-card details. The current credit-pack checkout is not connected and does not collect card details or charge a card.

Claim and unlisting codes are tied to your account and avatar, expire after 30 minutes, and are stored only as hashes. We fetch the current VRChat description only when you explicitly press Check. Successful codes cannot be reused. We retain your claim, the avatar’s author identifier, claim time, and whether you unlisted it to manage listings. Account data deletion clears your claims and codes; existing unlistings remain in effect.

Tags are inferred from public avatar text by a small model running on our backend, with keyword fallback during outages. We do not send this tagging data to OpenAI or other hosted AI providers. Inferred tags can be wrong. Description editing access does not establish copyright ownership, and formal reports remain available.

The catalog contains public avatar names, descriptions, creator identifiers, thumbnails, tags, and platform information. Public creator profiles may be linked to listings. Automated and administrator-managed moderation checks this listing metadata. Verified creators can hide their listings from public AviSeek results through Avatar Insights.

Referral preview endpoints publicly expose the inviter’s display name and profile-picture URL. Referral images combine that picture with AviSeek branding. Anyone with the link, including Discord and other preview crawlers, can retrieve this information. Avatar links likewise expose public listing information. Those services may retain their own cached previews after a profile changes or a listing is hidden.

An HTTP-only session cookie keeps you signed in, and a short-lived OAuth state cookie protects the sign-in flow. Browser storage also remembers settings such as sound preferences and cached display preferences. Clearing browser data resets locally stored choices and can sign you out.

Installing AviSeek uses the browser’s web-app facilities. Its service worker caches an offline fallback page and app icon. It does not cache your account pages or API responses for offline access. Ordinary browser and infrastructure caching can also store public assets such as styles, scripts, and images.

Cloudflare and hosting infrastructure process requests to deliver and protect the service; this can include IP addresses, browser information, request paths, and diagnostic or security logs. Rate limiting also processes request information. Aggregate catalog counters should not be read as a promise that infrastructure never processes identifying request data.

VRChat Legends supplies sign-in and profile information. VRChat supplies catalog media and group information, and profile images may come from VRChat Legends or Discord’s media services. When your browser loads external media or follows an external link, that provider receives the request under its own policies. Preview services receive public metadata when they fetch shared links.

The account page exports the preferences and collections included in its download. Delete AviSeek data clears favorites, favorite groups, likes, dislikes, avatar claims, verification codes, learned interests, preferences, and AviSeek sessions. It does not delete your separate VRChat Legends account or public catalog listings.

The current self-service deletion does not erase credit ledgers, promotion records, referral records, or one-time reward history. These remain for balance integrity, reward-abuse prevention, and resolving disputes; the download is not an export of every operational record. Contact support to request access, correction, or deletion of remaining account information. We will explain any information that must be retained and why, subject to applicable law.

Eligible Patreon members and administrators can use the optional VRChat device login. AviSeek relays credentials, verification codes and Wear requests to VRChat without saving or logging them. The VRChat session is encrypted in an HttpOnly cookie on your browser for up to seven days, or ten minutes while verification is pending. It is decrypted only while relaying a request and is not stored in our database. Disconnect removes that cookie and attempts to revoke the VRChat session; website sign-out also removes the cookie.

Operational records and backups may remain after a change to active data. Browser storage and third-party cached previews are separate and may need to be cleared through those services. We do not promise immediate deletion from those copies.

If you connect Discord, AviSeek requests identity, server-list and Linked Roles permissions. It stores your Discord ID, display name, avatar URL, linked AviSeek account ID, encrypted OAuth access and refresh tokens, and sync status. Tokens are encrypted at rest on the backend so it can refresh the connection and update role checks while you are away. These are Discord tokens, separate from the device-only VRChat login.

Community account pairing uses a random code valid for ten minutes, tied to your current AviSeek session. The backend stores its hash, expiry, account identifier and session hash, and consumes it once through the authenticated Discord bot. The paired record stores your Discord identifier, display name and profile image, without a Discord password or OAuth token. Community-only connections enable wallet commands and booster checks; Linked Roles require the separate OAuth authorization.

The official AviSeek community bot observes server-member boost changes and checks the connected member’s active boost directly with Discord. It does not read messages or presence. A successful 150-credit booster reward stores hashed references to both the AviSeek and Discord accounts, server identifier and redemption time. These references remain after disconnecting or deleting account data to prevent repeated rewards; status checks and failed verification results are temporary.

Discord receives five checks: whether AviSeek is connected, whether a VRChat identity is linked, current wallet credit balance, confirmed Patreon tier level, and saved-avatar count. Identity and supporter claims older than 24 hours become unconfirmed on the next successful sync. Credit changes sync automatically, usually within seconds, and recovery checks run approximately hourly; Discord outages or revoked access can delay updates. Members choose roles in Discord, and server administrators decide which checks roles require.

The server dashboard reads your current Discord permissions before showing or saving a server. Only owners and members with Administrator permission can use it. Stored settings include whether commands are enabled, the permitted channel and reply visibility. Disconnect on the Linked Roles page clears role checks, revokes authorization and removes the stored connection. If authorization has already been revoked, remove the AviSeek connection in Discord too. You can also revoke access in Discord’s Authorized Apps settings.

The optional Discord bot processes slash-command inputs and Discord user, server, and channel identifiers to answer commands, enforce short-lived rate limits, and apply server settings. It does not request message-content or member-list gateway access. Commands use the same public moderated catalog as the website.

Server settings store the server ID, optional command-channel ID, and private-reply preference until reset or the bot is removed. Operational counters track command totals, failures, rate limits and aggregate minute-by-minute activity for the current backend process. Result pagination temporarily holds the requester, server, channel and search options in memory. Buttons expire after 10 minutes; expired sessions are removed during the next cleanup, which runs every minute. Pagination state is not written to the database. Rate-limit identifiers expire from the active limiter after one minute and are not written to the database. Public replies and embeds are messages handled by Discord under its policies; choose private replies if you do not want command results visible in the channel.

Use account settings to update preferences, reset personalization, export supported data, unlink your player, or delete the data described above. You can also revoke AviSeek’s authorization through VRChat Legends. Depending on your location, you may have additional rights to access, correct, delete, restrict, or object to processing, or complain to your local privacy authority. Contact support to exercise applicable rights; we may need to verify the request belongs to you.

We will date revisions to this policy and provide additional notice or obtain consent where required for material changes. This policy describes the current service rather than permission for unrelated future uses of your information.