Last updated 8 October 2026

Privacy policy

SaltBrite is a site where models, photographers, studios, stylists and makeup artists put up a profile and a set of photos so that other people can find them. Most of what you give us is there to be seen. This page says what we collect, what we do with it, who else touches it, and what you can ask us to do. It's written in plain English on purpose. If anything is unclear, ask us.

SaltBrite is the data controller for the personal data described here. You can reach us through the contact form or at hello@saltbrite.com.

Who this site is for

You must be 18 or over to have an account. Everyone shown in a photo on SaltBrite must be 18 or over too. We don't knowingly hold data about anyone younger, and if we find an account that belongs to someone under 18 we'll remove it. If you think that has happened, tell us.

What we collect when you join

The join form asks for a username, an email address, a password and what kind of member you are. We store the password as a hash, never the password itself, and we can't read it back. To check the email address we send a six-digit code; we keep a hash of that code for fifteen minutes and count how many times it's tried. We also record when the account was made and when the address was verified.

The join form and the contact form carry Cloudflare Turnstile, which tells people from scripts. Cloudflare sees your IP address and some details about your browser to do that. Its own privacy policy covers what it keeps.

Signing in with Google

If you join or log in with Google, Google sends us the id of your Google account, your email address, whether Google has verified that address, and your name. We store the id, so that your next Google sign-in finds your account, and the email. The name is only used to suggest a username, and we never see your Google password. If the email already belongs to a SaltBrite account and Google has verified it, that account is linked to your Google account and you're signed in. Google's own privacy policy covers what Google records about the sign-in.

What we collect for your profile

Your profile is what the site is for, and almost all of it is meant to be public once your profile has been approved. That includes your display name, the town you're based in, your bio, your website and Instagram links, and the details that go with your member type: what work you want or what you shoot, your experience, how you like to be paid, whether you'll travel. Studios give a contact name and a phone number, and the phone number is shown on the studio's page. Models give a date of birth; we show the age we work out from it, never the date itself.

Models can also give their height, weight and measurements, cup size, hair and eye colour, skin tone and ethnicity, and whatever is filled in shows on the public profile. Ethnicity is what UK data protection law calls special category data. We hold it only because you choose to put it on your public profile, and you can take it off again at any time on the edit page. It's optional. Every one of these fields can be left blank.

When you pick your town we look it up through Google's Places service. We keep the place name, the country, the coordinates and Google's place ID so that members can search by distance. Google sees the text you type into that box. We don't store a street address for anyone.

Members who are signed in can search profiles: by town and distance, by name, and by the details shown on a profile, such as the work you do, your experience and, for models, age, height, weight, measurements, cup size, hair and eye colour, skin tone and ethnicity. A detail you leave blank is never matched, and taking one off your profile takes you out of searches for it.

Photos

You can upload up to fifty photos, plus a separate avatar. For each photo we make several resized copies for the site and we keep the file you uploaded, unchanged, in private storage that nothing links to. That original may carry metadata from your camera or phone, including the place it was taken if location was on. We strip that metadata from every copy that is shown on the site, but it stays in the kept original. We keep the original so that a crop tool can start from the full-quality file rather than a resized one.

Public copies are served from our photo domain, sltbrt.com, through Cloudflare, at addresses that can't be guessed. Once your profile is approved, anyone with the address can open a photo, and anyone can find it through your profile. Photos marked as containing nudity are shown behind a warning and are never used as your main photo, your avatar, in share previews or on the home page.

When you delete a photo we delete our copies straight away. Copies that Cloudflare's edge or someone's browser has cached can survive for up to a year after that, because the files are sent with a one-year cache header. A photo that someone has saved to their own computer is beyond our reach.

What you do on the site

We record the photos you love, the comments you write, and the reports you make about photos and comments. We keep the lists of profiles and photos you bookmark, and only you can see them. A comment you delete is hidden rather than wiped, so that a report about it can still be read. We count how many times each photo page is opened; that count is a number on the photo, not a record of who opened it.

Messages

Messages between members are stored on our servers so that both of you can read them, with who sent each one and when, and when each of you last read the conversation. We also store who you've blocked and which conversations you've muted. A message you delete is hidden from both of you but kept, so that a report about it can still be read. Nobody at SaltBrite reads your conversations. The one exception is a message someone reports: the person who handles the report reads that message.

If you turn on notifications, we store the address your browser gave us for them, with the keys that encrypt them. The notification goes through your browser's push service (Google for Chrome and Edge, Mozilla for Firefox, Apple for Safari), which can't read it because it's encrypted. It says who wrote to you, never what they said. Turning notifications off on the settings page, or in your browser, removes that address.

