PillowBook

PillowBook Privacy Policy

Effective date: September 13, 2026
Last updated: September 13, 2026
Version: 1.0

This Privacy Policy applies to the iOS application PillowBook (the “App”) and the public support pages directly associated with the App.

The controller responsible for the App’s processing described in this policy is PillowBook’s independent developer, identified in the Developer or Seller field on the App Store product page (the “Developer”). Contact: pillowbook2026@gmail.com.

1. Privacy summary

The current version of the App:

“Stored on device” does not mean that information can never leave the device. iOS backup, device migration, file sharing, your chosen email service, and Apple’s store services may process information according to your settings and their own privacy policies, as explained below.

2. Information processed on your device

The App may process and store the following information locally to provide features you request. The Developer has no server or administrative console through which to access this information remotely.

2.1 Books and reading information

Content hashes are used only to detect duplicate imports. They are not used to identify you and are not sent to the Developer by the App.

2.2 A background image you select

If you use the iOS photo picker to choose a reading background, the App receives only the image you expressly select; it does not request access to browse your entire photo library. A resized and processed copy remains locally until you replace or clear it, or delete the App.

2.3 Speech and on-device intelligence

Apple system components or voice-resource downloads may be handled by Apple according to your device settings and Apple’s policies.

2.4 Device authentication

The “Vault” uses iOS device-owner authentication. Face ID, Touch ID, or device-passcode verification is performed by the operating system. The App receives only a success, cancellation, or failure result; it does not receive or store your face image, fingerprint, passcode, or biometric template.

2.5 Purchase status

The App locally stores whether the library limit has been unlocked, the number of tips recorded on that device, and a limited set of transaction identifiers used to avoid counting the same tip twice. StoreKit verifies entitlement and transaction authenticity. The App does not create a purchase profile on a Developer server.

3. Information that may leave your device

3.1 Support email you choose to send

If you select Feedback in the App and affirmatively send an email, the Developer may receive:

This information is used only to respond to your request, diagnose the reported problem, maintain security, improve functionality directly related to the request, comply with law, or handle a dispute. Sending a support email does not add you to a marketing list. The Developer will not ask you to send a complete book, password, payment-card information, or unnecessary sensitive information.

Your message passes through your chosen email provider and is delivered to a Developer mailbox provided by Google Gmail. Those providers process email and transmission data under their own policies. Unless specifically needed to investigate an issue, do not send book contents, identity documents, financial or health information, or other sensitive material.

3.2 Apple App Store and in-app purchases

Apple processes purchases of the non-consumable library-limit unlock, repeatable coffee tips, Apple Offer Code redemptions, purchase restoration, and App Store ratings. The App may receive verified product, transaction, entitlement, or revocation status, and the Developer may receive sales and financial reports that Apple makes available through App Store Connect.

The Developer does not receive your payment-card number, Apple Account password, or complete payment credentials. Apple is responsible for its own processing. See Apple’s Privacy Policy.

3.3 Wi-Fi Transfer

The App starts a temporary local-network web service only when you open the Wi-Fi Transfer screen. A browser transfers a file directly to the iPhone without using a Developer server. The App does not retain the other device’s IP address or create a transfer log. A successfully imported book remains locally as described in this policy.

Wi-Fi Transfer currently uses local HTTP rather than a TLS-encrypted connection and uses the four-digit pairing code shown on the iPhone to restrict uploads. The code reduces accidental transfers but is not a defense against a hostile local network. Use this feature only on a private Wi-Fi network you trust, share the address and code only with a device you control, and close the transfer screen when finished. Public or guest networks, including networks that monitor or isolate clients, are not appropriate for sensitive books.

3.4 Public privacy and support pages

This policy and the support pages are intended to be published as static webpages that require no sign-in. The hosting provider may automatically process an IP address, request time, requested path, browser or device type, response status, and similar technical logs to deliver the pages, maintain security, and prevent abuse. The Developer does not intentionally add advertising, behavioral analytics, cross-site tracking, or non-essential cookies to these pages. Processing that the host determines for its own purposes is governed by the terms shown for the hosting domain. When selecting or changing the host, the Developer will verify the actual configuration and add provider, retention, and international-transfer details where applicable law requires them.

4. Files, backups, and device migration

The App has no Developer-operated cloud-sync feature. Books and generated narration audio are stored in the App’s Documents directory and may be visible in the Files app, Finder file sharing, or device migration to a person who can access your unlocked device.

