ShutterHostby Craig Turnbull Photography
← Back to home

Privacy Policy

Last updated November 2026

This policy explains what Shutter Host collects, why, and how it is handled. Shutter Host is a suite of tools built for photographers who run workshops and events: hosted apps accessed through the Hub (GearHost, CalcHost, MenuHost, BioHost, GearListHost, ShotListHost, CompHost, OnboardHost and EventHost) and WordPress plugins you install on your own site (Shutter Host Tours, Onboarding & Payments, Gear List, Photo Comp and Events). It covers EventHost (previously Shutter Host Events), our event app, on the web and on iOS, so attendees who open this policy from inside the app find themselves described here. It also covers CalcHost, our free Workshop Cost Calculator app on iOS, which links to this page from its menu, MenuHost, our Sony camera menu guide, in the Hub and as an iOS app, and CompHost, our giveaway and prize draw tool.

Two ways you use Shutter Host

Where your data lives depends on which you use:

What we collect

Your account. Your name and email address, a securely hashed version of your password (never the password itself), and the details you choose to give at sign-up (such as company, phone, country, website, and any note). We use these to create and secure your account. When you sign up with an email and password, we email you a single-use link to confirm the address is yours before you can subscribe; we keep only a scrambled (hashed) copy of that link, and it expires after 48 hours.

Billing. Subscriptions bought on the web, including the EventHost plan, are handled by Stripe. We store a Stripe customer reference and your subscription status; we do not store your card number; Stripe handles payment details directly. A GearHost subscription bought inside the iOS app is handled by Apple, and RevenueCat tells us whether that subscription is active; we receive the status, not your payment details. The MenuHost iOS app’s one-time unlock is also handled by Apple through RevenueCat, with no account (see below). The EventHost iOS app and CalcHost are both free and have nothing to buy inside them.

GearHost (hosted app). The gear, events/workshops, attendees and loan history you enter are stored on our servers so the app works across your devices and so check-in links function. This can include attendee names and contact details that you choose to add. We hold this to operate the tool for you; see “Attendee information” below.

EventHost (hosted app). EventHost runs multi-day events, so it holds the details an organiser needs to run one. Each organiser chooses which of these an event asks for, and an event that does not need a detail never holds it:

Organisers and administrators also have an account with us (name, email and password as above), and can add two-factor authentication to it. If an organiser uses the optional writing helpers, their own draft text is sent to Anthropic to produce a suggestion; attendee details are never sent to it.

EventHost on iOS. The app uses your device camera and photo library only to take or choose a photo you are sharing to the gallery or setting as your profile picture. Location is used only when you ask for it, to show where you are on the event map, and, if you tap to share a meeting point in the chat, to send those coordinates as a map pin in that conversation; we do not track your location in the background. If you turn on notifications, we store a device token so we can send them, and Apple’s push service receives that token and the notification’s title and body, which is the same short preview you see on your lock screen.

Sign in with Apple (mobile apps). When you use Sign in with Apple in the GearHost app, Apple provides your name and email address (which may be a private relay address that forwards to you) and a unique identifier for your Apple account. We use these only to create or access your account. In the EventHost app, Sign in with Apple is a way into an account you already have from your event invite, not a way to create a new one.

Camera (mobile apps). The GearHost app uses your device camera only to scan gear QR codes for checking kit in and out. Camera images are processed on your device and are not stored or sent to us. In EventHost, a photo is sent to us only when you share it to the event gallery or set it as your profile picture.

CalcHost, the workshop calculator (hosted app). Your calculator plans are end-to-end encrypted: they are encrypted in your browser with a key derived from your password before anything is sent to us, so we store only unreadable ciphertext and cannot see your figures. Because the key comes from your password, resetting or forgetting your password makes previously-saved plans unrecoverable.

CalcHost (the calculator on iOS). The app is self-contained: there is no account, it calls none of our servers, and it collects nothing. The plans you build stay in the app’s own storage on your device and are deleted with it if you delete the app, so keep a copy through the app’s Export if they matter to you. Nothing is sent to us unless you choose to send it, by using the support link in the menu.

MenuHost (the camera menu guide). In the Hub it is part of your subscription and stores nothing about you. The iOS app needs no account. It keeps, in your device’s Keychain only: the camera you picked as your free one (so it stays free after a reinstall), and, if you sign in with your Hub account, your Hub session and when the Hub last confirmed your access, so the app keeps working offline. That session is sent only to our Hub, to check your access; signing out removes it. The one-time unlock is bought from Apple, and RevenueCat confirms it to the app under an anonymous identifier, not your name or email. RevenueCat also notifies our server of it, which ignores it: the purchase is never linked to a Hub account. Searches and the cameras you look at never leave your device.

