Privacy, in plain words.
While Fenly is in early access, this covers the waitlist, this website and your account in the Fenly app.
Who we are
Fenly is a design system manager with an AI agent, Pluto. It’s run by Felipe Linares in Bogotá, Colombia. When this page says “we”, that’s who it means. Write to hello@fenly.io about anything here.
The waitlist and this website
Your email address, the answers you choose to give about your team, and who invited you if you joined with a link. No tracking pixels in our emails and no advertising cookies. We keep your theme choice and your spot link in your browser.
Analytics and cookies
Only if you accept in the cookie banner, we use Google Analytics (through Google Tag Manager) to count visits and see which parts of the page work; it sets analytics cookies. If you reject, or your browser sends Global Privacy Control, no analytics cookies are set. Change your choice any time with Cookie settings at the bottom of every page. We never send your email or your answers to Google. The site also keeps your theme, your cookie choice and your spot link in your browser’s storage; these are needed for the site to work and are never shared.
When you sign in with Google
You sign in to the Fenly app (app.fenly.io) with Google, GitHub or your email, through Clerk. If you choose Google, we only ask for your basic profile: your name, email address and profile picture. We use them only to create your account and sign you in. Fenly never gets access to your Gmail, Google Drive or contacts.
We don’t sell Google user data, use it for ads, or let people read it, unless it’s needed for security, the law requires it, or you ask us to. Fenly’s use and transfer of information received from Google APIs follows the Google API Services User Data Policy, including the Limited Use requirements.
What you put in Fenly
Your workspaces, design systems, tokens, components, files and assets, and the comments you leave. It’s yours. We use it only to run Fenly for you: to store it, show it to you and the people in your workspace, and let Pluto work on it when you ask.
How Pluto uses AI
When you ask Pluto for something, we send the design system content he needs to Anthropic (the company behind the Claude models) so he can draft a proposal. Under Anthropic’s commercial terms, API data isn’t used to train their models. Pluto never changes anything on his own: Pluto proposes, a person approves.
Why
To run the waitlist and your account, invite you when your group opens, plan each group and make Fenly work for you. We never sell your data or share it for marketing.
Who processes it
A few services help us run Fenly, and each one only does what we ask. Clerk keeps the waitlist and runs your Fenly account and sign-in. Supabase stores the app’s database and files. Hostinger runs the servers the app lives on. Anthropic provides the AI behind Pluto. Resend sends our emails. Upstash stores invite counts and survey answers. Google Analytics measures visits to this website, if you accept. Vercel hosts this website. Slack gets our internal alerts so we know when something breaks; no customer content goes there.
How long we keep it
Waitlist: until you get access or leave. If you leave, we delete your email and answers right away. Your account and what you put in Fenly: while your account is active. Ask us to delete your account and we delete it, with your content, within 30 days.
Your choices
Leave the waitlist from your spot page at any time. To export your data, correct it or delete your account, write to hello@fenly.io and a person will sort it out.
Security
We keep access to your data to the people and services that need it to run Fenly, and use encrypted connections. No system is perfect, so if something ever happens that affects your data, we’ll tell you quickly and plainly.
Changes
If this page changes, we’ll update the date at the top. If a change matters for your account, we’ll tell you before it applies.
Questions? Write to us and a person answers.