Verdine Privacy Policy

Effective date: October 26, 2026

Verdine is a general-audience restaurant inspection service operated by Yaqin Works Inc. It helps people understand public health inspection records through restaurant search and source-backed context. This policy applies to the Verdine mobile app and website and explains what information we process and the choices available to you. In this policy, “Verdine,” “we,” “us,” and “our” refer to Yaqin Works Inc.

Information We Collect

Core restaurant lookup and match feedback do not require an account. If you grant location permission in the mobile app, Verdine may process your current device location to rank nearby results. Verdine does not store precise device location. Browser lookup starts with a restaurant name or address and does not request your device location.

Search and restaurant activity: search text, selected place or restaurant identifiers, viewed records, match status, inspection history and sharing interactions, and optional match feedback you submit.
Browser installation ID: a randomly generated UUID stored in this browser’s local storage and sent with protected lookup and feedback requests. It helps apply request limits and associate a response with the same browser installation. It is not an account.
Website analytics: permitted static and directory page views, generic restaurant-preview page views, limited referrer information, browser and device context, session timestamps, a Google Analytics browser identifier, and approximate region derived from the IP address. When web-app analytics is enabled, it also measures generic page categories, search-text length and result counts, selected result positions, match status, and inspection-history use.
App and request context: a randomly generated mobile installation ID, a Firebase-generated app-instance identifier, app version, platform, request timestamps, IP address, and basic request metadata used to operate and protect the service.
Security and integrity signals: verification material and tokens used to help distinguish legitimate app or browser requests from automated misuse.
Crash and reliability data: crash type, stack trace, app version, platform, device model and operating-system context, and a Firebase app-instance identifier used to diagnose stability problems. Verdine does not add search text, restaurant or place identifiers, names, addresses, or precise location to crash reports.
Public restaurant source data: public inspection records, source mappings, and place-discovery information used to provide restaurant context. Verdine does not currently store third-party review text or review author profiles.

Browser Lookup and Google Maps

When browser lookup is available, search text is sent through Verdine to Google Maps to obtain place suggestions. Selecting a suggestion uses its place identifier to look up place details and find an inspection record. Google Maps place discovery and official public health inspection records are separate sources.

Google processes the search and place-discovery information it receives under the Google Privacy Policy. Use of Google Maps features and content is subject to the Google Maps End User Additional Terms of Service.

Browser Security and Storage

Browser lookup uses Firebase App Check with reCAPTCHA Enterprise for security, fraud and abuse prevention. Google processes verification material and technical request information to provide this protection. App Check stores verification tokens in browser storage, and reCAPTCHA sets a necessary _GRECAPTCHA cookie for risk analysis. This security processing is separate from website analytics.

The browser keeps the installation ID in persistent site storage. Clearing the relevant site data removes it. If required storage or verification is unavailable, protected browser lookup and feedback may not work. You can still read available public inspection previews and discovery pages.

To preserve your return to search results when opening a public restaurant page, Verdine can store search text, the result list and the selected place’s identifier, name and address in this tab’s session storage. This one-use navigation transfer is separate from the persistent installation ID. The destination page removes it when checking it and ignores data older than five minutes. It does not contain feedback permissions, verification tokens or full inspection details.

For provider information about verification, see Privacy and Security in Firebase and Google’s reCAPTCHA data-processing information.

Match Feedback

If you submit match feedback, Verdine receives your response, the selected place and official-record identifiers, your installation ID, and the selected place name and address when supplied. Feedback helps review a possible match; it does not change the official inspection record or automatically confirm a match.

A short-lived permission to respond is kept in page memory. It is not placed in the page URL, browser navigation history or persistent browser storage, and reloading or leaving the review can end that permission. While it remains available, Change response updates your answer for the same browser installation, place and official record.

If a submission cannot be confirmed, it may already have been received. Verdine does not automatically resend an uncertain submission. Clearing browser data does not delete feedback already received by Verdine.

How We Use Information

Verdine does not sell personal information, serve ads, or provide account-based social features. Verdine uses Google Analytics to measure aggregate website page views, referral sources, and engagement on permitted static pages, directories and public inspection previews. When enabled, web-app analytics also measures whether visitors receive search results, select a result, load inspection information, and open inspection history. Google Firebase Analytics measures production mobile app usage, and Firebase Crashlytics helps diagnose production stability. Verdine disables Google Signals and advertising personalization for website analytics.

Website analytics uses generic page labels and virtual URLs for restaurant records and inspection history. Search text, precise location, restaurant or place identifiers, restaurant names and addresses, feedback responses and payloads, browser installation IDs, and verification or feedback-permission tokens are excluded from website analytics. Page views omit search parameters and fragments and use limited referrer information. Feedback responses are not measured as analytics events.

Verdine’s custom mobile analytics and crash instrumentation does not send search text, precise location, restaurant or place identifiers, restaurant names or addresses, advertising identifiers, or a Verdine user ID.

Provide restaurant search, restaurant detail, inspection history and sharing features.
Rank mobile results near your current area when you grant location permission.
Match restaurants carefully against public health inspection records and review optional feedback.
Protect the service from abuse and invalid requests, diagnose failures, and improve quality.
Measure aggregate website and mobile app use, and respond to support, privacy and legal requests.

Service Providers and Public Sources

Verdine relies on providers for hosting, database infrastructure, security, reliability, analytics and place discovery. Google provides Google Analytics for website reporting and Firebase Analytics and Crashlytics for the mobile app. Google Maps supports place discovery, while Firebase App Check and reCAPTCHA Enterprise support browser verification. These services have their own applicable terms and data-processing arrangements.

Verdine also uses public government and health-authority inspection sources. Those records remain subject to the source that publishes them. Verdine is independent from public health authorities.

Retention and Security

We retain website, app and service records for as long as reasonably needed to provide Verdine, maintain security, prevent abuse, troubleshoot issues, comply with legal obligations and improve reliability. Public inspection and restaurant source records may be retained as part of Verdine’s database. Analytics, installation-level request, diagnostic and feedback records may be deleted, aggregated or de-identified when no longer needed for these purposes.

We use reasonable technical and organizational safeguards to protect information, but no internet service can guarantee absolute security.

Your Choices and Requests

You can stop using Verdine at any time.
You can block or delete website analytics cookies through your browser settings.
You can clear browser site data to remove its locally stored installation ID and verification state. Blocking necessary storage or verification can prevent browser lookup and feedback. Clearing local data does not delete server-side records already created.
You can clear app data or reinstall the app where supported by your platform to reset local mobile app data. Server-side records may continue to be retained, deleted or de-identified as described above.
You can contact us to request access, deletion, correction or other privacy support related to information reasonably associated with your use of Verdine.

Changes and Contact

We may update this policy as Verdine changes. If we make material changes, we will update this page and the effective date.

For privacy questions or requests, contact [email protected]. See also the Verdine Terms of Use.