mattblu is the name behind a few small products, listed on mattblu.com. It's one person, Matt, not a company with a team. This page covers the mattblu account: the one account you use to sign in to any of those products, and the server behind it. In short: it keeps who you are and how you sign in, it never sells or shares that for advertising, and you can have it deleted whenever you like.
What each product does with the things you collect or create in it is in that product's own policy (see "Each product's own data" below).
What your account keeps
- Who you are: your name and email address, and your profile picture's web address if you sign in with Google.
- How you sign in: a scrambled (hashed) copy of your password if you set one, which can't be turned back into the password; or the fact that you sign in with Google, with your Google account's ID.
- Your organization: every account gets a personal workspace named after you, which the products use to keep your things together.
- Which products you use: for each one, when you first and last used it, and when Claude last used it for you if you've connected it.
- Your sign-ins: each signed-in browser or extension, with the IP address and browser details it signed in from and when it expires (after 7 days unless used). They're there so you stay signed in and so the account can be protected from misuse.
- Connections to Claude: if you connect a product to Claude (or another AI app), which app it is, what you allowed it, and the keys it uses, until you remove the connection.
Your account doesn't keep payment details, and nothing you browse.
Signing in with Google
If you choose Continue with Google, Google asks you to share your name, email address and profile picture with mattblu, and confirms you own that email. That's all we ask Google for (the basic "openid", "email" and "profile" sign-in permissions). We use it only to create your account and sign you in. We can't see your Google password, and we don't read your Gmail, contacts, files, calendar or anything else in your Google account.
Google also sends back a short-lived sign-in pass, which is kept with your account record. We don't use it to call Google for anything.
mattblu's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. In plain words: the data from Google is used only to sign you in and show who you're signed in as, never for advertising, never sold, never used to train AI models, and never read by a person unless you ask us to (for example to help with your account) or the law requires it.
Where it's kept
Your account lives in a Postgres database run by Neon, and the server that answers sign-ins runs on Fly.io, in London. Connections to it are encrypted (https).
Usage data and error reports
If you agreed, in a product, to share usage data, signing up and signing in each send a short record to Mixpanel, an analytics service that stores the data in the EU: that it happened, whether you used a password or Google, which product, the product's random ID for your browser and your account's ID. No name, email or location is sent. If you didn't agree, nothing is sent.
When something goes wrong on the server, an error report goes to Sentry, an error-reporting service that stores the data in the EU, so it can be fixed: what failed, where in the code, and your account's ID if you were signed in. Reports never include your password, IP address or what you sent.
Cookies
When you sign in on a product's website (such as app.parsly.to), the server sets one sign-in cookie on that product's own domain, so you stay signed in. Page scripts can't read it, and it isn't used for advertising or to follow you around the web. Signing in with Google also sets a short-lived cookie that lasts only while you go to Google and back. Extensions don't use cookies: they keep a sign-in key in the browser's storage for that extension.
Who else handles it
We don't sell your data or share it for advertising. The only other companies that handle it are the services that run mattblu for us, each only for that job: Neon (the database), Fly.io (the server), Google (if you sign in with Google), and, as above, Mixpanel and Sentry. We'd also hand data over if the law required it.
How long it's kept, and deleting it
Your account is kept until you ask for it to be deleted. Sign-ins expire on their own, and you can sign out at any time. There's no delete button yet: to delete your account, email[email protected] from the address on the account. We'll delete it, with your organization, sign-ins, product list and Claude connections, and confirm when it's done. You can also remove mattblu's access in your Google account's settings at any time.
You can also ask to see, correct or get a copy of what your account holds, the same way. If you're unhappy with how your data is handled, you can complain to your data protection authority (in the UK, the ICO).
Each product's own data
Each product has its own policy for what it collects and where that's kept:
- Parsly: parsly.to/privacy
This website
mattblu.com has no cookies, analytics or sign-in. It's hosted on Cloudflare, which processes standard request data such as IP addresses to deliver and protect the site.
Children
mattblu's products aren't meant for children under 16, and we don't knowingly keep their data.
Changes
If this policy changes, the new version goes on this page with a new date at the top.
Contact
Questions about this policy or your data: [email protected]. It comes straight to Matt.