Rune Writer

Privacy Policy

Last updated:

Your words stay yours.

Rune Writer is a small, private writing tool developed by Keegan Rush. This policy covers the Rune Writer iPhone app and Rune Writer Keyboard.

Writing stays on your iPhone

Text conversion happens on your device and works offline. Rune Writer does not upload your writing or send your text or keyboard input to the developer.

The app has no account, advertising, tracking, or third-party analytics. It does not collect personal information for transmission to the developer. Information saved on your device is used only to provide the app’s features, as described below.

History is yours to keep

Copying a conversion, completing a share, or tapping Save adds that conversion to local history. A saved entry contains your source text, converted result, selected alphabet, and the date and time it was saved.

Rune Writer keeps up to 50 entries on your iPhone, with newer entries replacing the oldest when the limit is reached. The app does not save every keystroke or intermediate edit, sync history between devices, or share history with the keyboard.

Keyboard privacy

The keyboard can’t access the Internet and can’t collect, save, or log what you type. It can read settings from the main app.

The app you type into receives the inserted text and handles it under its own privacy practices.

You choose what to share

Copy, share, and image export happen when you choose them. Copy places the selected result on the system clipboard. Sharing sends the text or image to the apps or people you select using the iOS share sheet.

Exported images are saved to Photos only when you choose Save Image. An image can include your source text if you leave that option enabled. Rune Writer does not upload exported images to the developer.

Rune Writer does not share your writing with analytics providers, advertisers, or other service providers on the developer’s behalf. Content you choose to send to another app or person is handled by that recipient; review their privacy practices before sharing sensitive information.

Purchases go through Apple

Apple handles payments and purchase restoration. Rune Writer uses Apple’s purchase status to enable purchased features. The developer does not receive your payment card details through the app.

Apple’s handling of purchase information is described in the Apple Privacy Policy.

Retention, deletion, and your choices

  • Saved history: Entries remain on your device until you delete them, they are replaced by newer entries at the 50-entry limit, or you delete the app’s local data.
  • Delete local data: You can remove local history by deleting Rune Writer from your iPhone. Choose Delete App rather than Offload App, which preserves app data.
  • Keyboard: You can stop using the keyboard or remove it in iOS Settings under General → Keyboard → Keyboards.
  • Shared content: Delete exported images in Photos or wherever you saved them. Deleting history or the app does not delete content already copied, shared, or saved elsewhere.

Rune Writer does not provide cloud sync, but your device’s backup settings may include local app data in an iCloud or computer backup. Copies in backups are managed separately through Apple’s backup controls. See Apple’s instructions for managing iCloud backups.

The developer has no remote copy of your local history or keyboard input and cannot retrieve or delete it remotely. You can stop sharing at any time by declining to copy, share, or export content, and manage any system permissions in iOS Settings.

Contact

For privacy questions or requests, contact Keegan Rush at thecodedself+runewriter@gmail.com.

If you email the developer, your email address and any information you choose to include are used to respond to your request. Correspondence is retained only as long as needed to handle the request or meet applicable legal obligations. You can use the same address to request deletion of that correspondence. Please avoid sending sensitive writing or keyboard input.

Changes to this policy

If Rune Writer’s privacy practices change, this policy will be updated and the date above will reflect the latest revision.