Privacy Policy

Calendar+ 2 · Last updated: June 13, 2026

Short version Calendar+ 2 is a local-first calendar app. Your calendar events, reminders, settings, and contact data stay on your device — we never receive them, with one exception you control: the optional AI features (AI Quick Add, the AI Assistant, and the AI Daily Planner). When you choose to use those, the text you type — and, for the AI Daily Planner only, the titles and times of nearby existing events plus your calendar names — is sent to our backend and to our AI provider (Anthropic) to generate a suggestion (see section 2.8). We also collect anonymous usage analytics (which features and screens are used, and whether a purchase is completed) through Google Firebase Analytics to understand how the app is used and to improve it. We do not use advertising SDKs or advertising identifiers, and we do not sell, share, or rent your personal information to third parties.

1. Who we are

Calendar+ 2 (“the app”, “we”, “us”) is developed and published by Joshua & Company Inc. This Privacy Policy explains what information the app accesses on your device, why it accesses it, and how it is handled.

If you have any questions about this policy, you can reach us at admin@joshuanco.com.

2. Information the app accesses

Calendar+ 2 acts as a client for the calendar database that already exists on your device (Android Calendar Provider on Android, EventKit on iOS). It does not maintain a cloud account for your calendar data and never stores your events on our servers. The only server we operate is a small backend that powers the optional AI features described in section 2.8, and it is contacted only when you actively use one of those features.

2.1 Calendar data

The app reads and writes calendar events, reminders, attendees, and calendar-account metadata through the operating system’s calendar APIs.
Events you view or edit in Calendar+ 2 are the same events stored by the calendar accounts you have already configured on your device (for example, Google, iCloud, Exchange, or a local-only calendar).
Synchronization with those accounts is performed by the operating system and by the account providers, not by Calendar+ 2. Whether your events are uploaded to a cloud provider depends on the account you chose in the OS — not on this app.
The app does not transmit your events to us or to any third party that we operate.

2.2 Contacts

If you grant the contacts permission, the app reads contact names, email addresses, and contact photos so it can suggest attendees while you type and display a photo or initial next to a participant.
Contact lookups happen entirely on the device. The app does not upload your contact list.
You can revoke the contacts permission at any time in your system settings; attendee autocomplete and photos will simply be disabled.

2.3 Notifications

The app schedules and posts local notifications for event reminders and snooze. These notifications are generated on your device by the operating system — we do not operate a push server.
The app may request the notification permission and, where applicable, the exact-alarm permission so reminders fire at the correct moment.

2.4 App settings and preferences

Your in-app preferences (theme, week start day, view type, widget configuration, default reminder, quick responses, holiday filter, etc.) are stored locally on your device.
These settings are not sent to us. They may be included in your standard operating-system backup (Android Auto Backup / iOS device or iCloud backup) if you have that feature enabled; that backup is managed by the OS vendor, not by us.

2.5 Photos / images (widget background)

If you choose a photo from your library as a widget background, the app reads that single image and stores a derived (e.g. blurred) copy in its own app-private storage so the widget can render it.
The app does not scan your photo library beyond the image you explicitly pick, and it does not upload any image.

2.6 Purchases and subscriptions

Premium features, if any, are unlocked through Google Play Billing (Android) or the App Store (iOS). The payment, billing address, and subscription state are handled by Google or Apple under their own terms and privacy policies.
Calendar+ 2 only receives a signal from Google Play or the App Store that indicates whether your purchase is currently active. We do not see your payment instrument, name, or billing address.
Subscriptions and the “is this purchase active?” entitlement check are managed for us by Adapty, a subscription-management provider. Adapty assigns a pseudonymous profile identifier (a random ID, not your name or email), which is also used to check your monthly allowance for the AI features in section 2.8. The underlying payment and billing details remain with Google or Apple. See Adapty’s Privacy Policy.

2.7 Usage analytics

