Privacy Policy

1. Scope and company

This Privacy Policy describes how ReliaPulse LLC ("ReliaPulse," "we," "us," or "our") handles personal information through the ReliaPulse websites, application, Early Access program, plans and billing features, device services, integrations, weather features, notifications, customer-support communications, SMS support, bug-reporting features, campaign features, and related services (collectively, the "Service").

The current Service is offered to United States users.

This Policy does not govern third-party services you independently connect, visit, or purchase from. Their privacy policies apply to their processing.

2. Information we collect

Account and membership information

Name, email address, password hash, account role, plan, subscription status, login and account timestamps, location memberships, member roles, assignments, account preferences, and related account settings.

Locations, assets, tasks, and records

Location names and addresses, time zone, asset name and type, manufacturer, model, serial number, purchase and warranty dates, status, notes, chores, planned tasks, recurring schedules, priorities, completion or dismissal status, assignments, resolution notes, service provider, service date, cost, and service history.

Files you choose to provide

When supported, manuals, warranties, receipts, photos, screenshots, service records, filenames, file type and size, notes, and upload time.

Devices and telemetry

Device identifiers and pair status, firmware and board information, network address, online or offline status, timestamps, Wi-Fi signal strength, uptime, memory status, point and state values, event payloads, rule configuration, alarms, errors, update status, and other device health or diagnostic information.

Home Assistant integration

Server name and URL, encrypted access token, selected entity identifiers and friendly names, current state and attributes, device class, unit, rule settings, synchronization status, errors, and timestamps.

ReliaPulse may use Home Assistant history to evaluate rules but does not intentionally retain raw Home Assistant history unless a feature expressly requires and discloses it.

MQTT settings

Broker host and port, username, encrypted password, enabled status, connection state, errors, and timestamps.

Weather, address mapping, and location-derived information

When you use weather features, ReliaPulse may process:

• the saved street address for a location;
• latitude and longitude derived from that address;
• an address match returned by a geocoding service;
• weather forecast office and grid identifiers;
• official observation station identifiers;
• weather-alert and precipitation-source identifiers;
• weather forecasts, observations, alerts, radar- or gauge-derived precipitation estimates, timestamps, source health, and trigger-evaluation records; and
• task-audit information showing why a weather-based task was or was not generated.

ReliaPulse may use ReliaPulse-operated geocoding infrastructure and/or official United States government geocoding services. The current weather implementation may submit a saved address to the U.S. Census Geocoding Services to obtain coordinates.

After mapping, ReliaPulse may send coordinates or official source identifiers to National Weather Service or National Oceanic and Atmospheric Administration services to obtain weather information. These weather requests generally use mapped coordinates or source identifiers rather than your full saved street address.

ReliaPulse weather features do not require browser or device GPS access in the current implementation.

Notifications

Push endpoint and subscription keys, browser and platform details, user-agent information, notification preferences and quiet hours, notification title, body and link, delivery status, errors, and timestamps.

The current ReliaPulse SMS program is separate from automated application notifications and is limited to customer-support communications as described below.

Customer-support SMS and mobile information

If you contact ReliaPulse using SMS or otherwise provide a mobile telephone number for SMS customer support, we may process:

• your mobile telephone number;
• the content of messages sent between you and ReliaPulse;
• message timestamps;
• delivery, failure, and messaging-status information;
• support case or account information associated with the conversation when applicable;
• SMS opt-in, opt-out, HELP, and STOP request status;
• records showing when and how SMS consent was provided or withdrawn; and
• technical or carrier information reasonably necessary to provide, troubleshoot, secure, or document the messaging service.

The current ReliaPulse SMS program is intended for customer support and direct replies to customer-initiated communications. ReliaPulse does not currently use this program for advertising, marketing campaigns, promotional broadcasts, mass messaging, or automated application notifications.

When you initiate an SMS conversation with ReliaPulse, you consent to receiving SMS replies reasonably related to that support conversation.

