Data & privacy

Fig Almanac is a journal first. These notes describe how your data is handled, in plain language. The short version: what you add is yours, it starts private, publishing is always your explicit choice, and we don’t sell anything to anyone.

What we store

Your email address (used only to sign you in — login is by emailed link, so there’s no password to store), your chosen handle and profile details, and the culture entries — the figs— you add: books, films, music, podcasts, shows, performances, places, and the notes and images you attach to them. If you connect an outside service to import listening or watching history, we store what’s needed to run that sync and the data it returns.

Private by default

Everything you add is visible only to you until you decide otherwise. Publishing works at three levels: your whole almanac, a single category (say, just your books), or an individual fig. Anything you don’t publish stays private, full stop. You can unpublish at any time, though pages already seen or indexed elsewhere may take time to fall out of caches.

Cookies

One cookie, for keeping you signed in. No advertising cookies, no cross-site trackers, no fingerprinting.

Who else touches the data

Fig Almanac runs on a small set of infrastructure providers: Vercel (hosting), Neon (database), Resend (transactional email), and Cloudflare (DNS). Each processes data only as needed to run the service. Basic, aggregate hosting analytics may exist (page counts, not people). No data is ever sold or shared for advertising.

Your data is yours

You can export everything you’ve added as a spreadsheet, and you can ask for your account and all its data to be deleted — permanently, from the live database. (Encrypted backups age out on their own schedule.) For either, use the contact page while account tooling is still growing.

Beta honesty

Fig Almanac is in an invite-only beta. Features described here — publishing controls, exports, deletion — are being built in the open, and this page will be updated as they land. If anything here changes in a way that affects your data, you’ll hear about it by email first.

Last updated July 27, 2026.