DoorCue: Before You Go

Privacy Policy & Local Data Processing Declaration

Last Updated: September 8, 2026

Contents

  1. Overview & Offline-First Architecture
  2. Information We Do Not Collect
  3. Local Data Storage & Photo Isolation
  4. Device Permissions & Technical Justifications
  5. Advertising & Google UMP Consent Framework
  6. Data Retention, Portability & Deletion
  7. Children's Privacy
  8. Contact Us

1 Overview & Offline-First Architecture

DoorCue ("we", "our", or "the App") is developed by Tech2U Savannah as a calm, offline-first personal departure checklist utility. We believe that your home location, daily schedule, and personal belongings should remain strictly confidential.

Zero Cloud Account Requirement: DoorCue does not require user registration, logins, phone numbers, or passwords. All checklist items, monitored place anchors, departure triggers, and attached item photos are processed exclusively on your physical device.

2 Information We Do Not Collect

Because the app runs locally without a backend server, we do not collect, sell, or rent:

3 Local Data Storage & Photo Isolation

All items, place geofences, and departure histories are stored locally in an on-device SQLite database managed by Android Room. Attached item photographs are stored strictly inside the application's sandboxed internal directory (context.filesDir/item_photos/). No photos are accessible to other applications or uploaded to external cloud storage.

4 Device Permissions & Technical Justifications

DoorCue requests only the minimum required permissions necessary to trigger timely departure reminders:

ACCESS_FINE_LOCATION & ACCESS_COARSE_LOCATION

Used solely by Android's hardware Geofencing API to detect when your device exits a user-defined departure perimeter (e.g. Home, Work, Gym). Coordinates remain on your hardware and are never transmitted over the internet.

ACCESS_BACKGROUND_LOCATION

Required to allow Android's Geofencing Client to detect when you walk out of your door even when the phone screen is locked or DoorCue is minimized.

POST_NOTIFICATIONS

Required on Android 13+ (API 33+) to dispatch the "Before You Go" checklist notification when a departure boundary exit is detected.

RECEIVE_BOOT_COMPLETED

Allows DoorCue to re-register your active geofences with Android system services whenever your phone restarts.

CAMERA (Optional)

Used only when you explicitly tap the camera icon to photograph an essential checklist item via Android's native system camera. The app does not maintain a background camera service.

5 Advertising & Google UMP Consent Framework

DoorCue utilizes the Google Mobile Ads SDK (AdMob) to support development. We strictly adhere to global privacy standards (EU GDPR, UK GDPR, Swiss DPA, and US CCPA/CPRA):

Google User Messaging Platform (UMP)

Before any ads are initialized or requested, DoorCue presents a certified Google CMP consent dialog to users in relevant regulatory jurisdictions. Users can freely accept, reject, or customize ad personalization.

Consent Revocation: You may modify or withdraw your consent at any time directly inside DoorCue by navigating to Settings → Privacy & Consent → Consent Preferences.

6 Data Retention, Portability & Deletion

Since all data lives on your device, you retain total control:

7 Children's Privacy

DoorCue does not knowingly collect any personal information from children under the age of 13. The application is a general productivity tool suitable for all audiences.

8 Contact Us

If you have questions, feedback, or inquiries regarding this Privacy Policy:

Tech2U Savannah

developer.tech2u@gmail.com