Privacy Policy

Effective 21 August 2026. Revised 28 September 2026.

Salt & Gorse Ltd ("Storybrdr", "we", "us" or "our") is a company registered in England and Wales under company number 15581747, with its registered office at Bosnoweth, Higher Argal, Budock Water, Cornwall TR11 5PE.

We operate Storybrdr (the "Service") through our website, web application and iOS app.

This Privacy Policy explains how we collect, use and protect personal data, when we act as a controller or processor, and your rights under the UK GDPR.

1. Our role under data protection law

Our role depends on the personal data being processed.

Account and Service data

We are the controller of personal data used to provide and operate your Storybrdr account. This includes your name, email address, sign-in information, billing information and the technical records needed to operate and secure the Service.

Customer Content

For the content you add to Storybrdr, including Projects, Boards, uploaded images, notes and personal data relating to anyone appearing in an image you upload, you are the controller and we act as your processor.

We process Customer Content on your instructions to provide the Service. This includes storing and displaying it, generating thumbnails, producing exports you request and making shared Boards available to people with whom you choose to share them.

Our obligations when acting as your processor are set out in our Data Processing Addendum, which forms part of our contract with you.

There are limited circumstances in which we process information contained in Customer Content for purposes that we determine ourselves. These include the mandatory safety check and reviewing content that has been flagged or reported. Where we determine the purpose and means of that processing, we act as controller as described in this Privacy Policy.

Safety check

We automatically check every uploaded image for material that may be unlawful to host on the Service.

We determine the purpose of this processing, what the check looks for and what happens when content is flagged. The check is mandatory and cannot be disabled.

We therefore act as the controller for the safety check, and only for that processing.

Descriptive tagging

Descriptive tagging is processing carried out on your behalf. It processes Customer Content for your benefit as a feature of the Service and enables images to be found by searching your Library.

You can ask us to remove descriptive tags at any time, as explained below.

If someone appearing in an image you have uploaded makes a request concerning the image itself, you remain the controller and we will assist you in responding. For personal data created or processed as part of our safety check, we are the controller.

Members of a workspace

If you are invited into a workspace that belongs to another Storybrdr customer, both roles apply at once and cover different things.

Your account is yours. Your name, email address, password, profile photo and job title are held by us as controller. They follow you to any other workspace you join, and you can change or delete them without asking anyone.

What you do inside that workspace belongs to the customer who owns it: the Boards you edit, the comments you leave, the approvals you give and the record that you are a member. For all of that the customer is the controller and we are their processor. Your name and profile photo appear beside your comments and approvals to people reviewing a Board through a Share Link. Your job title is shown inside the workspace only.

Invitations

Before an invited person joins, the invitation is processed on behalf of the customer who sent it. The customer chooses whom to invite and the role to offer, and is the controller for that invitation data. We act as the customer's processor in sending and managing the invitation.

If the invited person accepts and joins Storybrdr, we become the controller for the personal data used to provide and operate their own Storybrdr account, as described under Account and Service data above. The customer remains the controller for the person's membership and activity within that customer's workspace, as described under Members of a workspace.

2. Personal data we collect and how we use it

Account data

Data: Name, email address, password, and a profile photo and job title if you choose to add them. If you use Google to sign in, we also receive a Google account identifier.

Passwords are stored only as irreversible hashes.

Purpose: To create, authenticate and provide your Storybrdr account.

Lawful basis: Performance of our contract with you.

Customer Content

Data: Projects, Boards, images, notes and other content you create or upload.

Purpose: To provide the Service and the features you choose to use.

We process Customer Content as your processor, on your instructions and under our contract with you. The safety check and other limited processing for which Storybrdr acts as controller are described separately in this Privacy Policy.

Customer Content is private to you and the people with whom you choose to share it. A person at Storybrdr accesses it only where necessary to provide support at your request, comply with a legal requirement, review content flagged by the safety check, or review content someone has reported.

Billing data

Data: Your subscription plan and status and your country for VAT purposes.

The card form on our payment page is provided by Stripe. Card details are entered into Stripe's own fields and sent directly to Stripe, so Storybrdr does not receive or store your full card details.

Purpose: To manage subscriptions, payments, invoicing and our accounting and tax obligations.

Lawful basis: Performance of our contract with you and compliance with our legal obligations.

Guest data

Data: The name a guest provides when commenting on or approving a Board through a Share Link, together with the comment or approval.

Purpose: To provide the sharing, commenting and approval features requested by the Storybrdr customer.

This forms part of the customer's Customer Content. The customer is the controller and we process it on the customer's behalf, except where a comment is reported to Storybrdr as described in section 6.

Member data

Data: Who is in a workspace, the role each person holds (owner, admin or member), when they joined, and the log of every change to that list showing who made the change, who it concerned and when.

Purpose: To provide the workspace to the customer who owns it and to count the people in it against the seats their plan allows.

This is the customer's record of their own team. The customer is the controller and we process it on the customer's behalf. Counting seats is performance of our contract with the customer.

Invitation data

Data: An email address typed by a workspace owner or admin to invite a colleague, the role offered, who sent the invitation and when it was sent or resent.

Purpose: To send the invitation requested by the customer and hold it until it is accepted, declined, withdrawn or expires.

The customer is the controller for this invitation data and we process it on the customer's behalf. The inviter's name and email address appear in the invitation, and the invitation itself explains what we hold and how to decline.

If the invitation is accepted, the invited person's Storybrdr account data is then processed by us as controller as described under Account data. Their membership and activity within the customer's workspace continue to be processed on behalf of that customer.

Technical data

Data: IP address, browser or device type, device model where provided by the iOS app, error reports, security logs and an approximate location derived from an IP address for security notices.

Purpose: To maintain the security of the Service, prevent fraud, provide security information about sign-ins, and diagnose and fix faults.

Lawful basis: Our legitimate interests in operating a secure and reliable Service.

Error reports are scrubbed of Customer Content, passwords and other sensitive request information before they are sent to our error-monitoring provider.

First-party usage data

We maintain a limited first-party record of certain actions taken through a Storybrdr account. These include:

• creating an account;
• signing in;
• creating a Board;
• adding frames;
• sharing a link;
• exporting a PDF;
• starting a Board version;
• using the moodboard;
• importing a script;
• using On Set;
• reaching the payment page, including the plan and billing cadence selected;
• starting a trial;
• a trial becoming a paid subscription;
• cancelling a subscription, including whether it ended or was set to end at the end of the billing period; and
• a comment being received on a Board you shared.

For comments, we record only that a comment arrived for your account. We do not retain usage data about the guest.

Each usage entry contains the date, the action and, where relevant, a count or type, such as the number of frames, type of link or layout. It never contains the content of your work.

When an account is created, we also record which of our pages you first arrived on, the page that referred you, any campaign or invitation tag contained in the link and the name of the referring website. We record the referring website address, not the particular page you were viewing on that website.

These records are created by our own server within the Service. We do not use an analytics script, analytics cookie or third-party analytics provider for this processing.

Menu and feature choices

We also record which menu options are chosen, so we can understand how the product is being used and improve it. These choices are recorded at workspace level rather than against individual members. We don't record who selected an option, the content they were working on, their device or browser (only whether it was our website or app, and a rough screen size), or their activity on other websites.

We don't use a third-party analytics service for this information. Menu choices are kept for 13 months and then automatically deleted. We don't sell this information, share it with advertisers, use it for advertising, or use it to build profiles of individual users.

Purpose: To understand how Storybrdr is being used, identify where new accounts encounter difficulties and improve the Service. For trial accounts that appear to have stalled, we may review this information at account level so that we can offer relevant help.

Lawful basis: Our legitimate interests in understanding and improving Storybrdr and supporting customers who are trying the Service.

Usage data is otherwise reviewed in aggregate. It is retained while your account exists (menu choices are deleted after 13 months) and deleted with your account. We do not use advertising or cross-site trackers for this purpose.

Public website measurement

On the public Storybrdr website, but not within the Storybrdr app, our hosting provider records page views and two specific interactions: starting a trial and joining the product-updates list. It also records the referring page.

This measurement does not set a cookie and does not use an identifier that follows you between websites.

Purpose: To understand which parts of our public website are useful and worth developing.

Lawful basis: Our legitimate interests in understanding and improving our website.

Cancellation feedback

If you choose to answer the optional question presented when cancelling, we record the reason you select and anything you write.

Purpose: To understand why customers leave and improve Storybrdr.

Lawful basis: Our legitimate interests in improving the Service.

Cancellation feedback is read by the founder, retained while your account exists and deleted with your account.

Support correspondence

Data: Emails and other information you send us when requesting support.

Purpose: To respond to and manage your request.

