DATA & PRIVACY
Home cues are processed at home.
This page describes the processing intended by the open-source Élise OS code and the public website. Actual processing depends on how each installation is configured and hosted.
Last updated: September 30, 2026
Scope and controller
Élise OS is open-source software distributed under the AGPL-3.0-only licence and designed to run in the home. The project does not automatically receive data produced by an installation. Each person or organisation configuring a household determines its purposes and access; that operator must inform the people concerned and identify the controller they can contact.
The public website is an independently led project in France by Paul Breton. Contact: contact@paulbreton.dev. The website host may process technical connection data to deliver and secure its pages; the host identity and log retention depend on the hosting service in use.
A single legal basis and all obligations for every home cannot be set by the software alone. The controller for each installation must determine them based on its use and the data processed.
Data and purposes
Depending on enabled features, an installation may process account and session information, household member names and roles, information entered in journal or calendar features, normalized sensor events, and alerts used to support the household. These cues may reveal daily routines and must be protected as personal information.
Sensors send structured facts needed to operate the service. Cameras are optional and separate from these cues: their images and audio are not ingested into observations or AI analysis. A configured camera may contribute only a normalized person-presence fact.
If mobile notifications are enabled with the user’s permission, the installation stores an Expo push token, mobile platform and, when available, device name. An alert notification contains generic text, the alert type and identifier, and its priority so the app can open it; details remain in the household space.
Cameras, intercom and video calls
Live video is relayed on demand through a five-minute signed session. Intercom audio is transmitted only while the user deliberately holds the control and is not recorded by Élise OS. Camera stream credentials are encrypted at rest. Camera access and changes to privacy or consent settings are logged.
OWNER, ADMINISTRATOR and CAREGIVER roles may view configured cameras. Only OWNER and ADMINISTRATOR roles may add or reconfigure them. An explicit consent confirmation is required to configure a camera in a bedroom or bathroom. The household controller must make sure the information and consent are appropriate to the situation.
Video calls use the Jitsi server configured for the installation. Audio and video are transmitted to that server during the call; the server operator and participants may access them according to its configuration. The server may be self-hosted or provided by a service chosen for the installation. Check its terms and location before use.
Élise OS cannot verify that a third-party camera has stopped recording when an app-only privacy mode is used. A hardware privacy control is preferred.
Recipients and transfers
Household data is processed on the local installation and made available to authorised members according to their roles. Remote family access may use a household-managed VPN. The software maintainer does not automatically access this data.
To deliver notifications, the server sends the token and minimal notification content to Expo Push. Apple Push Notification service or Firebase Cloud Messaging is then involved according to the mobile operating system. Expo and these services receive the technical information needed for delivery; their own terms and retention practices apply.
Video calls transmit audio and video to the configured Jitsi server. Webhooks or other external integrations receive data only when explicitly configured. The household controller must document chosen providers, their access, any transfers outside the European Economic Area and applicable safeguards.
Retention periods
The project’s documented reference configuration uses the following periods. An installation may have been customised; its controller should check the actual settings and inform the people concerned.
- Detailed observations: 90 days.
- Completed delivery jobs and technical operational records: 30 days.
- Journal summaries: up to two years by default.
- Accounts and audit records: until account or household deletion, subject to integrity requirements.
- Alert snapshots: 24 hours, stored locally and excluded from normal backups.
- Push subscriptions: kept by the installation while registered; delivery logs follow the technical-log retention period. Revoking phone-level notification permission may not remove the subscription stored on the local server.
Public website
The current website source includes no audience measurement tool, advertising pixel or collection form. Fonts, images and logos are served with the website. The page address determines the language. As with any website, its hosting infrastructure may process technical logs needed to deliver and secure it.
A contact link opens your email application and does not send a message automatically. Information you choose to email is used to respond to your request. Links to third-party websites are subject to their own privacy policies.
Your choices and rights
For household data, contact the controller identified by the person or organisation managing the installation. Depending on the rules applicable to your situation, you may request access, rectification, erasure or restriction, object to certain processing, request data portability, or withdraw consent. You can also ask the household controller to stop a camera or intercom feature.
For a request about the public website or the project, email contact@paulbreton.dev. If you believe your rights are not respected in processing subject to French law, you may lodge a complaint with the CNIL.
Data exports should be encrypted before they leave the home. The installation controller is responsible for protecting network settings, backups and any service providers used.
Information & privacy
- Project publisher
- Élise OS is a project led individually in France by Paul Breton. Contact: contact@paulbreton.dev. The site is hosted by Netlify, Inc. (netlify.com).
- This website
- This version has no analytics or data collection form. Fonts and images are hosted with the site. Video calls may use Jitsi when a call is started; they remain separate from local household context. The language is determined by the page address. To show the latest Élise release, pages query GitHub’s public API from your browser; downloadable files are served by GitHub.
- Getting in touch
- An email link opens your email application. The site does not send messages automatically. Information you choose to send by email is used to respond to your request; you can write to the same address to request its deletion.
- Images and availability
- Screenshots come from a demonstration installation using fictional data. They show the prototype’s actual interfaces, but are not evidence of field effectiveness or complete hardware compatibility. Élise is in development and does not replace an emergency service or a professional.
- Product licence
- Élise OS is open-source software distributed under the AGPL-3.0-only licence. Its Docker architecture is designed for Raspberry Pi 4/5 and mini PCs.
This page describes the reference technical behaviour of open-source software. It is not legal advice or a certification of GDPR compliance. Each installation controller must check the features actually enabled, their legal basis, service providers and the information supplied to affected people.