Egret

Privacy

What Egret does with personal information — both a studio's own, and that of the people in a studio's client list, which are two different things.

These terms are not in force yet. The company they would bind has not been set on this deployment, so what follows describes how the service works and is not yet an agreement with anyone. Nothing below has been reviewed by a lawyer.

1Two roles, and which one applies to you

If you run a studio here, the operator of this service is the controller of your account information: your name, your address, what you pay, and how you use the service.

If a photographer has your details in this system — you are their client, you sent them an enquiry, or your photographs are in one of their galleries — then they are the controller and we are only the processor. We hold that information on their instructions and do nothing else with it. To see it, correct it or have it deleted, ask the studio; they can do all three, and they can hand you a copy of everything they hold. If you cannot reach them, write to us and we will try to put you in touch.

2We collect user data. Here is exactly what

Every kind of personal information this software holds, why it is held, the basis for holding it, and how long it stays. Grouped by who you are, because that decides who answers for it.

If you run a studio here

We are the controller. Write to us.

  • The name and email address of everyone with a seat, the studio's own contact details, and its branding.

    To give the studio an account and let the right people into it.

    Basis Performance of the contract in the terms of service.

    Kept While the account is open, then deleted thirty days after it is closed.

  • The plan, subscription status and billing history. Card details are entered on Stripe's own pages and never reach this software.

    To charge for the service and to show what was charged.

    Basis Performance of the contract, and legal obligation for the tax record of a sale.

    Kept As long as the law requires a record of the transaction.

  • Sign-in attempts and whether each succeeded.

    It is what stops somebody walking a list of addresses to find which ones have accounts.

    Basis Legitimate interests in keeping accounts from being enumerated.

    Kept While the account is open.

  • Error reports: the route that broke and the studio's id. Never a name, never a request body, and access links are stripped out of the address first.

    So a fault is noticed and fixed rather than reported by the person it happened to.

    Basis Legitimate interests in a service that works.

    Kept The reporting provider's own retention period.

If you are a studio's client

Your photographer is the controller. Ask them.

  • Whatever the studio records: name, email address, phone number, venue addresses, the answers to their checklists, and messages either side has sent.

    It is the studio's client record. The software stores it on their behalf.

    Basis Held on the studio's instructions. They decide what is collected.

    Kept Until the studio deletes the client, the project, or closes the account.

  • The photographs, video and documents a studio delivers, and the files a client uploads to a checklist. Photographs carry whatever the camera recorded, including when the frame was taken.

    Delivering the work is what the product is for.

    Basis Held on the studio's instructions.

    Kept Until the studio deletes the gallery, the project or the account.

  • For a gallery a studio shares by invitation: the email address and name they invited, and when the gallery was last opened with it. The six-digit codes sent to that address are stored only as a one-way hash.

    So only the people a studio chose can open a gallery, without anybody having to make an account.

    Basis Held on the studio's instructions. They decide who is invited.

    Kept The invitation, until the studio removes it or deletes the gallery. Each code works for ten minutes and is deleted within a day of expiring.

  • Notes left on a film: the words, the moment in the film they are about, and the name of the invited guest or signed-in client who left them.

    So a studio can see exactly what a client wants changed, and where.

    Basis Held on the studio's instructions.

    Kept Until the studio deletes the film or the gallery.

  • The signing record on a contract: who signed, when, the wording they agreed to, their IP address and their browser's user agent.

    A signature nobody can evidence afterwards is not worth collecting. This is what makes it evidence.

    Basis Held on the studio's instructions, and the legitimate interest both sides have in a signature that holds up.

    Kept With the contract, until the studio deletes it.

If you sent a studio an enquiry

The studio you wrote to is the controller.

  • The name, email address, phone number and answers given on a studio's enquiry or booking form, where the sender said they heard of them, the address of the studio's own web page the form was filled in on, the page of that site the visit started on, the site it was reached from, and the campaign tags in the link they followed — utm_source, utm_medium, utm_campaign, utm_term, utm_content, and the click identifiers gclid, fbclid and msclkid. No other part of any web address is kept.

    So the studio can reply, so a repeat enquiry finds the same person rather than making a second record, and so the studio can see which of its pages, and which of its campaigns, an enquiry came from.

    Basis Held on the studio's instructions, at the request of the person filling in the form.

    Kept Until the studio deletes the lead or closes the account.

  • An anti-spam check on public forms sees the sender's IP address and browser signals at the moment of submitting. This software does not store either.

    It is what tells a person from a script on a form open to the whole internet.

    Basis Legitimate interests in not having the forms abused.

    Kept Not stored here at all. The provider keeps its own records.

  • When somebody at the studio has connected their Gmail: the subject line, time and direction of each email exchanged with a lead or client, and the address it was exchanged with. Not what the email said.

    So the studio can see on one page that a conversation is already under way.

    Basis Held on the studio's instructions, with the consent of the staff member who connected the mailbox.

    Kept Until the lead or client is deleted, or the mailbox connection is removed.