Lawful basis: Our legitimate interests in providing customer support.

Product-updates list

Data: Your email address, when and how you joined the list, the page or link through which you joined and the exact consent wording shown to you at the time.

Purpose: To send the product-update emails you have requested.

Lawful basis: Your consent.

Joining the product-updates list is optional and is not required to use Storybrdr. You can unsubscribe at any time.

We do not sell personal data, use third-party advertising trackers or use Customer Content to train AI models.

3. Emails and communications

Product updates

The product-updates list is separate from your Storybrdr account.

If you provide your email address through our website to receive product updates, we record your email address, the date you joined, the page on which you joined, the referring link where applicable and the exact consent wording shown to you. This allows us to maintain a record of the consent you gave.

We do not store your IP address with your subscription. A hashed form of it is held for up to a day to limit abuse of the form, then deleted. We do not place a cookie or other information on your device to track where you came from.

After joining, you receive one welcome email confirming your subscription. We then send occasional product updates.

Every product-update email contains an unsubscribe link. You can also manage your subscription through a preferences page operated by our email provider.

If you unsubscribe, we retain a minimal suppression record consisting of your email address and relevant dates. We use this only to ensure that you are not emailed or inadvertently added to the list again.

If the same email address is subsequently entered on our website, this does not automatically resubscribe it. We may send a confirmation email asking whether you intended to rejoin, no more than once in any seven-day period and no more than three times in total. You are resubscribed only if you confirm through that email.

You can ask us to delete the suppression record by contacting support. If we delete it, we will no longer be able to ensure that the address cannot be added again if it is subsequently submitted as a new address.

Addresses that bounce or report our messages as spam automatically stop receiving product-update emails and cannot be restored through the confirmation process described above.

Invitation and membership emails

When a workspace owner or admin invites you, we send one invitation email naming the person who invited you and the workspace. It can be resent once at your inviter's request and is not followed by reminders. Declining needs no account and deletes your address.

We also send Service messages about your membership, for example when you are removed from a workspace, made an owner, or a workspace you belong to is deleted, and when the email address on your account is changed. These are necessary to operate your account and are sent regardless of your marketing preferences.

Trial and pre-trial emails

Before and during a trial, we may send a short series of emails intended to help you get started with Storybrdr and make use of the Service.

Product-usage emails contain an unsubscribe link. You can opt out of these emails at any time.

We rely on our legitimate interests in helping people who have started or are preparing to start a Storybrdr trial to make effective use of the Service, subject to the applicable rules for electronic marketing.

Subscription and Service notices are different. Messages necessary to administer your account or subscription, including the trial welcome, reminder before your first payment, payment or conversion confirmation, password resets and security notices, form part of providing the Service and are sent regardless of your marketing preferences.

Unsubscribing from product updates or product-usage emails does not stop these necessary Service messages.

4. Automated image tagging and safety checks

When you upload an image, Storybrdr sends the image once to Anthropic's API. The same transmission is used for two purposes:

• to return descriptive tags that make the image searchable in your Library; and
• to return a safety assessment under our Acceptable Use Policy.

Anthropic is not sent a separate copy of the image for the safety check.

What is sent

We send the image or, where available, a smaller rendition of it, together with an instruction to describe and assess it.

We do not send customer identifiers with the image. Anthropic does not receive your name, email address, Project title, client name or workspace name as part of this request.

How often an image is sent

An image is sent once.

We record the processing attempt before the image is transmitted. This prevents the same image from being sent twice, including where two parts of the Service attempt to process it at the same time.

If the request fails after that point, the image is marked as unscanned and is not automatically sent again. It remains visible to you but is excluded from Share Links and exports. Contact support@storybrdr.com if this happens.

Descriptions of people

Descriptive tags identify what appears in an image. This can include broad descriptions of people, such as "crew", "woman" or "two men".

These descriptions are stored against the image in your Library so that you can search for them.

We do not use these descriptions to identify people. We do not attempt to determine anyone's identity, use facial recognition or match an image or person against another image or database.

A written description of a person may nevertheless constitute personal data relating to that person.

Special category and other sensitive information

Images may reveal sensitive information about a person, including information concerning health, disability, racial or ethnic origin, religion, sexual orientation, political views or trade union activity.

The model is instructed not to describe these characteristics. We also filter descriptive tags before storing them so that, if the model nevertheless produces such a description, we do not retain it in the searchable tags.

