Privacy Policy

ALYT is an edge-AI smart home platform built on a simple premise: the intelligence that understands your home should live in your home. This policy explains, in as much detail as we can honestly give you, what information ALYT collects, what stays on your own hardware, what reaches our servers, what (if anything) reaches third parties, and exactly how to see, correct, export, or delete anything we hold about you.

We wrote this policy by reading our own source code and database schema, not by adapting a template. Where we were not certain of a fact — a retention period that has not yet been fixed as a business policy, for instance — we say so plainly instead of guessing. You will see a few notes marked [LEGAL-VERIFY] below; those are open items being tracked internally, not gaps we are hiding from you.

1. Who This Policy Covers

This is the privacy policy for the ALYT product — the smart home platform a household uses to control and automate their home. It covers:

• The console web application at app.alyt.com
• The ALYT mobile app for iOS and Android (bundle identifier com.alyt.home)
• The marketing site at alyt.com
• ALYT hub hardware, voice satellites, and any ALYT-branded device
• The voice assistant, automation engine, and connected-device features that run on the platform
• Amazon Alexa integration when you link your ALYT home to an Alexa account

This policy does not cover the ALYT Developer Platform at developers.alyt.com, which is used by third-party software developers building connectors and integrations for ALYT. That platform has its own privacy policy, published at developers.alyt.com/legal/privacy, because developer accounts, API keys, and sandbox usage are a genuinely different relationship from a household using ALYT in their home. If you are a developer building on ALYT and a household running ALYT in your own home, both policies apply to you, each to the relevant activity.

This policy also does not cover the practices of third-party services you choose to connect to ALYT (Sonos, Amazon, Ring, SwitchBot, and so on). Those companies have their own privacy policies governing the data they hold about you independently of ALYT. We tell you, integration by integration, what data passes through ALYT to reach them — see Section 10 — but we do not control, and cannot promise anything about, what those companies do with your data once it is in their systems.

2. Who Operates ALYT

ALYT is a product of Fizzify Inc., a company registered in Wyoming, United States. Fizzify Inc. is the data controller (in the language of GDPR) or business (in the language of the CCPA) responsible for the personal information described in this policy.

Fizzify Inc. also operates a separate corporate website at fizzify.co with its own general privacy policy. That corporate policy is not a substitute for this one: it describes Fizzify's practices as a company in general, while this document describes specifically what ALYT — an IoT, smart-home, security, voice, and AI product — does with your data. Where the two differ on anything relevant to ALYT, this policy controls.

3. The Core Design: Local by Default, Cloud by Choice

Before we walk through categories of data, it is worth explaining the architecture, because it is the reason the rest of this policy reads the way it does.

ALYT's voice and automation intelligence is designed to run on hardware inside your home — the ALYT hub — rather than by default shipping your voice, your habits, and your household's activity to a data center. Wake-word detection, speech recognition, language understanding, and speech synthesis can all run entirely on your own hub using local models. When that is how your household is configured, none of the words you say to ALYT ever leave your property.

That does not mean nothing leaves your home. A cloud-connected product needs an account system, needs to know your devices exist in order to show them to you on your phone away from home, needs to deliver push notifications through Apple's and Google's infrastructure, and needs certain third-party integrations (a handful of connected-device brands only offer cloud APIs, not local ones) to work at all. Where that is true, we say so plainly, integration by integration, in the sections below — we do not want you discovering after the fact that a claim we made was technically true only under conditions we never mentioned.

Two settings sit at the center of this design, and we want you to understand them before anything else:

These are two independent switches, deliberately. A household that wants faster, more capable answers by using cloud reasoning should not be forced to also accept that everything they say is permanently logged. And a household that wants a searchable transcript of what the assistant heard should not be forced to also route their queries to the cloud. Both are opt-in, both default to off, and — this matters — neither can be turned on by an API request; only a household administrator can change them, from the console or the app, because we do not want a bug or a misconfigured integration to silently widen what leaves your home.

4. Account Information

