Privacy
Updated November 4, 2026. This notice covers the reference-based iOS app, Android test app, and native Mac submission candidate (0.1.0, build 3). Available features depend on the distributed version. Earlier Mac prototypes are excluded.
Contacts and local settings
Contact names, postal addresses, company information, joint names, sender details and phone numbers are read from OS Contacts for display and printing in memory. Their text is not copied into app storage or iCloud. The app does not edit your OS Contacts. Local settings retain app pattern IDs, contact/address/phone field references, typography, geometry, and whitespace positions. Contact references are personal data, not universal anonymous person IDs. Search and source comparison text is not persisted.
iCloud, AI, printing and PDF
On Apple platforms, only the supported common print preferences and sender-pattern settings are synced. Contact text, references and background images are excluded. AI layout checks receive geometry and character counts, not contact text. Printing sends the addressed document to your chosen printer. PDFs you explicitly save or share contain the printed information. Preview backgrounds and guides are excluded from address PDFs.
Seasonal notifications
On iOS and Android, optional notifications use Firebase Cloud Messaging and require separate app consent and OS permission. They are off by default. Registration uses the Firebase installation identifier, notification tokens (including APNs on iOS), language and device/app technical information. Contact text and reference IDs are never sent. Opting out stops receipt and requests deletion of the messaging registration; failed requests are retried when possible.
Optional app usage sharing
Supported iOS and Android builds offer “Share app usage” in Settings. It is off by default, separate from notification consent, stored only on the device and never synced to iCloud. You can edit, print and save PDFs without sharing usage.
When enabled, Google Analytics for Firebase receives predefined screen names and categories of editing actions, pattern/selection actions, PDF preparation and saving, system-print UI opening/closing, direct-print connection/acceptance states, purchase/restore outcomes, AI layout-review usage outcomes, and contact-permission and notification-setting choices. The app never sends contact text, contact/address/phone field IDs, pattern IDs, search terms, exact formatting values, printer names/addresses, PDF/image contents or error descriptions.
The Google SDK also processes an app-instance identifier, sessions, first launch, device/OS/app versions, language and related technical information. Google may infer an approximate region from your IP address. Because an identifier can relate app interactions, we do not describe this as fully anonymous. On iOS and Android, the SDK may record purchase events, including product, value, currency and transaction identifiers. The app does not send your Apple Account, Google Account credentials or payment-card details to Analytics. Advertising-ID collection, ad personalization and identity derived from Contacts are disabled.
Turning sharing off stops app analytics collection and resets local analytics data and its identifier. This does not automatically delete information already sent to Google. See Firebase privacy and security and Google’s privacy policy.
Purchases and this website
iOS payments, refunds and subscriptions are handled by Apple. The app verifies StoreKit entitlements without linking them to Contacts. This promotional website uses fictional samples; it does not read OS Contacts and includes no website analytics or advertising tracking.
Android purchase verification
Android payments, refunds and subscriptions are managed through Google Play. Printing or saving one page at a time is free; batch output requires a lifetime or annual plan. For purchase, restore and entitlement checks, the product ID, Google Play purchase token, a temporary request nonce and Firebase App Check token are processed by the AddressPrint Firebase verification service and Google services. Contact text and OS contact, address or phone references are never included.
The service checks authoritative Google Play purchase status and expiry and acknowledges eligible purchases. We do not maintain a purchase-token database. The app keeps verified access temporarily in memory; reconfirmation after restarting requires an internet connection. Free single-page output does not require purchase verification. Firebase App Check uses Google Play Integrity and app/device technical information to protect purchase verification. This required purchase-security processing is separate from optional usage sharing.
Cloud infrastructure may retain connection/security records including IP address, time and HTTP status. Application verification logs do not contain purchase tokens, contact text or printer information. AddressPrint does not obtain payment-card numbers or Google Account credentials. Use Google Play for purchase/refund requests, or the contact below for data inquiries. See Firebase Privacy and Security.
Google Play purchase notifications reach the verification service through Google Cloud Pub/Sub. Notifications containing product identifiers and purchase tokens may be temporarily queued for delivery or retries for up to seven days. Notifications are not linked to Contacts, and the service does not create a separate purchase-history database or log notification bodies.
Mac and direct-print recovery
The native Mac candidate contains no analytics SDK or Firebase notification SDK. On iOS and Mac, direct printing keeps only a local unresolved-attempt flag for recovery after restart. This flag contains no contact text, PDF, printer address or print-job ID and is not synced to iCloud or analytics.
Contact
Cavemen.jp, K.K.
info@cavemen.jp
Developer website