The safety check necessarily considers the contents of an image in order to determine whether it may contain unlawful material. Information arising from that assessment is retained only where there is a concern, only for as long as necessary to act on that concern, and is not added to the Library search index.

A safety assessment may record a flag, a category and a short explanatory note. Where an image is flagged, we treat that note as sensitive because it represents an allegation concerning the content of the image.

Lawful bases

For descriptive tagging used to make your own Library searchable, the processing forms part of the Service you have requested. Our lawful basis in relation to you is performance of our contract.

Where another person appears in an uploaded image, our lawful basis for processing personal data about that person for tagging is our legitimate interests in providing the feature requested by our customer.

For the safety check, our lawful basis is our legitimate interests in operating a lawful Service and the interests of our customers in ensuring that their work is not hosted alongside unlawful material.

We have assessed these interests against the rights and interests of the people concerned and recorded that assessment.

The safety check is mandatory

The safety check is a condition of using Storybrdr and cannot be disabled.

We do not rely on consent as our lawful basis under UK data protection law for the safety check. Its purpose is to prevent unlawful material from being hosted through the Service, and allowing it to be disabled would undermine that purpose.

Removing descriptive tags

Descriptive tags are a search feature and are separate from the safety check.

You can ask us to delete the descriptive tags associated with an individual image, a Project or your entire Library. There is no charge and we will complete the request within one month.

Removing descriptive tags does not remove or disable the safety check. Images from which tags have been removed remain searchable by filename and Project name.

Profile photos

A profile photo is an upload like any other. It goes through the same mandatory safety check, and it is sent to Anthropic once for that purpose and for nothing else. Descriptive tagging does not run on profile photos. A photo that does not pass the check is never shown, and your initials are used instead.

5. Automated restrictions, human review and objections

The initial safety check is automated. Two possible outcomes can take effect before human review.

Images flagged for review

If an image is flagged for review, it remains visible to you but is temporarily excluded from Share Links and exports until it has been reviewed by a person.

Images blocked automatically

An image may be blocked automatically only where it is suspected to contain child sexual abuse material and the model expresses no doubt about that assessment.

In that circumstance, the image is immediately withheld from everyone, including you, while it awaits human review.

We apply the restriction immediately because we will not knowingly continue to make suspected child sexual abuse material available while awaiting review.

Human review and appeals

A person follows up every flagged or blocked decision.

Where an appeal option is shown on a Board frame, you can use it to challenge the restriction. You can also contact us at support@storybrdr.com.

A person reviews every appeal, normally within one working day, and can remove the restriction.

You can explain why you believe the automated assessment is incorrect and challenge the outcome of the human review.

An automated restriction can hide or restrict an image. Only a person can decide to remove your work.

Images that cannot be checked

Occasionally the safety check may be unable to read an image, for example because of an unusual file format or a technical failure.

The image remains visible to you and is marked in your Library so that you know it has not been checked. It is excluded from Share Links and exports.

If this happens, contact support@storybrdr.com.

Your right to object to the safety check

You can object to our processing for the safety check. A person appearing in an uploaded image can also object.

We consider every objection on its individual circumstances and will explain our decision.

Our position is that preventing Storybrdr from hosting material that it would be unlawful to hold is a compelling legitimate interest. We therefore expect that, in most cases, this interest will provide compelling grounds for continuing the safety check despite an objection.

We nevertheless consider each objection individually.

If we reject an objection, we will explain our reasons in writing and inform you of your right to complain to the Information Commissioner's Office or seek a remedy through the courts.

Objections concerning descriptive tags are handled differently. If you ask us to remove descriptive tags, we will remove them as described in section 4.

Requests can be sent to support@storybrdr.com.

Where a person appearing in an image contacts us directly, we will deal with the parts of the request for which Storybrdr is controller and, where necessary, contact the customer whose Library contains the image.

6. Content reports and blocking

Signed-in users can report a comment. Anyone viewing a shared page can report that page without an account.

When a report is made, we record information needed to investigate it. Depending on the circumstances, this can include the reported comment, the guest's name, the workspace and Project concerned, the author information available to us and the reporter's email address.

A report may also be sent to Storybrdr support through our email provider so that a person can review it.

A person reviews every report and records the outcome. When you report a comment, you can also stop the Share Link through which it was posted, which prevents further comments from that link.

For guest reports, the reporter's email address is retained only until the report is closed and is then removed from the stored report.

