Privacy Policy

Last updated 23 September 2026

Once Spoken is a small independent project run by one person. This page explains, in plain English, what information it holds, why it holds it, and what you can ask us to do about it.

The short version

Who operates Once Spoken

Once Spoken is operated from England by Robert Hawes, a sole trader trading as Once Spoken. Robert Hawes is the data controller for the personal information described on this page and reads every message that comes in.

The way to reach the controller — about a memorial, about your own information, or about anything else on this page — is the contact form on Once Spoken. The controller’s geographical and service address is 201 Linley Drive, Hastings, East Sussex, TN34 2BX, United Kingdom.

Information about people who have died

This matters, and it is often misunderstood, so it is worth being precise about it.

UK data protection law — the UK GDPR and the Data Protection Act 2018 — protects living individuals. Information about a person who has died is not that person’s “personal data” under those laws, and the rights described further down this page (access, erasure, and so on) do not belong to someone who has died.

A recording of somebody’s voice sits in the same place. The voice of a person who has died is not their personal data, and we are not treating it as though it were. But a recording is also somebody’s property — there is copyright in a recording, and a performer has rights in their own recorded performance, both of which can outlive the person and belong to whoever inherited them. That is a different question from data protection and it does not disappear because the person has died, which is why the first tick asks whether you have the right or permission to provide the recording at all, and why we may refuse one.

That is a statement about the law, not about how we behave. We treat memorials with care because of what they are, and we will always consider a request from a family member about someone they have lost, whether or not the law obliges us to. See corrections and removal.

Two things do remain personal data, and are covered by this policy in the ordinary way:

What we collect

When you submit a memorial

The submission form asks for the person’s name, the year they were born, the year they died, a short piece of something they said, and a photograph. It also asks you to position that photograph inside the round frame the memorial shows it in, and it stores three numbers describing where you left it — across, up and down, and how far in you zoomed — so that the memorial displays the photograph framed the way you chose rather than however it happened to be cropped automatically. Those numbers describe the picture, not you, and the photograph itself is stored exactly as you sent it. That material is intended to be published, and if we approve it, it will be publicly visible on this site to anyone who comes across it.

A published memorial has its own web address, and search engines can find it. Once a memorial is approved it is given a permanent address of its own — the person’s name, followed by the memorial’s identifier — and that page carries their name, the years, the photograph and the words on it. It is a page on the open web, so search engines are able to list it, and the name, a short extract of the words and the photograph may appear in search results and in the preview shown when the link is posted on social media. That is deliberate: being found by people who were not looking is the purpose of this site, and it is why a memorial is published at all. Nothing about you, the person who submitted it, is on that page or in anything a search engine or social network reads — see the paragraph below. If a memorial is corrected, taken out of public view or removed, its page stops being served within five minutes. We cannot control how long a search engine keeps its own copy or its own thumbnail afterwards, and we will not pretend otherwise; if that matters to you, tell us and we will tell you what we have asked them to do.

The form also asks about you, the person submitting it:

Below those, in a section of its own headed Email choices — optional, the form offers three separate ticks. Every one of them starts empty; none is preselected; none is required; ticking or leaving any one of them has no effect on the others, and no effect at all on whether the memorial is submitted, whether it is published, or on which funding choice is available to you. They are described one at a time under your email choices, which also explains how to change or withdraw any of them afterwards.

For each of the three, and for the social media permission above, we record whether you gave it, when, the exact wording you were shown at the time, and — if you later withdraw it — that you withdrew it and when. That record is how we honour the choice accurately rather than from memory, and it is not visible to anybody but us.

Your name, your email address and your relationship are private. They are administrative information about the submission, not part of the memorial. They are not shown on the memorial, not shown anywhere else on the site, not included in the pages that search engines and social networks read, and not returned by the public parts of our database — a visitor looking at the memorial, or at the page’s source, cannot see them. Nor is your email address ever used as a memorial’s address or put into its link. Only a signed-in administrator can read them.

We use them to administer the memorial you submitted: to keep a record of who sent it in, to write to you about the submission, to tell you when it has been approved and give you its permanent link, to answer you if you ask us something about it, to review the memorial, and — if it ever becomes necessary — to deal fairly with a question about who has a say over that memorial, or with a dispute or a removal request about it.

Giving us your email address does not subscribe you to anything. It is not a marketing permission, we do not treat it as one, and it does not add you to a mailing list, a newsletter or any promotional list. The only messages we send beyond telling you what happened to your own submission are the optional ones you ticked for, and each is sent only under the tick that asked for it — see your email choices below.

Memorials submitted before this change may have no submitter name, no relationship, and in some cases no email address, because those questions were not asked at the time or were optional. We have not gone back and filled anything in. Nobody who submitted a memorial before one of the optional ticks existed holds that permission, and none has been created for them: not by an earlier agreement, not by the address itself, not by a change to these terms, and not by the fact that they had already agreed to something else. An older permission for memorial features stays limited to memorial features; it does not expand to products, services, offers or support. Anyone can make the current choice themselves at Email updates & offers, followed by a confirmation button sent to their address.

Your funding choice and contributions

For each new memorial we keep the funding option chosen, the amount attached to that option (including zero), the memorial it belongs to, its status and the date. This is how we can see whether the cost of the service is being shared sustainably and whether a payment journey was completed, cancelled, failed or abandoned. The choice is never used in moderation and is not visible on the memorial.

If you choose a positive contribution, Stripe processes the payment. Once Spoken keeps the amount, currency, status, Stripe checkout and payment references, refund information and dates needed to confirm the payment and keep accounts. We do not receive or store your full card number, security code or bank-login details. If you are signed in, the contribution may be linked to your account so My Once Spoken can show your private history and so we do not keep asking you to contribute again. An anonymous contribution remains anonymous unless some other record, such as the memorial submission itself, already identifies you.

When you use My Once Spoken

