CarryAwareNJ · Your information

Privacy Policy

Effective date: September 9, 2026

This policy explains how Mignone Labs LLC handles information in connection with CarryAwareNJ. It does not describe the separate FlockAware project or the practices of external websites.

1. Location and information on your device

CarryAwareNJ uses the location permission you grant to show relevant places and provide proximity-based alerts. Background location access, shown as Always in iOS when available, supports alerts while you are not actively viewing the app.

Alert history, app preferences, downloaded location data, and Home Quiet Zone settings can be stored locally on your device. Home Quiet Zone coordinates are kept on your iPhone and are not uploaded by that feature. Local alert history is different from a public community submission.

Map, place-search, and address-lookup requests can be processed by Apple’s mapping services. Requests for app data also pass through the infrastructure that hosts that data. A report you choose to submit includes its selected location and is uploaded as described below.

2. Accounts and sign-in

You can browse maps and use awareness features without signing in with Apple or Google. The app may use an anonymous Firebase guest session for service access. Anonymous authentication uses a technical account identifier; it does not mean that service requests have no identifiers.

Apple or Google sign-in is required for community contributions such as reports, photos, and votes. Firebase Authentication processes the provider credentials and account identifiers needed to sign you in. Your provider may supply a name and email address, including an Apple private-relay address when you choose that option. Mignone Labs does not receive your Apple or Google password.

New reports do not show your sign-in name by default. The Show My Sign-In Name setting lets you include the available name on future reports. Contributions remain associated with a community account identifier whether or not a name is displayed.

3. Community reports, photos, and moderation

When you submit a report, we store information such as the place name, type, selected address or coordinates, notes, account identifier, submission time, and any display name you choose to include. Photos you upload and related ownership or moderation information are processed through Firebase services, including Cloud Firestore and Cloud Storage.

Reports and approved community photos can be visible to other users. Voting, content reports, contributor blocking, and moderation use account and content identifiers to manage contributions and respond to abuse. Moderators may review submitted content.

Treat community submissions as information you are choosing to share publicly. Do not submit passwords, personal documents, sensitive personal information, or images you do not have permission to share. A public contribution may be copied by others; we cannot remove copies outside services we control.

4. Notifications and technical service data

CarryAwareNJ uses on-device proximity notifications and remote news or app-update notifications. Remote delivery uses Apple notification services and Firebase Cloud Messaging, which process app-installation identifiers and delivery tokens to route messages. You can control supported message categories in the app and notification permission in iPhone Settings.

Technical services can process connection and operational data, such as IP addresses, request times, identifiers, and error information, to authenticate requests, deliver data, operate the service, and investigate problems. Diagnostics you choose to share with support can include your app version, device/iOS information, a description of the problem, and screenshots or logs you attach.

Firebase’s documentation explains the information its individual services process and their retention practices. The presence of Firebase in the app does not mean that every Firebase product or every type of analytics is used.

5. Support messages

When you email us, we receive your email address, message, and attachments through our email service. These messages remain in our support correspondence as needed to respond to the request and follow up on the issue. Do not send passwords, authentication codes, or unnecessary private location information.

For a request concerning support correspondence, contact support@mignonelabs.com. Deleting a community account is not the same as deleting separately exchanged email.

6. How information is used and shared

We use information to provide the app, deliver relevant data and notifications, authenticate community access, display user contributions, maintain voting and moderation controls, process deletion requests, and respond to support inquiries.

We do not sell, rent, or trade personal information. Public submissions are shared as described above. Apple, Google/Firebase, and the infrastructure and email services involved in providing these functions process information as needed for those functions and under their applicable terms and privacy practices.

External resource links open services with their own privacy policies. Review the Firebase privacy and security documentation, Apple Privacy Policy, and Google Privacy Policy for provider information.

7. Retention and account deletion

Community account records and contributions are retained to provide community features until removed through supported deletion or moderation processes. Device-local information remains subject to the app’s clearing controls, iOS storage, and any device backups you manage. Provider operational records, diagnostics, and backups can have separate retention periods; removal from the visible app is not a promise of immediate removal from every provider backup.

To request deletion, open CarryAwareNJ’s Settings, go to Community Access, and choose Delete Account. Read the confirmation and complete any provider-verification steps. A supported request is processed by the service to remove the community account and its associated contributions. The app can show request and completion status, and technical deletion-request or status records may be used to track processing.

Requests require a connection and may take time to finish. Follow the status shown in the app and contact support if deletion is unavailable, fails, or remains pending after 24 hours. Signing out or uninstalling the app does not submit a server-side account-deletion request.

For other data requests or questions about retention, email support@mignonelabs.com. We may need enough information to verify that a request concerns your account; do not send a password or sign-in code.

8. Your choices

  • Change or revoke location and notification permissions in iPhone Settings.
  • Choose alert categories, pacing, and Home Quiet Zone settings in the app.
  • Use the map and awareness tools without Apple or Google community sign-in.
  • Choose not to submit reports or photos, and control whether your sign-in name appears on future reports.
  • Use the app’s supported content, blocking, and account-deletion controls.
  • Contact support about your information or a contribution.

Some features will be limited when permissions or service access are unavailable.

9. Security and children

We use authentication, access controls, and service-provider security features to help protect information. No electronic transmission or storage system can be guaranteed completely secure.

CarryAwareNJ is not directed to children under 13, and we do not knowingly solicit personal information from them. Contact us if you believe a child has provided personal information so we can investigate and address it.

10. Changes and contact

We may revise this policy as the app and its services change. The effective date identifies this version of the policy.

Mignone Labs LLC
Contact: Matthew Mignone
Privacy and support: support@mignonelabs.com
Business inquiries: matt@mignonelabs.com