Privacy Policy
2026-11-12
MINISTRY OF GOOD VIBES LLC (“we”, “us”) operates the Deck Pointer app and the deckpointer.com website. This page explains, in plain terms, what data either one touches, why, and what you can do about it.
Who's responsible
Deck Pointer is made by MINISTRY OF GOOD VIBES LLC, a company registered in Wyoming, United States. For this policy we're the data controller for the website's waitlist, and the customer of the processor named below for app crash reports.
Questions or requests about your data go to hello@deckpointer.com.
The short version
The app's controls work without an internet connection. Your phone talks directly to your PC or Steam Deck over Bluetooth — we never see that input traffic and it never touches our servers.
Published builds send product-usage events to PostHog and crash reports to Sentry. These help us understand setup and fix bugs; Bluetooth input, presets, and Actions are not sent to either provider. On Android and iPhone, optional free-games notifications use Firebase Cloud Messaging; on iPhone delivery also uses Apple's push notification service.
The website stores an email address only if you type it into the iOS waitlist form yourself, and only to send you the iOS test invite or update you asked for.
If you subscribe to free-game emails, the website keeps your email address and your settings in an account you can delete at any time. There are no ads in the app or on the site. To learn which of our own ads bring people to Deck Pointer, the Android and iOS apps and the website tell Google, Meta and TikTok about a few moments (an install, a first connection, a click on a store button): in the EEA, the UK and Switzerland only after you allow it, and you can turn it off anywhere (see “Ad measurement” under “Product analytics”). Product analytics use a random app-installation or browser identifier, never your email address; the data and providers are described below.
What stays on your phone
Deck Pointer keeps everything it needs locally: your theme, scroll settings, control presets, and the list of computers you've paired with (each entry has that computer's Bluetooth address and the name it broadcasts, so the app can reconnect and remember your layout for it).
Recorded Actions — the clicks, waits, and keystrokes you capture for one-tap replay — are stored in a file encrypted with AES-256-GCM, keyed to your device's secure key store — the Android Keystore on Android, the Keychain on iOS. That key never leaves the phone and can't be exported. Actions can include a password you typed, which is exactly why we encrypt them: they never leave your device and we can't read them.
We do not run our own cloud backup. Your operating system may back up or transfer settings, presets and saved hosts according to its backup settings. On Android, only deck_pointer_settings.xml is included; Actions, encryption keys, TV pairing identities and installation/attribution identifiers are excluded. On iOS, Action files and the connection log are excluded from backup, and the app's Action and TV identity keys use device-only Keychain storage. Uninstalling removes the app's local files; operating-system backups follow the operating system's retention and deletion controls. There is no app account to close.
What goes over Bluetooth
Deck Pointer pairs with your computer as a standard Bluetooth HID device — the same kind of connection a physical mouse or keyboard uses. All it sends are HID input reports: cursor movement, button and scroll state, keyboard scan codes, and gamepad axes and buttons. Typed text is converted into the same keystrokes a physical keyboard would send.
That connection is between your phone and your computer only. It doesn't pass through any server of ours, we can't see it, and we don't log it.
Crash reports
Connection diagnostics also include the Bluetooth radio and HID registration state, whether the app is in the foreground, whether a registration callback arrived, coarse callback timing, counts of recovery attempts and connected or subscribed hosts, and service-publication and advertising error codes. A report is linked to its random setup ID. These are codes, booleans and counts, without host names, Bluetooth addresses, key values or typed text.
If the app crashes, it sends an error report to Sentry (Functional Software, Inc.), our crash-reporting provider, hosted in the EU. A report can include: the stack trace, app version, device model, Android or iOS version, your phone's language setting, a random installation ID Sentry generates (not tied to your name or account — there isn't one), and a short trail of recent app actions (like “3 devices bonded” or “connect attempt”) with no device names or Bluetooth addresses in them. If the connection keeps dropping or cannot be restored, the app also sends one warning with the same short trail and the kind of computer (never its name), so we can see what happened without a crash.
We don't turn on screenshots, screen-recording, or Sentry's “send default PII” option, so your name, email, or exact location are never part of a crash report.
This exists for one reason: finding and fixing bugs. Our legal basis is legitimate interest in keeping the app working.
If you send a problem report from the app (Settings, the connection panel or the pairing guide), Sentry receives exactly what the form shows: the kind of problem you picked, the Steam Deck model and SteamOS channel you picked, the system version or computer description you typed, your optional note, any photos you attach, the app and phone details above, whether you restarted the phone or the computer, roughly how long the phone has been on (under 10 minutes, under an hour, under a day, or longer), the support code, the kind of computer and its Bluetooth stack version (such as “BlueZ 5.85”), whether the phone was connecting over Bluetooth or Wi-Fi, whether Wi-Fi is set up and how many Bluetooth attempts failed since the last working link, and the recent connection trail (the last few hundred connection steps kept on the phone, without names or addresses). Nothing is sent until you press Send report, and the report carries no email address unless you write one in the note. If you answer “Something else” in the first setup questions (which device you want to control, what you want to do), the few words you type go to Sentry as well, up to 200 characters; the codes you pick (device, task) also go to our usage analytics, the words never do.
When you finish the setup questions in the app, it also tells our own server (a database hosted by Supabase) the codes you picked (device, task), how the setup ended (connected or closed, the step you stopped on, how many connection attempts failed, how long it took), your phone's model, its system version and language, the app version and, if you came through one of our links, which link. The server adds your country from the connection; it does not store your IP address. If you typed words under “Something else”, they go to our server as well, up to 200 characters; they are used for one message to us (see below) and deleted right after, or within seven days. None of this carries your name, email, Bluetooth address or an account, because there are no accounts.
Product analytics
Website diagnostics also include unhandled JavaScript errors and rejected Promises (error type, message and stack trace) and Web Vitals: loading and interaction timing and layout shifts (LCP, INP, FCP, CLS). We redact email addresses and known sign-in parameters from these diagnostics before sending them to PostHog. Source maps are build artifacts used to link an error to our original code; they contain our code, not a visitor’s form entries.
On the website, PostHog Replay Vision uses AI (Google Gemini) to analyze session recordings for navigation problems and the steps leading to a lead, subscription or store click. We also record when an app button or subscription form is visible and which page or preset led to a store click. All input values, displayed email addresses and sign-in codes are masked before new recordings are sent; account pages are excluded from replay. Request bodies and headers and browser console logs are not recorded. This does not enable replay in the apps.
To improve text input across languages, app analytics also include the app language, system locale, the current input language when the keyboard reports it, and the receiving keyboard layout you selected. Android may also report language codes exposed by enabled keyboard subtypes; this list can be incomplete. iOS does not send its list of enabled keyboards. These are language codes and technical availability indicators, never typed text, passwords, clipboard contents, keyboard app names or identifiers.
Published builds of the app, and this website, send product-usage events to PostHog (PostHog, Inc.), processed in the United States. The app sends lifecycle events; events for connection attempts, successful connections, completed pairings, and connections that fail, drop or keep dropping; events for the first use of the trackpad, Live Typing and the gamepad; events for preset selection, layout saving and Action playback; and events for onboarding steps (started, device chosen, Bluetooth permission granted or denied, skipped or completed). On Android it also sends whether notifications were allowed during onboarding. On Android it also sends how you use the Free games section: opening it and a game's page, refreshing, sorting and filtering the list, the links you follow out of the app from a game's page (to claim a game, to the store's Steam Deck guide, to Steam reviews or Metacritic; the address is sent without its query), and what happens with the daily notification (received, shown or skipped, opened, switched on or off, and whether notifications are allowed). When a connection ends, the app sends how it ended, how long it lasted and in how many seconds input was sent (never the input itself). It also sends the steps of the connect wizard and of pairing, the search for a Steam Deck over Wi-Fi, the moments when it could ask for a store rating and what you did in the seconds after, and whether you opened the rating link in Settings. Wi-Fi problem events also say whether a VPN was on. The website records page views and selected clicks. We use these to understand use and improve setup. Connection events also carry the kind of computer the app connected to (for example Steam Deck, Windows PC or Mac; never its name or address), and problem events carry a reason code or a rough duration such as “under 2 seconds”. Settings shows the first characters of the random installation ID as a support code; it is sent nowhere unless you paste it into a bug report or email. Debug builds of the app and preview deployments of the site send nothing.
An app event carries the app version, device model, OS version, and a random installation ID PostHog generates. It never carries a device name, a Bluetooth address, anything you type, or the contents of a preset or an Action. Session replay and screen recording are switched off in the app, and no person profile is created, because there is no account to attach one to.
On the website the events include page views and selected clicks, with the page address, the referring page, and browser information. PostHog session replay may run on the website and can capture page interactions and visible page content, including text entered into fields, unless that content is masked by PostHog or client-side configuration. PostHog receives the source IP address with analytics requests from both the app and the website and may use it to infer approximate location. This policy does not state whether raw IP addresses are retained.
If you subscribe to free-game emails, the website also records the steps of subscribing and signing in (for example code sent, signed in, subscribed) and which settings you changed — never your email address or the code. Links in our emails carry tags that tell PostHog which email and which link brought you to the site.
Links on deckpointer.com/go (and the older short links /get, /app, /download and /install) record a visit with a random click ID, the channel the link was posted in, your device type and your country. Your IP address is not passed on to PostHog from these links and no cookie is set. On Android, the app reads once, from Google Play, which link the install came from (the Google Play install referrer) and sends it with that click ID as a single event, so we can tell which videos and posts bring installs; it carries no advertising ID, and the origin is kept as a property on later events. If the install came from one of our ads on Facebook or Instagram, Meta puts which campaign, ad set and ad it was into that referrer, encrypted; our server decrypts it and keeps those ad IDs and names with the install, and the app passes the origin to our payment provider RevenueCat, so we can see which ads lead to purchases.
We keep these clicks, and a few moments of each install, in our own database (Supabase) as well as in PostHog: the click and where it came from; the install; the two optional questions at the start of setup (what you want to control and where you heard of us, answered by choosing from a list, never typed); the first successful connection; the first trial or purchase (whether it was a trial, a subscription or Pro for life, its price and currency); and a once-a-day “opened” mark. They are tied only to the random installation ID the app makes on first launch, and carry no name, email, IP address, Bluetooth address or device name.
Free-game notifications (Android and iPhone): the app can tell you once a day when new free games appear, using Firebase Cloud Messaging, a service of Google LLC (United States); on iPhone it is delivered through Apple's push notification service. The app subscribes to a topic named after your phone's time zone offset (for example “UTC+3”), so the notification arrives around 18:00 your time. We keep no list of phones, tokens or addresses: our server sends one message to the topic. To deliver it, Google's service creates an installation identifier and a push token on your phone and processes them under its own terms; the app creates them only once notifications are allowed for the app and the bell on the Free games screen is on, and it leaves the topic when you switch the bell off. The notification text is put together on your phone from the public list of free games. You can turn it off with the bell on the Free games screen or in your phone's notification settings.
Per connected session the app also sends counts of what was used, never what was typed or pressed: for example how many characters were typed, how many keys, clicks and gamepad inputs there were, and how long the link held. It also reports once when what you do first matches the task you picked in the setup questions.
Ad measurement (Android and iOS apps, and website). We advertise Deck Pointer on Google, Meta (Facebook, Instagram) and TikTok. To learn which ads bring people who actually use the app, and to show our ads to people like them, the apps tell Google (Firebase Analytics, linked to Google Ads), Meta and TikTok, through their software kits, about a few moments: that the app was installed and opened, that onboarding was finished, the first connection to a device, the first time what you did matched the task you picked in setup, and that the Deck Pointer Pro screen was shown. They carry codes only (the kind of computer, Bluetooth or Wi-Fi, which Pro screen) and go with your phone's advertising ID and the identifiers those kits create. Trials, purchases and renewals reach Google and Meta from RevenueCat, and TikTok from the app and through our server, which passes RevenueCat's notification on without keeping it; with the price and currency, tied to the same identifiers. They never receive what you type, the names or addresses of your devices, your presets or Actions, or your email address.
On deckpointer.com the Google tag, the Meta Pixel and the TikTok Pixel record page views and clicks on the store buttons, and set their own cookies. Their automatic matching of email addresses and phone numbers is switched off: nothing you type into a form goes to them.
Your choice. In the EEA, the UK and Switzerland none of this runs until you allow it: the app normally asks after your first connection to a device. For a new Android install identified as coming from Google Ads, it asks before selecting onboarding so Google can retrieve the destination from that ad. The website shows a banner. Everywhere else it is on until you turn it off: in the app under Settings → Ad measurement, on the website with “Ad measurement” at the bottom of any page. To know whether to ask first, the Android app reads the country of your SIM card and mobile network on the phone, and the apps and the website ask our server for the country of your connection's IP address; neither is stored. The website also treats a Global Privacy Control signal from your browser as a no. On iPhone, iOS asks for your permission to track (App Tracking Transparency) after setup, the first time you reach the app's main screen, and nothing goes to Google, Meta or TikTok before you answer. If you say no, Meta and TikTok receive nothing from the app, Google receives the moments above without the advertising identifier and is told not to use them for ads, your purchases are not passed on to Meta or Google, and in the EEA, the UK and Switzerland the app does not ask about ad measurement, so none of it runs. On iPhone, RevenueCat also receives Apple's own attribution token for Apple Search Ads, which needs no tracking permission. Turning ad measurement off also deletes the identifiers the apps gave RevenueCat for it, so later renewals are not passed on. You can reset or delete your phone's advertising ID in the phone's settings at any time. Google, Meta and TikTok use this data under their own terms and policies and may also use it to improve their ad services: [Google](https://policies.google.com/privacy), [Meta](https://www.facebook.com/privacy/policy/), [TikTok](https://www.tiktok.com/legal/page/global/privacy-policy/en). Where the law requires it, our legal basis is your consent, which you can withdraw the same way.
Connection events also carry, when the computer reports it, the version of its Bluetooth stack (for example “BlueZ 5.85”), how many computers and phones your phone is paired with, and whether the phone's keyboard mode was already busy — counts and codes, never a device name or address. The app also reports when a pairing with a computer it knows disappears, when a session cannot start (Bluetooth off, permission withdrawn), and, if you close the setup without connecting, your answer to one question: whether the computer showed your phone in its list. If you connect a TV over Wi-Fi, connection events and problem reports also carry the TV's model as the TV reports it (for example “OLED55C1”) and which of the TV protocols the app used — never the name you gave the TV or its network address.
On iOS, TikTok event measurement runs only when ad measurement is enabled and you have also allowed tracking in the iOS system prompt. If you refuse either, TikTok event delivery stops and events the app held while waiting for your answer are discarded.
App permissions
Bluetooth (connect, advertise, and — on Android 11 and below — the legacy Bluetooth/Bluetooth Admin permissions): required to pair with and control your computer.
On iOS the app asks for Bluetooth; for local network access when you discover or connect to a Steam Deck or supported TV over Wi-Fi; for notifications when you turn on free-games notifications; and for tracking (App Tracking Transparency) the first time you reach the main screen. The background Bluetooth mode keeps the connection alive. The other items below describe Android permissions.
Notifications: shows the “Connected to <device>” status while a session is running and, while you leave it on, the once-a-day free-games notification; you can deny it and the app still works, just without those notifications.
Foreground service: keeps the Bluetooth connection alive while the app is in the background.
Internet: used to send product-usage events to PostHog and crash reports to Sentry, as described above. Bluetooth controls do not pass through our servers.
Advertising ID (Android; iPhone): read only for ad measurement, as described under “Product analytics”, in the EEA, the UK and Switzerland only after you allow it, and on iPhone only after you also allow it in the system's tracking prompt.
Photos: the app never asks for access to your photo library. When you choose a picture as a preset's icon, the system's photo picker hands the app only that picture; the app keeps a small copy on your phone and sends it nowhere.
Nearby Bluetooth discovery uses BLUETOOTH_SCAN on Android 12 and later. On Android 11 and earlier, discovery requires the system's location permission (ACCESS_FINE_LOCATION); the app uses it only to find nearby Bluetooth devices, not to read GPS coordinates. We do not request contacts, camera, microphone or broad storage/file access. PostHog may infer approximate location from the IP address as described above.
The iOS waitlist on the website
If you submit the form on deckpointer.com, we collect the email address, platform (iOS), and site language you provided. A honeypot field and a short-lived, in-memory rate limit on your IP address help keep the form free of bots. The waitlist function itself does not store the IP address; website hosting and PostHog analytics process IP addresses as described above.
We use double opt-in: the confirmation link is a signed token containing your email, platform, and language, valid for 24 hours, with nothing stored server-side until you click it.
Once confirmed, your email and the platform/language you chose are stored as a contact with Resend (our email provider) so we can send you the iOS update you requested, and a notification with the same details goes to our own inbox.
Free-game emails and your account
If you subscribe to free-game emails or sign in on deckpointer.com, we keep your email address, the stores you picked, whether emails are on, the site language you subscribed in and your browser's time zone, so emails show times you can use. You can change all of it on deckpointer.com/account/.
There is no password. To sign in we email you a 6-digit code and a link, valid for 10 minutes and usable once. The account and its settings are stored with Supabase, our database provider; the codes are mailed through our website by Resend.
You can switch the emails off or delete the account at any time on deckpointer.com/account/. Deleting removes your address and settings at once. Every email also has an unsubscribe link.
Deck Pointer Pro and purchases
Deck Pointer Pro is a paid tier of the Android app. The iOS app has no paid features yet: everything there is free. You can subscribe weekly or annually (some plans start with a free trial) or buy Pro once for life. Google Play takes the payment. We never see your name, email address, card or any other payment details.
To check what you bought and unlock Pro, the app uses RevenueCat (RevenueCat, Inc., United States), our purchase-management provider, which acts as our processor. RevenueCat receives from the app and from the store (Google Play on Android, the App Store on iPhone): an anonymous app user ID it creates on your phone; whether Pro is active and the status of the subscription or purchase (product, dates, trial, renewal, cancellation or refund); the price, currency and store country; Google Play or App Store order and transaction identifiers; and, as any server does, the IP address and basic technical details of the request (app and system version, language).
The app also attaches to that anonymous user three labels and one identifier, and nothing else: the codes of your answers to the first setup questions (which device you want to control and what you want to do, chosen from a list, never the words you typed under “Something else”); whether you used Deck Pointer before paid features existed (true or false); and, in published builds, the random installation ID that PostHog uses for the analytics above, so subscription events (started, renewed, cancelled) land on the same anonymous record in PostHog.
RevenueCat does not receive your name, email address, Bluetooth address, device name, anything you type or control with the app, or payment-card data. It may use this data only to provide its service to us, under its own terms and privacy policy.
Everyone who used Deck Pointer before paid features existed keeps Pro free, for good. The app recognises such installs on your phone and passes that mark on as the label above.
RevenueCat keeps the purchase record for as long as we use its service for the app, so Pro survives a reinstall or a new phone signed in to the same Google account or Apple Account; its own retention terms apply. Google and Apple keep your orders under their own policies. To have the record for your install deleted, write to hello@deckpointer.com with the support code from Settings and we will ask RevenueCat to delete it. RevenueCat processes data in the United States; see “International transfers”.
Who else touches this data
Vercel — hosts the website and its server functions (sign-ups, sign-in emails, the free-games pages), and sees ordinary web-server request logs (IP address, page requested) like any host does.
Supabase — stores the free-game accounts (email address and settings) and checks sign-in codes.
Resend — stores your waitlist contact and delivers our emails.
RevenueCat (RevenueCat, Inc.) — checks Deck Pointer Pro purchases on Android and iPhone and keeps your Pro status, processed in the United States. It receives an anonymous app user ID, the purchase and subscription status, product, price and currency, store country and Google Play or App Store transaction identifiers, plus the labels described under “Deck Pointer Pro and purchases” — never your name, email address or card data.
Sentry — receives app crash reports, as described above, processed in the EU.
Google (Firebase Cloud Messaging) — delivers the once-a-day free-games notification to phones that have it on (to iPhones through Apple's push notification service), processed in the United States. It receives a push token and the time-zone topic; it never receives your name, your email or what you do in the app.
PostHog — receives the product-analytics events described above, from published builds of the app and from this website, processed in the United States. Session replay is switched off in the app. Website session replay may run and can capture page interactions and visible page content, including text entered into fields, unless that content is masked by PostHog or client-side configuration. App events carry no device names or Bluetooth addresses.
If you use the in-app feedback button, Deck Pointer opens an external Ducalis feedback board in your browser. Deck Pointer does not transmit feedback data itself; Ducalis may process your browser/device details and IP address, plus content and email/account details you submit for voting or comments, under its own [privacy policy](https://ducalis.io/privacy-policy/).
Telegram — delivers us a private message for each setup described above (the codes, the outcome, the phone model, the country and any words you typed under “Something else”), so we can see in real time who the app is for. Only we read it; Telegram does not receive your email or Bluetooth data. Our server also receives whether the stated goal was reached and a summary when each connected session ends: a random session ID tied to the setup, its duration, and counts of characters, keys, pointer movements, clicks, scrolls, gamepad actions, shortcuts, macros, media commands and slide commands. It receives counts, never typed text or the keys themselves. These update the same private Telegram setup message. Optional notes are sent as a reply and deleted from our server only after Telegram confirms delivery, or within seven days.
Google (Firebase Analytics and Google Ads), Meta Platforms (Facebook, Instagram) and TikTok — receive the ad-measurement data described under “Product analytics”, from the Android and iOS apps, the website and RevenueCat, and use it under their own terms. Not in the EEA, the UK or Switzerland before you allow it; not anywhere after you turn it off.
Nobody else. We don't sell your data or share it with data brokers. Apart from Google, Meta and TikTok for ad measurement as described, none of these providers may use your data for their own purposes.
Cookies and tracking
One: PostHog (see “Product analytics” above) stores an identifier in your browser — a cookie on our own domain, alongside a matching entry in local storage — so that coming back tomorrow isn't counted as a new visitor. It is first-party, it says nothing about you, and clearing your browser data removes it.
Signing in for free-game emails also keeps your sign-in session in your browser's local storage, so you stay signed in. It is needed for the account to work, is not used for tracking, and signing out removes it.
With ad measurement on (see “Product analytics”), the Google tag, the Meta Pixel and the TikTok Pixel also set their own cookies (such as _ga, _fbp and _ttp) to recognise a returning browser and measure our ads; in the EEA, the UK and Switzerland only after you allow it in the banner. Your answer is kept in your browser's local storage.
Nothing else, and no fingerprinting. The site's fonts are hosted on our own domain specifically so that a font request can't leak your IP address to a third party either.
How long we keep it
Waitlist contacts: until the iOS waitlist ends, or until you ask us to remove you — whichever comes first. (Contacts who joined the earlier Android waitlist are kept on the same terms.)
Free-game account: until you delete it on deckpointer.com/account/ or ask us to. Deleting removes it at once.
Crash reports: kept under Sentry's standard retention window (90 days for error events at the time of writing), then deleted automatically.
Product-analytics events: retained in PostHog according to our plan's retention settings; contact us to exercise your data rights as described below. We do not promise a 90-day deletion period for these events.
On-device data (presets, known hosts, Actions): kept until you delete it in the app or uninstall the app — that's fully under your control, not ours.
Your rights
If you're in the EU/UK/EEA (GDPR): you can ask to access, correct, delete, or export your data, or object to how we use it, by writing to hello@deckpointer.com. You can also complain to your local data protection authority.
If you're in California (CCPA/CPRA) or another US state with similar rights: you can ask to know what we hold, delete it, or opt out of its sale or sharing. We don't sell personal data. Ad measurement with Google, Meta and TikTok may count as “sharing” for targeted advertising: opt out with Settings → Ad measurement in the app or “Ad measurement” at the bottom of the website, and the website honours Global Privacy Control.
Either way, write to hello@deckpointer.com and we'll respond within 30 days.
Children
Deck Pointer isn't directed at children, and we don't knowingly collect data from anyone under 13 (or under 16 in the EU). If you believe a child gave us data, contact us and we'll delete it.
International transfers
We're a US company; Resend, RevenueCat and Google's notification service run in the US and Sentry in the EU. Google, Meta and TikTok process ad-measurement data in the United States and other countries under their own safeguards. If you're in the EEA/UK, your data may be transferred outside it under Standard Contractual Clauses or an equivalent safeguard.
Changes to this policy
We'll update the date above when this changes. If a change is significant, we'll also email anyone on the iOS waitlist.