ruffup Privacy Policy

Last updated: 2026-09-07

This is the privacy policy for ruffup, an iOS alarm app. It explains what data the app collects, where it goes, and what choices you have.

The short version: Onboarding answers, alarms, streaks, and mission results stay on your device. What leaves your phone: your subscription state (to confirm you’re a paying subscriber), basic usage and crash analytics (to understand how the app is used and to fix bugs), and a few app events we share with AppsFlyer and TikTok to measure our own ads. If you allow tracking when iOS asks, your device’s advertising identifier is used for that ad measurement too; if you decline, ad measurement stays aggregated and anonymous. None of it is tied to your name, email, or any account, and we never sell it.

1. What stays on your device

The following is stored only in the local SwiftData store on your iPhone and is never transmitted to ruffup or any third party by us:

• Alarm schedules (time, weekdays, mission, sound)
• Onboarding answers (wake time, difficulty rating, pain points, mission preferences, goal)
• Streak history and mission results
• Camera images captured during fetch missions (used in-memory only — the image is analyzed by Apple’s on-device Vision framework and then discarded; nothing is uploaded)
• App preferences (theme, disabled missions, etc.)

If you delete the app, this data is removed with it.

2. Subscription data (RevenueCat + Apple)

To gate paid features we use RevenueCat (https://www.revenuecat.com/), which wraps Apple’s StoreKit framework. When you open the paywall or complete a purchase, the following is processed:

• An anonymous, random user identifier generated by the RevenueCat SDK. It is not tied to your name, email, Apple ID, or any account.
• Subscription status — which subscription package you bought, when it was purchased, when it renews or expires, and whether your trial converted.
• Device + locale info Apple sends with every StoreKit transaction (App Store country, iOS version, app version).

This is sent to RevenueCat’s servers so the app can confirm your entitlement on subsequent launches without you needing to sign in. RevenueCat’s privacy policy is at https://www.revenuecat.com/privacy.

We do not associate this data with your name, email, or Apple ID, and we never sell it. Some anonymous purchase events (for example, that a trial or a subscription started) are also shared with the analytics and advertising-measurement partners described in Section 3, only so we can understand and measure our own marketing.

3. Usage analytics, crash reports, and advertising measurement

To understand how the app is used, fix bugs, and measure our own advertising, ruffup sends a small amount of event data off the device. None of it is tied to your name, email, Apple ID, or any account, we do not show third-party ads inside the app, and we never sell it. The only identifier involved beyond the random one from Section 2 is the device advertising identifier, and only if you allow tracking when iOS asks (see the AppsFlyer entry below).

PostHog (product analytics + crash reports). We use PostHog (https://posthog.com/) to record anonymous in-app events, such as which onboarding steps you reach, when an alarm is created, when a wake mission is completed, when the paywall is shown, and when a trial or subscription starts. If you use Send feedback in Settings, the text you type is sent to PostHog as one of these events; it is only collected when you choose to send it, and you should avoid including personal details in it. In release builds, PostHog also automatically captures crash and error reports so we can find and fix problems. These events are keyed to the same anonymous, random identifier described in Section 2 and are processed on PostHog’s US servers (us.i.posthog.com). PostHog’s privacy policy is at https://posthog.com/privacy.

Bug reports (email). If you use Report a bug in Settings, the app opens your own Mail app with a message addressed to support@ruffup.app. The message includes a small diagnostics file (app and iOS version, device model, locale and time zone, your anonymous RevenueCat identifier, subscription and onboarding state, which test groups the app assigned you to, your alarm schedules, permission states, and recent mission results) so we can find the problem. Nothing is sent until you tap Send in Mail, and you can remove the attachment or any part of the message before sending. We use the email only to reply to you and fix the bug, keep it in our support inbox, and delete it on request.

AppsFlyer (advertising measurement and attribution). We use AppsFlyer (https://www.appsflyer.com/), a mobile measurement partner, to understand which of our own ads bring people to ruffup. When you first open the app, iOS shows the standard App Tracking Transparency prompt. If you tap Allow, AppsFlyer receives your device’s advertising identifier (IDFA) and uses it to match your install to the ad you tapped. If you decline, no IDFA is collected and measurement falls back to aggregated, privacy-preserving methods (Apple’s SKAdNetwork and AppsFlyer’s modeled estimates). Either way, AppsFlyer receives a small set of app events (first open, completing onboarding, creating an alarm, completing a wake mission, viewing the paywall, and the anonymous trial and subscription events described in Section 2), keyed to the same random identifier from Section 2, and forwards conversion signals to the ad network the install came from (currently TikTok) so ad delivery can improve. AppsFlyer’s privacy policy is at https://www.appsflyer.com/legal/services-privacy-policy/.

TikTok (advertising measurement). ruffup does not include any TikTok software. If you install ruffup after tapping one of our TikTok ads, TikTok learns about the install and the conversion events described above in two ways: the conversion signals AppsFlyer forwards on our behalf, and Apple’s privacy-preserving SKAdNetwork aggregated reporting. TikTok’s privacy policy is at https://www.tiktok.com/legal/page/row/privacy-policy/en.

4. Notification permission

If you allow notifications, the app uses AlarmKit (iOS 26+) or UserNotifications (older iOS) to schedule local alarm notifications on your device. These never leave your phone. If you decline, the app still works but your alarms will not fire while it’s in the background.

5. Permissions

ruffup may ask for:

• Notifications — required for alarms to fire.
• Camera — required if you choose a camera-based wake mission (e.g., “fetch the sink”). Used in-memory only.
• Tracking (optional): lets us match your install to one of our own ads using the device advertising identifier, as described in Section 3. Declining changes nothing about how the app works.

You can revoke any of these at any time in iOS Settings → ruffup.

6. Children

ruffup is not directed at children under 13 and does not knowingly collect data from them.

7. Your rights

You can:

• See what’s stored about you. Onboarding answers, alarms, streaks, and mission results live only on your device — you already have direct access via the app. For your subscription record at RevenueCat, or your anonymous analytics events and any feedback text at PostHog, you can request a copy by emailing support@ruffup.app.
• Delete your data. Removing the app removes everything stored on-device. To also remove your anonymous subscription record from RevenueCat, your anonymous analytics, crash, and feedback events from PostHog, your attribution record from AppsFlyer, or any bug-report email you sent us, email support@ruffup.app and we’ll request deletion on your behalf. Advertising-measurement signals shared with TikTok through Apple’s SKAdNetwork are aggregated and anonymous, so they cannot be tied back to you to delete individually.
• Correct your data. If something we hold is wrong, email support@ruffup.app.
• Object to or restrict processing. Stop using the app and we’ll cease all processing related to you.
• Port your data. Where required by law, we can provide a copy of your subscription data in a structured, machine-readable format.
• Withdraw consent. Revoke notification or camera permissions at any time in iOS Settings → ruffup.

We respond to verified rights requests within 30 days.

8. Legal basis for processing (EU / UK users)

Where the General Data Protection Regulation (GDPR) or UK GDPR applies, our legal bases for processing are:

• Subscription processing — performance of a contract (Article 6(1)(b)). The subscription record is necessary to provide the paid features you bought.
• Receipt validation and anti-fraud — legitimate interests (Article 6(1)(f)). Ensuring purchases are real and entitlements are correctly assigned.
• Usage analytics, crash reporting, and advertising measurement — legitimate interests (Article 6(1)(f)). Understanding how the app is used, fixing bugs, and measuring the effectiveness of our own advertising, using anonymous data that is not linked to your identity. You can object at any time by emailing support@ruffup.app.
• Ad attribution using the device advertising identifier (IDFA): your consent (Article 6(1)(a)), given through the iOS tracking prompt. You can withdraw it at any time in iOS Settings → Privacy & Security → Tracking.
• Notifications and camera access — your consent (Article 6(1)(a)). You can withdraw consent at any time in iOS Settings.

We do not make automated decisions that produce legal or similarly significant effects about you.

9. Data retention

• On-device data is retained for as long as the app is installed. Deleting the app deletes the data.
• RevenueCat subscription records are retained per RevenueCat’s retention policy (typically up to 7 years for purchase records, to satisfy tax, chargeback, and audit retention windows). You can request earlier deletion via the rights process in section 7.
• Analytics and crash data at PostHog are retained per PostHog’s retention settings and deleted on request via the process in section 7. Advertising-measurement signals processed through Apple’s SKAdNetwork are aggregated and time-limited by Apple.
• Attribution data at AppsFlyer is retained per AppsFlyer’s retention policy and deleted on request via the process in section 7.

10. International data transfers

ruffup is operated from outside the European Union. RevenueCat, PostHog, AppsFlyer, and TikTok are all based in the United States. When you purchase a subscription, your anonymous purchase record is transferred to and processed in the US by RevenueCat; the analytics, crash, and advertising-measurement events described in section 3 are likewise transferred to and processed in the US by PostHog, AppsFlyer, and TikTok. Each relies on Standard Contractual Clauses (SCCs) approved by the European Commission as the legal mechanism for these transfers. RevenueCat’s Data Processing Agreement and SCCs are available at https://www.revenuecat.com/legal/, PostHog’s at https://posthog.com/dpa, AppsFlyer’s at https://www.appsflyer.com/legal/dpa/, and TikTok’s business-products terms at https://www.tiktok.com/legal/.

11. Supervisory authority

If you are in the EU, UK, or EEA, you have the right to lodge a complaint with your national data protection authority. Contact details for EU/EEA authorities are at https://edpb.europa.eu/about-edpb/about-edpb/members_en and for the UK at https://ico.org.uk.

12. Data controller (EU / UK users)

For the purposes of the GDPR and UK GDPR, the data controller is:

Justin Lim (sole proprietor) — 8809 Washington Blvd, Unit 322, Culver City, CA, 90232, United States — email support@ruffup.app.

This address is also published on our App Store listing under the Digital Services Act.

13. Changes

If we materially change how data is handled, we’ll update this page and the “Last updated” date above.

14. Contact

Questions? Email support@ruffup.app.