Tripelfy Evently

Legal and Privacy Notice

Effective date / last updated: August 1, 2026 Application name: Tripelfy Evently Operator: Balázs Kovács Country: Hungary Contact: hello@tripelfy.com Website: tripelfy.com

This document contains the privacy notice, terms of use, subscription terms, information regarding affiliate links, rules applicable to third-party services, data deletion and data export information, and other legal terms relating to the use of the Tripelfy Evently application.

The application is developed and operated from Hungary, but it is intended for a global market, including, among others, the European Union, the United Kingdom, the United States of America, Australia, Japan, China, and other countries.

The application is currently developed and operated by a natural person. If the commercial operation of the application makes it necessary, the operation may later continue in the form of a business or company.

Tripelfy Evently does not use its own user accounts and does not use external server-based registration. The application primarily operates on the user’s own device. Data may be stored on the user’s device, in App Group shared storage, or, if optional iCloud synchronization is used, in the user’s personal iCloud storage linked to the user’s Apple ID.

The full private residential address is not displayed directly in the application. If a law, App Store requirement, authority request, or official procedure requires additional identifying information, it will be provided separately through an appropriate official channel.

1. Purpose of the application

Tripelfy Evently is a personal event management, reminder, and daily organization application.

The purpose of the application is to help the user manage important dates, events, name days, birthdays, anniversaries, work schedules, subscriptions, and related reminders.

The application may include, among others, the following functions:

• displaying name days by multiple countries and languages;
• managing birthdays;
• managing anniversaries;
• creating custom events;
• managing work schedules and work-related time planning;
• local notifications;
• contact import;
• management of contact data and contact images;
• iCloud synchronization;
• profile and profile picture;
• widgets;
• Apple Watch companion features, if available;
• calendar export in .ics format;
• subscription tracker;
• world clock and time zone features;
• gift, restaurant, flower, and activity recommendations;
• optional location-based recommendations;
• affiliate links;
• premium or subscription-based features.

The application is a convenience and organization tool. It does not constitute legal, financial, tax, accounting, medical, safety, emergency, or other professional advice.

2. Data controller

The data controller and operator of the application is:

Name: Balázs Kovács Country: Hungary Contact email: hello@tripelfy.com Website: tripelfy.com

The primary contact method for privacy, legal, technical, or user-related questions is email.

Recommended email subject for privacy requests:

Privacy Request – Tripelfy Evently

3. Categories of data processed

Depending on the user’s choices, permissions, and functions used, the application may process the following data:

• event name;
• event date;
• event type;
• event category;
• repeat settings;
• reminder time;
• notes;
• emoji or visual marker;
• name day data;
• birthdays;
• anniversaries;
• dates linked to persons;
• custom events;
• images linked to custom events;
• work schedule;
• shifts;
• start and end time of work;
• rest days;
• workplace name or workplace-related designation;
• work-related notes;
• weekly or periodic working time statistics;
• profile name;
• optional profile picture;
• application settings;
• language settings;
• country settings;
• notification settings;
• display data required for widgets;
• data required for Apple Watch display, if such function is available;
• name of a subscription entered in the subscription tracker;
• subscription amount;
• subscription currency;
• subscription renewal or expiry date;
• subscription category;
• in case of contact import: name, nickname, display name, birthday, anniversary or other date stored in the contact, phone number, email address, postal address or address data, workplace or organization, job title, relationship or family-type label, contact image, and other data linked to the relevant person in the iOS Contacts system that is necessary for the functions of the application;
• images belonging to contacts, if the user allows access to contacts;
• images selected from the Photo Library;
• optional location data, if the user grants permission;
• synchronized data created from application data when iCloud synchronization is used;
• entitlement status related to in-app purchases or subscriptions;
• technical entitlement information related to StoreKit transactions;
• basic system information required for technical operation, if provided by iOS or Apple services.