Message frequency varies based on the support interaction. Message and data rates may apply.

You may withdraw consent to SMS communications at any time by replying STOP. You may reply HELP for assistance or contact ReliaPulse using the support methods published by the Service.

If ReliaPulse later introduces automated SMS notifications or another materially different SMS use case, we will update the applicable disclosures, consent process, Terms, and this Privacy Policy as appropriate before enabling that use case.

Billing and subscription information

If you select or manage a paid plan, ReliaPulse may receive and store billing-related information such as:

• Stripe, Link, or other billing-provider customer identifiers;
• subscription, checkout-session, invoice, payment, price, and product identifiers;
• current plan, billing interval, subscription status, renewal or cancellation status, and next billing date;
• transaction amount, currency, payment status, refund status, and related timestamps;
• payment-method type and non-sensitive display information such as card brand, last four digits, and expiration month and year, when provided by the billing provider; and
• billing events and webhook records needed to synchronize your ReliaPulse entitlements and maintain accounting or audit records.

Full card numbers, card security codes, and similar sensitive payment credentials are handled by the billing provider and are not intentionally stored by ReliaPulse.

Depending on the payment configuration, Stripe or Link may act as a payment processor or merchant of record. Their privacy notices and transaction terms apply to information they process for those functions.

Technical and security information

IP address, browser and device information, user-agent information, session cookie, request and error data, anti-abuse challenge information, login time, connection information, rate-limit information, security events, and administrative audit records.

Browser storage and application preferences

The progressive web app may use browser cache, service-worker storage, cookies, and limited local browser storage to provide application behavior and remember interface preferences.

For example, the current application uses `localStorage` to remember whether a user dismissed an optional progressive-web-app installation prompt.

Browser storage may also be used as a user-interface optimization for non-critical preferences or campaign display behavior. Server-side records remain authoritative for account, security, entitlement, and campaign-frequency decisions where applicable.

Product highlights, campaigns, and interaction data

ReliaPulse may display first-party product tips, feature announcements, setup recommendations, plan education, internal promotions, and, if enabled, sponsored content.

To control relevance and frequency and to measure whether content is useful, we may process:

• campaign or creative identifier;
• user and account identifier;
• current plan;
• placement;
• impression, click, dismissal, and completion timestamps;
• request or event identifier;
• prior campaign interaction state;
• account age;
• role, platform, feature state, usage-limit state, or similar in-product eligibility signals; and
• frequency, cooldown, or suppression state.

We do not intentionally use sensitive personal information to target campaigns.

Mobile telephone information, SMS opt-in information, and SMS consent are not used to target campaigns or sponsored content.

The current application does not rely on third-party behavioral analytics or external advertising pixels for this first-party campaign system. If ReliaPulse later enables an external advertising network or materially different tracking technology, we will update this Policy and any required consent practices before enabling it for affected users.

Bug reports, support, and feedback

When you submit a bug report, support request, survey, or other feedback, we may collect:

• the description, comments, troubleshooting details, screenshots, files, or other information you choose to provide;
• your optional contact information;
• when you are signed in, your ReliaPulse user ID, name, and account email address;
• the website or application from which the report was submitted;
• the current page URL, path, page title, and active application view;
• the date and time of submission and your reported time zone;
• your IP address and browser user-agent information;
• browser language and platform information;
• whether the browser reports a mobile device;
• browser viewport, screen dimensions, available screen area, color depth, and device pixel ratio;
• internet connectivity status, application display mode, referring page, and supported touch-point count; and
• administrative status, internal notes, resolution information, and the date and administrator associated with resolving or closing the report.

URLs may include information contained in query strings or page fragments.

The bug-report form is not intended for passwords, authentication tokens, full payment-card information, bank credentials, Social Security numbers, private encryption keys, medical information, or other sensitive information. Do not include this information in a report.

Legal acceptance and account-audit records

When you accept Terms, Privacy Policy versions, Early Access terms, or other required agreements, we may retain records such as:

