Privacy Policy & Your Quote

1. Information we handle

Information supplied by customers

Quote requests can include your name, email, telephone number, property address and unit, selected services, measurements, surfaces and conditions, fence dimensions and sides, trash-bin sizes and quantities, project descriptions, photographs and other permitted files. We keep your submitted answers and applicable consent evidence with the request. Optional answers remain optional; an explicit unknown answer is not a measurement you confirmed.

Customer account and service records can also include profile details, scheduling and access preferences, appointments, reminder choices, messages and attachments, proposals, invoices, payment status, and any signature or response you submit. A proposal acceptance and a separate communication-consent choice are recorded as different actions.

Crew-member and administrator information

Authorized staff records can contain names, contact details, addresses, avatars, account roles and permissions, assigned work and scheduling information. Work-related messages, actions and permission changes can be recorded for business operations and security. Optional location sharing is described below; it is not enabled just by reading this page.

Information generated during use

The application and hosting services process connection and request information such as IP address, request time, browser or app details, security events and operational errors. Account access can generate session, trusted-device, passkey and notification-registration records. Selected device features can provide additional information only as described in the permissions section.

2. Why information is used

• Respond to inquiries, understand the work requested, check the service address, prepare pricing and project documents, and deliver the requested service.
• Provide customer and crew access, apply account permissions, associate records with the correct account, and detect or investigate unauthorized or repeated requests.
• Coordinate appointments, assigned work, approved reminders and related customer or staff communications.
• Issue invoices, hand off supported payments to the selected payment provider, reconcile payment status, and maintain business and consent records.
• Display authorized files and documents, publish only selected gallery material, and support configured integrations or approved assistance features.
• Maintain and troubleshoot the application, recover from failures and protect records through authorized backups.

Submitting a quote does not itself confirm an appointment, accept a proposal or authorize payment. The contact-consent wording displayed in the form remains authoritative for that choice; this policy does not silently grant additional permission.

3. Sharing and optional services

Authorized business staff receive the information needed for their permitted work. Hosting, storage and delivery services process information needed to run this installation. The services below depend on the operator's configuration and the feature you use; listing a supported option does not mean every provider is connected or receives your information.

• Email and SMS: the configured mail service and intended recipients receive the address, subject and message content needed for delivery. The selected SMS gateway receives telephone/sender information, message text and delivery identifiers. Supported gateways include Infobip, Plivo, SignalWire, Sinch, Telnyx, TextBee, Twilio and Vonage, plus Textedly through a Zapier relay. TextBee also uses a dedicated Android/SIM delivery device. Only the configured workflow is used; ask the business which service handles its messages.
• Browser push: when you explicitly permit and register a supported browser, its push service (such as Google, Mozilla or Apple) handles a subscription endpoint and generic wake-up signals. Subscription endpoints are protected server-side. The browser retrieves eligible notices through your current signed-in web session; account changes, sign-out, expiry and revoked access prevent access to the former account's notices. Browser permission, saved preferences and confirmed delivery are different states. Device permission can be withdrawn in browser settings.
• Push notifications: when configured and registered, Google Firebase Cloud Messaging processes a device token and event data for eligible notices. Some notices contain appointment timing or decision details; not every payload is anonymous. Local device reminders are a separate feature.
• Address checks and form protection: optional USPS, Melissa address-only checking or Google Maps Address Validation receives the address fields needed for its check, not the quote photographs or full project description. Google reCAPTCHA or legacy Cloudflare Turnstile, when used, processes verification and technical browser/connection data. Local character matching is handled by this installation instead of an external CAPTCHA service. A suggested address is not proof of property ownership.
• Payments: supported checkout through Stripe or PayPal, including eligible Venmo through PayPal, shares transaction amounts, currency and invoice/attempt identifiers; Stripe can also receive a receipt email. Payment details entered with the provider are governed by that provider's processing. VistaRinse records transaction identifiers, status and related accounting evidence rather than asking for card numbers in the quote form. See Stripe's privacy policy and PayPal's privacy statement.
• Maps and arrival information: eligible visit tracking can send crew coordinates and a service address to Google Routes for route/arrival calculations. Android map views request tiles directly from OpenStreetMap; the requested map area/zoom and normal connection details, including IP address, reach that service. See Google's privacy policy and the OpenStreetMap Foundation privacy policy.
• Connected calendars: an enabled Google Calendar or configured CalDAV service/device can receive appointment titles, times, locations and scheduling notes. Those notes may contain personal information. Disconnecting does not erase events or backups already held by the external service.
• Backups: selected business/configuration components can be included in protected backup archives on hosting storage, connected Google Drive or the operator's configured FTP/FTPS destination. Archive encryption, transfer protection and destination retention are separate concerns; legacy FTP transport is not encrypted. The operator must review which destinations and copies it uses.
• Optional AI assistance: after enabled configuration and explicit preview approval, selected text, service measurements and up to three reviewed images can be sent to OpenAI for advisory analysis. Preparation redacts known identifiers and re-encodes images, but visible image details or remaining text may still identify a person or property. The request's storage setting does not guarantee zero provider retention. See OpenAI's privacy policy. AI assistance is not automatically enabled by submitting a quote.

