Zauli privacy policy

Last updated: October 13, 2026

Zauli is developed by Arseni Kipachu. This policy explains how we handle information when you use the app. For privacy questions, contact kipachu_dev@outlook.com.

Files stay on your device

Zauli processes files and archives on your device, including PDF, image, text, and text-recognition operations. We do not upload file contents, filenames, paths, archive entries, passwords, or your text input to our servers, RevenueCat, PostHog, or an AI service. Zauli does not require an app account.

Zauli copies imported files into its own local storage and creates new results without overwriting originals. You can move an imported copy or completed result to Recently Deleted using its confirmed removal control. Deleted copies stay there for 30 days, during which you can restore them or delete them permanently. After 30 days, Zauli removes them when Recently Deleted is refreshed. Removing an imported copy from Zauli leaves the original file and completed results in place. Copies exported to Files or another destination must be removed there separately. Imported copies and completed results that you have not deleted remain in local app storage. Removing the app removes its local storage according to iOS behavior. Device backups may include this data according to your operating system and backup settings.

System pickers give Zauli access to files you select. Files stored only in iCloud or another provider may need to download before import. Your file provider handles that transfer. When you save or share a result, the destination you choose receives the exported file and handles it under its own privacy practices.

Local settings and free operations

Zauli stores preferences and a record of its five free successful processing operations locally. Failed or cancelled work does not use this allowance. Imports, previews, archive inspection, reuse of existing results, and export do not use it. The local allowance record contains operation and result identifiers needed to account for completed work. It is not sent to RevenueCat or PostHog.

Purchases and RevenueCat

Apple processes Zauli Pro purchases through your Apple Account. We do not receive your payment-card number or Apple Account password.

RevenueCat checks Pro access, restores purchases, displays offers, and supports purchase and paywall analytics. RevenueCat receives an automatically generated app-user identifier and Apple purchase and transaction records. These records include product and transaction identifiers, purchase dates, and purchase, renewal, or expiration status. RevenueCat may also process paywall interactions and technical context such as app and operating-system versions, store, language, locale, and currency.

We do not supply RevenueCat with your name, email, file contents, filenames, paths, archive entries, or passwords. RevenueCat may connect when the app starts or checks access. Purchases, restores, and loading uncached offers require an internet connection. Previously obtained Pro access may work offline according to the SDK's cached access and expiration rules. File processing runs on your device.

We may compare different offers or prices through RevenueCat experiments. When Usage analytics is on, RevenueCat may send purchase lifecycle, revenue, and paywall interaction events to PostHog using Zauli's random installation identifier. These records associate app usage with purchase outcomes. Custom subscriber attributes are not shared as PostHog person properties.

See RevenueCat's privacy policy and Apple's privacy policy for information about these providers.

Usage analytics and diagnostics

When Usage analytics is on, Zauli sends PostHog usage events and structured diagnostic records to help us understand which tools people use and which operations fail. Records include a random installation identifier, app/platform and screen/tool categories, native app version/build, operation and journey relationships, presentation stages, approved configuration categories, outcomes, elapsed time, and bounded error categories. Some operations report file counts or output-size totals. Records can be connected to the same installation. The identifier is generated on your device and is not an account identifier.

PostHog's US Cloud service receives these records. Zauli disables session recordings, automatic interaction capture, console capture, advertising tracking. Zauli does not request GPS access. PostHog infers approximate location, including country, from the network IP for app usage events. Handled error records contain generated category summaries and exclude original error messages and stacks. Project settings discard event IP addresses. RevenueCat’s integration can create an analytics profile for the random installation identifier. We do not send names, email addresses, file data or custom subscriber attributes as profile properties.

Usage analytics is enabled by default on new installations. Settings explains this collection without a toggle. Previously saved opt-outs remain respected and stop local capture. Disabling capture clears queued application telemetry and unfinished-attempt records. While enabled, Zauli keeps at most 200 sanitized pending events and 24 unfinished attempts. Entries expire from use after 24 hours, and a later app initialization removes expired stored entries. Delivery is best effort and requires an internet connection. File processing does not wait for analytics.

Previously saved analytics opt-outs also update RevenueCat's server-side consent attribute when the device can connect. If a saved opt-out has not synchronized, some server events may be sent before synchronization succeeds.

Zauli does not use advertising identifiers or track you across other companies' apps and websites for advertising. See PostHog's privacy policy for information about that provider.

Support and this website

If you contact us, we receive your email address, message, and any attachments you choose to send. We use that information to respond and troubleshoot. You do not need to send files to request help. Please avoid sending sensitive content or another person's information without permission.

Opening this page uses your browser and an internet connection. The website's hosting provider receives request information needed to serve the page. Your local files are not included in that request.

Use, retention, and your choices

Apple, RevenueCat, PostHog, and our email provider process information needed for their respective services. They may process information outside your country. We use purchase, usage, diagnostic, and support information for the purposes described above and retain it as needed for those purposes, security, and legal obligations. We may disclose information where legally required or necessary to investigate misuse or protect legal rights. We do not sell your personal information.

You can remove local app data by deleting the app. Copies exported to Files or other destinations must be deleted there separately. Removing the app does not cancel an Apple subscription or necessarily remove backups or information already held by service providers. Uninstalling Zauli does not automatically erase previously collected purchase or analytics records.

Use Restore purchases in Zauli's Settings to restore access. Manage or cancel subscriptions through your Apple Account subscription settings.

Depending on where you live, you may have rights to access, correct, delete, or obtain a copy of personal information, object to or restrict processing, withdraw consent where processing relies on consent, or complain to a data-protection authority. Email kipachu_dev@outlook.com to make a request. We may need limited information to verify your request and locate relevant records. Because Zauli has no app account, an email address alone may not identify purchase or analytics records. Never send your Apple Account password or full payment details. Some transaction or legally required records may need to be retained.

Changes

We will update this page and its date if Zauli's data practices change.