A Quarterly Profile Hygiene Audit for Shared Media Apps
Quarterly profile hygiene keeps recurring contexts distinct, names private, owners accountable, preferences intentional, and obsolete profiles governed without exposing viewing histories.
In short: Every quarter, review each profile's recurring purpose, responsible administrator, privacy-safe name, expected preferences, and shared-screen handoff. Identify duplicates and obsolete contexts without inspecting or exporting detailed viewing history. Verify current plan capacity separately from device use. Plan renames, consolidation, or retirement before making destructive changes, and never present profile capacity as parental control, source authorization, or a simultaneous-playback limit.
Profiles accumulate quietly. A temporary context becomes permanent, a label reveals too much, or two profiles begin serving the same purpose. Quarterly hygiene keeps the household model understandable without turning the audit into surveillance.
Use the maintenance schedule
Place this review under the media maintenance handbook, separate from the monthly account-and-device check. Choose one administrator and invite profile owners to confirm purpose without disclosing what they watched.
Record only the quarter, neutral profile code, and decision.
Confirm a recurring purpose
Each profile should represent a stable personal or shared viewing context. Ask whether the context still recurs, whether another profile serves the same need, and whether a new recurring context has emerged. Do not create or delete profiles merely because capacity exists.
The first-profile purpose guide provides the original definition method.
Verify ownership and handoff
Record the adult administrator responsible for renaming, retirement, and support. On a supported shared screen, ask the regular user to select the correct profile from the normal viewing distance. Record whether the handoff is clear, not which titles appear.
If household membership changed, use the household-change profile audit because access and administration may require immediate action.
Review names for privacy
Reject labels containing full names, emails, birth dates, precise locations, health or belief information, account identifiers, or source details. Check whether two names become confusing when truncated on a shared screen.
Use the privacy-safe profile naming guide to create a neutral replacement before changing anything.
Check duplication by context
Two profiles are duplicates only when their purpose and owner context overlap, not merely because their names look similar. Record the reason for potential consolidation. Avoid promising that histories, favorites, or preferences can be merged unless current official support documents that behavior.
Use “merge-plan” as an administrative decision, not a product feature claim.
Review preferences with known samples
Where language or subtitle preferences are available, use one known item whose source tracks are confirmed. Check the intended profile and actual selected option on a required supported screen. A preference cannot create a track the source does not supply.
Do not inspect private history to infer a preference when the user can state it directly.
Compare need with current capacity
Current official information describes up to two profiles for Norva and up to five for Norva Family. Review current pricing and conditions before changing plans. Count recurring contexts, not screens or people who might visit once.
Norva Family describes profile capacity. Do not present it as a parental-control system.
Plan profile retirement safely
Before retiring a profile, record its purpose, owner approval, unresolved favorites or progress concerns, and the current official support guidance. Do not assume deletion is reversible or that state transfers automatically. Use a cooling-off period for uncertain cases.
After any approved change, verify the remaining names and one shared-screen handoff.
Minimize audit evidence
Keep neutral profile codes, stated purpose, owner role, decision, and review trigger. Exclude viewing histories, full identities, credentials, and source information. Delete temporary screenshots when the administrative need ends.
Original evidence: profile disposition register
| Profile code | Recurring purpose | Owner | Name safe and distinct | Preference sample | Disposition |
|---|---|---|---|---|---|
| P1 | |||||
| P2 | |||||
| P3 |
Use retain, rename, merge-plan, retire-plan, or unresolved. Assign an owner and review date to every non-retain result.
Common mistakes and limitations
- Reviewing detailed history instead of purpose.
- Deleting before checking current support guidance.
- Assuming profiles can be merged automatically.
- Counting devices as profile needs.
- Treating Family as a parental-control claim.
- Leaving sensitive labels visible on shared screens.
Frequently asked questions
Must every profile belong to one person?
No. A recurring shared context can be valid when its purpose and administrator are clear.
Can I merge two profiles and preserve all state?
Do not assume so. Review current official controls and support before any destructive change.
How many profiles do current plans describe?
Norva includes up to two profiles and Norva Family up to five. Verify current pricing and terms when making a plan decision.