Enabled extensions or diagnostics may introduce additional processing, as described below. Contact the operator for its currently enabled providers, hosting arrangements and any further disclosure relevant to your information.

4. Android permissions and device features

Optional crew location sharing, including background use

An authorized crew member can explicitly start location sharing for an assigned visit after the applicable disclosure and permissions. VistaRinse uses location, background-location and foreground-service capabilities to send latitude, longitude, accuracy and capture timing to the selected installation. A user-started sharing session can continue while the app is minimized or its task is swiped away; it is not limited to the screen being open.

The ongoing sharing notification includes a Stop action. Use Stop or revoke the relevant Android permission to prevent further device updates. If the server cannot be reached, the last server-side live point/session can remain until expiry. Permitting location alone does not start sharing, and ordinary sign-in does not require you to start it. Authorized staff and eligible customer visit views can receive arrival information. A customer viewing the crew's arrival map is not thereby sharing the customer's own device location.

Photos, files, downloads and QR scanning

Attachment and avatar workflows access files or images you choose through Android's picker rather than scanning the entire photo library. The connection QR feature uses the Google Play services code scanner when you choose to scan; its camera/scanner interface is separate from a background camera feed. The app does not use the Android address book, microphone or personal SMS inbox for these workflows. Customer SMS conversations are business messages handled through the configured service, not a general reading of your phone's messages.

Files you deliberately save, print, email or share can be copied to the selected storage destination or receiving app/service. Those exported copies are outside VistaRinse logout and server-deletion controls.

Notifications and biometrics

Android notification permission controls whether supported app notices can be shown; it does not itself enable every reminder or contact channel. Device reminders can be restored after a restart or time change, but this does not start GPS sharing. Optional biometric unlock uses Android's protected authentication/Keystore mechanisms. VistaRinse receives the authentication result, not a fingerprint image or biometric template. Passkey providers manage their own authentication and synchronization.

5. Account access and security data

Customer and crew sign-in use the selected installation and account-specific workflows. Authentication can involve an email/SMS code, password, passkey, trusted-device enrollment and short-lived security verification. The server retains the security records needed to validate access, identify a registered device or credential and prevent replay. A saved passkey is associated with its account and relying-party domain; the provider holds the passkey's private material rather than VistaRinse receiving your fingerprint or exporting a private key.

Android stores supported session, saved-sign-in and offline data in app-private storage with protected encryption for the relevant vaults and offline snapshots. Account/site bindings prevent using one installation's session as another installation's login. Device and app security controls do not grant another account access to your records.

Signing out, removing a saved sign-in or revoking a device changes access but is not deletion of business records. If a remote revocation cannot be confirmed because the network is unavailable, do not assume the server record was removed. A credential provider can retain or synchronize its own passkeys according to its account settings and policies.

6. Browser storage, local caches and diagnostics

Essential browser sessions support sign-in and security tokens. A quote form can temporarily retain entered information for error recovery. Appearance and other interface preferences may be stored locally; Auto follows the device/browser theme. Reading this standalone policy does not require sign-in or consume a pending quote's saved form state.

Android retains selected-server and interface preferences, notification/reminder state, protected account data and eligible offline snapshots. Offline snapshot reuse is limited by its freshness policy, including a maximum seven-day fallback window; this is not a promise that every stored byte is erased exactly at seven days. Map tiles, temporary files and non-secret preferences use separate caches, and not all of them are encrypted. Removing local data does not remove already exported files or remote records.

Hosting and application logs can retain technical events needed for operations and security. An enabled diagnostics extension can process request/status/duration, error, validation or message context according to its installed implementation and settings. Approved plugins can add further website, staff or customer features and assets. The business must review the actual extension's data, recipients and retention; the base application cannot establish a blanket claim that every deployment has no analytics or tracking. Operational crew location sharing is a separate function, not evidence that advertising analytics is active.

The operator can explain its enabled diagnostics/plugins, any additional processors and relevant choices. Do not include passwords or sensitive customer information in troubleshooting messages.

7. Files, proposals and public photographs

Quote and follow-up files are associated with their request and made available through the application's authorized workflows; submitting a private project file does not automatically publish it in the gallery. Permitted attachments can contain personal information in their visible content or metadata. Do not upload passwords, identity documents, payment-card details, alarm codes or information you are not authorized to share.

