Нейвprivacy policy · version 2026-09-21

Українська →

Privacy Policy of the Neiv app

Edition of September 21, 2026. Document version: 2026-09-21.

In short

Neiv is a navigator that keeps your position on the road when the GPS signal disappears or is distorted. To do that, the app reads data from your phone and from your car.

By default no data about your trips leaves your phone for our server until you allow it yourself. The app has no registration and no account; we ask for neither your name, nor your email, nor your phone number. Navigation works in full even if you choose “Send nothing”. A few service connections to our server the app makes always—they carry neither your route nor your trip recordings, and the full list of them is in the section “What the app always does”.

Separately from the sending levels there is a “Traffic map” switch. It is off by default, is turned on and off on its own, and has its own section below.

The app has a paid subscription, a referral programme (“Invite a friend”) and a promotion for video authors. They work through our server, so they have a separate section below—this is the only part of the app where anything unrelated to your trips goes to the server.

Who processes the data

The Neiv app is developed by Kiril Polishchuk (Кирило Поліщук), who is also the personal data controller: Kiril Polishchuk, individual entrepreneur registered in Ukraine, tax ID 3811908712, 23B Sviatoslava Khorobroho St, apt. 53, Berdychiv, Zhytomyr Oblast, 13303, Ukraine, phone +380 97 277 47 44. The same details are given in section 2 of the Terms of Use. Privacy contact: [email protected].

The data is technically stored and delivered on our behalf by processors: Cloudflare, Inc.— servers and storage, including outside Ukraine (see “Where the data is stored and for how long”), and Telegram—only a copy of your letter from the feedback form. The device service mark (DeviceCheck) is verified by Apple. We pass them only what that task needs, and we require them to protect the data at least as well as described here.

What the app reads on your phone

This happens on the device and does not mean that the data goes anywhere.

What Why
Location (precise) to show you on the map, guide you along the route, and notice when the GPS signal cannot be trusted
Gyroscope, accelerometer, barometer, magnetometer to hold the position by dead reckoning when GPS is gone or lying
Speed and steering angle from your car through the OBD adapter the same: without data from the car, dead reckoning is impossible
Phone model, iOS version, app version, adapter model to understand which hardware a problem occurred on

Trip recordings are stored in your phone’s memory. You can review them on the “Trips” screen and delete them at any time together with the app.

What the app always does

A few connections to our server are what the app needs in order to work at all, so they happen at any sending level—including at “Send nothing”. The list is complete:

None of these connections carries your route, your trip recordings, your name or your contacts.

What is sent to us—and only by your choice

You choose the level at first launch and can change it at any time: Settings → Data and privacy.

Send nothing

No data about your trips leaves the app. All navigation features work as usual. The service connections from the section “What the app always does” remain—they carry neither your route nor your trip recordings.

Level 1. Connection passport (pre-selected on the consent screen)

Your route is not sent. When you connect the adapter in your car, the app sends a “connection passport”—no more than three per car × adapter pair, about 16 KB each. It contains:

The passport contains no coordinates, no route and no VIN. It is sent over any network, including cellular in “Wi-Fi only” mode. It goes only after you tap “Save choice” on the consent screen; if you turn it off there or choose “Send nothing”, no passport is sent.

What for: to tune speed reading for your particular car and to see which adapters really work.

Level 2. Problem reports—a trip sent by hand

There are no automatic reports by marker. A recorded trip can be sent only with the button on its card on the “Trips” screen—a separate action, one trip at a time. Such a trip travels in full, as at level 3: the route, the data from the car and the readings of the phone’s sensors. The button works at any level except “Send nothing”.

Without your tap nothing is sent.

What for: a trip in which the navigator got it wrong is the most valuable data for fixing it.

Level 3. Automatic sending of full trips (turned on and off by you)

Every recorded trip is sent by itself, without a tap. The entire trip is sent: the route from start to finish, the data from the car, and the full sensor stream of the phone—100 measurements per second (gyroscope, accelerometer, barometer). We do not thin this stream out: it is exactly where the behavior of the suspension and of the turns shows, which is what the level exists for.

We do not trim the start and the end of the route. That means the recording will show the place where you get into the car and where you leave it—usually home and work. We do this deliberately: the first minutes of a trip are where the scale factor for your particular car is picked up, and without them the level loses its point. The same applies to a trip you send by hand. If that is not acceptable for you, do not turn this level on and do not send trips by hand—then no trip goes anywhere.

What for: to work out exactly how your car model reports speed and angles, and to add it to the list of fully supported cars.

This is the largest amount of data about you, so this level is turned on by a separate confirmation and never turns itself on.

The traffic map—a separate choice

This is a separate switch, not a level on the scale above. It is off by default, is turned on separately, is turned off separately, and works at any chosen level—even at “Send nothing”. We ask about it on a separate screen because its purpose is a different one: not “to fine-tune dead reckoning for your particular car”, but “to build a shared map of travel times for everyone”.

What exactly is sent

To get permission to send, once a day the app shows the server a one-time service mark of the device from Apple (DeviceCheck): it proves only that this is a genuine device with our app, is not stored, and is linked neither to trips nor to the pseudonym.