Purpose: To investigate reports, enforce our Acceptable Use Policy and maintain the safety and integrity of the Service.

Lawful basis: Our legitimate interests in protecting Storybrdr, our customers and people using shared Boards from misuse and inappropriate content. Where we process information on behalf of a customer in relation to their Board, we also act in support of that customer's interests in managing their content and collaboration.

7. Script Import

If you paste a script into Storybrdr's Script Import tool and choose to import it, the script text is sent once to Anthropic so that it can suggest a breakdown into scenes and shots.

The resulting suggestion is returned to Storybrdr and becomes editable Board content. We do not retain the pasted script as a separate copy.

Nothing is sent unless you choose to use Script Import.

Scripts may contain personal data, including the names of characters and, in some cases, real cast and crew.

For processing carried out to provide the script breakdown you request, our lawful basis in relation to you is performance of our contract.

Where the script contains personal data relating to another real person, our lawful basis is legitimate interests, assessed on the same basis as personal data relating to people appearing in uploaded images.

Anthropic's role

Anthropic acts as our subprocessor for descriptive tagging and Script Import, which we carry out on your instructions.

Anthropic acts as our processor for the safety check, for which Storybrdr is the controller.

Anthropic is bound by a data processing agreement. Under Anthropic's commercial terms, Customer Content submitted through its commercial services is not used to train its models.

If we add or replace a subprocessor, we will update the list below and notify account holders by email at least 30 days before the change takes effect.

You may object to the proposed change. If we cannot resolve your objection, you may cancel your subscription and we will refund the unused portion of any amount you have paid.

8. Service providers and subprocessors

We use the following providers to operate Storybrdr.

Vercel

Purpose: Application hosting and cookieless page measurement on the public Storybrdr website.

Location and safeguards: EU and United States. The UK International Data Transfer Addendum applies to relevant transfers to the United States.

Neon

Purpose: Database hosting.

Location: London, United Kingdom.

The Storybrdr production database, including its backups, does not leave the United Kingdom.

Cloudflare

Purpose: File storage and bot protection.

Uploaded files are stored by Cloudflare under an enforced EU jurisdiction restriction. Storybrdr also uses Cloudflare Turnstile for bot checks on sign-up, password reset and the product-updates form. Turnstile processes technical browser and network information needed to perform the check.

Files stored in Cloudflare are retrieved by the Storybrdr application and served to you from our London hosting.

Stripe

Purpose: Payments, subscriptions, invoices, VAT-related payment processing and fraud prevention, including Apple Pay and Google Pay where you choose to use them.

Location: Global.

The card form on Storybrdr's payment page uses Stripe's own fields. Stripe processes card information directly so that Storybrdr does not receive or store your full card details.

Stripe is PCI DSS certified.

Resend

Purpose: Sending account verification, password resets, Service notices, trial and product-usage emails and product-update emails. Resend also holds the product-updates mailing list and provides its preferences page.

Location and safeguards: EU and United States. The UK International Data Transfer Addendum applies to relevant transfers to the United States.

Sentry

Purpose: Error monitoring.

Location: EU region.

Information sent to Sentry is scrubbed of Customer Content, passwords, request bodies, cookies and other sensitive request information before transmission.

Anthropic

Purpose: Descriptive image tagging, Script Import and the safety check.

Location: United States.

Transfer safeguard: The UK International Data Transfer Addendum to the European Commission's Standard Contractual Clauses.

Customer Content submitted through Anthropic's commercial services is not used to train its models under Anthropic's commercial terms.

YouTube and Vimeo

If you add a YouTube or Vimeo video link to a moodboard, Storybrdr retrieves information needed to create the video card, including its thumbnail, from the relevant service.

We re-host the thumbnail so that simply viewing the moodboard does not cause the viewer's browser to contact YouTube or Vimeo.

If a viewer chooses to play the video, it is played using the relevant provider's own player. The viewer then connects to that provider and its own privacy terms apply.

Google Sign-In

Google is not our subprocessor for Google Sign-In.

If you choose to sign in using Google, Google authenticates you as an independent controller under its own privacy policy and provides Storybrdr with an account identifier.

We do not send Google information about your Customer Content.

If you sign in using your email address and password instead, Google is not involved in that authentication.

The current Storybrdr subprocessor list is the list published in this Privacy Policy.

9. International data transfers

Storybrdr is operated by a UK company. We have designed the Service so that the principal databases containing customer accounts and Customer Content remain in the UK and EU.

