OurBeom
SIMTA Privacy Policy
2026-09-21
English
This is an archived version. See the current policy
SIMTA is a timer app for iOS, published by OurBeom (아워범), a business
registered in the Republic of Korea. This policy explains what the app collects,
why, and what you can do about it. It covers the iOS app only (App Store ID
6477752878, bundle ID im.oh3vci.--PRODUCT-NAME-rfc1034identifier-), not the
OurBeom website.
The app has no accounts and no sign-in. From version 1.3.0 it includes advertising and a one-time in-app purchase. If you are on 1.2.1 or earlier, sections 1-2 and 1-3 do not apply to you. Each section states which version it starts from.
1. What the app collects
Four things — usage statistics, advertising, purchase status, and diagnostics. None of them is linked to your identity.
1-1. Usage statistics (Google Analytics for Firebase)
Used to see overall trends in how the app is used. The build excludes the advertising identifier, so no IDFA is collected and no App Tracking Transparency prompt appears.
| Item | Purpose | Kept for |
|---|---|---|
| App instance ID — assigned automatically to each installation. Not linked to your identity or to any advertising identifier. | Usage statistics | 14 months |
| Coarse location — country or region level, derived from a masked IP address. iOS location services are not used and precise location is never collected. | Usage statistics | 2 months |
| Usage records — app lifecycle events such as screen views and sessions. | Usage statistics | 2 months |
The two retention periods are Google Analytics settings; event records and the identifier attached to them are stored separately. Both expire automatically, and aggregated statistics are unaffected.
1-2. Advertising (Google AdMob) — from 1.3.0
From version 1.3.0 the app shows ads — one interstitial when you press stop after a timer ends, and one banner each at the bottom of the settings screen and the history screen.
Personalized advertising is not used. Every ad request carries the
non-personalized flag (npa=1), so nothing is selected based on your interests
or your activity in other apps.
No IDFA (advertising identifier) is requested, so no App Tracking Transparency
prompt appears. The privacy manifest the app submits to the App Store also
declares that it does not track (NSPrivacyTracking = false). The Google
publisher first-party identifier is also explicitly disabled.
Showing an ad is not the same as processing nothing. To deliver ads, to stop the same ad from repeating (frequency capping), and to detect invalid clicks, AdMob processes the following.
| Item | Purpose |
|---|---|
| Device information — model, OS version, screen dimensions | Ad delivery, invalid click detection |
| Device identifier — not the IDFA; a value the ad SDK uses to tell devices apart | Frequency capping, invalid click detection |
| Coarse location derived from IP address — country level | Region-appropriate delivery, invalid click detection |
| Ad interactions — impressions and clicks | Frequency capping, performance counting |
| In-app interactions — screen transitions and similar | Deciding when to show an ad, performance counting |
From version 1.5.0 (build 6), the app uses Google UMP (User Messaging Platform) to update the current privacy status before starting the advertising SDK. It does not present a new consent message for personalized advertising. In the European Economic Area, United Kingdom, and Switzerland, if UMP reports that ads cannot be requested, Google Mobile Ads is not started and no ads are requested or shown.
If UMP reports that ads can be requested based on a valid choice made previously,
the app still requests only non-personalized ads (npa=1). Google may further
restrict delivery to limited ads according to that choice. An eligible existing
user can review or change the previous choice under Settings > Privacy.
Versions 1.3.0 through 1.5.0 (build 5) may instead present a UMP message before advertising in those regions and process advertising data according to the choice made there.
How Google handles this data is described in the Google advertising partner sites policy.
Ads are removed by purchasing SIMTA PRO (see 1-3).
1-3. Purchase status (Apple · RevenueCat) — from 1.3.0
From version 1.3.0 there is a one-time purchase, SIMTA PRO — removes ads, adds ten themes and twelve history slots. It is not a subscription; you buy it once.
Apple handles the payment through StoreKit. Card numbers, account details, and other payment credentials are never passed to OurBeom, and the app neither sees nor stores them.
RevenueCat is used to keep purchase status consistent across devices. It receives an anonymous user ID and transaction receipt information. Your name, email address, and anything else that identifies you are not sent.
1-4. Diagnostics (Google) — from 1.3.0
The advertising SDK (Google Mobile Ads) and the consent SDK (User Messaging Platform) send diagnostics about their own operation to Google. The app does not gather or store this itself; each SDK transmits it directly, as declared in its own privacy manifest.
| Item | Purpose |
|---|---|
| Crash records | Analytics |
| Performance data — response times, error rates | App Functionality, Third-Party Advertising, Analytics |
| Other diagnostic data | Analytics, Third-Party Advertising |
App Functionality appears only against performance data because the consent SDK uses it to present consent messages in versions through 1.5.0 (build 5), and from build 6 to update privacy status and present the privacy options form for an eligible existing user. These purposes match what each SDK declares in its manifest, and match the App Privacy details shown on the App Store.
This data does not identify you and is not used for tracking. As stated in 1-2,
ads are fixed to non-personalized (npa=1) and no IDFA is requested.
The crash records described here are separate from the ones Apple collects at the operating-system level and shows to developers. Those are processed by Apple only if you have opted into sharing in your device settings, and this app does not receive them.
Versions 1.2.1 and earlier do not contain the advertising SDK, so this section does not apply to them.
2. What the app does not collect
No account information, name, email address, phone number, contacts, photos, precise location, payment credentials, or advertising identifier (IDFA).
Your activity outside this app is not tracked. We do not do what Apple calls tracking — linking data with data collected from other companies' apps or websites for targeted advertising — which is why no App Tracking Transparency prompt appears. The device information and coarse location described in 1-2 are processed in order to deliver ads and do not constitute that tracking.
3. What stays on your device
Timer durations, theme colour, keep-screen-awake setting, and timer history are
stored on the device in iOS UserDefaults. They are never sent to a server and
are removed when you delete the app.
4. Notifications
The timer-finished alert is a local notification scheduled on the device. There is no push server and no device token is collected.
5. Links out of the app
In settings, Feedback opens your mail app, Leave a review opens the App Store, and Share the app opens the iOS share sheet. All are handled by the system and the app sends nothing on its own. If you write to us by mail, your device model, iOS version, and app version are prefilled in the body — you can review and edit them before sending.
Tapping an ad opens a destination chosen by the advertiser. What happens after that follows that advertiser's and Google's policies.
6. Your rights
Wherever you are, you can request the following at simpletimerapp@gmail.com. We reply within two business days.
One practical note first. The data above is not linked to your identity, so we normally cannot tell which records belong to a particular person. If you want something done for a specific installation, tell us and we will explain what we need. Deleting the app removes the app instance ID from your device; reinstalling creates a new one, and earlier records expire on the schedule above.
- Republic of Korea (PIPA) — you may request access, correction, deletion, and suspension of processing. You may also bring a dispute or report to the Personal Information Dispute Mediation Committee (kopico.go.kr) or the Korea Internet & Security Agency's privacy centre (privacy.kisa.or.kr, 118).
- European Economic Area and United Kingdom (GDPR) — you have rights of access, rectification, erasure, restriction, objection, and portability, and you may lodge a complaint with your supervisory authority. If Privacy appears in the app's Settings, you can use it to reopen Google's privacy options and review or change a choice made previously.
- California (CCPA/CPRA) — you have the right to know what is collected, to request deletion, and not to be discriminated against for exercising those rights. We do not sell or share personal information, and have not done so in the preceding twelve months.
Under the GDPR the legal basis is legitimate interest (Art. 6(1)(f)) for the usage statistics in 1-1; consent (Art. 6(1)(a)) where required for the advertising processing in 1-2 in the EEA, the UK, and Switzerland; and performance of a contract (Art. 6(1)(b)) for purchase status in 1-3. If UMP does not report that ads can be requested, the app makes no ad request.
7. Who else processes this data
The following process data on our behalf. We do not sell personal information to third parties for advertising.
| Recipient | What | Policy |
|---|---|---|
| Google (Firebase) | Usage statistics in 1-1 | firebase.google.com/support/privacy |
| Google (AdMob · UMP) | Advertising data in 1-2, diagnostics in 1-4 | policies.google.com/technologies/partner-sites |
| Apple | In-app purchase processing | apple.com/legal/privacy |
| RevenueCat, Inc. | Anonymous user ID and receipt information in 1-3 | revenuecat.com/privacy |
These providers may process data outside your country and state that such transfers rely on the European Commission's Standard Contractual Clauses.
8. Children
SIMTA is not directed to children under 14, and we do not knowingly collect personal data from them. Its App Store age rating is not a children's category.
One note about advertising: because the app does not use personalized ads, no ad is selected on the basis of interests, regardless of the viewer's age. If you believe a child has provided us with personal data, write to simpletimerapp@gmail.com and we will delete it.
9. Changes to this policy
If this policy changes, the updated version is published at this same address with a new effective date, and the previous versions stay available from the date menu at the top of the page. The address does not change.
Revision history
- September 21, 2026 — from version 1.5.0 (build 6), the app no longer presents a new UMP advertising-consent message. It does not start Google Mobile Ads or request ads when UMP reports that ads cannot be requested. All ad requests remain non-personalized, and Google's publisher first-party identifier is explicitly disabled. Existing users who previously completed Google's privacy choices can reopen them from Settings when UMP requires that entry point.
- September 10, 2026 — app version 1.3.0 introduces Google AdMob advertising and a one-time in-app purchase (SIMTA PRO). Sections 1-2 and 1-3 were added, and the tracking wording in section 2 and the processor list in section 7 were revised to match. Published ahead of the 1.3.0 release. Later the same day, section 1-4 was added after finding that the advertising and consent SDKs send diagnostics of their own.
- September 7, 2026 — first published.
10. Contact
OurBeom (아워범) · Daeho Kim, representative