Accounts use passwordless email sign-in through Supabase. We hold the account identifier, verified email address, sign-in and last-visit times, and the links between that account and memorials it owns, co-manages or saves. We do not create or store a password. You can browse, share, light candles, contribute and submit a memorial without signing in; an account becomes necessary only when you ask to manage one.

When you ask for a sign-in link, Once Spoken’s server asks Supabase to create a one-time verification secret and Resend delivers the service email. Direct public sign-up remains closed. To prevent repeated or automated sends, we keep for no more than 14 days a keyed one-way fingerprint of the normalised address, the request time, whether sending succeeded and an opaque provider message reference. The throttle record contains no readable email address, IP address, cookie or device identifier. The one-time secret is placed after the # in the link so browsers do not send it in an ordinary page request, and it is removed from the address bar as soon as the page uses it.

When you first sign in, we compare the verified address with the private submitter email already stored against memorials. An exact match can link those memorials to your account. The comparison happens privately and does not reveal other addresses or memorials. An owner can also invite a co-manager by email. We keep the invited address, a one-way fingerprint of the invitation link, who sent it, its status and its expiry. Active managers of the same memorial can see one another’s email address and role so they know who shares responsibility for it; none of that appears publicly.

My Once Spoken records memorials you deliberately save, proposed edits and review decisions, ownership transfers, and a baseline of view, candle and share totals when you visit. The next visit can then show only what changed since the previous one. Those are aggregate memorial figures, not the identities of visitors or the people who lit candles—we do not have those identities. Public edits are requests: the existing memorial stays unchanged until a person approves them.

If you add a voice clip

This part of the site is available now, both while a memorial is being submitted and afterwards through the private, expiring link described below.

A memorial may carry a short recording of the person’s own voice. The form asks “Do you have their voice somewhere?” and explains that a voicemail, family video or voice note can work. It is genuinely optional: choosing to do it later, leaving it alone, changing your mind, or abandoning it halfway through has no effect on whether the memorial is submitted, reviewed or published, or on which funding choice is available to you.

What happens to the file you choose. You pick an audio or video file you already have — a voicemail, a video from a birthday, a recording made for you — and listen before you commit to anything. If it is already short enough, the page lets you confirm the whole recording as it is. If it is longer, you choose the few seconds you want privately in your own browser, with a player that lets you listen and adjust. When you confirm, two things are stored: the original file, kept privately, and a short processed clip made from all or the part you chose. The original is never published, never served to a visitor, and never linked to from any page — it is kept so that we can show what the clip was made from if that is ever questioned. The processed clip is the only thing that could ever be public.

What we record with it. The length of your file and of the clip, where in the file the clip starts and ends, the format it was in, the size in bytes, and whether the processing succeeded. A written transcript of what is said — you may type one, and we may correct it, because a memorial that can only be heard is no memorial at all to somebody who cannot hear it. No artificial intelligence or speech-recognition service is involved in any of that. No recording is sent to a transcription service, a speech-to-text service, or any other third party for processing: nothing of the kind is connected to this site.

The permission, which is asked separately. The ticks only appear once you have actually chosen a recording, they sit apart from the optional email choices, none of them is pre-ticked, and all four are required before a recording can be accepted:

Alongside them the page says, in its own words, that your original file is kept privately and is never the file anyone hears; that approving the memorial does not approve its recording, because the two are reviewed separately and we may refuse or remove a recording; that the permission covers this recording on this memorial and does not allow advertising, use by anyone else, voice cloning, AI training, synthetic speech, impersonation, sale or licensing to another company, and that a materially different use would need a new permission asked for and named at the time; and that asking us to take a clip down removes public access promptly but does not rewrite the record of what was agreed before.

What we keep as the record of that. Which memorial and which submission it was, which recording it was, each of the four statements you agreed to, the exact wording you were shown and its version, the moment it happened — timed by our database rather than by your device — which part of the site it came from, and whether it was a permission given, later withdrawn, or disputed. Each of those is written once and never edited: a withdrawal is a new record saying so, never a change to the one that said yes. It holds nothing about your device, your browser or your location, because none of that is evidence of anything.

Nobody is treated as having given it who was not asked. No memorial submitted before this existed has any audio permission attached to it, and none has been created for one. It is not inferred from a file, not inherited from the memorial’s own confirmation, not read out of the social media permission, and not read out of any email choice. If a recording is replaced, the new one needs its own permission; the old one’s record stays as it was.

Other people who can be heard. A recording of somebody who has died is not that person’s personal data — see information about people who have died — but a living person who can be clearly heard on it is a different matter, both in data protection terms and in fairness. That is what the second tick is about. A longer file can be trimmed before you commit; if a short file includes somebody who has not agreed, choose a different file. If you are a living person who can be heard on a clip on this site, contact us and we will take it out of public view while we look at it.

Withdrawing it. You can ask us to take a clip down at any time, whether or not you use My Once Spoken. Ask through the contact form, through your signed-in memorial management area, or use the private link described under corrections, changes and removal. Public access ends when we act on it; the record of what was permitted, and when, is kept, for the reason given under how long we keep it.

When you contact us

The contact form asks for your name, your email address, what your message is about, and the message itself. If you were looking at a particular memorial when you opened the form, a reference to that memorial is included so we can see what you are writing about.

Partnership applications and referral links

When an organisation applies. The partnership form asks for the organisation’s name, type, website, service area, how it proposes to introduce Once Spoken, and the applicant’s name, role, work email address and optional telephone number. It also records the version of the partnership terms accepted, the time of the application, the review decision and any administrative note. We use that information to assess and administer the application, prevent repeated automated applications, and send operational messages confirming receipt and the decision. It is not added to a marketing list. The private status link contains a random capability in its fragment — the part after #, which a browser does not send in its request — and our database stores only a one-way fingerprint of it.

