The agency made of AI Open the studio

Privacy Policy

What we collect, why, and the promises behind it. Every promise on this page is written out in exact terms further down, and every one of them is true.

Studio58, Inc. · Last updated 30 October 2026 · Version 2.24

The promises, plainly

The rest of this page is the same promises, in the exact terms a lawyer and a regulator would hold us to.


Who we are

Studio58, Inc. ("Kaldune," "we," "us," or "our") is a Delaware corporation and the company that operates the Kaldune service. Studio58, Inc. is the data controller for the personal data described in this policy: it decides what we collect and why. This policy covers individual and business customers, and it applies to Kaldune's users worldwide.

1. What we collect and why

We collect only what we need to run Kaldune for you.

Your account. Your name (you sign in with it and we address you by it), your email address (to sign you in and send the service messages your account depends on), your time zone (so the studio knows your local time), and your language preference. Kaldune is passwordless: you sign in with Google or with a one-time code sent to your email. There is no password field in the product and no password stored anywhere. We also record when you accepted our Terms and which version you accepted.

How you found us. If you arrived through a link that carries one of our own tags (for example, the link in our TikTok, Instagram, LinkedIn or X profile), or came straight from one of those four sites, we note that one word on your account when you sign up, so we can count how many people each channel brings us. Of the page you came from we read only the site's name, to choose that word; we keep nothing else about the link or the page you came from, no outside company receives it, and it is deleted with your account.

Security and fraud signals. When you sign in and when you use the studio, a device-recognition service reads signals from your browser so that each person gets one welcome credit. We keep, with your account, the device identifier it returns, the IP address you signed up from, and whether the visit looked automated or came through a VPN or a private window. These signals are recorded; they never stop you signing in or using the studio. For each signed-in device we also keep the browser and operating system and, where our network edge provides it, a coarse location, so you can see and end your sessions in Settings. If you verify a phone number, we keep a one-way hash of it, not the number. To stop a second welcome credit going to the same person or company, we keep a separate welcome-credit record. It holds only keyed hashes (HMAC-SHA256) of the email address, card, phone and device that received the credit; the key is held in a managed secret store, and only the service can read it. It also holds a keyed hash of the IP address you signed up from, for one day only, and your email address's domain in plain text, so we can cap welcome credits per company. It never holds your email address, IP address, browser string, device identifier, card or phone number themselves. We use it for nothing else, and we delete it 3 years after your account is deleted (Section 7).

Memory notes: none today, and yours to control if they ever exist. The studio keeps no memory of you between briefs; each brief starts from what you bring it. The studio is built to keep a small file of plain facts and preferences you've stated, the way an account team remembers a returning client, and it is not switched on. If it is ever switched on for your account, this is the commitment it arrives with, stated here first: each note is written in the studio's own words, carries its date, and is announced in the conversation when it is made; when you correct something, the note is updated then and there; if you run briefs for different clients of your own, notes are kept one file per client and never cross between them; memory never determines what the studio makes, and your current brief always outranks it; the studio does not note credentials or passwords, confidential or unannounced material, or sensitive-category personal details (health and the like); you can read, edit, or delete any note, or switch memory off entirely, in Settings; your data export includes the notes; and deleting your account deletes them on the same schedule as the rest of your data (Section 7).

Your card details, held by our payment processor, not by us. When you add funds or start a subscription, payment is handled by our payment processor. Studio58, Inc. never sees or stores your full card details; they go directly to the payment processor, which is bound to use them only to process your payment.

Your work, stored for you, never sold or trained on. The briefs you write, the files you attach, and the work the studio delivers to you. We store this so your studio is waiting when you return, so you can download everything whenever you want, and so you can resume a brief where you left off. Inside each brief, the studio also keeps the record of how Laura and her makers worked on it, including the exact requests they sent, so it can check its own work by automated replay; no person reads your work in it. The exact requests are deleted 90 days after they were sent and are never in our backups, and the whole record is deleted with the brief. It is your content, not a profile of you: we do not read it in the normal course, we do not profile you from it, we do not sell or share it, and we do not use it to train or improve any AI model.

Usage and technical data, kept to a minimum. Basic technical logs to keep the service secure and to fix faults, plus the ledger of your credits and receipts so your billing is accurate. Our service logs are kept 30 days, and we do not use them to build a profile of you.