The list above is complete: these are not “technical indicators”. It carries no name, no phone number, no email and no account—the app has no accounts at all. We receive neither your starting point, nor your destination, nor the route as a whole, and the first and last 500 metres of every trip are not recorded at all—precisely because that is usually home and work.

When it is collected

While the app is running and you are driving—on any trip, even without a planned route. This includes the background: if you minimise the app or lock the screen and it keeps running, collection continues. When the app is fully closed, no road data is collected: it does not start itself in the background. The app does not ask for the “always” location permission for this either.

Under which key

Every trip travels under its own one-time random code, created at the start of that trip and never repeated. It is not your pseudonym from the section below: the two data streams are never stitched together—neither on the phone nor on the server. That is why your trips do not add up into one history: we cannot tell that two trips belong to the same person.

How long it is stored

Whom it is passed to

No one except Cloudflare, on whose servers the data is stored (see “Who processes the data”). The only thing that leaves is the aggregated map itself, and it comes back to the users of the app, you included. Everyone gets the map regardless of whether you turned this switch on: access to it will never be a reward for data, and no paid feature depends on it.

How to withdraw, and what gets deleted

The switch can be turned off at any time: Settings → Data and privacy → Traffic map. At that very moment the app stops collecting, erases from the phone everything that has not gone out yet, and asks the server to delete the trips that were sent but not yet merged into the averages.

Honestly about the limit: a contribution that has already been merged into the averages cannot be taken out—there is no longer either your trip or its code in there, so there is nothing to look for. This is a property of an aggregate, not our reluctance; that is why we say it before you turn the switch on, not afterwards.

The estimate of your driving style stays on the phone

The app estimates how much faster or slower your driving is than average—in order to show you a more accurate travel time. That estimate is computed on the phone, stored on the phone and is never sent to the server. Turning the switch off does not erase it: it is not our data about you, it is your own calculation that goes nowhere.

Which trips are never sent—at any level

A pseudonym instead of a name

The data you have allowed to be sent is labeled with a random pseudonym that the app itself creates on your phone. The pseudonym is linked neither to your Apple ID, nor to an advertising identifier, nor to a phone number, nor to the car’s VIN.

You can replace it at any time: Settings → Data and privacy → Create a new pseudonym. After the replacement, what was sent earlier cannot be linked to what you send from then on. Deleting the app also destroys the pseudonym for good.

If you write to us through the feedback form

There is a feedback form in Settings. It is a letter you compose and send yourself, as a separate action. What travels with it:

There are no coordinates, no route and no trip recordings in the form. The message is stored in our database, and the server forwards a copy of it to the developer’s working Telegram chat—otherwise nobody would read it in time. The form itself says so, before the “Send” button. We keep the message until it has been dealt with and you have had a reply; to have it deleted sooner, write to [email protected].

When and how the data is transferred

A trip recording is cut into two-minute parts; each is compressed and sent separately during the trip—precisely because there is no Wi-Fi on the road, and after the trip the app is usually closed already.

The delivery mode is chosen in Settings → Data delivery:

If the connection dropped, the transfer continues from the same place at the next opportunity; parts that have already arrived are not sent again. After a successful transfer the copies of the parts are deleted from the phone—the trip recording itself stays with you.

The modes above govern what goes from you. Separately from them the app downloads the traffic map for your region—automatically and over cellular as well, with no switch of its own. The price is up to about 3 MiB a week; without it the travel time shown to you would be markedly worse. This is receiving a ready-made map, and it does not depend on the “Traffic map” switch with which you allow your own drives to be sent.

If you buy a subscription, take part in the referral programme or in the promotion for authors

This is a separate part of the app, and it is the only one where anything unrelated to your trips goes to our server. Everything described above does not apply to it, and vice versa.

Installation identifier. So that the server can tell whose subscription this is, the app creates a random installation identifier (the same one the app passes to the App Store as appAccountToken). It is created only at the moment you first buy a subscription or first open the “Invite a friend” screen. Before that no subscription is tied to you. It is not linked to your Apple ID, your email, or the advertising identifier.

The claim number for the starter minutes is a different number. The app creates it at first launch, before any purchase, and sends it together with the device mark (below) so that the same claim is not counted twice. It travels in the same request field as the installation identifier, but it is a different random number: it is linked neither to your subscription, nor to the trip pseudonym, nor to your Apple ID.

Starter free minutes and the device mark. So that the starter free minutes are granted once per device, the app asks Apple for a service mark of the device (DeviceCheck) and sends it to us together with the claim number. The mark contains none of your data and is not an identifier of a person; it is stored on Apple’s side, and all we see is the answer “this device has already been granted” or “not yet”. This happens at first launch, regardless of the sending level you chose, which is why it is also named in the section “What the app always does”.

It and the statistics pseudonym are two different things that never meet: the pseudonym labels trip data, the installation identifier labels purchases and rewards. We do not link them, and there is no referral code in the trip data.

What goes to our server:

What does NOT go—at any of these steps: your coordinates, routes, trip recordings, vehicle data, the telemetry pseudonym, contacts from your address book. The referral programme does not read your address book and sends invitations to no one: you pass the code to your friend yourself, however you see fit.

