PRIVACY & LOCAL DATA
Your coffee stays here.
DayCup uses local rules to calculate recipes. It has no account, AI calls, analytics SDK, required API key or automatic upload of your records or photos.
Your equipment, beans, photos, recipes, notes and feedback live in this browser profile. A downloaded HTML file contains the app and its catalogues, not the records you add later. Export a JSON backup from My data before changing browser or device, or clearing browser data.
Photos are cropped and compressed on your device. They are included in backups. Replacing or removing a photo removes the older image from the current library; previously exported backups still contain their original photos. Import photo backups into DayCup 2.3 or newer.
Local records and exported JSON are not encrypted. Anyone using this browser profile can access them. A SideCourt subpath is not a separate security origin; trusted scripts on the same origin can access its storage.
Older account libraries remain separate on this device. Recovery is explicit. DayCup does not sign in to the old service or automatically merge those records. Clearing this local library does not delete cloud records.
Manufacturer links open only when you choose them. A hosted edition requests static app files from its host, which may retain access logs under its own policy.
Without a backup, clearing local data is permanent. Persistent storage is a best-effort protection. Private browsing is not a reliable long-term library.