Privacy Policy
Standby Desk
Nade Labs ("Nade Labs", "we", "our", or "us") operates the Standby Desk mobile application (the "App"). This Privacy Policy describes how we handle, process, and protect your information when you download, install, or use our App.
We believe that privacy is a fundamental human right. Our App is designed with a local-first, privacy-by-default architecture: we do not require you to create an account, we do not operate a cloud database holding your personal files, and we process your media and desk controls directly on your device.
By downloading or using the App, you agree to the processing of information in accordance with this Privacy Policy.
Key Takeaways
- No Account Required: You can use every feature of Standby Desk without registering, signing in, or sharing your email address.
- On-Device Processing: Photos, calendar schedules, alarms, timers, and theme preferences are processed and stored locally on your device.
- Peer-to-Peer PC Companion (Zero Cloud Relay): The Standby Desk companion connects directly to your Windows PC over your local Wi-Fi network (LAN). No macro keystrokes, button taps, or companion data ever pass through our servers or external cloud relays.
- Photos Never Leave Your Phone: Images selected for the Photo Clock are saved directly into the App's secure private sandbox on your device and are never uploaded anywhere.
- Transparent Monetization: The free tier of the App is supported by Google AdMob (including Rewarded Ads for unlocking select cosmetic features). In-app subscriptions and one-time purchases are securely managed through Google Play Billing and RevenueCat without collecting your name or banking details.
1. Information We Do NOT Collect
To be completely transparent, here is what we never collect, transmit, or store on any remote server:
- We do not collect your real name, home address, or phone number.
- We do not collect your email address or account passwords (there is no user registration).
- We do not collect or view your personal photos, albums, or media files.
- We do not collect any kind of other user data.
2. Information Processed Locally on Your Device
The App processes certain information strictly within your device's memory and local sandbox. This data never leaves your device:
A. Photo Clock & Media Files
- If you use the Photo Clock feature, you may select individual images or photo albums using the system photo picker or album browser.
- The App copies selected images into its internal, sandboxed app directory (
context.filesDir) to render the background slideshow. - These photos remain 100% private to your device and are never transmitted to Nade Labs or any third party.
B. Media Playback & Now Playing Metadata
- The App includes an ambient music player widget. To show what is currently playing, the App utilizes Android’s
MediaSessionManagervia a Notification Listener service (StandByNotificationListener). - This service inspects active media sessions strictly to retrieve playback state (playing/paused), track title, artist name, and album artwork so you can control music playback from the desk clock.
- The App does NOT read, inspect, or store private notifications, messages, chat logs, or emails. Media metadata is used in-memory on the active screen and is never logged or uploaded.
C. Camera & QR Code Pairing
- When connecting the App to the Standby Desk Windows Host, the App requests camera access to scan the pairing QR code displayed on your PC screen.
- The camera stream is analyzed in real time on your device using Google ML Kit Barcode Scanning strictly to extract the local IP address and port.
- No photographs or video recordings are captured, saved, or uploaded. The camera is released immediately after pairing.
D. Active Tools, Timers & Alarms
- The Pomodoro timer, countdown timers, and stopwatch store their active states, durations, and sound preferences locally in SQLite (
Room) and Jetpack DataStore. - Precise alarms are scheduled via Android’s local
AlarmManagerand trigger local device notifications. No alarm data is synced to any cloud server.
E. Standby Desk PC Companion (Local Network Only)
The PC Companion communicates with your Windows PC via local network protocols:
- WebSocket (
ws://<pc-ip>:8088): Dispatches button presses and receives layout catalogs. - HTTP (
http://<pc-ip>:8087): Streams button icon assets from your PC to your phone. - UDP Broadcast (
port 8089): Auto-discovers Standby Desk hosts on your local subnet.
This communication is entirely peer-to-peer (P2P) across your local area network (LAN). It requires no internet access to function and does not route through any intermediary proxy or cloud server.
3. Information Collected by Third-Party Services
We integrate a limited number of trusted, industry-standard third-party SDKs to provide advertising, purchase verification, and diagnostic crash reporting. These third parties may collect certain technical identifiers and usage information:
A. Google AdMob (Advertising)
We use Google Mobile Ads (AdMob) to display advertisements in the free version of the App (such as Rewarded Ads that grant temporary access to select fonts or clock styles, as well as native or banner ads).
- Data Collected: Unique device identifiers (such as the Google Advertising ID / GAID), IP address, general device model, carrier, operating system version, and ad interaction data (impressions, clicks).
- Purpose: To serve contextual or interest-based advertisements, detect fraud, and deliver rewards when you watch an ad.
- Opt-Out: You can reset or delete your Advertising ID at any time in your Android system settings under Settings > Privacy > Ads. For more details, consult Google’s Advertising Privacy Policy.
B. RevenueCat & Google Play In-App Billing
We use RevenueCat to facilitate Google Play in-app purchases and manage premium entitlements.
- Data Collected: An anonymous App User ID generated by RevenueCat (
$RCAnonymousID:...), Google Play purchase tokens, transaction order identifiers, and active subscription status. - Purpose: To verify your purchase with Google Play, grant Premium features across reinstalls, and handle subscription renewals.
- No Financial Data: We do not collect or store credit card numbers, billing addresses, or bank details. All transactions are securely processed by Google Play. Review RevenueCat’s Privacy Policy and Google Play’s Terms.
C. Google Firebase (Crashlytics & Analytics)
We use Firebase Crashlytics and Firebase Analytics to ensure the App is stable, performant, and bug-free across thousands of Android device configurations.
- Data Collected: Anonymous device characteristics (device model, CPU architecture, Android OS version, battery level), crash stack traces, and non-identifying aggregate product events (such as
clock_selected,widget_added, orauto_launch_triggered). - Purpose: To identify and fix crashes, measure feature adoption, and improve the user experience. This data cannot be used to identify you personally. Review Google’s Privacy Policy.
D. Weather Service (Planned Feature — Work in Progress)
- In upcoming releases, the App may offer a live weather widget. If you opt to grant location permissions (
ACCESS_COARSE_LOCATIONorACCESS_FINE_LOCATION), the App sends your approximate coordinates directly to our weather API provider (such as OpenWeatherMap) to fetch local conditions. - No user identifiers, names, or accounts are attached to weather queries. If you do not wish to share location, you can leave the permission disabled or select a manual city.
4. Device Permissions We Request
To deliver its core ambient display and macro deck capabilities, the App requests specific Android system permissions. Here is why each is needed:
DeckQrScanner to scan the desktop pairing QR code on your PC. No photos or video streams are saved or uploaded.StandByNotificationListener to detect active music player sessions (song name, artist, album art) for the ambient media widget. Does not read private messages or notifications.5. Data Retention & Deletion
- Local Data: Because all layouts, clock customizations, timer histories, and cached photos are stored locally on your device, you have complete control. You can permanently erase all data at any time by clearing the App's storage via Android Settings > Apps > Standby Desk > Clear Data / Storage, or by uninstalling the App.
- Third-Party Telemetry: Anonymous crash logs collected by Firebase Crashlytics are retained for 90 days according to Google’s standard retention schedule, after which they are automatically deleted.
- Ad Identifiers: You can purge your Advertising ID history at any time through your device's Google settings (Settings > Privacy > Ads > Delete Advertising ID).
6. Children's Privacy (COPPA & GDPR-K Compliance)
Our App is designed for a general audience and is not directed at children under the age of 13 (or under 16 in the European Union). We do not knowingly collect personal data from children. If you believe that a child has provided us with personal information, please contact us at support@standbydesk.app, and we will take immediate steps to remove any such information.
7. Your Privacy Rights
Depending on your geographic location (including the European Economic Area, the United Kingdom, and California), you may hold specific privacy rights under applicable data protection laws:
- Right to Access & Portability: You have the right to know what personal data is processed. Because we do not operate user accounts, we hold no personal profile tied to your identity.
- Right to Erasure (Deletion): You can delete all local application data by uninstalling the App or clearing app storage.
- Right to Opt-Out of Personalized Advertising: You can opt out of interest-based ads by navigating to Android Settings > Privacy > Ads and selecting "Delete advertising ID" or "Opt out of Ads Personalization".
- Non-Discrimination: We will never discriminate against you for exercising your privacy rights.
To make an inquiry regarding your data rights, contact us at support@standbydesk.app.
8. Data Security
We employ technical and organizational safeguards to protect your information:
- All communications with third-party service providers (Google AdMob, RevenueCat, Firebase) are conducted over encrypted HTTPS/TLS connections.
- Local data is protected by Android’s application sandbox, which isolates app data from other applications running on your device.
- Local companion traffic stays within your trusted home or office local Wi-Fi router.
9. Changes to this Privacy Policy
We may update this Privacy Policy from time to time to reflect changes in our features, legal requirements, or operational practices. We will notify you of any material changes by updating the "Last Updated" date at the top of this page and, where appropriate, posting an update notification within the App. We encourage you to review this policy periodically.
10. Contact Us & Data Controller
If you have any questions, concerns, or requests regarding this Privacy Policy or our privacy practices, please contact us: