Privacy policy

How Palm Technologies LLC and participating facilities handle information in FaciliPulse.

Last updated: September 17, 2026

This Privacy Policy explains how Palm Technologies LLC ("Palm Technologies," "FaciliPulse," "we," "us," or "our") handles personal information when people visit facilipulse.com, contact us, use FaciliPulse, receive a facility update, or interact with a related integration (collectively, the "Services"). It should be read with the FaciliPulse Terms of Service and, where applicable, a facility's own privacy notice.

1. Who controls the information

FaciliPulse is a business-to-business platform used by facilities to publish operating information, estimate occupancy, manage member updates, and connect operational tools. The facility that chooses the purposes and settings for its organization data—such as its members, notifications, camera configuration, and public notices—generally controls that information. Palm Technologies generally processes that information to provide the Services and under the facility's instructions.

Palm Technologies controls information it collects for its own business purposes, including marketing-site inquiries, prospective-customer communications, billing and account-administration records, service security, and legal compliance. If you are a member or visitor of a participating facility, contact that facility first for requests about information it controls. We will assist the facility as appropriate and as required by applicable law.

2. Information we collect or process

Website, contact, and sales information

When you use the contact form or communicate with us, we process your name, work email, organization, request topic, message, and the time of the request. To protect the form and prevent abuse, we also process a hashed network identifier for rate limiting and use Cloudflare Turnstile to assess whether a submission appears automated. Please do not send passwords, payment-card details, camera credentials, or other sensitive information through the contact form.

Account, identity, and administrator information

Depending on the sign-in method and organization configuration, this can include name, email address, phone number, organization role, authentication-provider identifier, user ID, verification state, login and security events, and multi-factor or recent-authentication status. FaciliPulse supports email/password and may support phone, Google, Microsoft, Apple, or organization-approved identity-provider sign-in methods.

Facility, member, and notification information

Participating facilities may enter organization and area names, hours, public notices, administrator and member records, external membership identifiers, email addresses, phone numbers, selected topics and channels, consent or verification records where collected, opt-out state, message content, and delivery outcomes. A phone number or roster entry alone is not permission to send an SMS or voice message; the facility is responsible for its enrollment and consent process.

Occupancy, camera, and device information

FaciliPulse connects to configured local cameras via an on-premise application or edge client. To estimate the number of people in an area, the client captures short video segments (typically up to 3 seconds) and securely transmits them to our cloud infrastructure for real-time model inference. Routine inference clips are processed in volatile memory or temporary cloud storage and are deleted immediately upon generating the numerical occupancy count. The platform records resulting numerical observations, area configurations, timestamps, device health, relay status, network diagnostics, and count-quality data. The product is engineered strictly for people counting and does not use facial recognition to identify visitors.

Camera images may be handled when a facility uses calibration, snapshot, troubleshooting, or diagnostic features. Diagnostic capture is off by default and time-limited. Exclusion zones control what is used for counting; they are not a representation that every image is redacted or that no image can ever be stored. Facilities are responsible for lawful camera placement, notice, and authorization.

Operational analytics, location, and weather information

We process occupancy observations, aggregated attendance history, status events, facility timezone, and—if a facility enables weather—its city, ZIP code, or coordinates and the resulting weather observations. We use this information to show current conditions, historical trends, and configured weather context; not to infer a visitor's precise location.

Integration, support, and billing information

When an organization connects an integration, we process the connection metadata and credentials needed to operate it, such as selected Slack or Teams workspace and channel, OAuth tokens, webhook URL, API-key status, event subscriptions, and delivery records. We also process support communications and associated troubleshooting information. Stripe handles payment credentials for paid subscriptions; FaciliPulse receives account, subscription, invoice, payment-status, and transaction-reference information, but does not store full payment-card numbers.

Optional AI-assisted review

If an authorized administrator invokes an AI review feature, the submitted announcement text and limited request context are sent to the configured AI provider to classify or rewrite the text. Do not submit sensitive personal information, health information, payment information, or camera credentials to an AI review field.

3. How we use information

We use information to:

• provide, configure, secure, and support the Services;
• authenticate users, enforce roles, and protect accounts, devices, APIs, and integrations;
• publish facility status, calculate occupancy estimates, and provide configured reports and displays;
• send, suppress, route, measure, and troubleshoot authorized SMS, email, voice, and other notifications;
• operate customer-selected integrations and process their delivery results;
• create and manage subscriptions, invoices, and customer-support records;
• prevent spam, fraud, security incidents, and misuse;
• comply with law, enforce agreements, and establish or defend legal claims; and
• improve reliability and functionality using de-identified or aggregated information where reasonably practical.

