Data Collection Practices
Effective date: August 9, 2026 · Companion to the Privacy Policy
This page explains what data the Social Media Liaison Service collects or processes, where it typically lives, and why. It is written for transparency (including app store / platform review contexts).
1. Data categories
| Category | Examples | Purpose |
|---|---|---|
| Identity / social handles | @handles, display names, platform user IDs | Connect and label accounts in the dashboard |
| Authentication secrets | API keys, OAuth tokens, page tokens | Call platform APIs on your behalf |
| Media & writing | Videos, images, Markdown/text insights, captions | Generate posts and publish content you approve |
| AI prompts & outputs | Title/description/hashtag drafts, comment replies | Assist content creation and engagement |
| Engagement metrics | Views, likes, comments, shares (when APIs allow) | Analytics charts and performance reports |
| Comments & replies | Comment text, author ids, reply text | Moderation signals and optional auto-replies |
| Operational logs | Job status, errors, event JSONL, alerts | Reliability, debugging, away-mode alerts |
| Device / host metadata | Request IPs, user agent (via host); local paths on Mac | Serve dashboard; watch local content library |
2. What we do not intentionally collect
- Payment card numbers (not processed by this app).
- Precise GPS tracking of end users browsing public posts.
- Contacts lists, SMS, or microphone audio beyond media files you explicitly provide.
- Sale of personal data to data brokers.
3. Where data may be stored
- Your Mac: content library folders, local SQLite DB, logs, optional app settings.
- Railway (or other host): dashboard app, environment variables/secrets, ephemeral runtime logs.
- Social platforms: published posts, comments, and metrics under your accounts.
- AI provider: prompt/response content when generation features are enabled.
4. Legal bases / purposes (practical)
- Provide the Service you request (posting, analytics, engagement).
- Secure and maintain the Service (logs, error handling).
- Comply with law and platform requirements.
5. Your controls
- Toggle dry-run, AI content, and auto-engage in configuration.
- Remove accounts in the dashboard; revoke tokens at each platform.
- Delete files under Doc Weather Content and local databases.
- Contact us via linktr.ee/URP for data questions.
6. Related policies
Privacy Policy · Terms of Service · Violations & Acceptable Use