• the document and version accepted;
• date and time of acceptance;
• account, name, and email snapshot;
• IP address;
• browser user-agent information;
• acceptance method; and
• the acceptance statement or other audit information needed to demonstrate agreement.

3. Sources of information

We collect information:

• directly from you when you register, configure the Service, enter records, upload files, choose a plan, submit a report, contact us, send us an SMS message, or provide feedback;
• from other authorized members or administrators of a shared location or organization;
• automatically from your browser, device, network, and use of the Service;
• from devices, MQTT brokers, Home Assistant, and other integrations you choose to connect and authorize;
• from official government geocoding and weather sources when weather features are enabled;
• from Stripe, Link, or other billing providers when you purchase or manage a paid plan;
• from telecommunications carriers, messaging providers, or support-service providers as necessary to send, receive, route, secure, or troubleshoot customer-support SMS; and
• from security, hosting, email, backup, and infrastructure providers used to operate and protect the Service.

4. How we use information

We use information to:

• provide accounts, shared locations, assets, tasks, records, files, notifications, device functions, integrations, weather features, and support;
• authenticate users, enforce roles and plan limits, maintain sessions, prevent abuse, secure systems, investigate incidents, and keep administrative audit records;
• map locations to weather coverage and obtain official weather information when you enable those features;
• generate schedules, tasks, alerts, state summaries, weather-triggered work, and other requested outputs;
• create, manage, renew, change, cancel, or synchronize subscription plans and account entitlements;
• reconcile billing events, refunds, payments, and accounting records;
• send or facilitate transaction, account, security, service, and subscription communications;
• respond to customer-initiated SMS support requests and provide follow-up reasonably related to those requests;
• route, deliver, troubleshoot, and secure customer-support SMS communications;
• maintain records of SMS consent, opt-out requests, HELP requests, and messaging preferences;
• comply with carrier, telecommunications, anti-abuse, and messaging-program requirements;
• select and frequency-limit product highlights or campaigns using in-product eligibility information;
• measure impressions, clicks, dismissals, and completion of product or sponsored campaigns;
• receive, review, reproduce, prioritize, investigate, track, and resolve reported bugs and technical issues;
• associate reports with the correct account, page, application view, browser, device environment, or Service component;
• contact you about a report when you provide contact information or submit the report through a signed-in account;
• identify duplicate, recurring, fraudulent, automated, or abusive submissions;
• verify fixes, monitor whether issues recur, and maintain an internal history of reported problems and resolutions;
• operate, troubleshoot, test, analyze, and improve Early Access and production features, including using feedback and aggregated or de-identified information where practical;
• communicate about the Service, requested support, security, legal notices, Early Access activities, billing, and material changes;
• document acceptance of legal agreements and plan terms;
• comply with law, respond to lawful process, enforce agreements, protect rights and safety, and complete business transactions.

ReliaPulse does not use SMS opt-in information or SMS consent for advertising, marketing targeting, sponsored-content targeting, or unrelated promotional purposes.

5. How we disclose information

We do not sell or rent personal information.

We do not use personal information for cross-context behavioral or targeted advertising.

SMS mobile information and consent

ReliaPulse does not sell, rent, or share mobile telephone information with third parties or affiliates for marketing or promotional purposes.

SMS opt-in information and consent are not shared with third parties or affiliates for their marketing or promotional purposes.

Text-message originator opt-in information and consent are used only for the applicable ReliaPulse messaging and customer-support purposes.

ReliaPulse may provide mobile information to telecommunications carriers, messaging providers, or subcontractors that perform services necessary to operate the SMS or customer-support service. Such providers may process the information only as reasonably necessary to provide services to ReliaPulse and are not authorized by ReliaPulse to use SMS opt-in information or consent for their own marketing or promotional purposes.

ReliaPulse does not transfer SMS consent to another business for that business to contact you.

Authorized ReliaPulse personnel

