I built Homemarks for myself and I'm sharing it for free. This is not a professionally drafted privacy policy, and you should not assume the same guarantees, audits, or support you'd get from a paid product.
Homemarks stores the minimum data needed to operate: your Google account identifier and email address (to identify your account), plus the bookmarks you save and basic usage data like click history (to sort and improve your experience).
I do not sell your personal data. I have no intention of ever doing that. But I'm also making no promises that nothing will ever change, and you should assume this service could be modified, paused, or shut down at any time.
I try to protect the data I store, but I can't guarantee security. No system is perfectly secure, and you use the service at your own risk. If you're not comfortable with that, don't use Homemarks.
Some functionality relies on third parties. Sign-in uses Google. To create a concise bookmark title, Homemarks fetches page metadata and sends the bookmark URL and that metadata to OpenAI with response storage disabled. For a newly added or manually refreshed low-resolution favicon, Homemarks may also send the discovered favicon's processed PNG and the bookmark URL to OpenAI to reconstruct a higher-resolution version. If direct favicon discovery fails, Homemarks may ask Google's or DuckDuckGo's favicon service for a fallback. Embedded URL usernames and passwords are removed before all title, favicon, third-party, and debug-log lookups; the remaining URL, including its path, query, and fragment, may still be processed. Requests to those providers are governed by their own policies.
I don't send marketing emails. If I ever need to contact you about a serious operational or security issue, I may not be able to.
By using Homemarks, you agree to this level of privacy and these limitations.