Privacy

Last updated: 11 October 2026

In short

Deeck works on your iPhone. Your Victron devices' readings, Bluetooth keys, history and energy data stay on your phone: we never send them to our servers.

You can use the whole app without an account. If you create a Deeck ID (optional), we store your system's configuration and a little account data on our server — never the data your system produces. No advertising trackers, no third-party SDKs.

Without an account

Everything stays on the device: Bluetooth keys (in the iOS Keychain), device list, readings history, preferences, alarm rules. Backups, if you enable them, live in your own iCloud, protected by Apple.

Without an account there is no personal data on our server: only an anonymous installation identifier and, if you use Deeck Bridge or notifications, your phone's push token (see below).

With a Deeck ID (optional account)

A Deeck ID is only needed for features that have to recognise you: Pro tied to you as a person, pre-order codes, referrals, remote bridge and settings backup. In the welcome screen you can choose “Continue with Apple”, “Continue with Google” or “Continue without an account”.

You sign in with Apple or Google (identity, email and name only): we never handle passwords. With Apple you can use “Hide My Email”, and we only see the forwarding address.

What we store: your Apple or Google user identifier, your email, your name if you give it, creation and last sign-in dates, and your consent choices. Optionally, your system profile: vehicle type (campervan, van, boat, off-grid, other), battery chemistry and capacity, the location you chose for weather forecasts (city name and city-level coordinates) and the app language.

Your system configuration, synced across your devices: alarm thresholds and settings, reserve, units, the list of your devices with the names you chose, device type and identifier, forecast location, and whether VRM or a bridge is connected. Of each device we keep only type and model (e.g. “SmartShunt 500A”) and when it was first and last seen — not its Bluetooth address.

What we never store: readings, history, energy data, VRM credentials or tokens, real-time location. No GPS tracking.

Purchases

Deeck Pro is bought on the App Store; Apple handles payment and we never see payment details. To tie Pro to your Deeck ID we keep a purchase identifier (our account token, the original transaction identifier and the product identifier).

Waiting list, pre-orders and invites

When you join the list with Sign in with Apple we receive and keep: the identifier Apple assigns to you for Deeck, your email (or Apple's private relay address, if you choose to hide yours), your name if you share it, the language of the site, your country if known, technical details of your device (type, system version, browser, screen size, the page or campaign you came from; the exact iPhone model comes from the app the first time you sign in there), who invited you, the state of your pre-order offer, your pre-orders and refunds, and your invite rewards (credits and partial refunds). Card details never reach Deeck: they stay with Paddle, and we only receive the outcome, the amount and the order identifiers.

We use them to keep your place on the list, show you your offer, activate Pro on your Apple ID, run the invite program (credits and partial refunds) and send you the emails about your order: performance of a contract. Informational emails about the launch are based on your consent, and every one of them has an unsubscribe link.

We keep these data for 24 months after the launch, or until you unsubscribe from the list; accounting records of pre-orders and refunds are kept for as long as the law requires. They are processed by Cloudflare (hosting and database, EU region), Paddle (payments; as merchant of record it receives your email, country and payment details and is an independent controller for the payment), Resend (email delivery) and Apple (Sign in with Apple). You have the rights described below: to unsubscribe or have these data deleted, use the link in any of our emails or write to privacy@deeck.app.

Usage events (“Help improve Deeck”)

To learn which features really matter we record a few product events — for example “app opened” or “device detail” — with some technical properties (app version, device type), the time, the anonymous installation identifier and, if you have a Deeck ID, your user identifier. We do this ourselves, without third-party SDKs, and keep the events for 12 months.

The “Help improve Deeck” switch is on by default and you can turn it off at any time in Settings: from then on nothing is sent.

Notifications and Deeck Bridge

To deliver alarm notifications we keep your phone's push token (and its environment, test or production), tied to the installation. If you use Deeck Bridge, the bridge on your Raspberry Pi or GX sends alarms through our relay, which forwards them to Apple's push service: the relay keeps only the bridge's activation token and, if you have a Deeck ID, the link to your account. Notifications are for alarms and product communications; never marketing without your explicit consent.

Remote features via VRM

If you connect a Victron VRM account, Deeck talks directly to Victron's VRM servers from your phone, with the credentials you provide. They never pass through us and we don't store them: on our server we only know that VRM is connected.

Weather forecast

The solar forecast uses your system's location (set manually, taken from VRM or from the phone once) to request weather data from Open-Meteo.com, straight from your phone. Only the coordinates are sent, with no account or identifiers.

This website (deeck.app)

The site is hosted on Cloudflare Pages. To deliver and protect the pages, Cloudflare processes technical connection data (IP address, browser type, page requested). We also use Cloudflare Web Analytics, which uses no cookies and gives us only aggregate statistics that do not identify you.

We also run a cookieless counter of our own: on every page, and at a few steps such as joining the list or opening the pre-order, your browser sends our server a small signal with the page, the language, where you came from (campaign, invite link or referring site) and the type of device (iPhone, Android or computer). It carries no identifiers, we do not store your IP address and the data is only added up per day: we cannot trace it back to you. Legal basis: our legitimate interest in understanding how the site is used.

We also use Google Analytics 4 (Google Ireland Ltd.) with Google's Consent Mode. Until you accept, Google Analytics sets no cookies and receives only anonymous signals, without cookies or identifiers (for example that a page was viewed), which Google uses in aggregate. If you accept, it sets the _ga cookies (they last up to 13 months) and collects usage data such as pages viewed, approximate location (country and city), device and browser; it does not store your IP address. Advertising features are switched off: we do not use this data for ads or profiling.

You can change your mind at any time with “Cookie preferences” at the bottom of every page. Legal basis for the Google Analytics cookies: your consent. Google may process this data in the United States under the EU–US Data Privacy Framework.

Where the data lives and who processes it

Account data is stored on Cloudflare (Workers and the D1 database) in the European Union region; bridge tokens in Cloudflare KV; the website on Cloudflare Pages.

Apple processes Sign in with Apple, push notifications and purchases; Google processes Google Sign-In, only if you choose it; Victron processes your system's data on VRM, with your credentials; Open-Meteo processes weather requests. Any transfer outside the EU happens only through these providers, under the standard contractual clauses or Data Privacy Framework each of them adopts.

Contact form: your name, email and message are used only to reply to you and are kept until the request is closed.

Why we may process it

To provide the service you ask for (account, configuration sync, Pro tied to you, bridge): performance of a contract. For usage events and product emails: your consent, which you can withdraw in the app. For security and abuse prevention (rate limits, technical logs kept for a few days): our legitimate interest.

How long, and how to delete

Account data is kept for as long as the account exists. You can delete it in the app from Settings → Deeck ID → Delete account: we delete the user, profile, configuration, devices and purchases; usage events and push and bridge tokens are anonymised (we remove your identifier, only the installation's remains). Usage events expire after 12 months anyway.

The app keeps working without an account, with the data on your phone.

Your rights

You can access your data, correct it, delete it (in the app or by writing to us), export your configuration and withdraw consents in the app. For any request write to privacy@deeck.app; you also have the right to lodge a complaint with your country's supervisory authority.

Children

Deeck is not intended for children under 16 and does not knowingly collect their data.

Controller and contact

Data controller: Deeck. For privacy matters write to privacy@deeck.app. If this page changes substantially we update the date above and, if you have a Deeck ID, tell you in the app.