Skip to content
gen2apps
AppsServicesWritingSupport
Start a project
AppsServicesWritingSupport
Legal

Privacy Policy

Last updated: November 15, 2026

gen2apps ("we", "us") builds focused apps for iOS, Android and the web. We design every app to be privacy-respecting: no ads, no advertising trackers, and we never sell your data. This policy explains what we collect and why. It applies to KeepUp, Scour and our other apps and to this website. KeepUp's and Scour's app data handling and this website's own measurement are described in separate sections below.

The short version

  • KeepUp stores your habit database on your device. On iOS, eligible data may also synchronize through your private iCloud account. On Android, the habit database is local; Android's backup can hold a separate copy in your Google Account if enabled. The Android app does not upload the habit database to our servers.
  • KeepUp reads selected Apple Health metrics to evaluate habit goals. Derived completion history and copies from earlier versions are described under Apple Health below.
  • KeepUp uses limited, pseudonymous product analytics. Installation and subscription identifiers can link records; this is not anonymous data.

Data you create (habits & activity)

KeepUp stores habits, activity, notes, moods, reminders and settings in the app's database. On iOS, when the app starts with Premium enabled and iCloud is available, eligible data may synchronize through your private iCloud account using Apple CloudKit. Exports, shared images, widgets and paired Apple Watch features can hold separate copies of app data.

Apple Health

If you link a KeepUp habit to Apple Health, the app reads the metric you choose, such as steps, exercise time, mindful time, active energy or sleep, to evaluate that habit's goal. KeepUp does not write anything to Apple Health, and raw Health readings are not sent to us.

From version 2.7, habits that Health completes are recorded in a file on your device rather than in the app's iCloud-synced database, and no Health-related event is sent to our analytics. Versions before 2.7 recorded those completions in the app's database, which synchronizes through iCloud when that is on, and sent an event when a habit was linked to Health or completed by it. In every version, the widget and a paired Apple Watch show these completions, and exports or images you choose to share can include them. Updating the app does not by itself remove copies already synced or events already sent.

Purchases & subscriptions

Purchases and subscriptions are processed entirely by Apple, using Apple's own StoreKit, or on Android by Google Play. Whether you have Pro is decided on your device from Apple's or Google's own record of your purchase.

Apple tells our server when a subscription starts, renews, lapses or is refunded, so we can count active subscriptions, renewals and refunds. The app itself checks your purchase with Apple on your device. What Apple sends us includes the transaction identifiers it generated, the product, the purchase, renewal and expiry dates, whether the subscription is set to renew, the storefront country, the price and the currency. It does not include your name, your email, your Apple ID or any payment details — Apple never shares those with us.

RevenueCat

We use RevenueCat (RevenueCat, Inc.) as a service provider to measure purchases in KeepUp, StepKit, Scour and WeightKit. RevenueCat only observes purchases: you still buy through Apple or Google, and RevenueCat does not decide whether you have Pro. Since October 14, 2026, Apple's notifications about these apps' purchases go to RevenueCat first, which passes them on to our server unchanged. In app versions that include RevenueCat's software kit, the app also contacts RevenueCat when it starts and after a purchase, using the same installation identifier as our own analytics.

