Legal
Privacy Policy.
For RLSAND Inc. and the RLSAND HOME app.
RLSAND Inc. ("we", "us") respects your privacy. This policy describes the limited information we collect, how we use it, and how to contact us.
Your use of the app is also governed by our Terms of Use (End-User License Agreement).
What we collect
RLSAND HOME app
Your HomeKit data — rooms, accessories, scenes, sensor names, automation rules — is managed by Apple's HomeKit and never reaches our servers. (HomeKit itself may store and sync this across your own Apple devices and home hubs — that's Apple's framework, not us.) The app reads your HomeKit data on your device to show and change your automations. Two features can send a little of it off your device, and only when you choose to:
- Product docs: to find a device's manual, you can choose to have your web browser search Google for the device's maker and model (or its kind, such as "smart plug", when the model is missing). The app shows the search first; the device's name and room are never part of it.
- Private Cloud Compute (iOS, iPadOS or macOS 27 or later, only if you allow it): some of your AI Wizard messages go to Apple as you typed or confirmed them. Besides fixed instructions, the app may add general descriptions built from your home's setup, such as an automation's parts for advice (“a motion sensor turns on 2–3 lights”) or the choices in a question (“option 1: battery motion sensor”), but never adds a name from your home. See Private Cloud Compute below.
Two other features pass some of it to Apple's own services for you. Siri and Search (on unless you turn it off) adds the names of your rooms, devices, scenes and automations to the Search index on your device. From version 1.0.10 (build 186), iCloud sync (off until you turn it on, on any of your devices) keeps your paired shades in your own iCloud as private codes, with any name you gave a pair. Earlier versions kept more of it in your iCloud (before 1.0.8, some even with sync off); see “iCloud sync” and “iCloud in versions before 1.0.8” below. Anything you export and share yourself goes where you send it.
AI features. When you describe an automation in your own words ("turn the kitchen lights on when it's dark"), the app understands it on your device, using its own parser and Apple Intelligence (Apple's Foundation Models framework), or, on iOS, iPadOS or macOS 27 or later and only if you allow it, with help from Apple's Private Cloud Compute (see below). From version 2.0, the whole app needs iOS or iPadOS 26 or later, or macOS 26 or later. The Apple Intelligence features need a device that supports Apple Intelligence, with Apple Intelligence turned on. Versions before 2.0 also run on earlier systems (iOS and iPadOS 17 or later and macOS 14 or later; 17.4 and 14.4 from version 1.0.5); on those systems the app does not use Apple Intelligence or any other generative AI model. Apart from Apple's Private Cloud Compute, which you can allow, RLSAND uses no third-party AI service, and your words are never sent to RLSAND.
Microphone and speech recognition. If you choose to talk to the app's AI Wizard or its help assistant, the app asks for access to your microphone. Speaking to the app needs iOS or iPadOS 26 or later, or macOS 26 or later. On earlier systems, where only versions before 2.0 run, the app never uses the microphone. The app uses the microphone only in the AI Wizard's voice conversation and in the help assistant's chat. In the AI Wizard, it listens after you tap the mic, or, from build 164 and once you have allowed the microphone, for a short time after each question the wizard asks, until you pause or stop voice. In the help assistant's chat (from build 186), it listens only after you tap its mic; your words appear in the message field and are sent when you pause speaking, or when you tap Send. In the help assistant's chat, your words are read by Apple Intelligence on your device only. It stops listening when you leave the page; in the help assistant's chat it also stops after it sends on a pause, when you close the chat, switch away from the app, or tap the mic again. Your speech is turned into text by Apple's speech recognition on your device. The app does not record, store, or send your audio: the microphone's sound goes straight to that recognizer, is held only in memory while it is recognized, and is never saved to a file. The recognized words stay on your device, except words you send to Private Cloud Compute in the AI Wizard (described below). If you leave an AI Wizard automation half done to open another page, the app keeps your words and answers in a small file on this device until you save or discard it. Neither your audio nor your words are included in analytics. To recognize names more accurately, the app gives the on-device recognizer the names of your rooms and devices; those names stay on your device. The app's spoken replies are also produced on your device. You can turn microphone access off at any time in your device's Settings and still type instead.
Interrupting the wizard (test versions). In TestFlight versions that offer it, if you turn on Interrupt by speaking in the AI Wizard settings (the AI Assistant page in older test versions; it is off until you do), the microphone also listens while the wizard is speaking, so you can cut in. Your speech is turned into text on your device, and the app does not record, store, or send your audio.
Debug mode for saved automations (from build 183). Debug mode is on unless you turn it off in the app under Settings → Automations. While its Debug page is open, the app reads the sensors and devices of one saved automation on your device and can say what changes out loud using the device's text-to-speech. It never uses the microphone, never changes your home, and nothing about your sensors or devices leaves this device.
Tile alerts (from build 188). Tile alerts are off until you turn them on for a Home-page tile. When they are on, the app shows a notification on this device when one of the tile's devices turns on, opens or unlocks, and only while the app is open; a third-party app hears HomeKit changes only while it runs. The notification is made and shown by your device; nothing is sent to a server. It shows the device's name and the tile's name in the banner and on the lock screen, unless you hide notification previews in your device's Settings. For a tile made of devices you pick, the app keeps those devices' HomeKit identifiers in its storage on this device; they are never synced to iCloud, though they can be part of your device's own backup, like the rest of the app's settings.
Record of Risky Actions. From version 1.0.13 the app keeps a private record of the risky actions it refuses, asks you about or sends (unlocking a door, opening a garage, turning off an alarm, or turning on a heater, a valve, a faucet or an outlet you marked as powering a heater or water), including saving or switching on an automation that does one, repairs of such automations, and each time you turn Allow Risky Actions on or off. Each entry holds when, what the action was, the kind of device, a private code for the device (never its HomeKit identifier), what started it, whether you confirmed, what happened and the app version. It stores no device names. It is kept on this device, is not backed up and is never sent to RLSAND by the app; it leaves this device only if you export and share it. It keeps the latest 1,000 entries at most, none older than two years. It can't be switched off, but you can export it or clear it in Settings → Data & Sharing → Record of Risky Actions; an export includes device names only if you choose. What happened is Sent (HomeKit accepted the command; the record doesn't show whether the device did it), Refused, Not sent or Failed; for the setting itself, Turned on or Turned off. It is stored encrypted on this device and readable once the device has been unlocked after a restart. Anyone who can use your unlocked device can open, export or clear it. It lists only what this app did, including its Siri and Shortcuts actions — not the Home app, other apps, or automations HomeKit runs later — so it is not a security log.
Private Cloud Compute. Only on iPhone and iPad with iOS or iPadOS 27 or later, and on Mac with macOS 27 or later (never on 26 or earlier), where this option is available in your version of the app, and only if you choose to allow it, the app may ask Apple's Private Cloud Compute for help in the cases described here. App Store versions (from build 190) use it for sorting what you say, your answers to the app's questions, and advice. Test (TestFlight) versions may also use it for a second opinion on your requests (only with the tester switch "Try Private Cloud for unclear requests" on) and for a question about the app asked in the AI Wizard, sent with up to three of the app's own help pages. Each request the app sends counts toward Apple's daily Private Cloud limit for your Apple Account; once the app knows that limit is reached, it sends nothing more until the limit resets. Your choice in Settings → AI Wizard → Private Cloud is kept on this device only and works like this:
- Allow: the app sends in these cases without asking each time.
- Ask (the starting choice): the app asks before advice and the second opinion; everything else stays on your device.
- Never: nothing is sent.
After three "Not Now" answers in a row, the app stops asking and points you to Settings once; making any choice there resets this. If a later version adds a new use, an earlier Allow doesn't cover it; the app asks again, or keeps that use on your device. Exception: in TestFlight versions, an Allow given for advice also covers questions about the app.
The cases, one by one:
- A second opinion on your requests (iOS, iPadOS and macOS 27 or later; from build 155; currently only in test (TestFlight) versions). Words you submitted to the AI Wizard (typed and sent, or read back and confirmed with "yes") may go to Apple's Private Cloud Compute when your Private Cloud choice allows it (only with the tester switch on): a request the app cannot fully understand on your device. Only a request you submitted yourself can be sent. RLSAND Inc. never receives them. You can choose Never at any time in Settings → AI Wizard → Private Cloud.
- Your answers to the app's questions (iOS, iPadOS and macOS 27 or later; from build 190 also in the App Store version). When the app asks you a question, such as which sensor to use, and you answer in your own words instead of picking a choice, the app first tries to match your answer on your device. If it can't, your answer may be sent together with short, generic descriptions of the choices, such as "option 1: battery motion sensor". These descriptions are built only from a fixed list of generic words — the kind of device, how it is powered and its place in the list — never from the names you gave your home, rooms, devices or people. Your answer itself is sent as you wrote it, so if you typed or said a name from your home, that name goes with it; the app never adds one. Answers are sent only if your Private Cloud choice is Allow (set in Settings, or by tapping “Always Use Private Cloud” when the app asks). The app never asks about an answer, so with Ask or Never your answers stay on your device. A typed answer can be sent once you send it; a spoken answer only after the app reads it back to you and you answer with a clear "yes".
- Sorting what you say to the AI Wizard (iOS, iPadOS or macOS 27 or later, on a device that supports Apple Intelligence; from build 184 in test (TestFlight) versions; from build 190 also in the App Store version). When you type or speak to the AI Wizard and neither the app's rules nor the on-device model can tell whether your words describe an automation, and only if you have allowed Apple Private Cloud Compute, the app may send your own words, and only those words, exactly as you sent them, to Private Cloud Compute to decide. Sorting sends only your own message, exactly as you sent it: typed text as typed, or spoken words after the app has read them back and you have said a clear "yes". The app adds nothing about your home, and a message that uses a name the app recognizes in your home (a room, device, sensor, scene, automation, or a nickname) is never sent for this. It happens at most once per message, not once the app knows Apple's daily Private Cloud limit is reached, and the reply only decides where your words go; it never builds an automation. Apple says the data it processes in Private Cloud Compute is “processed only to fulfill your request” and “is not stored or made accessible to Apple” (Apple Intelligence & Privacy). RLSAND Inc. never sees your words.
- Advice (iOS, iPadOS or macOS 27 or later, on a device that supports Apple Intelligence; from build 190, including the App Store version). When you ask the AI Wizard how to improve or test an automation and the app can't answer on this device, the app may send Private Cloud Compute your question and a description of the automation's parts in general words (for example “a motion sensor turns on 2–3 lights”). The description uses only a fixed list of general words, such as the kinds of trigger, check and action, and rounded numbers (counts, times, light levels and other sensor thresholds). The app adds no names — never names of your home, rooms, devices or people, sensors, scenes or automations — and no dates, a device's maker and model, or which room something is in (only whether a sensor is in the same room or another room). If your question uses a name the app recognizes in your home, the app answers on this device and sends nothing. A typed question goes as you sent it; a spoken question only after the app reads it back and you say a clear “yes”. It happens at most once per question, and not once the app knows Apple's daily Private Cloud limit is reached. The reply is text, with at most one suggested change you can accept with Yes or decline; nothing is changed without your yes, and advice never saves anything to your home by itself.
- Questions about the app (iOS, iPadOS or macOS 27 or later, on a device that supports Apple Intelligence; from build 208, only in test (TestFlight) versions). A question about the app that you ask in the AI Wizard, and that the app can't answer on your device, may be sent with up to three of the app's own help pages. Nothing about your home is added, and a question that uses a name the app recognizes in your home is never sent. It is sent only when your Private Cloud choice is Allow; an Allow given for advice also covers these questions.
Sorting, advice and questions about the app never send your words when they use a name the app recognizes in your home, or even one word of such a name: the names of your home, rooms, zones, devices, sensors, scenes and automations, your own name in Settings, and nicknames the app has learned. Your own-words answers, and the TestFlight second opinion, are sent as you wrote them, so they can include a name you used. Besides your own words, the app sends Private Cloud Compute only its fixed instructions and question wording, the generic descriptions above and, in TestFlight versions, the app's own help pages with a question about the app. The app never adds a name from your home, and your home's list of rooms, devices or sensors and your audio are never sent. RLSAND never receives any of it.
iCloud sync. If you turn on iCloud sync in the app's Settings, your app preferences (such as display, units, voice and AI settings, your name and the assistant's name; your Private Cloud choice and Allow Risky Actions stay on each device) are stored in your own iCloud account through Apple's iCloud service, so they match on your devices. RLSAND cannot access your iCloud account. From version 1.0.13, the app does not copy your home's names, rooms or accessory list to iCloud (a name you give a pair of shades is the one exception; see Paired shades below). Before version 1.0.13, the list of HomePods and Apple TVs the app found on your Wi-Fi (their names, models and network hardware IDs) was also kept in your iCloud: from version 1.0.8 only with iCloud sync on, and in earlier versions, such as 1.0.4, whenever you were signed in to iCloud, even with the app's iCloud sync off. From 1.0.13 it stays on each device. Version 1.0.13 (build 218) and 2.0 build 219 delete the old iCloud copy the first time they run with iCloud sync on; until then, while sync is off, any old copy stays, and an older version on another of your devices can put it back, even after it was deleted. From 2.0 build 220 (for now only in TestFlight test versions), the app deletes that old iCloud copy each time it starts, whether iCloud sync is on or off, so a copy put back by an older version on another device goes away too. Deleting sends none of your data. From version 1.0.8, if iCloud sync is off, the app writes no preferences or pairing codes to iCloud; it writes only the on/off choice itself there, saved when you change it, so your other devices can follow it. Turning sync off does not delete what was saved while it was on. The secret keys the app uses to make the private codes it syncs (one shared key ring; see Paired shades below) stay in your iCloud Keychain (end-to-end encrypted) whenever iCloud Keychain is on, even with the app's iCloud sync off; they hold no information about your home. Temporary copies of your home's layout that the app keeps to start faster are stored on your device, encrypted until you first unlock it after a restart, and left out of device backups.
iCloud in versions before 1.0.8. Versions before 1.0.8, such as 1.0.4, kept more in your iCloud. The HomeKit identifiers mentioned here are ID codes HomeKit gives each room, device and automation; they contain no names.
- Whenever you were signed in to iCloud, even with the app's iCloud sync off: the list of HomePods and Apple TVs described above; for each automation you saved from one of the app's templates, HomeKit's identifier for that automation with the template's title, which can include a room's name (for example “Kitchen: Lights on when motion”); and, as later versions do, the iCloud sync on/off choice itself.
- Also, with iCloud sync on: nicknames the app learned (your word; the name and room of the device, room, sensor or scene it stands for; how often you confirmed it, and when it was created and last used); a darkness level for each room, listed by HomeKit's room identifier; which automations are paired, by HomeKit's automation identifiers; and your paired shades, with HomeKit's identifiers for the room and both motors, the pair's name (made from your devices' names unless you renamed it) and motor settings, plus the pairings you said No to, stored as the two motors' identifiers.
From 1.0.8 the app no longer writes the template list, nicknames, darkness levels, paired automations or these shade pairings to iCloud (for the HomePod and Apple TV list, see above), and it deletes the template list from iCloud each time it starts, whether sync is on or off. With sync on, 1.0.8 and later copy the old nicknames, darkness levels, paired automations and shade pairings onto the device once and then stop reading them. Those old copies stay in your iCloud for now, and a device still running an older version keeps using and updating them.
Paired shades. With iCloud sync on (from version 1.0.10, build 186), your paired shades, and the pairing suggestions you said No to, also sync between your devices. (Versions before 1.0.8 also synced paired shades with sync on, using HomeKit's identifiers instead of private codes; see above.) The shades themselves are identified only by private codes the app makes from HomeKit's identifiers with a secret key; without that key, the codes can't be matched to those identifiers. A name you gave a pair and its motor settings sync with them. That key ring, which also makes the private IDs Siri and Shortcuts use (since version 1.0.8, build 144), is kept in your iCloud Keychain, end-to-end encrypted, whenever iCloud Keychain is on. From version 1.0.8, other settings tied to a specific room or device, such as darkness levels, paired automations and learned nicknames, stay on each device and are not synced between your devices for now (earlier versions synced them; see above).
Siri and Search. The app can add the names of your rooms, devices, scenes and automations, with the room and kind of device, to the Search index on your device, so they appear in Search and Siri Suggestions and help Siri find them. Versions before 2.0 do this from version 1.0.8, and only on iOS and iPadOS 18 or later, and on Mac with macOS 15 or later. When you run a scene or automation in the app, the app also tells Siri about it, so Siri can learn your routines. The words you type or speak to create an automation are never included, and neither are HomeKit identifiers. This is handled by Apple's Spotlight and Siri frameworks, under Apple's privacy practices; RLSAND does not receive this information. It is on by default. You can turn it off in the app under Settings → General → Siri and Search, which removes these names and routines from the index.
Product docs. On a device's page you can tap Product docs to look for the device's manual on the web. The app first shows you the exact search and waits until you tap Search; only then does your web browser open a web search (Google). The search uses only the maker and model of the device (or its kind, such as "smart plug", when the model is missing) and never includes your device name or room. If you tap Cancel, nothing is sent. The search runs in your browser under the search provider's own privacy policy; RLSAND does not receive it, and the app sends no analytics about it.
Analytics (optional). If you choose to share it, the app sends product-interaction analytics through TelemetryDeck: which features are used and basic app events, plus device type, system version and language; technical details such as app version, region, time zone and screen size; how often and how long the app is used; and accessibility and display settings such as text size and dark mode. Each signal carries a code TelemetryDeck's software makes on your device by one-way scrambling (hashing) an identifier Apple gives the app for your device, so signals from one device can be grouped; it is not your name, email or Apple Account. Nothing is sent until you turn it on (on the last page of the app's introduction, or in Settings), and you can turn it off at any time. (This applies from app version 1.0.10. Earlier versions sent these analytics unless you turned them off in Settings.) This data is not linked to your identity, is not used to track you across apps or websites, and contains none of your HomeKit data, request text, audio or spoken words. For voice features it records only counts, such as whether a voice session was started or finished. In test (TestFlight) versions, and in App Store versions before 1.0.11, the analytics also include error and crash counts. Besides what every signal carries, each count adds only the area and kind of problem as a short code (such as a HomeKit error number), the part of the app where it happened, and whether the sample home was in use, never an error message, a name or your words.
Crash reports from Apple (optional in App Store versions). If you turn on Share With App Developers in your device's settings (Settings → Privacy & Security → Analytics & Improvements; System Settings on a Mac), Apple may share crash data and statistics about how you use the app with us. Apple says it shares these only aggregated or in a form that does not personally identify you. We see them in Apple's developer tools and use them only to find and fix problems and to improve the app. You can turn sharing off there at any time; it is also off whenever your device's own analytics sharing with Apple is off. This applies to every App Store version of the app. In test (TestFlight) versions, Apple's TestFlight terms apply instead: Apple automatically collects crash logs and usage information and shares them with us, and this can't be turned off. What we receive can also include the name and email address you were invited with. Any feedback you send through TestFlight reaches us too, including screenshots, which can show your home's names or your requests.
Website & support
If you submit the support form or contact form on this site, we receive the information you provide (name, email, the issue you described, optional device and version metadata). We use this to respond to your request and may keep it in our support email archive; some of it is also recorded in our server log (below).
Standard server logs (IP address, user agent, requested URL) are kept for short periods to support security and debugging. When you send one of the site's forms, our server log also records what you entered except your message: your name and email; on a support form, your device, system and app versions and topic; on the contact form, your company, phone, project type, budget and timeline; on the RLSAND HOME support form, also the product you chose and any automation name you give.
How we use it
- To provide the natural-language and AI features in the app.
- To understand, in aggregate, which features are used so we can improve the app.
- To respond to your questions and support requests.
- To keep our service running and secure.
How we share it
We do not sell, rent, or share your information with third parties for their own purposes. The providers that run the app and site for us are TelemetryDeck (analytics), our email-delivery service and our hosting provider; they get only what they need. Our support inbox, where form messages arrive, is hosted by Google (Gmail) under its own terms. Apple handles data for features you use (Private Cloud Compute, iCloud, Siri and Search, crash reports, TestFlight) under its own terms. Google receives a Product docs search from your browser. AI features run on your device using Apple's frameworks or, only if you allow it and in the cases described above, Apple's Private Cloud Compute; we use no other AI provider. Apple also gives us crash data and usage statistics, under its own privacy terms, as described above. We disclose information only if required by law.
Retention
Support correspondence: kept while it's useful for ongoing support. Server logs: short-lived. Crash reports, usage statistics and TestFlight feedback stay in Apple's developer tools; we don't copy them elsewhere. Apple says it keeps beta feedback for a year and may keep crash data until the bugs are resolved. Ask us through our support form to have your TestFlight feedback deleted. You can ask us to delete your support correspondence at any time. We keep no AI or voice logs: your requests and speech are handled on your device (or, where you allow it and in the cases described above, by Apple's Private Cloud Compute) and reach us only if you send them yourself, for example in a support message or TestFlight feedback.
Your rights
Depending on where you live, you may have rights to access, correct, or delete information we hold about you. Reach us through our support form and we'll respond.
Children
RLSAND HOME is intended for adults setting up and managing a home, and is not directed to children. We do not knowingly collect information from children under 13.
Changes
We'll update this page when our practices change.
Contact
Questions about this policy: use our support form.