Paylendar is developed by Jan Kazubski. This policy explains what information is used when you use the Paylendar app and website and how that information is stored and processed.
For privacy questions, contact:
1. Data stored in Paylendar
Paylendar lets you store information used to plan payments and income, including:
- payment and income names;
- amounts and currencies;
- dates and schedules;
- completion status for individual occurrences;
- accounts and tags used to organize information;
- notes;
- optional links;
- reminder settings;
- optional images;
- app settings.
In the current version, this information is stored locally on your device.
Paylendar does not operate its own server to which the contents of your plans are uploaded, and it does not require you to create a Paylendar account.
The app does not:
- connect to your bank accounts;
- download bank transaction history;
- make payments or transfers;
- require online banking credentials;
- require payment card numbers.
You should not store passwords, authentication codes, online banking credentials or full payment card numbers in Paylendar notes.
2. No iCloud synchronization in the current version
The current version of Paylendar does not synchronize app data between devices using iCloud or CloudKit.
Information stored in Paylendar on one device is not currently transferred by Paylendar to your other devices.
Separately, depending on your device settings, Apple may include application data in a system device backup. This is an Apple service and is not Paylendar's cross-device synchronization feature.
3. Notifications
If you enable notifications, Paylendar uses local system notifications to remind you about planned payments or income.
A notification may contain information stored in the app, such as:
- a plan name;
- an amount;
- a date;
- an account name.
Notifications are scheduled locally on your device. Paylendar does not use its own server to send these reminders.
Whether notification content is visible on your lock screen depends on your system settings.
4. Widgets
Paylendar widgets use information stored locally on the same device.
The app prepares a local copy of information required to display a widget. This information:
- is not a separate cloud database;
- is not used to synchronize information between devices;
- is not sent by the widget to the Paylendar developer.
5. Images
If you select an image for a plan, Paylendar uses the system photo or file selection mechanisms.
The selected image is used by the app and stored locally.
Paylendar does not send the contents of these images to the developer or to RevenueCat.
6. Premium, the App Store and RevenueCat
Paylendar offers optional Premium features.
Purchases are processed through Apple's App Store purchase system. The Paylendar developer does not receive your payment card number, bank account details or other payment credentials used through the App Store.
Paylendar uses RevenueCat to:
- determine Premium status;
- validate purchases;
- manage subscriptions;
- manage one-time purchases;
- restore purchases;
- determine whether Premium features should be available.
For this purpose, RevenueCat may process purchase or subscription information and a technical customer identifier required to determine Premium status.
Paylendar does not send RevenueCat the contents of information stored in the app, such as:
- plan names;
- amounts entered in plans;
- notes;
- tags;
- account names;
- saved links;
- selected images.
Paylendar does not use RevenueCat to track you across apps or websites for advertising purposes.
RevenueCat may provide the Paylendar developer with statistics related to purchases and Premium.
RevenueCat may process information related to Premium services in the United States. Where transfers are subject to European data protection law, RevenueCat uses appropriate legal safeguards, including the European Commission's Standard Contractual Clauses. More information is available in RevenueCat's privacy documentation.
7. Analytics, advertising and tracking
The current version of Paylendar:
- does not display advertising;
- does not use advertising trackers;
- does not use your information for advertising profiling;
- does not track your activity across apps or websites for advertising purposes;
- does not use a third-party behavioral analytics service such as Firebase Analytics, Mixpanel, Amplitude or a similar service.
RevenueCat processes purchase-related information and may provide statistics related to purchases and Premium. This is not advertising tracking.
Apple may separately process App Store, purchase, device or diagnostic information according to your Apple settings and Apple's privacy practices.
8. Contacting support
Contacting support is voluntary.
If you send a message to paylendar@gmail.com, the Paylendar developer receives the information you choose to provide, such as:
- your email address;
- the contents of your message;
- attachments;
- technical information about the app or device that you voluntarily provide.
This information is used to respond to your message and resolve the reported problem.
Paylendar does not automatically send the developer the contents of your plans, amounts, notes or images.
The technical report available for certain local database problems is designed to contain technical schema information rather than the private contents of your plans. The message is sent only after an action by you.
Do not send support messages containing:
- passwords;
- authentication codes;
- online banking credentials;
- full payment card numbers;
- private financial documents unless they are necessary to resolve the issue.
9. Paylendar website
The Paylendar website is hosted using GitHub Pages.
The Paylendar website itself:
- does not use its own user analytics;
- does not use advertising trackers;
- does not use a backend contact form;
- may store simple interface preferences locally in your browser, such as your selected theme.
GitHub states that when a GitHub Pages website is visited, the visitor's IP address is logged for security purposes. GitHub may also process other technical information according to its own privacy practices.
GitHub Privacy Statement:
https://docs.github.com/en/site-policy/privacy-policies/github-general-privacy-statement
GitHub Pages information:
https://docs.github.com/en/pages/getting-started-with-github-pages/what-is-github-pages
Visiting the Paylendar website does not send the contents of plans stored in the Paylendar app to the developer.
10. Why some information is processed
Purchase-related information is processed because it is required to complete purchases, determine Premium status and provide purchased features.
Information voluntarily submitted to support is used to respond to requests and resolve reported issues.
Where required or permitted by law, certain information may also be processed to comply with legal obligations, prevent abuse, or establish, exercise or defend legal claims.
11. Who may process information
The Paylendar developer does not sell users' personal data.
Information may be processed by external providers only to the extent required for a particular feature, including:
- Apple - App Store, purchases and device system services;
- RevenueCat - Premium and purchase management;
- GitHub - website hosting;
- email providers - when you contact support by email.
Some providers may process information outside your country according to their privacy practices and applicable legal safeguards.
Information may also be disclosed to competent public authorities where required by law.
12. Retention and deletion
Information stored in the app
Information entered into Paylendar remains locally on your device until you:
- delete a particular item;
- remove data using available app functionality;
- delete the app and its local data.
The Paylendar developer does not have remote access to the app's local database and cannot remotely delete this information for you.
If information has been included in an Apple system backup, that backup is managed through Apple's services and settings.
Purchase-related information
Purchase-related information may be retained by Apple and RevenueCat for as long as required to:
- maintain the correct purchase or subscription status;
- restore purchases;
- maintain security and prevent abuse;
- comply with legal obligations.
The detailed retention practices of Apple and RevenueCat are governed by their respective policies.
Support messages
Support correspondence is retained until the request has been resolved and afterwards only for as long as reasonably required to document the resolution, prevent abuse or comply with legal obligations.
For requests concerning information under the Paylendar developer's control, contact:
13. Your privacy rights
Depending on applicable law, you may have rights to access, correct or delete your personal data, restrict certain processing, object to certain processing or request data portability where applicable.
For information under the Paylendar developer's control, contact:
You may also have the right to lodge a complaint with the competent data protection authority.
14. Security
Paylendar limits the amount of information transmitted off-device. Core information entered by the user is stored locally in the application's storage protected by the operating system.
No information system can guarantee absolute security.
You should protect your device using an appropriate device passcode, Face ID or Touch ID and keep your operating system up to date.
15. Children
Paylendar is a general payment-planning utility and is not designed specifically for children.
The app does not operate its own user account system. Premium purchases are processed by Apple and are subject to Apple account settings and available parental controls.
16. Changes to this Privacy Policy
This policy may be updated if the way Paylendar works, the information it processes or the external services it uses change.
The policy will be updated before a Paylendar feature that synchronizes app data between devices is made available, if such a feature is introduced.
The current version and last-updated date will be available on the Paylendar website.
17. Contact
For privacy questions: