Privacy Policy

RoomPrivacy: Room Data, Permissions, and Service Providers

RoomPrivacy helps you inspect a room with a checklist, local Wi-Fi and Bluetooth discovery, and a camera view. It does not confirm that a room is free of hidden cameras. You do not need to create an account. RoomPrivacy does not send room photos or scan results to an AI service, and does not include advertising. It uses PostHog to understand feature use and diagnose app errors.

Room records and photos stay on your phone

Room names, checklist records, discovered device names and addresses, advertised service information, detailed scan history, and inspection photos and clips you choose to save are processed and stored locally. Analytics includes your onboarding selections, checklist actions, and scan summaries such as device counts and elapsed time; it does not include room names, discovered device names or addresses, or inspection photos and clips. Camera, Bluetooth, and local network permissions support the tools you choose to use. You can change these permissions in your phone's Settings. Your device's backup settings may allow app data to be included in system backups.

What leaves the device

• Exports you choose: Settings → Export room data opens your phone's share sheet with a file containing checklist and scan summaries. It excludes room names, nearby device names and addresses, Bluetooth identifiers, and photo files. The destination you choose receives the file and handles it under its own terms. Exported copies are separate from the data inside RoomPrivacy.
• Lamply — feedback: opening the feedback screen sends a randomly generated app identifier to retrieve suggestions. Submitting feedback sends the title and details you enter, that identifier, and RoomPrivacy's app ID to Lamply. The random identifier links submissions from the same installation without requiring your name or email address. Suggestions may be shown to other users if included in an in-app feedback list. Leave out names, room numbers, private addresses, and other sensitive information. Room records, scans, and photos are not attached. RoomPrivacy does not send app-open or session activity to Lamply.
• RevenueCat — purchases and Pro access: an anonymous app customer ID, store purchase history, product and transaction information, purchase/subscription and entitlement status, and device/app information are used to provide, validate, and restore premium access. RevenueCat also records when the app last connects to its service and a country inferred from the connection's IP address. It provides subscription analytics such as purchase history, revenue summaries, and country-level reports. These service records remain associated with the app customer ID. RoomPrivacy does not send room records or photos to RevenueCat. Apple or Google processes payment; RoomPrivacy does not receive your full payment-card details.
• PostHog — app usage and error reports: app launches, screens, feature actions, onboarding selections, checklist actions, scan counts and elapsed time, purchase activity, and subscription status help us understand how the app is used. PostHog also receives app/device information and technical error reports, including unhandled errors and fatal JavaScript errors, so we can investigate failures. It can derive approximate location from your connection's IP address. Analytics uses a persistent installation identifier and is linked to the RevenueCat app customer ID; the corresponding analytics ID is also stored with the RevenueCat customer. These are linked service records even though no name or sign-in is required. Room names, discovered device names and addresses, and inspection photos and clips are not included in the app's analytics events. PostHog processes this data through its EU service.
• Support: if you email us, we receive your email address, message, and any information or attachments you choose to include. We use these to respond to your request. The feedback deletion email draft includes your locally stored feedback identifier so we can locate the relevant submissions. You review and send the email yourself.

Service identifiers can link records to the same installation or customer even without a name or sign-in account. Network requests expose IP addresses and standard request metadata to the services handling them. Lamply retains the source IP address in temporary request-limit records to prevent spam and abuse. These records are normally cleaned up after about two hours; cleanup depends on later requests and may take longer. Feedback and support records are retained as needed to respond, improve the product, and meet applicable obligations; the shared retention provisions below also apply.

RoomPrivacy privacy choices and data deletion

Settings → Delete all room data removes saved rooms, scan history, app-owned inspection photos, onboarding choices, the local feedback identifier, and review-prompt history from the app. It does not remove exported copies, system backups, feedback already sent to Lamply, analytics or error reports already sent to PostHog, or store purchase records. It does not cancel a subscription; manage cancellation in your Apple or Google account.

Feedback already submitted to Lamply is separate from your saved room data. If you want that feedback deleted, Settings → Request feedback deletion prepares an email containing the identifier needed to locate your submissions. Do this before removing the local identifier. For access, correction, or deletion of other records held by our service providers, see Privacy questions and requests. If you no longer have an identifier, describe the submission or purchase so we can help locate it; leave out private room information.

Service-held records and backups are separate from local deletion. Some transaction, security, or legal-compliance records may need to be retained, and backup copies may remain until the applicable backup retention period ends. We do not use retained records for unrelated purposes.

