Skip to content
TimeBusterby NaviLab
Service informationPrivacy, account deletion and support information for TimeBuster.

PRIVACY, EXPLAINED CLEARLY

Privacy policy

Where your TimeBuster records are stored, what leaves your device and how deletion is handled.

How your records and personal information are handledThis policy explains cloud processing of accounts and general records, and private health storage on your device. The account-deletion and support pages explain how to request deletion or contact us.

Service provider and privacy contact

Provider
NaviLab (나비랩)
Representative / privacy officer
Park Jong-deok (박종덕)
Address
27-16, Baegot 1-ro, Siheung-si, Gyeonggi-do, Republic of Korea
Email
timebuster.app@gmail.com

NaviLab operates TimeBuster separately from CodingCom academy.

1. Purpose and service structure

TimeBuster helps you record activities and review your time, schedules and goals. Local SQLite recording is available without an account. Account connection, sync and cloud backup depend on the released version, enabled services and your choices.

Processing supports recording, time calculations, restoration, undo and change history, conflict handling, authentication, subscription entitlements and support. Activity recording, daily analysis and automatic cross-device sync are free; weekly, monthly and yearly analysis are Premium.

Versions meeting platform and store requirements can optionally import selected sleep and workout records on the device to avoid entering the same activity again.

2. Authentication and account information

Official Google or Apple sign-in passes provider tokens and required authentication information to Supabase Auth. Account information can include a Supabase UUID, provider identity and supplied email, name and metadata. Apple may provide a name on first authorization and supports hidden email addresses. A name or email is not always available.

The app does not collect your Google or Apple password through its own password form. Authentication sessions, including access and refresh tokens, use device secure storage. This does not mean every local activity or exported file is encrypted by the app.

3. Records, schedules and settings

  • Activity identifiers, names, categories, start/end/estimated times, status, parent relationships, goals, evaluations, input source and timestamps
  • Work and pause segments, plus inefficient periods confirmed by you
  • Schedule names, repeated days, times, enabled status, versions and effective dates
  • Language, time zone, onboarding, theme, notification settings and related change/audit history

Records are saved locally first. Enabled sync and backup can send those records and related history to Supabase. Free text can contain personal or sensitive information. Earlier values may remain in history or snapshots after an individual record is changed or deleted.

Workspace UI personalization files—quick-start names, icons, colours, order, haptics, sounds and timeline display preferences—are not currently part of DB sync or JSON backup. Analysis is derived from records; unrecorded gaps are not uploaded as fabricated activities.

The Supabase transmission described in this section applies to general records. Separately approved private health imports and their derived aggregates are excluded from that transmission and general backups; section 4-1 applies.

4. Local storage, sync and backups

Activity data is stored in app-private SQLite files. The app does not provide whole-database SQLCipher encryption. Exported JSON is plain text and may contain private records. Server deletion cannot recall files you export or share.

Sync exchanges changes between devices. Requests can include owner/device identifiers, operation and batch identifiers, entity identifiers, revisions and actual record payloads. Pull requests include a cursor and page size. App backups send a complete snapshot JSON.

Outbox and conflict state are local, but pending record payloads can be sent when connectivity returns. Signing in does not itself authorize merging all Guest records. Signing out does not delete local or server records.

The explanation above continues to apply to the general activity database and general JSON backups. Only private health imports use a separate SQLCipher-encrypted, device-only store excluded from backups, as explained in section 4-1.

4-1. Optional health imports and automatic observation storage

In versions meeting platform and store requirements, TimeBuster can read sleep and workout records from Apple Health (HealthKit) or Health Connect to avoid entering the same activity again. Saving a confirmed activity requires you to select, review and approve the record. Separately, only with your separate consent for sleep and for workouts, the app retains permitted health observations in encrypted storage on this device when you open or return to the app. Consent to automatic observation storage, OS health-reading permission and approval to save an activity are separate choices. You can use general activity recording without consenting.

Automatic reads cover the current local date and the previous six dates. This is not continuous background monitoring, and repeated reads within a short interval may be limited. Data includes start/end times, observed sleep and awake intervals, exercise type and minimal source identifiers for duplicate prevention. Heart rate, calories, workout routes and medical records are not read. TimeBuster never changes or deletes originals in the health platform.

An automatic observation does not save a confirmed activity or confirm an activity, purpose, plan adherence, goal completion or wasted time. Unobserved time is not classified as waste. Changed or unverifiable evidence may flag related judgments for review; it does not automatically overwrite or delete approved activities. Revoked access and incomplete responses are not treated as deletion of source health records.

Automatic observations and source-specific consent, approved health activities, actual intervals and minimal import, review, dismissal, deletion and edit history are stored in a separate SQLCipher-encrypted store, isolated by device, signed-in account and workspace. Keys stay in device-only secure storage. Both observations and approved health activities, including health-derived aggregates, are excluded from Supabase, general cloud sync, JSON backups, server analysis caches, advertising, marketing and analytics SDKs. Approval to save an activity is not consent to cloud transmission. Approved health activities appear in the existing timeline and daily, weekly, monthly and yearly analysis only on this device. Results may differ on other devices. This does not mean that the entire general activity database is encrypted.

The seven-date window is the range for reading new observations, not a retention period or an automatic deletion deadline after seven days. Earlier observations and approved health activities may remain on this device until you delete them. A capacity failure is reported rather than silently deleting existing observations.

Stopping automatic import stops new reads only. Deleting a source’s sleep or workout observations turns off its automatic refresh and removes only those observations, keeping approved activities, judgment history and HealthKit/Health Connect originals. Revoke reading access through the Health app profile → Apps/data access → TimeBuster on iPhone, or Health Connect → App permissions → TimeBuster on Android. Menu names can vary by OS version. Revoking access or disconnecting also does not automatically delete approved activities. You can delete approved activities individually in the app. Separately, confirming deletion of all private health imports in health settings removes this account’s health activities, intervals, observations, handling, review, dismissal, deletion and edit history, consent and keys on this device, including prior workspaces. General records, other accounts and health-platform originals are not deleted.

These records stay on this device and do not sync. They are excluded from general app backups, OS backups and device transfers. Observations, approved activities and edit, review and dismissal history may not be recoverable after app removal or device replacement. Available health originals can be imported again, but this does not restore app edits, review or dismissal history. Missing keys or integrity errors stop access without automatic reset.

5. Speech recognition and Siri

In-app speech uses the operating system’s speech service. iOS in-app speech requests on-device recognition and offers keyboard input if that support is unavailable. Android uses the installed system recognition service, which may send audio to providers such as Google or Samsung for network processing. Offline recording does not imply offline speech recognition.

Siri and Shortcuts are processed by Apple’s OS separately from in-app speech. Depending on the action, an activity phrase, current activity name or today’s total may be supplied to or displayed/spoken by Siri. The prepared native request queue keeps raw requests in memory for up to 120 seconds; that limit is not the retention period of a confirmed saved activity.

The app does not itself save raw audio as recordings or upload audio files to Supabase or a separate STT API. Recognized text is processed in memory and confirmed activity text and related events can be stored and synced. This is not a claim that all OS speech data stays on the device.

6. On-device AI and availability

Rule-based command parsing runs locally. Apple Foundation Models and Android AICore/ML Kit with Gemini Nano check device, OS, language, model readiness and enabled product options. Current product opt-in paths can be used in Release builds; internal test and diagnostic paths remain excluded. Model preparation may require your agreement and supported device services.

Model inputs can include the activity phrase, date/time zone and limited control context—not the account’s entire database or Supabase authentication tokens. Validated results go through confirmation; models do not directly access the database or sync engine. Unsupported environments retain rule-based or keyboard alternatives.

