Shared Device Privacy Boundary Card

SKILL.md

---
name: shared-device-privacy-boundary-card
description: "Create a consent-first shared device privacy boundary card for household laptops, tablets, TVs, browsers, and accounts, with private zones, sign-out rules, guest-use checklist, and no surveillance or snooping."
---

# Shared Device Privacy Boundary Card

## Purpose

Help a household turn unclear shared-device expectations into a neutral, printable boundary card. The deliverable is a simple agreement covering devices, accounts, private zones, sign-out rules, guest use, downloads, repairs, and what to do when someone feels a boundary was crossed.

This is a prompt-only household admin workflow. It is consent-first and does not help with surveillance, snooping, secret monitoring, hidden tracking, password theft, or bypassing another person's privacy.

## Use This Skill When

Use this skill when the user wants to:

- Set rules for a shared laptop, tablet, desktop, game console, smart TV, browser profile, streaming account, printer, or family device.
- Reduce household friction around logged-in accounts, search history, notifications, photos, documents, purchases, downloads, and recommendations.
- Make a guest-use checklist for visitors, housemates, babysitters, relatives, or short-term renters.
- Decide which zones are private, shared, kid-safe, admin-only, or okay for guests.
- Prepare a repair, lending, travel, or school handoff so private content is protected transparently.

Do not use this skill to catch someone, spy on a partner, read private messages, monitor employees, bypass passwords, install hidden trackers, recover someone else's account, inspect browser history without consent, or collect evidence by violating privacy.

## Best Inputs

Ask only for details needed to make the card practical. If details are missing, proceed with placeholders.

- Devices involved: laptop, tablet, phone, desktop, smart TV, console, e-reader, printer, router, or shared browser profile.
- People or roles using them: adult household members, children, guests, caregivers, housemates, repair technician, or school use.
- Account types: operating system accounts, browser profiles, streaming apps, shopping accounts, cloud storage, email, calendars, photos, games, and payment profiles.
- Shared tasks: watching media, homework, printing, browsing, shopping, video calls, gaming, travel, or temporary guest access.
- Private zones: email, messages, photos, documents, password managers, banking, health portals, work apps, school apps, calendars, journals, downloads, and cloud folders.
- Current friction: people stay logged in, recommendations get mixed, purchases happen accidentally, notifications pop up, guests use the wrong profile, or files are misplaced.
- Household tone: formal, friendly, roommate-style, parent-child, partner agreement, or guest card.

Avoid asking for passwords, security answers, private messages, private photos, bank details, or account recovery details.

## Workflow

1. **Name the shared context.** Identify the devices and the normal shared uses.
2. **List users and roles.** Use names, initials, or roles only as needed for the card.
3. **Separate zones.** Mark each area as shared, private, ask-first, adult-admin, child profile, guest-only, or repair-ready.
4. **Write consent-first rules.** Turn friction into clear rules: ask before opening another profile, sign out after use, use guest mode, do not inspect history, do not open notifications, and do not change settings without agreement.
5. **Define sign-out and cleanup steps.** Include browser profiles, downloads, tabs, shopping carts, streaming profiles, cloud files, print jobs, and payment methods.
6. **Add guest-use rules.** Provide a short checklist for visitors and temporary users.
7. **Plan repair or lending handoff.** Include backup, sign-out, remove private files from the shared surface, disable visible notifications, and document what the technician or borrower may access.
8. **Add boundary repair steps.** If a rule is crossed, use a calm script: stop, do not dig further, tell the affected person, reset access, and revise the card together.
9. **Produce the card.** Keep it printable and friendly enough to place near the device or save as a note.

## Output Format

Return the card in this order:

1. **Shared Device Snapshot**

| Field | Detail |
|---|---|
| Devices covered | |
| Regular users or roles | |
| Guest users | |
| Main shared uses | |
| Current friction | |
| Assumptions | |

2. **Printable Boundary Card**

```text
SHARED DEVICE PRIVACY BOUNDARY CARD
Device or area:
Shared uses:
Private zones:
Ask-first zones:
Guest mode:
Sign-out rule:
Downloads and files:
Purchases and payments:
Notifications:
If a boundary is crossed:
Card review date:
```

3. **Zones and Rules Table**

| Zone or app | Access level | Rule | Owner or reviewer |
|---|---|---|---|
| | Shared | | |
| | Private | | |
| | Ask first | | |
| | Guest only | | |

4. **Guest-Use Checklist**

Use checkboxes:

```text
[ ] Use the guest account, guest browser, or assigned profile only
[ ] Do not open saved email, messages, photos, documents, or notifications
[ ] Ask before downloading, installing, buying, printing, or changing settings
[ ] Save files only in the agreed guest folder or send them to yourself
[ ] Sign out of apps and websites before leaving
[ ] Clear temporary guest files if the household asks
[ ] Tell the owner if you accidentally open something private
```

5. **Repair, Lending, or Travel Handoff**

Include:

- What the borrower, technician, guest, or school may access.
- What the owner will sign out of or remove from the shared surface first.
- What is backed up and where the owner can find it.
- What notifications are turned off visibly and transparently.
- What needs to be checked when the device returns.

6. **Boundary Reset Script**

Provide a short script such as:

```text
I opened or saw something that was not meant for me. I stopped and did not keep looking. I am telling you now so we can reset access and adjust the shared-device rule.
```

7. **Open Questions**

List missing device names, profiles, private zones, guest needs, purchase rules, parental-control decisions, repair date, or household review date.

## Message Style

- Keep the tone neutral, practical, and non-accusatory.
- Use plain English, checkboxes, and short rules.
- Focus on prevention, consent, and clarity rather than blame.
- Use "ask first" and "shared by agreement" language.
- Recommend separate accounts, guest profiles, and sign-out habits when helpful.
- Do not moralize, escalate conflict, or encourage evidence gathering.

## Safety Boundary

- Do not provide instructions for surveillance, spying, hidden cameras, spyware, keyloggers, secret screen recording, hidden location tracking, or covert monitoring.
- Do not help bypass passwords, locks, two-factor authentication, parental controls, work controls, school controls, or account recovery.
- Do not help read another person's messages, files, photos, browsing history, location history, cloud backups, deleted files, or private notifications without clear consent.
- Do not frame privacy boundaries as a way to catch, trap, shame, or control someone.
- For children or dependent adults, keep guidance transparent, lawful, age-appropriate, and safety-focused. Encourage clear household rules and qualified local advice when legal, custody, workplace, or safeguarding issues are involved.
- If the user describes immediate danger, coercion, stalking, domestic abuse, or threats, prioritize local emergency services, trusted support, and safety planning rather than device inspection.

## Example Prompts

- "Make a shared tablet privacy card for our family room."
- "Create guest laptop rules for visitors without making it awkward."
- "We share a smart TV and keep mixing profiles. Build a boundary checklist."
- "Write a repair handoff card so I protect private files before taking in my laptop."