NowLine — Privacy Policy

Effective date: 23 October 2026  ·  Version 1.4

This policy describes how the NowLine mobile app for iOS and Android handles your data. NowLine is published by Tilveno, an individual entrepreneur registered in the Republic of Armenia.

This policy covers the app only. The tilveno.com website has its own website privacy policy.

The short version

• There is no account. NowLine never asks you to sign up, sign in, or give us your name or email.
• Your custom labels stay on your device and are not transmitted anywhere. Analytics do name the city or time zone of a clock you add, move or remove — as the app's own index names it, never by your label — and which theme, language, clock format, temperature unit and vibration setting you use, and whether the weather is on.
• Clocks of cities show the weather there. To get it, the app sends the coordinates of those cities — never your own position — to our weather server, which sees your IP address.
• Anonymous usage analytics, diagnostic logs and crash reports are collected, and you can turn them off in Settings → Privacy.
• No advertising, no ad networks, no data brokers. We do not sell personal data.

What stays on your device

The following never leaves your phone. It is written to the app's private storage — an SQLite database and the system preferences store — and is not transmitted to us or to anyone else:

• your list of clocks as a whole, its order, and any custom labels you give the clocks (the analytics below name one clock when it is added, changed or removed; the list is never uploaded);
• the flags that remember whether you have seen the tutorial and the rating prompt;
• the weather forecast for each city on your clocks, which is deleted 7 days after it was fetched;
• the latest result of the location lookup described below, with the public IP address it was made from (the city it found is named in the diagnostic logs; the IP address is never sent).

We hold no copy of any of it. There is no account to close and no server-side backup. Deleting the app removes all of it from your device. See Deleting your data.

Usage analytics, diagnostic logs and crash reports

Who processes it. PostHog, on their European instance (eu.i.posthog.com). Analytics and crash data are sent there and are not transferred outside the EU by us.

How you are identified. By a random identifier generated on your device by the analytics SDK. It is not your name, your email, your phone number, your Apple or Google account, or your device's advertising identifier. We cannot use it to work out who you are.

What is sent. Which features are used — not what you type into them. The events are: a clock added, deleted, reordered or relabeled; a search performed; the timeline dragged; the paywall shown; a purchase succeeded, failed or was restored; the theme, clock format or language changed; the outcome of each location lookup; the outcome of each weather update; the temperature unit changed; the weather switched on or off; and how you responded to the rating prompt. Each event carries a few technical parameters, such as how many clocks you have or how many results a search returned. Events about a clock — added, deleted, moved or relabeled — name that clock: its city or zone as the app's own index names it, its time zone, and a random identifier of the clock. Events about the weather carry only counts — how many cities were updated, from which source, how long it took — never a city or its coordinates.

Your settings. With analytics on, the app also records the current value of six settings — theme, language, 12- or 24-hour format, temperature unit, vibration and whether the weather is on — against the same random identifier, so that we can count how many people use each. They are sent when the app starts and when you change one of them, and they stop with the same switch.

Diagnostic logs. The app also sends a log of what happens in it, so that a defect can be followed from launch to the moment it occurred: how long startup took, screens opened, buttons tapped, settings changed (the old and the new value), searches (the length of the query and the number of results), how the location lookup went (whether it answered, how long it took, and the approximate city, country and time zone it found), which city the app marked as yours and offered in search, your device's own time zone setting, how a weather update went (the same counts as its event), and the store's answers during a purchase. Log records follow the same rules as events: never your labels, your search text or your feedback, never the text of an error, and they stop with the same switch.

What is never sent. The custom labels you write, the text you type into search, and what you write in feedback. A search event or log records the length of the query and the number of results, never the query itself. Nor is your IP address, or the coordinates the location lookup returns.

Crash reports. When the app throws an unhandled error or crashes, the error, its stack trace, and the device model, operating system version and app version are sent through the same service. This is the app's only crash channel.

Screen recording. The analytics SDK supports session replay. It is switched off in the versions published on the App Store and Google Play and runs only in internal development builds — where text and images are masked regardless. Allowing analytics is not the same as allowing a recording of your screen, so we do not treat one as consent for the other.

Turning it off. Settings → Privacy → Share usage data. When it is off the SDK is never started at all, rather than started and silenced. Please note the consequence: diagnostic logs and crash reports travel through the same SDK, so switching analytics off also stops them. There is no second channel that stays on.

Retention. Events are held by PostHog on their EU infrastructure. On the plan we use, PostHog guarantees to retain them for one year. We want to be precise about what that means, because it is a guarantee to keep data rather than a promise to destroy it: we cannot tell you that a given event is erased on a fixed date. What we can tell you is that we never export events or copy them anywhere else, that we hold no second store of our own, and that you can stop new events being created at any moment in Settings → Privacy. If you want data erased rather than left to age, see Deleting your data.

Diagnostic logs are kept for 14 days and are then deleted by PostHog.

Approximate location from your IP address

NowLine uses your approximate location for three things: to pre-select a sensible first city the first time you open it, to mark the clock of the city you are in, and to offer that city at the top of search. To find it, the app makes an HTTPS request to ipwho.is, falling back to freeipapi.com if that fails. Your device's public IP address is visible to that service as part of making the request — that is how IP-based geolocation works — and the service returns an approximate city, country and time zone.

