Security & Automated Abuse Prevention Notice

Protecting requested forms

LimoVibes uses Google reCAPTCHA, part of Google Cloud Fraud Defense, on enabled forms to help detect automated submissions, spam and other abuse. It supplements our existing form validation, request limits, access controls and verification steps. A risk score is a security signal, not proof of a person’s identity or wrongdoing.

When information is sent

On a form where this protection is enabled and connected, the Google script loads when you attempt to submit a form that passes its browser validation. It does not load through this integration merely because you view the page or focus a field. Google evaluates technical browser, network and interaction signals, and LimoVibes sends the resulting token for a server assessment before deciding how to handle the submission. This processing can occur even if the form is not ultimately accepted.

The information involved can include an IP address, browser and device information, interaction signals, technical identifiers and the type of form action. LimoVibes does not intentionally include names, email addresses, message text, pickup or destination addresses, or trip details in the reCAPTCHA assessment payload. This integration does not send an account identifier for account profiling.

How protection is used

Administrators can disable protection, observe its results or enforce configured checks on selected forms. The initial public-form rollout uses observation: Google still receives and processes the security information, but the reCAPTCHA result alone does not reject a submission. Existing safeguards continue to apply. In enforcement mode, an invalid verification or a risk result can prevent a submission from proceeding and require another attempt or assistance. Protection is not enabled for every form merely because this notice is published.

Review any on-screen guidance if verification is unavailable. Your request is not confirmed until the form reports that it was accepted. If you cannot complete a form, use the assistance and contact routes on LimoVibes. Leaving the page or disabling protection does not erase information already processed.

Operational records

The form-protection dashboard keeps daily aggregate counts and up to 50 recent diagnostic events for no more than seven days. Those events contain only the time, form action, outcome, limited reason, rounded score and response duration. This feature does not store raw reCAPTCHA tokens, raw IP addresses, user-agent strings, account identifiers or form contents in those operational records. The counts are not Google’s billing record.

Submitted requests, existing rate-limit records and administrative audit history continue to follow their existing access and retention rules. They are not erased or given a new retention period by this feature. See the Data Retention Policy.

Google’s processing and necessary storage

Since April 2, 2026, Google acts as a processor of reCAPTCHA Customer Data, with LimoVibes responsible as controller for its use of the service. Google processes that data for the service under the Google Cloud Terms of Service, Cloud Data Processing Addendum and applicable service terms, including security, fraud and abuse prevention.

reCAPTCHA uses the necessary _GRECAPTCHA cookie for risk analysis. The script is loaded through recaptcha.net; this does not make the feature cookie-free or anonymous. Its necessary security storage is separate from optional analytics, remembered preferences, advertising and marketing. Using a protected form does not grant any of those optional permissions or device-location permission. See the Cookie Policy.

Your information and existing permissions

This security feature does not publish private information, change who may receive a quote, or replace the permission required to submit a request. Google Maps address search is a separate feature described in the Google Maps & Address Search Notice; its disclosures remain unchanged.

This notice applies from actual publication and does not rewrite earlier policy versions, requests or agreements. For privacy questions, information requests or help with a security check, use the contact and privacy-request routes in the Privacy Policy.