Depending on your iOS, iCloud, and device-backup settings, Apple may include local App data in iCloud Backup or a computer backup and restore that data during migration or recovery. These backups are controlled by you and Apple; they are not a Developer-operated sync service. Deleting the App normally removes its current on-device container. Offloading the App may retain its data, and copies already present in a backup or another location may remain.

5. Purposes and legal bases

Where applicable law requires a legal basis, the Developer relies on:

The App does not use personal data to make solely automated decisions that produce legal or similarly significant effects, and it does not create advertising profiles.

6. Disclosure, sale, and tracking

The Developer does not sell personal data, “share” it for cross-context behavioral advertising, exchange it with data brokers, or track your activity across other companies’ apps or websites.

Information may be processed or disclosed only in these limited circumstances:

The current App contains no third-party advertising or analytics SDK. Before releasing a feature that materially changes processing — such as accounts, cloud sync, analytics, crash reporting, advertising, online AI, or another backend — the Developer will update this policy, the App Store privacy disclosures, and any required consent flow.

7. Retention and deletion

You can delete individual books, bookmarks, a selected background, and narration caches within the App. To remove all local App data from the device, use Delete App in iOS rather than only Offload App, and manage iCloud or computer backups as appropriate.

To ask about or request deletion of support correspondence actually held by the Developer, email pillowbook2026@gmail.com and provide enough information to locate the correspondence. Because the Developer cannot access your device, the Developer cannot remotely view, export, or delete books and reading information stored only on that device.

8. Security measures and important limitations

The App relies on controls such as the iOS sandbox, App Group permissions, system file protection, and system authentication, and is designed to minimize information leaving the device. The Developer also applies access and retention limits proportionate to the risk of support correspondence received.

No storage or transmission method can be guaranteed completely secure. In particular:

If you believe a security or privacy incident involving the App has occurred, contact the Developer promptly, but do not attach sensitive files to your first message.

9. Your privacy rights

Subject to applicable law, you may have rights to request information, access, correction, deletion, restriction, objection, or portability regarding personal data held by the Developer; to withdraw consent; and to complain to a competent data-protection authority. You will not receive discriminatory treatment for exercising a privacy right. Rights may be limited by reasonable identity verification, the rights of others, legal retention duties, and other statutory exceptions.

For people in the European Economic Area, United Kingdom, or Switzerland, the Developer will honor applicable GDPR or equivalent rights. Support information is generally processed to carry out a request you initiated or under legitimate interests in support and security. You may also complain to the data-protection authority where you live.

For California residents, to the extent the CCPA applies, categories the Developer may have processed in the preceding twelve months are limited to identifiers/contact details, customer-support content, and limited diagnostic information you provide when contacting support. The source is you; purposes are support, security, and legal compliance; recipient categories are email-service providers and legally authorized authorities. The Developer does not sell or share this information for cross-context behavioral advertising and does not use or disclose sensitive personal information to infer characteristics.

For people in Japan, the Developer handles personal information within the stated purposes under the applicable Act on the Protection of Personal Information and accepts inquiries and requests concerning disclosure, correction, cessation of use, or deletion at the contact address below.

To exercise a right, email pillowbook2026@gmail.com. The Developer may request information matching the original support correspondence to reasonably verify identity and will respond within the period required by applicable law.

10. Children and teens

The App is a general-purpose reading tool. It is not designed to collect children’s personal data and contains no advertising, social network, or public-posting feature. The Developer does not knowingly ask children to provide personal data. A minor who needs support should have a parent or guardian contact the Developer where appropriate and should not send unnecessary sensitive information. If the Developer learns that children’s personal data was received without an appropriate legal basis, reasonable steps will be taken to delete it.

The App does not provide or sell book content. Material a user imports may have varying age suitability and should be managed by the user or the user’s guardian.

11. International processing

A support email, or necessary technical information generated when you visit the public privacy and support pages, may be processed by your email provider, Google, the webpage host, and the Developer outside your country or region. Where applicable law requires it, the Developer will use reasonable contractual, organizational, or other safeguards. Processing locations depend on the services you choose and their infrastructure; review the relevant provider notices, including the Google Privacy Policy.

12. Changes to this policy

The Developer may update this policy to reflect changes in features, law, or operations. The revised policy will show a new “Last updated” date. If a change materially affects user rights or processing, the Developer will provide more prominent notice where reasonably practicable, such as an in-App notice, the support page, or App Store release notes. Because the App has no account system, the Developer generally cannot email every user proactively.

13. Contact

For privacy, data-rights, or security questions:

Do not attach a complete book, identity document, payment-card information, password, or other unnecessary sensitive material to your first message.