When somebody follows an approved partner link. We create one random referral reference and one random secret for that visit. The secret is held in that tab’s session storage; our database stores only its one-way fingerprint, the partner link used, the time, whether the site was live or a preview, and when the reference expires. It stores no name, email address, IP address, user agent, location or device details. If a memorial is genuinely submitted within 30 days, the reference may be connected to the identifier of that submission or memorial. An abandoned form records no memorial. The secret is removed from the tab when the connection has been confirmed, and closing the tab removes it in any event.

What a partner can see. An approved partner’s private status page shows only aggregate totals: visits through its link, memorials created, memorials published, candles lit on those memorials, and the total of its own voluntary contributions. It never shows who visited, a family’s name or contact details, which memorial was created, its photograph, words or recording, whether a particular family contributed, or any moderation note. A partner cannot contact a family through this system, influence moderation, or change what a family pays. Administrators can see the application and the underlying records needed to review misuse or correct the figures.

Optional organisational support. If an approved partner makes a contribution while using its private status page, we may associate that contribution with the partner so its own support total can be shown. The payment remains governed by the payment terms below; the association is not considered when an application is approved, when a partner is kept active, or when any memorial is moderated.

Moderation records

Every memorial is reviewed by a person before it appears. We keep the record of that review — whether a memorial was approved or rejected, and any note made about it — along with the submission itself.

Analytics — how the site is used

Once Spoken uses limited first-party analytics. It is ours, it runs on our own database, and the information does not leave it. As pages are used, we may record:

For those voice events, the page sends only the allowlisted event name and the page path. The same analytics routine adds the approximate country and the short-lived visitor and visit hashes explained below. It does not send or store a filename, email address, memorial name or identifier, recording, transcript, owner link or owner token; the path has no query string and a memorial address is reduced to /memorial.

About that country. It is worked out on our side of the connection, from a country signal that the edge network in front of the site has already attached to the request. Nothing looks your address up in a geolocation or IP-location database, and no third-party service of that kind is involved anywhere in it. Your browser is never asked for permission to use your location — that permission is switched off for this site altogether. No city, region, postcode, precise location or coordinates are collected, and there is nothing more precise than the country for us to hold. It is an approximation, and we treat it as one rather than as a verified statement of where you are: a VPN, a proxy, or simply the way a network routes traffic can all make it wrong. We use it only for aggregate analytics and reporting — how many visits came from which country — and never to decide anything about you. It is not used to sign anyone in, not to grant or refuse access, not for fraud prevention, not for consent, not for moderation, and not for any other security decision. The retention and the lawful basis described for analytics below apply to it unchanged.

Counts of visitors and visits are worked out inside our database from short-lived pseudonymous hashes that it derives from the request itself. Your IP address and your browser’s user-agent string are used in passing to produce those hashes and are not stored: they are not written into the analytics records and cannot be read back out of them. We call this pseudonymous rather than anonymous deliberately. A hash is calculated from information about your connection rather than invented at random, so — although we cannot turn one back into you, and do not try to — calling it completely anonymous would be overstating it.

Nothing is stored on your device for this. There is no analytics cookie, no local storage entry and no session storage entry, and nothing here attempts to fingerprint your device — no screen size, no font list, no device model. Nor is there any Google Analytics, Meta Pixel or cross-site advertising tracker anywhere on this site. Analytics information is not sold, not shared for anyone else’s marketing, and not combined with anything you have sent us.

Sharing a memorial. Every memorial has a share button beneath it, and the page shown after you send one in offers you its permanent link to copy. The share button opens a few ready-made words about the memorial, which you are free to change, rewrite or delete, together with buttons for WhatsApp, for Facebook, for your phone’s own share sheet where it has one, and for copying the words and the link. What those words say never reaches us. They are put together in your browser, they go only where you send them, and nothing you type or edit there is sent to Once Spoken or stored anywhere by us. When somebody actually uses one of these controls — not when it is merely on the screen — we record three things: which memorial it was, which part of the site it was shared from, and whether the link was copied to your clipboard or handed over to another application. We do not record where you then sent it. That includes the WhatsApp and Facebook buttons: pressing one of them simply follows an ordinary link, and all we keep is that a share happened and which of those two things it was — not which button you pressed, not which application it went to, and nothing about who received it. If you use your phone’s share sheet, the browser tells the page that it finished and nothing more, so we cannot know whether you chose WhatsApp, Messages, email or anything else — and we do not guess. There is no record of a recipient, an address, a phone number or a message. Neither WhatsApp nor Facebook has any code on this site: nothing of theirs loads here, nothing of theirs watches you here, and neither of them learns anything until you choose to open one of them yourself.

There are two places where we have to be straight with you about the limits of that. On an Android phone, the share sheet your browser opens is part of the phone rather than part of this site, and the browser reports the same result to the page whether you picked something from it or changed your mind and dismissed it. We cannot tell those two apart, and we are not willing to read your clipboard to find out. So on Android, opening the share sheet and then closing it without sharing is counted here as a share. It records nothing more than an ordinary share does — the memorial, the moment, and which part of the site it came from — and it still records nothing about you. It means only that our count of Android shares is a count of times the share sheet was opened, and so is a little high. On a computer or an iPhone the browser does tell the page the difference, and closing the sheet without sharing records nothing at all. Simply looking at a memorial, or opening its link, still records no share on any device. The WhatsApp and Facebook buttons sit under the same honest limit: they count at the moment you press them, because that is where this page’s part in it ends. Whether you then press send in WhatsApp, or finish the post on Facebook, is between you and them — we are never told, so these are counts of shares started rather than shares delivered.

When you share a memorial using one of those controls, the link they hand over carries one extra word on the end of it — &via=share. The permanent link shown to you on the screen does not: it stays exactly as it has always been, so selecting it by hand, bookmarking it or typing it in carries no extra word and is counted as nothing. If somebody follows a link carrying that word, we record that a visit arrived at that memorial through a shared link. That is the entire purpose of it: to tell us whether the memorials bring anybody here, which we otherwise have no way of knowing. It is the same single word on every share of every memorial by everybody, so it identifies no share and no person, and there is nothing in it to tell two people apart. It is not required for the link to work — the ordinary permanent link to a memorial is unchanged, every link shared before this existed still works exactly as it did, and stripping the word off changes nothing but our ability to count. Once the memorial is on the screen the word is removed from your address bar, and it is not written anywhere on your device at any point.