The CloudAiInterpreter interface does not currently implement cloud-model transmission. This does not establish that OS services never use networks. Siri, speech providers, model distribution and OS diagnostics have their own processing conditions.

RevenueCat, purchases and asynchronous deletion

To provide subscriptions and restore purchases, TimeBuster links your Supabase account UUID to a RevenueCat App User ID and processes store product, purchase, transaction, subscription and entitlement information. The app does not send activity content or Supabase authentication tokens to RevenueCat. Apple and Google handle store payments and subscription management separately.

The server workflow requests deletion of the associated RevenueCat customer and verifies the result in a later check. Request acceptance is not deletion completion. Pending or failed work is not reported as fully complete. Limited account identifiers and verified aliases remain in a restricted server job record for retries and are removed from that job when completion is confirmed. Provider delays, errors or an account-linking conflict may require retry or manual review; no fixed completion time is promised.

The account-deletion API, automated worker and scheduled processing are operational. Completion is reported after the required server stages, including RevenueCat customer deletion, are verified for the request. Customer deletion does not erase the store’s original transaction records, cancel a mobile subscription, or establish immediate physical erasure from every provider backup. SDK logout is not customer deletion.

NaviLab is the controller and RevenueCat, Inc. is its processor for subscription services under the RevenueCat DPA. RevenueCat uses US hosting for customer data. Account identifiers and purchase/subscription data are transmitted over HTTPS when the SDK checks or restores purchases, or when server deletion is requested. Data is used to provide and verify entitlements; the associated customer is deleted through the account-deletion workflow. Store transaction records and provider recovery/log copies have separate rules; a contract-termination period is not an end-user deletion deadline. RevenueCat DPA · compliance@revenuecat.com · Customer deletion reference

7. Diagnostics, website and support email

This website uses a TimeBuster-only language preference cookie for up to one year when you choose a language. It contains only ko or en, is not an activity record or tracking identifier, and can be removed through your browser settings. Without a saved choice, supported browser-language preferences are used.

Diagnostics can include permissions, locale, availability, status, fixed error codes, sync counts, cursors and identifier fingerprints. The supplied implementation excludes activity phrases and model responses from ordinary speech/AI diagnostics. A fingerprint is not necessarily anonymous.

Server, SDK, OS and web-host services can process connection metadata such as IP addresses, timestamps and browser/device information. Supabase Free makes API and database logs viewable for one day; this is not a promise that all logs are physically erased after one day.

The operator has confirmed that WastedHours-Dev uses Supabase Free in Seoul (ap-northeast-2). Free provides a one-day API/database log viewing window, not a physical-erasure deadline for all logs, security telemetry or recovery copies. Free does not support Log Drains; this feature is not used for separate log exports. Supabase’s October 6, 2026 Data Residency FAQ states that service operations logs are collected and stored in EU data centres. The exact EU member states and the provider’s internal physical retention and erasure periods cannot be established from the official public material. The inspected TimeBuster deletion-function source does not separately print request bodies or tokens, and the RevenueCat SDK uses error-level logging; these settings do not disable or immediately erase provider platform operations/security logs.

This site does not automatically attach app records or authentication data to an inquiry. Gmail handles the sender address, message, attachments and replies you choose to send. Support email is not automatically deleted by the app’s account-deletion workflow. General customer inquiry emails and replies are retained for one year from the date the inquiry is resolved and deleted after that period. Unresolved inquiries are retained until resolution. Records subject to statutory retention, including purchase, payment and dispute records, are kept separately from general inquiries for the period required by the applicable law. This is NaviLab’s policy for deleting the email it manages; it does not guarantee immediate physical erasure of Gmail or provider recovery copies. Receipt and replies at the support mailbox have been verified; support receives and responds to inquiries. Opening an email app is not delivery or receipt.

Health originals, activity names, times, intervals and health-derived analysis aggregates are not recorded in or sent to general diagnostic or analytics SDKs or server caches. This is separate from the general operational metadata described above.

