Skip to content
How Studio-Tools handle your files

Your files are processed in your browser.

Every file-processing tool in DigiLakshya Studio-Tools does its work on your machine — the creative you drop in is opened, checked, compressed or converted by JavaScript running in your own browser, not on our server. That's a design decision, not a promise we ask you to take on faith: this page spells out the rule, the exceptions (including Digi Bot, the production service, which works on our servers), and exactly what we do record.

Plain language, no legalese. For the site-wide policy, see the privacy policy.
The rule

These tools process files 100% in your browser

Drop a file into any of these and it is never uploaded to DigiLakshya. Close the tab and it's gone. That's what makes them safe for unreleased campaigns and client work under NDA.

Processed in your browser, with one server step at download: these four do their work on your machine too, but the finished PRO download makes one licence-check round trip through our server (it is not stored — see exception 4).

One detail worth knowing about the Background Remover: the traffic flows toward you, not from you. On first use it downloads the AI model (~179 MB on the default setting, 43 MB on Faster) to your browser and caches it — your image is then processed on your own device and never uploaded. We don't claim the tools work offline, and we don't wave certifications around; the claim here is narrower and checkable: your files aren't sent to us.

The exceptions, stated plainly

When something does reach our server

Eight cases — every one of them starts with an explicit click from you, never automatically.

1. Opt-in hosted share links

Some tools offer a hosted link so a client or teammate can open your work without a file attachment. Creating one uploads that shared snapshot to DigiLakshya: Ad Preview's "Create share link" — available on free accounts with a monthly allowance, 50 a month on Pro and unlimited with the Agency pack — stores the previewed creatives and auto-expires after 3 days on free, 30 days on Pro; Creative Review's Pro share and team-review links store the annotated screens as flattened images, with feedback share links expiring after 3 days. Hosted shares draw on your account’s storage budget and are kept in secure cloud storage (Cloudflare R2) until they expire — then they're deleted automatically. The one link with no end date is Character Animation's editable copy (PRO): it uploads that one project when you choose to share it, anyone with the link can open their own copy, and it stays until you delete it in My links or delete your account. Sharing is always a deliberate button press — previewing and annotating alone upload nothing.

2. Workspace client-report links

A Workspace manager can generate a read-only report link for a client. The link itself stores only its settings — which client, which columns are visible, the month window, an optional passcode (kept hashed) — and renders a live view of board data that already lives in your team account. It doesn't copy your board anywhere new, and links work until you revoke them.

3. Team apps are server-side — that's the product

Workspace, Leave Manager and team chat (including chat attachments) exist so several people can see the same data — so that data is stored per account, keyed to your team — board and leave data on our server, chat attachment files in secure cloud storage (Cloudflare R2). Attachments live in a size-capped, self-pruning pool tied to the workspace owner; when an attachment is pruned or its board is deleted, the stored file is deleted too. Chat messages are kept for 12 months (older ones are archived by month on our server, then deleted), and all of a board’s chat goes when the board is deleted. A tool can't both live only in one person's browser and be shared with a team; for these, server-side storage is the feature.

Video Meetings works the same way: a meeting's title, time, agenda, the addresses you invite, their Yes/No answers and who joined and for how long are stored on our server with your account, and the invitations and updates are e-mailed from us. During a meeting, audio, video and screen shares travel through Cloudflare’s real-time media servers to the other people in it; nothing is recorded or stored. Messages typed in the meeting’s chat are kept only until the meeting ends, then deleted. If someone uses the link in an invitation to stop meeting invites, we keep that address so no one can invite it again.

4. Four tools send a Pro download through our licence check

In four tools the Pro file really is different from the one a free account may save — Image Optimizer, Backup JPG Generator, HTML5 Ad Generator and Banner Resizer. There, the finished file makes one round trip through our server so we can verify the plan, then streams straight back to you. It is not stored. Everywhere else the file is saved straight from your browser and never reaches us at all. Separately, and on every plan: if you are signed in, a download is noted in your account activity by file name, size and which tool produced it — never the contents, and never the file. Signed out, nothing is recorded.

5. Send Files is an uploader — that's its entire purpose

Send Files exists to move files to someone else, so of course it uploads them: your files go straight from your browser to secure cloud storage (Cloudflare R2) and live there until the link expires — 3 days free, 30 days Pro — then they're deleted automatically (abandoned half-uploads are cleared within a day). Our server keeps only the file names, sizes and expiry, never the contents. Links are unguessable random tokens, but anyone holding one can download, so don't send secrets you wouldn't email.

6. Saving your work to your account (PRO)

When you press Save to account in a builder or a big-file tool, the document or file you chose to save is stored in secure cloud storage (Cloudflare R2) under your account, so you can reopen it from any browser. It stays until you delete it. Nothing is saved unless you press Save.

7. Digi Bot jobs: your brief and files are processed on our servers

Digi Bot is a production service, not an in-browser tool. When you send it a brief, the brief and any attachments (up to 5 GB a job) are uploaded to our servers, and our production system processes them with AI models from our technology providers to do the job — with people on our team when needed, and always for Studio Team jobs. Your files are used only to do that job and are not used to train those models; files and download links are kept for 30 days. The Digi Bot terms set out the rest.

