Privacy — dayvu

Who we are

Dayvu, Minnesota, and this page covers the whole service.

Dayvu is a company in Minnesota, in the United States. This page covers the website at dayvu.us, the enquiry you send us, and the office service we run for a client business. Where the person reading this is a customer of one of our client businesses, your information reached us inside that business's own paperwork, and the business you deal with is the one to talk to first.

Anything on this page can be asked about directly, and the answer will come from one of the two people who run the office. The address is at the bottom.

What we collect

Three groups, and none of them is a surprise.

If you write to us

Your enquiry.

The business name, your name, your email, a phone number if you choose to give one, the one job that piles up fastest for you, and whatever you type in the box about the chores eating your time. That is the whole of it, and the form asks for nothing else.

If you become a client

The work itself.

The documents, spreadsheets, exports and messages you send us, the logins or keys needed to pull them, the register we keep about how your business runs, and the messages you and your staff send your agent in the portal.

As any visitor

Technical records.

Our host keeps standard server logs: the address your request came from, your browser and device type, the page you asked for, and the time. Our host also runs cookieless page analytics, which counts visits without identifying anybody.

We do not buy lists, and we do not run advertising or tracking pixels on this site.

Why we hold it

One reason per thing, and no side uses.

To answer you. Your enquiry is read by us and used to write your one-page summary and to reply. The support address is answered around the clock, and the desk keeps the thread so the same question is not asked twice.
To run the office. Your documents and exports are what the agent works from, and your register is how it learns your business well enough to be trusted with the repeat work.
To report back. The weekly report and the monthly pack are built from your data and sent to you.
To keep the relationship working. Billing, records we must keep by law, and keeping the service secure.
To improve the office. We look at how our own jobs run so the next one is better. Where an example from a client's work is useful, it is stripped of anything that identifies the business or its customers before it is used internally, and nothing about your business goes on this site or into any proposal without your written permission.

What we never do

The four things that are off the table.

We do not sell or rent it. Your information does not go to data brokers, list sellers or advertisers, and there is nothing here to opt out of, because it does not happen.

We do not train models on it. Nothing you send us is used to train an AI model by us, and we do not hand it to anyone for their own product development.

We do not contact your customers. The office writes in your name where you have asked it to, and never treats your customer list as a marketing list of ours.

We do not name you without permission. A case study, a logo or a public reference happens only with your written say-so.

Who else touches it

The providers that carry the work.

A service like this runs on other people's infrastructure. These are the ones that see your data, named so you do not have to guess, and each of them is bound to use it only to provide that piece of the service.

Cloudflare serves this website and its DNS, and provides the cookieless analytics. It sees the technical records described above.
AgentMail and Google carry our email: the inbox the enquiry form sends to, and the inbox we read and answer from.
Our own servers run the office. Your agent, your register and your files live in a space of their own, on infrastructure we control, with nothing of yours sitting beside another business's work.
Language model providers process the content an agent works on in order to produce the output you asked for. We choose those providers on cost, capability and their data-handling terms, and we will tell you which ones carry your work if you ask.

Beyond that list, we share your information only when the law genuinely requires it, and we tell you when that happens unless we are legally barred from telling you.

Credentials

We ask for the least access the job needs.

Where an export or a read-only login will do the work, that is what we use. Where the work genuinely needs a password, it is stored in our own systems, kept out of the client-facing page, and used only by the job that needs it. We never hold a card or bank credential, because the office never moves money.

You can revoke any access you have given us at any time by changing the password or the permission on your side, and we will tell you if a job stops working because of it.

How long we keep it

Long enough to do the job, then gone.

An enquiry that does not become a client: Up to 24 months, then deleted
A client's working data: Kept while the office runs for you
After you cancel: Your files and register sent to you, then deleted within 30 days
Routine backups: Overwritten on their own cycle, within 30 days
Billing and tax records: Kept as long as the law requires, and nothing else in them
Anytime you ask: Deleted within 30 days, subject to the billing records above

Your choices

Four things you can ask for, and how.

Email us and ask. There is no form, no fee, and no hoops: dayvusupport at gmail dot com.

See it. Ask what we hold about your business and we will tell you, and show you where it sits.
Copy it. Ask for a copy of your files and your register and we will send them to you in the format you can open.
Correct it. If something we hold is wrong, tell us and we will fix it, including in the register the agent works from.
Delete it. Ask and we will delete what we hold within 30 days, apart from the billing records we are required to keep.

We answer these within 30 days, and usually the same week.

Cookies and analytics

One cookie, and it is the one that keeps you signed in.

The marketing pages on dayvu.us set no cookies, run no advertising scripts and carry no tracking pixels. The analytics our host adds are cookieless: they count visits and pages without identifying the person who made them.

The client portal sets one strictly necessary cookie, which is the signed session that keeps you logged in. It carries no advertising purpose, and deleting it signs you out.

Security

What we do, and what we will tell you.

Data moves over encrypted connections, each client's work sits in its own space, and access to it is limited to the two people who run Dayvu. Routine jobs run in the client's own space with the rules that client set.

No system is perfect, and we will not pretend otherwise. If something happens that puts your information at risk, we tell you in writing: what happened, what it touched, what we have already done about it, and what we would do differently. We would rather you heard it from us on the day than worked it out in month four.

Scope of this page

A business service, and changes to this policy.

Dayvu is sold to businesses, and this site is not aimed at consumers or at anyone under 18. We do not knowingly collect information from children.

If we change this page, we will say so here and change the effective date at the top. Where a change is material for a client, it goes out by email at least 30 days before it takes effect, alongside the notice promised in the terms of service.

Dayvu, Minnesota, USA. This policy is effective from 16 September 2026. Questions about it go to dayvusupport at gmail dot com, or through the contact page.

What we hold, and what we do with it.