Data privacy
Scope
Operator-facing guidance on what data the robot/device captures, how to talk about it in public, and what to not say. This SOP synthesizes the homeowner-conversation guidance from the PortalCam SOPs and the public-interaction guidance from SOP V3.
Purpose
Reduce risk that operators inadvertently mis-describe data collection in ways that create legal, customer, or PR exposure.
Hard scope boundary
Exterior only. No interior scans. No window-focused capture.
[SOURCE: WEB Portal Scan §"Homeowner Conversation Guide"]
Soft scope description
“Focused mainly on the front walkway — entry path, steps, curb.”
[SOURCE: WEB Portal Scan]
What to say
| Concept | Use |
|---|---|
| The work | ”Measurements”, “heat map”, “walkway map”, “measurement view” |
| The device | ”This is the device I use to capture measurements” |
| The purpose | ”Accessibility tech”, “navigation tech” |
| The area | ”Front entry area”, “front walkway” |
[SOURCE: WEB Portal Scan §"Use Instead" table]
What NOT to say
Avoid these terms in homeowner / public conversations: [SOURCE: WEB Portal Scan §"Never Say"; Outdoor PortalCam SOP §9.2]
- AI
- Recording
- Surveillance
- Model training
- Dataset
- Computer vision
- LiDAR
- “Scanning your house”
- “Collecting images of your home”
Standard responses
Opener
“Hi, I’m doing quick exterior measurements for accessibility and navigation tech. Focused on the front walkway — usually under 10 minutes. Would you be open to a quick one?"
"What is that device?”
“This is the device I use to capture measurements.” Show heatmap preview if helpful. Do not name the technology.
”Why does it matter?”
“More variety in real walkways = better navigation tech.” Frame as general future value. Do not promise a specific product or timeline. [SOURCE: Outdoor PortalCam SOP §9.5]
”Why this neighborhood?”
“We’re looking for variety — different curb heights, steps, slopes, and materials. That variety helps make navigation more reliable.” [SOURCE: Outdoor PortalCam SOP §9.7]
Privacy concerns
“Exterior only, focused mainly on the walkway, pointed down.” Do not argue. Reassure scope. Offer control: “If there’s any area you want me to avoid, just let me know.” [SOURCE: Outdoor PortalCam SOP §9.6]
If they say no
“Completely understand. Thanks for your time — have a great day.” Do not push. Do not linger. [SOURCE: Outdoor PortalCam SOP §9.8]
Flustered reset
If you start rambling, reset to one sentence:
“It’s a quick exterior heat map of the front walkway to help improve accessibility navigation.” [SOURCE: WEB Portal Scan + Outdoor PortalCam SOP §9.9]
Confidentiality (operator-side)
Skild is a startup working on sensitive technology. Confidentiality is paramount. Do not share, post, or discuss any of the work you do or see or interact with at Skild. This includes LinkedIn / Glassdoor public posts. Do not take photos or videos of machines, software, employees, or anything inside the office. Failure to adhere will result in immediate off-boarding.
[SOURCE: Operator Onboarding Guide Pittsburgh]
Public-context capture (LGA / indoor)
For the GO2W at LGA: [SOURCE: SOP V3 §III "Public Interaction" + §XV "Data Collection via Camera"]
- Public curiosity is expected. Brief, friendly interactions are part of the job.
- Physically decline any attempt to touch or interact with the robot.
- On-demand image capture via the browser camera button is supported and used for engineering data requests.
- Capture variety over volume: 10 images from 10 different angles is more useful than 50 from one angle.
[SOURCE: SOP V3 §XV "Variety Over Volume"]
- Capture variety over volume: 10 images from 10 different angles is more useful than 50 from one angle.
What this SOP does NOT cover
- Server-side data retention, redaction, and access policy — lives outside this document. Likely policy doc exists on Drive or is being developed; flag for later resolution.
- Legal-jurisdiction-specific consent law (state, country) — out of scope; site-level policy lives in
/sites/. - Customer-contractual data-handling commitments — see relevant deployment in
/deployments/.
Why this SOP is draft
- The only source-grounded content is operator-facing conversation discipline.
- Underlying data policy (retention, redaction, sharing, retention windows, PII handling) is not present in any source available. Likely lives in Linear / Drive policy docs not yet surfaced (BACKLOG B-B7).
Source notes
[SOURCE: WEB (Current) Portal.Scan.Final.SOPReal.docx]V2 — Homeowner Conversation Guide section.[SOURCE: Outdoor_PortalCam_Scan_SOP.docx]— §9 (Homeowner-facing conversation guide).[SOURCE: GO2_Standard_Operating_Procedure_V3.docx]§III (Public Interaction), §XV (Data Collection via Camera).[SOURCE: Operator Onboarding Guide Pittsburgh]— confidentiality clause.
Related
- /projects/customer-consent/door-knock-script/ — the full at-the-door script.
- /projects/customer-consent/home-scanning-consent/ — the formal consent form workflow.
- /general/safety/ — public-interaction safety guidance.
- Site/jurisdiction-specific privacy policy lives in
/sites/.