Skip to content
LimoVibesRequest a Quote
LimoVibes

Data Retention, Deletion, Legal Hold, and Records Policy

Purpose-based schedules, deletion, minimization, legal holds and evidence.

← All policies and disclosures

Version 8 Effective

Retention is tied to the record and its purpose

LimoVibes uses different retention rules for different records. A payment, closed support case, expired access link, removed public listing, or account sign-out does not by itself delete every associated record. This policy supplements our Privacy Policy.

Private ownership-verification files

Business-registration documents and owner identification submitted for a listing claim are used to verify ownership and handle related disputes. They are not published as listing media.

  • Activated claims: Files are retained while the claim is being completed and are scheduled for deletion one calendar year after successful claim activation.
  • Claims that never activate: For a rejected, withdrawn, or abandoned claim, files are scheduled for deletion 90 days after the claim is closed.

The claim's recorded workflow establishes the activation or closure event. Payment alone is not activation. Later renewals or an ownership change do not by themselves restart an established activation-based deadline. These are LimoVibes business retention periods, not universal California statutory minimums.

Criteria for other records

  • Account and listing records: Whether the account or listing relationship remains active, whether a change or ownership question remains unresolved, and whether a reliable record of an earlier decision is still needed.
  • Quote, contact, and support records: The requested service, ongoing replies or follow-up, unresolved concerns, and a relevant dispute or legal obligation. An expired access link is an access control, not a promise that the conversation has been erased.
  • Orders, payments, refunds, and billing correspondence: Reconciliation, outstanding obligations, refunds or chargebacks, and applicable accounting, tax, dispute, or other legal recordkeeping requirements.
  • Permission, policy, moderation, and audit records: Evidence of the action and version involved, accountability for decisions, applicable rights requests, and the duration of a relevant dispute or legal obligation.
  • Technical and security records: The need to maintain access, detect abuse, investigate an incident, and preserve relevant evidence. Some disposable operational records have separate cleanup rules; these do not delete all security or legal records.
  • Browser storage: The durations and controls described in the Cookies Policy.

These criteria guide retention decisions; the application does not apply one blanket automatic deletion deadline to every category. Retention must remain connected to a relevant purpose and applicable legal obligations, rather than keeping information indefinitely merely because storage is available.

A documented legal hold can pause deletion of relevant records. Claim-document holds record a reason and an authorized action. Releasing a hold does not restart the original schedule; overdue files can become eligible for the next cleanup. Applicable law can require earlier deletion or a different retention treatment.

Deleting a verification file does not itself erase the claim decision, payment record, or the record that the file was handled and deleted. Requests concerning related records are assessed separately. This policy does not promise that a file-removal action deletes every independently retained copy, export, or record held by another service.

Asking about retention or deletion

Email privacy@limovibes.com or use our privacy request form. Include a listing, claim, order, or support reference when available, but do not send identity documents through ordinary email or the contact form. We may need to verify identity or authority and identify any applicable exception before acting. A submission receipt is not confirmation that deletion has been completed.

Listing publication and quote requests

From this version’s actual publication, this section describes the listing-publication features and governs new quote requests and newly authorized expansions. For those features it replaces inconsistent descriptions earlier in this document. It does not rewrite earlier accepted orders, prices, permissions or recorded promised quote-allowance dates. Applicable notice and any required renewed agreement remain necessary before a material change is applied to an ongoing arrangement; publishing this version alone does not supply either. Other provisions continue to apply. Your quote form identifies the route available for your request before you submit it.

Listing publication is not a retention deadline

Approved listings do not automatically expire because a Free quote allowance or paid membership ends. A paid listing whose paid rights end continues as a Free listing. This does not prevent an owner from deleting a listing or LimoVibes from moderating, suspending or removing a listing for another valid reason.

A public listing remaining active does not require keeping every quote, message or verification artifact indefinitely. Billing and historical policy receipts retain their separate retention requirements; ending quote access does not rewrite them.

