Are my wedding photos uploaded anywhere?

No. The folder is read directly from your drive inside the browser using the File System Access API. There is no server that receives images, and you can confirm this by loading the page and then disconnecting from wi-fi — everything keeps working.

What is stored in my browser?

Two entries in IndexedDB: a handle for the last source folder and a handle for the last destination folder, so the resume function can reopen them. No image data is stored in the browser. Clearing site data removes both.

Does Shaadi Pic use cookies or analytics?

Neither. There are no cookies, no analytics scripts, no tracking pixels and no beacons. The web server keeps ordinary access logs, as every web server does, and those contain nothing about your photos.

Does anything third-party load on the page?

Two typefaces are loaded from Google Fonts, so Google sees your IP address and user agent when the page loads. That is the only third-party request. No photo data is involved.

What happens to my email if I join the iOS waitlist?

The address you type, along with which page you submitted from and a timestamp, is sent to the maintainer's notification channel so you can be told when the iOS app exists. Nothing else is sent, and you can ask for it to be deleted at any time.

Are my original photos modified?

No. Photos you keep are copied into a /selected subfolder with their filenames unchanged, and the originals stay exactly where they are. A small progress file is written into the folder so you can resume a session, and it can be deleted freely.

Privacy

The whole pitch is that nothing is uploaded, so this page states precisely what happens to your files and what — if anything — leaves the browser.

Last updated 4 September 2026 · by Harshit Luthra

Your wedding photos are never uploaded. Shaadi Pic reads the folder directly from your drive inside the browser, and there is no server that receives images. There is no account, no cookie, no analytics and no tracking of any kind.

The only thing this site ever sends anywhere is an email address, and only if you choose to type one into the iOS waitlist form. You can verify all of this in your browser's network tab, or by disconnecting from wi-fi after the page loads and continuing to work.

How the photos are read

When you click to open your wedding folder, the browser shows its own permission dialog and hands the page a reference to that folder using the File System Access API. Your photos are then read from disk into the page, one at a time, as you look at them. This is the same mechanism a desktop application uses, running inside the browser's sandbox rather than outside it.

There is no upload step because there is nothing to upload to. The site is static files served by a web server; it has no database and no image endpoint.

What gets written, and where

What	Where it lives	What it contains
Your keepers	A `/selected` subfolder inside the folder you opened	Copies of the photos you kept, filenames unchanged. Originals are not moved or modified.
Session progress	`.shaadi-photo-selector.json` in the folder you opened	Which filenames you kept, skipped or archived, so you can resume. Written atomically via a `.tmp` file alongside it.
Folder shortcuts	IndexedDB, in your browser, on your machine	Two entries only — a handle for the last source folder and one for the last destination folder, so "resume" can reopen them. No image data.
A write test	The folder you opened, momentarily	An empty file named `.shaadi-photo-write-test-…`, created to check the folder is writable and deleted immediately.

Every row of that table is on your own disk or in your own browser. None of it is transmitted.

What leaves your browser

Three things, and this is the complete list:

1. The page itself

Loading the site fetches its HTML, JavaScript, CSS and images from the server, like any website. The web server keeps standard access logs — IP address, timestamp, requested page, browser user agent. Those are ordinary server logs, not a tracking system, and they contain nothing about your photos.

2. Web fonts from Google

The interface uses two typefaces loaded from Google Fonts, which means your browser requests them from fonts.googleapis.com and fonts.gstatic.com. Google therefore sees your IP address and browser user agent when the page loads. No photo data and no identifying information about you is involved, but it is a third-party request and this page would be dishonest if it did not say so.

3. Your email, only if you type it in

There is a waitlist form for the iOS app that does not exist yet. If you submit it, the email address you typed is sent — along with which page you submitted from and a timestamp — to the maintainer's notification channel. Nothing else goes with it. If you do not submit the form, nothing is sent.

What there is none of

No analytics. No Google Analytics, no Plausible, no PostHog, no pixels, no beacons of any kind.
No cookies. The site sets none.
No account. There is nothing to sign up for, so there is no profile, no password and no email required to use the tool.
No advertising, and no data sold or shared. There is no data to sell.
No image processing on a server. HEIC decoding and EXIF reading run in your browser, in WebAssembly, on your machine.

How to verify it yourself

You do not have to take any of this on trust, which is the point of building it this way:

Open the app, then open your browser's developer tools and switch to the Network tab.
Start picking photos. Watch the request list — no image uploads appear, because none are made.
Or simpler: load the page, then turn off wi-fi. Keep picking. Everything continues to work, because everything is happening on your machine.

The offline test is the convincing one. A tool that was uploading your photos could not keep working with the network switched off.

Deleting everything

The photos and your picks are your own files, in your own folder. Delete the /selected subfolder and the .shaadi-photo-selector.json file and nothing remains.
The folder shortcuts live in your browser's storage for this site. Clearing site data in your browser settings removes them.
A waitlist email can be removed on request — write to [email protected].

Why it is built this way

Partly principle, and partly because it is a better product. A wedding delivery is commonly tens of gigabytes; uploading it somewhere just to choose a hundred frames would mean hours of waiting, a storage bill, and a copy of your wedding on someone else's server for as long as that company exists. Reading the folder locally removes all three problems at once.

It also sets the constraint the tool lives with: it needs a browser that can read a folder from your drive, which means a laptop or desktop running Chrome, Edge, Brave, Arc or Opera. See browser support for the details.

The free tool for the picking part

Shaadi Pic opens the wedding folder straight from your drive — nothing is uploaded, there is no account and there is no charge. Left arrow skips, right arrow keeps, Z undoes. Your keepers are copied into a /selected subfolder with filenames unchanged, ready to zip and send back.

Open your folder and start picking →
Free · runs locally · no sign-up · needs a laptop running Chrome, Edge, Brave, Arc or Opera

Frequently asked questions

Are my wedding photos uploaded anywhere?: No. The folder is read directly from your drive inside the browser using the File System Access API. There is no server that receives images, and you can confirm this by loading the page and then disconnecting from wi-fi — everything keeps working.
What is stored in my browser?: Two entries in IndexedDB: a handle for the last source folder and a handle for the last destination folder, so the resume function can reopen them. No image data is stored in the browser. Clearing site data removes both.
Does Shaadi Pic use cookies or analytics?: Neither. There are no cookies, no analytics scripts, no tracking pixels and no beacons. The web server keeps ordinary access logs, as every web server does, and those contain nothing about your photos.
Does anything third-party load on the page?: Two typefaces are loaded from Google Fonts, so Google sees your IP address and user agent when the page loads. That is the only third-party request. No photo data is involved.
What happens to my email if I join the iOS waitlist?: The address you type, along with which page you submitted from and a timestamp, is sent to the maintainer's notification channel so you can be told when the iOS app exists. Nothing else is sent, and you can ask for it to be deleted at any time.
Are my original photos modified?: No. Photos you keep are copied into a /selected subfolder with their filenames unchanged, and the originals stay exactly where they are. A small progress file is written into the folder so you can resume a session, and it can be deleted freely.