What I do with your information

Who I am

Doxasi Studio is a one-person studio based in Brisbane, Australia, doing music production, video post-production, and AI agent development for small businesses. Everything below is done by me, and questions come to me directly through the contact page.

Visiting this website

This site is a set of plain pages. There is no analytics, no tracking pixel, no advertising network, and no cookie set by me. I do not know who you are or that you were here.

Two things do reach someone else when a page loads:

• Fonts come from Google. Loading them tells Google your IP address and roughly what browser you are using, the same as visiting most sites on the web.
• Cloudflare serves the site, and keeps short-lived technical records of requests so it stays up and is not attacked. It may set a cookie of its own to tell real visitors from automated traffic.

Sending me a message

If you fill in a form here, it goes through a service called Web3Forms and arrives as an email in my inbox. That means I receive what you typed: usually your name, your email address, and what you are asking about. I keep it while we are still talking and delete it once we are not. It is never sold, never shared, and never added to a mailing list.

If I build you an AI agent

This is the part that matters, because it means connecting something of yours. The example throughout is the morning brief, which reads a business owner's email overnight and sends one message about what needs them today. The same principles apply to anything else I build you.

What it can and cannot do

• Read only. The access you grant cannot send, reply, delete, label, or change anything at all. If everything went wrong at once, the worst outcome is that something was read.
• It never contacts your customers. It only ever talks to you. Nothing goes out to anyone else, ever, without you sending it yourself.
• You can switch it off without asking me. The access lives in your own Google account and you can revoke it there at any time, and it stops that moment.

What is read, and what is actually kept

Those are different things, and the difference is the whole design. Messages are read to work out what matters. What gets written down is much less.

• The contents of your messages are never written down.They are fetched, held in memory for the seconds it takes to sort them, and dropped.
• What is stored is a short record: the subject line, who the message was from, when it arrived, and the note it writes for itself about what the message seems to need from you.
• That record is deleted after fourteen days. The subject line goes, the sender's name goes, their address goes, and so does that note. What remains is a line saying something was dealt with and when, which is what lets it tell you how long something has been waiting.
• The deletion is part of the ordinary daily run, not a separate job that could quietly stop, and it covers the working records and the backups on the same clock.

Two things fourteen days does not cover

Said plainly, because a policy that claims a clean sweep and is wrong is worse than one that names its edges.

• Your brief stays in your own Slack. It is delivered to a private channel in your workspace and sits in your history like any other message, for as long as your Slack settings keep it. That is yours to control, and I will help you set it if you want it shorter.
• A rule you teach it keeps its example. If you say "stop showing me these", it has to remember which message you meant, so that one subject line is kept for as long as the rule lives. You can delete the rule, and the example goes with it.

Who else is involved

I do not do this alone, and you should know exactly who touches what. Some of these are overseas, which I would rather state than bury.

The system that reads your mailbox runs on a machine in Australia. Your mailbox stays where it is, in your own Google account, and no copy of it is made anywhere.

To be precise about the one thing that is easy to word misleadingly: working out what a message needs means the message has to be read, and part of that reading is done by the AI provider named above. It is sent for that purpose, used to answer that one question, and not kept. That is why the provider is listed here rather than left out.

When something breaks

If the system gets something wrong or stops working, it reports itself to me automatically. Those reports carry settings, timings and an internal reference number. They never carry your subject lines, never who wrote to you, and never anything anyone said.

Training

I do not use your information to train anything, and I never will. The AI provider is used on commercial terms under which what is sent is not used to train their models either. It exists to produce your brief and nothing else.

If you are a health service

Health information carries obligations beyond ordinary business records, and I treat that as part of the work rather than as paperwork. Before starting with a health client I put the arrangement in writing: which mailbox is connected and which is not, how long anything is kept, who else is involved, and what happens if something goes wrong. If you are a clinic considering this, ask for that document early. I would rather have the conversation before we start than after.

Your choices

• Ask me what I hold about you, and I will tell you.
• Ask me to delete it, and I will, unless the law says otherwise.
• Revoke a connected account yourself, from your own Google or Slack settings, without going through me.
• Complain. Come to me first and I will try to put it right. If I cannot, you can take it to the Office of the Australian Information Commissioner.

Changes

If this page changes in a way that affects a client, I will tell that client directly rather than quietly updating the date at the top.

Questions about any of this go through the contact page. They reach me, not a support queue, and I answer them myself.