Privacy

Who we are

Company

Garciel Inc.

Address

76 Pl. Montmorency, Laval, QC H7N 1T6

Email

[email protected]

We're responsible for the data this page describes.

What stays on your computer

Your recordings, library, projects, transcripts and settings stay on your computer, where you put them. We have no copy, and Compiler has no cloud of its own.

A vault's password and recovery phrase never leave your computer. Nobody can open a vault whose password and phrase are both lost, us included.

Transcription runs on your computer, and the audio never leaves it.

If you set up uploads, copies go to the storage you choose, under that storage's own terms.

What we keep about you

Our license server keeps what it needs to sell licenses, count their computers and give each computer one trial.

• Your email, if you give one, so a license is yours and support can find it.
• A hash of your license key, never the key itself, and the key's first group, so support can find a key you read out.
• For each computer, a fingerprint made of salted hashes of its hardware, never a raw serial number. With it, its system and processor type, its name, the app's version, whether the app's signature checked out, and the public half of a key the app makes for it.
• Each computer's trial, with when it started and ended.
• A record of what changed a license or a computer, and who changed it.
• For each order, its invoice and receipt, the country you declare and the country your connection comes from, and how you paid. For a crypto payment, the amount and its value. Receipts are kept for our accounts.
• If you came through an affiliate's link, which affiliate, so they're paid their share.

Our database keeps no IP addresses. The rate limits hold them in memory only, and the server's own logs leave them out. The proxy in front of the server may log them.

To settleHow long trial records, the change record and the proxy's log are kept, and how your email, licenses and computers are removed when you ask.

What the app sends, and to whom

Compiler has no analytics and no advertising. It sends only what's listed here.

• To our license server, to start a trial, activate a license and keep it current, at launch, every 6 hours, after the computer wakes and when you press Check now. The details above go with it, and the update check sends your license.
• To our license server, with each check, a request for the signed settings that keep live streams working. Nothing about you goes with it.
• To our license server, only if you turn on Share anonymous stream counts (Settings → Privacy). Once a day, Compiler sends how many live streams it opened and how often each site refused them or asked for a browser check, per day and site, with the app's version. Nothing about you, the streamers or what you watch is sent, and we keep only totals.
• To our download host, a request for the update you install.
• Compiler downloads add-on components it needs from the internet, from their publishers' releases on GitHub, and keeps them current. Nothing about you is sent, but GitHub sees the request.
• On Windows and Linux, if you turn on OpenH264 (Settings → Editor), Compiler downloads Cisco's OpenH264 video codec from Cisco (ciscobinary.openh264.org), which sees that request.
• To GIPHY, only when you use the editor's GIF picker, what you search for, and GIPHY's notes of the GIFs shown and picked.
• To Google Fonts, when you pick a Google font in the editor, a request for that font's files.
• To the sites you add, what your browsing and recording ask of them, as a browser would. They see your IP address.
• To the servers named by what you add by its link, the requests for it and for what it names. For some of it, Compiler also downloads public files from a fixed list of hosts it ships with, sending nothing about you or what you added.

This website

This website sets no cookies and loads nothing from other companies' servers. Its host may keep logs of the pages asked for, with the IP address and the time.

We count visits with Umami, which runs on our own server. It notes the page, the site you came from, your browser, system, device, screen size and language, the country, region and city your IP address points to, and which download or plan you choose. It sets no cookie and keeps no IP address. So a return visit in the same month counts once, it keeps a one-way hash of your IP address and browser. Of a page's address it keeps only a campaign's tags, never what a link carries. If your browser asks sites not to track it, nothing is counted, and the payment pages never load it.

Our shop's pages use cookies only to work. One lets the browser that paid see its key, one keeps you signed in to the customer portal for an hour, and one remembers the affiliate whose link you came through, for a while.

To settleThe website's host, how long it keeps its logs, and how long visit counts are kept.

Payments and email

Card payments go through Stripe, which handles your card details under its own privacy policy. Crypto payments go through BTCPay, whose invoice holds the order, the product and the computer it's for. Your key and your receipts are emailed through Amazon SES, Amazon Web Services' email service.

To settleHow long Amazon SES keeps what it sends, and the addresses on its list of mail that bounced or was marked as spam.

Your choices

To ask what we keep about you, or to have it corrected or removed, write to us. Stream counts can be turned off at any time, and what's counted but not yet sent is dropped at once.

Changes

When this page changes, the date at the top changes with it.