SmellBook
Menu

TECHNOLOGY & PRIVACY

Keep the public atlas simple enough to understand.

SmellBook’s current website architecture deliberately avoids unnecessary client frameworks, trackers, embedded third-party widgets and device permissions.

01

Server/static first

Most public discovery remains server/static. Four audited client components support the optional Personal SmellBook, which is kept only in your browser, and one copies citations to the clipboard.

02

Three runtime dependencies

The current runtime dependency set is Next.js, React and React DOM.

03

No analytics SDK

SmellBook does not currently include a website analytics SDK in the public runtime.

04

No advertising SDK

The public website contains no ad network or behavioral advertising library.

05

No authentication SDK

The local personal layer needs no account. The public website still does not ship an authentication framework.

06

Local storage only

One versioned record, kept only in your browser, stores what you choose to save in the Personal SmellBook. No cookies or server sync are used for that record.

07

No map service or device sensors

The public website does not request camera, microphone or geolocation permissions and does not ship a map SDK.

08

External sources are links

Scientific source links can leave SmellBook for DOI/publisher pages, but those publishers do not run embedded scripts inside SmellBook pages.

FUTURE FEATURES

New capability should justify new runtime cost.

If accounts, cloud sync, analytics or other personal-data services are added later, the public privacy and architecture pages should be updated before those capabilities are treated as normal.