Privacy Policy: goWare & BeQuiet

Effective Date: September 27, 2026

At goWare (a software brand operated under Dreamgineering, LLC), we build the future of agentic software. We believe privacy policies should be readable by humans, not just attorneys. Here is exactly how we handle your data, split between our website and our mobile apps.

1. The Honest Truth (Websites & Contact Forms)

When you contact us on our website or sign up for our beta releases, we collect the data you explicitly provide to us (like your name, email, device type, and inquiry details). When you register for our iOS TestFlight beta, Apple manages your Apple ID directly—we never ask for, collect, or store your Apple ID.

We don't hide behind legalese. The truth is: we don't know exactly how we will use your email address in the future.

You should assume that while we are currently committed to using your contact information exclusively within the goWare family of products and services, we may use it at some point to contact you about new products, software releases, or development services that go beyond your initial inquiry. We will not sell your data to third parties.

If you want to be part of the agentic revolution with us, this is the trade-off. If you're not comfortable with us potentially reaching out to you later with cool new stuff, we strongly encourage you to use a pseudonym, a disposable email address, or simply consider not submitting your contact information at all.

2. The BeQuiet Mobile App (The "We Don't Want Your Data" Policy)

While our website offers products and services that may require creating a profile to manage them, there is no connection between these website profiles and the BeQuiet app running on your device. The application is engineered from the ground up as an offline-first, on-device utility.

  • No Location Tracking: BeQuiet automatically manages your quiet state based on WiFi networks and location. On iOS, because Apple limits background Wi-Fi scanning, BeQuiet uses on-device circular geofencing and your connected Wi-Fi network to detect Quiet Zones. On Android, it scans nearby Wi-Fi beacons. All matching happens 100% locally on your device. When syncing public directories or checking connectivity, standard transient HTTPS/CDN access logs (such as IP address and request headers) occur as part of normal web traffic, but these are never linked to personal location history. We never send your location tracks, coordinates, or travel routes back to our servers. If we wanted to stalk you, we'd build a social network.
  • No Background Uploads: The custom Quiet Zones you add to your app are stored locally and privately on your physical device. They never touch our servers. You can optionally opt-in to let Quiet Zone sponsors know how many times a day your instance of BeQuiet entered their sponsored zone. This is done via anonymous aggregated check-ins that do not contain personal identifiers, hardware fingerprints, or tracking histories.
  • Sponsor "Thank You" Telemetry: If you use the app to silence your phone at a sponsored location and explicitly tap the "Thank Sponsor" button, we send a completely anonymous network ping to our database. This payload contains only the WiFi hash, a timestamp, and a +1 counter. It is entirely stripped of device IDs, user identities, or hardware fingerprints. We just want sponsors to know the system is useful; we don't care who pressed the button.

3. Why We Ask For Permissions

To function as designed, mobile operating systems require BeQuiet to ask for some scary-sounding permissions. Here is what they actually do and why, separated clearly by platform:

Apple iOS Permissions & Capabilities

  • NSLocationWhenInUseUsageDescription / When In Use: On-device geofence evaluation while the app is in use; required by iOS to read the connected Wi-Fi SSID. GPS is used strictly on-device and is never uploaded for Quiet Zone detection.
  • NSLocationAlwaysAndWhenInUseUsageDescription / Always: Background geofencing so entering and leaving Quiet Zones works automatically without having to keep the app open. Same on-device-only rule; no route or track uploads.
  • com.apple.developer.networking.wifi-info (Access Wi-Fi Information Entitlement): Allows BeQuiet to read your currently connected Wi-Fi network's SSID and BSSID to refine quiet detection. This applies only to the network you actively join, not an Android-style background airwave scan.
  • NSFocusStatusUsageDescription (Focus Status): Reads whether your Focus / Quiet Mode is turned on so the app knows ringers are silenced. We guide you to engage a one-tap Quiet Mode / Focus for ringers; third-party iOS apps cannot programmatically force DND like Android's ACCESS_NOTIFICATION_POLICY and cannot flip the physical hardware Silent switch.
  • UNUserNotificationCenter (Notifications): Optional local banners when entering or leaving a Quiet Zone, or to confirm status. Generated entirely on-device; no remote push tracking.
  • NSBluetoothAlwaysUsageDescription (Bluetooth Always, Pro): Used only in the Pro Tier for vehicle hands-free, earbud, or CarPlay-related bypass so driving navigation and music aren't muted.
  • UIBackgroundModes (location, fetch, processing, audio):
    • location: Wakes the app when crossing circular geofence boundaries so muting triggers immediately.
    • fetch & processing: Uses Apple's background task scheduler (BGTaskScheduler identifier dev.goware.bequiet.refresh) to periodically refresh the public Quiet Zone directory.
    • audio: Configures audio session categories (AVAudioSession) to mute and restore media volume smoothly.
  • LSApplicationQueriesSchemes (shortcuts): Enables one-tap handoff to the Apple Shortcuts app to trigger your custom Quiet Mode Focus.
  • What We Do NOT Request on iOS: We do not request Camera, Microphone, Contacts, Photos, or App Tracking Transparency (ATT/IDFA). We never sell your location or personal data.

Google Android Permissions

  • ACCESS_FINE_LOCATION & ACCESS_BACKGROUND_LOCATION: Google bundles WiFi scanning under "Location" permissions. We need this to see the name of the WiFi network the device is near so the app can mute it. We never read or save device GPS coordinates.
  • ACCESS_NOTIFICATION_POLICY: Required so the app can programmatically toggle your device's native "Do Not Disturb" (DND) state for ringers and notifications.
  • POST_NOTIFICATIONS: Android requires a persistent foreground notification ("Quiet zone active - phone muted") to prevent the operating system from abruptly killing the background service.
  • RECEIVE_BOOT_COMPLETED: Allows the background service to start automatically when your phone reboots, so you don't have to manually open the app every time your phone restarts.

4. Legal Privacy Compliance

We are committed to complying with major global privacy frameworks, including the General Data Protection Regulation (GDPR) and the California Consumer Privacy Act (CCPA). Because our mobile application is built on offline-first, on-device matching and strict data minimization, it inherently adheres to the strictest principles of user privacy and consent. For any web-based data you explicitly provide to us, you retain the full right to request access, correction, or deletion of your personal data at any time.

5. Contact & Support

If you have any questions, feedback, or concerns regarding our privacy standards, or if you just want to talk about agentic software, please reach out to the engineering team:

goWare Support
Dreamgineering, LLC
[email protected] | goware.dev