Privacy Policy

About Drivie

Drivie is an independent app for Homey. Homey is a trademark of Athom B.V. Drivie is not affiliated with, endorsed by or sponsored by Athom B.V.

Privacy

A few technical details are needed for the app to work. They are listed below. The app talks directly to your Homey and to Athom’s account service to sign you in. Your login tokens are held in your device’s keychain, and your favourites and settings stay on your own devices, including the watch app on Apple Watch or Wear OS which talks directly to your paired phone. If you enable iCloud sync on iOS, or if Android Auto Backup to Google Drive is enabled on your device, your favourites and settings are stored only in your own personal iCloud or Google Drive storage; we have no access to it. The app contains no advertising and does not track you for advertising.

For push notifications, such as refreshing the widget when a device changes or a car notification on the CarPlay/Android Auto screen, the Homey companion app sends messages through the platform’s usual push service: Apple Push Notification service (APNs) on iOS, Google Firebase Cloud Messaging (FCM) on Android. Apple and Google see your device’s push token and the content of the message. This way the app does not need to hold its own connection open.

Rather than every Homey holding a sending key from Apple or Google, the companion app sends those messages through a small, separate key service at Cloudflare. That service passes each notification on to Apple or Google and sees its content while doing so, such as the text of a car notification or what is on a card. It does not keep that content, not even in a log. Apart from that one small key service there are no servers of our own.

The key service also checks that a notification only goes to phones registered for your Homey. For that it keeps, per Homey, a hash of a key the companion app creates itself and that never leaves your Homey. Per push token it keeps a hash of the token, together with your Homey’s ID, an ID for your phone, the platform, the kind of token, and when it was registered and last refreshed. The token itself is not stored in readable form. When registering, the app sends along the session token it already uses to talk to your Homey, and the key service asks Athom, the maker of Homey, whether that token gives access to that Homey. It does not keep the session token, but it does remember a hash of it for ten minutes so it need not ask Athom again on every registration. When your Homey’s key is registered, the key service uses your session to read the Drivie device on your Homey. That way it checks that the fingerprint the app offers matches the companion’s. It stores nothing in the process. It also counts how many notifications go out per Homey and per token each day, under a hash, and deletes those counters the next day. During registration it also counts requests per hour for each IP address and each Homey, again under a hash. Such a counter only applies to that hour and is deleted the next day.

Subscriptions run through Paddle as Merchant of Record; we receive no payment details.

To recognise your Homey for a Drivie Pro subscription, the companion app uses a random Drivie ID it generates itself, never your account, email address or name. The key service records which Homey cloud ID that Drivie ID belongs to, and when the two were linked, so that a subscription applies to one Homey only. Your Homey’s cloud ID is also stored with the hashes described above, and we use it to let your device know that something about your subscription has changed.

For a Drivie Pro subscription, the key service keeps a subscription record per Drivie ID in Cloudflare’s storage (Workers KV). It holds Paddle’s subscription ID and customer ID, the subscription’s status (for example trial, active, past due or cancelled), the end date of the current period, any scheduled change or cancellation, the billing period (monthly or yearly) and whether it concerns Paddle’s test or live environment. It also keeps lookups from Paddle’s subscription ID and customer ID to your Drivie ID, and from your Drivie ID to your Homey’s cloud ID. Your name, email address, address and payment details are not part of it: only Paddle has those. If a notification from Paddle cannot be tied to a Drivie ID, the service keeps the kind of notification, Paddle’s subscription ID and customer ID and the time, so it can still be matched later. If we give you Pro by hand, for example through support, that is kept with a note and an end date of at most one year in the same storage. A checkout code that ties your Drivie ID to a payment in progress is kept for six hours and deleted after the payment. For device authentication when a push token is registered, it also keeps a hash of the public key of the phone that registered the token first (token_owners), so only that phone can reuse or unregister the token, along with a blocklist of blocked token hashes in case of misuse (blocked_tokens). It counts failed attempts to open the service’s admin routes for fifteen minutes per IP address.

If you choose “Log in with Homey” on the order page, you sign in with Athom, the maker of Homey. The key service uses that sign-in once to fetch the list of your Homeys and see which ones run Drivie. It does not use or keep your email address, name or other account details that Athom sends along, and it does not keep Athom’s access token either. If more than one of your Homeys runs Drivie, it keeps their names for five minutes so you can pick one. The basis is carrying out your request to order Pro (Article 6(1)(b) GDPR).

Location and activity

If you use places or rides (Drivie Pro), the app uses your phone’s location, even when the app is closed or not in use. That is how the app notices that you arrive at or leave a place and recognises when a ride starts and ends. The app asks for your permission first, and you can withdraw it at any time in your phone’s settings.

To see that you are driving, the app also uses your phone’s activity recognition (Motion & Fitness on iOS). This recognition happens on your phone itself and is only about driving.

Your location and this activity data are processed on your phone. Your own Homey receives the places you save (name, spot and radius) and the events: that you arrived at or left a place, that a ride started or ended, and the car’s status. That goes over the same connection to your Homey as the rest of the app. The short troubleshooting log on your Homey (see above) mentions arrivals and rides by place name, without coordinates; its last lines only reach us if you send a support request with diagnostics yourself. Your location history does not go to our servers and we do not keep it.

On iPhone, the location card on the lock screen is started with a push message that carries the place name. That message goes through our key service to Apple, which does not store the content (see the push notifications paragraph above).

Without location, places stop working. Without activity recognition, rides are only recognised through CarPlay or Android Auto. The rest of the app keeps working. On the Locations screen (when choosing an area on the map or searching for an address), map tiles and address searches are fetched directly from Apple Maps (MapKit) on iOS and from OpenStreetMap and Nominatim on Android, so those services see the area you view and your search query. The basis is your consent (Article 6(1)(a) GDPR).

Who processes your data

The controller is Cyril Hendriks, trading as Namiddag, based in Belgium. You can reach us at info@getdrivie.com.

For a Drivie Pro subscription, Paddle is the seller and is itself responsible for your payment, invoice and address details. Those never reach us.

What for, on what basis, and for how long

Your device’s push token and your Homey’s Drivie ID are used to deliver notifications and to know whether your subscription is running. The basis is performance of the contract (Article 6(1)(b) GDPR): without them the app cannot do what you installed it for.

The hashes the key service keeps, and the session token it checks, make sure notifications only reach phones of your Homey and that nobody else can send notifications through the service. The basis here is again performance of the contract (Article 6(1)(b) GDPR) and, for the security of the service, our legitimate interest (Article 6(1)(f) GDPR).

The push token belongs to your device and is deleted as soon as you remove the device in the Homey app. The key service deletes what it holds for a token as soon as Apple or Google report that the token is no longer valid, as soon as you sign out in the app, or once the phone has not refreshed the token for 90 days. Your Homey’s key hash is kept for as long as your Homey uses Drivie. If the companion registers a new key after a reinstall, the new one replaces it. If we revoke your Homey, for example because of misuse, it stays revoked, even after a new registration. That lasts at most 12 months after the revocation, unless we lift it sooner. The hash stays all that time; after that the service deletes the hash automatically. The link between your Drivie ID and your Homey is kept too, and is recorded again whenever a new key is registered. The service deletes neither automatically: if you remove the companion app, email info@getdrivie.com and we will delete both. The Drivie ID belongs to your Homey and exists for as long as the companion app is installed on it.

We keep the details of your Pro subscription (Paddle’s subscription and customer numbers, status and billing period) for up to 12 months after your subscription ends; after that the key service deletes them automatically. It deletes payment notifications we could not link to an installation after 90 days. While your subscription runs, the basis is performance of the contract (Article 6(1)(b) GDPR). For the twelve months after, it is our legitimate interest in recognising you as a returning customer and handling questions, disputes and refunds (Article 6(1)(f) GDPR). What your notifications need to work (your Homey’s key hash and your phones’ push tokens) is kept for as long as you use Drivie, under the rules above. If you want us to delete everything we hold about your Drivie installation, email info@getdrivie.com with your Drivie ID. You can find it in the Drivie companion’s settings on your Homey, with a button to copy it. We then delete the related data in one go. If several Drivie installations share one Homey, that Homey’s data (key hash and push tokens) stays until the last installation has been deleted. If we revoke a Homey’s access to Drivie, for example because of misuse, we keep that Homey’s ID and the time of revocation so the block can be enforced, for at most 12 months after the revocation; after that we delete them automatically. If you ask us to erase your data while such a block is in place, we keep only those two items until that period has ended. The basis for this is our legitimate interest in preventing misuse (Article 6(1)(f) GDPR). Cloudflare holds the data as our processor; Paddle keeps your payment and invoice details as an independent controller under its own privacy policy.