To use ALYT you need an account. When you create one, we collect:

Required

• Email address — used as your unique identifier and for account recovery, security notices, and (if you opt in) product communications
• Password — never stored in plain text; we store only an Argon2id hash, a modern password-hashing algorithm specifically designed so that even if our database were stolen, your password could not practically be recovered from it

Optional

• Display name — shown to other household members and staff who assist you
• Preferences — a small settings object covering things like whether you prefer metric or imperial units and your chosen light/dark theme
• Multi-factor authentication (TOTP) secret — if you enable two-factor sign-in, we store the shared secret used to verify six-digit codes from an authenticator app, encrypted at rest

Automatically recorded

• Last sign-in timestamp
• Email verification status

Your account is the anchor for everything else in this policy: your home, your devices, your voice history (if enabled), and your household members are all tied to it. Deleting your account deletes this information — see Delete Your Account for the complete, itemized breakdown of what is removed and what (narrowly) may be retained.

5. Home, Room, and Device Configuration

Setting up ALYT means telling it about your home. This is where most of the "smart home" data lives, and it breaks down as follows.

5.1 Property (your home)

• Property name — e.g., "Los Angeles Home" — required
• Home address — entirely optional. If you provide it, we geocode it once (convert it to a latitude and longitude) at the moment you save it, and use the resulting coordinates for two specific features: the weather shown on your Dashboard, and sunrise/sunset-based triggers in routines (e.g., a routine that runs "at sunset"). We do not continuously track your location, we do not re-geocode on any schedule, and if you clear the address field, the stored coordinates are cleared with it. Nothing about your location is ever guessed from your IP address or your phone's GPS — the only location ALYT knows is the one you typed in.
• Timezone — used to interpret quiet hours and scheduled routines correctly
• Dashboard layout — which device tiles and routines you have pinned to your home screen

5.2 Rooms

• Room names, icons, and the order you arrange them in
• Whether voice listening is enabled in that room (a room-level, not device-level, setting — turning off "listening" for the Nursery, for instance, silences every voice-capable device physically in that room)
• Quiet hours (start and end time) per room, if you set them, which suppress spoken announcements during those hours
• Announcement volume for that room's speaker
• The tile actions you have chosen for quick control from that room's card

5.3 Devices

