Privacy Policy

1. The kind of house behind the sign

The pages under the hailida.autos address belong to the software house that signs its mail as HighDesertGreen LLC. That house sits at 15247 S Old Port Way, Bluffdale - 84065-2516, United States (US). For the purpose of this policy the HAILIDA site and the house behind it are one and the same record keeper. HAILIDA is the public ridge of the house, the fire tower from which the house presents its systems practice, and it is watched by the same crew that undertakes the services you may read about further along.

Nothing on this site asks you to surrender more personal material than a neighbour would hand over in the shade of a porch. The spirit of the whole mesa runs to least collection, plain language and a box you may close at any time. Every phrase below should be read in that temper.

2. The narrow ground this policy covers

This privacy notice is intended for the mail sent to the public pages of the site, the forms that sit on those pages, and the ordinary traffic that any web host records. It does not reach beyond those rails. If we later work with you under a wider contract, the agreement for that work carries its own fuller treatment of personal data, and where the terms disagree, the tighter, more protective one prevails in respect of personal material.

This policy does not govern the behaviour of a third party whose own site you land on from a link we offer. Every external destination keeps its own ledger, and you should ask that ledger keeper the same plain questions this notice answers for our own hold.

3. The rule of least collection

The strongest single habit of this record room is the rule of least collection. We try not to ask for a single fact we do not have a reason to hold. A visitor who only reads the tower, scrolls the shutters and leaves without a word should reasonably expect that almost no personal trace remains of the passage beyond the ordinary server figure that any machine must keep.

Least collection spares you the burden of policing a dark file and spares the house the risk of guarding a barn full of hay nobody ever asked to grow. Wherever a field can be optional, it stays optional. Wherever a log line can drop a character, it drops. This is not a small favour; it is the load-bearing wall of the whole privacy posture.

4. The data that crosses the threshold

When you visit the site, the equipment that carries your request sees the ordinary facts any web handshake learns: the network address of the machine at your end, the kind of browser you ride, the hour of the request, the pages your reading took in, and the site you arrived from, if your browser chooses to say so. Most web servers pass through exactly these details before any human looks at them.

When you fill the logbook form, the fields you choose to type join the record: a name, an address for a reply, a subject and the text of your message. We will treat the text of a message as sensitive to the sender, even when it carries no obviously personal mark, because a message written to the house is a confidence offered, not a coin laid on a counter.

Should you write to the desk by electronic mail instead, the email itself becomes the record, with the customary lines at its head. We keep such mail no longer than the reason for holding it lasts, and we never pull names from a message to build a side list for some other purpose.

5. Server logs and the visitor ledger

Like almost every site on the open ground, this one leans on a hosting ledger that records requests as they arrive. The purpose of that ledger is not to spy on any one reader but to keep the tower upright: to see when a page is slow, when a bot hammers a doorway, when a file is asked for that no longer stands, and when a surge of interest tells the crew to widen a stair.

The entries in that ledger are held for a bounded window, commonly measured in days or a modest run of weeks, then rolled off the tail. We do not merge the ledger promptly with any mailing list, and no one rises through those lines to greet a named visitor unless the visitor himself or herself first raised a hand.

When a request shows the smell of abuse, a flood of traffic from a bare handful of machines or a scanner feeling every door, the house may hold the offending lines longer to keep the fence intact. That longer hold is aimed at the machine, not at the human behind it.

6. Cookies and quiet machinery

The word cookie, in the browser sense, describes a small tag your machine agrees to keep at the request of a site, so the next visit can be greeted with memory. This site tries to manage with very few of those tags. We do not set a cookie purely for the sake of setting one, and we do not stretch the public welcome mat across a network of unseen our advertising partners.

Where a cookie helps a real job, such as remembering the reply address you typed so you are not forced to retype it, we keep that job small, scoped to the site and short lived. You may at any time clear the storehouse that holds such tags through the settings of your own browser, and the tower stands fine without them; a couple of conveniences may simply forget you between visits.

7. The logbook and the mail route

The logbook form on the contact page is routed through your own mail client as a fallback, so the message you compose never has to wait inside an unseen web hopper if the direct route is closed. When you press the send latch, the site gathers the fields exactly as you wrote them and hands them to the mail habit of your machine under the clear address contact@hailida.autos.