The application does not intentionally request and does not deliberately process special categories of personal data, such as health data, political opinions, religious beliefs, biometric identifiers, or similar sensitive data.

If the user voluntarily enters such data into notes, event names, work-related notes, fields imported from contacts, or other free-text fields, the user is responsible for this.

4. Purpose of data processing

The purposes of data processing are:

• providing the basic functions of the application;
• creating and displaying events;
• managing name days, birthdays, and anniversaries;
• managing custom events;
• managing work schedules;
• displaying work-related time planning;
• providing work-related reminders;
• operating reminders;
• sending notifications;
• importing contact data;
• displaying or managing basic information related to contacts;
• displaying contact images;
• managing profile pictures and event images;
• using images selected from the Photo Library;
• providing iCloud synchronization;
• operating widgets;
• providing Apple Watch display, if such function is available;
• providing calendar export;
• operating the subscription tracker;
• verifying premium entitlements;
• displaying location-based recommendations;
• managing external offers and affiliate links;
• preserving application settings;
• improving user experience;
• fulfilling legal obligations;
• handling user requests.

5. Legal basis for data processing

The legal basis for data processing may vary depending on the user’s place of residence and applicable laws.

In the European Union and the United Kingdom, the legal basis for processing may include in particular:

• the user’s consent;
• performance of a service requested by the user;
• legitimate interest;
• compliance with a legal obligation.

In the United States of America, certain state privacy laws may be relevant. In Australia, the Australian Privacy Principles may apply. In Japan, the Act on the Protection of Personal Information may be relevant. In China, the Personal Information Protection Law may apply, to the extent applicable to the relevant user or data processing situation.

This document has been prepared as a global notice. If the law of the user’s place of residence provides broader rights, the relevant mandatory legal provisions apply.

6. Use of contacts

The application accesses contacts stored on the device only if the user expressly allows this through iOS.

The purpose of using contacts may include:

• importing birthdays;
• displaying persons linked to name days;
• recording anniversaries or other dates;
• creating reminders linked to persons;
• making it easier to manage events related to important contacts;
• displaying contact images for visual identification within the application;
• displaying or managing basic contact details if the relevant function requires this;
• operating person-related events, reminders, and name-day-linked displays.

With the user’s permission, the application may read the following data from contacts:

• name;
• nickname or contact name;
• display name;
• birthday;
• anniversary or other date stored in the contact;
• phone number;
• email address;
• postal address or address data;
• name of workplace or organization;
• job title or related designation;
• relationship or family-type label, if such data is included in the contact;
• contact image;
• other fields linked to the relevant person in the iOS Contacts system and necessary for the functions of the application.

The application uses these data only to operate the functions used by the user, for example for birthdays, name days, anniversaries, person-related events, reminders, visual identification, or contact-based display.

The application does not sell contact data, does not use it for advertising profiling, does not transfer it to its own central server, and does not operate a central contact database.

Certain contact data may be stored locally on the user’s device, in App Group shared storage, or, if optional iCloud synchronization is used, in the user’s personal iCloud storage linked to the user’s Apple ID.

The application does not modify the user’s address book and does not write data to the contact list, unless such a function is later introduced with separate and clear user permission.

Granting contact permission is not mandatory. If the user does not grant access to contacts, functions related to contact import, contact images, birthday import, persons linked to name days, or other contact-based functions may not work or may work only in a limited way.

The user may revoke or modify access to contacts at any time in the iOS system settings.

The user is responsible for processing other persons’ data lawfully in the application.

7. Use of location data

The application may optionally request location data.

The purpose of using location data may include:

• searching for nearby restaurants;
• searching for nearby flower shops;
• refining gift or activity recommendations;
• displaying location-based external offers;
• providing a more relevant user experience.

The use of location data is not mandatory. If the user does not grant location access, certain location-based functions may not work or may work only in a limited way.

The application does not use location data for continuous tracking, unless a future function separately and clearly states this and the user gives separate consent.

The user may change or revoke location access at any time in the iOS system settings.

8. Notifications

The application may send local notifications if the user allows this.

Notifications may relate, for example, to:

• name days;
• birthdays;
• anniversaries;
• custom events;
• contact-related events;
• work schedule;
• shift start or work-related reminders;
• subscription renewal;
• daily or periodic reminders;
• upcoming important dates.

Delivery of notifications depends on iOS, device settings, notification permissions, Focus modes, battery-saving settings, and other system conditions.

The operator does not guarantee that every notification will appear exactly on time or in every case.

9. iCloud synchronization

The application may offer iCloud synchronization.

If the user uses this, certain application data may be stored in the user’s personal iCloud storage linked to the user’s Apple ID and synchronized between the user’s own Apple devices.

The operation, availability, security, and data processing of iCloud are also governed by Apple’s own terms and privacy rules.

The operator does not have direct access to application data stored in the user’s own iCloud account.

The operator does not guarantee:

• immediate synchronization;
• full consistency between devices;
• uninterrupted operation of Apple services;
• details of Apple’s processing of data stored in iCloud.

For important data, the user is advised to create a separate backup.

10. Widgets and Apple Watch display

The application may provide widgets that display upcoming events, name days, birthdays, anniversaries, contact-related events, work schedule data, or other information.

The application may also provide Apple Watch companion features, if these are available.

Data displayed in widgets or on the Apple Watch interface may come from application data stored on the device, App Group shared storage, or data synchronized through iCloud.

The user is responsible for which widget or Apple Watch display they enable, because these may make certain events, personal information, contact-related data, or work schedule data visible to others on the device screen.

11. Calendar export

The application may allow events to be exported in .ics format.

The exported file may contain:

• event name;
• event date;
• recurrence;
• category;
• notes;
• reminder information.

The user saves, shares, or imports the exported file into another calendar application based on their own decision.

The exported file may contain personal data. The user is responsible for deciding to whom they send the exported file, where they upload it, and into which service they import it.

12. Subscription tracker

The application may include a subscription tracker function.

In this function, the user may record, for example:

• subscription name;
• subscription amount;
• currency;
• renewal date;
• expiry date;
• category;
• reminder.

The subscription tracker is a convenience function. It does not constitute financial, investment, tax, accounting, or legal advice.

The amounts, currencies, and dates displayed in the application are based on data entered by the user. The user is responsible for their accuracy.

Data recorded in the subscription tracker may be considered personal information of a financial nature, even if the application does not process bank card data and does not carry out financial transactions.

13. Premium features and subscription

Certain functions may be subject to a premium subscription or in-app purchase.

Premium functions may include, for example:

• extended event management;
• additional reminders;
• premium widgets;
• subscription tracker;
• extended export functions;
• special appearance settings;
• management of name day data for more countries or languages;
• more advanced recommendation functions.

In-app purchases and subscriptions take place through the Apple App Store system.

Auto-renewable subscriptions may renew automatically at the end of the subscription period until the user cancels them.

Subscription management and cancellation take place in Apple’s system:

iOS Settings → Apple ID → Subscriptions

Where possible, the application provides:

• subscription management;
• purchase restoration;
• premium status verification.

Refund requests are handled by Apple according to the App Store rules.

The operator does not directly process App Store payments and does not have access to the user’s full bank card data.

14. Affiliate links and external offers

Certain functions of the application may display external offers.

These may include, for example:

• gift ideas;
• flower delivery;
• restaurant recommendations;
• activity recommendations;
• travel or booking offers;
• webshop offers;
• coupons;
• promotions.

Some links may be affiliate links. This means that if the user purchases, books, or uses a service through the relevant link, the application operator may receive a commission.

This generally does not result in any additional cost to the user.

External service providers operate according to their own terms. The external provider is responsible for:

• the product;
• the service;
• the price;
• stock or availability;
• opening hours;
• booking;
• delivery;
• complaint handling;
• its own data processing.

Tripelfy Evently is not responsible for the performance, accuracy, prices, availability, or quality of external providers or their offers.

Clicking on and using external offers is the user’s own decision.

15. External service providers

During the operation of Tripelfy Evently, the following external services may be connected to the application:

• Apple App Store;
• Apple StoreKit;
• Apple iCloud;
• Apple system permissions;
• Apple notification services;
• Apple App Group mechanisms;
• widget and Apple Watch system components;
• affiliate networks;
• offer partners;
• map or location-based service providers;
• flower delivery partners;
• restaurant or activity recommendation services;
• booking or webshop partners.

Third-party service providers have their own privacy notices, terms of use, and customer support systems.

The user uses third-party services based on their own decision.

16. Data storage

Application data is primarily stored on the user’s device.

Certain data may be stored:

• locally in the application storage;
• in the application container provided by iOS;
• in App Group shared storage when using widgets or an Apple Watch companion feature;
• in iCloud, if the user uses synchronization;
• in an exported file, if the user exports their data;
• in Apple’s systems, if an App Store purchase, subscription, or iCloud service is used.

Tripelfy Evently does not use its own user account system, does not operate its own user database, and does not store users’ personal data on a central server.

The application does not sell the user’s personal data.

17. Data transfer

Data transfer or external data processing may occur if:

• the user clicks on an external offer;
• the user opens an external website;
• the user uses an Apple service;
• the user uses iCloud synchronization;
• the user starts an App Store purchase or subscription;
• the user exports and shares a calendar file;
• the user visits an affiliate partner’s website;
• the user uses a location-based service.

Tripelfy Evently does not sell users’ personal data to third parties.

The operator does not transfer user data from its own central server to third parties, because in the current operation of the application such data is not stored on the operator’s own server.

18. International use and data transfers

The application is intended for a global market. Users may use the application from different countries, including the European Union, the United Kingdom, the United States of America, Australia, Japan, China, and other countries.

The main operation of the application may be based on the local device and Apple services.

If the user uses Apple iCloud, the App Store, an external offer, an affiliate link, or another third-party service, data may be transferred to other countries or to systems operated by other providers.

International data transfers are governed by the privacy rules of the relevant provider and applicable laws.

19. Retention period

Data is retained until:

• the user deletes the relevant data;
• the user deletes the application;
• the user disables or deletes data stored in iCloud;
• the purpose of data processing continues to exist;
• a legal obligation requires longer retention;
• in the case of App Store purchase or subscription data, Apple retains it according to its own rules.

Because the application may store many types of data locally or in the user’s own iCloud account, the operator may not necessarily have direct access to all data.

20. User rights

Depending on the user’s place of residence and applicable laws, the user may have the right to:

• request information about data processing;
• request access to data processed about them;
• request rectification of their data;
• request deletion of their data;
• request restriction of data processing;
• request data portability;
• object to certain data processing;
• withdraw consent;
• lodge a complaint with the competent data protection authority;
• request that their data not be sold or shared in a way for which applicable local law provides an opt-out right.

Because Tripelfy Evently does not use its own user account and does not store users’ personal data on a central server, certain privacy rights may primarily be exercised on the user’s own device, in their iCloud account, or through Apple settings.

Privacy questions or requests may be sent to:

hello@tripelfy.com

Recommended subject:

Privacy Request – Tripelfy Evently

The request should, where possible, include:

• which right the user wishes to exercise;
• which data the request concerns;
• the email address to which the user requests a reply;
• the country in which the user lives;
• the device on which the user used the application;
• whether the user uses iCloud synchronization.

21. Exporting my data

Tripelfy Evently may allow the user to export their own events.

The application may provide .ics calendar file export.

The exported file may contain:

• event name;
• event date;
• recurrence;
• category;
• notes;
• reminder information.

Further handling of the exported file is the user’s responsibility.

