Coverage under this Privacy Policy applies to the privacy-related handling that occurs when Zalobi is used, when purchases are processed through supported app-store channels, or when a user communicates with us about the app.
Policy Coverage
Zalobi is operated as an accountless utility app. This Policy describes the broad categories of information that may be collected, used, retained, shared, and protected in connection with the app and related legal or support communications.
The Policy applies to information handled by us directly and to limited processing carried out by service providers that help operate, distribute, secure, analyze, or support the app. It also applies when information is required for purchase administration, compliance, fraud prevention, or responding to privacy requests.
This Policy does not replace the privacy terms of app stores, device platforms, payment processors, or other third-party services that operate under their own privacy notices. Their handling of information is controlled by their own terms and policies.
Private Content Context
Some content entered into a utility app can be personal or sensitive because it reflects a user's notes, preferences, routines, observations, or other self-recorded information. Zalobi treats this context carefully and limits handling to purposes that are reasonably connected to providing, maintaining, securing, and supporting the app.
Users should avoid adding information that they do not want handled under this Policy or that they are not authorized to provide. Where local laws treat certain user-added content as sensitive, processing will be handled under an applicable legal basis, such as user direction, consent where required, performance of the app service, legitimate interests in security and operation, compliance with law, or protection of legal claims.
How this notice treats records connected with app use
Information covered by this Policy may include content a user enters into the app, app activity records, device or diagnostic information, purchase-related records received from app-store or payment channels, and messages sent to us. The exact information involved depends on how the app is used and what information is made available through the user's device, platform, or app-store environment.
User content may include text, labels, dates, notes, settings, and other material a user chooses to create or maintain in the app. Operational records may include device type, app version, language or region settings, crash information, usage events, approximate technical identifiers, and logs needed to detect errors or protect the app from misuse.
Purchase-related information is usually handled by the app store or payment provider. We may receive limited confirmation, receipt, entitlement, transaction, or fraud-prevention information needed to provide purchased access, respond to payment issues, or comply with financial and legal requirements.
Reasons information is handled
Information is used to operate and improve Zalobi, maintain app functionality, preserve user-selected content where the app design supports it, process purchase-related entitlements, provide support, detect technical problems, prevent abuse, and comply with legal obligations.
Where applicable law requires a legal basis, the basis may include performance of a contract when processing is needed to provide the app or purchased access, consent where a user has given it, legitimate interests in maintaining safety and reliability, legal obligation where records must be kept or disclosed, and legal claims where information is needed to protect rights or respond to disputes.
Aggregated or de-identified information may be used for analytics, quality review, operational planning, and similar purposes. Such information is not intended to identify a specific user and will be handled in a manner consistent with applicable law.
Sharing and Service Providers
Provider access can occur when outside companies support Zalobi's hosting, storage, distribution, payment confirmation, analytics, crash review, security, or customer communication needs. Access is limited to the role each provider performs and to lawful operational instructions.
App stores and payment providers usually handle purchases under their own rules. We may receive limited records from those channels when needed to confirm access, address transaction issues, prevent misuse, or meet legal duties.
Disclosure can also be required for court orders, regulatory demands, protection of rights, safety issues, or a business transfer. Because the app may be available in more than one country, provider processing and support activity may cross borders under appropriate safeguards or other lawful transfer grounds.
How we decide whether information still needs to be kept
Retention is based on purpose. App content, operational records, purchase confirmations, support communications, and legal records are kept only while they still serve a legitimate app, compliance, security, accounting, dispute, or rights-management need.
Different categories follow different periods because device storage, platform records, backup cycles, tax duties, fraud review, and legal holds do not operate on the same schedule.
After a record no longer has an active purpose, the operator may remove it, aggregate it, de-identify it, or keep it outside ordinary use until deletion is technically or legally available.
Security Measures
Protection of information in Zalobi relies on layered controls for access, provider handling, transmission where supported, and issue response. Those controls are chosen with the sensitivity of user-added content and ordinary mobile-app risks in mind.
Complete security cannot be promised for any app, device, network, or storage environment. Users should keep their devices and app-store credentials protected. If a security event triggers a legal notice duty, notice will be given in the form required by law.
Updates to this notice and how they apply
We may update this Policy to reflect changes in law, app operations, service providers, security practices, or legal requirements. Material changes will be communicated through an appropriate channel, such as an in-app notice, updated policy page, app-store information, or another reasonable method.
Version details: effective June 7, 2026; last updated June 7, 2026.
Continued use of Zalobi after an updated Policy becomes available means the updated version applies from its stated date, except where applicable law requires a different form of notice or consent.
Safeguards that apply to age-sensitive use
Zalobi is intended for users who have the legal capacity to use mobile apps and make privacy choices under the laws that apply to them. Where a user is below the age at which they can provide valid privacy consent on their own, a parent or legal guardian should supervise use and handle any required permission.
If information from a minor has been provided in a way that requires parental action, deletion, or another legal response, we will handle the matter according to applicable law once we have enough information to evaluate the request.
What you can request about app information
Privacy requests can ask for review, correction, removal, limitation, objection, portability, or consent withdrawal when the law that applies to the user grants that option.
Some choices are handled through device settings, app-store controls, platform permissions, or in-app controls when available. Requests sent to the operator are reviewed against legal duties, technical limits, security needs, purchase records, and the rights of other people.
Local privacy laws may provide additional protections. When those laws apply, the operator will handle eligible requests within the required period and will not treat a user unfairly for making a valid privacy request.
Where to Send Privacy Requests
Privacy communications for Zalobi should be routed through welcome@zalobi.app. Use one clear request and we will review it under the privacy law that applies.
A response may depend on lawful limits, technical feasibility, and the rights of other people.