Privacy

Last updated: 6 October 2026

In short: vectorizing happens in your browser by default; nothing leaves your computer until you save to your account or ask for a server job. The account is optional. A production export (account required) does not upload the image: the server only notes its format and date.

What stays in your browser

• The images you open and the SVGs produced: processing runs on your computer, in a “worker” of the page. Without an account, nothing is uploaded.
• Your theme preference (light, dark or system), your language choice (homotope.lang) and whether some settings panels are collapsed or open, kept in the browser’s local storage.
• Your swatch library (homotope.nuancier): the colours you store in it, their names and its settings, kept in local storage until you empty it.
• The purchase snapshot (homotope.achat): when a payment starts, your plan and balance at that moment, so we can recognise your return from the payment page. It is erased when you come back and ignored after one hour.

These items never leave your browser: they are neither sent to the server nor shared.

What goes to the server, and when

• Sign-in with Google, if you choose it: the account’s Google identifier (“sub”), email address, name and avatar address. We keep no Google token. We note the date the account was created, the date of the last sign-in, and the account language (French or English), set at sign-up and changeable on the account page.
• Saving to your gallery, only when you click “Save”: the source image as you opened it, the SVG, a thumbnail (small PNG image), the name you chose, the dimensions, the preset, the settings and a few statistics (number of paths, colours…).
• Server processing, only if you ask for it (account required, for an image too large for your device, or through the API and MCP, see below): the image (PNG or JPEG) is uploaded and processed on our server, with the name, preset and settings you chose. The image and the SVG produced are kept after the job ends, then deleted automatically after 7 days by default (daily storage clean-up); until then, they count towards your account’s storage. The record of the job (name, settings, statistics, dates) stays in your account until it is deleted and is included in the export.
• Production exports (DXF, EPS, PDF, separations, “ready to cut” version, single stroke; account required): the conversion happens in your browser and the image is not sent to us. The server counts your production exports: it records, linked to your account, the format and date of each export, to apply the month’s included exports and charge a credit beyond them (legal basis: performance of the contract). The details of each export (format, date) are deleted with the account; the number of free exports used in the month is kept under a fingerprint, see “Preventing free-trial fraud” below.

API and MCP

• Images sent through the API or MCP: an image received with your API key, or read by our server from the public image_url you provide, is handled as a server job, with the same retention periods (files deleted after 7 days by default, job record kept in your account).
• Reading a URL: it is restricted to https only, port 443, no private or local address, 3 redirects at most, 15 seconds and 80 MB. The URL is never logged.
• API keys: we only keep a fingerprint of each key (never the key itself), with its name, prefix, creation date and last use.
• Your keys are included in the export (cles-api.json, without the fingerprint) and deleted with the account.

Gifted rights

Homotope may give you the Pro plan for a limited time or credits (server job or production export). We then keep your email address, what was given, its dates, an optional reason and the date of any revocation. If your account does not exist yet, the right waits for your first Google sign-in with that verified address. These rights are included in the export (droits-offerts.json) and deleted with the account.

Referrals

If you create your account from another user’s link, we keep the link between their account and yours (and the date of your first Pro payment, to work out their reward) for as long as both accounts exist. Your referrer only sees counters (number of referrals, credits earned) and, if you upgrade to Pro, the expected date their pending reward will be paid (14 days after your payment): never your name or your address. Your referral code, drawn at random, contains no personal data. If you delete your account, this link disappears (credits already paid to your referrer stay theirs); if your referrer deletes theirs, you keep your credits. Your code and your counters are included in the export (parrainage.json), without the identity of the people you referred.

Preventing referral fraud: when a sign-up bonus is paid, we keep a fingerprint of your verified Google email address, encrypted with a secret server key (HMAC-SHA256) and not reversible without that key, never the address itself, so that the same address only receives this bonus once. This fingerprint is linked to no account, has no other use, and is kept even after your account is deleted: that is its purpose (legitimate interest in preventing fraud).

Preventing free-trial fraud: for each month in which you use a server job trial or a free production export, we keep the number of free trials and exports used, and the date the 7-day trial of unlimited exports was granted to your Google identity, linked to a fingerprint of your Google identifier (HMAC-SHA256 under a secret server key, not reversible without it), never the identifier itself. This data has no other use and is kept after your account is deleted, so that deleting and recreating an account renews neither the month’s free trials and exports nor the export trial (legitimate interest in preventing fraud).

Teams

If you join a Pro subscriber’s team (the “payer”), they see your name, email address, status (active or waiting for a seat), the date you joined and the number of your server jobs this month: never your files, images or vectorizations. You, in turn, see the payer’s name and the date you joined. When the payer invites someone, we keep the invited email address, the invitation dates and a fingerprint (SHA-256) of the link, never the link itself; no email is sent by Homotope.

Legal basis: performance of the contract (providing the seats bought by the payer and Pro features to the member). This data is kept as long as the member belongs to the team: it is deleted when they leave, when the payer removes them or when either account is deleted. An invitation that has not been accepted (invited address, dates, fingerprint) is kept, even expired or revoked, until the team is dissolved. The export (equipe.json) contains, for the payer, their seats, their members (name, email, status, joining date) and their pending or expired invitations (neither accepted nor revoked); for the member, the payer’s name, their joining date and status, never the payer’s address.

Emails

Homotope only writes to you to run the service, never for marketing:

• Welcome, once, when your account is created (verified Google address): what Homotope does and the link to the workshop.
• Gifted Pro, when the Homotope team gives you the Pro subscription: its length and end date, at the address chosen for the gift.
• Team invitation, when a subscriber invites you: the link to join and its expiry date, at the invited address (the subscriber’s identity is not included).

These emails are sent by Resend (Resend, Inc., United States, privacy policy), our transactional email processor, under the European Commission’s standard contractual clauses. Resend receives the recipient’s address and the content of the message. Legal basis: performance of the contract (and, for an invitation, the legitimate interest of the subscriber inviting you). On our side, the content of the message is erased as soon as it is sent (the invitation link is not kept); what remains is the kind of email, the address, the status and the dates, deleted after 90 days or with your account, and listed in the export (e-mails.json, without content). No tracking pixel, no tracked link.

Payment

If you buy a credit pack or the Pro subscription, payment is handled by Stripe (Stripe Payments Europe, Ltd., privacy policy), on its own payment page. Stripe receives your email address and your payment details (card). Homotope neither receives nor stores any card number or IBAN: we only keep the Stripe identifiers of your customer account and subscription, the subscription status (active, cancelled, end of period) and the history of your credits (purchases, jobs charged and refunded, production exports charged). Invoices are issued and kept by Stripe. If you delete your account, this data is deleted on our side, but the Stripe customer account and its invoices are kept by Stripe for our accounting and tax obligations (10 years).

Cookies

• The session cookie (homotope.sid, prefixed __Host- in production), set only when you click “Sign in with Google”, which keeps you signed in for 30 days at most.
• The referral cookie (homotope.ref), set only when you open a user’s referral link: it contains their code (no data about you), is used only to recognise them as your referrer if you create your account, and lasts 30 days at most. It is erased when you sign in.
• The invitation cookie (homotope.invite), set only when you open a team invitation link: it contains that link’s token, is used only to add you to the team when you sign in, and lasts 7 days at most. It is erased when you sign in.
• The language cookie (homotope_lang), set when you choose a language: it only contains fr or en; the server reads it to answer you in that language and to set your account’s language when it is created. It lasts one year.

No third-party cookies, no audience measurement, no advertising.

Where the data is

The site and the database (accounts, list of vectorizations, sessions) are hosted by Railway (Railway Corporation), region europe-west4 (Netherlands, European Union). Files are stored in a Railway bucket (S3-compatible storage) attached to the same project. Sign-in goes through Google (Google LLC), which receives the sign-in request when you click “Sign in with Google”. Once you are signed in, your avatar is displayed from Google’s servers (without passing them the page address). Transactional emails go out through Resend (Resend, Inc., United States, standard contractual clauses), see “Emails” above.

How long

Your data stays until you delete it: a vectorization, from the gallery; the whole account, from “My account”. A sign-in session expires 30 days after sign-in at the latest, or as soon as you sign out.

Your rights, in one click

• Export: “My account” → “Export my data” downloads a ZIP archive with your profile (account language included), the list of your vectorizations and their settings, each SVG and each source image, the record of your server jobs, workshop and API included (the files of those jobs, which are temporary, are not included), the list of your API keys (name, prefix, dates, without fingerprint), your referral code with its counters, your team (equipe.json), the log of your production exports (format, source, date: exports-fabrication.json), and the list of emails sent to you (kind, date, status, without content: e-mails.json).
• Delete: “My account” → “Delete my account”. Deletion is permanent and immediate: account, vectorizations, server jobs, API keys, files and sessions on all your devices. Files are erased from storage straight after; if erasing a file fails, we remove it during a manual storage clean-up. If you sign in again with Google afterwards, a new, empty account is created.
• For any other request (correction, question, complaint): write to us. You can also contact the CNIL, the French data protection authority (cnil.fr).

Contact

[email protected]

This English text is a translation: the French version prevails.