Where a privacy law requires a legal basis, we process information to perform our contract, comply with legal obligations, pursue legitimate interests such as security and service improvement, or with consent where required. The facility is responsible for identifying the appropriate legal basis for information it provides to FaciliPulse and for communications it instructs us to send.

4. When we disclose information

We disclose information only as needed to provide the Services, at an organization's direction, with your permission, or as required or permitted by law. This may include:

• The participating facility and its authorized users. Administrators and staff may access information for their organization according to their assigned role. Public status viewers may display the facility name, operating hours, notices, area status, and occupancy estimates selected by the facility.
• Cloud infrastructure and application providers. We use Google/Firebase services, including authentication, Cloud Functions, Firestore, Realtime Database, Cloud Storage, and Hosting, to operate the Services.
• Security and anti-abuse providers. Cloudflare Turnstile processes information needed to help distinguish human form submissions from automated traffic. It does not receive the contents of the contact-form fields through the Turnstile widget itself.
• Communications and voice providers. Depending on the organization and configured delivery path, message information may be processed by Telnyx, Twilio, AhaSend, Amazon Web Services Simple Email Service, Google Cloud Text-to-Speech, Amazon Polly, or another approved provider. These providers may process recipient address or phone number, content, delivery metadata, and provider response data needed to send or report on a message.
• Payments. Stripe processes payment information, subscription checkout, customer-portal actions, and fraud-prevention information for paid plans.
• AI and weather providers. When enabled, OpenAI or a configured Cloudflare AI Gateway may process submitted review text; OpenWeather may process facility weather-location data to return weather information.
• Customer-directed integrations. Slack, Microsoft Teams, Zapier, and a customer's own webhook endpoint receive the data selected by the organization for that integration. Their use of data is governed by their own terms and privacy practices and the customer's configuration.
• Professional advisers, corporate transactions, and legal requirements. We may disclose information to advisers, insurers, auditors, a successor in a merger or similar transaction, or government and law-enforcement authorities when legally required or reasonably necessary to protect rights, safety, property, or the Services.

We do not sell personal information. We do not share mobile-phone information with third parties for their own promotional or marketing purposes. We do not use FaciliPulse data for cross-context behavioral advertising.

5. Retention

Retention depends on the record type, organization settings, service configuration, legal obligations, and whether a scheduled cleanup process has run successfully. Current default operational settings are summarized below; a facility may configure longer periods within product limits. These periods do not override a legal hold, security investigation, provider record, backup, or a different contracted retention requirement.

An expiring link or a request to remove a record does not automatically erase independently retained copies from logs, backups, or third-party providers. Provider-hosted records, including payment and communications records, remain subject to the provider's retention and deletion controls.

6. Your choices and privacy requests

You may manage available notification topics and channels through your facility's preferences experience. SMS recipients can reply STOP to a supported sending number to opt out of future texts from that number; reply HELP or contact the facility for help. Opting out of a message channel does not automatically delete account, consent, or delivery records.

Authorized organization super administrators can use the privacy area to review retention settings and request an export of operational organization data. Organization deletion is restricted and requires additional confirmation. To request access, correction, export, or deletion, email support@facilipulse.com with the subject line “Privacy request.” We may verify identity and authority, and will direct a member or visitor request to the facility that controls the relevant data when appropriate.

7. International processing

FaciliPulse and its providers may process information in the United States and other countries where they or their service providers operate. Those locations may have data-protection laws that differ from the laws where you live. Where required, we use appropriate safeguards for transfers and work with our providers under their applicable data-protection terms.

8. Security

We use technical and organizational measures designed to protect information, including authentication, role-based access controls, encryption in transit, access logging, credential separation for supported integrations, and retention controls. No system, transmission, or storage method is completely secure. Facilities and users must protect their devices, passwords, API keys, webhook secrets, integration tokens, and camera credentials and promptly report suspected unauthorized access.

9. Children and sensitive settings

FaciliPulse is designed for facilities and their authorized users; it is not directed to children. A facility that serves minors is responsible for determining whether and how it may use the Services, providing required notices, obtaining required permissions, and configuring camera and notification features appropriately. Do not use FaciliPulse to collect or send sensitive personal information unless the facility has confirmed it may lawfully do so and has an appropriate agreement with Palm Technologies.

10. Changes and contact

We may update this Privacy Policy as the Services, providers, or legal requirements change. We will post the revised version here and change the “Last updated” date. For questions about this policy or our privacy practices, contact support@facilipulse.com.