Last updated: October 12, 2026.
Overview
Fascinante Digital LLC operates this website and its business visibility review. This policy describes the information used to provide those features and connected business messaging pilots, protect them from abuse and respond to requests. Some dashboard screens display sample content rather than connected business services. They do not mean that we currently provide every feature shown.
Information We Collect
For a business review, we use the business you select through Google Places and information returned by our data providers. This can include a business name, public address, phone number, website, category, rating, review count and availability of opening hours. When a public website is available, the review may include its URL, response status and selected HTML fields. Public business information can also relate to an individual, including a sole proprietor.
If you request a copy by email, you provide an email address. We pass the address and the existing report to Resend to send the requested copy. Our report delivery feature records an encoded fingerprint of the address and whether the sending provider accepted the request; it does not retain the address in plain text in our report delivery records. This fingerprint can still relate to you and is not anonymous. Resend processes the actual address and message.
For accounts, we use information required by the sign-in method, such as name, email, profile image and account or session identifiers. Password sign-in uses a password hash. Google sign-in requests identity information; it does not grant permission to manage your Business Profile. Contact forms send the information you enter to our designated inbox. We also store your email address in HubSpot to organize follow-up on your request, reusing an existing contact when one is found. This connection does not copy your name or message to HubSpot or subscribe you to marketing. Hosting and verification providers may also process technical information to deliver the service and prevent abuse.
How We Use Your Information
We use business information to generate and display a dated review, reuse an existing review where applicable and explain basic findings. Requesting an email copy does not generate a new review, create an account, or subscribe you to marketing. The copy is sent only when requested. An email accepted by the sending provider is not a guarantee that it reached your inbox.
Account information supports sign-in and session management. Contact information lets us respond to your request. Technical and request records support abuse prevention, deduplication, troubleshooting and control of provider usage. We do not claim that the review verifies ownership of the business or the recipient email address.
Retention and Security
A business report is eligible for reuse for 30 minutes. Its stored result is scheduled for deletion after 24 hours. Completed or failed review records are eligible for deletion after 30 days when no provider request remains unresolved. Email delivery records are removed when their related scan is deleted. Records of requests whose outcome is uncertain can remain longer while they are investigated, to avoid repeating a potentially charged request. A daily cleanup processes eligible records; these intervals do not promise deletion at an exact instant.
Account information is kept to support sign-in and account security; contact messages are kept in our inbox so we can handle your request. Contact email addresses in HubSpot support follow-up. The report cleanup does not remove accounts, inbox messages or HubSpot contacts. We have not implemented a scheduled deletion period for these records. Requests concerning them require an individual review; contact us to ask about access or deletion. A contact may remain in HubSpot if sending the inbox notification fails; we do not treat that record as confirmation that your message was delivered. Hosting and email service logs follow provider retention practices and are not deleted by the report cleanup. Our implementation uses server-side credentials, encrypted connections, restricted database roles and verification for public forms. We do not claim that these measures eliminate every risk or that we perform recurring security audits.
Providers and Verification
We use Google for business discovery, maps, optional sign-in and connected Analytics and Search Console reports; DataForSEO for business and website observations; Neon for database storage; Vercel for hosting; Resend for email; HubSpot for contact follow-up; Meta for connected Messenger and WhatsApp messaging; and Cloudflare Turnstile for verification. These providers process information needed for their respective services under their applicable terms and privacy policies. Their retention is not necessarily the same as ours. Read the privacy notices for Google, DataForSEO, Neon, Vercel, Resend, HubSpot, and Meta. See the Cloudflare Turnstile Privacy Addendum for verification processing.
Requesting a report copy does not add your address to HubSpot or a marketing list. The Contact connection runs on our server and does not add HubSpot tracking to your browser. This policy does not promise that third-party processors retain no information or that technical logs never contain personal information.
Cookies and Browser Storage
Sign-in uses cookies to maintain your session. Display preferences, such as theme and sidebar state, can be stored in cookies or local storage on your device. Dashboard preference cookies can last up to one year; the sidebar preference lasts seven days. The business report page uses session storage to remember the report identifier within that browser tab. These preferences and identifiers are separate from the server-side report retention described above.
Google maps, business search, sign-in and Cloudflare verification involve requests to those providers. Their privacy notices describe their processing. Email open and click tracking are disabled in the sending domain configuration reviewed for this policy.
Connected Google Reports
Approved pilot users can separately connect Google Analytics or Google Search Console to the dashboard with read-only permission. Analytics provides aggregate website traffic reports; Search Console provides search performance, such as clicks, appearances in search results, queries and pages. We list the properties accessible to the connected Google account so you can choose what to link. Signing in with Google alone does not connect either service. These connections do not install tracking, change Google settings or subscribe you to marketing.
We store the account connection, encrypted access and refresh tokens, and the properties you select or link. A business owner or administrator must explicitly agree to share a property with the selected business. Members of that business can then view its connected reports in the dashboard. Access to a property in Google does not automatically share it with all your businesses.
Reports are fetched when requested; these modules do not save their responses as a report history in our database. Connection records, personal selections and business links are not covered by the public business report cleanup and have no scheduled deletion period. You can disconnect a service in dashboard Integrations; this removes its local connection and dependent property links, including links shared with other businesses, while preserving your sign-in and the other service's connection.
Disconnecting here does not revoke authorization in Google. You can separately revoke authorization through your Google Account connections; this can affect connected services using the same Google application. Revocation prevents further authorized requests but does not automatically delete our connection records. Contact us about deletion. Our current connections require the Google identity to match your verified sign-in account.
Connected Business Messaging
Our connected messaging pilots use Messenger and WhatsApp to display conversations for an explicitly linked business. When you message that business, Meta delivers events to our server. We store message and sender identifiers, timestamps, message text and relevant message metadata. WhatsApp can also provide your display name and phone number. We use these records to organize conversations, prevent duplicate processing, show delivery information where available and troubleshoot the connection.
The Messenger reception pilot does not request your profile name or photo. It records attachment types without downloading their media or retaining their media URLs. WhatsApp events can contain attachment metadata; the current inbox does not download or display those attachments. Avatar initials or a reference in the dashboard are not a profile photo supplied by Meta.
Only verified account holders with membership in the linked business can read its conversations in the dashboard. WhatsApp replies, where enabled, are limited to the business's owners and administrators and the configured pilot recipient. We store the operator identifier, recipient identifier, reply text, sending attempt and provider result, including delivery states where returned. Messenger is reception-only in the current pilot. These features do not subscribe you to marketing or send automated replies.
Meta processes messages under its own terms and privacy notices. Neon stores our conversation and sending records, and Vercel hosts the receiver and dashboard. Our messaging records have no scheduled deletion period and are not covered by the business-report cleanup. Disconnecting or disabling a connection does not automatically delete stored conversations. To request access, correction or deletion, use ; we may need to verify your identity and authority over the relevant records. We do not promise automated export or deletion controls that are not implemented.
Optional Website Analytics
If you accept optional Analytics, we use Google Analytics through Google Tag Manager to understand use of the public website, including pages viewed and interactions such as scrolling, link clicks, form interactions, downloads and video use where applicable. Google may process browser identifiers, device and browser information and usage events. Sign-in and dashboard pages are excluded from this integration. You can reject Analytics and continue using the website, or change your choice through Analytics preferences in the footer. We keep that choice in local storage until you change it or clear the site's browser storage.
Rejecting or withdrawing stops future collection by this integration. It does not automatically delete information already sent to Google or cookies already stored in your browser. We do not enable advertising tracking through this choice and do not add an advertising pixel.
Analytics uses cookies such as _ga and _ga_<identifier>. Google documents a default expiry of two years; browsers can impose shorter limits, and cookie expiry can be renewed during use. This cookie period is separate from Analytics data retention. See Google's Analytics cookie documentation and Google's privacy policy.
Our Google Analytics property is configured to retain user and event data for 14 months, with new activity renewing the retention period of a user identifier. These controls do not govern standard aggregated reports. They are separate from the retention and cleanup of business reports described above. See Google's explanation of Analytics retention.
We configure redaction of email addresses and selected URL parameters before Analytics sends events. This is an additional safeguard, not a promise that provider logs are anonymous or that automatic redaction detects every instance of personal information. We do not deliberately send contact form contents, recipient email addresses or business names as custom Analytics event parameters.
Your Choices and Contact
You can read the public report without requesting email delivery or creating an account. You can choose not to use Google sign-in or submit a contact form. To ask about information associated with you, or to request access, correction or deletion where applicable, use . We may need information to verify and process a request. We do not promise self-service export or deletion controls that are not implemented.
Policy Updates
We will update this page when the described practices change. The date above identifies the current revision. If you have questions about this policy or a specific feature, contact us before submitting information.