NimbleCal is built to keep your calendar private by default.

What NimbleCal encrypts

NimbleCal encrypts your calendar content on your device before syncing/storing it. This is end-to-end encryption (E2EE): your devices hold the keys needed to read event content.

See: Encryption overview

What NimbleCal still needs to store

Even with E2EE, a calendar app still needs some non-content data to function.

Examples of data that can exist outside the encrypted event payload:

• Account data (like your email address)
• Billing/subscription status
• Limited sync metadata (for example, timestamps used for conflict resolution)
• Reminder scheduling timestamps (so reminders can be delivered)

Invites: what gets shared

When you invite participants to an event, NimbleCal needs to share some event details so the recipient can view the invite and RSVP.

That invite flow can include event details like title, time, location, and description. Only recipients with the invite link (and/or the invited account) can access the invite.

See:

• Invite participants
• RSVP to an invite

Quick Add privacy (important)

Quick Add parsing runs fully on-device:

• The text you type is not sent to NimbleCal servers.
• The text you type is not shared with third-party AI APIs.

See: Quick Add (natural language)