Privacy policy · Prepared November 17, 2026
How Property Taxes uses information
Property Taxes is a private Google Apps Script application maintained by its owner. It helps approved users manage tax, sewer, and stormwater records, check supported public municipal websites, and track payment attempts in a dedicated Google Sheet. Contact the owner at wangwei969@gmail.com about the app or its handling of information.
Information the app accesses and records
- Google sign-in email: identifies the current user and is recorded with changes, website checks, payment claims, and payment verification.
- Configured tax and utility records: property labels, tax or utility authorities, public account and parcel identifiers, service type, payment-handling settings, source links, and notes in the dedicated workbook.
- Municipal website results: matched account and property details, dated balances, principal and interest when supplied, upcoming installments, bill references, and posted payment information when available.
- Payment tracking: amounts and dates entered by a user, confirmation references or receipt links, status, the person handling an attempt, and who recorded or checked it.
- Change history: request identifiers, timestamps, user email, action descriptions, and before/after record values used to recover interrupted saves and prevent duplicate changes.
The app has no fields for Google passwords, municipal passwords, bank credentials, or card details. Do not put these in notes or receipt links. Google handles Google sign-in. The application code does not save Google OAuth access or refresh tokens in its records workbook.
What the information is used for
The app uses this information to display tax and utility accounts, request and identify supported public municipal records, distinguish current amounts from future installments, coordinate payment attempts, track confirmations, and produce an owner-configured summary. It preserves dated checks and change history so users can understand where an amount or status came from.
Some websites return no usable result or require a manual account search or human CAPTCHA. The app stops at that requirement and shows the official link and available instructions. It does not bypass an access challenge, invent an account suffix, or infer a zero balance or payment from an unavailable result.
Automatic payment confirmation requires one unambiguous municipal record with an exact matching reference, date, and amount. A zero balance alone is not used to confirm an individual payment. The app does not send information to advertising, analytics, data-sale, or AI-model services.
Google permissions
https://www.googleapis.com/auth/spreadsheetspermits reading and writing Google Sheets. This Google permission can cover all spreadsheets the user can access. The current application code opens the single workbook configured by the owner; it does not browse other workbooks or offer an arbitrary file picker.https://www.googleapis.com/auth/userinfo.emailsupplies the signed-in email used for identification, payment coordination, and the activity record.https://www.googleapis.com/auth/script.external_requestlets Apps Script request supported public municipal websites to retrieve account records.
The web app runs as the person accessing it. Access to working records depends on that Google account’s permissions for the dedicated Sheet. A collaborator with editing access can also edit the underlying workbook directly; the app is not a separate field-level permission system.
Where information goes and who can see it
Google: Google Apps Script processes the app’s requests and Google Sheets stores its records. Authorized workbook collaborators can see information in that workbook. Google also operates sign-in, platform services, and execution diagnostics. The app enables Google’s exception logging, which may contain technical errors and identifying information included in an error message. Access and retention for those platform records depend on Google services and project configuration.
Municipalities and their service providers: when checking an account, the app sends the public lookup fields the selected service needs, such as the municipal account number, parcel, property address, or business owner name. The app uses configured HTTPS providers; it does not send the whole workbook, Google sign-in email, app activity history, or Google authorization tokens to those lookup services. Anonymous website session values needed for a public lookup are temporary and are not saved to the workbook.
People with access to a linked workbook: an owner-authorized Google Sheets IMPORTRANGE connection displays an account summary in another workbook. People who can view that destination can read the imported summary without separate access to the source workbook. Editors of the destination may use that granted connection to import other source ranges. The owner should review sharing for both workbooks. See Google’s explanation of IMPORTRANGE permissions.
Official payment and receipt websites: opening a portal or receipt link takes the user to that website. Any credentials or payment details entered there are handled by that website under its own terms and privacy practices. Property Taxes does not execute the financial payment or download the contents of a receipt link merely because the link is saved.
Retention, correction, and removal
The app keeps tax and utility records, previous website checks, payment history, and activity records in the owner-controlled workbook until the owner changes or removes them. There is no automatic retention deadline or in-app account-deletion button. Changing a current value does not remove previous values from the activity history.
Contact the owner to request access, an export, correction, or removal of information associated with your use. The owner can manage workbook sharing and review the relevant current records, activity history, linked summaries, and any separately retained exports. Removal should account for those related records; deleting one visible row does not erase every copy. Google’s version history, trash, and platform retention may continue to apply.
You can stop using the app and revoke its Google authorization through your Google Account connections. Revocation stops the app’s future use of that authorization; it does not delete records already stored in a shared workbook or remove other collaborators’ access.
Access controls and updates
The app requires Google sign-in, relies on Google Sheet permissions, uses HTTPS for configured municipal requests, validates returned account identities, and coordinates changes with record versions and request identifiers. These controls do not turn the app into a municipal system or a payment processor.
This public information page contains no analytics script, advertising code, or login form. Hosting and linked services may process ordinary web requests under their own policies. If the app’s information handling changes, this page should be updated to describe the implemented behavior.