The agency made of AI Open the studio

How we treat you and your work

Last updated: 2026-10-30

You're about to try something you've never used, and to hand over your card to do it. That's a fair moment to want the plain truth first.

So here it is, gathered in one place: how the studio treats you, and how it treats your work. Every line below is a promise the studio already keeps, written out in full somewhere else. This page just brings them together, and each one links to the exact terms behind it, if you want to check.

Your work is yours

What you make in Kaldune belongs to you. You can download any file the moment it exists, including work from a brief you never finished. Owning and downloading your work is never held back over money. It's yours outright.

See the Terms for exactly how ownership works.

The studio never sees your card

When you add funds, your card goes straight to our payment processor, which handles the money. The studio never sees or stores your full card number. The payment processor holds it, and it is bound to use it only to process your payment.

See the Privacy Policy for what we hold, and what our payment processor holds instead of us.

Here is everything we know about you, and you can read all of it

Your name, because you're signed in with it. Your email, so you can sign in and we can send the messages your account depends on. Your time zone, so the studio knows your local time. Your language, so the studio speaks it. The record of your credits and what you spent them on. And, to stop a second welcome credit going to the same person or company, keyed hashes of the email address, card, phone and device that received it, plus the email address's domain, which we keep until 3 years after your account is deleted and use for nothing else: the device check runs a script from a device-recognition service, which sees your browser's device signals and your IP address and uses them for nothing else. That's the whole of it. The studio keeps no memory notes about you today; if it ever keeps a small client file the way an account team would, it will be plain facts you've stated, announced whenever a note is made, yours to read, edit, delete, or switch off entirely in Settings, and this page will say so first. No behavioral profile. No record of your habits. Nothing about you sold or shared.

See the Privacy Policy for the full account of what we collect and why.

We don't read your work

In the normal course, no one at the studio reads your briefs or the work in your room. There are three narrow exceptions.

Support, when you ask. If you ask us for help with something in your work, a support specialist can open the exact item you've pointed us to, for the exact purpose you asked about, and nothing more. Administrative access, and any change made to your stored work outside the studio itself, is logged.

Feedback you send on a reply. When you send feedback on one of the studio's replies, such as a thumbs down with your reason, the studio reads that reply and your reason to improve the studio, and nothing more. What you send as feedback is never used to train any AI model.

A valid legal demand. The third exception has its own section, just below.

The full, plain reconciliation is in Trust & safety, and the binding version is Privacy Policy §6.

The only other time we'd hand something over: a court order

The law can compel us to disclose your data: a valid court order, subpoena, or warrant, or a genuine emergency where someone's at risk of serious harm. It's the third of the three exceptions, and we treat it as narrowly as it deserves. We check the request is valid, we push back on anything overbroad, and we hand over only what the law actually compels. Wherever we're allowed to, we tell you first. We never volunteer your work to anyone.

See the Privacy Policy for the exact terms.

We never train on your work

We don't use your work, your briefs, or your information to train or improve any AI model, ours or anyone else's. The language models the studio calls on and our cloud infrastructure are contractually barred from training on your work. For specialist tools, we use enterprise terms and switch training off wherever a provider offers it. Your work is stored for one reason: so you can come back to it.

See the Privacy Policy for how this holds across everyone who touches your data.

Every brief is a sealed world

Each brief is worked entirely on its own. Nothing of one person's work ever reaches another person, and one brief's work never bleeds into another. The only things that travel between your own briefs are the ones you confirmed and can see: your brand kit and your shared facts. Each one lands visibly in the brief it enters, and each one is yours to turn off. The work itself never carries: a new brief reads your words fresh.

See the Privacy Policy for how sealed briefs sit alongside resuming your work, search, and memory.

The studio checks its facts before it writes them

Before the room builds, it grounds the work. It reads your brief, finds what it doesn't yet know, and checks the facts it's about to rely on against the live world. Real sources, not guesses. Careful over confident.

See About Kaldune for how a job flows, research to finished work.

You have the last word

Nothing ships without your say. You watch the work happen, you steer it when you want to, and at any point on any job you can review it, redirect the room, or stop the pass entirely. The studio works while you watch, and it answers to you.

See About Kaldune for how you direct the room.

How we secure your work

Three commitments, kept the same way for a solo maker and a mid-size buyer. Same words in the studio drawer, same words here.

How we keep Kaldune and your data secure

If you're deciding whether to bring confidential material to Kaldune, here is how it is kept safe. The promises about your work itself are on this page: we don't read it, we never train on it, every brief is sealed, and where it lives and how it is encrypted. The providers who handle it are on the sub-processor list, and where our compliance work stands is further down. Our trust centre, trust.kaldune.ai, shows our controls, our sub-processors and our compliance status.

Your data never mixes with another client's. Every time a brief is opened, the studio checks that you own it or that it was shared with you, and our own accounts pass the same check. A brief you can't open answers exactly as if it didn't exist. Underneath, the database enforces row-level security on the tables that hold accounts, briefs and money, and the logins the studio's services use cannot bypass it.

Past work comes in only when you bring it. To use something from another of your briefs, you pick it from your own briefs and the studio copies it in, the same way as an upload. Only briefs you can open are offered.

Our own tools read how the work ran, not the work. To keep the studio healthy, we look at operational records: timings, errors, costs and which tools ran. The tools that grade and count across all clients' briefs report only those records, never the words of your briefs or your files.

What reaches the services the studio works with. Each AI service the studio uses on your work is named on the sub-processor list, with exactly what reaches it and its terms.

The environment itself.

Who runs the studio

Kaldune is operated by Studio58, Inc., a Delaware corporation. The registered agent of record is on file with the Delaware Division of Corporations at icis.corp.delaware.gov. One product, one voice: the promises on this page apply to every customer, from a first pay-as-you-go brief to an enterprise account. Nothing is gated behind a plan tier or a signed NDA.

Where the studio is available

Kaldune is offered only in the countries and regions where the whole studio can serve you, and never where U.S. sanctions apply. It is not offered in Afghanistan, Antarctica, Belarus, China (including Hong Kong and Macao), Cuba, Iran, Kosovo, Myanmar, North Korea, Russia, Syria, Venezuela, Western Sahara, Yemen, or the Crimea, Donetsk, Kherson, Luhansk or Zaporizhzhia regions of Ukraine. Access from every country and territory on this list is blocked at the network layer, and payments from them are refused; the listed regions of Ukraine are prohibited by the Terms of Service §13 and the Usage Policy §1.5. If you travel to one of those places briefly, do not sign in to the Service until you leave.

Where your work lives

Your work lives in the United States: the database in Iowa, your files in a US multi-region, with a nightly copy in Oregon. The Postgres database that holds your account and your room index sits on a private network, reachable only from inside our own service. Your files sit in storage buckets that are locked to us by policy. The buckets refuse any public listing, and no employee has a walking password to the drawer.

Everything is encrypted at rest with AES 256. Everything in transit is encrypted with TLS 1.2 or better. HSTS is on so a browser that has visited us once will refuse to talk to a downgrade.

When you publish your work

Nothing you make is public unless you publish it. When you choose to put a piece of work on the web as a public page, the rules are plain:

The binding version is the Terms Section 3.9 and the Usage Policy Section 2.16.

Who touches your data

Kaldune is a small, solo-founder-owned company as of this date. There is no support tier that reads your work in the normal course. When you ask us to look at a specific item to help you, one person opens that one item, and administrative access is logged. We do not sell your data. We do not share it with advertisers. We do not use it to build a picture of you beyond what is listed above.

The vendors we use to run the studio (the model providers, the payment processor, the email sender, the cloud) are named in the sub-processor list. Each vendor is bound by its commercial terms, and the data-processing terms we hold are linked on that list. The language models the studio calls on and our cloud infrastructure are contractually barred from training on your work. For specialist tools, we use enterprise terms and switch training off wherever a provider offers it. New sub-processors are announced on that list 30 days before they begin handling customer data; write to privacy@kaldune.ai to have each notice emailed to you. Public registers the studio searches, such as trade mark offices, receive only the search itself; they are listed on the same page.

What we don't do

Certifications we do not have

Honest is better than posture. As of today:

We are working on these three with our compliance platform. None of them is held today, and we show no badge. Our trust centre, trust.kaldune.ai, shows where each one stands.

What we do carry:

Report a security issue

Please email security@kaldune.ai with "Security" in the subject line for anything you find that looks wrong. We publish a security.txt with the same contact. Our Terms §19 commit to safe harbor for good-faith research: no legal action against a reporter who acts in good faith.

Report abuse

If a published page or anything made with Kaldune looks abusive, illegal or infringing, email safety@kaldune.ai with the page's address and what's wrong. We take down pages that host abuse.

Talk to us as an enterprise buyer

Write to enterprise@kaldune.ai with the subject "enterprise buyer". We will send our current security posture document, a sub-processor list, and answer procurement questions the same week.

If you want the exact terms

This page is the plain version, gathered in one place. Every promise on it is written out in full, in the terms a lawyer and a regulator would hold us to, on these pages:

Something not covered here? Getting help routes you to the right place and tells you what happens next.