Account, billing, support, SMS, bug-report, diagnostic, campaign, security, and administrative records may be accessed by authorized personnel responsible for operating, securing, supporting, billing for, and improving the Service.

Shared locations and organizations

Authorized location owners, administrators, members, and viewers can access information according to their role.

An organization may control its workspace, members, and organization content.

Bug reports submitted directly to ReliaPulse are not ordinarily shared with other users unless necessary to address an issue affecting a shared location or organization.

Customer-support SMS conversations are not ordinarily shared with other users or organization members unless reasonably necessary to resolve the support request and consistent with the user's authorization or the organization's administration of its ReliaPulse account.

Payment and billing providers

We may disclose account, subscription, purchase, contact, transaction, and other information needed by Stripe, Link, or another billing provider to:

• create or manage a customer or subscription;
• process payments;
• prevent fraud;
• issue invoices or receipts;
• process refunds;
• handle disputes;
• provide billing support; or
• perform merchant-of-record functions where applicable.

Sensitive payment credentials are submitted directly to the billing provider rather than intentionally stored by ReliaPulse.

Official government geocoding and weather services

When you enable weather mapping or weather-triggered features, ReliaPulse may submit a saved address to official U.S. government geocoding services, such as U.S. Census Geocoding Services, and may submit mapped coordinates or source identifiers to National Weather Service or National Oceanic and Atmospheric Administration services.

Those government systems operate separately from ReliaPulse and may maintain their own request, security, or access logs.

Service and infrastructure providers

We may disclose or permit processing of information by hosting, database, security, email, telecommunications, messaging, customer-support, backup, storage, networking, and infrastructure providers that process information for us or help us operate the Service.

Such service providers receive information only as reasonably necessary for the services they perform for ReliaPulse and are not authorized by ReliaPulse to use SMS opt-in information or consent for marketing or promotional purposes.

Cloudflare

ReliaPulse uses Cloudflare services for functions that may include DNS, network security, web traffic handling, tunnels, access controls, caching, and Turnstile anti-abuse checks.

Cloudflare may process IP addresses, requests, challenge information, headers, technical information, and web traffic as necessary to provide those services.

User-directed integrations

When you connect Home Assistant, MQTT, browser push services, devices, or another integration, information is exchanged with those systems as needed to perform your instructions.

Browser, operating-system, and push-service providers may process push subscription and delivery data.

Campaign and sponsored-content destinations

First-party campaign selection and interaction tracking are handled by ReliaPulse.

ReliaPulse does not use or disclose mobile telephone information, SMS opt-in information, or SMS consent for campaign or sponsored-content targeting.

If you choose to follow a sponsored or external link, the destination may receive information normally transmitted by your browser, such as your IP address, browser information, and referring information, subject to browser and Service configuration.

If ReliaPulse later enables an external advertising provider that processes personal information or loads third-party scripts, we will update this Policy and implement applicable consent requirements before enabling that provider for affected users.

SMS opt-in information and consent will not be provided to such advertising providers.

Legal and safety

We may disclose information when reasonably necessary to comply with law or legal process, enforce agreements, investigate fraud or security issues, or protect rights, property, and safety.

Business transfers

Information may be transferred as part of a financing, merger, acquisition, reorganization, bankruptcy, or sale of all or part of the business, subject to applicable law.

SMS opt-in information and consent do not constitute authorization for an acquiring or successor business to use that information for marketing or promotional SMS. Any materially different messaging purpose must have an independently valid legal basis and, where required, new consent.

With consent

We may disclose information in other ways you expressly authorize.

General consent to use the Service does not constitute consent to disclose SMS opt-in information or SMS consent for third-party marketing or promotional purposes.

6. Cookies, browser storage, and similar technology

ReliaPulse uses a first-party RELIAPULSE_SESSION cookie to keep you signed in and secure account access. The current configuration allows a session lifetime of up to 60 days. The cookie is configured as HttpOnly, SameSite=Lax, and Secure when the request is detected as HTTPS.

