CalmAgenda — Privacy Policy

Effective date: May 25, 2026  ·  Last updated: May 25, 2026

App: CalmAgenda (iOS bundle identifier com.calmagenda.app)
Publisher / data controller: Kevin Delgado Pagán ("we", "us", "our")
Contact: https://kevindelgadopagan.com/#contact-me

This policy describes what information CalmAgenda processes when you use the app, and what information third parties (specifically Google AdMob and its ad-network partners, and Apple) may process on our behalf so that we can show ads and accept payments. CalmAgenda is a local-first reminders and to-do app — we do not operate a server, we do not have user accounts, and we do not collect, store, or have access to any of the content you create in the app.

1. Summary (plain-English)

• We don't operate a backend. All of your reminders, to-do lists, and settings are stored only on your device using iOS's local key-value storage. They never leave your device through any system we control.
• We don't run our own analytics, crash reporting, or telemetry. There is no Firebase, Sentry, Crashlytics, Mixpanel, Amplitude, or similar SDK in the app.
• We don't use push notifications. Reminders are delivered by iOS's local notification system, scheduled on your device.
• We don't sell or share your personal data for our own marketing purposes.
• We do show ads through Google AdMob in the free version. Google and its ad-network partners receive and process information from your device to show those ads and prevent fraud (details in Section 4). You can limit this through Apple's App Tracking Transparency prompt and — once it is integrated — through the in-app Settings → Privacy → Privacy choices entry that opens Google's UMP consent screen.
• You can remove ads through an in-app purchase. Purchases are processed by Apple, not by us.
• You can erase all data we touch at any time by deleting the app from your device.

Interim status — EEA, UK, and Switzerland. CalmAgenda does not currently present a Google-certified Consent Management Platform (CMP). Google requires a CMP — typically its own User Messaging Platform (UMP) — before the Google Mobile Ads SDK may be initialized for users in the EEA, the United Kingdom, or Switzerland. We intend to integrate UMP as soon as possible. Until UMP is integrated, CalmAgenda is not distributed in the EEA, the UK, or Switzerland, and the Settings → Privacy → Privacy choices entry described below is not yet present in the app. This policy will be updated when UMP ships.

2. Information CalmAgenda stores on your device

