UPDATED OCTOBER 30, 2026
Privacy notice
This notice describes information collected through FacilitySignal’s public product website, workspace sign-in and pilot request form.
Information you provide
The pilot form collects your name, work email, company, optional role, territory, product category, optional message and contact consent. Please use business information and avoid submitting sensitive personal information.
How we use it
We use submissions to evaluate pilot fit, respond to your request and arrange access if appropriate. Submission does not subscribe you to automated marketing emails or authorize prospect outreach. Requests are stored in a database and can be viewed by the site owner after sign-in.
Google workspace sign-in
Workspace sign-in uses Google to verify your identity. We receive your Google account identifier, email and display name, and use them to link an approved workspace account. We request basic identity information only, without access to Gmail, Drive or other Google content. Signing in does not automatically grant workspace access.
Workspace sessions use a secure, HttpOnly cookie and a hashed session record. Sessions expire after seven days or when you sign out. Short-lived sign-in challenges prevent replay, and salted IP-derived counters limit repeated attempts. Linked identity information is retained with the account until it is removed.
Marketing Cloud connections
Approved workspace users can optionally connect their own Salesforce Marketing Cloud Engagement account. We store the package client secret encrypted on the server, together with connection settings, field mappings and sync history. Tokens are used on the server to read destination metadata and write selected company and facility signals to a non-sendable Data Extension. Private notes, contact email addresses and outreach drafts are excluded from this connector.
Daily syncing starts only after you preview and enable the connection. You can pause it, replace the client secret or disconnect. Disconnecting deletes stored credentials and local sync checkpoints; existing records in your Marketing Cloud account remain there for you to manage. Sync logs are retained for troubleshooting. Your Marketing Cloud contact matching, audience permissions and campaign sends remain under your control.
Technical information
Hosting providers process technical request information needed to serve and secure the website. To limit form abuse, the form stores a salted, hourly hash derived from the requesting IP address and a submission counter. Expired counters are removed during later submissions. The application does not store the raw IP address in its pilot request records.
Providers and cookies
The website runs on OpenAI Sites infrastructure with Cloudflare-backed hosting and database storage. Google Fonts receives browser requests to serve typefaces. The owner-only pilot-request inbox uses the hosting platform’s authentication and associated cookies. The separate workspace uses Google sign-in as described above. We have not added advertising pixels or application analytics to this website.
Retention and your choices
Pilot requests are retained for review and follow-up until the owner removes them. You may ask to access, correct or delete a submission, or withdraw contact consent, by using the request form with “Privacy request” in the message. Include the work email associated with your original submission so the owner can verify the request. No fixed response time is promised during the pilot.
Public project examples
Product examples summarize public business announcements and link to their original sources. Private workspace notes and user feedback are not part of the public website.