Messages you send us. When you email us, we keep your message and your email address so we can answer you. An AI assistant on our support desk answers routine questions itself; a person on the team handles the rest, and always anything about money, a legal matter or your account's standing. Every reply comes from the same support address.

Before you sign in. On our front page you can type what you need and read a short outline of what the studio would deliver for it, before you sign in. We keep what you typed and that outline for 30 days, so we can show you the outline again, and our own sweep then deletes them. If you sign in within those 30 days, your words become the start of your brief, the outline is shown to you once more on your first screen, and our copy of it is deleted then. The outline is written by the same AI providers under the same terms as the rest of your work (Section 2): it is never used to train anything. No person reads what you typed or the outline.

We do not collect special-category data (health, biometric, and the like) as a matter of course. If your briefs happen to contain such data because that is the work you asked for, it is handled as your content under the promises above, not added to any profile of you.

2. The AI models the studio calls on

The studio makes your work: Laura and her makers plan it, make it, check it and deliver it. To do that, the studio uses AI models and specialist tools from other companies, under their commercial terms. Each one receives only the part of your brief its step needs, and what it returns comes back into your brief, where the studio checks it. This matters for your privacy, so we are specific:

The vendors that handle your content are listed on our Sub-processors page (Section 4).

3. Every brief is its own sealed world

Every brief in Kaldune is worked in its own sealed context, and nothing carries from one brief to another except what you choose to bring in:

A brief persists so you can leave it and come back; the same brief, resumed, is still that one sealed world, right where you left it. Persisting and resuming happen within a single brief; they never merge one brief into another.

4. Who we share your data with

We do not sell your personal data, and we do not share it except with the service providers we need to run Kaldune. Each receives only what its piece of the work needs. They include our cloud host, the AI services the studio uses to make your work, our payment processor, our email sender, phone verification, the device-recognition service that guards the welcome credit, and the AI services that help us answer your email.

The full list, with what each provider does, what it receives, where it processes it, and its data terms, is on our Sub-processors page. It is generated from what our software actually calls, and our build fails if a provider our software reaches is missing from it.

When we add a new provider. We give advance notice, currently 30 days, before a new provider that handles your data starts doing so, and business customers with a data processing agreement can object under it.

5. Where your data lives, and international transfers

Your account and your work are stored in the United States: our servers and database run in us-central1 (Iowa), files are stored in a US multi-region, and a backup copy is held in us-west1 (Oregon). Kaldune operates from the United States. A few providers process outside the United States, as the Sub-processors page states for each. When we move personal data out of the UK, the EEA, or Switzerland, we protect it with a recognized transfer mechanism, principally the European Commission's Standard Contractual Clauses together with the UK and Swiss addenda where they apply. If you are elsewhere in the world, your data is likewise processed in the United States; where your local law requires a transfer safeguard, we apply one.

6. We do not read your work, and the three narrow exceptions

In the ordinary operation of the service, no one at Kaldune reads your briefs or the work in them. There are exactly three exceptions, and we state each plainly:

Support, when you ask. If you ask us for help with something in your work, and only then, a support specialist can open the specific brief or item you pointed us to, for the specific purpose you asked about, and nothing more. Every read of our database and every change anyone at Kaldune makes to your stored data outside the service is logged. You can ask us about any access to your work at privacy@kaldune.ai.

A valid legal demand. We disclose your work or personal data to a government or law-enforcement authority only when we are legally compelled to, by a validly issued subpoena, court order, or warrant, or in a genuine emergency where someone is at risk of serious physical harm. When we get such a request, we check that it is valid, we push back on requests that are overbroad or vague, and we disclose only the specific data the law actually compels. Wherever we are legally permitted to, we tell you before we disclose, so you have the chance to protect your data. We never volunteer your work to anyone.

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.

7. Retention: how long we keep your work, and when it is gone

Two things this section does not do: it does not delete your work because your credits ran low, and it does not delete work from a brief you left unfinished. Your work leaves only when you delete it or close your account, or where the law requires it.

Legal holds. We may keep data longer where the law requires it, to resolve a dispute, or to deal with misuse.

8. Your controls, in Settings

Two of the most important rights are controls in the product itself, not a request you have to write:

One more control lives with the work itself: if you have published a piece of work as a public page, you can take that page down instantly, at any time. Nothing you make is public unless you publish it. The publishing rules by plan are in the Terms of Service, Section 3.9.