One email we send carries a link with that word on it as well: the single sharing reminder described under the emails we send you, which exists so that you can pass the memorial on. It is the same constant word there as everywhere else — not unique to you, not unique to the message, not generated per recipient, and carrying nothing that could tell us who followed it. It is not a tracking pixel, not a redirect through anything of ours, and not click tracking. The link points straight at the memorial, so opening that email, or not opening it, still tells us nothing, and if somebody follows the link all that is recorded is the same anonymous row as any other shared arrival.

These two sharing records are the smallest thing that could answer the question. They hold a memorial, a moment in time, and for a share which button was pressed. Unlike the page and memorial views described above, they carry no visitor or visit hash at all — nothing derived from your connection, and nothing that could group your sharing with anything else you did. We describe them as containing no identifier rather than as anonymous, because they are timestamped and sit in the same database as the pseudonymous view records, and we would rather be accurate than flattering. They are used to count sharing in aggregate, and — as the next paragraph explains — to count what happened next when somebody arrived through a shared link. They are not used to contact anybody and not used to decide anything about you.

What happens after a shared link. Knowing that a shared link brought somebody here does not tell us whether it mattered, so we also count whether that visit went on to do something. When a visit arrives at a memorial through a shared link and that memorial is actually shown, the arrival record described above is stamped with a reference invented at random by our database for that one arrival. It is not derived from your address, your browser, your device or anything else about you; it is not stored on your device; and it cannot be read back by anything running in your browser. The page holds it in memory only while it is open. If, within two hours of that arrival, a candle is lit, a memorial is sent in, a contribution is actually paid, or a memorial is shared again, we record a single further row: which memorial had been shared, that reference, which of those four things happened, the memorial or contribution it was, and when — and, for a contribution, its amount and currency, so that we can total what sharing brings in. Nothing else. There is no name, no email address, no IP address, nothing about your device, and no record of a person: the reference belongs to one arrival at one memorial, not to you, and there is nothing in it that could be matched to another visit, another day or another site.

We should be plain about the one thing this does do that the sharing records on their own did not: it connects a candle, a memorial submission, a paid contribution or a further share to the fact that a shared link was followed first. Where you sent in a memorial or made a contribution, we already hold that record and explain it elsewhere on this page; this adds only the note that it followed a shared-link arrival. The two hours is a deliberate limit rather than a technical one — after it, the reference counts nothing, and the arrival is simply an arrival. A candle that is only a repeat tap, a submission form that is abandoned, a payment that fails or is cancelled, and a share that does not complete all record nothing here, because nothing happened to count. Following a link that carries the &via=share word to a memorial that does not exist, or adding that word to an address by hand, establishes nothing at all. We use these figures only in aggregate, to see whether sharing brings people who then take part, and whether that starts another round of sharing. They are not used to contact anybody, not used to build a profile, not used to decide anything about you, and never shared with an advertising network — as with everything else here, there is no third-party analytics or advertising tracker involved in any part of it.

The invitation you may be shown after a shared link. If you arrived at a memorial through a shared link and stayed with it for a moment, or lit its candle, the page may quietly ask whether there is somebody you would want the world to remember. Whether to show that is decided inside the open page and nowhere else. Nothing is recorded because you were shown it, nothing is written to your device for it, no cookie, local storage entry or session storage entry is created, and there is nothing left of it once you close or reload the tab. If you go on to send a memorial in, what is recorded is the single row already described above — the same one that would have been recorded if you had found the form yourself.

Passing Once Spoken itself on. There is a page for people who would like more families to find the site. It offers the same kind of ready-made words, which you are free to change, and the same buttons. When somebody actually uses one of them, we record a moment in time and two facts: which part of the site it was shared from, and whether the words went to your clipboard or were handed to another application. Pressing WhatsApp hands the words over; pressing Facebook copies them for you to paste, because Facebook will not accept words from a link, and that is recorded as a copy — which is what actually happened. There is no memorial in that record, because no memorial is involved: it cannot appear in any memorial’s figures and it takes no part in the shared-link counting described above. It holds no visitor, no visit, no referral code, no country, no referring site and no identifier of any kind, and there is no advocate account, no sign-up, no code to quote and no reward anywhere in it. Nothing is stored on your device for it. The same honest limit described above applies on an Android phone: opening the share sheet and then dismissing it is counted here as a share, because the phone does not tell the page the difference.

We use all of it for six things: to understand how the site is being used, to see whether our own outreach is reaching anybody, to understand how people discover the memorials, to see whether sharing a memorial brings anybody here, to see whether the people who want to help us reach more families are able to, and to improve the optional voice journey by seeing where people stop or encounter a failure. Raw analytics events are kept for 180 days and then deleted; the aggregate counts worked out from them remain. The sharing and attribution records above are kept for the same 180 days, and the reference that links them is deleted with them; so are the records of the site itself being passed on.

Technical information

Separately from the above, like any website, this site cannot be delivered to you without your device contacting the servers that serve it. Our hosting and database providers keep their own technical logs as part of running their services, which will ordinarily include IP addresses, timestamps and details of the request. We do not use those logs to build any profile of you. Each provider keeps them for its own limited period, under its own policy, and we do not export them, copy them anywhere else, or combine them with anything you have sent us.

Why we use it, and our lawful basis