Data stored in the UK and EU

The database containing Projects, Boards, notes and account information is hosted in London. It does not leave the United Kingdom, including for database backups.

Uploaded image files are stored by Cloudflare under an enforced EU jurisdiction restriction.

Files are retrieved by the Storybrdr application and served to users from our London hosting.

Transfers to the United States

Customer Content is transferred to Anthropic in the United States in two circumstances:

1. an uploaded image is sent once for descriptive tagging and the safety check, which take place in the same transmission; and
2. script text is sent if you choose to use Script Import.

Scripts may be more directly identifying than many uploaded images because they can contain the names of characters, cast or crew. If you do not use Script Import, we do not send your scripts to Anthropic.

When Customer Content is sent to Anthropic, we do not include your name, email address, account details, Project name, workspace name or client name, and Anthropic is not told which Storybrdr customer the material belongs to.

Under Anthropic's commercial terms, Customer Content submitted through its commercial services is not used to train its models.

Vercel and Resend also operate across the EU and United States. In providing application hosting and email services, they may process ordinary technical or account information involved in those services, such as an IP address in a server log or an email address used for an account verification message.

A reported comment may also be sent to Storybrdr support through Resend so that it can be reviewed as described in section 6.

Transfer safeguards

For relevant transfers to the United States, we use the UK International Data Transfer Addendum to the European Commission's Standard Contractual Clauses.

The applicable transfer terms form part of our agreements with Anthropic, Vercel and Resend.

These contractual safeguards do not remove the application of US law to a US provider. A US company may, in principle, receive a lawful government or other legal demand for information in circumstances that differ from those applying to a UK company.

We assess the risk in relation to Storybrdr Customer Content as low and have designed the relevant data flows to reduce that exposure. For Anthropic processing, the transferred material is limited to an individual image or script submitted for processing and is not accompanied by Storybrdr account information identifying the customer to whom it belongs.

The existence of these safeguards does not mean that the risk associated with an international transfer is zero.

You can contact us if you would like further information about the safeguards used for international transfers.

10. Information for people appearing in uploaded images

This section applies if you appear in a photograph uploaded to Storybrdr by one of our customers, for example in an image from a location recce, casting session or production.

What Storybrdr knows about you

We do not know your identity simply because you appear in an uploaded image.

We do not hold your name or contact details in connection with the image unless they have separately been provided to us, and we do not use facial recognition or attempt to match your face to an identified person.

Because we ordinarily have no information that enables us to identify or contact a person appearing in an uploaded photograph, we cannot individually notify everyone who may appear in Customer Content. We provide this information publicly instead.

What happens to the image

Two relevant forms of processing may take place.

First, the image may be given broad descriptive tags so that the Storybrdr customer can find it in their Library. Examples include descriptions such as "harbour", "two men" or "golden hour".

Second, the image is automatically checked to identify material that may be unlawful to host on Storybrdr.

The descriptive tags are stored against the image so that they can be searched. We do not use them to identify you.

Who is responsible

The Storybrdr customer who uploaded the photograph is the controller responsible for the photograph and determines what happens to it.

Storybrdr acts as that customer's processor in storing and otherwise processing the photograph to provide the Service.

Storybrdr is separately the controller for the mandatory safety check because we determine the purpose and operation of that processing.

Your rights and requests

You can contact us at support@storybrdr.com.

If you ask us to remove descriptive tags relating to a photograph, we will do so free of charge and within one month.

If your request concerns the photograph itself, we will pass the request to the customer whose Library contains the image and assist them in responding.

You can also object to processing for which Storybrdr is the controller. Section 5 explains how we handle objections to the safety check.

You have the right to complain to the Information Commissioner's Office and may also seek a remedy through the courts.

Identifying the relevant photograph

Because we ordinarily hold no information that identifies the people appearing in an image, we may not be able to locate a particular photograph from a description of the person alone.

Information such as the production, date or location can help us identify the relevant image.

11. Cookies and local browser storage

Storybrdr does not use advertising cookies or cross-site tracking cookies.

We use cookies and similar local storage only where needed to operate, secure or provide features of the Service. These include:

• cookies used to keep you signed in and secure your session;
• a temporary cookie recording that the correct password has been entered for a password-protected Share Link;
• cookies used by Cloudflare Turnstile when a bot check is required;
• Stripe cookies used for payment security and fraud prevention on our payment page; and
• local browser storage containing a guest reviewer's own name and limited interface preferences.

