Privacy policy

1. Scope and responsibility

This policy covers NeuraTiM Timer on Android, iOS and the web, and this website. The independent developer NeuraTiM is responsible for personal data handled in connection with the website and direct support enquiries.

The app is free, contains no advertising, and has no paid tier.

2. No in-app data collection by the developer

The app has no account system or analytics backend. It processes your timers locally and does not automatically send their contents to the developer. It does not request the following data for tracking or profiling:

• Your name, email address, phone number or account details; registration is not required
• Advertising identifiers or device identifiers for tracking
• Precise or approximate location
• Contacts, calendar entries, call logs, text messages or lists of installed apps
• Usage analytics, diagnostics or crash reports sent by the app
• Payment details within the timer app; optional website tips are covered separately below

3. Data stored on your device

The app saves the data needed to keep your timers and settings available, including:

• Saved timers and their type-specific settings, such as titles, colours, durations, steps, exercises, breaks, repeats, working hours and medication schedules
• Your quick timer’s most recent settings
• Each timer’s sound, alert repeat interval, vibration, on-screen duration and screen-awake preference
• Active sessions, their start and pause state, and history of completed or stopped sessions
• App preferences, including language, appearance and default alert settings

4. Where that data is kept

On Android and iOS, settings are stored in the app’s private storage, protected by the operating system’s app sandbox.

The web app uses storage in your browser for the app’s site address. Clearing that site’s data removes the locally stored information.

The app provides no developer-hosted cloud backup or device sync. Files you export and any backups managed by your operating system or browser are separate from the app’s local storage.

5. Permissions and device features

Permissions depend on the platform and the feature you use. You can manage them in system settings; refusing one may limit the related feature. QR scanning or selecting an import file may also require access to the camera or to the file or image you choose.

• Notifications and alarms — deliver scheduled local alerts. On iOS and iPadOS 26 or later, AlarmKit reminders require Alarms permission.
• Exact alarms (Android) — allow more precise scheduling, subject to system permissions and restrictions.
• Full-screen alerts (Android) — allow an alert to appear over the lock screen where supported and permitted. Otherwise, a standard notification may be shown.
• Run at startup (Android) — restores scheduled alerts after a device restart, subject to system restrictions.
• Vibration — provides the alert pattern you select, when supported by the device.

6. Sharing, exports and network access

QR codes and export files are created locally. Sharing them sends the included timer information to the person or service you choose. The app does not automatically upload your timers. The web version needs a connection to load; website hosting, payments and external links involve the services described below. Included alert sounds do not need streaming.

7. Keeping and deleting data

You manage timer data on your device; the developer has no cloud copy of it to retrieve or erase. Deleting app data does not delete files you exported, copies you shared or backups managed elsewhere.

• Delete individual timers from the side menu. The app asks for confirmation and briefly offers Undo.
• Stopping a session ends it but may leave a history entry. Clear history separately to remove those records.
• Clear the app’s stored data through your device settings, or delete the app and its data. Backup and app-offloading behaviour depends on the platform.
• For the web app, clear the site’s data in your browser.

8. Security

Local data relies on the security of your operating system, browser and device. A screen lock and up-to-date software help protect it.

The developer keeps no central database of your timers. Exported files and shared QR codes are outside the app’s private storage; share them carefully.

Alerts may show a timer’s title on the lock screen. Avoid sensitive details in titles, particularly for medication reminders, when other people might see your screen.

9. Children

The app is not designed for or directed at children under 13, or the applicable minimum age in their country. The developer does not collect children’s data through the timer app.

10. Third-party code in the app

The app uses open-source libraries for functions such as local notifications, audio, vibration and time-zone handling. These features process timer data on the device.

The timer app contains no advertising, attribution, analytics or crash-reporting SDKs. Included alert sounds are bundled with the app rather than streamed from an audio service.

11. This website

The website introduces the app, embeds its web version and offers optional ways to support development. Its network and payment services are separate from local timer storage.

• Hosting — Cloudflare serves the site and may process IP addresses, browser information and requested URLs for delivery and security. This site does not use advertising or analytics tracking. Hosting and payment services may process operational data under their own policies.
• Language — your choice is saved in browser storage and may appear in the page URL. A requested URL, including its language path, is visible to the hosting service.
• Tips — optional payments are processed by Stripe or the provider you choose, such as Ko-fi, PayPal or GitHub Sponsors. Their privacy policies apply. They may provide the developer with transaction records and donor details; full card details are handled by the payment provider. Support emails are also received by the developer.
• Try it — the embedded web app stores timer data in your browser. Loading it requires a web request, but your timer entries are not sent to the developer as analytics.
• External links — download pages, payment services, GitHub and other linked sites have their own privacy policies.

12. Your rights

Depending on applicable law, you may have rights to access, correct, erase or transfer your personal data, restrict or object to processing, or complain to a data protection authority. These rights may apply to website, payment or support data, even though your timers stay local.

The developer does not sell your timer data. For requests relating to support correspondence or payment records received by the developer, use the contact address below. Providers may need to handle requests about data they control.

The developer cannot access or restore timers stored only on your device. Manage those through the app or your device settings.

13. Changes to this policy

Updates to this policy will appear here with a revised date. Material changes to the app’s data handling will also be described in the relevant release notes. Any new processing must meet applicable notice and consent requirements.

Contact

For privacy questions or requests about the app, website or support correspondence, contact:

info@neuratim.com