Privacy at a glance
Your private character conversations are not publicly visible to other users simply because you use Vislan. We do not design the service so one ordinary user can browse another user’s private chats.
Important: “private from other users” does not mean no system or authorized service provider can ever process the data. Limited access or automated processing may be necessary to generate AI replies, store memory, secure the service, investigate abuse, troubleshoot problems or comply with law.
Information we may collect
- Account information such as email address, display name, account role and plan.
- Characters, personas, messages, memory entries, settings and community interactions you choose to create.
- Service usage information such as message counts, feature usage, timestamps and technical logs needed for reliability and security.
- Reports, moderation submissions, support messages and other communications you send to Vislan.
- Advertising or consent information when advertising features are enabled.
How information is used
We may use information to create and authenticate accounts; provide character responses; maintain story memory; enforce usage limits; protect users and the service; prevent fraud, spam and abuse; respond to support requests; improve reliability; comply with legal obligations; and provide plan or advertising functionality.
AI processing
Message content and relevant story context may be transmitted to third-party AI infrastructure used by Vislan to generate a response. Vislan currently uses server-side AI services, including DeepSeek-powered generation in the production architecture. We do not expose Vislan’s private API credentials to ordinary users.
Third-party providers may process data according to their own contractual terms and privacy obligations. Do not put passwords, government identifiers, payment secrets or other information you do not want processed into roleplay messages.
Private versus public content
Private chats are intended for the account holder and the service components required to operate them. Public characters, public comments, reactions, usernames or other community content may be visible to other users and can be moderated.
Authorized access
Authorized access to account data may occur when reasonably necessary to operate or secure Vislan, diagnose technical failures, investigate suspected policy violations, process a report, comply with applicable law, or protect users, rights and safety. We aim to limit such access to what is reasonably necessary for the task.
Retention and deletion
Different data types may be retained for different periods depending on product functionality, security, backups, legal requirements and dispute prevention. Account deletion is intended to remove account-associated data from active systems where technically and legally appropriate, but deletion from backups or logs may not always be instantaneous.
Advertising and cookies
Free versions of Vislan may display advertising on eligible discovery, update or other non-private-chat surfaces. Advertising providers may use cookies, device identifiers or similar technologies subject to consent and applicable law. Vislan does not intend to place ordinary Google display ads inside a private roleplay conversation where private communication is the main focus.
Security
We use reasonable technical and organizational measures appropriate to the service. No online service can promise perfect security. Users are responsible for protecting their passwords and should contact Vislan if they suspect unauthorized access.
Your choices and rights
Depending on where you live, you may have legal rights to access, correct, delete, restrict or object to certain processing of personal information. You may also have rights concerning advertising consent. Requests can be directed through the contact methods listed on our Contact page.
Changes to this policy
We may update this Privacy Policy when Vislan changes. Material changes should be reflected by updating the effective date or providing additional notice where required.
Effective date: September 2026.