Terms and privacy

1. The service

Relay — a simple dashboard shows the Home Assistant controls and readings you select on a separate dashboard here. Full Proxy opens the existing Home Assistant interface through your own HTTPS web address. Home Assistant must already run at your home. The products are separate; a paid plan for one does not include the other.

You must own the installation or have permission to administer it, and have legal capacity to enter this agreement. You remain responsible for your equipment, internet connection, local configuration and account security.

Relay needs outbound internet access. It does not reproduce the full Home Assistant interface, stream cameras, copy Home Assistant’s full history or supply a Companion app server address. Initial manual setup includes adding configuration, loading the REST commands and saving an automation.

Proxy requires a reachable public IPv4 and router forwarding restricted to the server shown in your private setup. Your public address uses HTTPS. By default, the separate connection from our server to your home uses unencrypted HTTP, including sign-in data. Existing trusted home HTTPS can encrypt that connection. A home certificate is not required for the standard setup.

myhomeassistant.top is independent of Home Assistant and Nabu Casa. It is not the official Home Assistant Cloud subscription.

2. Plans and annual billing

• Free Relay: one free allowance per account, five selected entities and scheduled 60-second updates. No personal subdomain.
• Relay Standard: $60 USD a year ($5 a month equivalent), 100 selected entities and scheduled 15-second updates.
• Relay Large: $108 USD a year ($9 a month equivalent), 200 selected entities and scheduled 10-second updates.
• Full Proxy: $72 USD a year ($6 a month equivalent), access to your existing Home Assistant interface when its connection requirements are met.

Each paid plan includes one personal HTTPS subdomain. A Relay address opens its Relay dashboard; a Proxy address opens your full Home Assistant. You may see a plan called a “license” in technical details. Your account can have multiple paid plans.

PayPal charges the full annual amount upfront and renews annually until cancelled. You review the price and billing agreement in PayPal before approving. Approval alone, a pending payment or a failed payment does not activate access. Current checkout availability appears on Plans.

Web addresses depend on availability and reserved-name restrictions. A name check does not reserve a name. Assignment requires a valid paid plan for the product; Proxy also requires a successful home connection check. You can use an assigned subdomain while its plan is valid, but do not own it as a separate domain.

3. Your responsibilities

Keep your site password, connection tokens and generated automations private. Review selected entities and scripts before enabling remote controls. Lock and cover controls require explicit permission per entity. Your site account protects Relay; your Home Assistant account protects its own interface.

Use unique passwords, enable Home Assistant multi-factor authentication, install updates and maintain backups. For Proxy, restrict forwarding to the server address in your private setup. Keep a local way to administer your home. If a credential is exposed, replace or revoke it and review access. Neither product should be your only way to control safety-critical equipment.

4. Usage limits

The service is for ordinary household dashboard access and automation control. Proxy permits intermittent camera viewing. Continuous CCTV relaying, commercial video distribution, general file hosting, backup transfers, network scanning, spam and denial-of-service activity are prohibited.

Each Full Proxy address has these limits:

• Up to 10 connections at once, including WebSockets.
• A sustained rate of 10 requests per second, with a burst allowance of 30 requests.
• Up to 10 MiB in each request body.

Excess requests may fail temporarily. Traffic that materially harms other subscribers may be throttled or suspended; urgent security or availability threats may be blocked immediately.

A Relay snapshot is limited to 64 KiB and must contain unique selected entity IDs within the plan allowance. State, room and unit values are limited to 128 characters. Oversized or invalid updates are rejected. Paid tokens permit at most 30 state updates and eight command checks per minute. These are maximum rates, not the normal update schedule for your plan. Free clients use the 60-second schedule. Entity-configuration requests permit six per minute and account command queues 30 actions per minute.

No traffic overage charge is created by these terms. A new paid allowance or material fair-use change must be disclosed before it applies.

5. Updates, commands and availability

Access depends on home power and internet, your ISP, DNS and our hosting. Maintenance, outages and security incidents can interrupt it. We do not guarantee an uptime percentage or provide an emergency-response service.

Relay intervals are schedules, not guaranteed response times. Missing updates do not prove that the home is offline. A command waits up to five minutes for Home Assistant to collect it. After collection, you cannot cancel it. If the response is lost or Home Assistant fails while handling it, the command may not run. An unconfirmed command is removed five minutes after it was sent. A matching reported state confirms the requested state, not a physical change. A script acknowledgement does not prove successful completion.

Paid outage email availability is shown on Plans and in each connection’s settings; Relay Free does not include it. When available and enabled in your connection settings, monitoring checks for at least ten minutes without accepted Relay updates or continuous failed Proxy public-route checks. Recovery needs stable successful observations. It does not test every device or feature, identify the cause of a home outage or provide emergency notification. Checks and email delivery add time, and mail-server acceptance does not prove an email reached an inbox. Turning alert email off leaves your connection and necessary account or payment emails unchanged.

6. Renewal, expiration and refunds

