Privacy Policy
The sensitive thing never reaches us.
Terera is built so that the sensitive thing — what you say and what you write — never reaches us. This page describes exactly what happens to your data, including the parts most privacy policies leave out.
Terkon Pty Ltd (ABN 81 652 483 997) · Last updated 9 August 2026
The short version
Your scripts and your voice never leave your computer. Speech recognition runs on a model stored on your own disk. Audio becomes text on your processor and is discarded immediately. There is no upload path in the software to switch off.
We do not have an account system. There is no login, no profile, no password. We do not know who our customers are beyond what is needed to sell them a licence and support it.
We set no cookies, no tracking scripts, no advertising, no profiles. We do read aggregate server logs for this website — see This website below. The application sends none of that.
Terera reaches the network for one thing: downloading its speech model. It carries nothing you said or wrote. Your licence is checked on your own computer — entering a key sends nothing, to anyone.
What stays on your computer
All of the following is stored only on your own machine, in your user profile folder. We never receive it, and we have no ability to retrieve it.
Uninstalling Terera offers to remove this. If you choose to keep it, it stays on your disk until you delete it.
What Terera sends over the network
This is the complete list. Nothing else in Terera's own code makes a network request.
01 — Downloading the speech model
The first time you switch on voice following, Terera downloads its speech-recognition model from Hugging Face (huggingface.co), which hosts the open-source model the application uses.
This is a file download. It carries nothing about you and nothing about your scripts. As with any download, Hugging Face can see the IP address that requested the file. It happens once; afterwards the model lives on your disk and voice following works with no network at all.
02 — Your licence — checked on your own computer
When you enter a licence key, Terera verifies it on your own machine, against a verification key built into the application. This is a mathematical check of the key's signature, done entirely on your processor.
What is sent: nothing. Not the key, not a device identifier, not a machine count, not an email address. There is no licensing server, and we do not learn that you activated, when you use the software, or on which machines.
The application re-checks the stored licence from time to time. That check is also local — it works identically with the network off, which is why Terera runs on a plane.
An earlier version of this policy described a licence check that contacted a licensing provider. That design was dropped before launch in favour of the on-device check described here; no such contact exists in the software.
03 — Checking for updates
Automatic update checking is not currently enabled. If a future version enables it, that request will carry your Terera version and operating system, and nothing else. This page will be updated before that ships.
This website
Separate from the application, and worth stating plainly rather than leaving you to guess.
Cloudflare, our DNS and delivery provider, keeps standard server logs of requests to terera.app — the page requested, the referring site, an approximate country, and the IP address that made the request. We read the aggregate to see which pages people find useful.
We set no cookies, run no tracking scripts, carry no advertising, and build no profiles — and nothing is sold or shared with anyone. The one exception is buying: Paddle's secure checkout sets the cookies it needs to process a purchase and prevent fraud, under Paddle's own privacy policy (paddle.com/legal/privacy). Browse without buying and nothing is stored on your device — which is why this site has no consent banner.
An IP address counts as personal information in some countries even when it is only in a log, so we tell you about it here rather than rely on how private the arrangement happens to be.
This section is about the website only. Terera the application transmits nothing you write or say — see the two sections above.
What we receive when you buy
Purchases are handled by Paddle, which acts as the merchant of record — Paddle is the legal seller, and it, not us, processes your payment.
We never see your card details. They go to Paddle and its payment processors, and are never transmitted to us or stored on our systems.
From a completed purchase we receive: your name, your email address, your country, the order reference, and what you bought. We use this to issue your licence, to provide support, and to meet our tax and record-keeping obligations.
For the purchase details we receive — your name, email address, country and order reference — Terkon Pty Ltd is the data controller. Paddle is an independent controller for the payment itself, including card data, invoicing, tax and fraud checks, under its own privacy policy (paddle.com/legal/privacy).
Product news, only if you ask for it
The checkout offers a tick-box to hear about Terera updates. It is optional, unticked by default, and buying never depends on it. If you tick it, we keep your email address for that one purpose — occasional product news, such as a new version shipping — on the legal basis of your consent (GDPR Article 6(1)(a)). Every email includes an unsubscribe link; unsubscribing removes you from the list and changes nothing about your licence. We never add buyers to this list who did not tick the box.
Who else handles data on our behalf
We keep this list short on purpose, and it is complete.
Provider
What it handles
Where
{{ p.n }}
{{ p.w }}
{{ p.z }}
Some of these are outside Australia, which means data we hold may be processed overseas. Each of these providers processes data on our documented instructions under a data-processing agreement, not on terms of its own choosing. Where data belonging to people in the EU or UK leaves those regions, the transfer rests on the safeguards those agreements incorporate — the providers' EU–US Data Privacy Framework certifications and the European Commission's Standard Contractual Clauses.
How long we keep things
Your rights
You can ask us to tell you what we hold about you, correct anything that is wrong, delete what we hold (subject to records we are legally required to keep), or send you a copy of it.
Email support@terera.app. We will respond within 30 days. There is no charge.
If you are in the European Union or the United Kingdom, the GDPR gives you these rights and others, including the right to object to processing and to complain to your data protection authority. For the record, our legal bases under the GDPR are: performance of a contract (Article 6(1)(b)) for issuing your licence and providing support; legal obligation (Article 6(1)(c)) for tax and record retention; and legitimate interests (Article 6(1)(f)) for the aggregate website logs described above — the right to object applies to that last one.
If you are in Australia: as a small business we may fall outside the Privacy Act, but we will handle any complaint as though it applied — email us first. The Office of the Australian Information Commissioner (oaic.gov.au) publishes who the Act covers.
Children
Terera is offered to adults for professional use. We do not knowingly sell to, or collect information from, anyone under 16. If we learn we hold information about someone under 16, we will delete it and arrange cancellation and a refund of the licence.
Security
Your scripts and speech are protected by the strongest measure available: we never receive them. For the limited purchase and support data we do hold, we use reputable providers, keep access restricted to those who need it, and do not copy that data into systems that do not need it.
No system is perfectly secure. If we ever discover a breach affecting your information, we will tell you promptly, and notify regulators where required — the OAIC under Australia's Notifiable Data Breaches scheme where it applies to us, and the relevant EU or UK supervisory authority within 72 hours where the GDPR applies.
Changes
If we change this policy we will update the date at the top. If a change materially affects what we do with your data — particularly if the application begins sending something it does not send today — we will say so plainly rather than quietly revising the text.