Privacy Notice for ClientFlow ClientFlow is a business productivity app for managing clients, appointments, scheduling, and related workflow information. This notice explains what stays on the user’s device, what may be processed by third-party SDKs, and how privacy choices such as tracking permission work in the current version of the app. Effective date: [29-03-2026] Last updated: [[29-03-2026] Short version. Client information entered into ClientFlow, such as names, phone numbers, addresses, notes, appointments, and session amounts, is stored locally on the user’s device in the current version of the app and is not uploaded by us to our own servers. The app also uses Google AdMob / Google Mobile Ads SDK, which may process its own advertising, device, interaction, crash, and performance-related data under Google’s policies. Contents Controller Scope of this notice Data entered by the user What we do not collect from client records Third-party advertising and SDK data No sharing of client-entered fields with AdMob by us App Tracking Transparency Calendar integration Legal bases under GDPR Data minimization and purpose limitation Data retention Your rights Security International transfers Children Changes to this notice Contact 1. Controller ClientFlow is provided by: [efthimis tsantes] Email: [efthimistsantes@hotmail.com] Where applicable under the General Data Protection Regulation (GDPR), we act as the controller for personal data processed through the app, except where this notice explains that certain third-party providers process data under their own policies. 2. Scope of this notice This notice applies to the current version of ClientFlow as made available to users. It is intended to describe the practical privacy behavior of the app as it currently operates. If a future version introduces cloud sync, user accounts, external backups, server-side processing, API-based AI features, or any other off-device processing of client-entered records, this notice should be updated before or at the time that such processing begins. 3. Data entered by the user ClientFlow allows users to manually enter information such as: client names phone numbers addresses or visit locations notes appointment and session details session prices or amounts This information is stored locally on the user’s device and is not uploaded by us to our own servers in the current version of the app. In practical terms, this means the app works as an on-device business tool for these fields. In the current version, we do not operate a backend service that receives or stores these client records. 4. What we do not collect from client records We do not intentionally collect, transmit, or store on our own servers the client information that users type into the app, including names, phone numbers, addresses, notes, appointments, and session records, unless a future version of the app clearly introduces such a feature and this notice is updated accordingly. In other words, client fields entered by the user remain under the user’s control on their own device. Important distinction. This notice concerns the current version of the app. It does not promise that no third-party SDK ever processes any data; it states that the client records entered by the user are not intentionally uploaded by us to our own servers. 5. Third-party advertising and SDK data ClientFlow uses Google AdMob / Google Mobile Ads SDK to display ads. As part of providing advertising services, Google and its partners may process certain categories of data associated with the advertising SDK, such as: device identifiers advertising data product interaction data crash data performance data IP address This processing is governed by the relevant third-party provider’s policies and disclosures. 6. No sharing of client-entered fields with AdMob by us The client information entered by the user into ClientFlow is not intentionally sent by us to Google AdMob as client profile data. AdMob-related processing is limited to the advertising SDK’s own operation in the app and the data categories associated with that SDK. Put differently, when a user types a client’s name, phone number, address, notes, or appointment details into the app, those fields are intended to remain local to the device and are not used by us as advertising payload for Google AdMob. 7. App Tracking Transparency ClientFlow may display Apple’s App Tracking Transparency permission prompt. If the user grants permission, advertising-related data may be used by advertising partners for tracking, advertising, and advertising measurement in accordance with Apple’s framework and the relevant provider’s policies. If the user does not grant permission, the app should continue to function, but advertising-related processing may be more limited. Users can change their tracking choice at any time in iOS Settings. 8. Calendar integration If the user chooses to use calendar-related features, ClientFlow may write appointment details to Apple Calendar on the user’s device through Apple system frameworks. This occurs only when the user uses that feature. Calendar-related data written to Apple Calendar is then subject to the user’s device environment and Apple’s own system behavior. 9. Legal bases under GDPR Where GDPR applies, the legal bases for processing are: Performance of a contract / provision of the requested service for locally storing and managing scheduling and workflow data entered by the user. Consent where required for tracking-related advertising activities, including where the user chooses whether to allow tracking via Apple’s ATT prompt. Legitimate interests where permitted for limited diagnostics, stability, app integrity, and app performance support. Where a third-party provider acts under its own policies, that provider may rely on its own legal bases for the processing it carries out. 10. Data minimization and purpose limitation We aim to keep processing limited to what is necessary for the app to work as described. In the current version, client records entered by the user are used primarily for local business-management functionality, such as displaying client details, scheduling sessions, saving notes, and managing related workflow entries on the device. We do not describe the app as collecting those client-entered fields to our own backend because, in the current version, it does not do so. 11. Data retention Data entered by the user into ClientFlow remains stored on the user’s device until edited or deleted by the user, or until the app is removed from the device, unless a future version changes this behavior. Advertising, crash, performance, and related SDK data processed by third-party providers may be retained according to those providers’ own retention policies. 12. Your rights If GDPR applies to you, you may have the right to: access personal data rectify inaccurate data erase data restrict processing object to certain processing data portability withdraw consent where consent is the legal basis lodge a complaint with a supervisory authority Because client-entered records are stored locally on the device in the current version, many correction and deletion actions can be performed directly by the user inside the app. 13. Security We take reasonable steps to support the security and stability of the app. However, no software, device, storage medium, or transmission channel can be guaranteed to be completely secure. Users are responsible for controlling access to their own devices, including the use of device passcodes, biometric access controls, and other device-level protections where available. 14. International transfers Third-party providers such as Google may process relevant SDK-related data on servers located outside your country or the European Economic Area. Where applicable, such processing is governed by the provider’s own contractual and legal safeguards. 15. Children ClientFlow is not intended for children. We do not knowingly design the app for children or encourage children to submit personal information through it. 16. Changes to this notice We may update this Privacy Notice from time to time. If we do, we will revise the “Last updated” date above. 17. Contact For privacy questions, contact: [Efthimis Tsantes] [efthimistsantes@hotmail.com]