Pink Rest · Last updated 2026-05-24

Privacy Policy

Short version

Pink Rest 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. The only network calls the app makes are to Apple's StoreKit when you choose to subscribe or unlock the Lifetime tier.

Who we are

Pink Rest 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

What stays on your device

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

In-app purchases

If you choose to subscribe (Monthly, Annual) or buy the Lifetime unlock, that transaction is handled by Apple's StoreKit. Apple processes the payment and shares only the receipt with the app so we can verify your entitlement. We never see your card number, billing address, or any personal information beyond Apple's opaque transaction identifier.

Subscription receipts are stored on-device by iOS and used to validate your entitlement when you re-open the app. They are not sent to any server we operate.

Family Sharing

Pink Rest Pro purchases (Monthly, Annual, Lifetime) are Family-Shareable through Apple's standard Family Sharing mechanism. Apple handles eligibility checks; we do not see who is in your family group.

Children

Pink Rest 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 Rest 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.