BioHost (your link-in-bio page). We store what you add to your page: your name, bio, location, photos, social links, links and workshops. Once you publish it, all of that is public at your biohost.link address, so only add what you are happy for anyone to see. Photos are re-encoded when you upload them, which removes hidden details such as GPS location and camera serial numbers. For your visitors, the page has no scripts, no cookies and no analytics, and we store nothing about who visits it: the only thing counted is how many times each link is clicked, as a plain number. If we have turned on event listing from Sony Scene for your account and you add your Sony Scene host page, our server reads that public page every few hours to list your upcoming events; it sends nothing about you or your visitors to Sony Scene. If you add YouTube videos to your page, we store a copy of each video’s picture, so your visitors’ browsers don’t contact YouTube when the page loads; YouTube’s privacy-enhanced player is only loaded when a visitor taps play, and from then on YouTube’s own privacy policy applies to that video. If you add your YouTube channel, our server reads the channel’s public video list from YouTube every hour to show your newest videos; it sends nothing about you or your visitors.

BioHost messages. If a BioHost owner turns on Send a message, visitors can write to them from the page. We keep the name, email address, topic and message the visitor sends, encrypted, for the owner to read in the Hub, and delete it after 90 days (sooner if the owner deletes it). We don’t keep anything about the visitor’s device or location. The owner gets an email saying a message has arrived; the message itself isn’t in that email. When the owner replies, they use their own email, and their reply is between them and the visitor.

BioHost subscriptions. If a BioHost owner turns on Subscribe, visitors can sign up by email for that page’s news: new workshops, new videos and updates from the owner. We keep the email address, first name (if given) and what they chose, encrypted, and only once they confirm by email; unconfirmed sign-ups are deleted after 7 days. Subscribers get at most one email a day, sent through Brevo, and every email has an unsubscribe link, which deletes their details straight away. The owner can see their subscribers’ email addresses and names, and download them. The Add these to your calendar link under workshops collects nothing at all.

BioHost contact and Wallet cards. If you add phone numbers to your page, they go in the Save contact file and on your Wallet cards, which anyone with your link can open, even if you choose not to show them on the page itself, so treat them as public. Your Apple Wallet card is made and signed on our server from what your page shows. When someone adds it to Apple Wallet, their device registers with us so the card can update itself: we keep a random identifier Apple Wallet gives that device and its push address, and nothing else about the person. When you change your page, Apple’s push service is sent an empty message telling those devices to fetch the new card. If you add your card to Google Wallet, we send Google what the card shows (your name, location, bio, links, phone numbers and the addresses of your photos) and Google keeps it; saving your page updates it there. We don’t learn who scans your card or saves your contact.

Support & feedback. If you contact us we keep your name, email, message, and basic context (such as the page or app version) so we can help.

CompHost (giveaways and prize draws). A host can run a giveaway or prize draw on a CompHost page. If you enter one, we store for that host the details their entry form asks for: your name and email address, and, where they ask, your Instagram handle, a phone number, an answer to their question and whether you ticked the box to hear from them, plus when you entered. The host is the promoter: they decide what is asked and what the terms are, and they see their own comp’s entries and no one else’s. We use entries only to run that draw. The winners are picked at random by our server, and we keep a record of each draw (when it ran, how many entries were in it and which entry numbers came up). A confirmed winner is emailed for the host, and their reply goes to the host. If you ticked the box to hear from a host, they can download your name and email address, and where the host uses BioHost you may be sent one email asking you to confirm, after which you are one of that page’s subscribers (see BioHost above) until you unsubscribe; nothing else about an entry is ever exported, and nothing is passed to anyone else. Entries that didn’t win are deleted 30 days after a comp closes, and a winner’s entry a little over a year after the win; the host can delete them sooner, and you can ask the host, or us, to remove yours. When the prize is a free year of the Shutter Host Hub, the winner’s name and email address also become their Hub account.

