Effective Date: August 31, 2026 Last Updated: November 14, 2026
This Privacy Policy describes how IxomeAI (“we,” “us,” “our”) collects, uses, discloses, and protects your personal information when you use the IxomeAI platform.
What: A UUID (universally unique identifier) generated in your browser and stored in localStorage under the key ixome_user_id. This is your primary account identifier.
How collected: Generated automatically on first visit. You are not required to provide an email address or password to use the Service.
Personal data status: The UUID alone is not personal data under most definitions. However, if combined with a display name, hardware IP addresses, or Stripe customer data, the combination becomes personal data.
What: Your display name (optional), selected system type (Control4, Lutron, or Both), room names you configure during onboarding (stored as a JSON array), your onboarding completion status, and your experience level (numeric preference).
How collected: Provided by you during the onboarding wizard (Steps 0–4) and stored in the users table in our PostgreSQL database.
Personal data status: Display name is directly personal. Room names (“Master Bedroom,” “Home Office”) may indirectly identify you. Room configuration data reveals the layout of your home.
What: Your smart-home system type, room names, and the IP addresses of your Control4 and Lutron systems.
How collected: Provided by you during onboarding and saved to your account.
Sensitivity: Home network IP addresses (e.g., 192.168.x.x) are sensitive because they enable direct communication with physical hardware in your home. These are stored in our database and used to route commands to your devices. They are not transmitted to OpenAI or Anthropic in their raw form — they are used server-side by IxomeAI’s backend to establish hardware connections.
What it talks to: the Control4 controller or the Lutron lighting processor on your home network (at a Control4 home it can also read your Lutron processor, as described below), and Ixome (www.ixome.ai) over an encrypted connection. For a Lutron HomeWorks QS backup (below) it also downloads Lutron’s own programming software from Lutron’s download location (s3.amazonaws.com/HWQS2), and opens Lutron’s two sign-out pages (sso.login.lutron.com and umslogin.lutron.com) in your web browser.
What it sends us: a one-time link code and then its own connection key and version number; what it found while looking for your controller on your home network (this computer’s local address, the address range it searched, how many devices there answered on the two ports a Control4 controller uses, 443 and 5020, and which of them identified as a Control4 controller); your controller’s local address, software version and the name in its security certificate (which contains the controller’s network hardware address); and your Control4 project as your controller reports it: your rooms and devices with their names, each Control4 device’s network details, and its current settings (for example a light’s level). For a Lutron system (HomeWorks QS, HomeWorks QSX, RadioRA 2, RadioRA 3), once a night: your processor’s address and its own programming database as the processor serves it — its areas, the names and numbers of its lights and other outputs, its firmware version and the date it was last saved. One connector at your Control4 home can also take your Lutron system’s nightly read: when your account has just one Control4 system and one Lutron system with us, the Lutron system has no Ixome Connection of its own, and nothing on file says the two are at different addresses (if we have no address for one of them, we treat them as one home), the connector at your Control4 home also takes your Lutron system’s nightly read (its address and programming database, read only). It asks only at the address we have on file for your Lutron processor, never searches your network for one, and what it reads is kept with your Lutron system. Disconnecting the Control4 system on My System stops both, and disconnecting the Lutron system stops the read.
For a Lutron HomeWorks QS backup: only when we start a backup from our side, the app downloads the exact version of Lutron’s own programming software (HomeWorks QS) that your processor runs, from Lutron’s download location (https://s3.amazonaws.com/HWQS2/), checks that it is Lutron’s file byte for byte, and starts its installer, which answers its own setup questions for the versions we have recorded them for; Windows asks you first (unless you have turned those prompts off). It then opens that program and works its menus itself to take two backups of your processor’s programming; it writes nothing to your processor. If the program asks for a Lutron sign-in, the app signs it in with our Lutron dealer login, never yours (Lutron’s program may finish that sign-in in your web browser; the app closes the tab it used). To find Lutron’s sign-in page it looks at the titles and page text of your open browser windows, and keeps none of it. Before it starts it opens Lutron’s sign-out pages in your browser; when the backup is taken, or if it stops part-way, it signs that program out of our login and opens those pages again. If the computer is switched off or the app is closed part-way, our login can stay in that program until we sign it out. Lutron’s program saves each backup file into the folder its Save box shows; the app then moves the file into a folder called IxomeAI in your Windows user folder, sends it to us, and deletes its copy as soon as we have it. If a backup stops before it is sent, its files can stay on this computer, in that folder or where Lutron’s program saved them. The installer it downloaded, its answer file (where there is one) and its install log stay in the IxomeAI folder, so the installer is not downloaded again. Afterwards we can start that program’s own Windows uninstaller to remove it again; you are asked to confirm first.
What it does not do: it does not look at your other devices beyond asking whether those two ports answer (and, to find a Lutron processor, whether a device answering on port 80 serves a Lutron programming database), does not open or read your own files (it reads and writes only its own: its settings and log, and its IxomeAI folder; one exception: if Lutron’s program saves a backup into a folder that already holds a file with the same name, the app moves that file aside while it saves and then puts it back, and if it cannot, the file is kept in its IxomeAI folder, never deleted), and does not record anything you type or view.
What it does on your network: it reads your controller (at a Control4 home, also your Lutron processor, as above); it carries out only the commands you or we start from your Ixome account (for example, turning on a light from chat); and, for work you have paid for, it opens a connection that lets our Control4 software reach your controller (for a Lutron system, it carries our Lutron software’s search for your processor onto your home network instead). That connection lasts for the length of the job, or, if your house is one we keep connected between jobs (we turn that on house by house; it is not part of the Health plan), we keep it open until you disconnect your system on My System. Quitting the app closes it until the app runs again; when it starts again (for example after the computer restarts), we usually reopen it within about ten minutes, unless we are working on your system at that moment. Before a paid job changes your system’s programming or software, we back up your project first.
Sleep: while that connection is open, it asks Windows not to put the computer to sleep for being idle, and stops asking when the connection closes. Closing a laptop’s lid or pressing the power button still puts it to sleep, and that ends the connection until the computer wakes.
How to stop it: quit it from its icon, turn it off under Settings, Apps, Startup, or uninstall it; quitting or uninstalling it also closes any connection it has open, at once (if your house is one we keep connected between jobs, starting the app again reopens it; uninstalling it, or disconnecting your system on My System, stops that). Disconnecting your system on My System stops it reading your system and carrying out commands at once, and we stop opening or keeping a connection through it; to close one it already has open straight away, quit the app as well.
What: Every message you send to the IxomeAI AI system, including natural-language commands (e.g., “Turn off the lights,” “What’s the status of my Control4 system”), and the AI-generated responses to those messages.
How collected: Captured by the LangGraph orchestration layer (backend/agents/chat_graph.py) as LangChain HumanMessage and AIMessage objects, and saved in our database so a conversation can pick up where it left off and so we can see where our answers fall short.
How long we keep it: one year after the last message in a conversation. A nightly job then deletes the whole conversation. Ask us to delete yours sooner and we will, and when you delete your account, we delete your conversations at once (or, if that first delete fails, by the next nightly job).
Transmitted to third parties: YES. Your messages are transmitted to:
What is NOT sent: Your hardware IP addresses, credentials, Stripe customer ID, or push subscription tokens are NOT included in messages sent to OpenAI or Anthropic.
What: A per-user JSON file stored on the IxomeAI server at data/user_memory/{user_id}.json. Contents may include: your preferred hardware interaction patterns, topics you’ve asked about, hardware feedback observed during your sessions, and any preferences the AI has inferred from your interactions.
How collected: Written and updated by backend/agents/user_memory_service.py at the end of each AI session.
Sensitivity: Medium. The memory file does not contain your name or contact information. It contains behavioral data about your smart-home usage patterns.
What: Your Stripe customer ID (stored in the stripe_customer_id field of the users table), your subscription plan and status (user_subscriptions table), payment amounts, and timestamps of payment events.
What IxomeAI does NOT store: Your full credit card number, CVV, or bank account details. These are handled exclusively by Stripe and never transmitted to or stored by IxomeAI.
Stripe’s privacy policy: https://stripe.com/privacy
What: If you opt into web push notifications, we store your full Web Push subscription object (JSON) in the push_subscriptions table. This object contains: an endpoint URL (provided by your browser’s push service, e.g., Google FCM or Apple APNs), a public VAPID authentication key, and a P-256 ECDH key pair for message encryption.
Personal data status: The push endpoint URL identifies your specific browser installation and can be used to send you push notifications. It does not contain your name or email. Push subscription tokens are specific to your browser and device.
Retention: Deleted immediately upon account deletion request or when the push service returns a “410 Gone” error (indicating your subscription is no longer valid).
What: IxomeAI no longer runs a referral or commission program for other businesses and no longer collects data for one. Any records from the discontinued program (a referring business’s name and email address, and its commission records) are retained solely as required for tax and accounting compliance (Terms of Service, Section 6).
What: Each message processed by the AI system generates a ModeratorEvent record in the database, containing: a timestamp, a preview of the message content (first 200 characters), whether the message was blocked, the reason for blocking (if applicable), a session ID, and the channel and source of the message.
Purpose: Content safety monitoring and abuse prevention.
What: Each execution of IxomeAI’s automated background jobs (morning briefings, evening summaries, firmware checks, etc.) generates a ScheduledAgentRun record containing: the job ID, start time, finish time, status, and a result snippet.
Personal data: These logs may contain your user ID if the job ran on your behalf.
What: IxomeAI no longer offers third-party agents, developer registration, or agent purchases, and collects no data for them. Records made before they were discontinued (a developer’s name, email, GitHub URL, agent idea description, approval status and Stripe Connect account ID; for an agent purchase, an AgentSession record with your user ID, the agent ID, the Stripe session ID and payment intent ID, the session status, and any session transcript) may remain in our database.
What: IxomeAI uses Pinecone to power its RAG (Retrieval Augmented Generation) feature. Pinecone stores vector embeddings — mathematical representations — of knowledge base documents about Control4, Lutron, smart-home protocols, and IxomeAI platform knowledge. The current index (ixome-support) contains approximately 6,959+ vectors.
Does Pinecone store your personal messages? Not by design. The RAG system uses your query to search Pinecone (by generating an embedding of your query and finding similar stored documents). The query text itself is processed by OpenAI’s embedding model to generate the vector, but only the query text is transmitted — not your user ID, hardware data, or subscription status.
User data isolation in Pinecone: Pinecone stores a shared knowledge base used to answer questions about smart-home systems. Your personal data, hardware details, account identifiers, and subscription status are not written to Pinecone. Pinecone is used only to retrieve relevant reference documents in response to your queries.
What: Standard server access logs including: IP address of the request, request path, HTTP status code, timestamp, and user agent. These are generated by Heroku’s infrastructure.
Retention: Heroku retains logs for a rolling period (typically 1,500 lines or 1 week), after which they are automatically discarded.
Product analytics (PostHog): IxomeAI uses PostHog (PostHog, Inc., US Cloud region) to understand how visitors move through the site — which pages are viewed, in what order, and where people stop. This is how we find and fix places where the Service is confusing or broken.
What PostHog receives: page URLs viewed, referrer, approximate location derived from IP, browser and device type, and a randomly generated visitor identifier. If you are signed in and take an identifying action, your account identifier may be associated with that visitor identifier.
Session recording — and what is deliberately excluded: PostHog records a reconstruction of the pages you view so we can see where a visitor gets stuck. All text inputs, text areas, and dropdown selections are masked before leaving your browser. That means the text you type — your name, email address, street address, system details, and anything you write into chat or the Design Studio — is not captured in these recordings. Payment card details are entered inside Stripe’s own embedded frames and are never accessible to this or any other script on our pages.
Retention: PostHog retains raw event data and session recordings according to its plan defaults (recordings are retained for a limited window, typically 30 days on the free tier, and then discarded).
Your choice: browser “Do Not Track” and “Global Privacy Control” signals, ad-blockers, and privacy-focused browsers commonly block PostHog outright, and the Service works fully without it. You may also email support@ixome.ai to request that your analytics data be deleted.
The free controller checker: the OS-upgrade checker at /control4-os-upgrade-checker never requires an account or an email address. When you run a check we keep one anonymous record of what was asked and what we answered — the controller model, the OS version band, whether a project is loaded, the verdict we gave, the host name of the site that referred you (for example c4forums.com, never the full referring address), and whether the answer was clicked through to a quote. No email address, no name, no IP address, no account identifier and no cookie is recorded with it, and unless you use the optional box described next, there is no way to connect one of these records back to a person. We keep it so we can tell the difference between “nobody used the tool” and “people used it and it did not help them” — those two look identical otherwise.
If you choose “Email me this answer”: that box is optional. If you fill it in, we keep the address you typed, linked to that one check, so we can send you the answer and at most one short note later asking whether it got done. Reply “stop” to either and we will not write again.
What we set:
| Name | Type | Content | Purpose | Duration |
|---|---|---|---|---|
ixome_user_id |
localStorage | UUID | Account identification | Persistent (until cleared) |
ixome_is_subscriber |
Cookie | “true” or absent | Funnel routing (show/hide subscription banner) | Session or persistent |
| Flask session cookie | Secure cookie | Encrypted session data | Server-side session management | Session |
ph_* (PostHog) |
Cookie + localStorage | Random visitor identifier and session state | Product analytics — see §1.13 | Up to 12 months |
Third-party scripts and cookies: IxomeAI embeds one third-party script: PostHog product analytics (see §1.13 for exactly what it does and does not collect). We do not embed advertising networks, ad-retargeting pixels, social media trackers, or data brokers, and we do not sell or share your personal information with third parties for advertising. Stripe’s payment fields are embedded frames served by Stripe and set Stripe’s own cookies — see Stripe’s privacy policy.
| Data Category | Primary Purpose | Secondary Purpose |
|---|---|---|
| Account UUID | Identify you in the database; route your AI sessions | Link billing records |
| Display name | Personalize AI responses | None |
| Room names, system type | Route hardware commands correctly | Training better routing (de-identified) |
| AI conversation messages | Generate AI responses | Quality improvement (see Section 3) |
| User memory files | Personalize responses across sessions | None |
| Hardware IPs | Connect to your physical systems | None |
| Stripe customer ID | Process payments; manage subscription status | Tax reporting |
| Push tokens | Deliver morning briefings, alerts, push notifications | None |
| Discontinued referral-program records | Tax and accounting compliance | None |
| Moderator events | Content safety; abuse prevention | None |
| Server logs | Debugging; security monitoring | None |
IxomeAI’s AI responses are generated through the Anthropic API (Claude models). Anthropic’s API privacy policy states that Anthropic does not train on customer API data by default. Messages submitted via the API are processed to generate responses and are subject to Anthropic’s data retention policies, available at anthropic.com/privacy.
IxomeAI uses the OpenAI API only to make search embeddings of message text and to transcribe voice input (see 1.4). No OpenAI model writes a response. OpenAI’s API data usage policies state that data submitted via the API is not used to train its models by default.
Retention disclosure: Text and audio sent to OpenAI via the API may be retained by OpenAI for up to 30 days for safety monitoring before deletion, in accordance with OpenAI’s API data usage policies.
IxomeAI does not use your hardware command history, room layout data, or conversation transcripts to train AI models operated by IxomeAI or any third party without your explicit consent. Aggregated, de-identified usage statistics (e.g., “X% of commands are lighting control requests”) may be used to improve the Service.
We do not sell your personal information. We share information only as follows:
Service Providers (Processors):
| Processor | Data Shared | Purpose | Privacy Policy |
|---|---|---|---|
| Heroku (Salesforce) | All data (hosting) | Platform hosting | salesforce.com/privacy |
| Stripe | Stripe customer ID, transaction metadata | Payment processing | stripe.com/privacy |
| Anthropic | AI conversation messages | AI response generation | anthropic.com/privacy |
| OpenAI | Message text for search embeddings; voice recordings, if you use voice input | Knowledge-base search; speech-to-text | openai.com/privacy |
| Pinecone | Query embeddings | RAG knowledge retrieval | pinecone.io/privacy |
| Tavily | Search queries (for research agents) | Web search | tavily.com/privacy |
| LangChain/LangSmith | Conversation traces (if tracing enabled) | Observability | langchain.com/privacy |
| If Google API is used for specific agents | Research | policies.google.com/privacy |
Legal Requirements: We may disclose personal information if required by law, court order, or government authority, or if we believe disclosure is necessary to protect the safety of any person or the security of the Service.
Business Transfers: In connection with a merger, acquisition, or sale of IxomeAI’s assets, personal data may be transferred to the acquiring entity, subject to the same privacy protections.
We implement industry-standard security measures to protect your personal information:
Despite these measures, no method of internet transmission or electronic storage is 100% secure. We cannot guarantee absolute security.
If you discover a security issue, please report it responsibly to security@ixome.ai.
California residents have the following rights under the California Consumer Privacy Act (Cal. Civ. Code § 1798.100 et seq.):
Right to Know: You may request that we disclose: (a) the categories and specific pieces of personal information we have collected about you; (b) the categories of sources from which we collected it; (c) our business purpose for collecting it; (d) the categories of third parties with whom we share it.
Right to Delete: You may request deletion of your personal information, subject to certain exceptions (e.g., information needed to complete a transaction, comply with legal obligations, or exercise free speech).
Right to Correct: You may request correction of inaccurate personal information.
Right to Opt-Out of Sale or Sharing: We do not sell or share personal information for cross-context behavioral advertising. This right is therefore satisfied by our current practices.
Right to Limit Use of Sensitive Personal Information: We do not use sensitive personal information (such as home network credentials) for any purpose other than providing the Service.
Right to Non-Discrimination: We will not discriminate against you for exercising your privacy rights.
How to Submit a Request: Email privacy@ixome.ai with the subject line “California Privacy Request.” We will respond within 45 days, extendable by an additional 45 days with notice.
Verification: Because our accounts are UUID-based and not tied to email addresses, we will need to verify your identity by asking you to confirm your account UUID and at least one other piece of identifying information (e.g., your display name, hardware system type, or subscription plan).
If you are located in the European Economic Area, United Kingdom, or Switzerland, you have rights under the GDPR and/or UK GDPR. Your rights include:
Legal basis for processing: IxomeAI processes your personal data on the following bases:
Data Protection Officer: IxomeAI has not yet appointed a formal DPO. Until one is designated, direct GDPR inquiries to privacy@ixome.ai.
EU Representation: EU residents may direct any GDPR inquiries to privacy@ixome.ai.
International Data Transfers: Your personal data is processed in the United States. If you are located in the EEA, this constitutes a transfer of personal data to a third country. IxomeAI relies on Standard Contractual Clauses (SCCs) where applicable.
Residents of other U.S. states with comprehensive privacy laws (Virginia, Colorado, Connecticut, Texas, Oregon, Montana, etc.) may have similar rights. Contact privacy@ixome.ai to exercise any applicable state privacy rights.
The Service is not directed to children under 13. We do not knowingly collect personal information from children under 13. If children live in a household that uses IxomeAI, note that:
(a) Children under 13 should not be given access to the AI chat interface;
(b) HVAC, lock, and security camera control commands issued by or on behalf of minor household members are the responsibility of the adult account holder;
(c) The Children’s Online Privacy Protection Act (COPPA, 15 U.S.C. § 6501 et seq.) requires verifiable parental consent before collecting personal information from children under 13. IxomeAI does not have a mechanism for verifiable parental consent and therefore does not knowingly permit children under 13 to create accounts.
If a child under 13 has used the Service, contact privacy@ixome.ai and we will delete any associated data promptly.
See Section 12 of the Terms of Service for the complete retention schedule. Summary:
| Data Type | Retention Period | Deletion Method |
|---|---|---|
| User UUID, profile, room names | Until deletion request + 30 days | SQL DELETE cascade |
| User memory files | Until deletion request | File system delete |
| Push subscriptions | Immediately on deletion | SQL DELETE |
| Chat conversations | 1 year after the last message, or sooner on request, and at once when you delete your account | Nightly cleanup job; SQL DELETE on account deletion |
| Moderator events | 90 days, and at once when you delete your account | SQL DELETE via cleanup job; SQL DELETE on account deletion |
| Stripe billing records | 7 years (legal requirement) | Retained; customer ID only |
| Hardware command audit logs (future) | 3 years | SQL DELETE |
| Server access logs | 1 week (Heroku rolling) | Automatic |
| LangSmith traces | Per LangChain policy | LangChain dashboard |
Backups of your home’s system are kept 90 days after your profile is deleted, then deleted — unless someone else still owns that home.
Privacy inquiries: privacy@ixome.ai
Security disclosures: security@ixome.ai (see responsible disclosure policy)
Mailing address: Ixome, 3701 Dorothy Lane, Waterford, MI 48329