Privacy and encryption
Can NimbleCal read my event titles and notes?
For encrypted calendar records you store or sync in the app: no.
NimbleCal encrypts your calendar content on your devices before storage or sync (end-to-end encryption). Your devices hold the keys needed to read event content, and those keys do not leave your devices in plaintext.
Email invites are an exception. See Are invites encrypted end-to-end?.
See:
What data is not encrypted?
A calendar app still needs some non-content data to function (even with end-to-end encryption).
Examples can include:
- Account data (like your email address)
- Billing/subscription status
- Limited sync metadata (for example, timestamps used for conflict resolution)
- Reminder scheduling timestamps, which NimbleCal stores outside encrypted event blobs so reminders can be delivered
For the detailed, canonical explanation, see: Privacy guide
Are invites encrypted end-to-end?
Invites are different from the end-to-end encrypted calendar storage and sync model.
When you invite participants, NimbleCal needs to store and send recipient email addresses for delivery, plus the invitation details recipients and email systems need to understand the invite, including the event title, start/end time, timezone, organizer name/email, optional organizer message, and any event location or description. Anyone with the full invite link can access the invite details, so keep it private.
See: Invite participants
Does Quick Add send my text to an AI API?
No.
Quick Add parsing runs on-device. The text you type is not sent to NimbleCal servers and is not shared with third-party AI APIs.
See: Quick Add with natural language
Account and signup
What personal information do I need to create an account?
An email address.
NimbleCal does not require your real name or a phone number. You can use an alias or forwarding email address if you prefer. Your email is used to identify your account, send essential messages like verification and password reset emails, and associate subscriptions with an account you control.
What data does Friendly Captcha process on signup?
Account signup uses Friendly Captcha to reduce automated abuse.
- The browser loads the Friendly Captcha widget on the signup form.
- For current details on how Friendly Captcha handles end-user data, see the Friendly Captcha Privacy Policy for End Users.
- When you submit signup, NimbleCal verifies the challenge on its own server path before it asks Supabase Auth to create the account.
- NimbleCal does not store the raw captcha response. It keeps hashed proof records, limited verification metadata, and related timestamps needed to enforce the signup boundary and support incident review. See the Privacy Policy for the current retention details.
- This captcha flow currently applies to account signup.
See:
Does login or password reset use the same captcha flow?
No.
Friendly Captcha currently protects account signup, so you should not expect the same widget on login or password reset.
Unlock and recovery
What happens if I forget my password?
Because NimbleCal uses end-to-end encryption, password resets have extra safety steps.
See: Passwords and key recovery
Why do I need to unlock again after restarting my browser?
NimbleCal avoids leaving a reusable local unlock path available longer than needed in the browser. That means a full browser close or restart can require you to unlock again.
If Quick unlock is available on a trusted device, you can use your face, fingerprint, or device PIN instead of typing your password. Quick unlock helps only on that device.
See: Passwords and key recovery
Do you collect biometric data?
No.
If you use Quick unlock, device verification happens through your operating system. NimbleCal does not receive or store biometric templates. Quick unlock data is stored locally in that browser or device and is not uploaded to NimbleCal servers.
See: Passwords and key recovery
Deletion, retention, and regions
What is retained after account deletion, and why?
Deleting your account removes the main account and synced server-side data path, but some records can still remain for billing, refund, dispute, backup, unsubscribe, support, and security reasons.
See the Privacy policy for the current retention details.
See:
Where is my data processed, and what does "EU region" mean here?
Today, NimbleCal's main production data path is EU-first, not EU-only.
Several services are configured for Germany/EU:
- The production Supabase project
- Vercel's non-global compute, where that control exists
- Sentry crash-report storage
Several supporting vendors are also Europe-first or Europe-based, including AhaSend, Plausible, Friendly Captcha, and Proton Mail.
That still does not mean every supporting path is EU-only, because some services involve global edge delivery, cross-border billing/compliance flows, Switzerland-based contact inbox hosting, or other vendor subprocessors.
See:
Privacy requests and legal process
How do I make a privacy or data-rights request?
Email privacy@nimblecal.com and tell us what you need help with. If possible, send the request from the email address on your account and include your country of residence so NimbleCal can respond with the most relevant rights information.
NimbleCal may need to verify your identity before fulfilling the request.
Because calendar content is end-to-end encrypted and NimbleCal cannot decrypt it server-side, access and export for that content are usually handled client-side from the app while you are logged in.
See:
What happens if NimbleCal receives a legal demand for my data?
NimbleCal can only provide data it actually has access to.
For encrypted calendar records you store or sync in the app, event titles, notes, and other encrypted calendar content are protected with end-to-end encryption, so NimbleCal cannot hand over plaintext calendar content it cannot read.
NimbleCal may still have access to other records, such as account information, subscription and billing metadata, support emails you send directly, operational crash diagnostics if enabled, invite data, and other server-side logs or records it is legally required to keep.
See:
Billing and refunds
What billing data does NimbleCal receive?
Paid subscriptions are processed through Paddle, which acts as NimbleCal's merchant of record for paid subscription orders.
Paddle and its payment partners handle payment-method details such as full card or bank account numbers. NimbleCal stores the subscription metadata needed to provide Plus and support billing, such as plan, status, customer identifiers, customer email, renewal state, cancellation state, and related timestamps. If you request a refund or there is a payment dispute, NimbleCal may also process related refund or dispute metadata, such as refund status, dispute identifiers, resolution timestamps, and related support notes.
See:
What happens if my subscription lapses or I get a refund?
NimbleCal does not delete your data automatically just because your plan changes.
If your paid subscription ends, your account falls back to the Free plan. You keep your existing calendars and events, but Free plan limits apply again. If you are over the Free plan limits, you can still view your data, but creating new calendars or events is blocked. Editing events in calendars beyond the Free plan limit is also blocked until you are back under the limit or upgrade again.
If you receive a refund, the paid subscription is canceled and the account falls back to Free. Refunds do not delete your data.
See:
Diagnostics and security contact
What do crash reports include?
If crash reports are enabled, they are operational diagnostics for unexpected client-side errors. They use a narrow, predefined payload that can include build version, a general route area, general browser and operating-system family, online/offline state, error type, sanitized stack-frame labels, and predefined diagnostic fields.
The payload is defined to exclude event titles, descriptions, notes, locations, email addresses, invite links, full query strings, and session replay data.
You can turn crash reports off in Settings. This preference applies only to the current browser.
See:
Do you use analytics or tracking?
The NimbleCal app does not run analytics scripts, advertising, or cross-site tracking.
The NimbleCal website uses Plausible for cookie-free aggregate pageview analytics and limited website click-event labels, such as CTA, checkout, or support-link clicks.
See:
How do I report a security issue?
Email: security@nimblecal.com
If you can, include:
- A short description of the issue
- Steps to reproduce
- Screenshots (with private event data redacted)