WhatWhyLawful basis
Submitter’s name To know who sent a memorial in, to address you properly if we write to you, and to be able to answer fairly if someone later asks who submitted it Legitimate interests: running a moderated memorial site and keeping an accurate record of where each memorial came from
Submitter’s email address To tell you when the memorial has been approved and give you its permanent link, and to reach you about a query, a problem or a decision on the submission you sent Legitimate interests: running a moderated memorial site and being able to tell the person who sent something in what happened to it. This is service correspondence about your own submission, not marketing
Submitter’s relationship to the person — optional To help us handle a later question, dispute or removal request about that memorial fairly Legitimate interests, where you chose to tell us. Leaving it unanswered has no effect on the submission
My Once Spoken account, memorial-manager links, invitations, saved memorials, visit baselines and change requests To authenticate you, let the verified submitter or an invited co-manager look after a memorial, show what changed since the last visit, and review requested public edits safely Legitimate interests: providing the private management service you asked to use, protecting memorials from unauthorised changes and keeping a clear record of who may manage each one. Saving a memorial or accepting an invitation is your deliberate action
Funding choice and contribution record To record how each memorial’s costs are intended to be met, open and reconcile a voluntary payment where chosen, issue refunds, show signed-in contribution history and understand completion or abandonment in aggregate Legitimate interests: funding and administering the service without making payment a condition of a memorial; and legal obligation for financial and accounting records where money is received
Submission confirmation To show that someone confirmed they had the right to submit a memorial and photograph Legitimate interests, and compliance with our legal obligations where a dispute or complaint arises
Optional social media permission To use a memorial in Once Spoken’s own promotional material, only where that was agreed Consent — which you can withdraw at any time
A voice clip — optional To store the recording you chose, make a short clip from all or the part you selected, review both, and publish that clip as part of the memorial if it is approved Consent, asked for on its own four ticks and covering this recording on this memorial only — which you can withdraw at any time. Where a living person can be heard on a recording, our basis for holding it while we act on a concern about it is our legitimate interest in dealing with that concern fairly
The record of that permission To be able to show which statements were agreed, in which words, when, and by which route — and to show a withdrawal without erasing what preceded it Legal obligation, and legitimate interests: the law that requires consent for publishing a recording also requires us to be able to demonstrate that we had it. It is kept even after a withdrawal, and holds nothing about your device
A transcript of a clip So that a memorial that can be heard can also be read, by somebody who cannot hear it or will not play sound Legitimate interests: making a published memorial accessible. It is written by you or by us, and never by an outside service
Optional sharing-reminder permission — and the one email sent under it To send you a single reminder about sharing the memorial you submitted, a few days after it is published, if nobody has shared it by then Consent — asked for separately on the form, recorded with its wording and its date, and withdrawable at any time. We use the stricter standard because a prompt to share sits close to direct marketing, even though it concerns your own memorial
Optional Once Spoken email permission — held by your email address To send occasional first-party email about Once Spoken’s memorial features, its own products and services, special offers, and ways to support the project. It never covers third-party marketing or sale of the address Consent — separately and actively chosen, confirmed through the address, recorded with the exact wording, version, date, source and confirmation, and withdrawable at any time. It is held by the address rather than by a memorial. We stop promotional sends when the recorded permission reaches its two-year review point unless it has been refreshed
Optional permission for us to ask about a memorial’s story — held by that one memorial To write to you and ask whether you would tell us more about that memorial, or whether its story could be featured. It is permission to ask, and nothing else: anything we would then use would be agreed with you separately first Consent — asked for separately on the form, recorded with its wording and its date, and withdrawable at any time. Given per memorial, so it says nothing about any other memorial you may have submitted
Consent records — which permission, granted or withdrawn, when, the wording shown at the time, and whether it was later withdrawn To honour each choice accurately, and to be able to show what was agreed and when if it is ever questioned Legal obligation, and legitimate interests: the law that makes consent the basis for the messages above also requires us to be able to demonstrate that consent was given. Keeping the record is how we do that. See how long we keep it
Preference links — a one-way fingerprint of the link in an email, and when it was issued, used or turned off To let the person who received one of our emails see and change their email choices without an account, a password or a sign-in Legitimate interests: making withdrawal at least as easy as giving permission in the first place. We store a fingerprint of the link rather than the link, so the record cannot be turned back into a working link by us or by anybody who obtained it
Contact form messages To read, answer and act on what you have asked us Legitimate interests: responding to the person who chose to write to us
Partnership application, review record and private status capability To assess an organisation’s application, tell its applicant what happened, administer an approved relationship and prevent duplicate or abusive applications Legitimate interests: operating a carefully reviewed referral programme and responding to an organisation that chose to apply. The status capability is stored only as a one-way fingerprint, and application email is operational rather than marketing
Partner referral reference, the approved link used, and whether a memorial submission followed it To give approved partners anonymous evidence that sharing the service is useful, and to understand whether the programme reaches families Legitimate interests: measuring a referral programme without disclosing family information or building a profile. The browser holds an opaque capability in that tab only; the server record contains no IP address, user agent, name, email address or device detail. You can object at any time
Living people appearing in memorial content Publishing an approved memorial Legitimate interests in operating a memorial service, balanced against that person’s rights — if you are that person, tell us and we will act
Analytics events — the page or memorial viewed, the referring hostname, campaign labels, an approximate country, voice-journey stage names, and the pseudonymous hashes used to count visits To understand how the site is used, whether our outreach reaches anybody, how people find the memorials, and where the optional voice journey works or fails Legitimate interests: understanding and improving a site whose entire purpose is that memorials are found. We have kept it to the least information that answers those questions, store no identifier on your device, and use none of it for advertising or profiling. You can object at any time
Sharing and attribution records — the memorial shared, the arrival through a shared link, the random reference for that arrival, and whether a candle, submission, paid contribution or further share followed it within two hours To see whether sharing a memorial brings anybody here, and whether the people it brings go on to take part Legitimate interests: understanding whether the sharing this site depends on actually works. It holds no identifier of a person, stores nothing on your device, is limited to two hours, and is used for no advertising or profiling. You can object at any time
Project sharing records — that Once Spoken itself was passed on from the page that invites it, and whether the words were copied or handed to another application To see whether the people who want more families to find the site are actually able to pass it on Legitimate interests: knowing whether that page does anything at all. It holds no memorial, no identifier of a person and nothing about you, stores nothing on your device, and is used for no advertising or profiling. You can object at any time
Provider technical logs Security, fault diagnosis and keeping the service running Legitimate interests: keeping the site available and secure

