LeTissier Creative Studios

Who is responsible

LeTissier Creative Studios Ltd, registered in Ireland under number 808819, is the controller of the personal data described here. Our registered office is 40 Carleton Road, Marino, Dublin 3, D03 VW30.

For anything about your data, contact info@letissier.ie.

The short version

We collect what we need to sell you a licence, deliver it, and keep it working, plus crash reports and feedback only when you choose to send them, and nothing else. This site has no analytics, no advertising and no tracking scripts, and its fonts are served from our own domain. We do not sell or share your data for marketing, and we don't send marketing email.

What we collect, and why

When you start a trial or buy a licence

Your email address and, if you give it, your name. We use these to issue your licence, email you the key, and let you sign in. Basis: performing our contract with you.
Order details from Paddle. This covers the product, Paddle's order and invoice references, the amount, currency, tax and fees, and any refund or chargeback. We use it to deliver and manage your licence and to keep our accounts. Basis: contract, and our legal duty to keep accounting records.

We never see or store your card or bank details. Paddle collects those at checkout (see below).

When the software activates or checks in

Your licence key, a machine identifier, and the machine name you give it, if any. The app sends a fingerprint of the machine, and we store only a one-way hash of it. We record when each machine activated and last checked in. We use this to enforce the seat limit, let you move seats between machines, and keep the licence working offline. Basis: contract.
For trials, we also keep the hashed machine identifier for each product, so a machine can't restart the same trial. Basis: our legitimate interest in preventing abuse of free trials.

When you sign in to your account

A one-time sign-in link is emailed to you. We store only a hash of it, and it expires.
A single cookie, account_session, keeps you signed in for up to 30 days. It is strictly necessary for the account to work, so it needs no consent banner. We set no other cookies on visitors.

When you visit the site

Our host, Vercel, handles each request and keeps short-lived server logs, which include your IP address and browser details. We use these only for security and to diagnose faults. Basis: our legitimate interest in running a secure website.

When an app sends a crash report

Our apps can send us a report when they crash, so we can fix the fault. This is off unless you turn it on. Each app has a setting, "Send crash reports automatically", which starts switched off; after a crash the app asks you once whether to send that report, and nothing is sent unless you say yes or have turned the setting on. Basis: your consent, which you can withdraw at any time by switching the setting off.

A crash report contains exactly these things:

the product, its version, your operating system and its version, and the processor type (for example arm64);
a random install identifier the app makes up the first time it runs. It is not derived from your licence, your hardware, your network or your name, and we use it only to count how many installs a crash affects and to limit how many reports one install can send;
the kind of crash, its first line, and the technical trace of where in our code it happened. The app removes your home folder, your user name and anything after a ? in a web address before sending, and we remove the same things again, along with anything shaped like an email address, an IP address or a licence key, when it arrives;
a short fingerprint of the crash, so the same fault from different computers is counted together, and when it happened;
a note, only if you type one, about what you were doing.

A crash report never contains your licence key, email address, name, the names or contents of your files, shows or presets, camera or audio, the names of video sources on your network, or the addresses of other devices.

When you send feedback from an app, or from our feedback page

The product, version, operating system, the app's random install identifier (not sent from the web page), the kind of feedback (a bug, an idea, a question or thanks), and your message.
Your email address and name, only if you type them because you'd like a reply.
Your licence key, only if you tick "Include my licence so you know who I am". We use it once, to look up which customer you are, and do not store the key itself; we store only the link to your customer record.
Whether you ticked "OK to post this on the public issue tracker".

We use this to fix problems, decide what to build next, keep a list of who asked for what, and reply if you asked us to. We do not add you to any mailing list, and nothing is emailed to you automatically: a reply, if you get one, is written by a person. Basis: your consent, given by pressing Send.

Where crash reports and feedback go. Both are stored in our database (Neon, through Vercel) and read in our private admin area. We also publish some of them on the product's public issue tracker on GitHub, so that fixes can be tracked in the open:

Crash reports are grouped, and each distinct crash gets one public issue showing the product, versions, operating systems, processor types, the kind of crash, its first line, the scrubbed trace and how many times it has happened. The public issue never includes your note, install identifier, IP address, email, name or licence.
Feedback is posted publicly only if it is a bug or an idea and you ticked the box. Then only your message, the product, version and operating system are posted, never your name, email or licence. Everything else stays private.

To stop one sender flooding us, we count reports per install identifier and per IP address. We never store the IP address: we keep a keyed hash of it that is made with a different key every day, so it cannot be matched to your address or across days, and we delete even that after 7 days.

When you email us

We keep the correspondence so we can help you, and as a record of anything agreed.

Paddle

Purchases are made through Paddle.com, our reseller and merchant of record. When you open the checkout, Paddle's script loads from Paddle's own servers and may set Paddle's own cookies. Your payment details, billing address and tax information go directly to Paddle, which handles them as an independent controller under its own privacy notice. Paddle then sends us the order details listed above.

Who else handles your data

We use a small number of service providers, who process data only on our instructions:

Provider	What for	Data
Vercel Inc.	Hosting this site and its server code	Everything above passes through it; server logs
Neon (through Vercel)	Our database	Account, licence, activation and order records
Resend	Sending email	Your email address and the messages we send you
GitHub, Inc.	Public issue trackers for our products	Only what is described above as public: scrubbed crash details, and feedback you ticked to make public, with no personal data

Some of these providers are based in, or use infrastructure in, the United States. Where your data leaves the European Economic Area, the transfer is covered by the EU–US Data Privacy Framework or by the European Commission's Standard Contractual Clauses.

We will also disclose data where the law requires it, for example to the Revenue Commissioners.

How long we keep it

Licence, activation and account records are kept for as long as the licence exists. A perpetual licence has to stay verifiable for as long as you use it.
Order and refund records are kept for six years after the end of the financial year they belong to, as Irish tax and company law require.
Sign-in links expire after use. Server logs are kept for a short period and then deleted by our host.
Trial machine identifiers are hashes that cannot identify you on their own. We keep them for as long as the product is offered.
Crash reports are kept for 12 months. The public issue for a crash, and the counts behind it, stay after that, because they contain no personal data.
Feedback is kept while the request it belongs to is open, and for 24 months after we mark that request done or declined. Feedback that was never part of a request (a question, a thank-you) is kept for 24 months. The record of who asked goes when nothing they sent is left.
IP address hashes on crash reports and feedback are deleted after 7 days.
Feedback you asked to be made public stays on GitHub until we remove it; ask us and we will.

Your rights

Under the GDPR you can ask us for a copy of your data, and ask us to correct it, delete it, restrict how we use it, or send it to you in a portable format. You can also object to anything we do on the basis of legitimate interests. Email info@letissier.ie and we will respond within one month.

If you ask us to delete your account, we delete everything except the order records the law requires us to keep. Deleting the account also ends any licences on it, because a licence we can no longer look up cannot activate.

To have your crash reports or feedback deleted, email info@letissier.ie, with the email address you gave or the product and roughly when you sent it, and we will delete it and anything else we hold that you sent, including any public issue made from your feedback. Switching crash reporting off in the app stops any further reports.

If you're unhappy with how we have handled your data, you can complain to the Data Protection Commission, Ireland's supervisory authority, or to the authority where you live.

Children

Our software and this site are meant for adults working in live production. We do not knowingly collect data from anyone under 16.

Changes

If we change what we collect or who handles it, we will update this page and the date at the top. If you have an account and the change is significant, we will also email you.