SOURCE_URL: https://majikah.solutions/products/majik-buwiz/docs/buwiz-muid-manage

---
title: "Managing Your Identity & Profile"
id: "buwiz-muid-manage"
group: "majik-buwiz"
type: "products"
version: "0.1.1"
lastUpdated: "2026-05-13T00:00:00.000Z"
difficulty: "Intermediate"
time: "5 minutes"
tags: [muid, identity, passphrase, key-management, unlock, recovery, seed-phrase, majik-key]
---

# Managing Your Identity & Profile

> Managing your active Majik Key session, passphrase, profile edits, and recovery options

## Overview
How to manage your Majik Key session, change your passphrase, update your profile, and understand what happens if you lose access to your key.

### Your key session

Each time you open Majik Buwiz, you are prompted to enter your passphrase to unlock your Majik Key. Once unlocked, the key remains active for the entire app session — you will not be asked again until you close and reopen the app. There is no idle timeout while the app is running. When you close or restart Majik Buwiz, the in-memory key state is cleared automatically. Your private keys are never written to disk in plaintext at any point.

### Changing your passphrase

You can change your passphrase at any time from the Majik Universal ID tab. When you change your passphrase, the key material is re-encrypted under the new passphrase using Argon2id. Your seed phrase and all derived keys remain identical — only the local encryption wrapping changes. If your existing account was created with the legacy PBKDF2-SHA256 KDF, it is automatically upgraded to Argon2id at the next passphrase change.

### Editing your tax profile

Your tax profile fields — legal name, TIN, address, trade name, tax classification, and contact details — can all be updated at any time from the Majik Universal ID tab. Changes are saved immediately and used as the default issuer on all new invoices you create after the change. Previously signed invoices are not affected — the issuer data embedded in a signed invoice is part of the cryptographic commitment and cannot be altered without invalidating the signature.

### What can be changed after setup

| Item | Editable after setup? | Effect on existing invoices |
| --- | --- | --- |
| Tax profile (name, TIN, address, etc.) | Yes | No effect — existing signed invoices retain the original issuer data |
| Passphrase | Yes | No effect — only re-wraps the key locally |
| Bound Majik Key | No — key is permanent while MUID exists | N/A |
| Majikah account binding | No | N/A |
| MUID (unverified) | Delete and recreate | Old invoices retain old key fingerprint |
| MUID (verified) | Cannot be deleted for 30 days after verification | N/A |

*Caption: Summary of editable vs. fixed identity fields.*

### Forgot your passphrase

If you forget your passphrase, the only recovery path is to delete the Majik Key from the app and re-import it from your backup. Majik Buwiz supports three backup formats for import: a .json seed file, a .png backup image, or manually entering your 12/24-word seed phrase. All three restore the same key — after re-import you will be asked to set a new passphrase.

> ⚠️ **WARNING:** If you lose both the app data and all backup formats (the .json file, the .png file, and the seed phrase), there is no recovery path. Your signing identity, your invoice history tied to that key, and access to any Majikah products using that key are permanently lost. Store at least one backup in a secure offline location.

### Removing your key from the device

You can delete your Majik Key from Majik Buwiz from the Majik Universal ID tab. This removes the local key data from the app. It does not delete your MUID or your Majikah account — those remain intact on the platform. After deletion, you can re-import the same key using your backup to restore full functionality.

> **NOTE:** Your Majik Key is shared across all Majikah products — Majik Buwiz, Majik Message, and Majik Signature all use the same key. A passphrase change in Majik Buwiz only affects the local key storage in Majik Buwiz. Other Majikah apps on other devices retain their own locally stored copy of the key, each protected by its own passphrase.