Who we are
VesselMaker is operated by Marco Siino (“we”, “us”). You can reach us at hello@vesselmaker.app for any privacy question or request.
Signing in is required to use VesselMaker
You need an account to open the editor. You can create one with an email address and a password, or sign in with Google — whichever you prefer. Editing and the 3D preview never leave your browser. Signed-in usage does make a small number of further server requests: entitlement checks, premium export authorization, and — as described under What we store below — lightweight usage counters. Your actual vase design (the geometry, profile points, materials) is never part of any of those requests; a project file you save stays a local file on your device, as before.
Before launch, the tool is additionally invite-only: a signed-in account also needs an invite code or a grant from us to get in. If you sign in without one, we store your account (see below) but you won't have access to the tool until you're let in or the tool launches. When we grant a signed-in account access, we send a one-time notification email to the address on that account so you know you can start using the tool — this is a transactional message about your own account's status, sent whether or not you've opted in under Occasional updates & promo codes below, since that opt-in is about ongoing marketing/product-update email, not this single confirmation.
What we store
- If you use a password — we store your password only as a salted scrypt hash. We never store, log, or are able to read the password itself, and nobody at VesselMaker can tell you what it is. Confirming your address and resetting a password use single-use links that expire (24 hours and 1 hour respectively); we store only a hash of those too, so a copy of our database contains nothing that could be used to open your account. We also keep short-lived counters of failed sign-in attempts, keyed by a one-way hash of the address rather than the address itself, to make guessing attacks impractical.
- One account per email address — if you create a password account and later sign in with Google using the same address (or the reverse), you reach the same single account rather than a second one. We link them only when the address has been confirmed on both sides, and we email you when a new sign-in method is added to your account.
- Account data — when you sign in with Google, we store your email address, display name, and profile picture URL as provided by Google. We never see or store your Google password.
- Access & subscription records — records tied to your account that determine what it's entitled to use (your subscription tier, if any, and how it was granted) and, before launch, whether you've been let into the tool.
- Access requests — while VesselMaker is invite-only, signing in with Google does not add you to any separate list: your account itself is the record, and our team grants access to it individually. We email you as soon as that happens. (A small number of invite codes sent by email before this changed may still be tracked internally until redeemed — that bookkeeping is removed once the code is used or the invite-only period ends.)
- Occasional updates & promo codes — an optional opt-in, separate from the above and always off by default, never assumed: wherever VesselMaker shows an explicit opt-in for this (for example when signing in, in account Settings, or elsewhere in the product), choosing it stores that you opted in and the date. On most of these forms, leaving it unticked records that you have not opted in and clears any earlier opt-in from that email address — except the checkbox shown before you sign in, which can only grant this opt-in: at that point we don't yet know which account is signing in, so leaving it unticked there never clears an opt-in you may already have. Opting in lets us occasionally email you about VesselMaker in general — news, new features, progress, tips and behind-the-scenes — and, from time to time, a promo code. Declining changes nothing else about your account. We never use this for anything else and never share it with third parties. You can withdraw at any time — as easily as you gave it — via the toggle shown after signing in, the unsubscribe link included in those emails, or by contacting us.
- Usage & product-analytics counters — tied to your account, not a new cookie: how much time you spend using the editor, and counters for saves, exports, AI renders, upgrade-page views, how many times you've hit the export paywall, and which optional premium features (if any) you've tried. We use this only to understand how VesselMaker is actually used and to gauge demand for premium features — never sold, shared with third parties, or used for advertising. An admin can view this detail for a specific account, including a day-by-day breakdown (not just totals), for support and product-understanding purposes. Day-by-day usage detail is kept for up to 24 months and then automatically deleted; account-level totals (like your export count) are kept for as long as your account exists. A small, separate count of how often each individual feature has been used overall is kept in fully aggregate form with no link to any account — not personal data. Saving or exporting a design sends only an action type and a list of which features it uses — never the design's geometry, profile points, or materials.
- Email-send history — when we email you (for example, a pre-launch invite code, a notification that you've been let into the beta, or a direct message from us about your account or your experience using the product), we keep a record of that send tied to your account or waitlist entry: the recipient address, when it was sent, its delivery status (delivered, or bounced/blocked), and — if it failed — the error, so we can retry or troubleshoot a delivery problem. Our email provider, Brevo, embeds a standard open- and click-tracking pixel in these messages that cannot be disabled for transactional email; we run it in Brevo's anonymous tracking mode, so opens and clicks are not linked to you or your IP address, and we do not read, store, or act on open or click data — the delivery status we keep comes only from bounce/delivery reports.
- Onboarding & Academy progress — tied to your account: which guided lessons you have completed, whether you asked us not to offer the guide again, and which version of the onboarding you last saw. We use it only to decide what to show you, so a lesson you finished on your computer shows as finished on your tablet too, and it is kept for as long as your account exists. An admin can view which lessons a specific account has completed, and we also look at these same records in aggregate — for example, a total count of how many accounts have completed a given lesson — to see which lessons are working, for the same support and product-understanding purposes described under Usage & product-analytics counters above. Where people stop within a lesson (which step they gave up on) is counted separately in fully aggregate form with no link to any account — a plain tally per step, so we can tell which step loses people and fix it, without that tally ever identifying who. Which step you personally are on is remembered in your own browser and is never sent to us.
- Anonymous visit statistics — we count page views on our own site (which page, roughly where in the world, what kind of device) to understand how many people find VesselMaker and which pages they reach. This is collected by our hosting provider Vercel and sets no cookie and stores nothing on your device. Visitors are counted using a value derived from the network address and browser, which is reset every day, so these statistics cannot follow anyone from one day to the next, cannot be linked to your account, and are never used for advertising.
- Session cookie — a strictly-necessary cookie that keeps you signed in. It is not used for tracking or advertising.
As we add new tools and features to VesselMaker, we may add further usage counters of the same kind described above — either tied to your account or, like the step tallies above, in fully aggregate form with no link to any account — always for the same purpose: understanding how the product is actually used and deciding what to build next. A counter of this kind is covered by this policy and the rights below without a separate update for every one we add; we will still update this page, including the date below, whenever we add a materially different kind of data collection, a new purpose, or a new processor.
Some data never reaches our servers in any stored form: your Gemini API key (used for AI rendering) stays in your browser's local storage — requests using it are relayed through our server without being logged or persisted — and your vase project files stay on your device as local JSON files.
Processors we use
- Google — identity provider for sign-in (Google OAuth). See Google's Privacy Policy.
- Our hosting and database providers — used to run the application and store the account/entitlement data described above. Our hosting provider, Vercel, also collects the anonymous visit statistics described above. See Vercel's Privacy Policy.
- Brevo — sends the transactional emails described above (invite codes, beta-access notifications) on our behalf; Brevo processes the recipient address and message content needed to deliver them under its own data processing agreement/standard contractual clauses. Brevo embeds a standard open- and click-tracking pixel in these emails that cannot be turned off for transactional messages; we have it set to Brevo's anonymous tracking mode, so opens and clicks are not associated with you or your IP address, and we do not use or retain that data. See Brevo's Privacy Policy.
- If we add a payment provider in the future (for self-serve checkout), it will be a merchant of record responsible for handling payment details and applicable tax directly — we do not store card details ourselves.
Cookies & browser storage
We only use a strictly-necessary session cookie to keep you signed in. We do not use any tracking or advertising cookies. The anonymous visit statistics described above set no cookie and store nothing on your device, so no cookie-consent banner is shown.
The app also keeps a few things in your browser's own storage so it behaves the way you left it: your Gemini API key for AI rendering, editor preferences such as your printer build volume, and your place within an onboarding lesson. These are not cookies, they stay on your device, they are never sent to us, and none of them is used for tracking or advertising — so they don't change the answer above. You can clear them at any time through your browser's site-data settings.
Separately, as described under What we store above, we do keep server-side usage counters tied to your account (time spent, exports, saves, and similar). These involve no tracking technology in your browser; they're listed there for completeness.
Your rights
You can delete your account at any time from Settings. Deletion is immediate and permanent — there is no grace period and we cannot undo it. It removes your account and both sign-in methods, your password hash, your plan and redeemed-code history, your saved material presets, your usage counters, and your email address everywhere we hold it — including our waitlist, our record of emails we have sent you, and our marketing list, so you are removed from any future mailing rather than merely unsubscribed. We send one final email confirming the deletion, and keep no record of having sent it. Project files saved on your own device are not affected; they are yours and we never had them.
You can also contact us at the email above to request access to, correction of, or deletion of your data.
Changes to this policy
If this policy changes materially (for example, if we add a new processor such as a payment provider), we will update this page and the “Last updated” date above.