If you shoot for a studio

The studio is the controller.

  • The roster record: name, email address, phone number, biography, photograph, portfolio and tipping links, working days and time off. A studio's private notes about somebody are never shown to them.

    To schedule shoots and to credit the people on them.

    Basis Held on the studio's instructions.

    Kept Until the studio removes the record.

  • Only for somebody who connects a calendar: their shoot and consultation times, and the busy periods on their own calendar. Titles of other people's events are not read.

    So a shoot does not get booked over something already in the diary.

    Basis Consent, given by connecting it and withdrawn by disconnecting.

    Kept Until the calendar is disconnected.

  • Only for somebody who connects their Gmail: for each message to or from a person already in the studio's CRM, the subject line, the other person's address, whether it was sent or received, and when. Never the body or a preview — the permission asked of Google does not include them — and nothing at all about mail with anybody else.

    So an enquiry answered from the inbox does not look unanswered in the CRM.

    Basis Consent, given by connecting it and withdrawn by disconnecting.

    Kept Until the lead or client it is about is deleted, or the mailbox connection is removed.

If you opened a gallery link

The studio whose gallery it is, is the controller.

  • A random identifier and the name typed in, kept in one cookie for a year, so a heart or a comment has an author. It grants no access to anything.

    So a gallery can say who liked a photograph without asking anybody to make an account.

    Basis Consent, given by typing a name. Clearing the cookie ends it.

    Kept Until the cookie is cleared, or the studio deletes the gallery it was used on.

  • For a gallery shared by invitation, once a code is confirmed: a random token in a cookie for thirty days, readable only by that one gallery's address. We keep only a one-way hash of it, so the cookie cannot be recreated from anything we hold.

    So an invited guest confirms their address once per device rather than on every visit.

    Basis Strictly necessary to provide something that was asked for.

    Kept Thirty days, or until “Not you?” is pressed, or the studio removes the invitation — any of which ends it at once.

  • For a gallery with a PIN, the PIN itself in a cookie for twelve hours, readable only by that one gallery's address.

    So a PIN is typed once rather than on every photograph.

    Basis Strictly necessary to provide something that was asked for.

    Kept Twelve hours.

  • Where a studio has added our tracking line to their own website: the first page of it opened in this visit, the site it was reached from, and the campaign tags in the link. Held by the browser for that one tab, on the studio's own site, and read once — if and when a form on that site is submitted. It holds nothing that identifies anybody and it is never read on any other site.

    So an enquiry sent three pages later is credited to the page the visitor actually arrived on, rather than to whichever page happened to carry the form.

    Basis Held on the studio's instructions, on a website they operate. It is NOT strictly necessary — the form works without it — so where consent is required for it, that is the studio's to obtain, and we say so where they copy the line.

    Kept The length of the visit. The browser deletes it when the tab closes. Nothing is sent to us unless a form is submitted, and nothing at all is kept about somebody who does not send one.

If a studio emails you

The studio sending it is the controller.

  • Whether a message was delivered, and — for a studio's marketing campaigns only — whether it was opened and which link was clicked. Never for a sign-in link, a reminder or anything else transactional.

    So a studio can tell whether a campaign landed.

    Basis Held on the studio's instructions, in their legitimate interests.

    Kept Until the studio deletes the campaign or closes the account.

  • A record that somebody unsubscribed, which outlives the contact record it belonged to.

    Deleting the fact that a person opted out is how a person gets emailed again. This is the one record kept precisely so nothing else can undo it.

    Basis Legal obligation not to send marketing to somebody who has refused it.

    Kept Indefinitely, on purpose.

There is nothing else. No advertising network’s code runs here, no analytics package, no profiling, and no third party paying to be in this list. Where a campaign tag or a click identifier is recorded against an enquiry, it is the one that was already in the link the sender followed — nothing is asked of the advertising network it came from, and nothing is sent back to it.

3Who else sees it

These are our sub-processors. Marked ones are in use on this deployment; the rest are only used when a studio turns the feature on.

