Privacy overview
Domenill is designed around local-first records, explicit permission, visible memory, and approval before sensitive external action.
In the private build, the Mac runs the personal engine and stores app records such as captures, tasks, memories, approvals, and connected-source records under the user’s control. The iPhone experience connects to that trusted Mac.
Domenill does not need an advertising profile or data broker to work. The product direction is local-first and no-ad.
Email, calendar, files, devices, and other sources are optional. Where available, they require explicit setup and supported permission paths. A disconnected or unavailable source should be labeled honestly.
Domenill is built so users can inspect the personal context it carries forward, correct it when it is wrong, and remove it when it is no longer useful.
Domenill.com uses no advertising network or tracking pixel. When you submit the waitlist form, the site stores the information you choose to provide: email, optional name, optional Mac/iPhone answers, optional interest and daily-life friction answers, signup time, country, referrer, and limited browser information used for waitlist operations and abuse prevention.
That information is used only to manage private beta access and send important Domenill product updates. It is not sold. To request access, correction, deletion, or removal from updates, email admin@domenill.com.
Domenill may organize, summarize, draft, and prepare. Sensitive sends, posts, purchases, bookings, submissions, account changes, and similar actions should wait for explicit per-action approval.
This privacy overview describes the private beta posture. It will be updated before a new hosted service, analytics system, account system, or materially different data flow is introduced. Important changes will be dated here.
