top of page

Fu Er Dai GBP App Privacy Policy

Effective date: pending finalization of this policy and the corresponding system changes.

Fu Er Dai GBP is operated by FU ER DAI (BM) SDN. BHD. (Business Registration No. 202301041448 (1535367-A)).

Business address: 3408, Jalan Kulim, Taman Bukit Mas, 14000 Bukit Mertajam, Pulau Pinang, Malaysia.

Privacy enquiries and deletion requests: zack642824@gmail.com.

Fu Er Dai GBP is an owner-operated tool used to manage authorised Fu Er Dai Google Business Profiles and support customer-review management, internal reporting, data consistency and service improvement.

Information used

With the account owner's Google authorisation, the tool reads and stores business profile identifiers, review totals, ratings and review identifiers. Monitoring also stores reviewers' public display names, review text, star ratings, review creation and update timestamps, and owner replies in private review snapshots and comparison records. The separate review-response workflow processes and stores reviewer details, review text, ratings, replies and approval records. OAuth credentials are stored as encrypted Cloudflare secrets. The Google permission requested is business.manage; monitoring reads data, while the separate review-reply workflow can send owner replies under configured approval rules.

Purpose and service providers

We use this information to maintain review records, track review totals and customer-feedback trends, prepare internal business reports, check data consistency across connected services, and manage customer-review responses. These activities help us understand customer experiences and improve service quality. Cloudflare hosts the workflow and database. Zernio provides business-profile integration. Telegram delivers owner notifications and approval requests. Google provides authorised Business Profile data. Alerts may include review identifiers or public review excerpts, depending on the workflow. We do not sell Google user data or use it for advertising targeting.

Retention and access

Monitoring records are stored in a private Cloudflare D1 database. The monitoring and audit routines delete records older than 30 days when those routines execute, including review snapshots containing reviewer display names, review text, ratings, timestamps and owner replies. Count observations are cleaned up by their corresponding routines. Cleanup depends on execution: records may remain longer if the workflow is stopped or a routine fails before cleanup.

The current review-response workflow has no automatic expiry configured for its review records, approval records or run history. The 30-day monitoring cleanup does not delete these records, Telegram messages, downloaded reports, Cloudflare logs or backups, or Zernio-held records.

Access to monitoring endpoints requires authentication; approval actions are restricted to the paired owner. Credentials are not included in reports.

Your choices

The account owner can revoke Google access from their Google Account permissions page, stop the workflow, or request deletion of stored application data. Revoking Google access stops future authorised collection but does not itself delete previously stored records. Contact zack642824@gmail.com for questions or deletion requests.

Changes

We will update this policy when data handling changes and display the revised effective date.

Required owner checks before publication (remove this section only when finalized)

  • Business operator and privacy contact confirmed. Set the effective date when the final policy and matching system changes take effect; use 9 October 2026 only if both are finalized on that date.

  • Confirm deletion procedures and any retention periods for the reply database, approval records and run history; no automatic expiry was found in the current workflow code.

  • Verify retention and deletion arrangements for Telegram messages, downloaded reports, Cloudflare logs and database backups, and Zernio records. These are not covered by the monitoring cleanup and have not been verified.

  • Confirm the public homepage and privacy-policy URL on a domain you control.

  • Confirm all statements match production behavior and applicable Google data-use requirements before finalization.

bottom of page