How we treat you and your work

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 Stripe, the payment processor that handles the money. The studio never sees or stores your full card number. Stripe holds it, and Stripe is bound to use it only to process your payment.

See the Privacy Policy for what we hold, and what Stripe 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. 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. The one exception is support: 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. Every one of those accesses is logged.

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. That's the only other exception, 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 provider that powers the room is contractually barred from training on your work too. 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 delivery.

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 on the landing page, same words in the studio drawer, same words here.

• We do not train on your work. Not us, not the model providers we use. Every provider is bound by contract not to.
• We do not share your data. Not to any partner, not to any advertiser, not to anyone. The only exception is a valid legal order, and even then we push back and tell you first where we can.
• We do not connect to your systems. The studio has no path into your files, your email, your calendar, or your production. What you paste, upload, or ask for is what it sees, and nothing else.

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 around the world under U.S. law. It is not available in Cuba, Iran, North Korea, Syria, or the Crimea, Donetsk, Luhansk, Kherson, or Zaporizhzhia regions of Ukraine, or in any other place subject to U.S. comprehensive sanctions. Access from those places is blocked at the network layer and 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 Google Cloud, in the us-central1 region. 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 Google Cloud 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:

• Pay-as-you-go: your page lives at an automatically generated address for 30 days from publication or its latest reactivation, and bringing it back is one click, free, no purchase required.
• With a subscription: you can hold a custom address, and your page stays up for the life of your subscription, with a 14-day grace period if it lapses.
• Always: every published page carries a small MADE BY KALDUNE mark, you can take a page down instantly, and we take down pages that host abuse. Unpublishing or expiry never touches the work in your studio.

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 every 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 your name, your email, and your time zone.

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 one is bound by a data-processing agreement. Each one is barred from training on your work. If we add a new vendor, we tell you 30 days ahead.

What we don't do

• We don't train models on your prompts, your uploads, or your outputs.
• We don't fingerprint your visitors across other sites. There are no third-party trackers on the studio.
• We don't watermark your delivered work with our tool string. Our post-processing strips the Chromium and Sharp fingerprints from every PDF and image the studio ships.
• We don't keep your EXIF. Photos you upload are stripped of GPS and camera metadata at the door.
• We don't use a model provider whose terms permit training on our traffic. Every model provider in our sub-processor list commits contractually that the customer inputs and outputs it sees through our use are not used to train its models.

Certifications we do not have

Honest is better than posture. As of today:

• SOC 2, not certified. On the roadmap; the audit is planned when the business scale justifies the first-year engagement.
• ISO 27001, not certified. After SOC 2.
• HIPAA, we do not sign BAAs. Do not upload regulated health information; nothing in the service is built to carry it, and no BAA protects it here.
• FedRAMP / IRAP / C5 / StateRAMP, none. Not planned at this stage.

What we do carry:

• PCI DSS SAQ A, the eligible posture. Card data never touches Kaldune servers; Stripe holds it end to end.
• GDPR + CCPA, DPA available, sub-processors listed, standard contractual clauses in flight. Data subject requests: hello@kaldune.ai, 30 day response.

Report a security issue

Please email hello@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.

Talk to us as an enterprise buyer

Write to hello@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:

• Privacy Policy: what we collect, why, and the promises behind it.
• Terms: ownership, your account, and how the studio and you agree to work together.
• Usage Policy: what the studio will and won't take on.
• Privacy Choices: the controls in your settings and exactly what each one does.
• Data Processing Addendum: for business customers processing their own end-users' data through Kaldune.

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