Last updated: 2026-11-04
Thank you for using InvoicePad - Invoice Maker (the "App"). We take your privacy seriously. This Privacy Policy explains how the App handles your data.
InvoicePad keeps business profiles, clients and documents in local SwiftData storage and does not automatically upload those records to a developer-operated server. Apple purchases, system backups, user-directed exports and support correspondence have the separate handling described below.
The App lets you choose business logos, signature or stamp images, and supporting document photos. Signature/stamp images can be resized and have empty outer borders trimmed for PDF presentation; these operations run on the device. Issued-document snapshot image data is not replaced when a business profile image is later changed. Photos are chosen through the system photo picker, are stored locally within the App, and are not automatically uploaded to a developer-operated server. A shared document can include those images. The App only accesses the specific photos you select, and functions fully without attaching any.
The App does not use any analytics frameworks, tracking pixels, or third-party SDKs that collect user data. We do not track your usage behavior, location, or any other personal information.
The App has no third-party advertising or behavioral analytics SDK. Apple processes purchases and system services; when you choose to save or share an exported document, the selected destination receives its contents. Website hosting and support correspondence are described below.
InvoicePad uses Apple StoreKit for a yearly subscription and a one-time non-consumable Lifetime purchase. Loading products, checking offer eligibility, purchasing, restoring and verifying access communicate with Apple. The app reads verified product and entitlement information, including expiration or revocation status where applicable, and keeps local access state. Apple processes payment; InvoicePad does not receive your payment-card details or Apple Account password. Current and supported historical purchase access depend on verified transactions. See the InvoicePad terms for the available plans and subscription handling.
Use the available document and client deletion controls to remove those local records. A business profile can be deleted only when another profile exists and no document still references it. Deleting a client does not delete its documents or the client identity already saved in an issued or shared document. Document deletion removes its line items, rather than all clients, profiles or preferences. There is no Recently Deleted or full-database import/restore feature.
Business-profile and defaults editors keep unsaved edits in the current form until you choose Save; cancelling discards those edits. Saving defaults is a separate action from saving the parent profile editor. These temporary form drafts are not a durable backup. Saved invoice, estimate and receipt drafts are local document records. Issuing or sharing a document can preserve a separate business/client identity snapshot, including relevant contact details, logo or signature, so later profile changes or client deletion do not rewrite that document's saved identity.
CSV export is available without Pro and produces readable, unencrypted files. In version 1.3 and later, an export includes a document-summary file and a companion line-item file with ordered priced items and description-only rows. Description rows contain text but no quantity, price, total or taxable value; genuine zero-priced items remain priced rows. Earlier versions may export only document summaries. CSV does not include original images or signatures/stamps, complete business/client databases, identity snapshots, all item attributes or preferences. Temporary CSV copies are created inside the App container for sharing. Version 1.3 attempts to remove its export copies when the share flow finishes or fails; a file-system failure or interruption can leave temporary copies until the operating system clears them, with no guaranteed cleanup deadline. PDF and CSV outputs cannot reconstruct the database and there is no built-in import. The destination you select handles its own copy. Apple device backups may include local App data depending on settings and successful completion; recovery requires a usable backup and Apple's process and is not guaranteed. Removing the App can remove its local container, but does not erase previously exported files, recipients' copies or older device backups. We cannot retrieve those copies or restore your records.
The App is not directed at children under the age of 13. We do not knowingly collect personal information from children. The App is designed for business professionals and freelancers.
We may update this Privacy Policy from time to time. Any changes will be reflected by the "Last updated" date at the top of this page. Continued use of the App after changes constitutes acceptance of the updated policy.
When you enable payment-due reminders, InvoicePad requests iOS notification permission and schedules local alerts for eligible unpaid invoices. Alerts can contain the document number and whether it is due today or tomorrow; a local document identifier is used to associate the alert with its record. Notifications can appear on the Lock Screen according to your settings. No developer-operated push service receives invoice content. You can disable reminders or change notification visibility in iOS Settings; delivery is subject to system conditions.
If you have any questions about this Privacy Policy, please contact us at captainlongevity@gmail.com.
These InvoicePad legal pages are served by Vercel. Opening a page sends ordinary request information, such as IP address, browser information and the requested URL, to the host for delivery and security; see Vercel's Privacy Notice. These pages contain no advertising or analytics scripts. If you email support, we receive the address and information you choose to send to answer your request. Avoid including sensitive records that are not needed for that request.
The updated App checks document, line-item, client, saved-item, text-preset, business-profile and default-profile changes before reporting completion. Document edits, replacement line items, attachments and any new-document numbering change save together. Failed edits or cascade deletion keep the original affected records, relationships, stored amounts and attachment bytes; failed ordinary forms keep their current input while that editing state remains open. These temporary values are not durable drafts or backups. Adding a saved item to a document draft separately updates its usage count; canceling the document does not undo an already saved usage count. If that count fails to save, the item remains in the draft with a notice. New duplicates and estimate conversions retain supported source rows and attachments as new drafts with new row identifiers; recurring-document generation retains its existing behavior of creating rows without copying source photo attachments. A failed copy keeps the source recurrence date and numbering state and does not leave partial new documents. Document reminder cancellation follows successful deletion.
Existing document-photo bytes are retained when editing rather than recompressed merely by reopening and saving. If existing bytes cannot be previewed, the editor shows a placeholder and explanation and keeps those bytes unless you explicitly remove that attachment. New selected images continue to be prepared locally as JPEGs; if image encoding fails, the document save stops and keeps the original record and current editing values. This does not repair unreadable media or guarantee recovery from damaged data.
Preparing a share checks identity freezing and database persistence before handing a file to the sharing interface. If sharing is canceled, the App attempts to restore an unchanged, still-unissued draft to its earlier identity-snapshot state; a later edit prevents that restoration from overwriting newer data. If the restoration save fails or the process is interrupted, an identity snapshot can remain stored even when the share was canceled. Independently generated files, recipient copies and system backups remain separate from this database operation.
Product loading can check local network availability and retry unavailable Apple StoreKit prices. It does not upload document records or change an existing verified purchase entitlement. PDF rendering may adjust presentation contrast or fit amounts without changing the stored brand color or saved amounts.