IDENTITY · PRIVACY · FURRY TECH

In development

TAILS

Identity belongs to the user.

A privacy-first platform for the furry community: fursona identity, privacy, interaction, creators, and community infrastructure.

01 / OVERVIEW

Context

TAILS is a software platform for the furry community, not a physical accessories product. Its full name is The Anthropomorphic Identity and Link System.

The product separates a private real account from a user-controlled public furry identity. The user decides which identity to show, who can access data, and which interactions are allowed.

02 / SCOPE

My role

  • Product concept and identity model
  • Privacy- and consent-first principles
  • Modular web architecture design
  • Creator, event, and community discovery directions

03 / PROBLEM

Identity without forced exposure

Mainstream social platforms often mix real identity, public profile, and engagement mechanics. For the furry community that creates unnecessary risk: a fursona should not require public linkage to a real-world identity.

04 / IDENTITY MODEL

Private account → controlled identity

  • The real account remains private
  • A fursona exists as a separate managed identity
  • Visibility is scoped
  • Interactions depend on consent
  • Public exposure is not the default

05 / PRIVACY

Privacy & consent by default

Identity and data belong to the user. Safety comes before engagement farming: no dark patterns, forced exposure, or automatic permission for unwanted interactions.

06 / PRODUCT

Product directions

  • Fursona profiles and metadata
  • Gallery and art media
  • Events and notifications
  • Messaging and moderation
  • Privacy controls
  • Creator ecosystem and community discovery

07 / CREATORS

Creator marketplace

One direction is centralized discovery of artists, makers, and physical-goods creators, especially across Russia and the CIS. Commissions, storefronts, safer transactions, and delivery integrations are being considered; this is a direction, not a claimed finished marketplace.

08 / ARCHITECTURE

Designed platform architecture

The architecture has used or considered Next.js, NestJS, TypeScript, Bun, Turborepo, shared packages, APIs, S3-compatible storage, a message broker, Kubernetes, GitLab CI/CD, and Cloudflare / CDN.

  • Auth
  • Profile
  • Gallery
  • Events
  • Notification
  • Chat

09 / ACADEMIC CONTEXT

Additional context

The project has also been considered in an academic context around safe community identity and interaction. This is secondary context rather than the product’s main positioning.

STATUS / NOW

Current status

  • TAILS is in development; some directions remain architecture and product concept work.
  • Plans are separated from production functionality, and the full module set is not presented as implemented.
All projectsContact