Privacy Policy
Paylendar
Privacy PolicyTerms of UseSupport Language

Paylendar

Privacy Policy

Document version: 2026-10-20

ContentsProvider and contact Planner data Premium and iCloud Synchronization limits and security Turning synchronization off Storage and retention Deleting data Apple and RevenueCat Notifications, images and widgets Website storage Support information Purposes and legal bases Recipients and international processing Your privacy rights Age and other people's data Updates to these documents and the service

Provider and contact

Paylendar is provided by Jan Kazubski. Contact for support, complaints and privacy requests: paylendar@gmail.com. Seller information is also available in the App Store. Jan Kazubski is the controller of personal data processed for Paylendar's purposes described below. Apple separately handles its accounts, store and services under its own terms.

Jan Kazubski
ul. Jana Kazimierza 76
64-100 Leszno
Poland

Planner data

The app stores plan names, amounts, currency labels, dates, schedules, status and history, notes, links, tags, organizational accounts, selected images and settings on your device. The app does not send planner content to the developer's own server or to RevenueCat. Changing the currency changes labels, not numerical amounts: Paylendar does not perform currency conversion.

Premium and iCloud

With active Premium, synchronization starts automatically if no synchronization choice was previously saved on that device. This can upload existing plans as well as new entries. A saved choice to disable it is respected. Check or change the setting in Paylendar. Data is exchanged with the private CloudKit database associated with your iCloud account, including planner content, images, shared currency, display scope and reminder time. Use the same iCloud account on devices you want to synchronize.

Opening the data-management section on the iCloud screen may contact Apple to check the account and whether Paylendar cloud data exists, even without Premium or with sync disabled. This check uses a pseudonymous account identifier, does not fetch planner contents and does not turn synchronization on.

Synchronization limits and security

Synchronization uses record, installation and pseudonymous iCloud identifiers, versions, change times and deletion markers. Offline changes may arrive later; concurrent edits are reconciled automatically and one edit may replace another. Deletions can propagate. Availability depends on devices, network, storage and Apple. Sync is not a guaranteed backup or version archive. Apple protects iCloud under its security arrangements; we do not promise end-to-end encryption of every Paylendar field. Protect your devices and Apple Account.

Update Paylendar on every device: older versions that do not support the cleaned deletion markers can stop synchronizing when they encounter the newer data format. Updating one device does not erase local copies on another.

Turning synchronization off

Disabling sync stops exchange on that device; it does not delete local or cloud data. Other enabled devices can continue syncing. Premium expiry stops sync without automatically erasing data. Renewing, restoring Premium or enabling sync can restart exchange. The setting is per device. Cancelling a subscription, disabling sync and deleting data are separate actions.

Premium access follows the entitlement confirmed by the store, including any active grace period. The stated expiry date triggers a refresh; a temporary network error does not by itself cancel previously confirmed access.

Storage and retention

Planner data is stored on your device and, when synchronized, in iCloud. In the updated app, deletion markers no longer retain names, amounts, notes, URLs or images. Minimal identifiers and operation versions remain to reconcile deletions; some payment records also retain a plan identifier and a technical schedule date. These markers have no automatic expiry.

App-managed synchronization and migration backups can contain earlier content. After successful database startup, the app attempts to remove backups older than 30 days and keep at most three of each type; creating a new sync backup also triggers cleanup of that type. A closed app, failed startup or cleanup error can delay removal. This policy does not cover user exports, system backups or copies retained by Apple.

Technical copies do not guarantee recovery. Purchase records follow Apple and RevenueCat retention rules and applicable obligations. Support correspondence is kept as needed to resolve the request and for applicable legal obligations or claim periods, then deleted or anonymized.

Deleting data

Ending or archiving a plan does not erase it. In the updated app, deleting an item removes it from the visible planner and clears names, amounts, notes, URLs and images from its synchronization markers; minimal technical markers remain. Changes reach iCloud through successful synchronization, so earlier cloud content may remain until then. Deleting all Paylendar cloud data also removes those markers from its iCloud zone; local data and copies on other devices remain. Turning sync off, losing Premium or uninstalling does not erase iCloud.

On startup, the updated app also clears content from older local deletion markers, without requiring Premium or a network connection. Cleaning their iCloud copies requires subsequent successful synchronization. Update and launch the app on other devices too; earlier exports and backups can still contain previous content.

In the updated app, the data controls on the iCloud screen let you export local plans, history, images and settings to JSON and request deletion of Paylendar's cloud data, without Premium. Export does not fetch missing cloud data and is not an import/restore feature. The app does not encrypt the export file; protect it and manage any copies or storage services you choose. The export also includes received records awaiting related data and minimal deletion markers, without the deleted names, amounts, notes, URLs or images. It does not include historical backup files, individual widget configurations or CloudKit account identifiers and transport metadata.

