This Privacy Policy explains how YUU BATES LLC, the company operated by developer YuuBates, collects, uses and protects information when you visit our site, write to us, or engage our design services. We keep the policy plain because we believe privacy rules should sound like a conversation, not like a maze.
YUU BATES LLC is located at 793 W 1000 N, Pleasant Grove - 84062-1653, United States (US). Last updated: January of 2026.
Contents
- Our Approach to Privacy
- Who This Policy Covers
- Information You Give Us Directly
- Information Collected Automatically
- Special Note on Email and Messages
- Why We Use the Information
- Legal Bases for Processing
- Cookies and Similar Marks
- Web Analytics and Metrics
- Sharing With Third Parties
- Service Providers Who Help Us Work
- How Long We Keep Information
- Security of the Data We Hold
- Data Rights You Hold
- Privacy for Children
- Cross Border Transfers
- Links to Other Sites
- Changes to This Policy
- How to Use Your Requests
1. Our Approach to Privacy
The field and flow model that guides our engineering guides our privacy too. We would rather gather a little and filter it correctly than hold a reservoir of data nobody ever looks at again. Our default is restraint: we collect only what a conversation or a project genuinely needs, we keep it only as long as that need lasts, and we protect it as carefully as we protect a production channel under load.
This policy applies to the website, to our intake email box, to the telephone line we answer, and to the files we handle during a consulting engagement. It does not apply to tools owned by other companies where those tools, rather than we, collect the data; when you use a third party platform we integrate, that platform operator policy also matters. When the two sets of rules work together we say so plainly below.
2. Who This Policy Covers
This policy covers several kinds of people. It covers a visitor who only reads our pages. It covers a person who sends an email, fills the contact form, or telephones the intake line. It covers a client who signs a project, and it covers that client staff and customers whose information appears in the records we touch during automation, integration, dashboards and support.
Different roles bring different expectations, and the rules below note where they differ. A casual reader generally shares little more than a broad location and a page view. A project client shares significantly more because a systems project would be impossible without access to the real working data inside the client systems. We treat that deeper trust with the strongest safeguards we can reasonably apply.
3. Information You Give Us Directly
When you fill the contact form we receive the name, the email address, the subject line and the message you type. When you call us we may receive your number from caller identification and, depending on the conversation, your name and the name of your organization. When you write to reply@yuubates.lat we receive whatever is in the message and its headers, including your sending address.
During a project the list can grow to include billing details, access to production records, account lists, configuration exports and sample data. We never ask you to send sensitive payment card numbers through ordinary email and we never store those numbers ourselves; payments we accept through our billing channels are handled by a payment provider under that provider separate terms.
4. Information Collected Automatically
Like most well run sites, our web server logs a small record when a page loads. That record can include the web browser type, the operating system, the referring page, the rough network location such as city or region, and the pages read. We use an analytics approach explained further in the analytics section, and we keep the detail at a level that lets us improve the layout without building a detailed portrait of any single visitor.
We do not use this automatic information to re-identify visitors, to target advertisements at you on other sites, or to sell a visitor list. Automatic logs exist to keep the site reliable and to answer the practical question of which content helps people and which needs reworking. When a log is no longer useful for that job we remove it.
5. Special Note on Email and Messages
Email is transmitted across networks we do not control, so we do not promise it is encrypted in transit everywhere outside our own mail handling. We encourage you to avoid putting deeply sensitive material into a first message and to wait until a project is open, when we can tell you the more secure routes for files like account exports or recovery material.
We read messages to answer them and to prepare proposals, and a small team within YUU BATES LLC may need to see an inquiry more than once to route it correctly. Messages we receive are not sold and are not shared with mailing lists. Our replies come from our own mail domain and we will never ask you for a password or a one time code by email, so treat any message that does as a phishing attempt.
6. Why We Use the Information
We use your details for clearly described purposes. We use them to answer your question, to prepare and send a proposal, to manage the contract and the invoice, to build and test the systems you ask for, to keep those systems safe, and to meet accounting, security and legal duties. When you accept a managed plan we may also use a contact address to send you account news and plan changes that you need to act on.
We do not build a personal profile to advertise to you, and we do not merge the site analytics with the contact details to guess anything about you as an individual. Where a purpose is not core to the work we will ask separately rather than presume; where we can meet a purpose with less detail we collect less detail. This restraint is not an accident but a decision about the kind of company we want to be.
7. Legal Bases for Processing
Different regions ask companies to name a lawful ground before holding personal data. Our main grounds are these: first, fulfilling a contract with you to provide the services; second, our legitimate interest in running a reliable business and keeping its systems secure; third, a duty required by law for records such as tax and accounting files; and fourth, where the law asks for consent, we rely on consent you give when you reach out and may rely on it for certain analytics.
Where we base processing on legitimate interest, we weigh that interest against your rights and do not use the data in a way that overrides them. Where you give consent you may withdraw it at any time through the contact route in the final section, and withdrawing consent does not affect work already lawfully done before the withdrawal. We will name the specific ground when you ask in a written request.
8. Cookies and Similar Marks
A cookie is a small text file a site stores in your browser to remember a preference. Because our site carries no login area and no shopping cart, we use very few cookies and none are used to follow you across unrelated sites for advertising. The main browser storage we may set is limited to a technical token that supports the hosting provider secure delivery.
You can manage or clear cookies in your browser settings at any time without losing the ability to read our pages or use the site. Blocking all cookies is fine with us; it does not remove your ability to contact us, because our forms work by opening your own email program rather than by relying on a server that needs a session cookie.
9. Web Analytics and Metrics
We gather coarse, aggregated numbers about how the site is read so we can keep the layout honest and the content helpful. Aggregates answer questions such as which service page earns attention and which section confuses readers. Those aggregates do not identify you personally, and we choose tools and settings that avoid building a longitudinal trail of your clicks.
Because some regions treat analytics identifiers as personal data even at city scale, we keep the retention short, we mask at the region level where possible, and we provide the contact route below if you want to ask about the specific tool. Where direct advertising would require broader data we simply do not run it; the absence of retargeting is a deliberate feature, not an oversight.
10. Sharing With Third Parties
We do not sell data and do not rent it. The short list of what we do share sticks closely to what the work itself needs. We may share a limited amount with an accountant or a payment provider to settle an invoice, with a hosting provider to run the site and mail, and with a software vendor when the very point of a project is to connect one of our tools to that vendor product and to keep that connection healthy.
Each time we share, we share only the narrow slice the other party needs, we ask them to use it only for that purpose, and we try to work with vendors that commit to reasonable protection. Where a court, regulator or law requires us to share records we share only the minimum the demand requires and, unless prohibited, we tell you before we hand over the files. Client production data is never used to enrich our own marketing system.
11. Service Providers Who Help Us Work
We run our site on infrastructure provided by a hosting company, we answer mail through a mail provider, we keep project working files in cloud storage, and we may use a paid communication tool for calls. Each of these providers has its own terms and its own handling rules, and none of them is allowed to resell the access they receive from us to build their own customer lists from you.
Where a provider sits outside the region you live in, data may be sent across borders as described in the transfer section. We choose providers whose contracts allow us to move data lawfully and whose security practices we review before we hand them a production file. If a provider changes its security posture in a way that matters to you, the change is part of the whole project risk conversation we already owe you as a client.
12. How Long We Keep Information
We keep contact notes only as long as they are useful. Visitor logs are kept briefly, typically weeks rather than years. Messages that lead nowhere are removed after we respond. Messages that lead to proposals stay with the proposal file for a reasonable period. Records tied to a delivered project stay for the periods our accounting, warranty and tax duties require, which is usually a few years rather than forever.
Client production data we receive is handled by rule and not by whimsy: once the purpose is done, we return or delete it on request as the project and the intellectual property terms provide, and we confirm the deletion in writing. We never hold a copy in a vault just because we once had access. Retention tables are reviewed at least yearly so that the policy keeps pace with actual practice.
13. Security of the Data We Hold
Security follows the same gate and gauge discipline as our engineering. Access to your files is limited to the team members who need it for the task, given through separate and individual accounts whenever the platform allows them, and reviewed when a person changes role. Passwords are stored in a proper manager rather than on sticky notes or in shared spreadsheets, and we enable extra login protection on every service that offers it.
No method is perfect, and we do not promise a guarantee against every attack, just a serious and current effort. If a breach affects your data in a way the law requires us to report, we will tell the people who need to know without undue delay, describe what we are doing, and help you reduce any risk the event created rather than waiting for your question to find us.
14. Data Rights You Hold
Depending on where you live, you may hold a set of rights over the personal data we process about you. Common rights include the right to request a copy, to ask that we correct a mistake, to ask that we delete data no longer needed, to limit or object to certain processing, and to ask for a machine readable copy to take to another provider. When a law grants a right, we honour it regardless of whether the first version of this policy lists it explicitly.
To use a right, reach us by the route in the final section and name your request plainly, for example by asking us for a copy or for deletion of a specific record. We will verify you are the right person before acting, respond within the deadline the law sets, and explain any reason we cannot fully grant a request. A refusal never means we ignored you; it means the law or a competing duty, such as keeping an invoice for tax, genuinely gets in the way.
15. Privacy for Children
The services are built for business use and are not aimed at children. We do not knowingly collect personal data from a child below the age where marketing rules begin to apply, and we do not run the kind of games, chat or profiles that would attract a child to the site in the first place. If a child account appears in the working data of a project, that account belongs to the client system and is governed by the client rather than by us.
If we learn we have received personal data directly from a child without a proper basis, we will delete it promptly and tell the responsible adult what happened. Parents and guardians who believe a child has sent something to us should write to the contact route and we will search and remove what we reasonably can, keeping only the record a legal duty forces us to keep.
16. Cross Border Transfers
YUU BATES LLC works from the United States, and the site, the mail and several project tools are hosted in the United States or in other regions where the platform we chose runs. If you live outside the United States, sending us a note or starting a project means your information travels into the United States and may be handled there or in the region of a relevant provider.
We do not move data just to move it; we keep and transfer it where it needs to go for the service to work, and we rely on lawful grounds such as contracts with appropriate clauses or the ground of performing the service you requested. The transfer section of your local law may give you a way to ask about safeguards, and we will describe our structure honestly rather than hide it behind a long wall of text.
17. Links to Other Sites
Our pages sometimes link to the vendor sites we use, to official guidance, or to the accounts we hold on public platforms. Once you leave our site, this Privacy Policy no longer applies, and the destination page sets its own terms and handles its own data in its own way.
We choose links because we believe they help you and we review them as best we reasonably can, but we do not control those pages and we accept no responsibility for their content or their cookie choices. If a link feels dated or goes somewhere unexpected, tell us and we will fix or remove it. The policy boundary I describe here is a real one, not a fine print escape, so it colours how we talk about outside tools.
18. Changes to This Policy
We update this Privacy Policy when the law, the tools we use, or the shape of our work changes. We post the new version on this page with a fresh date at the top, and for managed plan clients we give a short heads up through the contact email we hold when the change is the kind a client would want to know about rather than only the kind a reader would.
A materially new version does not silently reclassify data we already hold under an old promise. Where a change would use data in a new way, we go back to the ground the original collection relied on and, if that ground was consent, we ask again. Reading this page after an update tells you which version currently governs the site.
19. How to Use Your Requests
The fastest way to reach the right desk is the intake line. Write to YUU BATES LLC at reply@yuubates.lat for privacy questions and removal requests, or telephone +17793264149 for account or support questions. Post a formal request to YUU BATES LLC, 793 W 1000 N, Pleasant Grove - 84062-1653, United States (US) when you want a paper trail or when the request is large.
When you write, tell us who you are, what you want, and roughly what you contacted us about, so we can find the right record without asking you to repeat a story. We aim to answer a privacy request within one business day and to act on a clear request within the deadline your law sets. You also have the right to complain to a supervisory authority in the region where you live if you believe we have not treated your data fairly, and we will not hold that against you.
This Privacy Policy reflects how YUU BATES LLC, run by developer YuuBates, actually works day to day: collect little, keep it safe, and hand it back when the season is over. Contact details and the full address appear above and on the Contact page.