Every profile is checked by a person before it goes public, and we record who approved it and when. If an account is suspended we record when, by whom and the reason. The reason is not shown to the member or to anyone else outside the admin section.

Reviews

Members can write a review of another member they've worked with: whether they'd recommend them, and their own words. A review is public on the reviewed member's profile under the writer's username, so anyone can read it. The reviewed member can reply publicly and can report a review, but can't take it down. We can hide a review that breaks the rules, and only admins see why.

If you delete a review you wrote, it comes off the site straight away, but we keep the text so that a report about it can still be looked into. We email a member when someone reviews them, and email the writer when the reviewed member first replies.

The contact form

A message sent through the contact form is stored with the name and email address you gave (or, if you were signed in, the ones on your account), the topic, the message itself, when it was sent and the IP address it came from. The IP address is there so that we can deal with abuse; we keep it for 90 days. The message is also emailed to us so that we can reply, and that email goes through our hosting provider's mail server.

Emails we send

We email you a verification code when you join or change your address, we email you when your profile is approved, suspended or unsuspended, and, unless you turn it off, we email you when a message has been waiting unread for fifteen minutes (it names who wrote, not what they said). Those go through Mailjet, which sees your email address, your username and the link to your profile. We don't send newsletters or marketing email, and we won't without asking first.

Cookies and analytics

The site sets a cookie to keep you signed in, one to protect its forms, and one if you switch between metric and imperial units. The live site also runs Google Analytics regardless of your answer to the cookie banner, which sets its own cookies and sends Google a record of the pages people open, with your IP address shortened so that it doesn't identify you. The cookie policy lists every one, with how long it lasts.

The fonts come from Google Fonts, so Google's servers see your IP address when a page loads. No cookie is set for that.

Why we're allowed to do this

UK data protection law asks us to say which legal basis covers each thing we do with your data.

• Running your account, showing your profile and photos, carrying messages between members and telling you about new ones, sending verification codes, and answering your messages to us: we do this because you've asked us to, which the law calls performance of a contract.
• Checking profiles before they go public, dealing with reports, keeping a suspension record, stopping spam with Turnstile and rate limits, and keeping the IP address on contact messages: our legitimate interest in running a safe site that people can trust.
• Analytics: our legitimate interest in knowing which pages get used, using data that doesn't identify you.
• Ethnicity on a model's profile: you put it there yourself, on a page you chose to make public, and you can take it off whenever you like.

Who else sees your data

We don't sell data and we don't share it with advertisers. These companies handle it on our behalf, each for one job:

• SmarterASP.NET hosts the site, its database and the mail server for contact form notifications.
• Cloudflare stores and serves the photo files, and runs the Turnstile check on the join and contact forms.
• Google provides the Places lookup for your town, the fonts, the analytics, and sign-in for members who choose it.
• Mailjet, part of Sinch, sends the verification, moderation and new-message emails.
• If you turn on notifications, your browser's push service (Google, Mozilla or Apple) delivers them, encrypted.

Some of these companies process data outside the UK. Where they do, we rely on the safeguards written into their contracts for UK customers.

Beyond that, your public profile is public. Search engines can index it, and we list approved profiles in the site's sitemap so that they do. Anyone can see your public profile, your photos, your comments, and the count of loves on a photo. Nobody but you and site admins can see your email address or your date of birth.

We'll hand data to the police or a court if the law requires it.

How long we keep things

Your account and everything on it stays for as long as you keep the account. There isn't a delete-my-account button yet; send us a message and we'll close the account and delete its data by hand. Messages between members stay until the account is closed. Contact form messages are kept so that we have a record of what was said; the IP address on them goes after 90 days. Verification codes expire after fifteen minutes. An account that never verifies its email address may be removed without notice.

Your rights

You can ask us for a copy of the data we hold about you, ask us to correct it, ask us to delete it, ask us to stop using it in a particular way, or ask for it in a form you can take elsewhere. Most of your profile you can change or remove yourself on the edit pages. For anything else, use the contact form and say what you'd like done. We'll answer within a month.

If you think we've handled your data badly, you can complain to the Information Commissioner's Office at ico.org.uk. We'd rather you told us first so that we can put it right.

Security

Passwords are hashed. Original photo files sit in storage that nothing public links to. Admin pages need a role that only the site's owners hold. Photo addresses can't be guessed. None of that makes a site unbreakable, and if there is ever a breach that puts you at risk we'll tell you and the ICO.

Changes to this policy

We'll change this page when the site changes. The date at the top says when. If a change matters to you, such as a new use of your data, we'll tell members by email before it happens.