If the user shares, sends, uploads, or imports the exported file into another service, that service or recipient may also become a data controller.

The exported file may contain personal data. It is recommended that the user saves or forwards it only to trusted places or recipients.

22. Deleting my data

Tripelfy Evently does not use its own user accounts and does not use external server-based registration. Therefore, the operator does not store or process users’ personal data on a central server.

Data recorded in the application may primarily be stored on the user’s own device, in App Group shared storage, or, if iCloud synchronization is used, in the user’s personal iCloud storage linked to the user’s Apple ID.

The user may independently delete data recorded in the application at any time, for example:

• custom events;
• anniversaries;
• birthdays;
• persons linked to name days;
• data imported from contacts;
• contact images;
• work schedule data;
• workplace data;
• subscription tracker entries;
• settings;
• profile data;
• profile picture;
• event images.

Deleting local data

Removing the application from the device may delete application data stored locally on that device.

Deleting iCloud data

If iCloud synchronization was active, some application data may also be stored in the user’s personal iCloud storage linked to the user’s Apple ID.

To manage or delete application data stored in iCloud, the user may use the iOS system settings, for example:

iOS Settings → Apple ID → iCloud → Manage Storage

Complete deletion of iCloud data may depend on Apple’s system, iCloud settings, and whether the user used the application on multiple Apple devices.

Limits of remote deletion

Because the operator does not have access to data stored on the user’s device or in the user’s own iCloud account, the operator cannot remotely delete such data on behalf of the user.

Contact for privacy questions:

hello@tripelfy.com

Recommended subject:

Data Deletion Request – Tripelfy Evently

In its current operation, Tripelfy Evently does not use its own Evently account and does not use external server-based registration. Therefore, there is no separate in-app account deletion function, because there is no user account managed by the operator.

If a proprietary user account, server-based registration, or centralized data storage is introduced in the future, the legal notice of the application will be updated, and an in-app account deletion option will also be provided where necessary.

23. Processing children’s data

The application is not specifically intended for children.

The application provides general event management, reminder, and organization functions. If a child’s personal data has been entered into the application unlawfully or by mistake, a deletion request may be sent to the following email address:

hello@tripelfy.com

In some countries, different age limits, parental consent rules, or child protection requirements may apply to the use of digital services. The user is responsible for using the application according to the rules applicable in their own country.

24. Security

The operator strives to ensure that data processed in the application is stored securely.

The application may store many types of data locally on the device, in App Group shared storage, or in the user’s own iCloud account.

The user is responsible for:

• protecting their own device;
• protecting their Apple ID account;
• checking their iCloud settings;
• using a passcode, Face ID, or Touch ID;
• handling exported files securely;
• checking shared data.

No digital system can be guaranteed to be completely error-free or risk-free.

25. User responsibility

The user is responsible for:

• the accuracy of the data they enter;
• lawful use of contact data;
• lawful processing of other persons’ data;
• lawful recording of work schedule and workplace data;
• handling exported files;
• checking notifications;
• their decision before using external offers;
• the security of their Apple ID, iCloud, and device;
• using the application in accordance with the laws applicable in their own country.

The user may not use the application for unlawful, misleading, harassing, harmful purposes, or in a way that infringes the rights of others.

26. Name day data and content accuracy

The application may display name day data for multiple countries and languages.

The operator strives for accuracy, but does not guarantee that all name day data is complete, error-free, official, accurate according to every local tradition, or uniformly accepted in every country.

Name day data, recommendations, reminders, and other content are provided for informational purposes.

For important events, deadlines, or personal decisions, the user is responsible for independently verifying the data.

27. Limitation of liability

The application is provided “as is” and “as available”.

To the extent permitted by law, the operator is not responsible for:

• data loss;
• missed events;
• missed notifications;
• incorrect name day data;
• incorrect dates;
• incorrect contact data;
• incorrect work schedule or subscription data;
• iCloud synchronization errors;
• Apple system errors;
• errors of third-party providers;
• damage arising from affiliate offers;
• inaccuracies of location-based recommendations;
• damage caused by user error;
• errors of external services;
• damage arising from improper use of exported files.

Consumer protection laws in some countries do not allow the exclusion of certain liabilities. In such cases, the mandatory laws of the relevant country apply.

28. Prohibited use

The application may not be used:

• for unlawful purposes;
• for unlawful processing of another person’s data;
• for harassment, deception, or causing harm;
• for reverse engineering, unauthorized modification, or hacking of the application;
• for automated abuse;
• to infringe third-party rights;
• to circumvent the terms of third-party services;
• to interfere with the operation of the application, Apple systems, or third-party services.

29. Intellectual property

The name, brand, design, code, graphical elements, data structures, texts, and other elements of Tripelfy Evently are the property of the operator or its authorized partners.

The user receives a personal, non-exclusive, non-transferable, and revocable right to use the application.

The user is not entitled to copy, distribute, reverse engineer, modify, sell, or otherwise use the application in a way that infringes the rights of the operator or third parties.

30. Open-source licenses

Tripelfy Evently may contain open-source or third-party software components.

Their licenses may appear in a separate list within the application.

If the current version does not contain any external library or license that must be displayed separately, the following text may be used:

The current version does not contain any open-source license that must be displayed separately.

If a Swift Package, SDK, analytics tool, crash reporting tool, map service, affiliate SDK, or other external component is added later, its license and privacy role must be reviewed separately.

31. App Store privacy disclosure, PrivacyInfo, and data processing categories

Tripelfy Evently may provide privacy information in App Store Connect and in the application’s PrivacyInfo.xcprivacy file in accordance with Apple App Store requirements.

The App Store privacy disclosure, the application’s privacy notice, and the content of the PrivacyInfo.xcprivacy file must be consistent with the actual operation of the application.

Based on the current operating model of Tripelfy Evently, the application does not use its own user account, does not operate its own central user database, and does not store users’ personal data on a central server.

Application data may primarily be stored on the user’s own device, in App Group shared storage, or, if optional iCloud synchronization is used, in the user’s personal iCloud storage linked to the user’s Apple ID.

31.1. Contact data

The application may access contacts stored on the device with the user’s permission.

The purpose of using contact data may include:

• importing birthdays;
• displaying persons linked to name days;
• managing anniversaries or other dates;
• creating events and reminders linked to persons;
• displaying or managing basic contact-related information;
• visually identifying contacts using contact images;
• operating the application’s person-related event management functions.

If contact permission is granted, the application may read several types of data from the iOS Contacts system, not only birthdays.

Such data may include, for example:

• name;
• nickname or display name;
• birthday;
• anniversary or other date;
• phone number;
• email address;
• postal address;
• workplace or organization;
• job title;
• relationship or family-type label;
• contact image;
• other data stored in the relevant contact that is technically available for the functions of the application.

The application uses contact data exclusively to operate the functions of the application.

The application does not sell contact data, does not operate a central contact database, does not transfer the full contact list to its own server, and does not use contact data for advertising profiling.

Part of the contact data may be stored locally on the user’s device, in App Group shared storage, or, if optional iCloud synchronization is used, in the user’s personal iCloud storage linked to the user’s Apple ID.

After revocation of contact permission, the application does not access system contacts again until the user grants permission again. Previously imported or locally stored data may be deleted by the user through in-app deletion options, by removing the application, or, in case of iCloud synchronization, by managing iCloud data.

31.2. Contact images

The application may also process images belonging to contacts if the user grants contact permission and the relevant contact has an image.

The purpose of contact images is solely to visually identify persons, provide a more personal display of events, and improve the user experience within the application.

Contact images may primarily be stored on the device, in App Group shared storage, or, if iCloud synchronization is used, in the user’s personal iCloud storage.

