Privacy Policy for the Discovery Platforms

1. Nature of our services

AshFindsFirst LLC provides computer systems design work and related professional, scientific and technical services. Our shop concentrates on discovery, matching, review, mapping, booking and merchant profiling tools that help one household or one business find a local provider whose skills match a stated need. These tools are offered through the Allife Health web properties and related partner pages.

Because our purpose is to connect a looking person with a willing provider, the data we handle has to be enough to make that connection work while staying far smaller than a general purpose social network. We therefore design every screen to ask only for the details a healthy local match requires, and we refuse to collect curiosities that have no use in the field.

2. Words we use

In this policy the expression a looker means any person who visits a platform to search, browse, review, match or book. The expression a merchant means any business, independent professional or service provider that keeps a profile on a platform. Personal data means any information relating to an identified or reasonably identifiable living person. A platform means one of the discovery systems we operate, taken together with its companion pages.

The expression we, our and us always refers to AshFindsFirst LLC, a limited liability company registered in the State of Utah, United States, whose street address is written at the head of this document. When we say the workshop we mean the same company acting from its Herriman rooms at the Sawa Court address.

3. Data the service gathers

We gather several loose families of data, and we record each family in its own drawer so the boundaries stay clear. The first drawer holds the identifiers you offer, such as your name, an email address and, at times, a phone number. The second drawer holds the working records of a request, including the kind of service you asked about and the area you named. The third drawer holds technical traces produced by your device while you use the site. The final drawer holds the notes merchants give us so their profiles read live and honest.

4. Personal identifiers

You are not required to create an account to read our public field guides or to inspect a merchant profile. When you choose to send a booking request, to write a review, or to ask a question through a contact form, we collect the identifiers that make the message usable: your full name, your email address and, when you volunteer it, your phone number or the address of the property involved in the job.

We use those identifiers only for the purpose that brought them to us. A booking request travels to the chosen merchant; a review travels to the review page under the name you gave; a contact enquiry arrives at our own response address. We do not sell these identifiers to any data broker, and we do not let a merchant export your address book or your booking history beyond the work you asked them to do.

5. Search and browsing information

When you run a local search, our engine records the terms you type, the filters you set, the results you open and the order in which you act. This trail helps us measure which discovery system answers well and which parts of the index feel thin. We treat that trail as behaviour on a field survey, not as a permanent personal diary.

We may combine search trails across many visitors to publish aggregate notes such as most requested service in Herriman or average weekend demand for plumbers. Aggregates never single out one person, and the underlying trail is pruned on the schedule described in the retention section below.

6. Location and use of place data

Some of our tools rely on a location: a place name, a postal code, a neighbourhood, or the coarse position your browser reports when you ask for results near you. We use that location to rank providers sensibly and to draw the map based browsing tools, and we store the place only as long as the tool needs to answer your current walk.

You always decide how exact your location will be. Choosing a postal code instead of precise coordinates still lets every discovery system work, and you may clear a saved place in the settings of a platform whenever you like without harming the usefulness of the remaining tools.

7. Device and technical data

Like nearly every web service, our servers register standard technical details to deliver pages reliably: the internet protocol address of your connection, the type and version of your browser, your operating system, your screen size, the referring page that brought you here, and the moment of each request. An internet protocol address is personal data in most legal views, so we treat it with the same care as a name.

We hold this technical trace to keep the field guides loading fast, to detect misuse such as automated review floods, and to protect the workshop from intrusion. Technical traces are rotated away after a short window unless a security investigation or a lawful request keeps a narrower copy alive for that purpose.

8. Purposes for which we use information

Legal requirements ask us to say plainly what we do with personal data. We use identifiers and enquiry contents to answer requests, to match a looker with the correct merchant, and to keep the booked calendar honest. We use search behaviour to improve ranking quality and to shape the service dashboard for merchants. We use device data to protect the systems and to measure audience size without exposing individual wanderers.

We also use limited data to send operational notes: to confirm a booking, to remind a looker of an appointment, to tell a merchant about a new review, or to answer a question a merchant asked about dashboard use. We send marketing only when a person ticks the box that asks for it, and every such note carries an easy way to stop future notes.

9. Legal basis for handling data

When a law requires us to name a legal basis, we rely on several. Contract covers the data needed to deliver a booking or an enquiry you asked us to arrange. Legitimate interest covers the honest improvement of our search, the safety of the platform and the answering of routine technical questions. Consent covers optional extras such as newsletter notes and advanced cross device personalisation, which you may withdraw at any time.

Where a regional rule (for example a European data protection act or the Utah consumer privacy act) sets a higher floor, we follow that higher rule for the people it protects even when another rule inside the United States would ask for less. We would rather overprotect a visitor than under-protect a resident of any country.

10. Sharing with third parties

We do not sell personal data. We share a narrow record with three kinds of helpers: hosting and security firms that run the servers where the field guides live, payment processors that carry a booking deposit when one is required, and the merchant whom you have chosen and to whom your request must travel to be useful.

Each helper receives only the slice of data the helper needs, under a written agreement that forbids the helper from selling the data or using it for an unrelated purpose. When a merchant is yourself, the disclosure is simply the delivery of the service you asked for. We keep a short register that records which helper saw which slice and on what date, and we can show that register on request.

11. What a merchant can see

A merchant dashboard does not open the whole field about every looker. A merchant can see the name, email and chosen location of a person who actually sends a booking request, because the request cannot be fulfilled without that address. A merchant never sees the search history of visitors who merely looked, and a merchant never sees the reviews that other merchants received.

If you write a review, the merchant of the reviewed business sees your public display name and your commentary, just as any reader does. If you would like your display name to hide your full identity from vendors, keep the display name free of a surname and do not type your email into the commentary box, because reviewers control the content they place on the page.

