How Studio-Tools handle your files

Your files never leave 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, 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.

One detail worth knowing about the Background Remover: the traffic flows toward you, not from you. On first use it downloads the AI model (~43 MB) 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

Five 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 daily allowance, unlimited on Pro — stores the previewed creatives and auto-expires after 3 days on free, 30 days on Pro (the free "Share file" .html export runs locally and never touches our server); 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), encrypted at rest, until they expire — then they're deleted automatically. 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, encrypted at rest). 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. A tool can't both live only in one person's browser and be shared with a team; for these three, server-side storage is the feature.

4. Pro full-size downloads pass through once

When a Pro account downloads a full-resolution result, the finished file makes one round trip through our server so we can verify the plan — then it streams straight back to you. It is not stored. The activity log records the file's name, size and which tool produced it — never the contents.

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), encrypted at rest, 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.

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.

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-vs-build Creative QA 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. The only time anything reaches our server is when you explicitly click a share, team or live-check feature — such as Email QA\u2019s 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. The free Ad Preview "Share file" export never touches our server at all.
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 43 MB on the default setting) and caches it. 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?
Two things, both 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.
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.

20+ 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.