Privacy policy

Information used to provide the service

The service processes your email address and verified account identifier, order and payment references, purchased plan and access dates, payment status, download-link request history and transactional email delivery status. If the existing Google sign-in path is used, account records may also contain the profile name, image and provider identifier returned by Google.

Why the information is used

Account and order records deliver access and restore purchases after email verification. Download-link records support recent download history and authorization. Hashed rate-limit identifiers, verification failures and operational audit records help prevent abuse and investigate delivery problems. A download-link request is not evidence that the file finished downloading or was installed.

Payment details and Apple credentials

Dodo Payments handles the hosted checkout when configured. This library does not collect your full payment-card number or Apple ID password. Do not send card details, Apple credentials or one-time email codes to support.

Cookies and email

A language-preference cookie remembers your interface language. Essential session cookies keep you signed in; email verification confirms control of your address. Transactional messages include verification codes and purchase confirmations. Confirmation messages return you to the website and do not attach the whole library. The current IPA pages do not load advertising or analytics trackers; hosting providers may still process request logs.

Service providers

The implementation uses Supabase for database, authentication and private file storage, Dodo Payments for hosted payments, and Resend for purchase confirmation messages when these services are configured. Verification emails use the authentication provider’s configured mail service. Hosting and these providers process the data needed to operate their services; processing locations depend on the deployed configuration.

Retention and privacy requests

You can ask the operator about access, correction or deletion of your information through the Contact page. Identity verification may be necessary. Order or security records may need to be retained to resolve disputes or meet applicable obligations. The final retention schedule and operating entity must be published before paid launch; this version does not promise an unimplemented automatic deletion period.

Policy updates

This policy describes the current IPA service implementation. The operator should update the published date and disclosures if service providers, tracking or data use change.

Service operator

The operating entity, service address and data-retention schedule have not yet been published. This is a prelaunch disclosure; these details must be completed before paid launch.

Use the support email below for order, privacy or resource-rights enquiries. Include an order reference when relevant; never send passwords, payment-card details or verification codes.