Operator: FormularySignal. Contact: support@formularysignal.com. This notice describes the current low-data design rather than promising a regulated healthcare or compliance service.
Data Collected
The service may collect work email, organization name, selected plan, billing identifiers from Stripe, watchlist terms, webhook URLs, additional report recipients, one-time billing-token metadata, and delivery preferences.
Data Use
Collected data is used to create checkout sessions, maintain subscriptions, generate customer-specific shortage watchlist reports, send HTML and plain-text service emails, provide support, maintain marketing/digest suppression records, and keep delivery and debugging records.
Processors
Stripe processes payments and billing metadata. Zoho Mail, Resend, or another transactional email provider may process report-delivery emails. Hosting and database providers may process service logs and stored watchlist configuration.
Payments
Payments are processed by Stripe. FormularySignal does not store card numbers.
Health Data
The service is not intended to receive PHI. Do not submit protected health information, patient identifiers, prescriptions, medical records, addresses, dates of birth, or individual treatment details. If PHI is submitted accidentally, contact support promptly.
HIPAA and BAA Posture
FormularySignal is designed for a non-PHI workflow: public shortage records, organization-level watch terms, work emails, and routing details. The current self-serve service is intended to avoid PHI rather than process it. If your organization requires a Business Associate Agreement before using any vendor, contact support before submitting watch terms or starting procurement.
Retention and Deletion
Customer account and watchlist data is retained while a subscription or active account relationship is in place. Delivery logs and public-data snapshots may be retained for debugging and source-history review. Suppression-list entries may be retained so opt-outs remain honored. Customers may request deletion of account-specific data by contacting support, subject to billing, security, abuse-prevention, opt-out, and backup-retention needs.
Security
FormularySignal minimizes sensitive data collection. Production uses HTTPS, managed secrets, verified payment webhooks, and transactional email providers. No system can guarantee absolute security.
Cookies and Analytics
The current service does not include advertising cookies or third-party analytics scripts. FormularySignal may record first-party, privacy-conscious event logs for operational pages such as digest signup, sample Signal Card clicks, pricing clicks, checkout starts, checkout completion, contact form submission, source page visits, weekly digest visits, and signal archive visits. These events are used to understand acquisition and product health without collecting PHI.