skills.rest
fullstorydev
fullstorydevOFFICIAL
Explore all skills by this author →
WebsiteGitHub

fullstory-anonymize-users

Anonymize identified user sessions across web and mobile platforms.

11|2|Updated Dec 2, 2025
Search Tags:#mobile#privacy#identity#web#logout#anonymize#account-switching
One-click install
npx skills add https://github.com/fullstorydev/fs-skills --skill fullstory-anonymize-users-fullstorydev
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: fullstory-anonymize-users
Source: https://github.com/fullstorydev/fs-skills/tree/main/core/fullstory-anonymize-users
Command: npx skills add https://github.com/fullstorydev/fs-skills --skill fullstory-anonymize-users-fullstorydev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Anonymize the currently identified user session to end attribution and start a new anonymous session.

Core Features & Use Cases

  • Logout handling: terminate an identified session before redirecting to login.
  • Account switching: provide a clean slate when switching between accounts.
  • Shared devices: prevent cross-user data linkage on kiosks or shared devices.
  • Privacy compliance: support privacy requests and consent workflows.

Quick Start

  • Track the logout event while the user is still identified.
  • Call the platform-specific anonymization API (web: setIdentity with anonymous: true or setIdentityAsync; mobile: anonymize()).
  • Clear local auth state and navigate to the login screen.

Frequently Asked Questions about fullstory-anonymize-users

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I anonymize a user session on logout for web and mobile platforms?▼

To anonymize a user session, track the logout event while the user is identified, then call the platform-specific API: setIdentity with anonymous: true for web or anonymize() for mobile. Clear local auth state and navigate to the login screen with a single call per logout.

What is the best way to handle account switching to prevent cross-user data linkage?▼

Anonymizing the current user session provides a clean slate for account switching. You must track the logout event first, apply the platform-specific anonymization call to end attribution, and then navigate to the new account login.

When do I need to anonymize an identified user session on shared devices?▼

You need to anonymize identified user sessions on shared devices and kiosks to prevent cross-user data linkage. The process requires tracking a logout event before enforcing platform-specific anonymization calls to start a fresh anonymous session.

Does anonymizing a session require tracking an event before navigation?▼

Yes, anonymizing a session requires tracking an event before the anonymization call occurs. You must log the logout event while the user is still identified, execute the anonymization API, and ensure anonymization happens before navigation.

Can I use session anonymization for privacy compliance and consent workflows?▼

Yes, session anonymization supports privacy compliance and consent workflows by ending user attribution. By tracking an event and applying platform-specific anonymization calls, you terminate the identified session and start a new anonymous one.

Related Skills

Explore More Software Engineering Skills→
RevenueCatRevenueCat
58

revenuecat-identify-user

Link app authentication users to RevenueCat identities via logIn and logOut.

Official
Intermediate
wheels-devwheels-dev
203

Wheels Auth Generator

Generate CFWheels user authentication with sessions controller and bcrypt password hashing.

Official
Basic
rcmaplesrcmaples

fullstory-anonymize-users

Anonymize Fullstory sessions with FS('setIdentity', {anonymous: true}) before redirects.

Community
Advanced
ythmythm
1

yida-logout

Clear local cookie cache to log out users from the Yida platform.

Community
Basic