Privacy Policy

This policy explains how personal information is handled when you use NowFoundX's website, app, QR tags and supported lost-and-found contact features. It covers both registered owners and people who scan tags.Privacy contact: [email protected].

The information relevant to the service includes the following categories, to the extent actually collected by the features you use:

• Account and item information: registration/login details, account identifiers, tag identifiers, item descriptions, Lost/Safe status and information you submit to support.
• Device and notification information: device registration identifiers, platform details and Firebase Cloud Messaging tokens used to route incoming-call notifications.
• Call information: call/session identifiers, participants' service identifiers, timestamps, status and technical connection information. Microphone audio and camera video are processed when a corresponding call feature is used.
• Location information: location supplied through an enabled feature with the relevant permission. The exact precision, recipient and retention must be explained when the feature asks you to share it.
• Orders and support: payment/order references, transaction status, delivery details if physical goods are shipped, and the content of support requests.
• Technical information: IP addresses, browser/device information, security and diagnostic logs, and session identifiers necessary to operate the service.

Information is used to authenticate accounts, associate tags with their owners, display the requested tag status, connect genuine finder-owner communications, deliver notifications, process orders, investigate failures and abuse, respond to support requests and meet applicable legal obligations.

We will explain optional purposes separately and seek consent where required. Information should not be collected merely because it might be useful later. Consent, service-related processing and other lawful grounds must be assessed under the law applicable at the time.

A person with access to a QR code can open its finder page and see the information that page exposes. During calls, the other participant can hear your voice and, if enabled, see your camera feed. Location or other details you choose to share may also become visible to the intended recipient.

Do not place confidential information in an item description or voluntarily reveal sensitive details during a call. Another participant could capture information using their own device; no platform can promise to prevent that entirely.

The app or browser may request microphone and camera access for calls, notification permission for alerts, and location permission for a location-sharing feature. You can manage permissions in your device or browser settings. Denying a permission may prevent the related feature from working. A QR tag does not itself continuously track an item.

Information necessary to run a feature may be processed by hosting, database, notification, communications, payment and support providers. Firebase is used for app notifications. Payment and calling providers must be identified according to the production integration.

We may disclose information when legally required, to respond to a valid legal request, or where necessary and lawful to investigate fraud, protect users or establish legal claims. If the business changes ownership, appropriate notice and safeguards will apply to any transfer of personal information.

Payments may be handled through a payment provider. Its privacy notice also applies to information you provide directly to it. NowFoundX may receive order/payment references and status needed to reconcile purchases and handle refunds. Never send card PINs, OTPs or banking passwords to support.

Session cookies and browser storage can be used to maintain sessions, protect forms and support website features. Browser controls allow you to manage cookies; blocking essential storage may affect functionality.

Information should be retained only as long as necessary for the disclosed purposes, applicable legal obligations and legitimate unresolved disputes. When no longer needed, it should be deleted or appropriately anonymised. Account deletion may require separate treatment for transaction records, abuse investigations and backup copies.Logging out or uninstalling the app does not by itself delete server-side records. Contact support to request account closure or deletion.

We use safeguards appropriate to the information processed and the risks of the service. No internet service can guarantee perfect security. Protect your account and report suspected unauthorised activity to support. Where required by applicable law, affected people and authorities will be notified of a qualifying data breach.

Contact [email protected] to request access to relevant account information, correction, account closure or deletion, withdrawal of consent for optional processing, or to raise a privacy complaint. Available statutory rights and exceptions depend on the applicable law and its commencement dates.

We may ask for proportionate information to verify your identity. Do not send identity documents unless specifically requested through an appropriate secure process. Withdrawal does not undo prior lawful processing; a feature may become unavailable if it requires the withdrawn permission. You retain the right to approach a competent authority where applicable.

Accounts are intended for adults. Minors should use the service only through a parent or legal guardian managing the account. Do not upload children's personal details or use tags to track people. Contact support if a child has supplied personal information without appropriate authorisation so we can investigate and take appropriate action.

For privacy requests, write to [email protected]. Provide only the information needed to understand your request. We aim to acknowledge complaints within 48 hours and resolve them within one month, subject to applicable shorter deadlines.Material changes will be communicated appropriately. Where a new purpose requires consent, a policy update alone will not replace that consent.