Privacy Policy

Last updated: 23 October 2026

TapCal is operated by Jonathan Jones trading as JonsTech ("TapCal", "we", "us" or "our"). We are the data controller for the personal information we process to provide the TapCal app, tapcal.app, and our support services. Apple, your calendar providers and other services also have their own responsibilities for information they process independently.

This policy explains what information TapCal accesses, how it is used and shared, where it is stored, and the choices available to you. The features you use, permissions you grant, and accounts you connect determine which information is processed.

1. How TapCal works

TapCal brings calendars and reminders together on your iPhone and in widgets. You can use calendars managed by iOS, connect Google or Microsoft accounts directly, or add subscription calendar feeds.

You do not need to create a separate TapCal login. Connecting an existing Google or Microsoft account is optional and gives TapCal the access described on that provider's permission screen.

Calendar and reminder content is processed and cached on your device. For a directly connected account, TapCal exchanges calendar information and changes with Google or Microsoft through their APIs. For accounts managed by iOS, Apple and the account provider handle account syncing. We do not operate a hosted database containing a copy of your calendars.

Some other information is sent to service providers: for example, limited usage measurements, advertising requests, and feedback you choose to submit. These are explained below.

2. Calendars, events and reminders

Calendars and reminders managed by iOS

If you grant Calendar or Reminders permission, TapCal uses Apple's EventKit framework to access the calendars, events, reminder lists and reminders available on your device. Depending on the feature, this can include:

Calendar and list names, colours, identifiers and account information exposed by iOS.
Event and reminder titles, notes, dates, times, time zones, locations and links.
Recurrence rules, availability, priority, completion status and alert settings.
Organiser and attendee information, invitation responses and other meeting details exposed by the calendar service.

TapCal uses this information to display your schedule, search, create and edit items, show invitations, provide widgets, and schedule reminders and alerts. Changes you save are written to the selected calendar or reminder account. Apple and your configured provider may then sync them to other devices or participants.

Accounts connected directly to TapCal

When you connect Google or Microsoft, TapCal accesses the information authorised for that account. This can include:

Your account identifier, email address and basic profile information returned during sign-in, so TapCal can distinguish connected accounts.
Calendar names, identifiers, descriptions, colours, time zones, ownership and access roles.
Event details, including titles, descriptions or notes, dates and times, recurrence, locations, links, meeting information, organisers, attendees, responses and personal alert settings.
Calendar-sharing information, including the people or other principals with access and their permissions, where your account is allowed to see it.
Provider metadata needed to sync correctly, preserve existing event details, detect conflicting changes and avoid duplicate writes.

TapCal uses this access to show your calendars and events, keep them up to date, and carry out actions you request. These actions may include creating, editing or deleting events and calendars, responding to invitations, changing alerts, and managing calendar sharing. Available actions depend on the provider, the permissions you grant and your role on the calendar or meeting.

Connecting a calendar account does not give TapCal access to read your email messages. The Google and Microsoft calendar integrations do not request mailbox-reading permissions.

Invitations and sharing

When you invite someone to an event or share a calendar, their email address and the relevant event or access information are sent to the calendar provider. The provider may notify recipients and make the information available to other authorised participants. Organisers and other participants may see your name, email address, response and changes according to the provider's rules.

Removing someone or changing their permissions affects future provider-controlled access. It cannot remove copies, notifications or information they have already received.

Storage and authentication

TapCal keeps local calendar snapshots, account and sharing metadata, settings, and queued changes so the app and widgets can work together and display saved information. Pending changes may remain on the device until they are uploaded, resolved or discarded.

Google and Microsoft sign-in is handled through their authentication services and SDKs. TapCal does not receive or store your Google or Microsoft account password. Authentication tokens and SDK credentials are stored using the iOS Keychain; calendar caches and account metadata are stored separately in the app's local storage.

The app shares relevant local data with its own widgets and extensions through an App Group. This does not make that data available to unrelated apps.

3. Google user data and Limited Use

TapCal uses Google account and Calendar API information to provide and improve the calendar features described in this policy. Permission requests distinguish access to calendar lists, calendar properties, events and sharing. Some features require additional permission; you can decline it, although the feature that needs it will be unavailable.

Our handling and disclosure of information received through Google APIs follows the Google API Services User Data Policy, including its Limited Use requirements.

We do not sell Google user data, supply it to advertising platforms or data brokers, use it to target advertisements, or use it to train general-purpose AI models. Google calendar access is separate from any advertising supplied by Google AdMob.

Google data is exchanged with Google and with recipients of calendar actions you authorise. Limited feature-use summaries may be processed by our analytics provider as described in section 7, to understand and improve TapCal's visible features. We do not send event titles, descriptions, attendee email addresses, exact event dates or event location coordinates to that analytics service.

We do not routinely read your calendar content. If you choose to send specific calendar information in a support request, we may read that information to help you. Any other access or disclosure must be permitted by Google's Limited Use rules, such as where necessary for security or a legal requirement.

4. Other optional features and permissions

Contacts

If you grant Contacts permission, TapCal can match event participants to contacts on your device and show contact names, photos and contact cards. This lookup happens on the device. TapCal does not upload your address book to our servers, analytics service or advertising service.

An email address you explicitly use to invite someone is sent to the relevant calendar provider as part of that action.

Weather and location

If enabled, weather features use your current location or a location you select to request forecasts through Apple WeatherKit. Apple may also process location information for map searches, location previews and place-name lookup.

TapCal saves the selected weather location and caches the latest forecast and its location coordinates on your device so the app and widgets can reuse them. We do not build a movement or route history.

Location-based reminder alerts use the places and arrival or departure conditions you choose. Background location permission may be needed for these alerts while the app is not open. Location information can also be part of a reminder or event that you save to your calendar or reminder account.

You can change location permission in iOS Settings. Turning it off can prevent current-location weather and location-triggered alerts from working.

Notifications and urgent alarms

With your permission, TapCal schedules local event and reminder notifications and, where supported and enabled, urgent reminder alarms. Notification and alarm information is passed to Apple's system services on the device. Providers may also send their own event alerts or invitation messages.

Notifications, alarms and widgets can display event or reminder information on your Home Screen or Lock Screen. You control their visibility through TapCal's available settings and the relevant iOS settings.

Natural-language event input and system integrations

TapCal's natural-language event parsing runs on the device. We do not send the text you enter for this feature to an external AI service. If you invoke Siri, Shortcuts or other Apple services, Apple handles those interactions under its own privacy information.

Subscription calendar feeds and external links

If you add a subscription calendar URL, TapCal downloads that feed and stores its events locally. The feed host receives the request, including ordinary network information such as your IP address. A private feed URL may itself contain an access token; treat it as confidential.

Opening an event link, map, support link or other external website can send information to that service under its own policy.

5. Purchases and subscriptions

Apple processes purchases, subscriptions, restoration and billing through the App Store. TapCal receives the product, transaction-verification and entitlement information needed to determine your access, restore purchases and handle subscription status. We do not receive your full payment-card details.

Limited purchase outcomes and plan status are included in product analytics. Receipt contents and transaction identifiers are not sent as TapCal analytics event properties.

6. Feedback and support

When you email us or submit feedback, we receive the message and any email address or attachments you choose to include.

In-app feedback also includes the app version, iOS version, device model and model code, locale, time zone, plan tier and a request identifier used to avoid duplicate submissions. The model code identifies a device type, such as an iPhone model; it is not the device's serial number. Support or tip messages may include the selected support tier.

In-app submissions are sent over HTTPS to a Cloudflare Worker and stored in a private Notion database for support and app improvement. Cloudflare and other communication providers may process network information such as IP addresses when handling requests.

Feedback is not automatically accompanied by your calendar contents or account credentials. Please include only the information needed to explain your issue. If you voluntarily include personal information about yourself or another person, it becomes part of your support message.

7. App analytics

TapCal uses PostHog to understand feature use, diagnose problems and improve the app. Measurements are associated with a pseudonymous installation or SDK identifier; they are not necessarily anonymous.

These measurements can include:

App and operating-system versions, device and technical information, timestamps and network information received by the service.
Screens and features used, onboarding steps, permission statuses and outcomes, and whether actions succeed or fail.
Theme and font choices, widget configurations, subscription tier and purchase outcomes.
Limited event and reminder characteristics, such as whether an item is all-day or recurring, its recurrence category, whether notes or a location are present, reminder priority, and broad duration or timing ranges.
Counts or ranges, such as calendar-set size, search-text length and search-result count. The actual search text is not sent.

These summaries help us understand how features are used. TapCal does not send event or reminder titles, note text, location text or coordinates, attendee email addresses, calendar account email addresses, account passwords or authentication tokens as analytics event properties. The app does not enable PostHog session replay to record your screen.