The progressive web app uses a service worker and browser cache for the application shell, static resources, offline behavior, and push notifications. The service worker may exclude API responses from caching while caching eligible same-origin pages and resources.

ReliaPulse uses limited `localStorage` or similar browser storage for interface preferences, such as remembering dismissal of an optional PWA installation prompt, and may use browser storage for other non-critical interface optimizations.

Cloudflare Turnstile may use necessary browser storage or related technology to distinguish legitimate users from automated abuse.

The current Service does not use browser or device GPS/geolocation calls for weather mapping. Location coordinates used for weather are derived from saved addresses or other configured location data.

The current first-party campaign system does not require Google Analytics, third-party behavioral analytics, or external advertising pixels.

You can clear cookies, browser cache, and local site data through your browser settings, although doing so may sign you out, remove preferences, or affect installed PWA behavior.

7. Retention

We retain information for as long as reasonably necessary to provide, support, bill for, improve, and secure the Service; maintain legitimate business and accounting records; comply with law; resolve disputes; prevent abuse; and enforce agreements.

Retention varies by data type, plan, feature, configuration, and legitimate recordkeeping need.

Account and core application records

Core account, location, asset, task, service, membership, and configuration records may remain while the account or shared location is active and until deletion is requested or otherwise scheduled.

Some plans provide different history and retention periods. Downgrading or canceling a plan may cause shorter retention settings to apply after the applicable transition or grace period.

Operational history and logs

Device point history, activity logs, trigger logs, notification delivery logs, and similar operational history may be automatically removed according to the retention entitlements configured for the account's plan.

Current plan configurations generally provide shorter retention on Free accounts and progressively longer retention on higher paid plans.

Weather information

Current weather-system settings generally retain normalized weather facts for approximately 30 days and unreferenced collection-run information for approximately 90 days.

Longer-lived event fingerprints, task evidence, or audit records may remain when needed to explain a generated task, prevent duplicates, or preserve service history.

Administrative and security records

Meaningful administrative action-audit records are generally scheduled for deletion after approximately 365 days unless a longer period is reasonably needed for security, investigation, legal, or business purposes.

Routine records may be removed sooner.

Campaign interaction data

Campaign impressions, clicks, dismissals, suppression state, and related reporting information may be retained for as long as reasonably needed for frequency control, reporting, abuse prevention, sponsor reconciliation, or product analysis, then deleted or de-identified when practical.

Bug reports and support

Bug reports and associated diagnostic details may be retained while an issue is open and for a reasonable period afterward to document resolution, verify fixes, identify recurring issues, prevent abuse, and improve the Service.

Resolved or closed reports may remain in an internal issue history.

SMS support records

Customer-support SMS messages, associated support records, delivery information, and related technical records may be retained while a support matter is active and for a reasonable period afterward to:

• maintain support history;
• resolve disputes;
• investigate abuse or delivery problems;
• demonstrate compliance with messaging requirements;
• document consent and opt-out requests; and
• protect ReliaPulse and its users.

Records of SMS opt-out requests may be retained as necessary to ensure that the opt-out remains honored.

Billing, accounting, and legal records

Subscription, invoice, transaction, refund, accounting, tax, legal-acceptance, and related audit records may be retained for longer periods when reasonably necessary to satisfy legal, tax, accounting, fraud-prevention, contractual, or dispute-resolution obligations.

Payment providers may retain billing information independently under their own legal obligations and privacy practices.

Deleted or disabled information

Disabled push subscriptions, SMS suppression or opt-out records, security records, legal records, and backup copies may remain for a limited period until routine deletion, backup rotation, or a legitimate retention need ends.

Because self-service account deletion may not be available for every account or data type, deletion requests may be handled manually.

We may retain limited records when required or permitted by law and will explain material exceptions when reasonably possible.

8. Security

We use administrative, technical, and organizational safeguards designed to protect information.

Current protections may include:

• password hashing;
• role-based access checks;
• secure-session settings;
• restricted administration;
• encryption for supported integration credentials and secrets;
• encrypted web-push delivery;
• TLS/HTTPS;
• Cloudflare security and tunnel services;
• origin restrictions;
• anti-spam controls;
• rate limits;
• administrative audit records; and
• separation of sensitive payment credentials from ReliaPulse systems through payment-provider integrations.

No system is completely secure, and we cannot guarantee that unauthorized access, loss, misuse, outage, or compromise will never occur.

Protect your email and ReliaPulse password, device and integration tokens, MQTT credentials, and network access.

Do not place passwords, access tokens, full payment information, or other secrets in bug reports, support messages, SMS messages, task notes, documents, or other fields not designed for them.

Promptly disconnect integrations and contact us if you suspect compromise.

9. Your choices and requests

• Account and content: Update information through available app features or contact us to request access, correction, export where reasonably available, closure, or deletion.
• Billing: Manage available subscription and billing controls through ReliaPulse or the applicable payment provider. Payment-provider privacy or deletion requests may need to be submitted directly to that provider.
• Bug reports: Providing a contact email on a public bug-report form may be optional. Signed-in reports are associated with the submitting account. You may contact us to request access to, correction of, or deletion of a report, subject to identity verification and legitimate retention needs.
• Shared locations: Location owners and administrators control membership and roles. Contact the relevant owner or administrator if organization-managed information is inaccurate or access should be removed.
• Push notifications: Change preferences in ReliaPulse and in your browser or device. Disabling push may not immediately delete prior delivery logs.
• SMS support: You may stop customer-support SMS communications at any time by replying STOP. You may reply HELP for assistance. Opting out of SMS does not prevent you from contacting ReliaPulse through other available support channels and does not automatically opt you out of unrelated communications that you have separately authorized.
• Integrations and devices: Disconnect Home Assistant, MQTT, push subscriptions, or devices through available controls, then rotate third-party credentials when appropriate.
• Weather: Disable or delete weather triggers through available controls when you no longer want those features to operate. Deleting a location or related weather configuration may not immediately remove all historical audit information.
• Campaigns: Available dismissal or preference controls may allow you to suppress optional campaigns. Required legal, security, account, billing, or service notices are not treated as optional marketing.
• Communications: You may opt out of non-essential promotional messages if offered. We may still send service, transaction, security, account, support, and legal notices through channels for which we have an appropriate basis to communicate.

We may verify identity and authority before acting, including authority to act for another person or organization.

Privacy rights vary by jurisdiction, and we will respond as required by applicable law.

10. Children

The Service is not directed to children and currently requires users to be at least 18 years old.

Do not create an account for a child or submit a child's personal information.

If you believe a child's information was provided, contact us so we can review and delete it as appropriate.

11. United States scope and international infrastructure processing

The current Service is offered to United States users and ReliaPulse's primary application and database infrastructure may be operated in the United States.

However, internet traffic and technical information may be processed through global networks and infrastructure providers.

For example, Cloudflare operates a global network and may terminate, inspect, route, cache, or otherwise process HTTPS traffic and related metadata at network locations outside the United States depending on configuration and where a user connects.

Other providers, including payment, email, telecommunications, messaging, push-notification, security, or integration providers, may also process information in locations where they operate.

Do not invite or enroll users outside the United States until ReliaPulse has reviewed applicable international privacy, consumer, tax, and data-transfer requirements and updated the Service and this Policy as appropriate.

12. Changes to this Policy

We may update this Policy as the Service, billing model, infrastructure, providers, features, messaging programs, and legal requirements change.

We will post the updated version and effective date and provide additional notice for material changes when appropriate.

If a change requires consent, our legal-acceptance system or another appropriate process may require you to accept the updated Policy before continued use.

If ReliaPulse materially expands its SMS program, including by introducing automated application notifications, recurring SMS alerts, promotional SMS, or other messaging not covered by the current customer-support program, we will update applicable disclosures and consent practices before enabling that use case.

13. Contact

Privacy questions and requests: [email protected].