The operator does not have central access to these images, does not use them for facial recognition, biometric identification, advertising profiling, or sale to third parties.

The processing of contact images is based on the contact permission granted by the user and the use of the application’s contact-based functions.

31.3. Profile picture

The application may allow the user to set their own profile picture.

The purpose of the profile picture is personalized display within the application.

The profile picture may be stored locally on the device or, in case of optional iCloud synchronization, in the user’s personal iCloud storage.

The operator does not use the profile picture for facial recognition, biometric identification, advertising profiling, or server-based central identification.

31.4. Photo Library access

The application may request access to the user’s Photo Library if the user wants to select an image, for example for a profile picture, event image, or another visual element within the application.

The purpose of Photo Library access is solely to use images selected by the user within the functions of the application.

The application does not automatically scan the entire Photo Library, does not upload the full photo collection to its own server, and does not use images for hidden analysis.

Selected images may be stored locally in the application or, if optional iCloud synchronization is used, in the user’s personal iCloud storage.

31.5. Custom event images

The application may allow the user to assign an image to custom events.

The purpose of event images is to visually distinguish and personalize events.

Event images may contain personal data if, for example, a person, location, document, family event, or other identifiable content appears in them.

The user is responsible for which image they select, save, or assign to an event.

31.6. Location data

The application may optionally request location data from the user.

The purpose of using location data may include:

• searching for nearby restaurants;
• searching for nearby flower shops;
• displaying location-based gift or activity recommendations;
• refining external offers;
• providing a more relevant user experience.

The use of location data is not mandatory. The user may change or revoke location access at any time in the iOS system settings.

The application does not use location data for continuous tracking, unless a future function separately and clearly states this and the user gives separate consent.

31.7. Work schedule and workplace data

The application may include a work schedule management function.

In this function, the user may record, for example:

• working days;
• shifts;
• start and end time of work;
• rest days;
• workplaces or workplace names;
• work-related notes;
• weekly or periodic working time statistics.

The purpose of work schedule data is solely to support the user’s personal time planning, reminders, and daily organization.

Work schedule data may be stored locally on the device, in local shared storage available to widgets or Apple Watch companions when App Group is used, or, if optional iCloud synchronization is used, in the user’s personal iCloud storage.

The operator does not use work schedule data for labor monitoring, performance evaluation, employer data processing, or centralized profiling.

The user is responsible for which workplace or work schedule data they record in the application.

31.8. iCloud synchronization

The application may optionally use iCloud synchronization.

The purpose of iCloud synchronization is to make the user’s data available between the user’s own Apple devices.

In case of iCloud synchronization, data may be stored in the user’s personal iCloud storage linked to the user’s Apple ID.

The operation, availability, security, and data processing of iCloud are also governed by Apple’s own terms and privacy rules.

The operator does not have direct access to application data stored in the user’s own iCloud account.

31.9. App Group, widget, and Apple Watch data sharing

The application may use App Group or a similar Apple system mechanism to share data between the main part of the application, its widgets, and a possible Apple Watch companion.

The purpose of such data sharing may include:

• displaying upcoming events in a widget;
• displaying name days, birthdays, or anniversaries;
• displaying contact-related events or persons;
• displaying work schedule data;
• quickly displaying reminders or daily information;
• simplified display on the Apple Watch interface;
• ensuring operational consistency between the application and its companions.

App Group, widget, and Apple Watch data sharing is a local data sharing mechanism within Apple’s system. This does not mean that the operator transfers the user’s personal data to its own central server.

The user is responsible for which widget or Apple Watch display they enable, because these may make certain events, work schedule data, contact-based data, or personal information visible to others on the device screen.

31.10. Affiliate links and third-party services

The application may display affiliate links or offers pointing to third-party services.

These may include, for example:

• gift offers;
• flower delivery;
• restaurant recommendations;
• activity recommendations;
• travel or booking offers;
• webshop offers;
• coupons or promotions.