The following information is created by you and stored locally on your device using @capacitor/preferences (Apple's NSUserDefaults) and localStorage. It is not transmitted to us and not transmitted to any third party by us:

Storage keys used: calm_agenda_v1_reminders, calm_agenda_v1_todolists, calm_agenda_v1_settings, calm_agenda_v1_schemaVersion, calmagenda_expanded_groups.

This information lives only on your device and is removed when you uninstall the app. It is not backed up to any server we control. If you have iCloud Backup enabled in iOS, Apple may include the app's local data in your encrypted iCloud Backup; that backup is governed by Apple's Privacy Policy.

3. Information your device sends to Apple

CalmAgenda relies on standard iOS frameworks. Apple receives information from your device in the normal course of providing those services. We do not receive copies of this data.

• Local notifications (@capacitor/local-notifications): scheduled and delivered by iOS itself. The notification content (title and reminder text you wrote) is rendered locally.
• App Tracking Transparency (ATT): iOS shows the system ATT prompt the first time we initialize ads. The string shown in the prompt is: "This identifier is used to show ads that are more relevant to you." Your decision is stored by iOS.
• In-App Purchase (StoreKit): when you tap to remove ads (if/when the purchase flow is enabled), Apple handles payment, identity, receipt validation, and refunds under Apple's Privacy Policy. We receive only a flag from the receipt indicating whether the entitlement is active. We do not receive your name, address, payment method, or Apple ID.
• SKAdNetwork: Apple's privacy-preserving ad attribution framework. When you interact with an ad, Apple may send a cryptographically signed, anonymized install/postback to the ad network. This is performed by iOS, not by us, and does not include a user identifier.

4. Information processed by Google AdMob and its ad partners (third-party tracking)

CalmAgenda displays banner ads on iOS through Google AdMob (the Google Mobile Ads SDK, integrated via @capacitor-community/admob). Google AdMob, Google LLC, and the third-party ad networks listed below are independent controllers of the data they collect to serve ads. They process that data under their own privacy policies. We have no access to it.

4.1 What is collected

When the ad SDK is initialized and a banner request is made, Google AdMob and its bidding partners typically receive:

• Device and OS information: device model, OS version, language, country/region, time zone, screen size, app foreground state, app version, app bundle identifier (com.calmagenda.app).
• IP address (used to derive coarse/IP-based location, fraud signals, and to deliver the ad).
• Ad event data: ad request, impression, click, time of event.
• Apple's Identifier for Advertisers (IDFA) — only if you grant tracking permission through the iOS ATT prompt. If you decline ATT, IDFA is not shared with Google or third-party ad networks.
• Apple's Vendor identifier (IDFV) and other resettable, non-cross-app identifiers used by Google for fraud prevention and frequency capping.
• SKAdNetwork postbacks for attribution (no user identifier, signed by Apple).

We do not share with Google or ad networks:

• the content of your reminders or to-do lists,
• your contacts, calendar, location (we never request location permissions), microphone, camera, or photos,
• any account identifier you might use elsewhere — the app has no account system.

Cookies and similar technologies. On a mobile app, the "cookies and similar technologies" that Google and its ad partners would normally use in a browser take the form of advertising identifiers (IDFA), vendor identifiers (IDFV), SKAdNetwork postbacks, and SDK-level local storage. They serve the same function — identifying a device or session for ad delivery, measurement, and fraud prevention — but no browser cookies are set by CalmAgenda.

4.2 Why this data is processed

• To select and deliver ads (contextual or personalized).
• To measure ad performance (impressions, clicks, viewability).
• To prevent invalid traffic, fraud, and abuse.
• To attribute installs and conversions via SKAdNetwork.
• To honor frequency capping and policy compliance (e.g., not showing the same ad too often).

4.3 Personalized vs. non-personalized ads

• Outside the EEA, UK, and Switzerland, Google may serve personalized ads subject to your ATT choice and to AdMob's defaults.
• Inside the EEA, UK, and Switzerland, Google requires a certified Consent Management Platform (CMP) before the Google Mobile Ads SDK can be initialized. We have not yet integrated a CMP. Until we do, CalmAgenda is not distributed in the EEA, the UK, or Switzerland. We plan to integrate Google's User Messaging Platform (UMP) as our IAB-TCF v2 CMP as soon as possible. Once integrated, the first time you open the app in those regions you will see a Google-provided consent form asking whether ad partners may use your data for personalized ads, measurement, etc.; your choice will be stored by Google in an IAB-TCF consent string, and if you decline, AdMob will serve non-personalized (contextual) ads instead.
• Once UMP is integrated, you will be able to change your UMP choices at any time via Settings → Privacy → Privacy choices in the app. (That row will be hidden in regions where Google reports that a privacy options entry point is not required.)

4.4 Ad-network partners (SKAdNetwork participants)

To make Apple's SKAdNetwork attribution work, our app declares the SKAdNetwork identifiers of ad networks that may bid through Google AdMob's mediation/exchange. The full list is published in the iOS Info.plist and reflects Google's recommended list. These networks include, among others:

Google, Meta Audience Network, AppLovin, Unity Ads, ironSource, Vungle (Liftoff), Mintegral, Tapjoy, Chartboost, Fyber/Digital Turbine, AdColony, InMobi, Pangle, and others. The authoritative, current list is the SKAdNetworkItems array in ios/App/App/Info.plist.

Each of these networks may receive an SKAdNetwork postback from Apple (no IDFA, no user identifier) when one of their ads results in an attributed install or in-app event. They may also receive bid request information from Google during ad selection. Each network has its own privacy policy.

4.5 Google's privacy resources

• How Google uses information from sites or apps that use our services
• Google Privacy Policy
• Google's ads & advertising privacy controls
• About Google AdMob & privacy / Apple ATT
• IAB Europe TCF list of vendors

5. We do not knowingly collect data from children

CalmAgenda is a general-audience productivity app and is not directed to children under 13 (or the equivalent age in your jurisdiction — 16 in much of the EEA). We do not knowingly collect personal information from children. We have not enabled AdMob's child-directed treatment, because the app is not intended for children. If you believe a child has used the app and you are concerned about what may have been processed by Google AdMob, please use the contact link in Section 11.

6. Your choices and controls

6.1 On the device

• Limit IDFA / opt out of cross-app tracking: iOS → Settings → Privacy & Security → Tracking → toggle CalmAgenda off (or system-wide "Allow Apps to Request to Track").
• Reset the advertising identifier: iOS → Settings → Privacy & Security → Tracking → "Reset" (or by toggling Tracking off).
• Personalized Ads (Apple): iOS → Settings → Privacy & Security → Apple Advertising.
• Google's personalized-ads controls: adjust Google's own ad personalization at Google Ads Settings (applies to any Google account you're signed into).
• Third-party ad-network opt-out: you can opt out of many third-party ad-network identifiers used for personalized advertising at aboutads.info/choices.
• Erase all locally-stored CalmAgenda data: uninstall the app. iOS removes the app's NSUserDefaults, any cached files, and any pending local notifications.

6.2 In the app

• Privacy choices (EEA/UK/Switzerland) — planned: once UMP is integrated, Settings → Privacy → "Privacy choices" will re-open the Google UMP consent form so you can change your IAB-TCF choices at any time. (This entry point will only be shown when Google reports that it is required for your region.) This control is not yet present in the current build.
• Remove ads: when the in-app purchase to remove ads is enabled, completing that purchase disables AdMob entirely. When adsRemoved is true, the Google Mobile Ads SDK is no longer asked to load or display ads.

7. Rights under GDPR / UK GDPR (EEA, UK, Switzerland)

CalmAgenda is not currently distributed in the EEA, the UK, or Switzerland because we have not yet integrated a Google-certified Consent Management Platform (see the interim status note in Section 1 and Section 4.3). We plan to integrate Google's User Messaging Platform (UMP) as soon as possible, at which point this section will apply to those users. If you are in the EEA, the United Kingdom, or Switzerland, the legal basis on which we process data is limited because we do not collect personal data ourselves. For the third-party ad processing described in Section 4 (once it becomes available in your region):

• Legal basis: your consent, collected through the Google UMP consent form, except for the limited processing strictly necessary to serve a non-personalized ad and to detect fraud, which Google relies on its legitimate interests for. Once UMP is integrated, you will be able to withdraw consent at any time via Settings → Privacy → Privacy choices.
• Rights: you have the right to access, rectify, erase, restrict, port, and object to the processing of personal data, and to lodge a complaint with your local supervisory authority. Because we do not hold copies of your AdMob data, requests to access, port, or erase that data must be made directly to Google LLC as data controller for AdMob.
• International transfers: Google may transfer data outside the EEA/UK/Switzerland under its own safeguards (Standard Contractual Clauses, Data Privacy Framework, etc. — see Google's privacy policy).

8. Rights under U.S. state privacy laws (CCPA/CPRA and similar)

If you are a California resident or are protected by another U.S. state privacy law:

• Categories of personal information processed (last 12 months): identifiers (advertising identifier, IP address, device identifier), internet/network activity information (ad interactions), and inferences drawn from the above for ad targeting. All of this is processed by Google AdMob and its partners, not by us.
• Sources: your device.
• Purposes: advertising, ad measurement, and fraud prevention by Google AdMob and its partners.
• "Sale" / "Share" / targeted advertising: to the extent personalized advertising delivered by Google AdMob and its partners is considered a "sale" or "share" of personal information under California law (or "targeted advertising" under Virginia/Colorado/Connecticut/etc. law), you can opt out by:
  • declining the ATT prompt (or toggling it off in iOS settings), and
  • once UMP is integrated (see Section 4.3), declining personalized ads via the UMP "Privacy choices" form in Settings, in regions where Google offers it.
• No discrimination: we do not charge different prices or provide a different level of service to users who exercise these rights.

We do not have user accounts, so we cannot match a request for data access/deletion to a specific user. Please direct AdMob-related requests to Google.

9. Data retention

• On-device data is retained until you delete the data inside the app, reset the data, or uninstall the app.
• AdMob / ad-partner data is retained under each company's own retention policies (see Google's privacy policy linked in Section 4.5).
• SKAdNetwork postbacks are time-limited by Apple and not retained by us.

10. Security

CalmAgenda's user content never leaves the device through any channel we control, so the device's own security (passcode, biometrics, iOS sandbox, full-disk encryption) is what protects it. Communication between the Google Mobile Ads SDK and Google's servers, and between the StoreKit framework and Apple's servers, uses TLS. No method of electronic storage or transmission is 100% secure.

11. Changes to this policy

We may update this policy when the app's behavior changes (for example, if we add an analytics SDK, change ad networks, or enable a new in-app purchase). When we do, we will update the "Effective date" and "Last updated" fields above. Material changes will, where reasonably possible, be highlighted in the app or on the app's listing page.

12. Contact

Questions, complaints, or data-subject requests can be sent through the contact form linked from the in-app Settings → Support → Contact us, which opens:

https://kevindelgadopagan.com/#contact-me

Appendix A — Third-party SDKs and services used in CalmAgenda (technical reference)

The above reflects the dependency set declared in package.json and the configuration in capacitor.config.ts and ios/App/App/Info.plist.

Appendix B — Things CalmAgenda does not do (as of the effective date)

• Does not create an account or require sign-in.
• Does not sync to iCloud (other than standard iOS device backups, which are between you and Apple) or to any backend server.
• Does not use push notifications. No APNs / FCM token is generated.
• Does not request location, contacts, calendar, microphone, camera, photo library, or HealthKit permissions.
• Does not include first-party analytics, crash reporting, or telemetry (no Firebase, Crashlytics, Sentry, Mixpanel, Amplitude, Adjust, Branch, AppsFlyer, etc.).
• Does not read or write files outside its own sandbox.
• Does not include a web tracker, fingerprinting library, or session-replay tool.