Private proposals, invoices and authorized document downloads can contain customer details, service descriptions, pricing, signatures and selected files. Some issued links act as access credentials: anyone receiving a forwarded link may be able to use it while valid. Keep these links private. Expiring or revoking a link stops future access through it but cannot recall downloaded copies or sent emails.

Administrators choose which gallery projects and processed before/after images to publish. Published material is visible to visitors and can be copied. Image processing does not automatically hide faces, house numbers or other visible personal details. Publication and removal must be reviewed by the business; unpublishing does not remove copies already retained elsewhere.

8. Retention and deletion

Customer account deletion is separate from deleting a business record. The verified customer workflow removes the customer sign-in identity, credentials and unneeded account information while retaining Quotes, Proposals, Invoices, signatures, amounts, payment history and the personal information and associations necessary for business operations, security and recordkeeping needs. It does not cancel appointments or services, change balances or refunds, alter existing payment or document statuses, or revoke already issued business-document links. Those links remain subject to their existing access controls.

Quote, customer, crew, appointment, message, proposal, invoice, consent and related business records do not share a single automatic deletion deadline. Attached records, correspondence, approved AI advisories and backup copies can remain until separately reviewed or removed under the operator's operational, security and applicable recordkeeping requirements. Contact the business for the retention applicable to your information; this policy does not invent a fixed legal or operational period.

Some security codes, access grants and live tracking records expire. Expiry stops an access or freshness function; physical cleanup can be deferred or performed in bounded maintenance batches. Staged, unattached quote files expire after two hours, with removal attempted during later cleanup; this is not a guarantee of deletion at that precise time or of deleting files already attached to a request.

Archive retains a record. A confirmed permanent deletion is dependency-checked: linked billing, payments, proposals or appointments may require separate resolution, and failed private-file removal can remain in a protected cleanup queue. Minimal deletion/audit or replay-prevention evidence can remain. Clearing an activity-log display, revoking a device or closing a link is not comprehensive erasure.

Deleting a live record cannot recall sent messages, downloaded/shared files, provider records or other backup copies. Backup destinations can have separate trash, history and retention. The business must review these copies and explain any information retained when responding to a deletion request.

9. Your choices

Use the customer portal or Android controls available to your account to review profile details, appointment reminders and supported notification channels. Appointment reminder choices and Android's device notification permission are separate. Changing a preference does not recall a reminder or message already handed off for delivery.

You can withdraw optional device permissions through Android settings, stop an active location-sharing session through its controls, manage passkeys or trusted devices through the available account settings, and return appearance settings to Auto. Clearing local browser/app data or uninstalling the app does not by itself delete server records or the provider's copies.

Contact the business to request access, correction, changes to contact preferences or deletion. Crew members should also contact their authorized administrator about employment-related records, work assignments and account access. Not every account has permission to edit every business record.

10. Request account or data deletion

Customers can use Request Account Deletion on this installation, or open My Profile → Delete My Account in their private portal. Sign in using the existing passkey or Email/SMS verification flow, review the information retained, and explicitly confirm deletion. Opening the link, signing in or viewing the confirmation does not delete an account. This process removes customer account access; it is not a promise that all personal information or associated business records are erased.

To request deletion of your VistaRinse customer or crew account and associated personal information, email office@vistarinse.com with the subject VistaRinse account or data deletion request. Identify this installation, the email or phone linked to your account, and the request reference if relevant. You can make this request without signing in or keeping the app installed.

Do not send a password, security code, passkey contents or identity document. The business will need to verify that the request concerns your account and review linked work, invoices, payments, security and any applicable recordkeeping obligations. An emailed privacy request is not immediate automated erasure. Customer self-service account deletion is a separate verified process and retains the business records described above. The business should explain what can be removed and any retained information and reason. Closing a session, disabling an account or archiving a record is not the same as deleting its data.

11. Security safeguards

VistaRinse uses HTTPS, server-side authentication and ownership/permission checks, security tokens and rate limits. Private configuration and supported secrets use protected storage. These safeguards do not mean that all business records, messages, downloaded copies or backups are end-to-end encrypted or immune from unauthorized access. Authorized business users and providers may need to process information for the stated functions.

No online system or email service can be guaranteed completely secure. Use the installation's correct secure address, protect your device and account, and contact the business if information appears to have been accessed or shared incorrectly.

12. Policy updates

The last-updated date identifies this notice. The operator should review this policy when it changes settings, providers, permissions or data-handling practices, and explain material changes as appropriate. Other VistaRinse installations are operated separately and can have different settings and contacts. Follow the privacy link for the installation you actually use.

External services apply their own privacy practices to information they receive. A privacy page or a successful integration test does not mean that Google or another provider has approved the application.