12. Reviews and public correspondence

Reviews are the honest glue of local discovery, so we publish them widely and protect them from silent erasure. When you post a review the platform records your display name, your rating, your written commentary, the date, and a marker that says whether you verified the purchase with the merchant. That public card is shown to every visitor and to the merchant, and it remains visible until you remove it through the same account that wrote it.

We reserve a narrow power to hide a review only for reasons such as spam, disclosed advertising, identifiable private health facts about an unconsenting person, or a court order. A hidden review is never falsely rewritten, and the author is told the reason in plain speech. Reviews are our public record of trust, so we keep them even when the underlying account becomes dormant, because removing an old and true review would mislead the next looker.

13. Cookies and similar markers

We set small text markers called cookies so the platforms remember light choices: that you kept a certain map zoom, that you closed a notice, or that you asked to stay signed into a merchant dashboard. Strictly necessary markers keep a form from losing your half written note and keep the login honest.

Analysis markers, when used, are limited and brief, and they never pass your personal data to a broker. You may reject non essential markers through your browser or through a consent banner where one appears, and choosing to reject them does not close the trail; the field guides remain fully readable with the strictly necessary markers alone.

14. How long we keep data

We prune the drawers on honest schedules that match each purpose. A bookkeeping of a booking is kept for the period required by tax and record rules and no longer. Enquiry note history is kept for a term of no more than thirty six months after the last message. Search trails used for tuning are aggregated or erased within twenty four months. Technical request logs are rotated every one to six months.

A review you wrote stays because it is public record, but identity markers that connect the review to your dormant login are dissolved after a long inactivity so the card loses its address to reach you. When a purpose ends, the associated personal data is deleted or anonymised, and we never keep data merely because we might want it later.

15. Security measures in the workshop

We protect personal data with measures chosen for the computer systems design trade in which we work. Traffic to the platforms travels over encrypted connections. Passwords are stored only as strong hashes, never as readable text. Access to the databases is limited to named staff of AshFindsFirst LLC who need it, and each access is recorded in a log the same way a visitor is recorded at the trailhead.

We run regular updates against known weaknesses, test our public forms for the common injection and script attacks, and rotate credentials on a timetable. Should a breach touch personal data, we assess what was exposed, notify the people affected within the legally allowed window when we can identify them, and describe the fix at this page rather than hiding behind a blanket promise.

16. Privacy for children

Our discovery and search platforms are built for adults who make service decisions for a home or a business. We do not knowingly collect personal data from children, and a platform profile, booking identity or merchant account is never transferred to anyone known to be under the age of eighteen without the very limited exceptions a legal guardian or a law permits.

If you believe a child has given us personal data without a guardian agreeing, tell the workshop at the address at the end of this policy and we will delete that data from the drawers as quickly as a scheduled purge can reach it. We also design our content so nothing on a field guide page tries to speak directly to a child or to gather a child attention for a service sale.

17. Your data rights

Depending on the law of your home, you hold a family of rights over the personal data we hold. You may ask to see a readable copy of the data about you. You may ask us to correct an error in a name, an address or an email. You may ask us to erase data whose purpose has ended, and you may ask us to restrict or to stop the processing that does not depend on a contract gap.

You may also take away a consent you once gave and ask to receive the data you typed to us in a portable file. We answer such requests within the time the law allows, and we do not charge a fee for a simple first copy. To begin any of these walks, write to respond@allifehealth.buzz and we will confirm your identity before we open the relevant drawer.

18. State notices and California rights

Residents of California and of Utah benefit from additional notices under their state privacy laws. Under those rules a resident may ask what categories of personal data we collected in the last twelve months, the sources of that data, the business purpose of each collection, and the categories of third parties, if any, who received the data. Our answer for the trailing year is the personal identifiers, search behaviour, location and device data described in this policy, collected from the visitor directly and from website request traces.

Neither the California nor the Utah rule sees us engaging in the sale or the sharing of personal data in the ordinary sense, so neither state sets up a need for a do not sell control at present. A resident may still request deletion, correction and a copy under the exact terms of the state act, and may not be penalised for refusing to allow marketing boxes. We honour a request made for one household member as if it were the authorised request of that member when the requester proves identity.

19. Links to outside sites

Merchant profiles and certain notices may link to the public site of a provider, to a review publication no longer aggregated, or to a tool such as a payment gateway. Once you leave a platform you travel under the privacy rules of the destination, which may differ from ours. We only place links we believe are useful, but we cannot govern the drawers of a site we do not run.

We encourage you to read the notice of the outside site before you give it a sensitive detail such as a payment card or a health form. When a destination asks for what looks like data we already hold, prefer to return to the platform and send it there rather than retyping it on a stranger page.

20. Changes to this policy

The workshops of AshFindsFirst LLC will occasionally sharpen this field document as the discovery systems grow. We post every newer edition at this same address with a fresh date written at the top, and for a change that grows beyond the ordinary we email the people whom we can still reach and who gave us a working address.

Each edition lists the day it became live, so a reader knows which text applies to a past visit. Continuing to use a platform after a new edition appears means you have read the newer notice, while any new data you send after that date is handled under the newer rule. We never take an old edition down without routing a reader forward to the current one, so the trail of our promises stays open.

21. Contacting the workshop

Questions, corrections, deletion requests and complaints about privacy all land in the same basket at the Sawa Court rooms. Reach the data caregiver of AshFindsFirst LLC by email at respond@allifehealth.buzz, by phone at +14353094670, or by post to 3446 W Sawa Ct, Herriman - 84096-2083, United States (US).

We read every privacy note personally and answer the walk you started. If you feel we answered poorly, you may also speak to the privacy or data protection authority of your own country or state, and we will cooperate fully with that authority so the matter closes with an honest signature on the log.