Quote lifecycle and evidence

Quote trip and contact records and provider conversations are retained using the purpose-based criteria in this policy, including completing the request, resolving disputes, preventing abuse and satisfying applicable recordkeeping duties. The response deadline and closure stop new assignments; neither promises immediate erasure or a fixed automatic deletion date for these records. Verification challenges follow their existing expiry rules. Nonselected routing diagnostic evidence is eligible for bounded automated cleanup under the applicable diagnostics-retention setting, subject to active legal holds.

Diagnostic cleanup does not erase the request, its conversation, actual recipient accounting or required permission evidence. Documented legal holds take precedence. These cleanup rules do not set a general automatic deletion date for quote contact details or conversations. Deletion and restriction requests use the existing verified privacy request route. A provider that already received a request is independently responsible for its applicable retention obligations.

Directory inquiries, receiving access and platform assistance

From this version’s actual publication, this section governs new quote requests and newly authorized expansions that use directory inquiry enrollment or platform assistance. For those features it replaces inconsistent descriptions earlier in this document, including any suggestion that quote-only access grants or always requires verified listing ownership. It does not rewrite earlier accepted orders, prices, permissions or recorded promised quote-allowance dates. Applicable notice and any required renewed agreement remain necessary before a material change is applied to an ongoing arrangement; publishing this version alone does not supply either. Existing requests retain their recorded permission, recipients and access limits.

Enrollment and quote-access evidence

Administrative inquiry approvals, directory source references, prospective allowance dates and receiving-access records are operational evidence. They follow the existing purpose-based criteria for request handling, security, disputes and applicable recordkeeping. A new transition allowance preserves the fact that older dates are unknown; it does not rewrite historical evidence.

This update introduces no general automatic deletion date for quote contact details, trip payloads, conversations or enrollment records. Verification challenges keep their existing expiry rules, and the bounded nonselected routing-diagnostics cleanup remains subject to the existing protections and legal holds.

Protected quote conversations and notifications

From this version’s actual publication, the following describes new quote-workspace actions and notifications. Earlier policy versions and permission receipts remain unchanged. New access methods do not increase an existing request’s authorized recipients, permit marketing, or change accepted commercial terms. Where a material change requires separate notice or agreement, publication alone does not provide it.

Quote records and separate expiry clocks

Archiving, closing a conversation, expiry of an email link and expiry of a session are not deletion deadlines for quote records. Quote records are handled under the retention purposes, configured schedule and applicable exceptions in the retention policy. Holds for a dispute, security matter or required recordkeeping can defer deletion. A privacy request requires identity and scope verification; it does not by itself authorize removal of another participant’s independent records. When eligible quote content is removed, minimal non-content records may remain to record the request, authorized disclosures, delivery outcomes and completed privacy action. Email copies already delivered to a participant’s own mailbox cannot be recalled by deleting the LimoVibes record.

Access links, quote-only sessions, request allocation, conversation availability and storage retention have separate clocks. Revoking access prevents further authorized viewing through that access method; it does not claim to erase information already received. Historical consent and accepted-price records are not rewritten by a workspace upgrade.

Quote requests, email replies and optional secure conversations

From this version’s actual publication and activation, these provisions govern newly accepted quote requests and supersede earlier descriptions of mandatory customer email confirmation, workspace-only replies, or omitted itinerary and quote terms for those requests. Historical request permissions, secure-only choices, policy versions and permission receipts remain unchanged. Existing requests do not receive broader disclosure or new sharing permission merely because this version is published. New access methods do not increase an existing request’s authorized recipients, permit marketing, or change accepted commercial terms. Where a material change requires separate notice or agreement, publication alone does not provide it.

Quote records and separate expiry clocks