How long we keep it:

How to leave or delete. Write to [email protected] and give your participant code—we will delete your record in the referral programme and your promotion entries. This does not cancel the subscription: you cancel a subscription in your Apple ID settings, and our actions do not affect it.

How the reward arrives. For a friend who takes out a paid subscription you receive a 50% discount on your next charge on the monthly plan. Technically this is an App Store promotional offer: our server signs it for Apple, and Apple applies it—after you confirm the purchase yourself in the app. We see neither your payment details nor the amount charged. Free subscription days (the promotion for authors) work differently: there Apple moves the date of your next charge, or we grant the access ourselves.

Refunds. If a friend refunded the subscription, the reward for that friend is not credited. The terms of the referral programme are on the neiv.app/referral page. The promotion for authors is not open yet; its terms will be published separately.

Where the data is stored and for how long

The data that is sent is stored on Cloudflare R2 servers (infrastructure, including outside Ukraine—the cross-border transfer is needed to carry out your sending choice). Retention periods:

The operational request journal. Every call the app makes to our server leaves a technical line: the request path, the response code, how long the handling took, the app version, the iOS version and the first four characters of the pseudonym or identifier, if the request carried one. There are no request bodies, no coordinates and no texts of any kind in the journal. The lines are deleted automatically after 14 days: the journal exists so that we can see server failures, not people’s behaviour.

Whom we pass the data to

We do not sell data and do not pass it on for advertising or analytics. The app has no ad networks, no third-party analytics SDKs, no cross-app tracking. The data is received only by the processors from “Who processes the data”, and only for their own task: Cloudflare stores and delivers everything sent to our server; Telegram receives a copy of your letter from the feedback form (see “If you write to us through the feedback form”); Apple verifies the device service mark. Beyond them—only on a lawful demand from an authorized state body of Ukraine.

Your rights

Since we do not know who you are, your pseudonym is the only way to find your data. If you have replaced it or deleted the app, what was sent earlier can no longer be found, neither by you nor by us.

Children

The app is intended for people aged 16 or over and is not addressed to children. We do not knowingly collect the data of people under 16.

Permissions the app requests

Refusing any of the permissions does not block the app: it will work in a limited mode and will honestly say what exactly is missing.

Policy changes

The app will announce changes that expand data collection on a separate screen and will ask for consent anew. The date of the edition is always at the top of this page.

That is exactly what has been done with this edition: until you have confirmed it on the “What’s changed” screen, no data about your trips is sent from your phone—no matter which level is set in Settings. The service connections from the section “What the app always does” continue meanwhile: without confirming access the app could not even tell you what has changed.

What changed in the edition of September 21, 2026. We have not started collecting anything new: what is sent, the pseudonym, the traffic map and the retention periods have not changed by a single word. Two places changed. “Children”: the previous edition said “not addressed to children under 13”, now the threshold is 16, the same as in the Terms of Use. The subscription and programmes section no longer names the page of the promotion for authors: the promotion is not open yet, we accept no entries, and its terms will be published separately—the disclosure of what an entry would send is unchanged. This does not widen collection. The app still asks you to confirm the edition, because consent is recorded against a specific edition.

What changed in the edition of September 18, 2026. One item changed: “When it is collected” in the section “The traffic map—a separate choice”. The previous edition said road data is collected only while the app is open. Now it is collected while the app is running—including in the background, when the app is minimised or the screen is locked: otherwise a trip broke off every time you took a call or switched the music. What is sent, the one-time trip code, the first and last 500 metres that are never recorded, and the retention periods have not changed. Because this widens collection, the app asks about the traffic map again: an answer given under the previous edition is not carried over, and until you answer, no road data is collected or sent.

What changed in the edition of September 15, 2026. We have not started collecting anything new—this edition describes what the app was already doing but the policy was silent about. A new section appeared: “What the app always does” (the access and time check, the settings, the map catalogue, the vehicle profiles, the traffic map download, the one-time DeviceCheck device mark). The feedback form with its optional contact field, the operational request journal with its 14-day period, and the traffic map download over cellular are now described. The phrase “nothing is sent” has been made precise: without your permission no data about your trips is sent, while the service connections are always there. The rules about the sending levels, the pseudonym, the traffic map and the trips that are never sent have not changed by a single word.

What changed in the edition of September 14, 2026. A new section appeared: “The traffic map—a separate choice”. The app learned to build a shared map of travel times out of measurements from all drivers, and for that it needs the speed at which road segments are driven. This is a separate switch, off by default: it is not part of levels 1–3, does not turn on together with them, and is asked about on a separate screen. The rules about the sending levels, the pseudonym and the trips that are never sent have not changed by a single word.

What changed in the edition of August 30, 2026. A new section appeared: “If you buy a subscription, take part in the referral programme or in the promotion for authors”. The app now has a paid subscription, a referral programme and a promotion for video authors, and with them an installation identifier that is created only if you use one of them. The rules about trips, sending levels and the pseudonym have not changed by a single word.

Contact

[email protected]