Legal
Privacy policy
SignalDesk Blog collects only what we need to run a public GEO newsroom and publisher studio. This policy explains what we collect, how cookies work, and how to contact us.
What we collect
- Account data — name/brand, username, hashed password, optional website and profile fields
- Content — posts, media URLs, metadata, and topic associations you submit
- Acceptance records — Terms version and timestamp when you accept at signup
- Technical logs — standard server logs (IP, user agent, request path) for security and reliability
- Analytics (optional) — if you accept analytics cookies and PostHog is configured: pages viewed and publisher context
- Newsletter (optional) — if Beehiiv is embedded, signups are processed by Beehiiv under their privacy policy
How we use data
We use this information to:
- Operate the studio, public site, feeds, and publish API
- Authenticate publishers and protect accounts
- Attribute posts to the correct publisher archive
- Enforce our Terms and respond to legal requests
- Improve the product when analytics consent is given
We do not sell personal information.
Retention
Account and content data are kept while your account is active and as needed to operate the service. Unpublished or deleted posts stop being served from SignalDesk Blog; residual copies may remain in backups for a limited period. Server logs are retained for a short operational window.
Your choices
- Update profile fields in Settings
- Rotate passwords and API keys
- Unpublish or delete posts you control
- Accept or reject analytics cookies
- Contact us to request account-related privacy help at the address below
Security & children
We use industry-standard practices such as hashed passwords and httpOnly session cookies. No method of transmission is 100% secure. SignalDesk Blog is not directed to children under 13, and we do not knowingly collect data from them.
Contact
Privacy questions: privacy@signaldesk.example
Copyright notices: see our DMCA policy.