Privacy and safety
A system that watches a home must answer hard privacy questions before it ships. These are our answers, written while the system is still a plan: every safeguard is labeled PLANNED or IMPLEMENTED, and nothing is implemented.
Pre-prototype. Every visual is concept imagery.
Sensor data collection · Planned, not implemented
This page describes the design intent for a system that does not exist yet. Nothing is implemented, so no data is being collected by Kore today. Every safeguard below is marked PLANNED or IMPLEMENTED.
Temperature, humidity, pressure, and VOC/air quality readings from the room, sampled on a fixed cadence. Used for thresholds, baselines, and the documented record.
Implemented: nothing. No device exists to take these readings.
Motion events from PIR sensing and presence patterns over time, so the system can learn the room's rhythm and notice meaningful absences.
Implemented: nothing. Presence sensing is a planned capability.
Stills or short clips captured on event triggers for visual documentation. The flagship configuration includes cameras; a camera-free configuration is planned for schools, churches, senior living, and similar sensitive settings.
Implemented: nothing. No camera is recording.
Device status, sensor errors, and alert history, so failures are visible instead of silent.
Implemented: nothing. No logs exist.
Cameras and audio · Planned functionality
Kore is being designed as a full ultra-surveillance system, cameras included, for unmatched safety and documentation. Both camera and audio functionality below are planned; neither is implemented.
Planned: cameras capture visual documentation on event triggers, stored locally first, viewable by the owner on the phone dashboard. Planned: recording indicators and clear on-device controls for when cameras are active.
Implemented: nothing. No camera exists, no footage exists, no indicators exist.
Planned: audio event sensing for safety-relevant events (for example, glass-break-like sounds), processed locally, with the same owner-only access as footage. Continuous audio recording is not part of the plan.
Implemented: nothing. No microphone is listening.
Planned: for schools, churches, senior living, and similar sensitive settings, the system can be configured without cameras, using environmental and presence sensing only. Privacy posture follows the setting.
Implemented: nothing. The option is a design commitment, not a shipped mode.
Planned: sensed rhythms and conditions belong to the person they describe. Sharing with doctors, insurers, agencies, or non-profits happens only with explicit opt-in per sharing point. Nothing moves without consent.
Implemented: nothing. There is no Personal Intelligence file yet.
Local vs cloud processing · Planned local-first
The design intent is local-first: sensing, comparison, and alerting happen on the device in the room. This is a plan, not a property of anything built.
Event detection, baseline comparison, and the documented record are planned to run on the local hub. Core monitoring is planned to keep working even if the network drops.
No hub exists, no local processing exists, and no cloud service exists. Any statement about where data lives today is simple: there is no data, because there is no device.
Storage, retention, deletion, user control · All planned
The documented record is the point of Kore, and the owner of the home owns it. Every control below is planned; none is implemented.
Planned: readings, events, and footage stored on the local device first. Implemented: nothing. No storage exists.
Planned: owner-set retention windows, so footage and readings age out automatically on a schedule the owner chooses. Implemented: nothing. No retention policy is enforced anywhere.
Planned: delete any event, clip, or the entire record at any time from the dashboard, with confirmation that deletion completed. Implemented: nothing. There is nothing to delete.
Planned: pause sensing, disable the camera, export your own data, and review exactly what the system recorded and why an event fired. Implemented: nothing. No controls exist.
Encryption and access controls · Planned, not implemented
A safety system that watches a home must protect what it records. The controls below are planned and will be tested on the prototype; they do not exist today, and this page does not claim otherwise.
Planned: encrypted storage on the device and encrypted transport for dashboard access. This page does not claim encryption exists. It does not. It is planned work for the prototype phase and will be listed as implemented only after it is built and checked.
Planned: owner-only access by default, per-person permissions for household members, and per-sharing-point opt-in before any data reaches doctors, insurers, agencies, or non-profits. No access model is implemented.
Human control · Design intent
Kore senses and documents; people act. Consequential actions stay under human control by design.
Planned: Kore alerts the owner and documents the event. It does not call emergency services on its own. The person decides whether to call, and the record shows what they decided.
Planned: sharing sensed data with a doctor, insurer, agency, or non-profit requires explicit opt-in for that specific sharing point. One yes does not open every door. Nothing moves without consent.
Contact and enquiry data · Implemented
This section is about this website today, not the future product. It is implemented, not planned.
Questions
Ask anything about the plan: data, cameras, sharing, or what happens next. Hard questions make the system better.
Interactive 3D · Concept
Drag to spin, pinch or scroll to zoom. Every product, explorable.