Our public website measurement does not use cookies or an identifier that follows you between websites.

We do not currently use advertising or cross-site tracking technologies. If this changes and consent is required, we will ask for consent before using them.

12. Data retention and deletion

Account data and Customer Content

We retain your account data and Customer Content while your account is active.

You can delete your account yourself through Storybrdr. Once you complete the confirmation process, deletion removes your account and Customer Content permanently and immediately from the live Service.

If you ask us to close your account through support, we will complete the request within one month.

In either case, we retain only minimal records we are required to keep, such as invoices, moderation records and a record that the deletion took place. Invoices required for tax purposes are retained for six years.

Deleted Customer Content

Deleted Customer Content is recoverable for 30 days.

After 30 days it is permanently deleted, including removal of a deleted image from any Boards in which it appeared.

Database backups

Our database maintains a rolling seven-day history in London.

Deleted data ages out of that history within seven days of deletion. After that period, no copy remains in the database backup history.

Guest comments and approvals

Guest comments are retained with the Project to which they relate.

A guest can contact us to ask for their name to be removed from a comment.

A name recorded as part of an approval is retained with that approval for as long as the Project exists because it forms part of the record of who approved the Board.

Invitations and membership

An invitation that is not taken up is deleted when it is declined or withdrawn, and in any case seven days after it was sent. The address is removed from the membership log at the same time, so nothing is left holding the address of someone who never joined.

Who is in a workspace is kept for as long as the workspace exists. The log of who joined, left or changed role is kept for two years and then deleted.

When you change the email address on your account, the record of the address you are leaving is deleted the moment the change completes, or within a day if the change is abandoned.

Content reports

For a guest report, the reporter's email address is retained with the report until it is closed and is then removed.

Other information associated with moderation and safety may be retained for as long as necessary to investigate the report, enforce our policies, protect the Service or meet legal requirements.

Logs and error reports

Logs and error reports are retained for up to 90 days.

Product-updates list

We retain your details on the product-updates list until you unsubscribe.

After unsubscribing, we retain the minimal suppression record described in section 3 so that you are not emailed or re-added by mistake.

Rejoining requires confirmation through your own email inbox.

You can ask support to erase the suppression record as described in section 3.

13. Your data protection rights

Under the UK GDPR, depending on the circumstances and the lawful basis for the relevant processing, you may have rights to:

• access your personal data;
• have inaccurate personal data corrected;
• have personal data erased;
• restrict processing;
• object to processing; and
• receive or transfer certain personal data in a portable format.

Where we rely on your consent, you can withdraw that consent at any time. Withdrawing consent does not affect processing that was lawful before the withdrawal.

Where we act only as a processor for Customer Content, the Storybrdr customer is responsible for responding to data protection requests concerning that Customer Content. We will assist the customer as required.

Your right to object

Where Storybrdr relies on legitimate interests, you have the right to object to that processing on grounds relating to your particular situation.

We will stop the relevant processing unless we can demonstrate compelling legitimate grounds that override your interests, rights and freedoms, or the processing is required for the establishment, exercise or defence of legal claims.

Your right to object to direct marketing is absolute. If you tell us to stop using your personal data for direct marketing, we will stop.

Section 5 explains specifically how objections to the Storybrdr safety check are handled.

Changing your details

You can change your name, job title and profile photo at any time in Settings. Changing the email address you sign in with is also self-service. It takes two emailed links: one to the address you are leaving, to confirm it is you, and one to the address you are taking, which completes the change. We then send a notice to the old address. Any workspace invitation waiting at your old address stops working, so whoever invited you will need to send a new one.

You can leave a workspace you were invited into at any time from Settings.

Exporting your Storybrdr data

You can export any Board as a PDF at any time, including after your subscription has lapsed.

CSV and PowerPoint exports require an active subscription.

A full export of your account, including original image files, is available by contacting us. We will provide it within one month.

Deleting your account

You can start account deletion through Storybrdr on the web or in the iOS app.

Go to Settings, choose Delete my account, type DELETE to confirm, and we will send you a confirmation link by email.

The confirmation link is completed while signed in to Storybrdr on the web. Opening it first cancels any applicable subscription and then permanently deletes your account, your workspace and everything in it.

A workspace you are alone in is deleted with your account. If you are the only owner of a workspace that other people belong to, make someone else an owner first, or contact us at support@storybrdr.com and we will delete the workspace with you. If a workspace you belong to is suspended or holds an image under safety review, or if you would prefer us to handle the request, contact us at the same address.

