Smart Bayit app — Privacy Policy
Last updated: November 20, 2026
Who we are
Smart Bayit is a smart-home service operated by Smart Bayit. Questions and requests: webadmin@bayit.online.
This policy covers the Smart Bayit app, the software inside the Smart Bayit hub in your home, and our cloud services. The bayit.online marketing website has its own policy.
The principle
The hub lives in your home and keeps most information there — devices, automations and household members. Lights, AC, shutters and sensors keep working on your home network without internet. Only what the internet-based services need reaches our cloud.
What we collect, why, and for how long
- Household members (name, and optionally email and phone): on the hub, to manage who is connected and to send join links and PIN-reset emails. The homeowner’s contact details are also kept by us until you ask us to delete them (see “Your rights” below). If any other hub is still linked to you in our records — whatever its state, including one that was replaced or revoked — they stay until the data of the last hub linked to you is deleted. To have them deleted sooner, send us a separate request by email (webadmin@bayit.online); our team handles it by hand.
- A household member’s email and the my.bayit.online account: When the manager adds an email to a household member, the hub reports that email and its permissions to us (manager, invoices and data, site access, whether a code was chosen, a site lock) — no name and nothing else from the home — so that only this email can sign in to the site. Each report replaces the last: a person removed on the hub is deleted from ours at the next report. Whoever signs in to the site chooses a password; we then keep the email, the password in hashed form (never the password itself) and the list of hubs you disconnected from the account; active sign-ins, password links and attempt counters are kept only briefly and deleted automatically. Your personal hub code is never kept by us: it travels encrypted straight to the hub and only the hub checks it, and we hold no key that can operate the home. The account is deleted when you ask us by email (webadmin@bayit.online), or together with the data of the last home that still reports your email. After it is deleted we keep only one number next to a hash of the email — not the email itself — so that a new account under the same email cannot enter the home without being approved again at home; anyone who already knows the email can compute the hash, so this is pseudonymous, not anonymous.
- Installation city/address: to compute Shabbat, holiday, sunrise and sunset times, and — rounded to an approximate location (about 10 km) — to fetch the weather — on the hub and by us, until you ask us to delete it (see “Your rights” below). The app has no location permission.
- Account log: we record account events for the home — activation (including the phone number and place given), a registration whose name or email differs from the one we already hold for that phone number (both versions are recorded), emails we sent, and license and backup check-ins. The entries are kept until you ask us to delete them (see “Your rights” below); the routine license and backup check-ins are also deleted automatically after 180 days.
- Hub identifiers and status: device id, license, software and radio-firmware versions, memory, CPU, disk, uptime and the hub’s time zone (a zone name such as Europe/London, not an address) — for licensing, updates and fault detection, while the hub is active. The hub’s hardware id, whether Shabbat or a holiday is in effect at the hub when it reports, and technical readings — such as memory, CPU, disk and uptime, software versions, the counts of its devices, rooms and automations and the number of chat requests it answered on its own — are also stored as metrics in Cloudflare Analytics Engine. They are not deleted with the home; Cloudflare expires them under its own retention.
- Nightly health report: each night the hub sends the results of its own health checks. The report can include the names of your rules and devices, network addresses and short lines from the Zigbee log. After 35 days we delete the names, network addresses and log lines from the report and cut it off from the hub’s id: it is kept without the home’s id, and we do not link it back to a home. General technical data remains, such as counts (how many checks passed and how many failed), so we can see trends and improve the product. The hub’s boot-card history (versions and radio details) gets the same treatment after 35 days, and health alerts that were closed after 90 days. If many such records pile up, we delete the oldest of them.
- Staff action log: actions our support team takes on your account (for example activation, with the details entered) are recorded — who, what and when — and deleted automatically after 365 days (the default). When a home’s data is deleted, the details recorded in this log about that home are deleted with it: the phone number, the city, the staff notes and your email address when our team emails you. Only who did what, and when, and the hub’s id, stays until the entry deletes itself. When our team marks a chat message from your household that the hub could not understand as handled (or re-opens it), up to 80 characters of that message are copied into this log for the same period; that entry is not tied to the home, so it stays after the home is deleted.
- Your phone’s key: pairing creates a key on your phone; only its public part is stored on the hub and on our relay server, to verify that remote commands really came from your phone — while the phone is paired.
- Relay server: the hub connects to our relay server when remote control is on or while an install or support window is open. Every new hub has an install window of three days from its first activation, and a hub whose plan includes a standing support window (the pilot plan) has a window with no end date: it stays connected for as long as the plan includes it, apart from a pause after the household closes the windows. On each connection the hub sends the state of all its devices (names, rooms and live states), and the relay keeps the latest copy, overwritten on every change, so it can show it when the hub briefly disconnects; the copy has no expiry date and stays until the home’s data is deleted. The relay also keeps the name and public key of each paired phone and, for each linked WhatsApp or Telegram account, an entry whose key contains your id with the provider (for WhatsApp, your phone number) and which also holds your display name; such an entry is deleted no later than the hub’s next connection after the person is removed from it, or with the home’s data.
- Chat: what you type is sent to the cloud to understand the request, together with the names of the home’s devices, rooms, groups, modes and automations and the sender’s name — so the model can match the request to your home. The home’s last 12 chat turns are kept for follow-up questions and are overwritten as the conversation continues. A sentence the hub could not understand on its own is kept to teach it — until reviewed, and up to 365 days after that. Each cloud chat request also leaves a technical usage record — the home’s id, the model that answered, how long it took, whether it worked, the type of action it produced and the token counts, but none of the text — kept for up to 365 days. When the hub reports a device it does not recognise and the AI is asked to identify it, that request leaves the same kind of usage record, under the same id. The hub checks every action the chat proposes before it runs.
- Feedback and AI-answer reports (only if you send them): the text you wrote; for a report on an AI answer, also the answer, the question before it and the reason you chose; and, if you choose, technical details (app version, the phone’s model and system, recent app errors). Deleted automatically after 180 days.
- Device problem reports (only if you send them): the description you wrote and technical details of the device (model, state and short log lines). Kept while the report is waiting to be handled, and deleted automatically once it has been handled and is more than 90 days old.
- Cloud backup (only if your plan includes it): a full backup of the hub: settings (including the installation location and the hub’s own credentials — the MQTT password, the web-access token, the phone-enrollment token and the key to the Zmanim service), rules, device and room names, device keys (Zigbee network, Gree and Tuya) and the home’s journal and chat history. It does not include the household member list or the home’s master PIN, although people’s names can appear inside the journal. The 8 most recent backups are kept; to have backups deleted, see “Your rights” below.
- WhatsApp / Telegram (only if you connect them): the link record — your id with the provider (for WhatsApp this is your phone number) and display name. It is kept after the channel is disconnected, until you ask us to delete it; a household member’s own request deletes this record only. The channel’s other records are deleted only together with the whole home’s data: a usage record of each message or assistant action (the home’s id, time, direction, type, outcome and, for WhatsApp, the billing details Meta reports — never the text), and this home’s channel state in the chat service, including the linked accounts with their id, display name, private signing key and the language of their last message (Hebrew or English), the time of the last message received, a monthly message counter, recent message ids and pending answer options. In addition, requests through these channels are also kept in an anonymous log that is not linked to your home: the day only (no time), the channel and the outcome — for Telegram and WhatsApp also the sentence that was sent (up to 300 characters, with join codes and device identifiers removed), so we can learn how people ask; for an external AI assistant only which action it called, which assistant family it is (Claude, Grok, ChatGPT or other) and whether it worked. The anonymous log is kept for up to 365 days and holds no home or person identifier — so nothing in it can be deleted on request.
- External AI assistant (only if you connect it): you can connect your own AI assistant (for example Claude, Grok or ChatGPT) to the home with your personal join code from the app. The assistant acts with the permissions of the person who connected it: it can control devices, read the home’s state and build or change automations — and it cannot delete an automation, change settings, bypass the PIN, update software or contact support. The hub checks every action before it runs and records it in the journal. What you tell the assistant, and what it receives from the home, passes through its own provider (Anthropic, xAI, OpenAI and others) under its terms, not ours. We keep only: the link record (the assistant’s name and a hashed identifier), its sign-in credentials — stored as hashes, not as text — for up to 90 days from the connection, a monthly action counter, and an anonymous record of which action the assistant called, its assistant family (Claude, Grok, ChatGPT or other) and whether it worked — with no device names, no values and no text. To disconnect: in the app, in the person’s list of connected devices, remove the assistant’s entry — its next request is refused — and you can also revoke access from the assistant’s side. Deleting the home’s data also revokes its sign-in credentials.
- Deletion requests: the contact details you enter, until handled and up to 12 months after, as a record that we did.
What we don’t do
No ads. We don’t sell data. No cross-app tracking. No access to your location, camera, contacts or files.
Service providers processing data on our behalf and under our instructions
Cloudflare (hosting, database, storage, email) · Google (Gemini model — paid service) · Anthropic (Claude model, via Cloudflare AI Gateway) · Meta (WhatsApp — only if you connect it) · Telegram (only if you connect it) · Open-Meteo (weather data — receives only an approximate location (about 10 km), nothing that identifies the home) · WeatherAPI (weather data — receives only an approximate location (about 10 km), nothing that identifies the home) · Anthropic · xAI · OpenAI… (the AI assistant you connect — only if you connect it, under its own terms).
Chat requests sent since October 4, 2026, are recorded by the Cloudflare AI Gateway only as anonymous technical usage records — the model, token counts, duration and outcome — never the content of your message or of the answer, and never which home the request came from.
Under the paid-service terms we use, these providers do not use the content to train models. Data may be processed outside Israel.
Security
Everything that leaves your home is encrypted (TLS). Remote commands are signed with a key created on your phone, and your home’s master PIN never leaves your home. Inside your home the app talks to the hub over plain HTTP on your home network — the hub has no public name a certificate could be issued for — and that traffic stays inside your home.
Support access
Our support team can reach your hub remotely only while an installation or support window is open, and only for its duration. A hub on the pilot plan has a standing support window with no end date, apart from a pause after the household closes the windows.
Your rights
You can view and correct your details in the app.
Deletion: a household member can remove themselves from the home in the app (Settings → Privacy & account). For any other deletion request, including all of a home’s data and cloud backups: https://bayit.online/app/delete-account. We handle requests within 30 days. After deletion we keep the purchase and license record, for warranty and fraud prevention, and a few other records — each is listed under “What we keep, and why” on the deletion page, with why we keep it and for how long.
Children
The app is not directed at children.
Changes
When this policy changes, we update this page and its date.