WhoWhat forWhat they see
Supabasein useThe database and sign-in system everything is stored in.Everything a studio records: clients, enquiries, projects, messages, email addresses and sign-in activity.
Vercelin useRuns the application and serves every page.Request metadata — IP address, browser, and the address of the page requested — in its operational logs.
Cloudflare R2in useStores uploaded photographs, video and documents.The files themselves. Uploads go from the browser straight to the bucket, so they do not pass through our servers.
Cloudflare Streamin useTurns uploaded films into video that plays smoothly on any screen.A copy of each uploaded video, fetched from the studio's own storage, and the IP address and browser of whoever watches it. The original file stays in storage; everything Stream holds can be made again.
Google Castin useSends a film to a television, only when a viewer presses the Cast button.The IP address and browser of the viewer who pressed Cast, and the address of the film they sent. Nothing is loaded from Google until that button is pressed.
Resendin useSends every email — sign-in links, reminders and campaigns.Recipient addresses and the content of the messages sent to them, plus whether each was delivered or opened.
StripeTakes subscription payments from studios.The studio's own billing details and card data. Cards are entered on Stripe's pages and never reach us. A studio's clients are not involved: nothing here bills them.
Cloudflare Turnstilein useTells a person from a script on public forms.IP address and browser signals at the moment a form is submitted.
SentryReports errors so they are noticed and fixed.Error messages and the shape of the page they happened on. URLs are stripped of names and access links before they are sent, request bodies are never sent, and it is not used to track anyone.
Google Calendarin useTwo-way calendar sync, only for crew who connect it.Shoot and consultation times for the person who connected it, and the busy times on their own calendar.
Gmailin useShows mail with known leads and clients on their timeline, only for crew who connect it.The subject line, addresses and time of mail between the connected mailbox and people already in the studio's CRM. Never a message body or preview, and nothing about anybody else.
Google Maps PlacesSuggests addresses while somebody types a venue.What is typed into an address field, as it is typed.

We do not sell personal information, and we do not share it for cross-context behavioural advertising — those two phrases have specific meanings under US state privacy law, and both answers are no. We have never done either, so there is nothing to opt out of. Nothing here profiles anybody or makes an automated decision about them.

4How long it is kept

Clause 2 gives the period for each kind of record. Over all of them sits one rule: a studio’s data is kept while its account is open, and when a studio closes its account everything is deleted thirty days later — including every file in storage. After that we keep only a record that the studio existed and was closed.

Within an open account, a studio decides: deleting a client, a project or a gallery deletes it, and the files with it. Unsubscribe records outlive the contact they belong to, for the reason given in clause 2.

5Where it is

The services in clause 3 operate internationally, so personal information may be processed outside the country you are in — in practice including the United States.

Where that is a transfer needing safeguards, the mechanism is the one in each provider’s own data processing agreement: the European Commission’s Standard Contractual Clauses, with the UK Addendum where the UK GDPR applies. We do not rely on any transfer mechanism of our own invention, and we do not move data anywhere a provider’s terms do not already cover.

6Security

Access is decided in the database itself rather than only in the application, so one studio cannot read another’s records even if the app is wrong. Files are served over links that expire. Sign-in is by emailed link, so there is no password to reuse or leak. Error reports have names and access links stripped out of them before they leave. None of that makes a system perfect, and if something does go wrong that affects you we will tell you.

7Your rights, and how to use them

You may ask to see the personal information held about you, to have it corrected, to have it deleted, to get a portable copy, to restrict what is done with it, and to object to processing based on legitimate interests. Where the basis is consent you can withdraw it at any time, and withdrawing it does not undo what was lawful beforehand.

For a studio’s own account, write to the address in the footer. We answer within one month, and will say so if a request is complex enough to need longer. There is no charge.

For anything a studio holds about you, ask that studio — clause 1 explains why they are the ones who can act. Studios can export everything they hold from Settings › Your data, and can delete any of it themselves. If a studio does not respond, write to us and we will try to put you in touch.

If you are in the UK or the EEA and you think we have got this wrong, you can complain to your data protection authority — the Information Commissioner’s Office in the UK — without asking us first. We would rather you told us too, but that is your choice and not a condition.

8If you are in the United States

Depending on your state you may have the right to know what is collected and why, to get a copy, to have it corrected or deleted, and to appeal a refusal. Clause 2 is the disclosure of what is collected; the rest is exercised the same way as clause 7, at the same address and at no cost.

We will not treat you differently for exercising any of it: no worse price, no reduced service, nothing withheld. As clause 3 says, there is no sale or sharing of personal information to opt out of, and this product contains no advertising.

9Children

This service is sold to businesses and is not directed at children, and we do not knowingly collect a child’s personal information for our own purposes. A studio’s own client list is a different matter — a family shoot contains photographs of children, and those are held on that studio’s instructions. They are the controller for them, as clause 1 sets out, and the consent to photograph and to share is theirs to hold.

10Cookies

Only ones that make the service work — no advertising, no analytics, nothing shared with anybody. The full list is here.