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.
Legal holds and exceptions
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.
About this version
Sets the existing activation-plus-one-calendar-year and never-activated closure-plus-90-day claim-document schedule, with documented holds, purpose-specific criteria for other records, and honest deletion-request handling.
Document history and reference
- Version 2 — effective
Content reference: 33cdb4421a66a68ee9c41a76e12d90c25f0891b6a070cd4aa36ab21d75b84cd5
