Where your CV lives, and who can see it.

Publishing puts your CV at getfolio.cv/cv/your-name and anyone with the link can open it. Search engines are allowed to index it — we don't block crawlers on published CVs.

That's the point rather than a side effect: the reason to have a CV at a URL is that you can send it to someone, and they can find it later without an attachment.

The editor, your dashboard and the sign-in pages are blocked from crawlers. Only published CVs and the marketing pages are indexable.

CVs are rows in a Postgres database (Neon, reached through Vercel). Profile photos and images on roles are stored as files on Vercel Blob. Everything is hosted on Vercel.

Drafts you haven't published are different: they live in your browser's local storage and never reach the server until you press Publish.

You can publish without signing up. When you do, we generate a random key for that CV and store it in your browser. That key is what proves you own the page, and it exists nowhere else.

So if you clear your browser data or move to another device, the CV stays online but you can no longer edit or delete it. Signing in attaches the CV to your account and removes that risk — the page and its link don't change.

We use PostHog for product analytics, and only when the app is configured with a key — a local or self-hosted copy with no key set records nothing at all.

When it is on, it records:

• page views and page exits
• a fixed list of product events — a CV published, a link copied, a Pro feature's locked state seen, checkout started
• PostHog's default autocapture, which records clicks and form interactions as anonymous events

Person profiles are only created for signed-in users. We don't sell data and there are no advertising trackers on the site.

Nothing is deleted. Your CVs stay live at their URLs and your data is untouched. What changes on the published page:

• images on your roles and rich link previews stop showing
• PDF export turns off
• the “Made with Folio” badge comes back
• a claimed subdomain stops resolving — the name stays reserved for you, not released to anyone else

Everything returns if you subscribe again.

You can delete any CV from your dashboard at any time, which removes the row and takes the page offline. Deleting your account is handled through your account settings.

There is no one-click data export yet. It's listed on the changelog under what isn't built, rather than implied here.