Privacy Policy

This policy describes how Stone & Crumb handles information. It only describes practices that are actually in place. Where something is not done, this page says so rather than reserving the right to do it later.

What this site is, technically

Every page you read here is a pre-built HTML file. There is no application server, no database, no content management system, and no login. Nothing you do while reading is sent anywhere by the site itself.

Cookies and similar storage

This site sets no cookies. It does not use local storage, session storage, or browser fingerprinting. There is no consent banner because there is nothing to consent to.

The site loads two first-party scripts. One writes the current year into the footer, opens and closes the section menu on narrow screens, and makes the contact form display the editorial desk's email address after submission. The form does not open an email application, send a message, or store its fields. The other script controls the optional viewport reveal animation. Neither script stores reading activity or sends page-view data anywhere.

Who is responsible for this site

Stone & Crumb is operated by its publisher, who decides what is published here and who is responsible for the limited data handling described on this page. The publisher can be reached through the Contact Us page, which provides a direct mailbox and a local form that displays the mailbox address after submission. The form does not send or store its contents.

Analytics

There is no analytics product on this site. No page-view counter, no heatmap tool, no session recorder, no tag manager, and no measurement pixel. Nobody here can see which articles you read.

Advertising

Advertising may be used to support the publication, including through Google's advertising services. Advertising technology may use cookies or similar identifiers to deliver and measure ads, subject to the choices and consent required in a visitor's region. This policy will name material changes to advertising vendors, storage, or data use before they take effect.

Google's advertising controls are available to readers, and the relevant links are given here:

• Turn off personalised advertising across Google services: Google My Ad Center personalisation setting
• How Google uses information from sites and apps that use its services: Google's technologies on partner sites

For the avoidance of doubt about how such advertising works generally: third-party vendors, including Google, use cookies to serve ads based on a user's prior visits to a website, and Google's use of advertising cookies enables it and its partners to serve ads based on those visits. Users may opt out of personalised advertising by visiting the My Ad Center link above. That control sits in your Google account or browser and applies to Google's services broadly, not to this site alone.

Legal bases for the limited processing that occurs

Two kinds of processing happen in connection with this site, and each has a straightforward basis.

Server log data is processed at the hosting layer because delivering a web page technically requires it, and because a host needs it to keep the service secure and available. The lawful basis for that, where European or United Kingdom data protection law applies, is legitimate interests.

Email you choose to send is processed in order to reply to you and to record any correction that resulted. The basis there is the legitimate interest in responding to correspondence you initiated. You are never required to provide a name, and a correction report works perfectly well without one.

No processing on this site relies on consent, because nothing is set or collected that would require it. If that changes, a consent mechanism will be added and this page will describe it.

How long information is kept

Server log entries are retained by the hosting provider for whatever period its own policy specifies. That period is set by the provider, not here, and this publication keeps no separate copy.

Email correspondence is kept in the mailbox for as long as it remains useful for handling the matter raised, and any resulting correction is recorded in the article itself rather than in a database of correspondents. If you ask for your message to be deleted, it will be deleted.

Nothing else is stored, so nothing else has a retention period.

Where processing takes place

Web hosting and email are internet services, which means the infrastructure handling a request may sit in a country other than yours. Any transfer of that kind happens at the hosting and mail provider layer, under those providers' own arrangements and safeguards, rather than through anything configured by this publication.

If you are in the European Economic Area or the United Kingdom

Data protection law in those jurisdictions gives you rights of access, rectification, erasure, restriction, objection, and portability, along with the right to complain to a supervisory authority.

In practice most of those rights have nothing to attach to here, because the site holds no personal data about readers. Where they do apply, there are two routes. For email correspondence, write to the editorial desk. For server log entries, the rights are exercised against the hosting provider, because that is where the processing takes place.

If you are in California

The California Consumer Privacy Act gives residents rights to know what personal information is collected, to have it deleted, and to opt out of its sale or sharing.

The site does not sell or share personal information for money. Advertising partners may process limited online identifiers as described above to deliver or measure ads, subject to applicable law and consent requirements. Where a regional opt-out or do-not-sell/share mechanism is required, it will be provided through the applicable consent controls.

Third-party requests

Loading a page here requests only files served from this site: the HTML document, one stylesheet, two first-party scripts, and the article's cover image. There are no third-party fonts, no embedded videos, no social media widgets, and no external image hosts. Your browser is not asked to contact another company in order to display an article.

Articles do link out to cited sources. Following such a link takes you to a site with its own policies and its own data practices, over which this publication has no control.

Hosting and server logs

The files are served by a hosting provider. Like effectively every web server, that provider's infrastructure processes the technical details required to deliver a page, which typically include the requesting IP address, the time of the request, the file requested, and the browser's user-agent string. That processing happens at the hosting layer and is governed by the provider's own policy and retention period, not by anything configured here. This publication does not maintain a separate copy of those logs, does not build profiles from them, and does not combine them with any other information.

Email you send

If you write to the editorial desk, that message and the address it came from are held in the mailbox for the purpose of replying, and for keeping a record of any correction that resulted. Correspondence is not added to a mailing list, is not used for marketing, and is not shared with third parties. There is no newsletter to subscribe to.

Please do not send sensitive personal information by email. A correction report needs the article and the claim, nothing more.

Children

This site is a general-interest reference publication about bread. It is not directed at children, and it collects no information from anyone, including children.

Your choices

Because no personal data is collected by the site, there is no account to delete, no profile to correct, and no tracking to opt out of. If you have written to the editorial desk and would like that correspondence deleted from the mailbox, ask and it will be removed.

Rights over data processed at the hosting layer, such as server log entries, are exercised through the hosting provider, since that is where the processing occurs.

Changes to this policy

If any of the above changes, the change will be made on this page and the updated date at the top will move. A change that introduces data collection, analytics, or advertising will be described specifically rather than covered by a general reservation of rights.

Questions

Questions about this policy go to the editorial desk through the Contact page.