Cookies and storage
Storage used to keep the site and sample workspace working.
Draft updated 10 October 2026. Operator and production details require legal review.
What we store
The current site has no advertising, analytics, or session-replay scripts. It uses first-party storage for the sample workspace, saved card designs, reminder settings, and sign-in security when accounts are enabled.
| Cookie | Purpose and mode | Configured lifetime |
|---|---|---|
ohdearly_sample_workspace | Stores sample people, notes, dates, promises, gifts, and workspace settings in this browser. It is readable by the server and unavailable to page scripts. | 30 days from the latest update, or until reset or cleared. |
__Host-ohdearly_session | Authenticates a signed-in session when production authentication is enabled. Secure and HTTP-only. | 15 minutes by default; configurable up to 1 hour. |
__Host-ohdearly_csrf | Protects authenticated change requests against cross-site request forgery. Secure; readable by the application. | Same as the associated session. |
__Host-ohdearly_login | Protects a sign-in attempt when the authentication flow is enabled. Secure and HTTP-only. | 10 minutes. |
Browser database
The browser database keeps saved card designs, the meeting-alert setting, and a record of alerts already shown. This data stays in the browser unless a feature states otherwise.
Remove browser data
Use Reset workspace in People to remove the sample cookie and discard its changes. Your browser's site-data settings can remove the other local records or block cookies. Blocking required cookies can stop sign-in or sample changes from working.
Clearing a browser cookie does not delete a production account, backend records, downloaded files, or data a merchant holds about a purchase.
Other websites
Gift and nearby-service links may open independent websites. Their own cookie notices and privacy terms apply there.
Future changes
Optional tracking would stay off until any required consent is collected. The current site has no consent banner because it does not use optional tracking.
See the privacy notice for how relationship data is handled.