Privacy
What we collect, and what happens to it.
Written about this website specifically, not about websites in general.
What the form collects.
- What you type
- Your name, the contact route you choose, what needs doing and how you relate to the property. You may also add optional ZIP, timing and photos, plus a work category if one fits.
- Files you attach
- Photos you choose to send. The browser removes embedded metadata while it prepares them, and the server stores them privately and scans them before issuing an opaque reference. They are never published from this form.
- Technical details
- The page where you submitted the request is kept with it. When a trusted network source is available, it is used transiently for abuse control and stored only as a scoped hash in short-lived counters. The public form does not retain a browser profile.
- Your consent
- Whether you allowed request processing, whether you separately chose marketing contact, when you acknowledged the form, and the policy versions shown at that time.
Who sees it.
Livanzh LLC first stores an accepted request in the website database. The approved request fields and clean photos are then delivered to Odoo, the customer-record system used to follow up and coordinate the work.
Telegram receives a short operational notification with the public request reference, request type, your name and chosen contact details, any selected audience or service, optional ZIP and timing, your description, the active-risk flag, submission page and photo count. Clean photos are sent separately to the same private work chat when you attach them.
Telegram does not receive the website's internal request ID, private storage key, network-source hash, browser profile, consent wording or Odoo record ID. Odoo and Telegram are service providers receiving these details for request handling; they are not advertising networks.
We do not sell your information, we do not use it for advertising, and we do not send it to advertising networks.
Optional anonymous analytics.
Livanzh LLC uses optional first-party analytics only after you allow it. It records aggregate event counts such as a fixed page class, a request step or a contact click. It creates no visitor or session identifier and does not store an analytics cookie, fingerprint, raw IP address, user agent, query string, form content or filename.
Your request-processing and marketing choices are separate and do not turn analytics on. You can change this choice at any time.
Anonymous analytics events are kept for up to 425 days under the current configuration. This period is provisional pending legal review.
How long it is kept.
The current provisional schedule keeps the raw website copy of an Odoo-delivered request and its private photos for up to 30 days before redaction. A reduced delivery audit can remain for 365 days. Abuse-control windows expire after they can no longer affect a current hourly or daily limit.
A request that has not reached the customer record is not erased merely because time passed; it stays available for reconciliation so an accepted request is not lost. Odoo records, Telegram copies, work records, financial documents and rolling backups follow their own operational, legal and expiry requirements.
These periods are configured implementation defaults under review, not a legal conclusion. Privacy, accounting and warranty requirements may require a different period before publication.
What you can ask for.
You can ask what we hold about you, ask for it to be corrected, or ask for it to be deleted where we are not required to keep it. Email us and say what you want — you do not need to use any particular form of words. Livanzh LLC will identify which website, Odoo, Telegram, file and backup copies can be corrected or deleted and which must expire or be retained for a stated reason.