Privacy

Last updated 5 October 2026

SeatThree is a private archive for fashion reference images. This page says plainly what we store, who processes it for us, and how to get it removed. SeatThree is run by Sainted Ltd in the United Kingdom; write to rob@withsainted.com about anything here.

If you ask to join

When you request access, on seatthree.com or on the app’s sign-in page, we keep your name and email address, whatever you entered for Instagram, job title and company, and a hashed record of the network address it came from, so we can recognise repeat requests. We use it only to decide whether to invite you; an invitation comes by email. A request we decline stays on our list so we recognise it if it comes again; email us and we remove it.

Your account

SeatThree has no passwords. You sign in with Google, or with a six-digit code we email you. We store your email address, your name if Google gives it to us, when you last signed in, and a signed session cookie in your browser. Codes are stored only as one-way hashes and expire after ten minutes. Your browser may also remember which sign-in method you used last time; that never leaves your device.

Your images and notes

Everything you upload is yours. We store the original file, smaller previews, your notes, tags and collections, and we keep it private to your account. Nothing in SeatThree is public and there is no feed. No other member can see your archive unless you share a collection with them: they can then see the images in that collection, their titles and their automatic descriptions, and download them, but not your notes, tags, sources or any other collection. You can stop a share at any time. We take no licence to your images beyond what is needed to store, display and search them for you.

Pictures saved from Vogue Runway are kept differently, because a runway look is the same public picture for everyone who saves it. We keep a shared copy of the file, its previews and its automatic description, and a member who saves that look gets their own record of it, which in most cases points at the shared copy instead of holding a file of its own. Your record is yours alone: your notes, tags and collections, when you saved it, and the fact that you saved it at all are kept with your account and shown to nobody else, and no member can find out who else has saved a look. If you replace, crop or enhance one of these pictures, you get a copy of your own and the shared one stays as it was.

To make your archive searchable, each image is described automatically. A reduced-size preview of the image is sent to Google’s Gemini model through Google Cloud, which returns a written description of the garments, colours, materials and setting it can see. Under Google Cloud’s terms that content is not used to train Google’s models. The description is stored with your image and marked as automatic and unverified. It is shown only to you, and to anyone you share a collection with. Search also uses a numerical summary of each description, produced and stored on Cloudflare’s infrastructure.

One action leaves your archive only when you ask for it. “Enhance picture” sends that picture, and nothing else (no title, notes, labels or sources), to Google Cloud’s web detection, which looks for a larger copy and the pages it appears on; the same Google Cloud terms apply, and the app tells you what it sends before you press the button. Nothing else in SeatThree looks anything up on the web.

The browser extension

The Chrome extension saves a picture into your archive without leaving the page you are on. It reads the one image you right-click, and sends it to SeatThree signed in as you, together with the address of the page it was on. When the site will not let the extension read the file itself, it sends the image’s web address instead and SeatThree fetches it once; from version 1.3 a picture on Vogue Runway is sent that way whenever SeatThree can fetch it. That is the whole of what it sends, except what the next paragraph says of a board you ask it to save.

With two exceptions, it cannot read the pages you visit. It has no permission to see your tabs, your history or anything you type, and outside vogue.com and pinterest.com it runs no code in any page. The first exception, from version 1.1, is Vogue Runway: there the extension runs a small script that waits for the space bar and, only if you have turned that setting on in the extension, saves the look you are viewing and shows what happened in a panel in the corner of the page. The script reads the address of that one picture and nothing else on the page, and it does nothing while the setting is off. The second, from version 1.4, is Pinterest: on a board you open, the extension can save that board’s pictures into your archive, but only when you ask it to. It then sends SeatThree the pictures’ addresses, the address of each pin, the pin’s own link and title, and the board’s name, and nothing else; it reads no other page of Pinterest’s, and nothing you remove on Pinterest is ever removed from your archive. Chrome lists what the extension asks for as the right-click menu item, local storage, reading and changing vogue.com and pinterest.com, and the ability to talk to app.seatthree.com. It contacts nothing else and has no analytics. Its toolbar menu shows which SeatThree account you are signed in to, which it asks SeatThree for each time and does not keep. On your own computer it keeps the last save, so it can show you what happened to it, your list of collections for a minute so it does not ask again for every picture, and whether the space bar setting is on. Removing the extension removes all three.

Who processes data for us

• Cloudflare hosts the application, stores your files and database in Western Europe, and runs the bot check on our forms. It also counts visits to seatthree.com for us with Cloudflare Web Analytics, which sets no cookie, keeps no address or identifier for you, and tells us only which pages were opened, from which country, and how fast they loaded.
• Google Cloud generates the automatic descriptions and, only when you press “Enhance picture”, looks a picture up on the web, as above; it also handles Google sign-in if you use it.
• Resend sends our email: sign-in codes, invitations and notifications.
• Stripe processes payments for the paid plans. Card details go to Stripe, never to us.

We do not sell data, run advertising trackers, or share your archive with anyone.

Deleting things

An image you delete moves to Trash, where you can restore it for thirty days. After that the original, its previews, its description and its search entries are permanently removed. A picture saved from Vogue Runway is the exception: deleting it removes your record of it, with your copy of its description and your search entries, and leaves the shared copy of the picture, which is not yours alone. You can download any original at any time. To close your account and remove everything, email us from the address you signed up with; we will confirm when it is done.

Your rights

Under UK data protection law you can ask what we hold about you, have it corrected or deleted, and object to how it is used. Email rob@withsainted.com. You can also complain to the Information Commissioner’s Office.

Changes

If this page changes in a way that matters, we will say so here and, for members, by email.

5 October 2026: pictures saved from Vogue Runway are now kept once and shared between the members who save them, as described under “Your images and notes”.

5 October 2026: “The browser extension” now describes what versions 1.1 to 1.3 do on Vogue Runway.

7 October 2026: “The browser extension” now describes what version 1.4 does on Pinterest boards you open.