Privacy Policy for Privacy Advocates

Our Approach

Online privacy is complex in the modern internet. We can't control what other services do with your data. What we can do is maintain a minimal-data approach to our scheduling service.

This policy explains exactly what we collect, what we don't, and why we need it.

What We Collect

• Email address: For magic links. No passwords = one less thing to leak
• OAuth tokens: To post on your behalf. Encrypted with AES-256-GCM, rotated monthly
• Recent posts: To mimic your style. Analyzed locally, deleted after 90 days
• Payment info: Stripe handles this. We see "customer_xyz paid" not your card
• Basic analytics: Page views, not behavior. We use Plausible, not Google Analytics

Our Zero-Knowledge Architecture

We've designed the system so we know as little as possible:

• Content separation: We don't know which posts are yours vs ours
• No behavioral tracking: We don't track clicks, scrolls, or dwell time
• No cross-referencing: Payment data and social data never meet
• Local processing: Style analysis happens on isolated containers
• Audit logs: You can see everything we've posted, when, and why

How We Store Data (The Technical Part)

• Database: PostgreSQL with row-level encryption
• OAuth tokens: Redis with 30-day expiry, encrypted at rest
• Backups: Encrypted with GPG, stored in privacy-respecting jurisdiction
• Logs: Rotated daily, auto-deleted after 7 days
• Infrastructure: Servers in Iceland/Switzerland (they still respect privacy)

Your Rights (They're Real)

• Access: Download all your data in JSON format anytime
• Deletion: Delete account = delete data within 48 hours
• Correction: Fix any incorrect data immediately
• Portability: Export to standard formats (JSON, CSV)
• Objection: Opt out of any processing you don't like
• Transparency: See exactly what we've posted and when

Data Retention (We're Not Hoarders)

• Posts: 90 days then auto-deleted
• OAuth tokens: 30 days then refreshed
• Payment records: 3 years (tax law requires this)
• Account data: 30 days after cancellation
• Logs: 7 days rolling window
• Backups: 90 days then purged

Cookie Policy (Just the One)

We use exactly one cookie: session_token for authentication.

• No tracking cookies
• No advertising cookies
• No analytics cookies
• No third-party cookies
• No fingerprinting scripts

The modern web relies on many tracking cookies. We use minimal cookies - just one session cookie.

Government Requests

When the feds come knocking (they haven't yet):

• We require valid warrants, not requests
• We notify you unless legally gagged
• We publish transparency reports
• We can only provide what we have (which isn't much)
• Canary: As of September 2025, zero requests received

Breaches (When, Not If)

Every service gets breached eventually. When it happens:

• Notification within 72 hours
• Full disclosure of what was accessed
• OAuth tokens auto-revoked
• Detailed timeline and remediation steps
• No corporate speak or minimization

Policy Changes

When our service evolves, we'll update this policy. Changes announced via:

• Email notification 30 days before changes
• Dashboard banner for logged-in users
• Changelog at /privacy-changelog
• No retroactive changes to existing users

Our Philosophy

We believe in minimal data collection. We collect only what's necessary to provide our scheduling service. Every byte we collect serves a specific purpose.

We're committed to transparency about what we collect and why.