The app keeps a short background log of what happens, so a fault can be traced afterwards. That log overwrites itself and goes to your own Homey; it stays within your household. We see it only when you send it to us yourself. The basis is our legitimate interest in fixing faults (Article 6(1)(f) GDPR).

If you ask a question through Need help? in the Drivie companion’s settings, your question, your email address and a diagnostics report reach us: the companion’s version, the number of locations, whether Pro is active, and for each paired phone its name, platform, model, app version, when it was last seen and the last 40 lines of its log. You send this yourself, and you can also email without diagnostics. The message goes to our key service at Cloudflare, which sends it as an email to our mailbox through Cloudflare Email Routing and keeps nothing of it. The legal basis is your consent (Article 6(1)(a) GDPR). To limit abuse, the service counts requests per IP address and per Homey, only under a hash (legitimate interest, Article 6(1)(f) GDPR). If you send a message through the contact form on this site, your name, email address, message and the page’s language also go through our key service and Cloudflare Email Routing to our mailbox. The service keeps nothing of it. The legal basis is our legitimate interest in answering your question (Article 6(1)(f) GDPR). Here too, the service counts requests per IP address, only under a hash, to limit abuse.

If you sign up on this site to hear about Drivie, we keep your email address, your language and when you gave consent, to send you one message when Drivie is released. It is kept in a separate database at Cloudflare, within the EU. The legal basis is your consent (Article 6(1)(a) GDPR). Once that message has been sent, we delete your address. To come off the list before then, email info@getdrivie.com. If you unsubscribe, we delete your address and keep only an irreversible code of it, with the date you unsubscribed, so nobody can sign you up again through the form, you included; if you do want news again, get in touch through the contact page. We keep that code for as long as we send messages about Drivie; once we stop, we delete that list too (legitimate interest, Article 6(1)(f) GDPR). To limit abuse, the sign-up service counts requests per IP address; that address is used only for this, briefly, and is not stored with your sign-up (legitimate interest, Article 6(1)(f) GDPR).

Who receives it, and where

Notifications travel via Apple (APNs) on iOS and Google (FCM) on Android. Your subscription runs through Paddle. The key service runs at Cloudflare, which acts as our processor for it. Through Cloudflare, notifications go to Apple and Google, the hashes described above are stored, and a question through Need help? or a message through the contact form reaches our mailbox via Cloudflare Email Routing. To check a registration, the key service shows your app’s session token to Athom, the maker of Homey, which issued that token in the first place. This website runs on Vercel. To see how many people view which page, how often someone signs up, starts an order or uses the contact form, and how fast the page loads, we use Vercel Web Analytics and Speed Insights, without cookies and only as aggregated figures (legitimate interest, Article 6(1)(f) GDPR). We also count a few clicks as anonymous events, such as switching language, opening a question in the FAQ or starting an order. We only send what you did and where, never your name, email address or other personal data. Beyond that Drivie shares no data with anyone: no advertising, no resale.

On the checkout page, Paddle’s payment environment (Paddle.js) loads, and with it code from ProfitWell, Paddle’s subscription management service (Retain). Your IP address therefore reaches Paddle, even if you don’t buy anything. Loading the page sets no cookies; during checkout Paddle uses what it needs for the payment and to prevent fraud. Paddle does so as an independent controller; see Paddle’s privacy policy.

Those parties may process data outside the European Economic Area. That happens under an adequacy decision of the European Commission or the standard contractual clauses.

Deleting your data

You can erase everything Drivie keeps about your phone yourself: in the app under Settings and Delete account, or without the app through the Homey app. The Delete account page explains step by step what is erased, how long we keep the rest and what you can still do yourself, such as deleting your Homey account at Athom.

Your rights

You have the right of access, rectification, erasure, restriction of processing, data portability and objection. Write to info@getdrivie.com. Because we do not know you by name, removing the device in the Homey app is usually the fastest route: that clears everything held for that device on your Homey. If you also sign out in the app, the key service deletes that phone’s push tokens. You can withdraw any consent you gave at any time; that does not affect what happened on the basis of it before.

If you disagree with how we handle your data, you can complain to the Belgian Data Protection Authority or to the supervisory authority in your own country.