If the user clicks on an external link, the privacy notice and terms of use of the relevant third party apply.

If an affiliate link is used, the operator may receive a commission, but this generally does not result in any additional cost to the user.

31.11. Analytics and crash reporting

Based on the current operation of the application, it does not necessarily use a separate analytics or crash reporting system.

If analytics, crash reporting, performance measurement, or a similar technical monitoring tool is introduced in the future, the privacy notice, App Store Connect privacy answers, and the PrivacyInfo.xcprivacy file must also be updated.

In such case, it must be reviewed separately:

• what data the analytics or crash reporting tool collects;
• whether the data can be linked to the user;
• whether data is transferred to a third party;
• whether user consent is required;
• how data processing can be disabled or restricted.

31.12. Purchase and subscription data

If the application uses StoreKit-based in-app purchases or subscriptions, the purchase and subscription process is handled by the Apple App Store system.

The application may process or verify:

• premium entitlement status;
• active or inactive status of a subscription;
• result of purchase restoration;
• technical entitlement information related to StoreKit transactions.

The operator does not have access to the user’s full bank card data or detailed payment instrument data.

Payment, billing, subscription renewal, cancellation, and refund requests are handled by Apple’s own system and rules.

31.13. PrivacyInfo and App Store checklist

A separate privacy review must be carried out before submitting the application to the App Store.

Areas to be reviewed separately include:

• processing of contact data;
• processing of contact images;
• processing of profile pictures;
• Photo Library access;
• processing of custom event images;
• use of location data;
• processing of work schedule data;
• processing of workplace data;
• operation of iCloud synchronization;
• App Group data sharing;
• widget data display;
• Apple Watch data display, if any;
• affiliate links and third-party services;
• analytics or crash reporting, if introduced;
• StoreKit, in-app purchases, or subscriptions, if introduced;
• local data storage;
• UserDefaults or similar settings storage;
• technical metadata related to files, such as timestamps.

If the application is expanded with a new data processing function, such as analytics, crash reporting, a proprietary server, user accounts, a third-party SDK, an Apple Watch companion, a new widget, or a new purchase system, the privacy notice, App Store Connect privacy answers, and the PrivacyInfo.xcprivacy file must also be updated.

32. Complaints and authorities

In case of privacy, legal, or technical complaints, the user may first contact the operator at:

Privacy and personal-data matters: privacy@tripelfy.com
Legal matters and formal notices: legal@tripelfy.com
General enquiries: hello@tripelfy.com

Users living in the European Union or the United Kingdom may have the right to lodge a complaint with the competent data protection supervisory authority.

In other countries, users may contact the data protection, consumer protection, or judicial authority competent according to their place of residence, if permitted by applicable law.

33. Applicable law

This document has been prepared primarily under Hungarian law.

This does not limit the user’s rights granted by mandatory consumer protection or privacy laws of the user’s place of residence.

For international users, mandatory rules of the relevant country may also apply.

34. Changes

The operator may modify this legal and privacy notice from time to time.

The modified version may appear in the application and/or on the tripelfy.com website.

By continuing to use the application, the user accepts the current terms, unless applicable law requires a different consent or notice mechanism.

35. Contact

Tripelfy maintains separate contact channels so that legal, privacy, security, technical and customer requests can be directed to the responsible team without unnecessary delay.

Balázs Kovács Hungary tripelfy.com

Recommended subject for privacy questions:

Privacy Request – Tripelfy Evently

Recommended subject for data deletion requests:

Data Deletion Request – Tripelfy Evently

Recommended iOS contact permission text

Longer English version:

Tripelfy Evently uses Contacts access to display and import birthdays, anniversaries, people linked to name days, contact details, and contact images, and to create related event reminders. Contact data is not sold and is not transferred to our own central server.

Shorter English version:

Contacts are used to manage birthdays, anniversaries, people linked to name days, contact details, contact images, and reminders. Contact data is not sold or transferred to our own server.