• When. Every time you start the app, and again when you return to it after it has been in the background for more than an hour; within that hour the answer it already has is reused. The request is repeated because where you are can change between launches — you travel, or your network changes — and an answer kept forever would mark the wrong city.
• What is kept on your device. The latest answer, together with the public IP address the service reports back, is kept in local storage on your device: the app shows your city from it before the network replies, and falls back to it when the request fails. A new answer replaces it. Clearing the app's data, or uninstalling the app, removes it.
• The location lookup does not go through us: your IP address reaches only the location service. The approximate city, country and time zone the lookup found do reach us, in the diagnostic logs above (kept 14 days), so that a wrong city or a missing mark can be traced; they stop with the same switch. Our weather server, described below, is a separate request.
• There is no separate switch for this request. Turning analytics off stops what is sent to PostHog, not the location lookup.
• The result is approximate — city-level at best. It is often wrong behind a VPN, which the app detects by cross-checking against your device's own time zone setting.
• NowLine never requests the GPS or precise-location permission. There is no permission prompt because no device location API is used.

In the App Store and Google Play questionnaires this is declared as coarse / approximate location, shared with a third party, not linked to your identity, and used for app functionality and for analytics — analytics because the events about a clock name its city, your first clock is chosen from where you are, and the diagnostic logs name the city the lookup found.

Weather

A clock of a city shows the weather there. To get it, the app sends the coordinates of the cities on your clocks — the cities, never your own position — over HTTPS to our weather server at weather.tilveno.com. The server runs on Cloudflare Workers; Cloudflare runs it for us and sees your IP address as part of the request. The server asks MET Norway for the forecast, or WeatherAPI.com when MET Norway does not answer. They see only our server, not your IP address.

• When. When you open the app, return to it, or add a city — and only for the cities whose forecast on your device has expired. A forecast less than an hour old is not asked for again. Clocks of time zones and UTC offsets send nothing.
• What our server keeps. Each city's forecast, stored under its coordinates until the forecast expires — up to an hour — so that the next request for the same city is answered without asking MET Norway again. Nothing in it tells who asked. Cloudflare keeps the server's logs, which may include your IP address, for 3 days, so that we can find faults; we do not copy them anywhere.
• If our server cannot be reached, the app asks MET Norway (api.met.no) directly. MET Norway then sees your IP address and the cities' coordinates.
• What is kept on your device. The forecast of each city, deleted 7 days after it was fetched. Clearing the app's data, or uninstalling the app, removes it.
• The weather can be switched off in Settings → Display → Weather. When it is off, the app sends no city coordinates to weather.tilveno.com or api.met.no. Turning analytics off stops what is sent to PostHog, not the weather update.

Your first clock is usually your own city, so the list of cities can hint at where you are. In the store questionnaires the weather is part of the approximate location declared above.

Purchases

NowLine offers one optional one-time in-app purchase, which removes the limit on how many clocks you can add. It is not a subscription and there is no recurring charge.

The payment itself is handled entirely by Apple or Google. We never see your card number, billing address, or Apple or Google account. The store tells the app only whether a valid purchase exists.

The app does send an analytics event when a purchase completes or is restored, and that event includes the displayed price. In store terminology this counts as purchase history, in the analytics category, not linked to your identity.

Email you choose to send us

If you use the in-app feedback form, or write to support@tilveno.com, your own mail app opens with the app version, your device model and operating system version, and your language code already filled in, so that we can reproduce what you are describing. You see the message before you send it, and nothing is sent unless you send it. We use what you write only to answer you.

Who else receives data

That is the complete list. There are no advertising networks, no attribution or tracking SDKs, no data brokers, and no sale or sharing of personal data for advertising purposes. NowLine does not ask for App Tracking Transparency permission because it does not track you across other companies' apps or websites.

Children

NowLine is not directed at children under 13, or under 16 where local law sets that higher age, and we do not knowingly collect personal data from them.

Your rights

If you are in the European Economic Area or the United Kingdom, the GDPR gives you rights over your personal data. Our legal bases are:

• Legitimate interests (Art. 6(1)(f)) for the pseudonymous usage analytics, diagnostic logs and crash reporting that let us find and fix defects and decide what to build. You can object at any time, with one switch, in Settings → Privacy;
• Performance of a contract (Art. 6(1)(b)) for handling the in-app purchase.

You have the right to request access to your data, correction, erasure, restriction of processing, portability, and to object to processing. You also have the right to complain to your national data protection authority.

One honest limitation follows from having no accounts: analytics events carry only a random device identifier, and we have no way to connect it to you, your email or your device. This is processing that does not require identification (Art. 11 GDPR). In practice, turning analytics off in Settings stops all further collection immediately, and events already collected stay where they are — in our provider's EU storage, never copied out — under the retention described above. See Deleting your data for the full picture, including how to ask us to erase them.

Changes to this policy

If this policy changes we will update this page and the effective date at the top. Changes that affect what is collected will also be noted in the app's release notes.

Contact

Privacy questions and requests: privacy@tilveno.com
App support: support@tilveno.com

Tilveno · Republic of Armenia. Registration details are on the legal page.

See also: End User License Agreement · NowLine support · Deleting your data