What arrives at that box stays in the box of the duty desk. It is read by the people who run the services, answered from the same address, and kept only while the thread of the conversation is warm. If a first contact grows into a piece of real work, the message may pass into the normal working file for that engagement, where the fuller terms of that agreement then govern it.

8. Data you give us about other people

The form is built for your own mail; it is not a machine for gathering a crowd. Yet a message occasionally carries the name of a colleague, a customer or a partner inside its prose, because that is how work is politely described. If you write such a name into a message, you are adding that person to the same narrow record as your own words, and you should have a genuine basis for doing so, typically a shared working purpose that the person would expect.

Where we can, we use the name only to understand the story you are telling and do not lift it into any wider file. If a message turns out to belong to someone else clear record, for example a customer who mistook the address, we hold it only long enough to point that customer toward the right door and then drop it.

9. The lawful reasons for holding data

Privacy law, and not least the Colorado and United States rules that touch a house like this, expects every keeper of personal material to name the lawful footing under which it holds that material. For this site the footing is ordinary and hard to overstate. First, some holding is necessary for the working of the site itself: without reading a network address no request can be returned, so the machine basis for holding that scrap is satisfaction of the very request you made.

Second, where you write to the desk or fill the logbook, the holding rests on your clear request that the house respond. A message to the box is a request for the reply to that message, and the record of it is needed to give the reply. Third, the house holds a modest, honest run of security logs on the footing of its own legitimate interest in keeping the tower upright and its visitors unharmed. Those three pillars carry nearly the whole weight of this site; there is no grander commercial engine hiding in the cellar.

10. The uses we keep data for

Personal material that crosses the gate is kept for a short, named list of purposes. The first is to answer the mail you send and to run a conversation about the work a visitor or prospective operator has asked about. The second is to keep the site whole and fast enough for everyone, by reading the traffic figures rather than the faces behind them. The third is to mind the fence against attacks and abuse, so a flood does not knock the light out for a quiet reader who never asked for trouble.

The house does not sell your personal material. The house does not rent it, trade it, or barter it for shelf space. If a business purpose arrives, years from now, that could tempt a different course, the house would not travel that road on the back of material already gathered under this notice; it would come back and ask openly.

11. When we pass data to a helper

A modern site breathes a little help, and that help sometimes carries a corner of the record. The hosting machines that hold the server ledger receive the visitor figures those machines must see. The desk that answers mail may use a mail service that reads the message to carry it across the wire, much as the postal wagon must read the label to know the road. Such helpers act under our instruction, keep the material only as long as the job needs, and may not wander off with it for their own schemes.

We choose helpers the way a cautious tower chooses a crew. The contract with each helper carries the same plain guardrails this notice promises you. Where a helper fails the standard, the house parts company with that helper rather than winking at the fault.

12. Analytics and measured visits

At the time this notice is drawn, the site keeps its own measuring to the server ledger described above, and prefers not to lean on a heavy third party cookie the moment anyone steps onto the mesa. Should the house later choose a counting service, it will pick one that aggregates rather than peeks, that can run with your consent instead of against it, and that lets a visitor bow out without a fight.

Any future counting would gather the same quiet traffic facts, never the field of a message. The whole point of a headcount is a headcount; the instant it becomes a name count, it changes its nature and its footing, and that is a change the house would not slip past you inside an update to a footnote.

13. How long the ledger keeps the lines

Sleeping records are a danger to the keeper and a bore to the kept. The house therefore sets its retention as short as the honest work allows. Traffic logs roll off after the modest window named in the ledger section. Mail threads are trimmed when the conversation goes cold, taken down once the reply is given and no loose rope remains, unless a real engagement turns the thread into working papers, where the fuller terms of that work then set the keep.

Where a legal duty holds a record longer, for example where tax or compliance rules demand a file that happens to carry a name, the house obeys the longer duty and says so plainly rather than quietly stretching every other shelf to match.

14. The locks around the record room

Almost no record worth guarding comes here to rest, and the room, being small, can be guarded well. The holding machines are chosen with current patch habits, the doors to the working files are held behind real authentication, and the few hands that may touch a customer message are the same hands that carry the work forward. Passwords are strong, recovery is disciplined, and access is denied by default until a need arrives to open a lane.