To understand how the app is used and to improve it — for example, which calendar views and features are popular and whether onboarding leads to a purchase — the app uses Google Firebase Analytics.
Firebase Analytics collects anonymous, aggregated information such as the in-app actions you take (for example, switching calendar views, creating an event, opening the upgrade screen, or completing a purchase), general device and operating-system information, a randomly generated app-instance identifier, and an approximate (city-level) location derived from your IP address.
We deliberately do not send the content of your events, reminders, or contacts to analytics. Event-related metrics are recorded only as non-identifying counts and categories (for example, “an event was created”) — never the titles, notes, attendees, times, or locations of your events.
We do not use the iOS advertising identifier (IDFA) or the Android advertising ID, and analytics is not used for advertising or cross-app tracking.
This data is processed by Google as our service provider. See Google’s Privacy Policy and how Firebase uses data. Event-level data is retained for a limited period under our Firebase configuration; aggregated, non-identifying reports may be kept longer.
Where required by law — for example, for users in the European Economic Area (EEA), the United Kingdom, or Switzerland — analytics is automatically disabled and no usage data is collected. The app determines the applicable region at launch and does not collect analytics from those users.

2.8 AI features (optional)

Calendar+ 2 offers optional AI-assisted features: AI Quick Add and the AI Assistant (turn a phrase like “lunch with Sam Friday 1pm” into an event or a calendar action) and the AI Daily Planner (turn a free-text to-do list into a time-blocked schedule). Unlike the rest of the app, these features send data off your device, so they are described separately here.

They are opt-in. Nothing is sent unless you actively type into one of these features and ask it to generate a result. They never run in the background.
What is sent. For AI Quick Add and the AI Assistant: the text you type, plus your current time, time zone, and language so the result is interpreted correctly. For the AI Daily Planner, additionally — so it can schedule around what you already have — the titles and start/end times of your existing events in the days being planned, and the display names of the calendars you can write to (for example “Work” or “Personal”) so a suggestion can be filed to the right one.
What is not sent. We do not send your calendar account addresses or IDs, event identifiers, attendees, locations, notes, your contacts, or any event outside the range you are planning. Your name, email, and payment details are never sent to the AI features.
How requests are identified. To check your monthly usage allowance, each request includes a pseudonymous subscription profile identifier from our payments provider, Adapty (see section 2.6). It is a random ID, not your name or email.
Who processes it. The request is received by our own backend, which runs on Cloudflare (which also routes the AI request), and is processed by Anthropic (the maker of the Claude AI models) to generate the response. They act as our service providers. Under Anthropic’s commercial API terms, your inputs and the generated outputs are not used to train its models and are retained only for a limited period.
What we store. Our backend does not store the text you send, your events, or the AI’s responses. It keeps only a per-month usage counter and a cached subscription-status flag, both tied to the pseudonymous Adapty identifier above. Our server logs record only the aggregate processing size (token counts), never the content of your request.
In transit. All AI requests are sent over an encrypted (HTTPS/TLS) connection.
Availability. Unlike analytics (section 2.7), the AI features are available in all regions, including the EEA, the UK, and Switzerland. If you use them there, the data described above is sent and processed to provide the feature you requested. Because Anthropic and Cloudflare may process the request on servers outside your country (including the United States), using an AI feature may involve an international transfer of the data you submit.

See Anthropic’s Privacy Policy and Cloudflare’s Privacy Policy for how those providers handle data on our behalf.

3. Information we do not collect

We do not operate a server that stores your events, reminders, or contacts, and we never transmit the content of your calendar data off your device — except for the optional, opt-in AI features described in section 2.8, where data you submit is sent to generate the result you asked for.
We do not use advertising SDKs, attribution SDKs, or advertising identifiers (Apple’s IDFA or Android’s Advertising ID), and we do not use analytics for cross-app tracking. Our only analytics is the anonymous usage measurement described in section 2.7.
We do not assign you an account or require a sign-up. Firebase Analytics uses a randomly generated app-instance identifier that is not tied to your identity.
We do not sell, rent, or share your personal information with data brokers or advertisers.