8. Account deletion and asynchronous processing

A new deletion request currently requires a valid signed-in session and recent reauthentication with the same linked Google or Apple account. A sender email or name alone is not proof of ownership, and passwords or tokens are not collected by email. The website has no separate reauthentication or manual deletion-approval path for someone unable to use the app, so an email inquiry alone does not create a server deletion job or establish completed deletion. The worker resumes previously approved jobs; it does not verify a new requester. The account-deletion API, automated worker and scheduled processing are operational.

The account-deletion API and automated worker process confirmed requests and retries. Completion is reported after the required server stages are verified. The workflow separates reauthentication, confirmation, Apple token revocation, owned Storage/sync/app-backup removal, Supabase Auth deletion, RevenueCat request and later verification, then current account workspace cleanup.

Pending or failed processing is not complete. Restricted server job records retain only necessary identifiers, verified aliases, status and retry information while processing; user identifiers are cleared from that job when completion is verified. Provider customer absence is a point-in-time result, not a guarantee that future store events or another device can never recreate a customer.

Other offline devices, exports, recovery copies, caches, support messages and applicable legal records need separate handling. Separate Guest/other-account workspaces and personal Google/Apple accounts are not deleted by the same request. The completed-receipt lookup window is seven days, not the retention period for all personal data.

Account deletion and external request instructions →

Deleting private health imports on the device is separate from general server-data deletion, subscription cancellation and deletion of health-platform originals. Section 4-1 explains the scope and recovery limits for this account’s health records and handling history on this device.

Subscriptions, cancellation and restoring purchases

Deleting your account does not cancel an Apple or Google subscription.Automatic billing may continue. Cancel separately in the store that billed you. Cancellation is not a prerequisite for requesting account deletion, and deleting the app or signing out does not cancel billing.

Apple: Settings → your name → Subscriptions → TimeBuster → Cancel Subscription. Google Play: profile → Payments & subscriptions → Subscriptions → TimeBuster → Cancel subscription. Use the store account used for the purchase. The store shows the next renewal or expiry date; cancelling usually stops the next renewal rather than refunding the current period. Deleting a TimeBuster account is separate from the store’s billing status.

To restore a purchase, use Restore purchases in the app with the original store account. Results depend on the store and the RevenueCat project’s restore settings; a new TimeBuster account does not automatically receive the old account’s purchase rights. We do not promise that purchases will transfer between accounts or stores.

9. Processors and international transfers

Supabase
NaviLab is the controller and Supabase Pte. Ltd. (Singapore) is its processor under the Supabase DPA. Supabase provides the infrastructure processing used for authentication, records, sync and app backups. The existing WastedHours-Dev Free project stores core DB/Auth/Storage data in Seoul, ap-northeast-2. A provider’s registered country is not necessarily the data-storage country.
Support and operations
Supabase, Inc. (United States) may access necessary project/account identifiers, configuration, logs and relevant sample data for support, operations or security response. This does not mean all activity content is continuously replicated to the US.
Logs
Supabase collects and stores service operations logs, telemetry and metadata in EU data centres. Its October 6, 2026 FAQ does not identify the exact EU member states or establish internal retention and physical-erasure periods. The Free plan’s one-day general log viewing window is not an erasure deadline. Platform logs and the full activity database are not the same data flow.
Provider contact
privacy@supabase.io
Transmission and timing
Authentication information is sent at sign-in; record changes are sent during enabled sync, including later retries; snapshot JSON is sent for backups. The app uses HTTPS APIs. Necessary provider access can occur during support or security response; service logs arise during service use. Provider access and logging are also described in Supabase’s public DPA and residency documentation.
RevenueCat and stores
RevenueCat, Inc.’s official DPA identifies its processor role for customer personal data. TimeBuster supplies the account identifier and store purchase/subscription information for entitlement and restoration services, not activity content or Supabase tokens. RevenueCat uses US hosting for customer data. Identifiers and purchase/subscription information are sent over HTTPS when purchases are checked or restored and when deletion is requested. The account-deletion workflow removes the associated customer; store transaction records and provider recovery/log exceptions are separate. Apple and Google handle payments and subscription management under their applicable store terms.