8. Character Animation AI drafts, AI art, AI voices and AI video (PRO), and AI Studio: what you send goes to the AI

When you press Write and build in Character Animation's AI draft, the idea, script or storyboard you typed and any character notes — with the editor's list of characters (including the names and looks of your own characters on the stage), voices, actions and backgrounds, and, when you continue an animation, its name and spoken lines — is sent through our server to Anthropic's Claude, which writes the scene plan. Nothing else leaves your browser: no pictures, no audio, no project file; the voices and the animation are made on your computer. We keep the plan it returned for 7 days (so the same draft can be fetched again without a second charge) and a record of the draft's size and cost for billing — not the text you typed. Anthropic does not use API requests to train its models.

AI art (20zn): when you press Make it in AI art — or have an AI draft paint its backgrounds — the description you typed (or the scene's setting the AI draft wrote) and the style you picked are sent through our server to OpenAI, which draws the picture or writes the SVG. Nothing else leaves your browser. We keep the finished piece for 2 days (so a lost answer can be fetched again without a second charge) and a record of its size and cost for billing — not the text you typed. OpenAI does not use API requests to train its models by default.

AI voices (28a): when an AI draft voices its lines, the lines, who says each one and the kind of voice each character has are sent through our server to ElevenLabs — directly, or through fal, which runs ElevenLabs’ voice models — and spoken there. Nothing else leaves your browser. We keep a record of how many characters were voiced and what it cost, for billing — not the lines.

AI video (29): when you press Film it with AI video, each scene’s start picture is painted first as AI art above (a picture of the scene as the editor draws it, and the paintings of your painted characters in it, go to OpenAI); then that picture, a description of the shot (the place, who is in it and what they say) and the scene’s voice lines are sent through our server to fal, which makes the video with the MiniMax video model. We keep the finished video on our server for 2 days (so a lost answer can be fetched again without a second charge) and a record of its length and cost for billing; the picture and voice lines you sent are deleted once the shot is made (or after 2 days if it never is).

AI Film Maker (30c): the AI Film Maker is made of these same parts, in its own steps. Your idea, the kind of film and the length you chose go to Anthropic’s Claude for the shot list (and each change you ask of the Director). On the Look step, See your cast in this look sends the words that describe your cast — and any pictures you add there (a photo or drawing of someone in your story, or a picture in a style you like) — to OpenAI, which paints the preview; your pictures go with that one request and are not kept on our server. The cast’s paintings, the start pictures (and the words of any change you type under one) go to OpenAI, the AI voices’ lines to ElevenLabs and each shot to fal, exactly as above. Your film — its shot list, look, previews, your pictures and the step you reached — is kept in this browser (Your films, on its start page) and nowhere else, unless you are PRO and press Save, which keeps it in your account like any other saved work.

AI Studio: AI Studio’s photo, video and sound tools are built from these same parts. The photos and videos you add, and the words you type for them, are sent through our server to fal, which runs the photo, video, music and sound models; pictures it paints go to OpenAI, words it writes for you come from Anthropic’s Claude, and voices are made as described above. What you send and what comes back are kept on our server for up to 2 days (so a lost answer can be fetched again without a second charge), with a record of the cost for billing.

9. Studio Canvas: designs, share links, comments and editing together

Studio Canvas runs in your browser. A PSD, SVG or image you open is read on your computer — it is never sent to us to be converted — and a design is kept in your browser's own storage until you choose otherwise. Fonts named in a PSD are used only when they are installed on your computer; they are never uploaded. A font you choose to upload is kept in this browser; when a design using it is saved to your team's files, the font file is stored on our server with the design so your team can see it. A share link never receives the font file: it shows that text as a picture. When you press Save to account (PRO), the design and the images in it are stored on our server for your team, who can open and edit them, and kept until someone with the right to do so deletes the design. When you press Share, anyone with the link can see that design (a password, if you set one, is stored only as a one-way hash); we count how often the link is opened. On a comment link, a visitor's comments are stored with the name they typed — no account, no e-mail address; we keep a scrambled form of their IP address only to limit floods, and it is never shown. Deleting the design deletes its images, link and comments with it.

Editing together (PRO). A design saved to your team's files connects to our live service, which runs on Cloudflare. It receives your display name and a one-way id, so teammates in the design know it is you. Working alone, nothing else is sent. When a teammate joins, the design's text and layer data, and each edit, cursor and selection, pass through Cloudflare and are stored there while you work together. Images are not: they stay on our server. That copy is deleted automatically once the design is saved and at most one person is left in it. If everyone leaves before it has saved, it is kept so that nobody's edits are lost, until the next person opens the design and it saves, and otherwise for up to 30 days. We keep daily counts of how much live editing is used, with no names or designs in them.

10. Paying for PRO or Digi Bot credits

Payments are taken by PayPal or, for payments in India, Razorpay. You pay inside their own checkout, so your card, bank or UPI details go to them, not to us. We receive their confirmation of the payment — what was bought, the amount and the account it is for — so we can switch your plan or credits on, and we keep that record.

The small print, in large print

What we record — and what's yours

Analytics: coarse on purpose

We use standard Google Analytics tags to learn which tools earn their keep: an event when a tool is opened, an event when a tool exports something, an event when a checkout opens. The payload is a tool name like "bg-remover" or a product name like "pro" — never file contents, never filenames. Alongside that, our own server keeps a plain visit log — page address, referring site, country, mobile or desktop, and your account name if you're signed in. Signed-out visitors are never stored by IP address: it becomes a one-way code re-scrambled every night, so a day's visitors can be counted but nobody can be followed across days. Share links are logged with the token removed, and raw entries are deleted after 90 days. The site also runs Google Tag Manager, a Google Ads tag and the LinkedIn Insight Tag to measure our own advertising; in the EU, EEA, UK and Switzerland they wait for your cookie choice, and Reject keeps them off anywhere. None of them sees your files. And when something in the studio breaks, your browser sends an anonymous error report — the tool, the error's message and where in our code it happened, with web addresses, file names and e-mail addresses removed — no account, no IP address, nothing from your files, deleted after 30 days. The weather in the top bar asks our server once a day which city and country your connection points to (Cloudflare's estimate, the position rounded to about a kilometre) so it can show your local weather — the answer is kept only in your browser and our server doesn't store it; a home city you choose in the world clock always takes its place.