Technical data. When you use our hosted apps, including the GearHost mobile app and the EventHost app, our servers keep standard logs (such as IP address, from which an approximate location can be derived, device or browser type, and timestamps) used only for security, abuse prevention and keeping the service reliable. Downloading an attendee list from EventHost is also recorded (who did it, when, from where, and how many records) so there is always an answer to where a copy of the data went. Our apps (the Hub and its tools: GearHost, CalcHost, MenuHost, BioHost, GearListHost, ShotListHost, CompHost, OnboardHost and EventHost, including the GearHost mobile app on iOS and Android and the EventHost app on iOS) do not include third-party advertising or analytics trackers, and we do not track you across other companies’ apps or websites.

Our marketing website. The public website at shutterhost.com.au, which is separate from the apps, uses two measurement tags. Google Analytics tells us how many people visit, which pages they read and which buttons they press, so we can improve the site. The Meta Pixel tells Meta (Facebook and Instagram) which pages of the website you visit, so we can see whether our ads on those platforms work and show them to people likely to be interested. Both set cookies in your browser and send Google and Meta the page you are on, your IP address and browser details, and Meta may link this to a Facebook or Instagram account you are signed in to. Neither is used in the Hub or any of our apps. You can block them with your browser’s privacy settings or a content blocker, opt out of Google Analytics with Google’s browser add-on, and control the ads Meta shows you in your Facebook or Instagram ad preferences.

How we use it

We use your information to provide, operate, secure and improve Shutter Host, to take payment, and to respond to you. In EventHost we use it to run the event you are part of: to show the schedule and who is coming, to allocate session places, to deliver chat and the gallery, to tell an organiser about catering needs or a medical contact when they have turned those on, and to send you the notifications you have asked for. We do not sell your personal information or your attendees’ details, and we do not use your gear, event, attendee or calculator content for marketing or to train anyone’s AI models.

Who we share it with

We share data only with the service providers needed to run the platform, and only as needed to provide the service, or where required by law. We do not sell your data. Those providers are:

These providers keep their own copies for their own retention periods (for example Brevo’s email delivery logs), which is worth knowing when you ask us to delete something.

Where your data is stored

Our apps and their databases run in Railway’s Singapore region (Southeast Asia), the closest region our host offers to Australia, and object storage sits in its own configured region. For an Australian customer this means personal information, including your attendees’ details, is stored offshore, which is a cross-border disclosure to weigh under Australian Privacy Principle 8. If your organisation requires personal information to stay in Australia, tell us before you run an event: our current host cannot meet that.

Storage & security

Data is stored on managed cloud infrastructure and protected in transit with HTTPS. Passwords are hashed with bcrypt and sessions use a signed, httpOnly token. CalcHost plans are end-to-end encrypted as described above.

In EventHost the sensitive fields are additionally encrypted in the database with AES-256-GCM, on top of our host’s own storage encryption: phone numbers, emergency contacts, dietary needs and allergies, flight numbers, accommodation details and travel notes, and the secrets the app must store but never show. Access is checked on our servers for each record, and every query is scoped to the event that owns it, so one event’s data is never reachable from another. Direct messages are visible only to the two people in them, our staff included. Uploaded images, photographs of people included, are served only through signed, time-limited links rather than a guessable path. Organisers and administrators can add two-factor authentication (an authenticator app) to their accounts. A sponsor invited as a guest sees only the schedule, the gallery and sponsor placement, never the attendee directory or the chat.

No method of transmission or storage is completely secure, but we take reasonable steps to protect your information.

Retention & deletion

GearListHost (your gear list). We store the gear you add (names, brands, descriptions, tags, product links and photos) and a plain count of taps on each product link, with nothing about who tapped. Photos are re-encoded with their location and camera details removed. While you have My gear turned on for a published BioHost page, the items you haven’t hidden are public there. Everything is deleted when you remove it or delete your account, and nothing is sent to any other service.

ShotListHost (shot lists). We store your shot lists: their name, date and notes, and each shot, including the names of the people in group photos that you or your helper type in. If you make a helper link, anyone holding it can see and change the sections you chose to share, with no account; they never see your other sections, your notes or your email. We store nothing about the helper: a ticked shot only records that it was ticked by you or by your helper, and when. The link is a long random key we keep encrypted, and it stops working when you turn it off or make a new one, two weeks after the shoot date, or if your subscription ends. If you save a list as your own template, we keep its sections and shots (with their notes) until you delete the template, but not the names typed into group photos, the list’s notes or, if you give them, the couple’s names. Nothing in your lists is sent to any other service.

