NearNow mobile application

Privacy Policy

Effective date: October 16, 2026

NearNow is a privacy-first local information service operated by SAA Soins de Sante Intelligents Inc. This policy explains what information the NearNow mobile application handles and why.

Information we handle

NearNow creates a random installation identifier and a separate local credential for the app installation. These identifiers are not your name, email address, phone number, or social-media identity.

You choose neighborhoods or postal-code prefixes manually. NearNow does not request GPS location, contacts, advertising identifiers, or access to your address book.

Local notifications are on by default for new installations, but require your device permission. New installations have no daily frequency cap, minimum spacing or quiet hours; you can disable alerts or choose limits and quiet hours in Alerts. Existing opt-outs are preserved. When merging old preview settings, previews stay off if either old setting was off. Relevant commercial alerts and notification previews are on by default for new installations; both can be disabled in Alerts. One preview control applies to Signal and team-message summaries. When you allow notifications, we store an encrypted push-notification token so Apple or Google can deliver relevant alerts. We store notification preferences and delivery status, but not the token in readable form.

Authorized NearNow administrators can see pseudonymous installations grouped by the local areas they select and whether notifications are enabled. They may send non-commercial service or community messages to an installation or selected-area audience. Businesses cannot access these lists. Team messages follow notification consent, quiet hours, area mutes, and frequency limits; message and delivery records are retained for up to 90 days. Turning notification previews off hides both Signal and team-message summaries.

Signals, reactions, reports, conversation messages, selected interests, and mutes are stored to provide the service, prevent abuse, and improve local relevance. Resident content is associated with a pseudonymous installation rather than a personal profile.

Communities and invitations

You may create or join places and events independently of your selected neighborhood. We store community metadata, membership, alert choices and safety actions. A shared building or venue address describes the community, not a verified resident address. Do not enter apartment numbers or personal contact details. Public communities are discoverable; private communities require an invitation. A code can be shared and does not verify residence or attendance. We store a protected verifier of invitation codes and never include codes in routine logs or exports.

Only current members can read community Signals and discussions. Leaving or removal revokes future access, including through old Alerts. Previously viewed or delivered information cannot be recalled. Camera access is requested only when you choose to scan a community invitation; no photograph or video is uploaded by that flow. Manual code entry is always available. Private community pushes use generic text, even when notification previews are enabled.

Creators can restrict publishing, remove community Signals and remove their authors from the community. System administrators can review reported communities and suspend unsafe ones. Ownership belongs to the current pseudonymous installation; deleting that profile closes its communities and removes its memberships. Ended events and closed communities have a member-only read window of up to 30 days. Content follows Signal retention, and de-linked moderation evidence may remain for up to 180 days.

How we use information

  • To show Signals for the local areas and interests you select.
  • To deliver allowed notifications and enforce any limits you choose.
  • To moderate content, prevent spam and abuse, and respond to reports.
  • To provide conversations attached to a Signal while it remains relevant.
  • To maintain security, reliability, and operational backups.

Service providers

NearNow uses infrastructure providers to host the service and Apple Push Notification Service or Firebase Cloud Messaging to deliver notifications. Providers process only the information needed for those purposes under their own terms and policies. NearNow does not sell personal information or use it for behavioral advertising.

Retention and your choices

Signals and conversations are designed to be short-lived. You can change followed areas, notification settings, and analytics consent in the app. The Privacy screen also lets you request a privacy export or delete the data associated with the installation. Some limited records may remain in protected backups until their scheduled expiry or where retention is required for security and legal obligations.

How to request deletion

In the NearNow app, open Privacy, review the privacy summary, and choose Delete my data. This removes the installation's resident profile, selected areas and interests, reactions, mutes, Signals, conversations, notification endpoints, and analytics data from the active service. You can also email [email protected] with a deletion request.

Protected backups and limited security or legal records may retain a minimal record until their scheduled expiry. We do not use retained backup data to provide the app, and it is removed through our backup-erasure process.

Children

NearNow is not directed to children under 13, and we do not knowingly collect personal information from children under 13.

Changes and contact

We may update this policy as NearNow changes. The effective date above will identify the current version. Privacy questions can be sent to [email protected].