Privacy Policy

Last updated: PLACEHOLDER

Who we are

ThirdThought is a product of Electric Monk, LLC (trading as Electric Monk). Electric Monk, LLC is the data controller for personal data collected through this site, and can be reached at hello@thirdthought.dev.

Electric Monk, LLC is registered in Nebraska, United States.

[PLACEHOLDER — postal address. Required in US marketing email under CAN-SPAM, and expected as a controller contact detail. Note that Nebraska has no comprehensive consumer privacy statute of its own, so obligations here are driven by where subscribers are located (UK/EU GDPR, and state laws such as California's) rather than by the state of registration.]

What we collect

At present, ThirdThought operates a pre-launch website. The only personal data we intend to collect is an email address, submitted voluntarily to join the early-access list.

[PLACEHOLDER — confirm whether analytics, logs, or cookies are in use on this website. If none, say so explicitly; if any are added later, this section must be updated first.]

What the application sends

This section describes the ThirdThought application rather than this website. It is stated here in advance of release because it is a design commitment, not an afterthought.

The application does not send us:

• Prompts, agent conversations, and file contents
• Secrets or PII detected by redaction — including the values themselves
• Source code or repository contents

Redaction happens on your machine. When the application detects a secret or personal identifier, the value is removed before the request leaves the device and restored in the response locally. We do not receive the detected value, and we do not receive a copy of the content it was found in.

Licence heartbeat

Each licence has an internal licence ID, which is linked to your purchase and to the email address we use to contact you about it. A device activates against that licence with a registration token, valid for 60 days and rotated automatically during the heartbeat.

The heartbeat carries the current registration token and a device identifier. The device identifier is generated randomly when the application is installed. It is not derived from your hardware, so it cannot be used to recognise your machine across a reinstall or to identify it to anyone else. It is used to:

• confirm the licence is still valid and issue a fresh token;
• count how many devices are active on the licence. If that count exceeds what the licence allows, the oldest activation is deactivated first — so reinstalling or moving to a new machine hands the licence to the newer install without you having to do anything.

It does not carry your name, your email address, or anything about the work the application is doing. If a device is not seen for 60 days, its token expires and the application returns to a deactivated state; a new token can be requested by email.

[PLACEHOLDER — state the heartbeat frequency, and whether the receiving endpoint logs IP addresses. Web servers commonly log IPs by default, before application code sees the request — verify this rather than assuming, because an IP tied to a device ID is location data.]

Optional

• Operational telemetry and crash reports, if enabled
• Diagnostic dumps you generate and choose to send us

Diagnostic dumps are generated locally and sent only if you choose to send them. Organizations can configure usage and redaction event logging; those events are delivered to a destination the organization operates — their own Logstash instance or data lake. We do not host, receive, or have access to that data. Redaction events record that a redaction occurred and what class of value it was; they never carry the value itself.

[PLACEHOLDER — before release, confirm the final position on telemetry and crash reporting: whether they ship at all, whether they default to off, and if they ship, precisely what the payloads contain and which processors handle them. If they are dropped in favour of manual dumps, remove them from this policy rather than leaving an over-broad disclosure.]

Names and email preferences

We ask for a legal name and, optionally, a preferred name. The legal name appears on billing records; the preferred name is used so our emails address you the way you would like to be addressed. Providing a preferred name is optional and it is used for nothing else.

Email about your licence — receipts, token requests, expiry notices — is transactional and sent because you hold a licence. Product update emails are separate and opt-in: you choose whether to receive them and can unsubscribe at any time without affecting your licence.

Surveys

We run occasional product surveys. Responses can be submitted anonymously. Sharing your email address is optional and is used only to ask follow-up questions about your response — it does not subscribe you to anything.

[PLACEHOLDER — name the survey tool once chosen and confirm whether it retains IP addresses or other metadata alongside responses. A survey advertised as anonymous that records an IP is not anonymous, and that claim would be the problem, not the IP.]

Purchases and billing

When you buy a licence, we keep a sales record: name, billing address, email address, and the transaction details. We do not store payment card numbers — card data is handled by our payment processor and never reaches our systems.

[PLACEHOLDER — name the payment processor, and confirm whether it acts as a processor or an independent controller (this differs by provider and changes what must be disclosed here). For organizations, also state whether seat-assignment records identify individual employees.]

How long we keep it

Device records are tied to a registration token. If a device stops checking in — because the application was uninstalled, the machine was retired, or the licence lapsed — its token expires after 60 days and the device record is deleted. This happens automatically and requires no request from you.

The licence ID and the email address attached to it are kept for the life of the licence, so that a new registration token can be issued if you reinstall or move to a new machine.

Sales and billing records are kept for as long as tax and accounting law requires, which is longer than the device retention above and is not affected by uninstalling the application. We keep them because we are required to, not to build a profile.

[PLACEHOLDER — state the statutory retention period for sales records (commonly seven years in the US; confirm the figure for Nebraska and for any jurisdiction you sell into), a retention period for early-access addresses that never convert, and how long survey responses are kept.]

Who else sees it

We do not sell personal data. For the application, the org-logging destination is operated by the customer, not by us — see above.

[PLACEHOLDER — name the email/list provider once chosen, where it stores data, and the transfer mechanism if data leaves the UK/EU. Also name the crash-reporting and telemetry processors before release, since those are the application's only outbound recipients.]

Your rights

You can ask what we hold about you, correct it, or ask us to delete it. Requests go tohello@thirdthought.dev.

One limit worth stating plainly: we cannot delete sales and billing records on request, because tax and accounting law requires us to retain them. Everything else we can remove — your early-access subscription, product update preferences, survey responses, and device records. Deleting the licence ID and its email address ends the licence for good. That record is the only thing a replacement registration token can be issued against, so once it is gone we cannot reactivate you, restore your remaining term, or verify that you ever bought anything — and any time left on the licence is forfeited. This is a consequence of erasing the data, not a penalty for asking. We will spell it out and ask you to confirm before acting on a request of this kind.

Within 15 days of purchase, our money-back guarantee applies and you can have a full refund — see the terms. After that, we do not refund the unused portion of a licence in this situation, except where the law where you live requires it. If you are entitled to a refund under local consumer protection law, ask and we will honour it.

[PLACEHOLDER — confirm the response timeframe (GDPR allows one month) and the process for verifying who is making a request. For organization customers, clarify who may exercise rights over seat records: the employee, the account administrator, or both. Every marketing email must also carry a working unsubscribe link.]

Contact

Questions about this policy: hello@thirdthought.dev