• Device names you assign (e.g., "Kitchen Hub", "Guest Room satellite")
• The device's hardware serial number, burned in at manufacturing, and its MAC address — used for warranty tracking, hardware replacement history, and to bind the device to your account securely (never to your Wi-Fi network's IP address, which can change)
• What the device can do — its declared capabilities (voice, audio playback, sensor readings, acting as a Zigbee/Thread/Matter hub, and so on)
• Current online/offline status and the last time it was seen
• The firmware update channel it follows (stable or beta) and its current firmware version
• Per-device settings you configure (for example, a device's own volume or playback mode)

6. Voice and the Assistant

This is the section we think deserves the most care, because it goes to the heart of what ALYT claims to be.

6.1 What happens when you say a wake word

Wake-word detection (listening for "hey Simone," or whichever wake word your hub uses) runs continuously on the hub's own hardware, using a small model built for exactly this purpose. Nothing is recorded, stored, or transmitted while the hub is only listening for its wake word — the model runs on a rolling buffer of audio in memory that is discarded the instant it is evaluated, unless and until the wake word is actually detected.

Once the wake word is heard, the hub begins processing what you say next. Depending on your household's settings, that processing runs entirely on your hub, or (only if you have opted in to cloud reasoning) part of it may be sent to Fizzify's cloud inference service for the language-understanding step.

6.2 Metadata: always recorded

Every completed exchange with the assistant — we call each one a "voice turn" — produces a metadata record. This is recorded regardless of your transcript-storage setting, because it is what lets you (and us) verify that the local-processing promise is actually being kept, rather than just asserted. A voice turn's metadata includes:

• Which device and room the exchange happened in
• Which wake word triggered it, and which "persona" (assistant voice/personality) answered
• Per-stage provenance — a record of which processing node handled speech recognition, language understanding, and speech synthesis, and specifically whether each stage ran locally or left your property
• A single denormalized flag, "cloud used," so it is trivially easy to check — without reading every stage — whether anything about a given exchange reached the cloud
• Timing for each stage, and the total time the exchange took
• How the request was ultimately handled: matched to a pre-defined routine phrase, handled by a built-in command, or answered by an AI language model
• The outcome (success, or a specific failure reason such as "could not reach the model")
• The timestamp

This is what powers the "local share" percentage shown on your Voice History screen — a number computed directly from your own turns, not an assertion we ask you to trust. It reads as blank (not 100%, and not 0%) when your household has no voice turns yet, deliberately, because a perfect score with no evidence behind it would be exactly the kind of hollow claim this whole design exists to avoid.

6.3 Content: transcript and reply, opt-in only

If you do turn transcript storage on, we begin storing the transcript of your speech and the assistant's spoken reply alongside the metadata for every subsequent voice turn. A few things to understand about this setting:

• It is not retroactive. Turning it on does not recover transcripts from before you enabled it — those words were genuinely never written down.
• It is also not "reversible" in the sense of erasing the past. Turning it back off stops new transcripts from being recorded, but any transcripts already stored while it was on remain until you delete them yourself.
• It is independent of cloud reasoning. You can store transcripts of voice turns that were processed entirely locally, and you can use cloud reasoning without storing a word of what was said. The two settings do not imply each other.

6.4 Deleting voice history

Whether or not transcript storage is on, you (or any household member with sufficient access) can delete voice history at any time:

• One turn at a time — from the Voice History screen, hold on any entry and choose Delete
• In bulk, for the whole property or a single device — from the same screen, "Delete All"

Both are hard deletes. We do not soft-delete voice data (mark it hidden while keeping it in the database) — a soft-deleted transcript is still, in every way that matters, a stored transcript, and that is not what "delete" should mean for words you spoke in your own home.

6.5 Who can see voice history

Access to your household's voice history is deliberately wider than access to most other operator-facing data, because the person with the strongest claim to see (and delete) what the assistant heard is the person who lives in the home — not just staff with an administrative role. Any household member with a client-level membership on your property can view and delete voice turns for that property, in addition to platform staff performing support with your authorization.

7. Device State, Telemetry, and Command History

To show you a live dashboard and let automations react to the real world, ALYT collects:

• Current device/endpoint state — on/off, brightness, temperature, lock status, and so on, for every connected device — kept as the most recent known value, not a full history, in most cases
• Telemetry — periodic readings devices report (battery level, signal strength, sensor values)
• Command history — a record of every command you (or an automation) issue to a device: what was requested, whether it succeeded, and — if it failed — the connector's own error message, so a failure can actually be diagnosed rather than just noted
• Reachability history — when a device transitions between reachable and unreachable, and the connector's stated reason, so "why did the Guest Room switch go offline last night" is a question that can be answered from the record rather than guessed at

[LEGAL-VERIFY] As of this policy's effective date, telemetry, command history, and reachability history do not yet have an automatic deletion schedule — they accumulate until a business decision is made about how long to keep them. See Section 19 for the complete retention picture, including what is and is not yet time-limited.

8. Automations and Routines

If you build automations ("routines" in ALYT's terminology — when a trigger happens, if conditions hold, do a set of actions), we store:

• The routine's definition: its name, icon, triggers, conditions, and the ordered list of actions it performs
• Execution history — the last fifty runs of each routine, including what triggered each run, whether a condition stopped it, and a step-by-step account of what each action did

Older runs beyond the most recent fifty are automatically pruned as new ones occur — this is the one category of activity history that already has a built-in retention limit, by design, rather than accumulating indefinitely.

9. Notifications and Push

9.1 In-product notifications

Whenever ALYT generates an alert — a device going offline, a routine completing, a security-relevant event — we record it: its kind, its title and body text, which device or property it concerns, and whether and when you marked it read. [LEGAL-VERIFY] This category also does not yet have an automatic deletion schedule.

9.2 Push notifications to your phone

To deliver alerts to your phone even when the app is closed, we register your device with Apple's Push Notification service (APNs) or Google's Firebase Cloud Messaging (FCM), depending on your platform. This requires us to store:

• Your device's push token — the address Apple or Google gives us to deliver to that specific device installation
• Which APNs environment the token belongs to (a technical detail distinguishing development/TestFlight builds from the production App Store build)
• Optional context: a label for the device, the app version installed, and locale
• Delivery history: whether each push attempt succeeded, and the provider's response if it failed

10. Connected Services and Integrations

ALYT can connect to third-party smart home services and devices. Whether your data reaches a third party's servers — and if so, what data — depends entirely on which integration and which device family you connect. We do not treat this uniformly, because it is not uniform: some integrations are purely local, some are local after an initial cloud-based discovery step, and some are cloud-dependent for as long as you use them. Here is every integration built into ALYT as of this policy's effective date, and exactly how each one handles data:

10.1 Amazon Alexa, in detail

Linking ALYT to Alexa uses a standard OAuth 2.0 flow: you sign in to your ALYT account inside the Alexa app, choose which home to link, and grant Alexa the ability to see and control that home. From that point on:

• Amazon's cloud sends your ALYT server a "directive" whenever you ask an Echo device to do something ALYT-related ("Alexa, turn off the corridor"); this is routed through a small proxy function that runs in Amazon's cloud (an AWS Lambda function, containing no logic of its own — it exists only because Amazon requires this technical shape for its integration) before reaching ALYT's own servers, where all the actual work happens.
• ALYT reports back device names, capabilities, and state — enough for Alexa to know what devices exist and what they currently are — but not your voice recordings from your ALYT hub, not your household's voice history, and not anything from your account beyond what is needed to represent your devices to Alexa.
• Voice commands you give to an actual Echo device are processed by Amazon's own speech systems, per Amazon's own privacy policy — ALYT never sees or hears that audio. Only the resulting directive (e.g., "turn off device X") reaches ALYT.
• Voice commands you give to your own ALYT hub are unaffected by the Alexa link and continue to be processed according to your local/cloud settings as described in Section 6 — none of that goes through Amazon.

You can revoke the Alexa link at any time, either from ALYT's Settings → Linked Services, or from the Alexa app's own skill settings. Revoking it immediately ends Alexa's ability to control your home; ALYT deletes the stored OAuth grant and any associated tokens.

11. Mobile App Permissions, in Detail

We think permission requests deserve more than a generic list, because a permission's stated purpose only means something if it is accurate. Here is exactly what the ALYT app requests, on each platform, and precisely why — verified against the app's actual configuration, not a guess at what a smart home app "probably" asks for.

11.1 iOS

11.2 Android

12. Access, Audit, and Security Logs

To keep your account and home secure, and to be able to answer "who changed this, and when" if something goes wrong, we keep audit logs of security-relevant actions: sign-ins, changes to account or property settings, devices added or removed, and household access grants and revocations, together with who performed the action and when. Audit logs are retained indefinitely and are not deletable by request, because their entire purpose is to remain a trustworthy record even after the events they describe (including, in the limiting case, an account's own deletion). Audit log entries do not, themselves, contain the content of what you said to the assistant, the content of your messages, or similarly sensitive material — they record actions, not content.

13. What We Deliberately Do Not Collect

It is easier to build trust by being explicit about absence, not just presence. As of this policy's effective date, ALYT does not collect:

• Demographic information — age, gender, race, ethnicity, religion, or political affiliation
• Payment or financial information (ALYT does not currently charge for the service; if and when billing is introduced, this policy will be updated before that change ships, and a separate, specific disclosure will describe what payment processor is used and what it collects)
• Biometric identifiers or templates — no fingerprint, face, or voiceprint templates are created or stored. Where a camera integration (like Ring) may show a face in a video frame, ALYT does not run facial recognition on that footage and does not create or store a biometric template of anyone's face or voice.
• Continuous or real-time location tracking of you or your phone
• Your contacts or address book
• Your calendar
• Photos or media from your phone's library (the camera permission described above is used live, for a one-time scan, not to browse or upload your existing photo library)
• Health or fitness data
• Advertising identifiers (Apple's IDFA or Android's advertising ID) for any purpose

14. Local vs. Cloud: The Complete Map

Bringing together everything above into one place, here is exactly what stays on your property, what always reaches Fizzify's servers, what reaches Fizzify's servers only if you opt in, and what reaches third parties.

14.1 Never leaves your property

• Wake-word detection (runs on the hub; nothing recorded before the wake word)
• Speech-to-text, language reasoning, and text-to-speech, when using local models (the default)
• Sonos, WiZ, Zigbee, HomeKit (ecobee), UniFi, and Home Assistant-bridged control
• Voice transcripts and replies, unless transcript storage is turned on

14.2 Always reaches Fizzify's servers

• Account and authentication data (email, hashed password, sign-in records)
• Home, room, and device configuration
• Voice turn metadata (never the content, unless transcript storage is on — see Section 6)
• Device state snapshots, telemetry, and command history
• Automations and their execution history
• Notifications and push token registrations
• Audit logs

14.3 Reaches Fizzify's servers only if you opt in

• Voice transcripts and replies (Settings → Voice → "Store voice history," off by default)
• Voice queries routed for cloud reasoning (Settings → Voice → "Use cloud reasoning," off by default)

14.4 Reaches a third party, depending on which integrations you connect

• Tuya (initial discovery only)
• SwitchBot, Ring, Cync, aromi.ai (ongoing, for as long as the integration is connected)
• Amazon (Alexa linking, if enabled)

15. Why We Process Your Data

We do not use your data for any of the following, and this is not a hedge — it is a direct statement of current practice:

• Training or fine-tuning AI models (see Section 26 for the full explanation)
• Selling to advertisers, data brokers, or any other third party
• Building behavioral advertising profiles
• Cross-app or cross-site tracking
• Automated decisions that produce a legal or similarly significant effect on you without human review

16. Who We Share Data With

16.1 Service providers (processors)

We use a small number of vendors to operate ALYT, each acting only on our instructions and only for the purpose described:

[LEGAL-VERIFY] A small number of additional infrastructure vendors — for automated backups, log aggregation, and service monitoring — are used operationally but had not, as of this policy's effective date, been finally confirmed for inclusion in our public subprocessor list. See the Subprocessors page, which we commit to keeping current as this is resolved.

16.2 Third-party integrations you choose to connect

Described fully in Section 10 above. We only share integration-relevant data with a third party if and when you connect that integration, and only the data necessary for it to function.

16.3 A successor in a business transfer

If Fizzify Inc. is acquired, merges, or sells substantially all of its assets, your data may be transferred to the successor entity as part of that transaction, subject to the successor's assumption of the commitments in this policy (or a materially equivalent one, with notice to you before any change takes effect).

17. Sharing Within Your Household

ALYT is built around the idea that a home has more than one person in it. When you invite others to your household, you choose their role:

You can revoke any member's access at any time; doing so signs them out immediately. It is your responsibility, as the account owner, to think through who should have access to what — ALYT gives you the controls, but the judgment about your own household's needs is necessarily yours.

18. Legal and Safety Disclosures

We may disclose information when we have a good-faith belief that doing so is necessary to:

• Comply with valid legal process — a court order, warrant, or subpoena we are legally obligated to honor
• Respond to an emergency involving danger of death or serious physical injury to a person
• Protect the rights, property, or safety of Fizzify Inc., our users, or the public
• Investigate or prevent fraud, security incidents, or violations of our terms

Where legally permitted, we will notify you before or promptly after any such disclosure. Some legal processes (e.g., a court-sealed order) may prohibit us from notifying you at all; in that narrow case, we comply with the law's restriction.

19. Data Retention

We aim to keep data only as long as it serves a purpose described in this policy. As of this policy's effective date, retention looks like this:

20. Cookies and Tracking Technologies

alyt.com and app.alyt.com use only strictly necessary cookies — to keep you signed in and to remember basic preferences like your chosen theme. We use no advertising cookies, no third-party analytics cookies, and no tracking pixels. Because we use only essential cookies, no cookie-consent banner is shown; if that ever changes, we will implement a proper consent mechanism before it does, rather than after. Full detail is in our dedicated Cookie Policy.

21. Security Practices

We protect your data with encryption in transit (TLS/HTTPS on every connection), Argon2id password hashing, hashed (not reversible) storage of refresh tokens and API keys, encryption at rest for sensitive secrets like MFA seeds and OAuth tokens, role-based access control, tenant isolation between households, rate limiting, and comprehensive audit logging. Full detail — including a candid account of a few known trade-offs, like why push tokens are the one thing we store unhashed — is in our Security & Responsible Disclosure page. No system is perfectly secure; if we ever discover a breach affecting your data, we will notify you without undue delay and within any legally required timeframe.

22. Your Privacy Rights

Wherever you live, you can exercise meaningful control over your ALYT data. The complete, step-by-step guide to every control described below — with exact menu paths — lives on our Your Privacy Choices page. Here is the summary:

• Access — see what we hold about you, or request a full export
• Correction — fix inaccurate account or home information yourself, in-app, at any time
• Deletion — delete specific data (a voice turn, an automation, an integration) or your entire account
• Portability — request your data in a machine-readable (JSON) format
• Opt-out — of cloud reasoning, transcript storage, and marketing email
• Objection and restriction (EU/UK/Swiss residents) — object to processing based on legitimate interest, or ask us to restrict processing
• Withdraw consent — for anything based on your consent (cloud features), at any time, without affecting past processing

To exercise any right not available directly in the app or console, email privacy@alyt.co with your request and enough information for us to verify your identity. We respond within 30 days generally, or within 45 days where California law applies (with the possibility of one 45-day extension, which we will notify you of if needed).

23. California Privacy Rights (CCPA/CPRA)

23.1 Categories collected in the past 12 months

• Identifiers — email address, name, device serial numbers
• Internet or network activity — IP address on requests, device telemetry, command history
• Geolocation data — a single, user-entered home address and its geocoded coordinates (not continuous tracking)
• Audio or electronic information — voice recordings while processing a command, and stored transcripts if you have opted in
• Professional or household information — your role within your household (owner, member, guest)
• Inferences — none drawn for profiling or advertising purposes; automation and dashboard behavior reflects settings you explicitly chose, not inferred characteristics about you

23.2 Sale and sharing

Fizzify Inc. does not sell or share (as those terms are specifically defined under the CCPA/CPRA, including for cross-context behavioral advertising) any personal information, and has not done so in the preceding 12 months. Because we do not sell or share, there is no "Do Not Sell or Share My Personal Information" mechanism to offer you — offering one anyway, with nothing behind it, would be exactly the kind of cosmetic gesture this policy tries to avoid. If our practices ever change, this section will be updated, and a genuine opt-out mechanism will be built before, not after, any such change takes effect. We honor Global Privacy Control (GPC) signals as described in Your Privacy Choices.

23.3 Your CCPA/CPRA rights

California residents have the right to know, delete, correct, and receive a portable copy of their personal information, and the right not to be discriminated against for exercising these rights. Submit requests to privacy@alyt.co; you may make up to two requests per 12-month period free of charge, and may designate an authorized agent with your signed permission.

24. EU, UK, and Swiss Residents

24.1 Lawful basis for processing

24.2 Your rights

In addition to access, correction, deletion, and portability described above, you have the right to restrict processing, to object to processing based on legitimate interest, and to withdraw consent at any time for anything processed on that basis. You have the right to lodge a complaint with your supervisory authority: your national data protection authority in the EU (listed by the European Data Protection Board), the UK Information Commissioner's Office, or Switzerland's Federal Data Protection and Information Commissioner.

25. International Data Transfers

ALYT is operated from the United States, and data described in this policy that reaches our servers is stored and processed there. If you are located in the European Economic Area, the United Kingdom, or Switzerland, this means your data is transferred outside those jurisdictions.

[LEGAL-VERIFY] We intend to rely on the European Commission's Standard Contractual Clauses (SCCs) as the legal transfer mechanism for such transfers. As of this policy's effective date, Fizzify Inc. has not completed formal execution of SCCs with every relevant infrastructure vendor, and is not currently certified under the EU-U.S. Data Privacy Framework. This is flagged internally as an item requiring completion with legal counsel before this policy can describe our transfer mechanism with full confidence rather than stated intent. We are not going to claim a certification we do not hold.

26. Children and Household Members Who Are Minors

You must be at least 18 (or the age of majority where you live) to create an ALYT account. We do not knowingly collect personal information directly from anyone under 13, and if we learn that we have, we will delete it promptly.

That said, ALYT is a household product, and households contain people of every age. If your home has a voice assistant, sensors, or (through an integration) cameras, those devices may naturally observe children in the home — a child's voice heard by the assistant, a child's presence detected by a motion sensor. This is not "collection from a child" in the sense the law is concerned with (a child creating their own tracked profile); it is your home's own devices operating in your own home, under your control as the account owner. It is your responsibility to:

• Decide whether and how voice, camera, or sensor features are used around children in your home
• Provide any notice or obtain any consent required by law in your jurisdiction for recording or monitoring minors, including your own children and any visiting children
• Use guest accounts and access controls thoughtfully if older children or teenagers use the app themselves

ALYT does not currently offer a distinct "child mode" or parental-control layer separate from ordinary household member/guest roles. If your household's needs require finer control than that, please tell us — this kind of feedback directly shapes what we build next.

27. AI and Automated Processing

27.1 Local models

Wake-word detection, and — when your household uses local processing (the default) — speech recognition, language understanding, and voice synthesis, run on pre-trained models deployed to your hub. These models are fixed at deployment; they do not learn from your household's voice or continue training on your data while running.

27.2 Cloud reasoning (opt-in)

If you enable cloud reasoning, voice queries that need it are sent to Fizzify's own inference infrastructure. Each request is handled independently — we do not retain a running conversational history across requests at the model layer beyond what is needed to answer an immediate, obvious follow-up in the same exchange (for example, correctly resolving "and Friday?" immediately after a question about Thursday).

27.3 No training on your data

We do not use your voice, transcripts, commands, device configuration, or any other personal data collected through ALYT to train, fine-tune, or otherwise improve any AI model — ours or a third party's. This is a direct statement of current practice; if this ever changes, this policy will be updated, prominently, before that change takes effect, and we would seek your explicit, opt-in consent before any such use, not treat it as covered by a prior "may improve our services" clause buried in a policy revision.

27.4 AI's limits

AI systems are probabilistic and imperfect. ALYT's voice assistant can misunderstand a command, mis-transcribe speech, or produce an answer that is confidently wrong. It is not designed, and should not be relied upon, for safety-critical decisions — unlocking a door during an emergency, for instance. See our dedicated AI & Automated Systems Notice for a fuller treatment of these limitations, including specifics on voice recognition and (where relevant) computer-vision limitations.

28. Changes to This Policy

We may update this policy as ALYT's features, our vendors, or applicable law change. For any material change, we will notify you by email and/or a prominent notice in the app or console at least 30 days before the change takes effect. Every version of this policy, with its effective date, remains available for reference — see the version history at the bottom of this page.

29. Contact Us

Fizzify Inc.
30 N Gould St STE N
Sheridan, WY 82801
United States

We aim to respond to all privacy inquiries within 30 days, or 45 days where California law applies.

Version history