Encryption rides the wire between your machine and the site, so a message does not wander the road in plain white for a bystander to read. There is no perfect fence, and this house does not claim one, but it keeps the field lights on, watches the fence line, and treats a reported hole as a summons rather than a suggestion.

15. Privacy for children

This site describes a business of software systems for grown operators; it is not built to court the young. The house does not knowingly gather personal material from children under thirteen, the age the United States child privacy law sets as its marker. If a child should wander up the tower and leave a line in the logbook, the record holds no more than a curious child might type, and the desk will answer once, gently, and then let the matter rest rather than build any file around a minor.

The careful parent or guardian who believes a child has left material with the house should raise the matter at the address below, and the house will look at once, drop what does not need to stay, and set the child wholly out of the record. No juvenile material is woven into any marketing or mailing corner of the site.

16. Your rights over your own record

The reader of this notice carries a set of rights over any personal material the house may hold about that reader. You may ask what the house keeps, in a plain and useful shape. You may ask for a copy of it. You may ask for a correction where a line has gone crooked, and where the law allows, you may ask that material be dropped or that its use be reined in. Where holding rests on consent rather than on a contract or a duty, you may pull the consent back at any hour, and the house will stop the related holding.

None of those requests carries a toll at the pass. Should a request arrive, the desk will answer within the window the law sets, count it from the day the request lands, and ask for confirmation only where the matter is genuinely cloudy about whose record sits in the file. A refusal, if one ever happens under a clear duty, will come with the reason nailed beside it.

17. The cookie choices in short reach

Because this site keeps to a few small cookies at most, the reader holds the whole steering wheel from the browser. Every current browser carries a corner where stored tags can be seen, cleared and screened. Should the site ever grow into the heavy cookie country described in the analytics section, the house would fit a plain consent latch on the door before the machinery ran, not present the visitor with a wall of legal afterthought once the shelves were already stocked.

For now, the honest advice is short: read with the browser cookie habits you already like. A cleared little tag may cost you a remembered message draft, and no more. The tower does not sulk when its cupboard is empty.

18. Links that lead away from the mesa

The HAILIDA prose will, from time to time, hand you a path to another ridge, be it a standard, a trade body, a colleague house or a public document. Once your feet leave our own mesa, this notice no longer walks beside you. The external keeper sets the rules of its own ledger, and the careful reader should spend as much care there as here before handing over anything personal.

The house does not quietly treat an outgoing link as a license to trade your traffic reading with the far ridge. A link is a border crossing for you alone; your ledger stays on our side of the wire unless you choose to carry yourself across it.

19. Transfers across the border

The house is a United States house with its watch above the Bluffdale mesa, and the reader should know that small traffic records and any mail the desk answers live on machines in the United States. If the reader sits beyond that border, the material rests in the care of a keeper governed by United States law rather than under the rule of the reader home jurisdiction, and the transfer is made only to carry out the request or the mail the reader sent with open eyes.

Because the holding here is so small and so plainly tied to the request of the moment, the risk carried across that border is slight. Should a heavier international flow ever appear, the house would stop and draw the alignment with the rules that guard it rather than wave the traffic through on a shrug.

20. Breach signals and the watch protocol

No fence is immortal, and the honest keeper keeps a lamp against the dark rather than a boast. If an intrusion ever reached material the house holds about you, the protocol is to act to stop the bleed, to look at what was seen, and where the law or plain decency requires, to tell you plainly and without delay what happened, what it touched, and what the house is doing about it.

The house keeps that watch current, rehearses a recovery habit so the light can be relit from a clean copy, and treats a quiet rumour of weakness as a summons to the fence line. Quiet diligence on quiet days is the whole craft of nights that never ring.

21. Asking a question of the privacy desk

Any question about this notice, any request named in the rights section and any report of a concern should be handed to the privacy desk. The desk sits at the postal and mail counters of the house: you may write to the desk at 15247 S Old Port Way, Bluffdale - 84065-2516, United States (US), or send mail to contact@hailida.autos, or hail +17756595475. Say that the matter concerns the HAILIDA privacy notice, so it is set on the right rail at once.

The desk will confirm within one working day that your message has been seen and will set to the matter without ceremony. There is no charge for a question, no patience worn thin by a repeated ask, and no corner of this notice too small to reopen. This policy may be updated as the site or the law changes; the current version always lives in this same single column, and the date of the newest revision stands at the foot of the page.