We do not ask for, and do not want, information that reveals a living person’s health, religion, beliefs, sexuality, politics or ethnic origin. A memorial is a name, two years, a photograph and something the person said — nothing on the form asks for more than that. If you believe a published memorial reveals something of that kind about a living person, tell us and we will take it out of public view while we look at it.

We do not use your information to make automated decisions about you, and we do not profile you.

The emails we send you

There are two quite different things an email address can be used for, and Once Spoken keeps them apart. A few messages sit between them, and every one of those is optional, asked for separately, and set out here and under your email choices.

Messages about something you did. If you submit a memorial, we may write to you about that submission — to confirm we have received it, to tell you it has been approved and give you its permanent link, to let you know when somebody has lit a candle for the person you submitted, to ask you something we need to know in order to review it, to tell you if we cannot publish it, or to reply to a message you sent us. These are service messages about your own submission. They are the reason we ask for an address at all, and they are not optional in the way marketing is: if you would rather we did not write to you about a memorial you have submitted, tell us and we will note it, though it may mean we cannot tell you what happened to it.

Partnership application messages. If you apply on behalf of an organisation, we send a receipt containing its reference and private status link, then an approval or decline message after a person reviews it. These are operational messages answering the application, not marketing. They carry no tracking pixel or click tracking. You do not need to agree to promotional email in order to apply, and applying does not create that permission.

Marketing. Once Spoken may send its own occasional promotional email only where the address holds a current, confirmed permission covering the subject of that message. Giving us an email address to submit a memorial is not that permission. We do not sell or rent addresses, pass them to a partner, advertiser or agency for their marketing, or treat acceptance of the terms as consent. No permission on this site covers third-party marketing.

The optional first-party choice. The relevant tick names the categories it covers: Once Spoken’s memorial features, its own products and services, special offers, and ways to support the project. It starts empty, is separate from the terms and from submitting a memorial, and requires a second, deliberate confirmation through the email address before it becomes sendable. Every promotional message includes a preference link. The exact wording and version are recorded, and an older, narrower version stays narrow.

A private link to manage a recording — only when you ask for it. A signed-in manager can request a single-use, expiring link from My Once Spoken. The existing route for an original submitter also remains: if the memorial and email address match our private submission record, the link is sent to that address. The public reply is identical whether a pair matched or not, so it cannot be used to test who submitted a memorial. Following a link changes nothing by itself; adding, withdrawing or removing anything needs a deliberate action, so a mail scanner or preview cannot act for you. This is a service message about a memorial you manage, not marketing and not sent under an optional marketing tick.

Candles. If somebody lights a candle for a person you submitted, we may tell you — the first time it happens, and then only at a few widely spaced totals after that. There is no message for every candle. We never tell you who lit it, because we do not know: a candle is counted, never signed. If you would rather not hear about candles at all, tell us and we will stop.

One reminder about sharing — only if you asked for it. The submission form carries an optional tick asking us to remind you about sharing the memorial. If you ticked it, then a few days after the memorial is published, and only if nobody has yet shared it using the site’s own share buttons, we may send you one email with the words already written so that you can pass it on. Everything about it is deliberately narrow:

We call this a reminder you asked for, rather than a service message, and we ask for it separately instead of reading it into the address you had to give us. We are not going to tell you it is certainly outside the rules that govern marketing email; the honest position is that a message inviting you to share something sits close to that line, however gently it is written. So it has been built as though the stricter rule applied: asked for in advance, in its own words, on its own tick that changes nothing else; never sent to anybody who did not tick it; sent once; stoppable from inside the message; and never sent to an address that has asked us to stop. If you would rather it had not been sent to you, saying so is enough — we will not ask you to justify it.

Who carries these messages. All of them, including optional marketing and the sharing reminder, are sent for us by Resend, an email delivery provider. For each send they receive the destination address and the message. We keep the consent ledger ourselves, do not upload an audience or contact list to Resend, and send one addressed message at a time. Our messages carry no tracking pixel and no click tracking, so opening one, or not opening it, tells us nothing.

If Once Spoken ever wants permission for a materially different purpose — including any third-party marketing — it will be asked for as a new, separate choice, in its own words, at the time. It will never be taken from a permission given for something else, an earlier wording version, acceptance of the terms, or silence. The database records which topics each wording version covers and checks that scope before a promotional send. We also stop treating marketing consent as sendable at its two-year review point unless it has been refreshed, and we honour a withdrawal immediately.

The optional social media permission on the submission form is a separate thing again, and is not an email choice at all: it is about using the memorial in our own promotional material, not about sending anything to you. You can give it, decline it, or withdraw it at any time, and none of that affects whether the memorial is published.

Your email choices

The submission form has a small section headed Email choices — optional holding three ticks. This is what each one means, who or what it belongs to, and how to change it. Two things are true of all three:

One reminder about sharing — this memorial

“Send me one reminder to share this memorial if I haven’t shared it after three days.”

This one belongs to the memorial you were submitting when you ticked it, not to you. If you submit two memorials, you make the choice twice, and the answer for one says nothing about the other. What it permits is a single email, once, and only while it is still true that nobody has shared that memorial through the site — set out in full, with every limit on it, under the emails we send you above.

Occasional Once Spoken email — your email address

“Email me occasionally about Once Spoken’s memorial features, its own products and services, special offers, and ways to support the project. Once Spoken only. No third-party marketing. We never sell your email address. I can unsubscribe at any time.”

