Pink Reading · Last updated 2026-09-25

Privacy Policy

Short version

Pink Reading does not collect, store, or transmit any personal data. The app runs fully on your device. There are no accounts, no analytics, and no third-party SDKs that contact a server. Pink Reading is free, sells nothing, and has no servers of its own.

Who we are

Pink Reading is published by Danielius Studio LLC, a Wyoming limited liability company at 30 N Gould St, Suite #5280, Sheridan, WY 82801, USA (“we”, “us”).

Data we do NOT collect

No account, no email, no password — the app has no signup.
No analytics, no telemetry, no event tracking.
No advertising identifiers (no IDFA, no fingerprinting).
No usage data sent off the device.
No microphone, no camera, no photos. Text you type stays on your device.
No location, no contacts, no calendar. The app does not request any sensitive iOS permission.

What stays on your device

Your books (title, and whether you finished them) and reading sessions (minutes and date). They live in on-device SwiftData until you delete them. Nothing leaves the device.
The date the app was first launched. Stored in UserDefaults.
Whether you have seen the intro cards.

All of the above lives in SwiftData and UserDefaults on your device and never leaves it. Uninstalling the app deletes it.

In-app purchases

Pink Reading is free. It has no subscriptions and no in-app purchases, so there is no payment data of any kind.

Children

Pink Reading is rated 4+ in the App Store. Because the app collects no data at all, it complies with COPPA and similar children's-privacy regulations by design.

Your rights

Because Pink Reading does not collect data, there is nothing for us to export, correct, or delete on your behalf. To revoke all access and remove all on-device state, simply delete the app.

For questions, write to privacy@danielius.studio.

Changes

If we ever introduce a feature that involves any data leaving the device (for example, cloud sync), this page will be updated and the “Last updated” date at the top will change. For v1.0, no such feature exists.