Your reading stays yours.

Who is responsible

Ken Eric Chalk operates History Wake as an Australian sole trader, ABN 43 949 110 407. In this policy, “History Wake”, “we” and “us” refer to that business.

Where the Privacy Act 1988 (Cth) and Australian Privacy Principles apply, this policy describes how we meet those obligations. We apply the commitments in this policy to History Wake users generally.

At a glance

• Reading progress, choices and preferences are stored locally and are not sent to History Wake or RevenueCat.
• We do not sell personal information, show third-party advertising or track you across apps or websites.
• Apple, Google Play and RevenueCat process limited purchase and device information needed to offer, verify and restore books.
• You can read the included Titanic book without an account or another purchase.

Reading information stored on your device

History Wake stores reading progress, story choices and history, completed runs, discovered endings, display preferences, narration speed and the selected device voice in local app storage. We do not receive or upload this reading information.

Local reading information remains until it is replaced or removed during normal app use, or the app is deleted. Device backups may retain or restore a copy according to your Apple or Google settings. To remove it, uninstall History Wake and, if required, remove the app's backup using your device or cloud-backup settings.

Purchase and entitlement information

On supported mobile builds, History Wake uses the Apple App Store or Google Play together with RevenueCat to show local prices, verify one-time purchases and restore books. When the app starts or returns to the foreground, and when it checks prices, purchases or restores, the RevenueCat SDK contacts RevenueCat.

RevenueCat receives a pseudonymous App User ID, a store receipt or purchase token and purchase history, device type and operating system, last-seen and transaction information, and related product, locale and currency information. It validates those records and returns entitlement information to the app. The SDK caches its App User ID and latest purchase-entitlement information on the device.

We use that information only to operate purchases and restoration, prevent fraud, answer purchase-support requests and understand purchase performance. History Wake does not configure RevenueCat with your name or email address, send it an advertising identifier, or receive payment-card details. If you voluntarily include the App User ID in a support request, it may be associated with your email and purchase details while we resolve that request. An App User ID may be merged with another pseudonymous identifier when a store purchase is restored.

Release 1 has no History Wake account and does not transfer ownership between Apple and Android. An eligible purchase can be restored on the same platform using the store account that made it.

Website visits and support messages

Cloudflare and the website hosting service may automatically process technical request information such as an IP address, browser or device type, requested page, timestamp and routing or security data to deliver and protect historywake.com. We do not create a separate visitor profile or use that information for advertising.

If you email support, we receive your email address and the information you choose to send. This may include a book title, store platform, device model, operating-system version, approximate purchase time, order ID, exact error message and any attachment you include. We use it to answer the request, investigate a problem, locate a purchase record, protect the service or meet a legal obligation.

Never send payment-card details, your Apple or Google password, or a full receipt containing unrelated purchases.

Read Aloud

Read Aloud passes the selected passage text, voice and speed setting to your browser or device text-to-speech service. Some system voices may process text off-device under the platform provider's settings and privacy terms. History Wake does not request microphone access, record your voice or receive the generated audio.

Website introduction video

The introduction uses a YouTube player. The website displays a locally hosted preview image and connects to YouTube only when you press play. Watching the video or following a YouTube link uses Google's service under its own privacy policy. Saving the release-date calendar file does not subscribe you to an email list or send us your calendar details.

Advertising, tracking and automated decisions

History Wake does not use app information for third-party advertising, data brokerage or cross-app tracking. The website does not intentionally set advertising or cross-site tracking cookies.

We do not use personal information to make decisions that have a significant legal or similarly significant effect. The app's entitlement check only determines whether the store reports an active purchase for a book.

Service providers and overseas processing

RevenueCat processes purchase and entitlement information for History Wake as a service provider. RevenueCat states that it and its service providers process and store information in the United States. Cloudflare and the website hosting and email services may process technical or support information in Australia, the United States, the European Economic Area and other countries where they operate.

Apple and Google process payments and store-account information under their own terms as platform providers. We require service providers that receive user information through History Wake to use it only for the purposes described here and provide the same or equivalent privacy protection described in this policy. Their policies provide more detail:

• Apple Privacy Policy
• Google Privacy Policy
• RevenueCat Privacy Policy
• Cloudflare Privacy Policy

How long information is kept

• Local reading information remains on your device as described above.
• Support messages are kept while a request is active and for up to 24 months after it closes. We may keep a necessary record longer to meet tax, accounting, dispute-resolution or other legal obligations.
• Pseudonymous purchase and entitlement records remain in RevenueCat while we use that service, unless they are deleted earlier in response to a valid request or must be kept for legal reasons. Deleting a RevenueCat customer profile removes its RevenueCat history; it does not refund a purchase or delete Apple or Google store records.
• We do not maintain our own website analytics profile. Website security and request logs are retained under the hosting and Cloudflare services' operational and legal retention controls.

Your choices, access and complaints

You can use History Wake without identifying yourself. Depending on applicable law, you may ask for access to, correction of or deletion of information we control, withdraw consent where processing relies on consent, or make a privacy complaint.

You may email the contact below. “Privacy request” in the subject helps us route it, but no special form or wording is required. State the request and the platform involved. Because there is no History Wake account, we may need an order ID or the Purchase Support ID shown in app Settings to locate a purchase record and may ask for limited information to verify the request. Deleting a RevenueCat record may affect purchase support or restoration until the store receipt is processed again.

We will acknowledge a complaint, investigate it and aim to respond in writing within 30 days. We will explain the action taken or why a store-controlled record, legal obligation or other lawful exception limits the request. If you remain dissatisfied after giving us a reasonable opportunity to respond, you may be entitled to contact the Office of the Australian Information Commissioner.

How information is held and protected

Reading information is held in local app storage. Purchase information is held by the applicable store and RevenueCat, and support messages are held by our email service. We use reasonable technical and organisational safeguards, restrict information handling to the purposes above and avoid collecting information the app does not need. No internet or storage system can be guaranteed completely secure.

Children and sensitive content

History Wake is not directed to children. Its historical stories may include disaster, conflict, violence and mature themes. We do not knowingly collect a child's name, contact details or other directly identifying information.

Policy changes

Material changes will be posted on this page with a new effective date. We review the policy when History Wake changes its data practices or service providers.

Publisher and privacy contact

Publisher: Ken Eric Chalk trading as History Wake

ABN: 43 949 110 407

Country: Australia

Effective date: 27 August 2026

Privacy contact: chalkken94@gmail.com