Cancel future annual renewal from your account or PayPal's automatic-payment controls. Cancellation stops future billing and does not automatically refund an existing payment. Paid access continues until its recorded end date unless the payment is fully refunded or reversed, or access is suspended for a breach.

Partial refunds do not remove access unless they total a full refund for that payment. Refunding an earlier period does not remove a later separately paid renewal. Other subscriptions are unchanged. Refund rights required by applicable law remain available; any additional commitment must be disclosed at checkout.

An expired or revoked plan cannot create a new address. New Proxy requests are denied, and scheduled cleanup removes expired routes. Existing proxy connections may continue until closed under the host's graceful shutdown policy.

Expired, revoked or disabled Relay access rejects new updates, command checks and controls. Its usable token, latest snapshot, sensor history and commands are invalidated or removed as requests are handled and during scheduled cleanup. Commands already collected by Home Assistant may still run; revocation cannot undo a physical action.

7. Data and privacy

We store account details, password hashes, plan records, assigned addresses, home connection settings and operational timestamps. Technical logs may include IP addresses and request information. PayPal handles payment credentials. We retain account-linked payment identifiers, status, paid periods and verification records, but do not store card details or PayPal passwords.

For Proxy, browser HTTPS ends at our server. The default home connection is unencrypted HTTP, including authentication and dashboard traffic; optional home HTTPS encrypts that separate connection. Our proxy can process the traffic in either case. The service is not end-to-end or zero-knowledge encryption. A source restriction does not encrypt HTTP.

Proxy uses the checked public IPv4 or the address resolved from your saved DNS/DDNS name. We look up saved home hostnames through Cloudflare’s HTTPS DNS service. For outage monitoring, we also use Google DNS. Each provider receives the hostnames queried through its service. Changed addresses must pass a connection check before replacing the saved IP; failed checks leave the last checked IP in place. DDNS is authoritative when configured. A changing IP without DDNS needs the automatic-update automation; a fixed IP needs no updater. Contact timestamps record reports, not continuous availability.

Relay stores the selected entity IDs, control permissions, latest states, rooms, units, change times, source IP and update time, short-lived commands and usage/rejection totals. These can reveal household routines. Relay saves one reading per selected sensor every five minutes, including a missing-reading marker when its value is not numeric. Free Relay keeps 24 hours; paid Relay keeps 7 days. History begins with new updates and does not import older Home Assistant data. Older samples are removed by scheduled cleanup; downgrading to Free reduces the available history to 24 hours. Removing a sensor, disabling its token or deleting Relay removes its stored history. Shared dashboard users can view this history too. The owner can view and control Relay. Paid Relay also allows additional dashboard logins: 1 on Standard and 4 on Large. These logins can view all selected entities and use their enabled controls, but cannot manage setup, people or billing. We store each shared login’s name, email and password hash. The owner can remove access or reset its password in Relay settings.

Relay and Proxy automations use separate connection tokens, not a Home Assistant login token. We store authentication hashes and encrypted copies so the owning account can copy setup again. Tokens can be refreshed or invalidated in the account. Automations, connector settings and backups also contain credentials and should remain private.

Password recovery uses single-use links that expire after 30 minutes. Reset tokens are stored as hashes; temporary email-delivery data is encrypted and removed after sending, use or expiration during scheduled cleanup. Resetting your password invalidates existing signed-in sessions. A separate, secure cookie can keep your Relay dashboard signed in on the same device for up to 30 days, including after you close the browser. Its random credential is stored as a hash on our server and grants dashboard access only. Logging out removes it from that site address; account password changes and revoked shared access invalidate the corresponding dashboard credentials. Expired credentials are deleted during scheduled cleanup.

Outage monitoring stores per-installation observation times, result categories, incidents and notification preferences separately from connection readiness. Proxy checks use public connection responses and the DNS services described above. They do not use your Home Assistant login credentials or send device commands. Alert preferences are saved on the website for each installation. Emails are sent to the address saved in your account; no separate email confirmation is required.

Our transactional email provider, Postmark, receives the recipient address and message content for account, security, payment and connection emails. Open and link tracking are disabled. Temporary message payloads are encrypted and removed after acceptance or expiration; password-reset content keeps its 30-minute limit, and other queued content lasts at most 24 hours. Delivery and closed-incident audit records are removed after 90 days by scheduled cleanup. Delivery failures and suppression hashes are kept to prevent repeated sends to bounced addresses. These emails do not contain your Relay readings or connection tokens.

For questions about your account or its data, open a support ticket.

8. Acceptable use and changes

Do not publish unlawful material, infringe others' rights, attempt unauthorized access, bypass security or capacity controls, resell access without agreement or submit false payment events. Access may be suspended to prevent harm, comply with legal obligations or address a material breach.

Material pricing or agreement changes must be communicated before renewal. Mandatory consumer rights are not excluded.

9. Contact

Open a support ticket about setup, billing or your account. Sign in to your registered account to create or follow a ticket. If you cannot sign in, use password recovery first.