Ratings use Apple's or Google's review system. RoomPrivacy keeps review-prompt timing on your phone, does not receive your chosen star rating from the native prompt API, and does not use feedback sentiment to decide whether you can rate the app.

Tracker Detect: Data, Permissions, and Service Providers

Tracker Detect checks nearby Bluetooth signals and helps you locate a device. You do not need to create an account. The following details apply to Tracker Detect, including its attribution-enabled release; the other apps above have their own data flows.

Bluetooth scans and location stay on your device

Bluetooth observations, nearby device names and radio payloads, scan history, saved device choices, and precise location coordinates used to give detections context are processed and stored locally. Background monitoring uses Bluetooth and, when enabled and permitted, location while the app is not on screen. These local records are not uploaded as a scan-history database or sent to advertising partners.

Local scanning does not mean the app collects no data. Product analytics include scan starts and outcomes, counts of detected or flagged devices, device categories, status/risk categories, onboarding choices, feature use, permission outcomes, and app-generated result identifiers in screen events. We do not attach precise GPS coordinates, nearby device names, or raw Bluetooth payloads to those analytics events. Tracker Detect does not send scans to an AI service.

What leaves the device

• PostHog — product analytics and reliability: app launches, screens and taps, onboarding and scan-summary events, paywall/checkout activity, error reports, app version/build, device/operating-system information, language, and IP-derived approximate location. Events use a persistent analytics identifier and may be associated with a RevenueCat customer identifier and subscription status. This helps us understand feature use, configure features and diagnose failures.
• RevenueCat — purchases and premium access: an app customer identifier, store transactions, product, price/currency, subscription and entitlement status, storefront, and relevant attribution identifiers. RevenueCat validates purchases, restores access and provides subscription analytics. Configured integrations send subscription lifecycle events to PostHog and AppsFlyer. Apple or Google handles payment details; Tracker Detect does not receive your full payment-card details.
• AppsFlyer and Meta Ads — measuring our marketing: install/app-open activity, onboarding completion, premium-paywall interactions and checkout starts; RevenueCat subscription events; AppsFlyer install ID, app customer ID, device identifiers where available and permitted, IP-derived approximate location, app/device/network metadata, attribution and technical performance signals. Configured conversion postbacks to Meta help measure and optimize ads for Tracker Detect. We do not forward your Bluetooth records, precise location, scan summaries, feedback text, or onboarding answers to these advertising partners.
• Lamply — Ideas and Issues: a persistent service identifier, app/session activity, and titles, descriptions and votes you submit. Submitted ideas or issues may appear in the in-app feedback list for other users. Do not include private location details, nearby device identifiers, or other sensitive information in feedback.
• Support: if you email us, we receive your email address, message, and any information or attachments you choose to include. We use these to answer the request and resolve the issue, not to add you to an advertising audience.

Service identifiers can link events to the same app installation, device, or customer even without your name or a sign-in account. Network requests also expose IP addresses and standard request metadata to the services handling them. We use service-provider infrastructure to operate these features.

Tracking permission and other controls

On iOS, Tracker Detect requests App Tracking Transparency permission during onboarding. If you decline, the app disables advertising-identifier (IDFA) collection for this integration; you can still scan and purchase premium access. Analytics, subscription handling and privacy-preserving attribution such as SKAdNetwork may continue without IDFA. When permitted, advertising identifiers and linked conversion events support advertising measurement across apps and websites. Tracker Detect itself does not display third-party ads.

You can change tracking, Bluetooth, location and notification permissions in your device's Settings. Denying Bluetooth prevents nearby scanning; restricting location can limit location context and background-monitoring features. Permission changes do not automatically erase data already stored locally or by service providers. To remove data, follow the deletion instructions below.

Tracker Detect privacy choices and data deletion

To delete scan history and app settings: follow the iPhone/iPad or Android deletion steps above. These records are stored on your device; you do not need to email us to remove them. Device backups and exported copies must be managed separately where you saved them.

Deleting local data does not erase analytics, attribution records, subscription metadata, or feedback already held by our service providers. For access, correction, or deletion of those records, see Privacy questions and requests. Tracker Detect does not require an account, so an email address alone may not identify your app's records. Settings → Contact Us in the app can help you contact support.

Some transaction, security, or legal-compliance records may need to be retained, and backup copies may remain until the applicable backup retention period ends. Deleting data does not cancel a subscription; use the store cancellation steps above.