PostHog can receive ordinary connection information, including an IP address, when the app contacts it. Purchase of TapCal Pro removes the app's advertising; it does not by itself disable product analytics.

You can contact us to ask about analytics information associated with your use. Because it is linked to a pseudonymous identifier rather than your email address, we may need additional information to locate a particular record.

8. Advertising

The free version of TapCal can display banner advertisements using Google AdMob. The Google Mobile Ads SDK may process IP addresses, app- or device-related identifiers permitted by iOS, ad requests and interactions, and diagnostic or performance information to provide, measure and protect advertising. An IP address may be used to estimate general location.

The availability and use of identifiers and personalised advertising depend on applicable permissions, privacy settings, service configuration and legal requirements. TapCal does not send your calendar or reminder contents, Google Calendar API information, contact records or precise device-location coordinates to AdMob for advertising.

See Google's privacy policy and Google's advertising controls for information about Google's processing and available choices. iOS also provides privacy and tracking controls. TapCal Pro removes in-app advertisements.

9. Website information and cookies

Our website and its hosting and security providers process information needed to deliver and protect the site, such as IP addresses, browser information, request times, requested pages, referring pages and error logs. If you contact us, we also process the information you submit.

The website does not use Google Analytics, DoubleClick or advertising-tracking cookies. Website hosting and security services may use essential cookies, local storage or similar technologies to deliver the site, protect it from abuse or remember necessary preferences. See our Cookie Policy for more information.

Your browser lets you restrict or remove cookies and local storage. External sites can apply their own privacy and cookie policies when you follow their links. App analytics and advertising are separate from the website and are described in sections 7 and 8.

10. Why we process information

We use information for the specific purposes explained above: providing requested calendar and reminder features, authenticating connected accounts, carrying out your changes and sharing instructions, delivering optional weather and alerts, managing purchases, responding to support requests, measuring app use and protecting the services.

Where UK or European data protection law applies, the legal basis depends on the activity:

Providing the service you request: processing necessary to deliver app features, account connections, purchase access and support under our contract with you.
Consent: optional access or processing for which we request consent, and advertising or analytics technologies where the law requires it. You can withdraw consent through the relevant controls or by contacting us. Withdrawal does not affect processing that was lawful before it was withdrawn.
Legitimate interests: keeping the app and website secure and reliable, responding to enquiries, and limited product measurement where permitted. These interests are balanced against your privacy and rights.
Legal obligations: processing needed to meet applicable legal requirements or respond to lawful requests.

An iOS or provider permission gives the app technical access to a feature; it is not blanket permission to use your information for unrelated purposes. Declining optional access can limit the feature that needs it while leaving other available features usable.

We do not use your information to make solely automated decisions that produce legal or similarly significant effects about you.

11. Who receives information

Information is disclosed only for the purposes described in this policy, including to:

Apple: operating-system features, EventKit, WeatherKit, Maps, notifications, alarms and App Store purchases.
Google and Microsoft: authentication, calendar access and actions you authorise for connected accounts.
Calendar participants and sharing recipients: information needed for invitations, responses and access changes you request.
PostHog: limited product analytics and technical information.
Google AdMob: advertising and related technical information when ads are used.
Cloudflare, Notion and communication providers: website delivery or security, feedback and support.
Subscription-feed hosts and external services: when you request their content or open their links.

Providers process information under their applicable terms and privacy policies. Some act on our behalf for particular services; others, such as your calendar provider or Apple when handling your account and purchases, also determine their own purposes and responsibilities.

We may disclose information where required by law or necessary to protect rights and investigate security or abuse. If the business changes ownership, any transfer must respect this policy, applicable law and, for Google user data, Google's Limited Use requirements and any required prior consent.

We do not sell your calendar information or use it to target advertisements.

12. Where information is processed

Your calendar caches, app settings and locally scheduled alerts are held on your device. Google, Microsoft, Apple and our other service providers may process information in other countries, including the United Kingdom, the European Economic Area and the United States, depending on the service and its hosting arrangements.

Where we are responsible for a transfer that requires safeguards under data protection law, those safeguards must apply to the transfer, for example an applicable adequacy decision or appropriate contractual protections. Contact us for information about the arrangements relevant to your request.

Provider privacy information is available here:

13. Retention and deletion

We retain information for the purpose for which it is needed. The period depends on the type of information, whether a feature or account is active, unresolved changes or support issues, security needs and applicable legal obligations.

Local calendars and caches: TapCal keeps information needed to display your calendars, use widgets, sync changes and recover from interrupted operations. Cached ranges and completed operation history are managed locally. Some local account metadata, cached content, templates or recovery records can remain after account access is disabled or an item is deleted.
Pending changes: unresolved or unsent changes can remain until they are uploaded, resolved or explicitly discarded. TapCal may require you to resolve pending work before disconnecting an account.
Authentication: the relevant locally stored credentials are removed when disconnection completes, unless the same account grant is still needed for another active TapCal connection. Provider-side revocation is a separate control and may be needed to end all authorisation.
Weather, settings and other local features: saved settings and caches remain while needed for those features or until cleared or removed with the app's data.
Analytics: records are retained for as long as needed to understand feature use, investigate reliability and compare app improvements, taking account of the detail of the records and the available retention controls. Information no longer needed for these purposes should be deleted or de-identified.
Feedback and support: correspondence and technical details are retained while needed to handle the request, follow up a reported issue, maintain relevant support history or meet legal requirements. You can request deletion.
Provider records and backups: Google, Microsoft, Apple and other providers control retention in their own systems. Device or cloud backups may retain earlier copies under their own settings and deletion processes.

Disconnecting TapCal does not delete calendars or events from Google, Microsoft or an account managed by iOS. Revoking permission does not automatically erase data already cached on your device. Use the provider or relevant calendar controls to delete remote items, and remove local app data if you want to clear local copies. Offloading an iOS app can retain its data; deleting the app and managing any backups are separate steps. Keychain credentials can also survive app deletion, so use disconnection and provider revocation before uninstalling if you want to end access.

For information we hold through support or analytics services, contact hello@tapcal.app to request access or deletion. We may need to verify your request and identify the relevant records. We cannot remotely inspect or erase an on-device-only calendar cache.

14. Your choices and rights

You can:

Review or change Calendar, Reminders, Contacts, Location, Notifications and other permissions in iOS Settings.
Manage and disconnect accounts in TapCal's Connected Accounts settings.
Revoke TapCal's access through your Google account's third-party connections settings or Microsoft's application-permission controls. Work or school accounts may require action from an administrator.
Change sharing permissions or delete items using the appropriate calendar controls.
Manage App Store subscriptions and device backups through Apple.
Contact us about information held in support or analytics systems.

Depending on your location and the circumstances, data protection law may give you rights to access or obtain a copy of personal information, correct it, request deletion, restrict processing, receive portable data, and withdraw consent.

You may object to processing based on legitimate interests. Contact us to explain your request. Where that right applies, we will stop the processing unless the law allows us to continue for compelling reasons or legal claims. You may also object to direct marketing if applicable.

These rights are subject to legal conditions and exceptions. We normally respond to applicable data-rights requests within one calendar month; where the law permits an extension, we will explain it. We may ask for information proportionate to verifying the request.

You may complain to your local data protection authority. In the UK, this is the Information Commissioner's Office. You can also raise a privacy concern directly with us at hello@tapcal.app.

If California privacy law applies to your use, you may have additional rights to know about, access, correct or delete personal information, to opt out of a sale or sharing for cross-context behavioural advertising where applicable, and to exercise your rights without unlawful discrimination. Contact us to make a request; available rights and exceptions depend on the law's application to our services.

15. Security

TapCal uses platform protections, Keychain storage for authentication credentials, and HTTPS for supported online services. Calendar content is not included in routine analytics event properties, and support records are held in access-restricted services.

Protect your device and connected accounts, use available account security controls, and avoid sharing private feed URLs or authentication information. No app, storage system or network transmission can be guaranteed completely secure.

16. Children

TapCal is not directed at children under 13. We do not knowingly collect children's personal information through our support, analytics or other services in circumstances where parental authorisation is required and has not been obtained. Contact us if you believe a child has provided information that needs to be removed. We will assess the request and take appropriate action.

17. Changes to this policy

We may update this policy when features, providers or data practices change. The latest version will be published on this page with an updated date. Where a change requires notice or fresh consent, we will provide it before using information for the new purpose.

18. Contact

Jonathan Jones trading as JonsTech
Operator of TapCal
Website: www.tapcal.app
Privacy and support: hello@tapcal.app