Privacy notice
How oh, dearly! handles relationship information.
Draft updated 10 October 2026. Operator and production details require legal review.
Who is responsible
The service operator and privacy contact are awaiting confirmation in the imprint. A company using the team workspace decides which client or staff information to enter, why it is needed, and who can access it. Production processing on its behalf requires a data-processing agreement and clear responsibilities.
Information in the app
The public app is a sample workspace. Use fictional records while account storage is not enabled.
| Information | Purpose |
|---|---|
| People | Names, circles, contact details, important dates, and relationship history keep a person's record together. |
| Notes and promises | Likes, dislikes, meeting notes, life updates, and promises support reminders and meeting briefs. |
| Cards and gifts | Ideas, messages, amounts, dates, send status, and reactions keep a history of what was sent or received. |
| Recipient profile | A person can add their own preferences and a private delivery address, choose who may see their profile, and delete it. |
| Team records | Owners, roles, budgets, approvals, and send logs support shared client and staff relationships. |
| Accounts in an authenticated workspace | User identifiers, organisation membership, roles, and session records control access when authentication is enabled. |
| Technical requests | Network addresses, requested URLs, and browser information are handled when the site and its hosting service respond to requests. |
Do not add health, religion, political views, or other sensitive details to business records. Companies must establish a legal basis and give clients and staff the required privacy information.
Why information is used
Information is used to show reminders, prepare meeting briefs, keep promises visible, suggest gifts, create cards, record sends, and support team handovers. Account and security records will be used to control access when customer accounts are enabled.
The operator must document the legal bases for account administration, security, support, and customer records before production launch. Adding someone to a workspace does not record their consent.
Capture and imports
Voice capture uses speech recognition supplied by the browser. The app receives the transcript and does not save a raw recording. The browser or its speech provider may process audio under its own terms. Nothing from a capture is added to a person until the user confirms it.
Calendar imports use an .ics file chosen by the user. The app shows possible matches and saves only confirmed meetings. Contact and connected-account imports are not active on the public sample site.
Suggestions, addresses, and other sites
Suggestions use the information saved about a person. Users review messages, gifts, and scheduled actions before sending unless they have enabled a rule within a set budget. A recipient's delivery address stays hidden from the sender and is used only for delivery.
Gift and nearby-service links may open independent websites. Those sites handle any enquiry, booking, payment, delivery details, and cookies under their own policies.
Storage and providers
The sample workspace stores changes in a first-party cookie and sends that cookie back to the site with requests. Use fictional information in this mode. The cookie notice lists its lifetime and reset controls.
Vercel hosts the public website and processes technical requests needed to serve it. Production database, authentication, email, logging, hosting regions, retention periods, and subprocessors must be confirmed before customer accounts collect real data.
Access, export, and deletion
Subject to the applicable conditions, you can request access, correction, deletion, restriction, and portability of personal data, object to processing based on legitimate interests, and withdraw consent for future processing. You can also complain to a data protection supervisory authority.
Reset removes the sample workspace cookie. It does not delete downloaded files, records held by another organisation, or data on an independent merchant site. Production export and deletion controls require the customer backend and identity service, which are not active on the public sample site. For records entered by an employer or another company, contact that company first.