Scope and contact
This policy covers the Timo app, its widgets, and this website. The developer’s public identifier is arvin-manager. Contact anarvin212@gmail.com for privacy requests and support. Independent processing by third-party platforms is also governed by their own policies.
Information you provide
Plan titles, dates, notes, subtasks, focus records, memos, countdowns, preferences, and photos attached to plans or memos or chosen as backgrounds are normally stored on your device. Selected photos are processed locally for attachments, backgrounds and sharing, including compression and metadata removal; the app does not proactively scan your library. Manual file exports and cloud backups may include this content and photos. Avoid entering unnecessary sensitive information.
Cloud backup
Local features need no account. Google or Apple sign-in and Firebase Authentication process authorized identifiers, name, email and sign-in information; Timo does not receive your provider password. A manual backup, or an automatic backup you enable with Plus, uploads a content snapshot and version, time and record-count metadata to your private Firestore space. Up to five complete versions are retained. Backups do not merge devices and are not end-to-end encrypted. Signing out keeps local content and cloud backups.
Optional usage analytics
Help improve Timo is off by default. If enabled, Firebase Analytics receives permitted events such as screens viewed, sign-in method, quadrants, feature use, timer mode and minutes, and backup counts, along with app, device, instance identifier, network, and other technical information needed by the SDK. Timo does not include plan titles, text, notes, photos, email addresses, or account IDs in analytics events. It does not set an analytics user ID and disables automatic screen reporting and IDFA / IDFV collection. Events can be associated with an installation-scoped app-instance identifier. Google may derive a general location from masked IP addresses; Timo does not request GPS or precise location permission for this. Authentication and backup providers may also process service diagnostics even when optional analytics is off.
Withdraw consent under Settings → Data & privacy to stop future collection and reset local Analytics state. This does not automatically erase previously transmitted data held by the provider. Contact us for further requests.
If you enable optional usage analytics, Timo records purchase product and outcome, ad impressions and estimated advertising revenue, alongside feature-use and backup counts. Analytics is off by default and can be withdrawn in Settings.
Advertising and privacy choices
No ads are requested during the initial 72-hour trial or an active subscription. Otherwise, Home and Statistics may show Google AdMob banners. Capped interstitials may follow saving a plan, leaving a focus result, or returning after resolving overdue plans, never during timing or editing. Google UMP handles applicable regional choices before requests. Requests are non-personalized; Timo does not request cross-app tracking authorization.
Non-personalized ads still involve data processing. Google advertising SDKs may process IP addresses, device or advertising identifiers, inferred approximate location, diagnostics, and ad impressions and interactions for delivery, measurement, frequency limits and fraud prevention. Actual processing depends on SDK version and Google disclosures. Where required, manage choices under Data & privacy → Ad privacy options. The analytics switch does not control ad choices.
Watch an ad to unlock one theme for 24 hours. Closing early or playback failure gives no reward.
Membership and trial records
Apple StoreKit processes subscriptions, payments and refunds. Timo uses Apple-verified transactions to determine access; the developer does not receive payment-card details or send transactions to a separate purchase server. The device Keychain stores the first-use and last-observed times to calculate one 72-hour trial and reduce reuse by rolling the clock back. These times are excluded from exported and cloud backups. Clearing local content does not reset the trial; they normally persist through ordinary reinstallation. This is a device-based trial, not an account-wide cross-device offer.
Permissions, reminders, and screen visibility
Notification permission is requested when you choose local plan, focus or countdown reminders. System interfaces handle selected photos and sharing; you choose the destination. Camera permission is requested when you choose to take a photo for a memo. Timo does not record continuously or request contacts, microphone or precise location access for core features. File access is used for backups you choose to import or export.
The memo access lock offers a numeric PIN; Plus or the app trial also enables a gesture and supported Face ID or Touch ID. Salted password and gesture derivatives are stored in the local Keychain and excluded from exported and cloud backups. iOS performs biometric authentication; Timo receives only its result, not raw face, fingerprint or biometric templates. The access lock does not encrypt the database or exported backups.
Widgets receive display information through the local App Group, including plan titles, memo excerpts, dates, focus status and selected photos. Memo excerpts are hidden when the memo lock is enabled. Live Activities may show focus titles and times on the lock screen and Dynamic Island. Choose widgets and system visibility settings carefully if others can see your screen.
Holidays and network requests
To retrieve holidays for your chosen region and year, the app may request public Google Firestore calendar caches and Nager.Date. Requests include country, subdivision, and year. Providers may receive IP addresses and technical network logs. This is not GPS location and does not upload your plans or memos. Local snapshots are used first; unavailable sources or networks may limit coverage.
Website hosting and support email
This website consists of static GitHub Pages files without embedded ads, analytics scripts, or tracking cookies. GitHub may process IP addresses, browser information, access logs, and security logs under its own policy. Linked sites and email services have independent policies. If you email support, we process the address, issue, and attachments you provide to respond, troubleshoot, and meet applicable obligations.
Purposes, legal grounds, and providers
Local processing carries out your actions. Authentication and backups provide services you request. Optional analytics relies on your withdrawable choice; ad choices follow applicable regional rules. Necessary security, abuse prevention, and support protect the service and legitimate rights, and legally required processing fulfills legal obligations. We do not sell your plans, memos, or backup content to advertisers or use that content for ad targeting.
Providers include Google (Firebase Auth, Firestore, Analytics, AdMob / UMP), Apple (sign-in and system services), GitHub (hosting), Nager.Date (public calendars), and email providers. They receive necessary information when related features are used. Necessary disclosures may also be made when required by law or to protect rights.
Retention, deletion, and copies
Local content stays until you delete it, clear app data, or uninstall; system copies also depend on iOS settings. Cloud backups generally retain the last five complete versions until replaced or the account is deleted. Incomplete uploads are removed during cleanup or account deletion. Successful deletion removes the Firebase account and cloud content. A minimal deletion marker associated with the former account identifier may remain to prevent still-valid tokens from recreating content; it contains no backup text or contact details.
Analytics, ads, security logs, and provider recovery copies follow provider settings, policies, and legal obligations. We do not promise immediate removal from every system copy. Support emails are retained through resolution and necessary follow-up, and can be deleted on request when no longer required. You must delete exported files and copies sent to third parties yourself.
Your choices and rights
You can edit or delete content, export files, disable analytics, adjust ad choices, revoke system permissions, and delete your account. Settings → Sign-in & account → Delete Timo account requires identity verification and deletes all cloud backups while keeping local content and exported files. Clearing local data is a separate action.
Email us to request access, correction, deletion, restriction, a data copy, withdrawal of consent, or to raise an objection or complaint. We respond within applicable legal deadlines and may verify identity first. Regional law may provide additional rights, including complaints to a regulator and applicable sale / sharing opt-outs. We do not discriminate for exercising legal rights.
International processing and security
Google, Apple, GitHub, and other providers may process information outside your region. Storage locations, transfer mechanisms, and safeguards depend on service configuration, contracts, and applicable law. Timo uses platform HTTPS, account access controls, and necessary validation. No system is completely secure, and we do not claim end-to-end encryption for all content. Protect your sign-in accounts and exported backups.
Children
Timo is not a service specifically directed at children under 13 and does not proactively request age or children’s information. Where local law requires guardian consent, obtain appropriate consent before using relevant online services. If children’s personal information has been processed without appropriate authorization, email us so we can investigate and take deletion or other necessary action.
Policy changes
We update this page and its effective date when the policy changes. Material changes affecting data use or your rights will receive appropriate in-app or website notice, with renewed consent where required by applicable law.