Privacy

Account and workspace data

When you create an account, the app stores your name, email address, email-verification status, and authentication records. Session records can include an IP address and browser user agent. Creating the first private workspace stores the business name, industry, and city you provide. The workspace also stores its business description, public website URL, trusted contact name, notification email, source connection statuses, and website verification challenge and expiry. If you connect Google Business Profile, the app stores an encrypted refresh token for your account, the one selected location, imported review text and ratings, reviewer display names when supplied, provider timestamps, and private reply drafts with their approval state. The initial trusted contact name and email come from your account; you can edit them in the workspace. The challenge is a technical DNS ownership check, separate from an availability check. Billing records store your selected plan and interval, the most recently checked provider subscription status and period end, and your monthly AI draft usage count.

Checks and monitoring events

An owner can run a one-time availability check against the saved public website URL. It is not background monitoring. The workspace records when the check ran; its result is returned to the signed-in owner. The app also stores monitoring events with a category, source, summary, optional details, and occurrence and creation timestamps. The event endpoint scopes reads to the signed-in owner and returns up to the latest 100 events.

An owner can authorize one Google Business Profile location; the app reads its reviews only when the owner connects or refreshes that location. Review text, rating, and the reviewer display name when present are sent to the Polsia-managed AI proxy to request a reply draft. Drafts stay private and Pending until the owner approves them. Approval only makes text available to copy: Glintwarden does not send or publish replies. Contact forms and social messages are not connected. The sample report is fictional.

Account setup and contact messages

Free account creation uses your name and email through the configured sign-in provider. Workspace setup saves the business name, industry, and city to the private workspace owned by that account. Free signup does not collect payment details. Paid subscriptions are created through hosted provider checkout. The provider handles card entry and payment details; Glintwarden does not store card numbers. Billing status is read from the provider for the signed-in account, and subscription management, payment methods, and invoices open in the hosted customer portal.

A message sent through the contact page includes your name, email, message, and submission time. The app saves that message, then tries to record it in the Polsia dashboard; if that does not work, it tries the company inbox. The contact form does not send a confirmation email to you.

Site analytics

The site includes Meta Pixel page-view tracking. When the deploy supplies its Polsia analytics setting, a Polsia page-view beacon also runs and stores a random visitor ID in browser local storage to distinguish repeat visits. These services receive information about site visits under their own policies.

Deletion requests

There is no self-service account or event deletion route. You can request deletion through the contact page; requests are handled manually. No deletion turnaround or data-retention window is promised here.