Privacy

This explains what Place a Stone stores, why, for how long, and what you can make us do about it. It is written to be read, not to be survived.

Updated 13 September 2026

Who is responsible

Place a Stone is operated by Codama. Contact: info@codama.dev.

For the purposes of the GDPR, Codama is the controller for account data and for the operation of the service. A memorial’s steward decides what goes on their page; for that content we act on their instructions.

What we store

An account: your email address, your display name if you give one, and the language you read in.

A memorial: the name, dates, places, biography and photographs entered by its stewards, and the memories, photographs, recordings and documents contributed by others.

A contribution: the text, any attached files, the contributor’s name if given, and their email address if given.

A salted, one-way hash of the IP address of anyone who submits something without an account, or lights a candle. We cannot recover the address from it. It exists only to stop one person flooding a page.

Nothing else. There is no advertising identifier, no behavioural profile, and no third-party analytics on a memorial page.

What we never do

A contributor’s email address is never shown on a page and never used for marketing. It is collected for one purpose: telling that person whether their memory was published.

There are no third-party advertising or social pixels on a memorial page. Not now, not later. No Facebook pixel.

GPS coordinates are stripped from every uploaded photograph, unconditionally, before it is stored.

Where a contributor is under 16, their surname is never displayed, and a steward must have explicitly enabled contributions from minors at all.

How long we keep it

The IP hash: 90 days, then deleted.

A contributor’s email address: for as long as the contribution it belongs to exists.

Identity verification: we store the verification provider’s reference and its outcome for seven years, because a dispute over who had the right to a memorial can arrive years later. We never store the identity document itself.

A memorial and its contents: until a steward deletes it, or asks us to.

Where it lives

The database and the uploaded files are hosted in the European Union (Frankfurt). The application servers are operated by Railway and the marketing site by Cloudflare.

Outbound email is sent through Infobip. Only the recipient address and the message itself are shared with them.

We have a data processing agreement with each of these, and we will publish the full subprocessor list before adding any new one.

What you can ask for

A copy of everything: every memorial has a one-click export that produces the full-resolution photographs, every word, the structured data, and a self-contained page that opens with no internet connection. It is not a support request; it is a button.

Deletion: a steward can delete a memorial. If you contributed to someone else’s page, you can ask us to remove what you wrote or to detach your name from it, and we will tell you which we have done.

Correction, restriction and objection, as the GDPR provides. Write to info@codama.dev.

If you believe we have handled your data badly, you may complain to a supervisory authority in the country where you live.

Content that should not be there

If something on a memorial is abusive, untrue, or invades the privacy of a living person, write to info@codama.dev. We respond within 72 hours. Where a complaint is credible on its face, the content comes down first and is reviewed afterwards.

Cookies

A session cookie when you are signed in, and a cookie remembering which language you chose. Both are strictly necessary; neither follows you anywhere.

If we ever add analytics it will be a self-hosted, EU-resident one with no cross-site tracking, and this page will say so before it happens.