RevenueCat receives that installation identifier, the products bought, the transaction identifiers Apple or Google generated (on Android, Google's purchase token), the purchase, renewal and expiry dates, the price, currency and storefront country, and the technical details its software kit sends, such as the app and operating system versions, the device model, the language and the IP address a request comes from. It does not receive your name, your email, your Apple Account or Google Account, payment details, or anything you create in the apps. RevenueCat processes this data on our behalf; its own policy is at revenuecat.com/privacy.

KeepUp product analytics

KeepUp sends product interaction events to our backend hosted on Google Cloud/Firebase and Cloudflare. Current event handling and analytics storage use Cloudflare Workers and D1; older Firebase copies may remain. Events describe app opens, onboarding, purchase screens, feature use, notification taps, sharing, completing a habit: that a habit reached its goal that day, never which habit, its name or its goal, and never for a habit linked to Apple Health; and saving a mood: at most once a day, where in the app it was saved and whether a note came with it, never the mood itself or anything written in the note. They include an installation identifier, event and screen information, app/build and OS versions, device model, and, when available, App Store storefront and device region. We also receive the app's reported Premium status and a known Apple original transaction identifier for subscription history.

The installation identifier is generated and retained locally, but is also sent with events and stored on our backend. These records are pseudonymous, not anonymous. An original transaction identifier can associate installation records with subscription history. Reinstalling the app does not erase records already held on our servers.

From version 2.8.1, when a purchase or a restore does not go through, the purchase or restore event also carries technical diagnostics so we can find out why: which ways of asking Apple's purchase system were tried, what each returned and how long it took, whether a system screen covered the app, the type and code of any error (never its message), how many app windows were open and whether the app was active, the iPhone model (such as "iPhone12,8", never the name you gave your phone), whether purchases are allowed on the device, which App Store environment the app was talking to, the renewal state of any KeepUp subscription on the Apple Account, and any lines Apple's purchase system wrote in the app's own log, reduced to letters and punctuation, with every number removed except an error code and with any address, link or identifier taken out. They never include payment details, your Apple Account or anything you typed.

KeepUp uses its own event client rather than a third-party analytics SDK. The events are processed on Google Cloud/Firebase and Cloudflare as our hosting providers and are not shared with any analytics or advertising company. Purchase records and the installation identifier are also processed by RevenueCat, as described under Purchases above.

KeepUp for Android

KeepUp for Android stores your habits, activity, notes, moods, reminders and settings in its local database on your phone. The app does not upload that database to our servers: this includes the habit names and descriptions you type, your notes, mood values, custom goals and detailed activity records. There is no KeepUp account or KeepUp cloud sync on Android. Android's own backup, if enabled, can hold a separate copy in your Google Account and carry the database to a new phone; that is your backup, not a database held by gen2apps. The backup file you export from Settings goes wherever you choose to save it.

If you link a habit to Health Connect, KeepUp reads the metric you choose (steps, exercise, active energy or sleep) to see whether that habit's goal is met. It never writes to Health Connect. Health Connect readings are processed on your phone. The completion records derived from them are kept in a separate local file excluded from Android backups and exports. Raw Health Connect readings are not part of the app's analytics payload. Dedicated Health-link and Health-completion events are filtered out. However, app-wide milestones, such as a day when all habits are complete, can be calculated using these local Health completions. If such a milestone is reached, its analytics event can contain the milestone type and threshold, along with the technical and installation data described below. It does not contain the raw Health readings or identify the habit or Health metric.

Separate product analytics: the Android app sends product-interaction events with an installation identifier generated on the phone, event and screen information, timestamps, the app's version and build, Android version, phone model and maker, platform, device region, Google Play billing country and reported Pro status. A manual habit-completion event says that a goal was reached that day; it does not include the habit's name or identifier, its goal or its count. Habits linked to Health Connect, including those with earlier Health history, are excluded from these direct completion events. Onboarding analytics can include the code of a predefined habit template selected from the app, or a generic marker such as custom, existing or quit; it does not include a name you typed or identify what you are quitting. Mood-logging events describe where the mood was saved and whether a note was included, not the mood value or note text. Milestone analytics can include the achievement type and threshold as explained above. These analytics records are separate from the private habit database on your phone.

Separate purchase records: KeepUp Pro on Android is bought through Google Play. To confirm a purchase, the app sends Google's purchase token for it to our server, which checks it with Google; Google also tells our server when a subscription starts, renews, is cancelled, expires or is refunded. We receive the product, its dates and state and Google's order number, never your payment details or your Google Account. RevenueCat receives the purchase token and the installation identifier as described under Purchases above.

KeepUp for Android: data retention and deletion

On your phone: your habits, activity, notes, moods, reminders and settings remain in KeepUp's local storage until you remove them or clear the app's storage. Deleting a habit removes its activity history and reminders, but earned milestone cards can retain the habit's name. To remove all KeepUp data on the phone, use your Android device's app-storage settings to clear KeepUp's storage. Copies in Android backups, exported backup files or images you have shared are separate: manage or delete them through the backup service or wherever you saved or shared them. We cannot erase copies in your own accounts or files. Clearing KeepUp does not erase the source data in Health Connect or cancel a Google Play subscription.

Server-held records: we currently keep product-analytics events, installation summaries and purchase-history records without a fixed automatic expiry. They are retained to understand app use, diagnose problems and maintain purchase, renewal and refund history. These records can exist in Cloudflare D1, older Google Cloud/Firebase copies and, for purchases, RevenueCat as described above. This does not mean that we hold a copy of your private Android habit database; its contents and your own backups have the separate lifecycle described above. Removing or reinstalling the app does not automatically erase the server-held analytics and purchase records.

How to request deletion: email [email protected] with the subject “KeepUp Android data deletion”. To include your installation identifier, open KeepUp Settings → Send Feedback, change the recipient to [email protected] and the subject to the same title, and send the email from your mail app. Do this before clearing or uninstalling KeepUp if possible: the prepared email includes the installation identifier we need to find that installation's records. Tell us that you use Android and what you want deleted. If you have already reinstalled, include any earlier installation identifiers you kept; a new installation has a different identifier. Do not include your habit or Health data, passwords or purchase tokens.

We review deletion requests manually. We may ask for the information needed to locate the records and verify the request. We will explain what we deleted and any records retained, and why. Our review includes records processed for us by RevenueCat where relevant; deleting only our analytics does not itself delete RevenueCat's records. Purchase records and subscriptions are separate from analytics: a deletion request does not cancel your subscription, and Apple, Google and other providers may retain records under their own policies. If you continue using KeepUp or make or restore a purchase after deletion, new usage or purchase records can be created; subscription lifecycle notifications can also create new purchase records.

Recovery copies and technical logs: removing an active record does not immediately remove provider recovery copies or logs. Cloudflare D1's recovery history can retain earlier versions for up to 30 days, as described in its Time Travel documentation. Our standard Google Cloud log bucket is configured for 30 days and its required audit-log bucket for 400 days. Other provider operational records follow the applicable service policies. These recovery and log periods are separate from the active analytics and purchase records described above.

Scour

Scour reads your photo library on your iPhone. Photos, thumbnails, the text Scour recognises and anything it finds in them never leave the device, and neither does which kind of sensitive data was found.

Scour sends product interaction events to the same backend: app opens, that a scan started or finished, that photos were deleted (as a count), and the purchase screen (shown, closed, a purchase tapped, completed, cancelled, waiting for approval or failed, and restores). Library size is rounded to a band before it is sent. Events include an installation identifier generated on the device, the app's version and build, the iOS version, the device family (such as "iPhone", never the exact model or its name) and the App Store storefront country. From the version after 1.1.0 they also include whether Scour Pro is active on the install and, when Pro was bought, Apple's original transaction identifier for that purchase. Scour Pro is a one-time purchase processed by Apple; Apple tells our server about the purchase and any refund, as described under Purchases above, and the original transaction identifier lets us connect that record to the install. RevenueCat also receives the purchase and the installation identifier, as described under Purchases above; it never sees your photos or what Scour found. These records are pseudonymous, not anonymous.

StepKit

StepKit keeps your steps, walks, walk routes, goals and Apple Health data on your iPhone and Apple Watch; none of it is sent to us.

StepKit sends product interaction events to the same backend: app opens, that onboarding was finished, the StepKit Pro screen (shown, closed, a plan tapped, a purchase completed, cancelled, waiting for approval or failed, the one-time option opened, and restores) and that a share sheet was opened. From version 1.0.3, StepKit's widgets also send one event a day saying that a StepKit widget is on your screen and was refreshed that day; it does not say which widget or whether you looked at it, and it never includes your steps. From version 1.0.6, StepKit also sends an event when a walk is saved, saying only whether it has a route and roughly how long it was (under 10 minutes, 10 to 30, 30 to 60 or over an hour), never where you walked, the route, its distance or your steps; an event when the App Store purchase sheet appears while you buy StepKit Pro; and an event when you tap a Pro card on the Today screen, saying only which card (trends or records), never what it showed. From version 1.0.7, StepKit also sends an event when you switch Today between Day, Week and Month, saying only which two; when you move to another day, week or month, saying only how (swipe, arrows, the week row or History), which of the three, and roughly how far back (0, 1, 2 to 6, 7 to 27, or 28 and more), never a date or your steps; when you open a day from a week bar, a month cell, History or the year heatmap, saying only which of them; and when you reach the end of the 16 weeks of history in the free app and tap the lock. The event for opening a share sheet now also says which style of card it opened on (such as ring, hours or calendar), never what the card shows. Pro cards and reports (the 3D replay, strongest weekdays, month-end forecast, consistency, walk insights, a year ago and the monthly report) report the same way when tapped, saying only which one and whether it was on Today or in History, and sharing the monthly report counts as a share sheet being opened. Events include an installation identifier generated on the device, the app's version and build, the iOS version, the iPhone model (such as "iPhone12,3", never the name you gave your phone; before version 1.0.3 only the device family, such as "iPhone") and the App Store storefront country. From version 1.0.2 they also include whether StepKit Pro is active on the install and, once known, Apple's original transaction identifier for the Pro purchase. StepKit Pro is a subscription or a one-time purchase processed by Apple; Apple tells our server about it as described under Purchases above, and the original transaction identifier lets us connect that record to the install. RevenueCat also receives the purchase and the installation identifier, as described under Purchases above. These records are pseudonymous, not anonymous. They never include payment details or your Apple Account.

StepKit for Android

StepKit for Android keeps the same promise: your steps, walks, walk routes and goals stay on your phone. Steps come from your phone's step sensor, which needs Android's Physical activity permission. If you turn on Health Connect sync, StepKit reads your steps and walking distance from Health Connect, including days from before you installed it, so your history starts there. It never writes to Health Connect, and what it reads never leaves your phone.

A walk's route uses your phone's location only while a walk you started is running, and only if you allowed Location. Maps are drawn with OpenFreeMap tiles made from OpenStreetMap data: like any map, the tile server sees your IP address and which area of the map your phone loads, not your route or your steps.

The Android app sends the same product interaction events as the iPhone app (above), from the app and once a day from its widgets, with an installation identifier generated on the phone, the app's version and build, the Android version, the phone's model and maker (such as "Pixel 8" and "Google"), that it is Android, and the Google Play billing country. StepKit Pro on Android is bought through Google Play. To confirm a purchase, the app sends Google's purchase token for it to our server, which checks it with Google; Google also tells our server when a subscription renews, is cancelled, expires or is refunded. We receive the product, its dates and state and Google's order number, never your payment details or your Google Account. RevenueCat receives the purchase token and the installation identifier as described under Purchases above.

WeightKit

WeightKit keeps the weights you log, their dates and notes, the body measurements you log (waist, hips, chest, upper arm and thigh), your goal and the details you give it (height, year of birth, sex and activity level) in the app's database on your iPhone; none of it is sent to us. With iCloud sync on, which is the default and can be turned off in Settings, that database also synchronizes through your private iCloud account using Apple CloudKit, so it can follow you to a new iPhone or come back after a reinstall. We cannot read your private iCloud data. The widgets and a paired Apple Watch hold a copy of the last 30 days, passed directly between your own devices, and a weigh-in entered on the watch goes to your iPhone the same way.

If you turn on Apple Health, WeightKit reads your weight history, height, date of birth and sex to fill in your details and bring in past weigh-ins, including ones a smart scale saved to Health, and it saves the weights you log in WeightKit to Health. Reading and saving can be switched off separately. The waist has its own permission, asked only if you turn on waist sync on the Apple Health page in Settings: WeightKit then reads your waist circumference from Health and saves the waist measurements you log there. What WeightKit reads from Health stays on your devices and is never sent to us.

WeightKit sends product interaction events to the same backend as our other apps: app opens, which onboarding steps were reached and that onboarding was finished, that the weigh-in screen was opened and from where (the app, a widget or a reminder), that the measurements screen was opened and from where, how many of the five measurements were saved at once (never their values), that the measurements suggestion was hidden, that waist sharing with Health was turned on or off, the WeightKit Pro screen (where it was opened from, shown, closed, a purchase started, completed, cancelled, waiting for approval or failed, and restores) and which locked Pro card was tapped. Events include an installation identifier generated on the device, the app's version and build, the iOS version, the iPhone model and the App Store storefront country, and whether WeightKit Pro is active on the install with, once known, Apple's original transaction identifier for the Pro purchase. WeightKit Pro is a subscription processed by Apple; Apple tells our server about it as described under Purchases above. RevenueCat also receives the purchase and the installation identifier, as described under Purchases above; it never sees your weights or anything from Apple Health. Events never include your weights, measurements, notes, goal, details or anything from Apple Health. These records are pseudonymous, not anonymous. The reminder before a free trial ends is a notification scheduled on your iPhone; nothing about it is sent to us.

WeightKit for Android

WeightKit for Android keeps the weights you log, their dates and notes, the body measurements you log (waist, hips, chest, upper arm and thigh), your goal and the details you give it (height, year of birth, sex and activity level) in the app's database on your phone; none of it is sent to us. There is no WeightKit account and no cloud sync. Android's own backup (to your Google Account, if you have it on) can carry the app's database to a new phone, and a JSON backup you export or an image you share goes only where you choose.

If you allow Health Connect, WeightKit reads your height and your weight records, including history from before you installed it where your phone supports it and you allow it, and saves the weights you log in WeightKit to Health Connect. These permissions are optional and you can revoke them in Health Connect at any time. What WeightKit reads from Health Connect stays on your phone and is never sent to us. Deleting an entry in WeightKit removes only WeightKit's own records from Health Connect.

Widgets show your weight only if you turn that on for each widget. A paired Wear OS watch exchanges recent entries with your phone directly through Google Play services; weigh-ins entered on the watch go to your phone, which saves them.

The Android app sends the same kind of product interaction events as the iPhone app (above): app opens, onboarding steps reached and finished, the weigh-in screen opened, the measurements screen opened, how many measurements were saved at once (never their values), the measurements suggestion hidden, the WeightKit Pro screen (shown, closed, a plan tapped, purchase outcome, restore), which locked Pro feature was tapped and that a share sheet was opened. Events include an installation identifier generated on the phone, the app's version and build, the Android version, the phone model, that it is Android, and whether Pro is active. They never include your weights, measurements, notes, goal, details or anything from Health Connect. These records are pseudonymous, not anonymous.

WeightKit Pro on Android is a subscription bought through Google Play. To confirm a purchase, the app sends the product, Google's purchase token and the installation identifier to our server, which checks it with Google; Google also tells our server when a subscription renews, is cancelled, expires or is refunded. We never receive your payment details or your Google Account. RevenueCat receives the purchase token and the installation identifier as described under Purchases above. WeightKit does not use the advertising ID.

To ask us to delete server-held analytics or purchase records for your installation, email [email protected]. Uninstalling the app deletes the data on your phone.

Website analytics

This website counts visits with Cloudflare Web Analytics, a script served by Cloudflare, which already delivers the site. It writes no cookies and stores nothing on your device. It reports page views and page-load performance by page, referring site, country, browser and device type, and it does not recognise you between visits or build a profile of you.

When you follow a link from this site to the App Store, it passes through gen2apps.com/go/… on our own server, which counts the click before sending you on. The count records which app and the language of the page you came from, and nothing else about you.

Earlier in September 2026 the site used Google Analytics in a cookie-free mode; it has been removed. If we ever move to cookie-based measurement, this page will say so and the site will ask for your consent first. You can block the measurement script with any content blocker; the site works the same either way.

Feature requests

KeepUp versions before 2.7 have a suggestion screen. When you submit a suggestion there, we store its text, app, device identifier and submission time. The feature-request identifier is separate from the analytics installation identifier: Apple's vendor identifier is used when available, with a locally generated fallback. It supports submission limits and vote deduplication. Suggestions are read by us and are not shown to other users. Please do not include sensitive habit, Health or personal information in a suggestion.

Contacting us

If you use the contact form on this website, we store the message, the email address you give us so we can reply, your name if you provide one, and which app the message is about. We also keep the browser's user-agent string and a one-way hash of your IP address — the hash exists to rate-limit the form, and the address itself is never stored. Messages are kept so support requests can be answered and looked up later; email us to have one deleted.

KeepUp's "Send Feedback" option opens an email in your own mail app, addressed to us and ready for you to edit or discard. Nothing is sent unless you send it. Below your message it lists the iOS or Android version, device model, KeepUp version and build, whether you have Pro, your App Store or Google Play billing country when available, and the app's installation identifier, so we can match the report to the app's diagnostics. It never includes your habits or notes. We receive your email address because the message comes from it, and we keep feedback emails only to answer and follow up on them; email us to have one deleted.

Newsletter ("the drop list")

If you subscribe to our newsletter from this website, we collect the email address you provide, along with the fact that you signed up from gen2apps.com, so we can send you occasional updates about new apps and major releases. We use this address for that purpose only — not for advertising, and not shared with other companies for their own marketing. Your address is stored in our own database, on infrastructure we control, and is shared with an email delivery provider only at the moment we actually send a newsletter. Every email includes a one-click unsubscribe link, or you can email [email protected] to be removed.

What we do not do

  • We do not sell or rent your personal data.
  • We do not include third-party advertising or ad-tracking SDKs anywhere. Our apps' product analytics, RevenueCat's purchase measurement and the website's measurement are described separately above.
  • KeepUp's habit database is separate from its analytics and feature-request services. Text you explicitly submit as a suggestion is sent to our servers.

Your choices

  • Health: revoke access anytime in iOS Settings → Privacy & Security → Health.
  • Health Connect: revoke access anytime in Health Connect settings.
  • iCloud sync: turn it off in your device's iCloud settings.
  • KeepUp export / delete: you can export app data. Local data, iCloud copies, subscriptions and server-held records have separate lifecycles. Deleting or reinstalling the app does not automatically delete server-held analytics or subscription records, or cancel a subscription. For KeepUp Android deletion requests, follow the instructions in the retention and deletion section above; email [email protected].
  • Website analytics: nothing is stored on your device to turn off; any content blocker stops the page-view script. The App Store click count happens on our server when you follow the link.

Children

Our apps are not directed to children under 13, and we do not knowingly collect personal information from them.

Changes

We may update this policy as our apps evolve. Material changes will be reflected here with a new "Last updated" date.

Contact

Questions? Email [email protected].

This policy is provided for transparency and may be updated as features change. For specific legal questions, please reach out.

gen2apps

A small indie studio shipping focused apps for iOS. Crafted with care, one at a time.

Apps

  • KeepUp
  • Scour
  • StepKit
  • pingrobot
  • All apps →

Studio

  • About
  • Manifesto
  • Writing
  • Support
  • Privacy
  • Terms
  • [email protected]
© 2026 gen2apps.com — All rights reserved Built with care