This one belongs to your email address rather than to a memorial. It is the only choice on the form that works that way, and it means you give it once rather than once per submission: if you have sent in several memorials, ticking it on one is a permission for the address, and withdrawing it withdraws it for all of them at once. It is not attached to any memorial and does not appear in any memorial’s record as a permission about that memorial.

What it does permit:

What it does not permit, and cannot be read as permitting:

There are further protections built into it. Because a permission held by an email address is only as good as our knowledge that the address is really yours, we do not make it sendable merely because a link was opened. The landing page repeats the exact choice and somebody must press its confirmation button; an automated mail scanner’s visit changes nothing. Until that happens the permission is recorded but not acted on. We keep older wording versions separate: the permission used from 7 September 2026 covered memorial features only, so it does not authorise products, services, offers or support. A current choice can also be made directly at Email updates & offers.

Permission for us to ask about a memorial’s story — this memorial

“You may contact me if Once Spoken would like to hear more about this memorial or consider featuring its story.” With, underneath it: “This allows us to ask. We would still agree the details with you before using anything new.”

This one belongs to that one memorial. If you have submitted more than one, you decide separately for each, and giving it for one is not giving it for another.

It is worth being exact about how narrow it is, because “featuring its story” could be read broadly and should not be:

Changing or withdrawing any of them

Every ongoing Once Spoken marketing message carries a link to an email-preference page. Opening it shows what the address currently permits, lets you turn the permission off, and offers one control that stops all optional email for that address. The single sharing reminder instead explains how to reply STOP or contact us. Preference links need no account or password, expire and can be revoked; memorial-specific choices appear only when the link also proves authority over that memorial.

You do not have to use it. Telling us through the contact form works just as well and reaches a person. Either way we do not ask you to explain yourself, and we do not make you confirm it twice.

Stopping optional email does not stop the necessary messages about a memorial you submitted — that it was received, that it was approved, that we need something from you. Those are the answer to something you did rather than something we are selling, and they are described under the emails we send you. If you want those stopped too, say so and we will, with the honest warning that we may then be unable to tell you what happened to your own submission.

What we keep, and what stays private

For every one of these choices we record the permission itself, whether it is currently given or withdrawn, whether it belongs to your address or to a particular memorial, the date, the exact wording and version shown, the source of the choice, the privacy-notice version, and — for address-level marketing — when that exact grant was confirmed. If you withdraw it, we record the withdrawal and its date and keep the record of the original permission. The law requires us to be able to demonstrate what consent existed when an earlier message was sent. The historical record does not keep permission alive: the send boundary reads the current answer, confirmation, topic scope, age and suppression status, never merely the history.

None of it is public. Consent records, your email address, and the preference links are not shown on any memorial, not in the page a memorial is built from, not in what search engines or social networks read, not in the sitemap, not in our analytics, not in anything our payment provider is given, and not returned by the public parts of our database. A visitor cannot read them. A memorial manager can see the email addresses and roles of that memorial’s other managers, but not its consent ledger or unrelated submitter details. Only an administrator can see the current permissions for a memorial, and that view is limited to what is needed to honour them.

Who else is involved

We do not sell personal information and we do not share it for anyone else’s marketing. We do rely on a small number of service providers to make the site work at all:

ProviderWhat it does for us
NetlifyHosts this website and serves its pages
SupabaseStores memorials, submitted photographs, account and management records, funding choices, contribution records, contact messages and our own analytics events, and handles passwordless user and administrator sign-in. Any voice recording you send is held there too, in private storage that the public site has no general read access to
StripeProcesses a voluntary contribution when you choose one. Stripe receives the amount, currency, our contribution reference and the payment details you enter on its page. We receive the resulting status and Stripe references, not your full card number or security code
ResendDelivers the emails described above — service messages about your submission and optional messages you have actually requested. For a send they receive its destination address and content. They are not given our database or consent ledger, and we do not upload a reusable contact list or audience to them
jsDelivrA public code network that delivers one software library the site uses; your browser requests that file from them, so they receive your IP address

No recording goes anywhere else. There is no transcription service, no speech-recognition service, no artificial-intelligence service and no media-processing company anywhere in this list, and none is used behind it. A recording you send is stored by Supabase, listened to by one administrator, and served — if it is approved and published — by this site’s own servers reading it out of that private storage. It is not handed to anybody to train anything, and nothing on this site is capable of doing so.

We may also disclose information where the law requires it, or where it is necessary to establish, exercise or defend a legal claim — for example where someone alleges that a photograph was published without their permission.

There is nothing else. Once Spoken keeps its own limited contact-and-consent ledger so it can prove and enforce each choice; it does not maintain a promotional audience inside Resend or another newsletter, campaign, customer-relationship or advertising platform. Messages you send through the contact form are stored with Supabase and read in the administration area of this site. If we reply by email, that reply and your address will also sit in the ordinary email account it was sent from, like any other correspondence.

Where information is held

Our providers are international companies and may process information outside the United Kingdom, including in the United States.

Before we use a provider for restricted transfers, we record the provider, data, destination and the account-specific safeguard in our processor register. Depending on the provider and destination, that may be a UK adequacy regulation, the UK International Data Transfer Agreement, or the UK Addendum to the EU Standard Contractual Clauses, together with appropriate security measures. We retain the applicable agreement and review provider and subprocessor changes. Ask through the contact form if you want information about the safeguard applying to your data.

How long we keep it

A published memorial is intended to be permanent. That is what people are asking us for when they submit one, and it is the point of the site: that someone might still come across that face and those words many years from now.

Everything else is kept only as long as it is useful:

Apart from those 180 days, we have deliberately not put a fixed number of months against each of these, because a figure invented for the sake of looking precise is worth nothing to you. The rule is the one above: something is kept while there is a reason to keep it, and deleted when there is not. If you want to know what we still hold about you, ask, and we will tell you.

Cookies and storage on your device

