Is SafeCal Safe?
How Your Calendar Data Is Handled

Last updated: 2026-03-18

SafeCal does not store your calendar events (titles, locations, descriptions, attendees) in any database. Calendar data is fetched from your upstream ICS URL on each request, filtered in memory, and returned as the response. It is never written to permanent storage. Not even SafeCal's operators can view your calendar contents.

What is stored vs. what isn't

DataStored?Details
Your ICS URLYesServer-side only, never sent to browser.
Filter settingsYesFilter mode, keyword mask, prefix/suffix.
Calendar eventsNoTitles, locations, descriptions, attendees — never stored.
Calendar cacheTemporaryCDN edge cache, max 24h. Not permanent storage.

How data flows

  1. Calendar app requests your SafeCal URL
  2. Feed config loaded from Workers KV (ICS URL + filter settings)
  3. Upstream calendar fetched via HTTPS (cached up to 5 min)
  4. Filters applied in memory
  5. Filtered ICS returned. Original data discarded from memory.

Operators cannot see your calendar. No event data is stored in any database or admin panel. Only your ICS URL and filter settings are accessible.

Getting your ICS URL from each service

To use SafeCal, you need your calendar's ICS URL. Here's where to find it:

Read our full Privacy Policy

Get Started Free

FAQ

Can SafeCal operators see my calendar events?

No. Calendar event data is never stored in any database. It is processed in memory and discarded after each response. Operators can only access your ICS URL and filter settings.

Where is my data stored?

Calendar content is not permanently stored. CDN cache holds upstream data for up to 24 hours as a fallback. Only feed configuration (ICS URL, filter mode) is stored in the database.

Is my ICS URL safe with SafeCal?

Your ICS URL is used server-side only and never sent to the browser or included in API responses. Row Level Security prevents other users from accessing it.

Related Articles