StreetSense Privacy Policy
Version 5.3 · Effective October 11, 2026
1. Overview
MNS Industries, LLC (“we,” “us,” or “our”) operates https://mnsindustriesllc.com/streetsense (the “Site”) and develops the StreetSense mobile application (the “App”).
This Privacy Policy explains what limited information the App and Site collect, how we use it, and the choices you have. It consolidates and supersedes all prior StreetSense privacy notices.
This Policy applies when you use the App or Site. Where applicable law requires consent for a particular collection or use, we request it separately. We may update this Policy; the latest version is posted at https://mnsindustriesllc.com/streetsense-privacy-policy/, and the effective date above reflects the most recent revision.
2. Information We Collect
StreetSense is built around data minimization. Federal case law and TempTag reference information ship in the App. State legal-reference packs are downloaded after you choose a state and remain available offline after installation. Some features — law-enforcement verification for the TempTag scanner, optional accounts, and subscriptions — involve limited data, described below.
(a) Stored only on your device
The following never leaves your device (except optional iCloud sync, below):
- Theme and display preferences; app-lock (Face ID / Touch ID) preference
- Recently viewed and favorited statutes; charge-sheet contents
- Non-legal onboarding progress and dismissed-screen preferences
- TempTag scan tallies by state (counts only) and recently viewed / favorited state codes
During ordinary scanning, camera images, text read from a tag, and analysis results are processed in memory only; they are not saved to your photo library or transmitted off your device. If you deliberately choose Export Report, the App creates a file-protected temporary PDF that can include the captured image, extracted tag details, findings, and any officer name or agency included in the report. The App presents Apple’s share sheet, sends the PDF only to the destination you select, and deletes its temporary copy when the share sheet closes. Your selected recipient or service then controls its copy. If you enable iCloud Sync, favorites and recently viewed legal-reference item identifiers sync through Apple’s iCloud Key-Value Store under Apple’s privacy policy — never to our servers.
The App keeps a small on-device diagnostic log — recent screens visited and any unexpected app closures — to help us fix crashes. It contains no scan content and no personal information, and stays on your device unless you choose to email it to us from Settings. Separately, when the App unexpectedly closes we use Firebase Crashlytics (Google LLC) to send us an automatic crash report — a stack trace, your device model, operating-system version, and app diagnostics. Content-update diagnostics may include the two-letter state-pack code, download phase, result, source, byte count, and duration, but not scan content. We do not attach your StreetSense account identifier, name, or email to those reports. We use them only to diagnose and fix crashes, never for advertising or profiling. Apple may also provide us aggregate crash reports if you have opted into sharing analytics in your iOS settings, governed by Apple’s privacy policy.
Location (optional). When you choose a state, the App can offer to suggest one from your approximate location if you allow it. The App sends your coordinates only to Apple’s geocoding service to look up the state; we never receive or store your location.
(b) Account and law-enforcement verification
If you create an account or request LE verification for the TempTag scanner, we collect through Google Firebase Authentication and store in our Google Cloud Firestore database (processed by our Google Cloud Functions):
- Your email address (or, with Sign in with Apple, the email or private-relay address you choose, plus your name if provided)
- Your name and department or agency from the verification form. No photo of your ID or badge number is collected.
- Your selected state, a Firebase user identifier, and sign-in timestamps
- If you allow push notifications, a Firebase Cloud Messaging push token and its platform, enabled flag, and last-updated time (see Section 4)
- If you choose your town for Local Ordinances, the municipality and county you select; if you ask us to add a town, that request
- For free accounts, the number of free searches used (a count and a random token — never the search words)
We use this only to administer accounts and verify law-enforcement status through approved-domain automation or manual review. Your password is handled by Google Firebase Authentication; we never see it. When you verify ownership of a work email, we send a one-time confirmation code to that address through Resend, Inc., an email-delivery service that receives the destination email address solely to deliver that message.
(c) Subscriptions and payments
Subscriptions are processed through Apple and managed with RevenueCat, Inc. The RevenueCat SDK transmits an app subscriber identifier (a RevenueCat anonymous identifier before sign-in and your Firebase user identifier after sign-in), subscription and purchase status with Apple, device/technical information, selected and licensed U.S. state, state-switch count, signup-source category, and the original and most recent version and time of your recorded Terms and Privacy acceptance. An App-Check-protected Google Cloud Function also records an idempotent acceptance event and original/latest acceptance summary in Firestore so we can document required consent; signed-in records are linked to your Firebase identifier and otherwise use a one-way-hashed RevenueCat identifier. We also receive authenticated RevenueCat webhook events and store a limited lifecycle mirror in Firestore: product and store, sandbox/production environment, purchase/expiration/cancellation/billing-event times and reasons, state, price/currency/country, and trial-conversion status. We use this information to administer entitlements, provide support, document consent, prevent abuse, and measure subscription and state-pack adoption. It is not used for advertising or cross-app tracking. Apple processes payment; we never receive your card or banking details.
(d) Reference-data updates
The App downloads selected state legal-reference packs and periodically downloads updated TempTag and universal reference data from our content delivery network (Amazon Web Services CloudFront/S3 at cdn.streetsenseapp.com). These are HTTPS GET requests with no user data in the body. As with any web request, server logs may record your IP address and a User-Agent string. Downloaded packs remain on the device for offline use until you clear or replace them.
(e) Corporate / agency licensing
If your department licenses StreetSense directly, we may collect the agency name, a billing or purchasing contact, and the invoicing details needed to fulfill the order. Direct agency orders are billed by invoice — we do not collect or store payment-card details. Each officer’s access is then activated on their own StreetSense account. We do not report individual officers’ use back to your department.
(f) Technical data via Apple
Crash data and App Store analytics may be collected by Apple if you have opted in through your Apple ID settings, governed by Apple’s privacy policy. Such data is aggregated and does not identify you to us.
(g) Device authorization
To protect purchased access from unauthorized sharing, the App registers the devices you sign in on. When you sign in, we send to our Google Cloud Function a per-install device identifier, your device name (as set on your device), and your device model, so we can bind your access to your device and let you reassign it if you switch phones. Firebase App Check also uses Apple’s App Attest or DeviceCheck to attest that backend requests came from a legitimate App installation. We use these signals only for app integrity, access security, and license enforcement — not to track your location or activity.
(h) Optional availability emails
If you ask to be notified when a state or tier becomes available, we store the email address you provide, the requested state code, platform, and the screen where you made the request. We use that information only to send the requested availability email through Resend. The request is scheduled for deletion no later than 30 days after a successful notice; you may also request deletion sooner.
(i) Limited feature-use milestones
The App sends a small allow-listed set of feature milestones to our Google Cloud Function, such as opening or submitting verification, requesting or confirming a work-email code, starting a search, or selecting a guided path. We store aggregate counts for all callers and, while you are signed in, only the time each milestone first occurred, under your Firebase user identifier. We do not send the search words, statute or case selected, guided-path answer, tag image, OCR text, tag number, or scan result with these milestones. We use them only to understand feature adoption and reliability.
(j) Optional feedback
If a version of the App offers a feedback form and you choose to submit it, we collect the text you enter, platform, your Firebase user identifier when signed in, and a contact email only if you opt to provide one. Feedback is used for support and product improvement and is scheduled for deletion within 180 days.
3. How We Use Information
We use the limited information above only to: administer and secure accounts; verify law-enforcement status through approved-domain automation or manual review; process and restore subscriptions; understand subscription, state-pack, and feature adoption; deliver reference-data updates; respond to feedback; and send requested or necessary service messages. We do not use it for advertising or profiling.
4. Notifications
The App may schedule local notifications on your device (for example, a reminder before a free trial converts, or when new reference data is available). These are created and delivered entirely on-device using Apple’s UserNotifications framework. No local-notification content leaves your device.
Push notifications (added October 11, 2026). After you submit a law-enforcement verification request, the App asks whether you want push notifications. This is optional, and you can turn them off at any time in iOS Settings; when you do, the App deletes the push token from our servers. We use push notifications only to tell you about the status of your account or verification, for example that your TempTag scanner verification was approved, needs more information, or was not approved, that a reviewer replied, or that a manual review was filed after a verification code was not delivered. The same notices are also sent by email. Push notifications are delivered through Apple Push Notification service using Google Firebase Cloud Messaging (FCM). To enable this, the App obtains an FCM registration token (a push token that identifies your app installation) and stores it in our Google Cloud Firestore database under your account, together with the platform (iOS or Android), an enabled flag, and the time it was last updated. We keep at most a few tokens per account, and we delete them when you sign out, when you turn notifications off, and when you delete your account. Notification text is generic status wording suitable for a lock screen; it never includes reviewer notes, names, agency, or other personal details. We do not send marketing push notifications. We do not use push tokens for advertising or tracking, do not share or sell them, and do not combine them with third-party data. They are not used to monitor what you search for or do in the App.
Separately, an availability email is sent only when you submit the optional request described in Section 2(h).
5. Third-Party Services
The App transmits data to only these processors, each under its own privacy policy:
- Google LLC (Firebase Authentication, Cloud Firestore, Cloud Functions, Firebase Cloud Messaging) — email, account and verification data, push notification token, sign-in metadata, device authorization, legal-acceptance records, subscription-event mirror, feature milestones, optional feedback, and IP address
- Google LLC (Firebase Crashlytics) — automatic crash reports: stack traces, device model, OS version, and app/content-update diagnostics described above; no StreetSense account identifier, name, email, or scan content is attached
- RevenueCat, Inc. (subscriptions and aggregate subscription analytics) — subscriber identifier, purchase data, technical information, state and switch data, signup-source category, and your original/latest recorded Terms and Privacy acceptance versions and timestamps
- Amazon Web Services (reference-data CDN) — IP address and User-Agent in server logs only
- Resend, Inc. (email delivery) — the destination address for verification, requested availability, and necessary account-service messages
- Apple — Apple Push Notification service (delivery of the account-status push notifications described in Section 4), subscription payment processing, Sign in with Apple, optional iCloud Key-Value Store sync, App Attest / DeviceCheck, and opt-in App Store analytics
The App uses no advertising or attribution SDK and does not track you across other companies’ apps or websites. The subscription and stability dashboards described above are used only for StreetSense operations. Links to official government legal resources open outside the App and are subject to those sites’ policies.
6. Cookies and Tracking
The App uses no browser cookies and does not perform advertising or cross-app tracking. It does use the account, subscription, device-binding, and app-integrity identifiers described above for functionality and security. We do not use cookies or pixels for behavioral advertising or cross-site profiling.
Website analytics (updated September 27, 2026). The Site uses Google Analytics, added through Google Site Kit, to measure aggregate traffic: which pages are viewed, the referring site, device and browser type, and approximate location derived from your IP address. Google Analytics sets first-party cookies (such as _ga) when a page loads. We use these reports only to understand how the Site is used, not for advertising, and we do not place advertising pixels on the Site. Google processes this data under its own privacy policy. You can decline cookies through the cookie banner or your browser settings, or install Google’s opt-out add-on at tools.google.com/dlpage/gaoptout. The Site may also use a standard session cookie to keep administrators signed in.
Do Not Track. The Site does not currently respond to browser “Do Not Track” signals. Other than the Google Analytics measurement described above, we do not allow third parties to collect personal information about your online activities over time and across websites through the Site.
7. Data Retention and Deletion
We retain account, verification, and legal-acceptance records while your account exists and as reasonably needed for security, consent documentation, dispute resolution, and legal obligations. A daily cleanup job removes expired email-confirmation and device-recovery codes, confirmed work-email proof no later than 30 days after confirmation unless submitted sooner, and optional feedback no later than 180 days after submission. Raw RevenueCat webhook lifecycle events are scheduled for deletion after two years. An unsent availability request remains until the requested release, account deletion, or an earlier deletion request; after a successful notice it is scheduled for deletion within 30 days. Push tokens are removed when you sign out, turn notifications off, or delete your account. Signed-in feature-milestone records are removed with account deletion; aggregate counters do not identify an account. You can permanently delete your account and associated data in the App: Settings → Account → Delete Account. This removes your authentication record, push tokens, linked Firestore records (including signed-in legal-acceptance records), and RevenueCat customer profile. Any active App Store subscription must be cancelled separately in your Apple ID settings. If we are legally required to preserve account records, we may pause deletion of the affected records for the required period and tell you that the deletion is on hold. Accounts provided by an agency license are deleted through the agency’s administrator; contact us and we will coordinate.
8. Your Privacy Rights
Depending on your jurisdiction, you may ask what information we hold about you, request its deletion or a copy, and exercise additional rights. Residents of California (CCPA), the EU/UK (GDPR), and other states with comprehensive privacy laws may have further rights, including to opt out of sale or sharing. We do not sell or share personal information for cross-context behavioral advertising and have no mechanism to do so.
Use the in-App deletion above, or email nick@mnsindustriesllc.com from your account email, to exercise any right. We respond within the timeframes applicable law requires.
9. Data Security
All App-controlled network connections use HTTPS. Authentication tokens and the per-install device identifier use the iOS Keychain. Ordinary scan photos, read text, and results remain in memory; the protected, user-initiated report-export exception is described in Section 2(a). We use commercially reasonable safeguards, but no method of transmission or storage is completely secure, and you are responsible for the physical security of your device and any report you export.
10. Children’s Privacy
The App and Site are not directed to individuals under 13, and we do not knowingly collect personal information from children. If you believe a child has provided us information, contact us and we will delete it.
11. Communications
We may send service messages (such as subscription confirmations, verification results, or critical updates) by email and, if you allow them, by push notification as described in Section 4. When you create an account, the sign-up screen tells you that we will email you StreetSense product updates, and we record that consent with your account. Every such email lets you unsubscribe, and you can also opt out at any time by emailing nick@mnsindustriesllc.com. Opting out does not stop service messages.
12. Policy Updates
We may update this Policy prospectively. The effective date reflects the latest revision, and the current version is posted on our website. We will provide additional notice or request consent when applicable law requires it.
13. Contact Us
Questions about this Policy or our data practices:
MNS Industries, LLC
nick@mnsindustriesllc.com
https://mnsindustriesllc.com/streetsense
We are committed to data minimization and to safeguarding the confidentiality of the limited information we hold.
Version 5.3 · Effective October 11, 2026