Create a One-Page Household Media Agreement
Write a concise household media agreement covering roles, profiles, authorised sources, trusted devices, privacy, change approval, guests, incidents, and exits.
In short: Put nine items on one page: purpose, account coordinator, source steward, profile ownership, trusted devices, credential boundary, shared-change approvals, guest and privacy rules, and incident/onboarding/offboarding steps. Use roles rather than passwords or personal history. Read it aloud, ask every member to explain their part, and revise rules that are not actionable.
The page should reduce uncertainty, not create household bureaucracy. If a rule needs a second document to understand, simplify it.
Draft it together in a private setting and assign one editor. Parallel copies quickly conflict, especially during an incident. Keep an effective date and short change reason so members know which version governs current shared-screen and source decisions.
State the purpose
Begin with one sentence:
“We use this agreement to protect viewing context, account access, authorised sources, shared devices, and household privacy.”
Do not frame it as monitoring personal tastes.
Name organisational roles
List the account coordinator, source steward, device custodian, and profile owners. These labels describe household responsibility, not Norva permissions.
The governance guide defines the account, source, profile, device, and session layers.
Define profile rules
Include:
- read the profile label before play;
- personal profile owners control their favourites and preferences;
- shared profiles use agreed defaults;
- profiles are not passwords;
- wrong-profile activity is paused and documented;
- removals require ownership review.
Use the profile-boundary explanation for teach-back wording.
Define source and credential rules
State that only compatible sources the household owns or is authorised to use may be connected. Name who coordinates changes.
Write “credentials are never placed in this agreement or shared chat,” not the credentials themselves.
Define device trust
List where the separate secret-free device inventory lives. State that borrowed or untrusted devices are signed out and that local eligible media is reviewed before a device leaves.
Do not confuse trusted with supported.
Set change thresholds
Use:
- personal reversible change: profile owner decides;
- shared reversible change: notify affected members;
- shared disruptive change: approval and rollback record required.
Examples of disruptive changes can include removing a source, resetting an app, or changing shared category structure, subject to current controls.
Add the troubleshooting rule
Preserve the first state, change one variable, record the result, and stop before destructive recovery. Use the household troubleshooting rule for detail.
Add lifecycle and privacy rules
State how new members are introduced, how departures are handled, when devices are removed, and who contacts support. Include consent and minimum evidence for profile reviews.
Review Norva's privacy policy and terms rather than copying legal text into the household page.
Original evidence: one-page template
- Purpose: ___
- Account coordinator: ___
- Source steward: ___
- Device inventory owner: ___
- Profile ownership rule: ___
- Credential boundary: never record secrets here
- Trusted-device rule: ___
- Shared-change approval: ___
- Guest/privacy rule: ___
- Troubleshooting rule: ___
- Onboarding/offboarding rule: ___
- Support route: https://norva.tv/support
- Review triggers: ___
- Accepted by: ___
The page should not contain emails, passwords, recovery codes, payment data, source URLs, or detailed viewing history.
Test the wording
Ask each member to explain what they do before play, before connecting a source, during a problem, and when leaving a device. Revise any answer that depends on unstated assumptions.
Test one ordinary scenario and one departure scenario. For example, rehearse a wrong-profile start and a borrowed tablet return without using real credentials or deleting data. The agreement passes when members choose the same safe next action.
Common mistakes and limitations
Avoid copying terms nobody understands, listing every personal action, storing secrets, assigning roles to people who did not agree, and treating the page as technical enforcement.
This agreement supports coordination. It is not legal advice and cannot grant product permissions or guarantee privacy.
Frequently asked questions
Does the agreement need signatures?
Use any acknowledgement that fits the household. The important result is shared understanding, not a legal formality.
Should viewing history be listed?
No. Record rules and decisions, not personal content-level activity.
Can the page include account credentials?
Never. Store and manage secrets through appropriate secure account controls.
Your next step
Review Norva's privacy information