the small print
privacy,
plainly.
Cuppa is built to be read without an account. It has no advertising, no analytics tracker, and no sale of personal data.
Effective 17 August 2026
1. Who this notice covers
This notice describes how the operator of Cuppa processes data when people visit cuppa.today, when public material is curated into Cuppa, and when the operator uses Cuppa's private administrative features. The operator of Cuppa is the controller responsible for that processing.
2. Information Cuppa processes
Ordinary visits
Hosting and security systems may process standard request data such as IP address, browser and device information, requested page, referrer, timestamps, and diagnostic or security events. Cuppa does not use this information to build reader profiles.
Browser preference
If you switch between the morning and evening themes, the choice is saved as cuppa-theme in your browser's local storage. It remains on your device and is not sent to Cuppa's server.
Public editorial sources
Cuppa collects and curates public articles, feeds, posts, videos, service-status reports, and security advisories. These may include a public author name or handle, published content, media, source URL, publication time, and public engagement information. Cuppa uses this material to rank, summarise, attribute, and publish an editorial digest and live information feed.
Private operator features
The operator can submit saved URLs, record ratings or notes, and connect an X account to import bookmarks. When used, Cuppa stores the submitted material, feedback, OAuth tokens, authorised scopes, bookmark identifiers and timestamps, and synchronisation state. These features are not available to ordinary readers.
3. Why the information is used
Cuppa processes information only as reasonably necessary to:
- deliver, maintain, secure, and troubleshoot the website;
- compile, rank, summarise, and display the editorial service;
- remember a reader's requested display preference;
- authenticate and operate private owner features; and
- comply with legal obligations and protect Cuppa and others.
Where a legal basis is required, this processing relies on Cuppa's legitimate interests in providing and securing the service, on the operator's request to use private features, or on compliance with law. Cuppa does not use automated processing to make legal or similarly significant decisions about readers or public authors.
4. Cookies and local storage
Public reading does not require a Cuppa cookie. The local theme setting described above stays until you clear site data or change it.
Private operator login uses a secure, HTTP-only authentication cookie lasting up to 30 days. An X connection uses secure, HTTP-only verification cookies lasting up to 10 minutes during the OAuth flow. These are functional security measures, not advertising or analytics cookies.
5. Service providers and disclosures
Cuppa does not sell personal data. It uses the following categories of providers:
- Cloudflare and Railway — content delivery, security, application hosting, and database infrastructure.
- OpenAI — ranking and summarising editorial-source material. Owner feedback may be included to personalise those editorial results.
- Langfuse — prompt management and technical observability when this optional integration is configured.
- YouTube/Google and media hosts — embedded or externally hosted media. Loading or playing that media can disclose normal request information to the media provider. YouTube embeds use its privacy-enhanced domain.
- X — only when the operator initiates the private account connection and bookmark-sync features.
Cuppa may also disclose information when required by law, to respond to valid legal process, or to protect the security and rights of Cuppa or others. External links are governed by the destination's own privacy notice.
6. International processing
Providers may process information in Switzerland, the European Economic Area, the United States, and other countries where they operate. Where required, cross-border processing is handled under recognised legal safeguards or another permitted transfer mechanism. Protection rules in a destination country may differ from those where you live.
7. Retention
Technical logs are retained according to operational, security, and provider settings, then deleted or aggregated when no longer needed. Public-source material and its editorial analysis may remain in the Cuppa archive while relevant to the service. Private operator data is kept until removed, replaced, disconnected, or no longer needed for the feature, subject to legal and security requirements. Cookie lifetimes are listed above.
8. Your choices and rights
You can clear local storage in your browser, avoid interacting with embedded media, or follow a source link directly. Depending on where you live, you may also have rights to request access, correction, deletion, restriction, portability, or objection, and to complain to your local data-protection authority.
Requests may require reasonable identity verification. Cuppa may retain information where law permits or requires it, including for security, freedom of expression and information, or legal claims.
9. Security and children
Cuppa uses reasonable technical and organisational safeguards, including encrypted transport and restricted administrative features. No system can be guaranteed completely secure.
Cuppa is a general-audience editorial service and is not directed to children. It does not knowingly request personal information from children.
10. Contact and changes
For privacy questions, requests, or concerns, contact the Cuppa operator through the project operator's GitHub profile.
This notice may change when Cuppa's features or providers change. A material update will be reflected here with a new effective date.