Archiving, closing a conversation, expiry of an email link and expiry of a session are not deletion deadlines for quote records. Quote records are handled under the retention purposes, configured schedule and applicable exceptions in the retention policy. Holds for a dispute, security matter or required recordkeeping can defer deletion. A privacy request requires identity and scope verification; it does not by itself authorize removal of another participant’s independent records. When eligible quote content is removed, minimal non-content records may remain to record the request, authorized disclosures, delivery outcomes and completed privacy action. Email copies already delivered to a participant’s own mailbox cannot be recalled by deleting the LimoVibes record.

Access links, quote-only sessions, request allocation, conversation availability and storage retention have separate clocks. Revoking access prevents further authorized viewing through that access method; it does not claim to erase information already received. Historical consent and accepted-price records are not rewritten by a workspace upgrade.

Administrator-reviewed provider invitation emails

From this addendum’s actual activation, an administrator may review an existing transportation inquiry and send its permitted trip details in a standard invitation email to specifically selected eligible providers. This includes a retained request that has been properly recovered for matching. The request must already authorize sharing with those providers within its existing recipient allowance. The invitation may contain the customer display name, itinerary, local pickup time, passenger and luggage counts, service requirements, notes, permitted contact information, and a private link to the assigned conversation.

This is a limited change to the earlier workspace-only invitation-content rule for historical requests. It applies only to a new, explicitly reviewed administrator invitation after activation; publishing this addendum alone does not expand an old email, reopen a request, add recipients, or resend anything. The administrator instruction, selected providers, trip revision and applicable disclosure rule are recorded separately. They are not recorded as customer consent and do not replace historical permission or policy-acceptance records.

The customer’s recorded contact preference continues to control whether a direct email address or telephone number is disclosed. A platform contact preference does not expose either contact field. This invitation rule does not enable email replies, disclose previous conversation messages or another provider’s quote, override an explicit secure-only message, or change customer update and reminder permissions. Where email replies are unavailable, the invitation directs the provider to the secure conversation.

Privacy restrictions, withdrawn sharing permission, protected closures, provider access restrictions and applicable deadlines continue to apply. An administrator cannot use this process to increase the authorized recipient limit, permit marketing, confirm a booking or change billing or subscription terms. The exact provider and current access are checked again before delivery. Email copies can be retained or forwarded outside LimoVibes and cannot be recalled; recipients must use the information only for the requested transportation inquiry.

Free listings, card verification and direct quotes

From this version’s actual publication, this section governs the configurable card requirements described below and supersedes inconsistent descriptions of those requirements earlier in this document. Other provisions continue to apply. Earlier accepted transactions, policy receipts, ownership decisions and recorded benefit dates are preserved. Applicable notice and any required renewed agreement remain necessary before a material change is applied to an ongoing arrangement; publication alone does not supply either.

Current card evidence and historical records

Stripe processes card details in its secure interface. LimoVibes does not store full card numbers or card security codes. We keep limited verification and operational records, including provider and listing or application references, Stripe customer, session, setup-intent and payment-method references, account and environment bindings, verification or revocation status, timestamps and limited card display details. We use these records to verify the authorized account’s card, apply the stated quote eligibility rules, prevent misuse and recover interrupted verification. A pending claimant’s records do not give that claimant the current owner’s rights. Private card and verification records are not published in listing search results or public profiles.

Verification records follow the existing purpose-based retention, access-control, privacy-request and legal-hold rules. Records needed to explain accepted applications, transactions or disputes may be retained separately from current card eligibility. Current verification can be invalidated when the recorded payment method is known to be detached or revoked. Deleting or changing current verification evidence does not rewrite historical policy receipts, accepted submissions or financial records.

About this version

Clarify independent Free submission and direct quote card settings, secure verification, unchanged approval and payment safeguards, and preservation of historical records.

Document history and reference

Content reference: 8cfa805c817d4af53beee2048868ea25cc294e47bc2476f192bc009d067c62e0

Questions or need assistance? All policies and disclosures