Privacy Policy

Last updated: October 7, 2026

What We Collect

When you connect your Buffer account, we store:

• Your Buffer user ID and email address
• Your Buffer OAuth access and rotating refresh tokens, or your API key, to fetch your scheduled posts
• If you choose API key sign-in, your Buffer API key (stored to authenticate Buffer API requests)
• Your scheduled post content, channels, and times (cached for 24 hours)
• A session cookie to keep you logged in

What We Don't Do

• We don't sell your data
• We don't show ads or use analytics trackers
• We don't share your information with third parties
• We don't access your Buffer account after you disconnect
• We don't store your posts longer than 24 hours (cache expiry)

How It Works

Buffer2iCal fetches your scheduled posts from Buffer's API every 5 minutes. This data is temporarily cached in Cloudflare's KV storage so your calendar app can quickly download it. Cached data automatically expires after 24 hours.

Your Control

You can disconnect your account and all associated data at any time from the Buffer2iCal dashboard. This immediately removes:

• Your Buffer access token
• All cached post content
• iCal feed/api URL
• All session data

Data Security

All data is transmitted over HTTPS. Buffer credentials are stored in the service's Cloudflare KV storage and are never intentionally included in application URLs or logs. Keep your dashboard and calendar feed private because the feed URL allows access to your scheduled posts.

Third-Party Services

We use two external services:

• Buffer - to fetch your scheduled posts (subject to Buffer's Privacy Policy)
• Cloudflare - to host this service and store cached data (subject to Cloudflare's Privacy Policy)

Open Source

This service is free and open source. You can inspect the code, self-host it, or contribute improvements.

• View Source Code (tangled)

Contact

Questions or concerns? Reach out at @danielmorrisey.com on Bluesky.

← Back to Buffer2iCal