Before cloud deletion, disable sync on other devices. Confirm deletion in the app; local plans and technical backups remain. Sync on this installation stays blocked while deletion is pending or failed; retry rather than assuming completion. Restarting upload after confirmed deletion requires a separate confirmation, Premium and the same iCloud account. Other or older devices can retain data or re-upload it. Apple's storage controls are another option where available: Apple / iCloud. Delete local data and export copies separately; Mac uninstall can leave containers, and iOS offloading retains data. For assistance, including residual copies, contact paylendar@gmail.com. The developer cannot directly browse or remotely clear your private iCloud; the app performs your confirmed request through Apple.

Apple and RevenueCat

Apple processes payments; we do not receive your full card details. RevenueCat validates and manages Premium using a pseudonymous app-user identifier, purchase and entitlement information and technical request data. It can be contacted when the app starts, including before a purchase by a free user. Its identifier is not a guarantee of anonymity. Planner amounts, notes and images are not sent to RevenueCat. The developer can access purchase and entitlement information through its service.

Notifications, images and widgets

From version 1.3.1, saving the first plan with reminders enabled can enable reminders on that device and request system permission if needed. You can change this in Paylendar and in system notification settings.

For active plans with reminders enabled, the app schedules daily reminders for the earliest unsettled occurrence, including overdue items. Reminders use a limited queue scheduled ahead; reopening the app refreshes it. Marking an item settled in Paylendar or disabling its reminder changes future scheduling. A payment made outside the app does not update its status automatically.

Reminders are scheduled locally and can show names, amounts and account labels on the lock screen. Their delivery depends on permissions, system settings and device state; every reminder is not guaranteed. Silent Apple notifications also support CloudKit sync. Widgets use a local shared copy of data and selected images and may show older information. Selected images are copied into app storage and may be synchronized; do not assume image metadata is removed. Appearance and notification permissions are device specific.

When preparing widget data, the app checks Premium access and attempts to remove the local widget cache and its images if access is unavailable. File errors can delay cleanup; the system controls when the displayed widget refreshes.

Apple Watch exchanges payment names, amounts, dates, statuses, optional account names and technical identifiers with your paired iPhone through WatchConnectivity, independently of Premium and iCloud sync. The watch keeps a local copy shared with complications, plus queued actions and their results. Updates and deletions appear after successful data exchange; complications can show older data.

Website storage

The website is hosted by GitHub Pages, which processes connection data such as IP addresses for operation and security. Your browser stores your selected language and theme in localStorage until you clear site data or change them. The site does not add advertising trackers or analytics cookies. There is no Paylendar contact form: email links open your email app. External links are subject to their providers' policies.

Support information

When you email us, we process your address, message and any details you choose to send. A prepared support message can include app and system versions, device information, language and diagnostic identifiers. Sending is your choice. Remove unnecessary financial or third-party information from screenshots and attachments. Support email is handled through Gmail/Google.

Purposes and legal bases

Where the GDPR applies, necessary service, Premium and requested support processing relies on performance of the contract (Article 6(1)(b)); legal recordkeeping relies on legal obligations (6(1)(c)); general correspondence, security and handling claims rely on legitimate interests (6(1)(f)), balanced against your rights. Consent (6(1)(a)) applies where legally required for an optional operation and may be withdrawn without affecting earlier lawful processing. A device permission or this policy alone is not consent to every processing activity. We do not sell planner data, use it for advertising or make decisions with legal effects through automated profiling.

Recipients and international processing

Relevant providers are Apple (App Store/iCloud), RevenueCat (Premium), GitHub (website) and Google (support email). Data is shared only for the functions described, with authorized advisers or authorities where legally required. Providers may process data outside your country, including the USA. Where GDPR transfer rules apply, transfers require a valid mechanism such as an applicable adequacy decision or standard contractual clauses and any necessary safeguards. Contact us for information about the mechanism relevant to your data. See Apple, RevenueCat, GitHub and Google.

Your privacy rights

Depending on applicable law, you can request access, correction, erasure, restriction and portability, object to processing based on legitimate interests and withdraw consent. Email paylendar@gmail.com; proportionate identity verification may be needed. GDPR requests normally receive a response within one month; any permitted extension is explained. You may complain to Poland's UODO or your competent local authority. Requests do not require Premium. We will explain limits where we cannot access data held only on your devices or private iCloud, and assist with the available controls. Providers also handle rights for their independent processing.

Age and other people's data

Paylendar is a general-purpose tool, not a service directed at children. Use must comply with local age and legal-capacity rules and Apple's account requirements; obtain parental authorization where required. Only enter personal data and images you may lawfully use. Contact us if a child has provided personal data without the authorization required by law.

Updates to these documents and the service

Version: 20 October 2026. These documents cover iPhone, iPad, native macOS, Apple Watch, Premium and iCloud. We may update information when the app, providers or law change. Material changes are communicated as required; posting a page alone does not obtain consent or amend an existing purchase retroactively. Changes to a paid digital service, notice, access and termination rights remain governed by the contract and mandatory law. Earlier versions may be requested by email.

Update for Paylendar 1.3.1: clarified reminder activation, daily repetition and scheduling limits.

Home© 2026 Jan Kazubski
Privacy PolicyTerms of UseSupportpaylendar@gmail.com