4. Permissions explained

The following permissions may be requested, depending on platform and feature usage. You can grant or revoke each of them in your system settings at any time.

Calendar (read & write) — required for the core feature: viewing, creating, editing, and deleting events.
Contacts (read) — used only for attendee suggestions and avatars. Optional.
Notifications — required to deliver local event reminders.
Exact alarms / full-screen intent (Android) — allows reminders, including snoozed reminders, to fire at the precise time and to show a heads-up popup.
Photos / media (when selecting a widget background) — used only at the moment you pick an image.
Billing — required by Google Play / the App Store to process in-app purchases.

5. Children

Calendar+ 2 is a general-audience productivity app and is not directed at children under 13. The app does not knowingly collect personal information from children. If you believe a child has provided personal information to us directly, please contact us at the address below and we will help address it.

6. Security

Because Calendar+ 2 stores its data locally on your device, security primarily depends on your device’s own protections (screen lock, full-disk encryption, OS account security). We rely on standard platform sandboxing so that other apps cannot read Calendar+ 2’s private files.

When you use an optional AI feature (section 2.8), the data for that request is transmitted to our backend and AI service providers over an encrypted (HTTPS/TLS) connection.

Calendar accounts that you have configured on your device (Google, iCloud, Exchange, etc.) are managed by their respective providers and are subject to their security and privacy practices.

7. Your choices

You can revoke any of the app’s permissions at any time in your system settings.
You can delete the app to remove all locally stored Calendar+ 2 data (settings, widget configuration, and any locally cached widget backgrounds). Events stored in your device’s calendar accounts are not deleted by uninstalling Calendar+ 2 — they belong to the underlying account (e.g. Google, iCloud) and must be deleted from there if you wish.
You can manage or cancel any subscription through Google Play or the App Store, under your own account settings.
We do not use advertising identifiers, and analytics is limited to the anonymous usage data described in section 2.7. You can reset the random app-instance identifier at any time by reinstalling the app, and you can contact us at the address below to request that we limit or delete this data.

8. Legal bases (GDPR / UK GDPR)

Where the GDPR or UK GDPR applies, our limited on-device processing is performed on the following bases:

Performance of a contract — providing the calendar functionality you have asked the app to perform.
Consent — for permissions you explicitly grant (contacts, notifications, photo selection).
Legitimate interests — basic, on-device operation of the app, protection against abuse, and the anonymous usage analytics described in section 2.7 (to measure feature usage and improve the app). You may object to analytics processing by contacting us.
Your request — when you actively use an optional AI feature (section 2.8), we send the data described there to our service providers to produce the suggestion you asked for.

The optional AI features (section 2.8) involve sending the data you submit to service providers (Anthropic and Cloudflare) that may process it outside your country, including in the United States. Those providers process the data under their own privacy terms, which include international data-transfer mechanisms.

We do not store your calendar content on our own servers, so for that data we are generally not in a position to provide an export or deletion of information we do not hold — to exercise rights against data held by your underlying calendar account provider, please contact that provider. For the anonymous usage analytics described in section 2.7, which is processed by Google on our behalf, you may contact us to request access or deletion, and we will act on it together with Google where technically possible.

9. California residents (CCPA / CPRA)

We do not “sell” or “share” personal information as those terms are defined by the CCPA/CPRA. Our analytics is configured without Google Signals or ad-personalization features, and we do not knowingly process the personal information of California consumers for cross-context behavioral advertising.

10. Changes to this policy

We may update this Privacy Policy from time to time, for example to reflect new features or legal requirements. When we do, we will revise the “Last updated” date at the top of this page. Material changes will be highlighted in the app or on the page where this policy is hosted.

11. Contact

Questions, requests, or concerns about this Privacy Policy or about Calendar+ 2 can be sent to:

Joshua & Company Inc.
Email: admin@joshuanco.com