Checkin Signals, a product of Digital Dynamics. Last updated September 2, 2026.
Account data: your name, email address, and business details (name, address, phone) you provide when you sign up or configure your business profile.
Job-site data: when a field tech submits a check-in, we collect the photos, notes, service type, and GPS location they capture. Published pages show only an approximate, deliberately offset location — never the exact address or coordinates.
Usage data: we run first-party analytics on our own site (page views, feature usage) and Google Analytics. We honor Do Not Track for our first-party analytics, and we do not load analytics inside the embeddable map widget shown on customer websites.
To run the service: turning check-ins into pages on your website, generating content with AI, posting to your Google Business Profile when you connect and enable it, sending operational emails, and billing through Stripe. We do not sell personal information.
We rely on these processors to operate: Clerk (sign-in), Stripe (payments — we never see or store card numbers), Google (Business Profile posting you explicitly connect, analytics), Anthropic (AI content generation), Neon (database), Fly.io and Vercel (hosting), and Cloudflare (photo storage). Credentials you connect — such as WordPress application passwords and Google refresh tokens — are stored encrypted and are never shown to anyone.
You can disconnect WordPress or Google at any time from your dashboard, pull down any published page, and cancel your subscription self-serve. To access, correct, or delete your data, email carlos@trydigitaldynamics.com and we'll respond within 30 days.
If you connect your Google Business Profile, we request the business.manage permission solely to publish posts and photos about your completed jobs to the profile you choose, when you have auto-posting enabled. We store only an encrypted refresh token, we never post without your setting enabled, and disconnecting deletes the token. Checkin Signals' use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.