This site does not set any cookies. There is no advertising and nothing that follows you between websites. The analytics described above is our own and stores nothing on your device at all — no cookie, no local storage entry, no session storage entry, and no identifier of any kind — so there is nothing about it to ask your permission for. That includes the sharing measurement: the &via=share word travels in the link itself, is read once as the page opens and is then gone, and is never written to your device. It also includes the reference used to count what happens after a shared link — it is held in the memory of the open page and nowhere else, so closing the tab or reloading the page discards it, and no cookie, local storage entry or session storage entry is created for it at any point. The same is true of the invitation you may be shown after arriving through a shared link, and of the page for passing Once Spoken on: neither writes anything to your device and neither reads anything from it. That is why you have still not been shown a cookie banner: consent of that sort is about storing or reading things on your device, and the measuring we do neither stores nor reads anything there.

A small number of items are stored in your browser’s own local or session storage, so that the site remembers what you have done on it or can complete a partner-link journey you deliberately opened. None of them is a cookie, none is shared with another website, and none is used to advertise to you or to follow you anywhere:

NameWhat it is
memoryflame_visitor A random identifier created by your own browser, so that lighting a candle for the same person twice is not counted twice. It is sent to our own database with a candle, and only for that purpose. It contains no name, no email address and nothing else about you, it is not shared with any other website, and it is not used to track you. The name is left over from an earlier version of this project and has been kept so that candles already lit are not lost.
oncespoken_candles_lit A list of the memorials this browser has already lit a candle for, so the candle still shows as lit when you come back and a repeat tap changes nothing. It holds memorial references only — nothing about you.
oncespoken_pending_submission Written only if you start filling in the submission form, so that a refresh, a lost connection or an impatient second tap does not create the same memorial twice or lose what you typed. It holds what you entered on the form until the submission is finished, and is then cleared.
oncespoken_pending_contribution and oncespoken_pending_support Random, single-purpose references kept while a voluntary payment is open, so returning from Stripe can confirm the correct attempt and a repeat tap cannot create a second one. They are not proof of payment, contain no card details and are cleared when the journey settles.
Supabase sign-in token Stored only after you deliberately sign in to My Once Spoken or the administration area. It keeps that browser signed in and lets the database enforce which private memorial-management records it may read or change. Signing out clears it; its technical name is chosen by Supabase.
oncespoken_partner_application Session storage only. If you open the private link for a partnership application, it keeps that application reference and its random capability available to the current tab so the status page can load. It is removed when the tab is closed and is not analytics.
oncespoken_partner_referral Session storage only. If you deliberately follow an approved partner’s link, it holds that link’s code, the partner’s public name, an expiry time and an opaque server-issued capability. It lets a completed memorial be counted in the partner’s anonymous totals, contains no family or memorial information, is cleared after a confirmed submission, and disappears when the tab is closed.

We consider each of these strictly necessary for the thing you are choosing to do — lighting a candle, submitting or managing a memorial, completing a chosen contribution, checking an application or using an approved referral link — which is why none is used for advertising or cross-site tracking. You can clear them at any time through your browser settings; the site will simply start again next time, though clearing a sign-in or private capability means you will need to sign in or reopen its link again.

Your rights

If you are a living individual whose personal data we hold, you have the right to:

These rights have limits and exceptions in the legislation. If we cannot do what you have asked, we will tell you why.

We do not charge for dealing with a request, and we aim to respond within one month.

Corrections, changes and removal

Separately from the legal rights above, you can simply ask. Please contact us if you would like a memorial corrected, a photograph changed or taken down, or a memorial removed altogether — or if you believe something has been submitted that should not have been, or was submitted by someone with no right to do it.

Tell us the name shown on the memorial and, if you can, your relationship to the person. It helps us act quickly and helps us be fair to everyone involved. Every message is read by a person.

A voice clip. Ask us to take one down and we will, whether you submitted the memorial, appear on the recording yourself, or hold the rights in it. There are two routes and both work: the contact form, or — if you submitted the memorial — a link emailed to the address already recorded against it, described under the emails we send you. Public access ends when we act, not on a schedule. Where a family disagrees about a recording, we will normally take it out of public view while we work out what is right rather than leave it up and argue about it.

Where a request concerns a memorial submitted by someone else, we may need to weigh up more than one person’s wishes. We will be straightforward with you about what we decide and why.

Children

Once Spoken is not designed specifically for children, but children may visit public memorials or receive a family invitation to contribute. We therefore use the same child-safe, high-privacy defaults for everyone: contributions are private and pending, contact details are not public, there is no behavioural advertising or profiling, and harmful material can be reported by a child or responsible adult. We assess the service against the ICO Children's Code. If a child has shared personal information or may be at risk, contact us; we will restrict harmful exposure promptly and decide correction, retention or deletion in the child's best interests and in accordance with any safety or legal evidence duties.

Security

Managing a memorial and entering the administration area both require verified sign-in. Row-level access rules limit an ordinary account to memorials it manages, its own saved memorials, contribution history and requests; administrator-only information — such as raw submitter details, consent records and the list of people who asked us not to write — is not readable through the public site. Invitation and private-link secrets are stored only as one-way fingerprints. Photographs and memorial records are held with Supabase, and the site is served over an encrypted connection.

We have described only what we can point to. No website can promise that information will never be compromised, and we would rather say that plainly than make a claim we cannot stand behind.

Complaints

If you are unhappy with how we have handled your information, please tell us first — it is usually the quickest way to put something right.

You also have the right to complain to the UK’s data protection regulator, the Information Commissioner’s Office. Its route for a complaint about how an organisation has handled your personal information is ico.org.uk/make-a-complaint/data-protection-complaints, and its helpline is 0303 123 1113.

Changes to this policy

If this policy changes, we will update the date at the top of the page. If a change materially affects how we use information you have given us, we will make that clear rather than quietly editing the text.

How to contact us

You can reach us through the contact form on Once Spoken. Choose the option that best matches what you need — including asking for a memorial to be removed — and a person will read it.