Requests handled through support are completed within one month. That process places the account on a seven-day deletion period before it is erased, allowing you to change your mind during that period.

Exercising your rights

Contact support@storybrdr.com to exercise your rights or make a data protection request.

We will respond without undue delay and normally within one month.

You also have the right to complain to the Information Commissioner's Office. We would appreciate the opportunity to address your concern first, but you are not required to contact us before making a complaint.

14. Security

We use technical and organisational measures designed to protect personal data and Customer Content.

Data is encrypted in transit using HTTPS and encrypted at rest.

Passwords are hashed and are never stored or logged in readable form.

Human access to Customer Content is limited to circumstances where it is needed to provide support at your request, comply with a legal requirement, review content flagged by the safety check or investigate content someone has reported. Such access is logged where applicable.

Card details are entered into Stripe-provided fields on Storybrdr's payment page and sent directly to Stripe. Storybrdr does not receive or store your full card details.

If a personal data breach occurs, we will notify affected individuals and the Information Commissioner's Office where required by law.

15. Children

Storybrdr is not directed at children.

You must be at least 16 years old to use the Service. We ask you to confirm that you are 16 or over when you create an account. We do not collect your date of birth.

16. Using Storybrdr on iOS

The Storybrdr iOS app provides access to the same Service, and this Privacy Policy applies equally when you use Storybrdr on an iPhone or iPad.

The following information applies specifically to the iOS app.

Camera and photo library

If you use the camera, Storybrdr asks for camera permission the first time you use that feature.

Pictures from your photo library are selected using Apple's system photo picker. Storybrdr receives only the picture you choose and does not receive permission to browse or read your photo library.

The app does not access your contacts, location or calendar and does not upload photographs without you choosing to add them to Storybrdr.

On-device storage

Your Projects and their images may be downloaded to your device so that they remain available without an internet connection, including when using Storybrdr on set.

This information is held within the app's private storage.

Signing out removes downloaded Projects, images and queued changes from the device. Deleting the app removes data held within the app itself.

Your device's own backup service, including iCloud Backup where enabled, may retain a copy of locally stored app data until that backup is refreshed or replaced.

Deleting your Storybrdr account removes the corresponding account and data held by Storybrdr as described in section 12.

Usage data, tracking and advertising

The Storybrdr iOS app does not contain an advertising identifier, third-party analytics SDK or third-party advertising tracker.

The app itself contains no third-party analytics code. The limited first-party account actions described in section 2 are recorded by our server when the app uses the Service.

Sign in with Apple

If you choose Sign in with Apple, Apple provides the email address associated with your Apple sign-in. That address must match an existing Storybrdr account.

Apple may also provide your name on the initial authorisation, but Storybrdr does not retain that name from the Apple sign-in response.

If you use Apple's Hide My Email feature and the relay address does not match your existing Storybrdr account, you will need to use another sign-in method.

When you delete your Storybrdr account, we also notify Apple that Storybrdr no longer requires the association with your Apple ID.

Inviting colleagues from the app

If you invite a colleague from the app, the email address you type is sent to us for that invitation only, as described in sections 2 and 12. The app does not read your contacts; you type the address yourself.

Third-party AI processing

As described in section 4, images uploaded to Storybrdr are sent to Anthropic for descriptive tagging and the mandatory safety check.

You are told about this processing in our Terms and in this Privacy Policy when you create your account, which happens on the web before any image can be uploaded. The iOS app sends an image to Anthropic only when you choose to add that image to a Board.

17. Changes to this Privacy Policy

We may update this Privacy Policy from time to time.

If we make a material change, we will bring it to the attention of affected account holders by email or through the Service. Where a change relates to a new purpose for processing personal data, we will provide the relevant information before that processing begins.

Changes to subprocessors are subject to the notice provisions described in section 7.

18. Contact and complaints

For questions about this Privacy Policy, to exercise your data protection rights or to make a privacy-related request, contact:

Salt & Gorse Ltd
Bosnoweth
Higher Argal
Budock Water
Cornwall
England
TR11 5PE

Email: support@storybrdr.com

Salt & Gorse Ltd is registered in England and Wales under company number 15581747.

If you have a concern about how we process personal data, you have the right to complain to the Information Commissioner's Office (ICO), the UK's data protection regulator.