The Supabase subprocessor list includes AWS hosting and other supporting services. A company’s registered country does not establish that this app sends data to every listed country or uses every optional service. Optional Storage CDN processing must be assessed against actual use; no app audio-upload path is implied.

If you do not want optional cloud processing, do not connect an account or use sync/cloud backups; local recording remains available. Request processing restriction or deletion of existing data through timebuster.app@gmail.com, subject to identity verification. Required cloud processing cannot be refused while continuing those cloud features. Logging out or emailing alone does not erase existing server data. OS speech/Siri choices are separate.

The transfer information above reflects the confirmed data, recipients, purposes and storage locations. Supabase publicly states that service operations logs are collected and stored in EU data centres. Its public materials do not establish individual EU member states, retention periods by log category or deletion conditions; no unverified country or period is stated here. You may contact NaviLab to request access, restriction or deletion. We verify identity and explain the available handling and result.

References: Supabase residency and transfers · Subprocessors · Supabase DPA · RevenueCat DPA.

10. Retention

Our policy is to keep account and activity information during service use and destroy it through account-deletion processing. That scope includes schedules, analysis source records, related history and app cloud backups. The account-deletion API, automated worker and scheduled processing are operational; completion is determined from each request’s final verified status.

Supabase Free does not include the automatic daily DB backup feature provided on paid plans. App cloud snapshots are a separate feature and are included in the account-deletion scope. Free does not mean no operational copies or logs can exist.

General inquiry emails and replies are retained for one year after resolution and then deleted; unresolved inquiries remain until resolution. Statutory purchase, payment and dispute records are kept separately for the applicable legally required period. Provider recovery copies and logs follow provider conditions; unresolved deletion jobs remain restricted while processing or retrying. The email retention policy does not determine provider retention. We do not substitute the one-day log-viewing window, seven-day receipt lookup window, provider contract-termination periods or project-deletion deadlines for end-user data-retention periods.

References: Supabase backups · Free plan and log access.

11. Destruction procedures

The account-deletion workflow verifies identity and ownership, removes the owner’s live records and account, requests and separately verifies RevenueCat customer deletion, then cleans the current account workspace. Failed or asynchronous stages remain pending or require assistance rather than being reported as complete. Email acknowledgement is not server deletion.

Deleting live database records is different from physically erasing storage media, recovery copies and provider logs. NaviLab deletes general inquiry emails and replies from its managed mailbox after the one-year period following resolution; unresolved inquiries and statutory records follow the retention rules above. Provider log and recovery-copy erasure methods and schedules require separate confirmation and are not the same as mailbox deletion. We cannot remotely recall your exports or erase an offline device immediately.

12. Your rights and how to contact us

You or an authorized representative can request access, correction, deletion or restriction of processing by emailing timebuster.app@gmail.com. We verify identity safely, explain applicable procedures and limitations, and distinguish receipt from completion. Do not email passwords, tokens, government identification numbers or private activity text.

13. Effective date and changes

Public-copy last revised: . The effective date will be set to the actual first publication date when this policy is formally published. Changes will be announced here with their effective date and content.

V2 health notice revised: . The existing distinctions between observations and confirmed activities, separate consent, query range, retention, deletion and recovery limits are preserved. This revision updates account-deletion operations, support status and confirmed cloud-processing information.

14. Privacy questions and complaints

Privacy officer: Park Jong-deok (박종덕), NaviLab representative. Contact timebuster.app@gmail.com for privacy questions, complaints or account requests. Receipt and replies at the support mailbox have been verified, and inquiries are accepted at this address. The one-year inquiry retention period is not a guaranteed response or deletion-completion deadline.

Contact support ↗