Your files stay yours

We claim no rights over the files you process or the output you generate — as our in-app terms put it, "your content stays yours." Our copyright covers the tools themselves: the code, design and bundled samples. You're responsible for holding the rights to the assets you bring; everything you make with them belongs to you.

FAQ

Quick answers.

Do the free tools upload my files?
No. Every file-processing tool — the validators, compressor, resizer, converter, image slicer, EDM builder, backup JPG generator, HTML5-to-GIF, ZIP and SVG optimizers, background remover, color picker, bulk rename, Creative Review annotation, the Design Compare design-vs-build comparator, the email and social QA checkers and the campaign namer — does its work in your browser. Your files never leave your machine while you use them. (In four of them — Image Optimizer, Backup JPG Generator, HTML5 Ad Generator and Banner Resizer — the finished PRO download makes one licence-check round trip through our server; it is not stored.) The only time anything reaches our server is when you explicitly click a share, team or live-check feature — such as Email QA’s Pro link check, which sends the link URLs and never the email itself, or its design share links, which upload the one email you explicitly chose to share so the preview can be served — and those cases are listed plainly on this page.
What exactly gets stored when I create a share link?
Only what's needed to serve the link, only after you click. An Ad Preview hosted share stores the creatives in that preview so your client can open a URL — it auto-expires after 3 days on a free account, 30 days on Pro (or never, if a Pro user chooses that). A Creative Review share stores the annotated screens as flattened images — it expires after 3 days. Both draw on your account’s hosting storage. A Workspace client-report link is lighter still: it stores the link's settings (which client, which columns, an optional passcode kept hashed) and shows a live, read-only view — it doesn't copy your board anywhere new.
Does the AI background remover send my photo anywhere?
No — the traffic goes the other way. On first use the tool downloads the AI model to your browser (about 179 MB on the default Best-quality setting, 43 MB on Faster) and caches it. Only the model files come down — from models.studiopreviewworld.com, or Hugging Face and cdn.jsdelivr.net as fallbacks — and no image goes up. Your photo is then processed on your own device. There is no upload of your image, which is exactly why we built it that way.
What analytics do you collect when I use a tool?
Four things, all deliberately coarse. Standard Google Analytics records which tool was opened, that an export happened, and when a checkout was opened — carrying a tool name like "bg-remover", never your file's contents and never its filename. Separately, our own server keeps a visit log: the page address, the site that referred you, your country, whether you're on mobile or desktop, and — if you're signed in — your account name. We do not store the IP addresses of signed-out visitors: they become a one-way code that is re-scrambled every night, so we can count how many people visited on a given day but cannot follow anyone from one day to the next. Share links are recorded with the token stripped out, so a log entry can never open someone's work. Raw entries are deleted after 90 days. Third, like most marketing sites, digilakshya.com runs Google Tag Manager, a Google Ads tag and the LinkedIn Insight Tag to measure our own advertising at page level. Where the law asks for consent first — the EU, EEA, UK and Switzerland — they wait for your answer to the cookie banner, and pressing Reject keeps them off anywhere. None of them receives your files, their contents or their filenames. Fourth, when something in the studio breaks, your browser sends us an anonymous error report: the tool that was open, the error's message and where in our code it happened — with web addresses, file names and e-mail addresses removed before it leaves your browser. It carries no account, no IP address and nothing from your files, and it is deleted after 30 days.
Who owns the files I process with Studio-Tools?
You do, entirely. We claim no rights over the files you bring or the output you generate — our in-app terms put it as "your content stays yours," and the copyright we hold covers only the tools themselves. You're responsible for having the rights to the assets you work with; what you make with them is yours.

Tools you can point your NDA at.

40+ free in-browser production tools from a studio that handles confidential agency creative every day. Your files stay on your machine unless you explicitly choose to share, transfer or save them, or send them to Digi Bot.