For anything these controls do not cover, email privacy@kaldune.ai and we will help.

9. Your rights around the world

If you are in the UK, the EEA, or Switzerland (GDPR). You have the right to access the personal data we hold about you; to rectify data that is wrong; to erasure, subject to the legal-hold exceptions in Section 7; to restrict or object to processing, including any direct marketing; to data portability; to withdraw consent where we rely on it; and to lodge a complaint with your data protection authority. The legal bases we rely on are performance of a contract for the core service and billing, legitimate interests for security and reliability, consent for marketing email, and legal obligation for tax records and valid legal process. We respond within one month, as the GDPR requires.

If you are in California (CCPA/CPRA). You have the right to know what personal information we collect, use, and disclose; to access and receive a copy; to correct it; to delete it, subject to Section 7's legal-hold exceptions; to opt out of sale or sharing (we do not sell or share your personal information as the CPRA defines those terms, so there is nothing to opt out of, but the right stands); to limit use of sensitive personal information (we do not use it beyond providing the service); and not to be discriminated against for exercising any of these rights. We do not use your personal information for cross-context behavioral advertising.

If you are in Brazil (LGPD). You have the right to confirm that we process your personal data; to access it; to correct incomplete, inaccurate or out-of-date data; to have unnecessary or excessive data anonymised, blocked or deleted; to data portability; to know with whom we share it; to withdraw consent where we rely on it, and to be told what follows if you refuse it; and to complain to the National Data Protection Authority (ANPD). Write to privacy@kaldune.ai, our channel for data protection requests.

If you are in South Korea (PIPA). Your personal data is transferred to and processed in the United States so that the service can run. The data is the profile, work and billing records described in Section 1. The recipients are the service providers named on our Trust page. The transfer happens over encrypted connections each time you use the service, for the purposes in Sections 1 and 2, and the data is kept for the periods in Section 7. You can refuse the transfer by not using the service or by deleting your account; without it, the studio cannot work for you. You may also complain to the Personal Information Protection Commission (PIPC).

If you are in Japan (APPI). Your personal data is provided to service providers in the United States. The United States has no single federal privacy law equivalent to the APPI. Protection there comes from sector and state laws and from the contracts we hold with each provider, which bind them to safeguards for your data consistent with the APPI. You may ask us for more on these measures, and you may complain to the Personal Information Protection Commission (PPC).

If you are elsewhere in the world. Many countries give you similar rights over your personal data: to confirm we hold it, access it, correct it, delete it, or receive a copy. Where your local law gives you those rights and it applies to us, we honor them. We do not make you clear a higher bar because of where you live.

Verification and agents. We may need to verify your identity before acting on a request, and we honor requests made by an authorized agent where the law provides for it.

10. Cookies

Kaldune uses only the cookies it needs to work: the session and sign-in cookies that keep you signed in, and security cookies, including a short-lived one (kaldune_device) that carries the device check through a Google sign-in. When you choose a language on kaldune.ai or in the studio, one more cookie (kaldune_locale) remembers that choice for a year, so the sign-in page opens in it, and the studio too unless you have chosen another language there; it holds only the language code. The device-recognition service (Section 1) may also store an identifier in your browser, for the welcome-credit guard only. We do not set advertising, analytics, or cross-site tracking cookies, so there is no consent banner to click through. Marketing email, if you opt in, always carries an unsubscribe link, and we do not sell your contact details.

11. Security

We protect your data with encryption in transit and at rest, passwordless sign-in, access controls that give staff only the access they need, 2-step verification enforced on every company account, a log of administrative access and of any change made outside the service to stored data, and the operational practices of a service that takes this seriously. The full picture, including our infrastructure, sub-processors, and vulnerability-reporting process, is published on the Trust page. If a data breach affects your personal data, we notify you and the relevant authorities as the law requires, without undue delay and within 72 hours of learning of it.

12. Children

Kaldune is not directed to children, and you must be at least 18 to use it. We do not knowingly collect personal information from anyone under 13; if we learn that we have, we delete it. If you believe a child has used the Service, contact privacy@kaldune.ai.

13. Changes to this policy

When we change this policy, we update the date at the top. If a change materially affects your rights, we tell you directly, by email or in the product, before it takes effect, and where the law requires it, we ask for your agreement.

14. Contact

For any privacy question, to exercise a right wherever in the world you are, or to ask about any access to your work: