Security and privacy

• Read-only, with one gated exception. Holler never moves money, and the only thing it ever writes to your field-service system is a job note a technician approved word for word. No approval, no write.
• Credentials are encrypted. API keys and tokens are AES-256-GCM encrypted at rest, validated once on connect, and never displayed again. Where a platform supports OAuth (Jobber), no long-lived key is ever pasted at all.
• Minimum customer data. Texts use a customer’s first name and street only.
• Phone numbers are for texting Holler texts. Tech numbers are used to deliver the product, never sold or shared.
• Full audit trail. Every inbound and outbound message is logged, and an idempotency ledger guarantees no duplicate sends.
• Site analytics. Holler records page views, clicks on its public pages, and signup steps with its own tracker, using an anonymous browser ID, device type, city-level location, and the ad or link that brought the visit. IP addresses are not stored.
• Consent is structural. Techs opt themselves in; STOP is honored instantly and permanently until a tech says otherwise.