What we collect, why we have it, who else touches it, and how to get it back or have it deleted.
Version 2026-07-25 · Effective 25 July 2026
Draft — not yet reviewed by a lawyer.
Still a placeholder insrc/lib/legal/terms.ts: Legal contact address, Privacy contact address, Copyright agent address. This notice disappears once they are filled in. Do not open public sign-up while it is showing.
Privacy policy updated: 8 September 2026.
MediaWriter Studio is operated by Translucid LLC. For anything in this policy, contact [[email protected] — mailbox must exist and be monitored].
Business mailing address: PO Box 194, La Mirada, CA 90637-0194, United States.
Private beta requests. If you request access, we store your email, optional project note, request date and permission to contact you about access. The workspace owner reviews these requests. This does not create an account or subscribe you to a newsletter. Requests expire from the active list after 180 days and are removed when the list is next used; backups expire on their normal retention schedule. Contact [[email protected] — mailbox must exist and be monitored] to withdraw your request sooner. We also temporarily store a keyed hash of your IP address to limit repeated requests, clearing it after its one-day limit expires when the form is next used.
Account details. Your name and email address, and a hashed password if you set a MediaWriter password. If you use Google sign-in, we receive the identity details described below. We never receive your Google password.
What you put in. Everything you upload or create — promos, source documents, video and audio, briefs, research runs, chat history and generated drafts.
Operational records. Session records, IP address, and logs needed to run the service, investigate faults and stop abuse.
We do not ask for payment card details, and while MediaWriter is in beta there is no billing to attach them to.
Choosing “Continue with Google” asks Google to identify you using the openid, email and profile permissions. We receive your Google account identifier, name, email address, whether Google has verified that address, and profile image URL. This sign-in does not request access to your Gmail messages, Google Drive files, contacts or calendar.
We use these details to create or find your MediaWriter account, display your account identity, and protect sign-in. A Google account can be linked to an existing MediaWriter account with the same email only when both addresses are verified. Google sign-in data is not used for advertising or to train AI models.
We store these identity details and the Google account link in our account database. The sign-in service also stores the identity and access tokens returned by Google, their permissions and expiry information, and a refresh token if Google provides one. These credentials support the account connection; they do not grant the Gmail or Drive permissions listed above.
Google processes the sign-in request under its own privacy policy. DigitalOcean hosts our account database and backups, and Cloudflare processes requests for network security and access control. If we send you an account verification or password-reset email, Resend receives your email address and that message. We use these services to operate and secure your account, and do not sell your Google sign-in data. The subprocessors page describes the separate providers that receive content when you use creative tools.
Connections to our production service use HTTPS. Access to account records is restricted on the server, and owner and administrator accounts must use two-factor authentication. Google identity details and stored account credentials remain while your MediaWriter account exists, subject to the deletion and backup limits below.
You can remove MediaWriter’s Google connection in your Google Account connections. Revoking Google access does not delete your MediaWriter account, workspace or existing MediaWriter sessions. Sign out of MediaWriter to end your current session, or use the account controls below to request deletion. If Google is your only sign-in method, removing the connection can prevent you from signing in again until you reconnect it.
To give you the product: storing your work, running the models you ask us to run, and keeping your account secure. We do not sell your data, and we do not use your work to train models.
Note the difference between those two claims. We do not train on your work. We cannot make that promise on behalf of every model provider, which is why the next section exists.
MediaWriter is a layer over other companies’ models and services. Running a draft, a research question or a video render means sending that content to a third party. The full list — who they are, what each is for, and exactly what of yours can reach them — is on the subprocessors page, and it is generated from the integrations that actually exist in the product.
Each of those providers has its own terms and its own retention. We choose providers whose terms say they do not train on API content, but you should read them if that matters to you.
We process your account details and your content to perform our contract with you — without them there is no product to deliver. We process operational records such as logs and IP addresses under our legitimate interest in keeping the service secure and working. Where we rely on consent, you can withdraw it at any time by writing to [[email protected] — mailbox must exist and be monitored].
We use essential cookies to keep you signed in, complete Google sign-in securely, and manage two-factor authentication. Our network security services may also set access or bot-protection cookies. There is no advertising cookie, no third-party tracker and no cross-site profiling on the Studio, which is why you are not being asked to dismiss a consent banner.
We do not sell or share your personal information, and we do not disclose it for cross-context behavioural advertising, as those terms are used in US state privacy laws. There is no opt-out to offer because there is nothing being sold.
Your workspace is stored on servers we operate, isolated per account. Large uploads may be stored in object storage. Model and media providers are located in various countries, so using MediaWriter means your content is processed internationally.
Your work stays until you delete it or ask us to close your account. Backups are retained on a rolling schedule and a deletion can persist in them for up to twelve months before ageing out.
Content already sent to a model or media provider is subject to that provider’s retention, which we do not control.
Export and member account deletion are self-serve, under Your account → Account and data. Export downloads your promos, briefs, chats, research and settings as JSON along with your uploads. Delete removes your account, including its stored Google account link and tokens, and erases your workspace subject to the limits below. Owner and administrator accounts require assistance because they share the organization’s workspace.
To correct something, or for anything the buttons do not cover, write to [[email protected] — mailbox must exist and be monitored] and we will confirm what we have done.
Two honest limits on deletion. Encrypted backups age out on their own retention schedule rather than being edited, so a deleted workspace can persist there for up to twelve months. And generated media held in shared storage is not yet separated per account, so it is not selectively erased — ask us and we will remove it by hand.
Depending on where you live you may have additional rights over your personal data, including to object to processing or to complain to a data protection authority.
Access to the Studio requires an account. Each workspace is isolated from every other. Media files are served only to signed-in sessions. No service can promise perfect security, and we do not.
MediaWriter is a tool for marketing professionals and is not intended for anyone under 18.
We will update the version stamp at the top when this policy changes, and tell account holders about material changes before they take effect.