OnboardHost (client onboarding and payments). A host stores their events, their bank details (shown to their own clients so they can pay), optionally their logo and a colour for their client emails and links (the logo is public at an address only those emails and links carry, and is the same for every client, so it can’t show who opened an email), and their clients’ names and email addresses, with each client’s room type (single or twin), whether they have an early-bird discount, and their deposit and when it was paid. Through their personal link, each client hands in a signed waiver (the wording they agreed to, a drawn signature and when they signed), whether behind-the-scenes photos of them may be used, a pre-event form (the gear they’re bringing, any dietary or access needs, an emergency contact and phone number, and their experience level) and the bank transfers they report. Payments are made by bank transfer straight to the host; we never handle the money or any card or bank login, and a payment only counts once the host confirms it arrived. A client’s link is a long random key we keep encrypted. It shows only that client’s own booking, and stops working 30 days after the event, when the host makes a new one or removes the client, or if the host’s subscription ends. Everything for an event, waivers, forms and payment records included, is deleted 12 months after the event date, or sooner if the host deletes it or their account. If the host runs the event in EventHost and adds its event code, a client’s link shows that code (and how to join) only once they’ve paid all or part of their balance. Reports of an event or of payments are made on the host’s own device from their own account, and nothing about them is stored or sent anywhere else; the same goes for bringing payments into CalcHost, which happens inside the calculator, so its plans stay end-to-end encrypted. The host invites their clients and is responsible for how they use what their clients hand in; clients can ask the host, or us, to access, correct or delete it.

We keep your account data while your account is active. You can request access to, correction of, or deletion of your information at any time by emailing hello@shutterhost.com.au. Deleting your account removes the data associated with it, including your gear/event records and your encrypted calculator data.

EventHost keeps an event’s data only as long as the event needs it. An organiser sets a retention window of 1 to 365 days after the event’s end date, and once it passes an automatic sweep permanently deletes the event and everything in it: profiles, emergency contacts, dietary notes, chat, sign-ups and the photo files themselves, not just their database rows. Participants can see that deletion date in the app. If an organiser sets no window, the data is kept until they delete the event by hand. An account left holding no event membership is removed automatically, and the record of who exported an attendee list is kept for 2 years and then aged out.

BioHost pages are deleted 3 months after your subscription ends. When your Hub subscription ends, your bio page stops being shown straight away and we email you the date it will be deleted. We email again two weeks before that date. Subscribe again before then and it comes back as it was; otherwise the page, its links and its photos are permanently deleted and the address is freed. You can also delete your page yourself at any time from the editor. A device’s Wallet registration is removed when the card is taken out of that Wallet, or with the page. Before a page is deleted, its Google Wallet card is marked expired; Google offers no way to delete it outright, so it keeps that expired copy under its own policy.

Shot lists are deleted 12 months after the shoot date. An automatic sweep permanently deletes each list, with every shot and name in it, 12 months after the date of the shoot, and the list shows that date. Lists without a date are kept until you delete them, and you can delete any list yourself at any time.

Asking to be deleted from an event. In EventHost you can delete your own account from inside the app, confirmed with your password, which removes your profile and membership in every event and the photos you uploaded. An organiser can also remove you from each event they run, which drops that membership and, once you hold none, your account. Chat messages stay in the conversation with your name detached, so the threads other people are part of are not torn apart. You can also email us and we will action it for you.

An honest limit. Our database host keeps its own automated backups on its own schedule. A deletion removes the live data straight away, but a copy can persist in those backups until they age out, and the providers listed above keep their own copies for their own periods.

Attendee information

When you add attendees in GearHost, or run an event in EventHost, you decide what the event asks for and you are responsible for having a lawful basis to collect it. We process that information on your behalf, only to provide the tool, and delete it when you delete the related records, when the event’s retention window passes, or when you delete your account.

If you are an attendee: EventHost shows a short notice explaining what a detail is for at the point you enter it, and links to this policy from inside the app. The organiser running your event decides which details it asks for, and you can leave optional directory fields hidden from other attendees. To ask for access to your information or to have it deleted, speak to your organiser or email us at hello@shutterhost.com.au.

Your rights

Depending on where you live, you may have rights to access, correct, delete, or restrict the use of your personal information, and to complain to a regulator. To exercise any of these, email hello@shutterhost.com.au.

Changes to this policy

We may update this policy as the service changes. We will revise the date above when we do.

Contact

Questions about this policy or your data? Reach us at hello@shutterhost.com.au.