SmellBook.com now includes an optional browser-local Personal SmellBook. Accounts, cloud sync and server-side personal profiles are not live.
What we intentionally collect today
SmellBook does not provide account creation or server-side personal profiles. The optional Personal SmellBook stores explicit saves, preferences, notes and local collections in your browser localStorage. SmellBook website code does not upload that local record to a SmellBook account or server.
Hosting and technical delivery
The site is hosted using third-party infrastructure. Hosting and security providers may process ordinary request information such as IP address, browser or device information, timestamps and requested URLs for delivery, security and operational purposes.
Cookies and tracking
SmellBook does not currently add advertising or behavioral-personalization tracking to the public website. Platform-level technical behavior may change as infrastructure changes, so this statement should be reviewed when analytics, consent tooling or accounts are added.
Search
The public Search page uses the text you enter to match against public SmellBook content. SmellBook’s website code does not build a personal search profile, personalize result ranking or use affiliate commission signals. Search results are marked noindex,follow so query variants do not become search-engine landing pages. Hosting infrastructure may still process ordinary request data as described above.
Browser-local personalization
My SmellBook and Global / Me can summarize explicit state stored only in this browser. You can export it as JSON, import it yourself, or clear it locally. There is no cloud sync, account recovery or server-side deletion request because the current SmellBook server does not store that personal record.
Future accounts and cloud sync
Before accounts, cloud synchronization or server-side personal profiles go live, SmellBook should publish the storage, retention, security, access and deletion model first.
Changes
As the product evolves, this privacy page should change with it. Material changes should be reflected in the public changelog where appropriate.