Sightdeck AIAgentic Studio

Privacy Policy

Last updated: September 2026

This Privacy Policy explains how personal data is processed when you use the Sightdeck AI website and purchase or manage a license. It follows the requirements of the EU General Data Protection Regulation (GDPR).

1. Controller

The controller responsible for data processing on this website is:

Christian Dangl
Schlierseestrasse 20
83101 Rohrdorf
Deutschland / Germany

For any privacy-related request, please use the contact form.

2. Data We Process

We process personal data only for the purposes described below.

2.1 Server log files

When you visit this website, the hosting infrastructure automatically records technical data such as your IP address, the requested URL, the date and time of the request, the referring page, and your browser and operating system. This data is required to deliver the site reliably and securely. Legal basis: Art. 6(1)(f) GDPR (legitimate interest in a stable, secure service). Log data is not merged with other data sources and is deleted after 14 days.

2.2 Contact form

When you submit the contact form, we process the information you provide (such as your email address and message) solely to handle your request. Legal basis: Art. 6(1)(b) GDPR (pre-contractual steps and contract performance) or Art. 6(1)(f) GDPR (legitimate interest in answering enquiries).

2.3 Purchase and license data

When you buy a license, your payment is processed by our payment provider Paddle (see section 3). We store the resulting license record — including your email address, the plan purchased, and the transaction reference — to issue and manage your license and to provide the "My licenses" and "Manage subscription" functions. Legal basis: Art. 6(1)(b) GDPR (contract performance) and Art. 6(1)(c) GDPR (statutory retention obligations for invoices and tax records).

2.4 Desktop application

Sightdeck AI is a local-first desktop application: your tasks, projects, and settings are stored on your own device. Your license is verified on your own device: the app checks the cryptographic signature of your license code locally, and no server has to confirm it before you can work. The one exception is the Store described in section 2.5 — when you rate, comment on, report or publish a template, the app sends your license code with that request so that we can confirm the request comes from a valid license. That code is checked in memory and discarded; we do not store it, and we do not store the email address it contains. All credentials you enter for optional integrations, and any AI provider keys, are stored encrypted on your device using the operating system's secure storage — the macOS Keychain on macOS, the Data Protection API (DPAPI) on Windows, and the system keyring (libsecret) on Linux. None of this is transmitted to us. When you use an integration or an AI provider, the app communicates with that third-party service directly from your machine under the credentials you supplied. The app contains no usage analytics and no background telemetry: it does not report which features you use, which projects you work on, or what you do inside them. It does download two files from our servers that are tied to no identity. One is the Store catalogue. The other is the AI model price list, which the app fetches when it starts and every few hours afterwards. Like any web request, those downloads leave an entry in the server log described in section 2.1, including your IP address and the app version. Anything else the app sends to us is listed in section 2.5 and only happens when you trigger it. Legal basis: Art. 6(1)(b) GDPR (contract performance) and Art. 6(1)(f) GDPR (legitimate interest in license integrity).

2.5 Store

The Store is the catalogue of shared templates you can browse from inside the desktop app; its web addresses carry the older name "gallery". Browsing, searching and installing a template needs no license and sends us no identity: the app downloads catalogue files, and the only trace is the server log entry described in section 2.1.

Four actions do require a license, because they write something: rating an entry, commenting on it, reporting a comment, and publishing a template of your own. For these, the app sends your license code with the request. We verify its cryptographic signature and then discard it — the code itself is never written to our database, and neither is the email address it contains. The one exception is publishing a template: there the name from your license is stored and published as the entry's author, as described below. What we store in place of the license is a pseudonym: a one-way hash, computed with a secret key held on our server, of a stable identifier taken from your license. For licenses newly issued from September 2026 onwards that identifier is a random number generated for you when your license was first issued, tied to nothing outside it. Licenses issued before that date started out with the email address as the identifier; the next time such a license is bought or renewed through our checkout it also receives a random number, and a nightly job then rewrites the pseudonyms already stored for it onto that number. That job matches a renewal against our checkout records, so it only ever reaches licenses that went through the checkout. A license we issued directly — for support, for press, for a partner, or free of charge — also receives a random number, but the pseudonyms stored for it before that keep the email address as their identifier. They also keep it as long as a license has not been bought or renewed again, as long as the newer purchase has not been refunded, and in the rare case where we cannot establish with certainty that the old and the new license belong to the same person: there we deliberately leave the old pseudonym untouched rather than risk attributing one person's contributions to another. Without the secret key, the stored pseudonym cannot be turned back into a license, an email address or a name. It is pseudonymous, not anonymous: we hold the key, so we can still tell which license a pseudonym belongs to when you ask us to show or delete your contributions. Day to day it only lets us recognise that two contributions come from the same customer — every license issued to the same email address shares one identifier, so a renewal does not start a new pseudonym. Legal basis: Art. 6(1)(b) GDPR (carrying out the action you asked for, as part of your license) and Art. 6(1)(f) GDPR (legitimate interest in accepting Store contributions only from licensed users, and in stopping abuse).

A rating is a score from one to five stars and, optionally, a short title and review text, stored with the app version you rated from. Each license rates an entry once; rating it again replaces the earlier rating. Ratings and reviews are published in the Store — the stars, the title, the text, the app version and the date — but never with a name: reviews are shown anonymously. A comment is the text you write plus a display name you choose yourself; leaving the name empty is a valid comment. We never use the name on your license as a byline, because you gave us that name for an invoice, not for a public post. Comments are public: anyone who opens that Store entry can read them. The Sightdeck team can hide a comment, delete it, or block a license from writing further ones; a block stores the pseudonym and, where we noted one, a reason, and it expires after 12 months. Legal basis: Art. 6(1)(b) GDPR (publishing the rating or comment you submitted) and Art. 6(1)(f) GDPR (legitimate interest in one rating per license, and in moderating a Store that is not used for abusive or unlawful content).

If you hold a license, you can report a comment once, choosing one of three fixed reasons — spam, abuse or off-topic. There is no free-text field, so a report cannot carry anything you write about the author yourself. Reports are not public: only the Sightdeck team sees the reason, and it is used solely to decide whether the reported comment stays. The report is recorded against the pseudonym of the reporting license, so that the same comment cannot be reported twice. Legal basis: Art. 6(1)(f) GDPR (legitimate interest in handling abuse reports).

When you publish a template, the app sends the exported template as structured data, an optional note to the reviewer, and a display name taken from your license. The Sightdeck team reviews the submission and either approves it — in which case the template appears in the Store with that display name as its author — or rejects it with a reason you can read in the app. Please keep in mind that an approved entry carries that name publicly until it is removed, and that the template content is published as you sent it: do not put anything into it that you do not want to be public. Legal basis: Art. 6(1)(b) GDPR (publication is the purpose of your submission, and the review is part of it).

When you install a template, the app sends a single ping so that the Store can show how often an entry has been installed. The ping carries a random identifier the app creates once for itself, and it is not derived from your device, your license or anything identifying. We store only a hash of it, which is what lets a repeated installation of the same entry be ignored instead of counted twice. We keep that hash for 90 days. After that it is irreversibly replaced by a value derived from nothing but the database row itself, so the install record can no longer be connected to an installation, or to any other install record. What remains is a dated count. Alongside it we keep short-lived hourly counters — per install identifier and per pseudonym — for no other purpose than stopping a script from flooding the Store; they are discarded after about a day. Legal basis: Art. 6(1)(f) GDPR (legitimate interest in install counts for ranking entries, and in protecting the service from abuse).

Store data is kept as follows. A comment the Sightdeck team has hidden is deleted 90 days after it was hidden. The reason given with a report is erased 90 days after it was made, whether or not we have decided by then; only the fact that this license already reported this comment remains, so that nobody reports the same comment twice. Visible comments, ratings and reviews have no fixed period: they are part of the entry they belong to and stay until we remove them or you ask us to. A comment or a rating whose entry is no longer in the Store is deleted together with it. Install pings carry no link to your license, and the install identifier behind them is anonymised after 90 days, leaving only the count. A rejected submission is deleted 90 days after the decision; you can read the reason in the app until then. For an approved submission we keep the record of what was published and by whom, but the submitted template content and the note to the reviewer are erased 90 days after publication — the template itself is in the Store from that point on. A block on a license expires 12 months after it was set, and the record of it, including the reason, is deleted with it. In every case this applies to the pseudonymous record described above, not to your license code or your email address, which we never store in the first place.

You need no license, no account and not even the app to have something in the Store removed. If a comment, a review or a published entry concerns you, or if you want your own contributions deleted, write to us through the contact form and describe the entry — the report function inside the app is a convenience for licensed users, never the only route. We remove the content from the published Store and, on request, delete the contributions belonging to your license. Your rights under section 6 apply here in full, including the right to object under Art. 21 GDPR to the processing we base on legitimate interest.

3. Payment Processing (Paddle)

Payments and subscription billing are handled by Paddle.com Market Limited, which acts as the Merchant of Record for purchases of Sightdeck AI. In plain terms, this means Paddle — not us — is the official seller of record and handles billing, taxes, and payment compliance on our behalf. When you check out, the payment and billing data you enter is processed by Paddle under its own privacy policy. We receive only the data required to issue and manage your license (such as your email address, plan, and transaction reference); we do not receive or store full payment card details. Legal basis: Art. 6(1)(b) GDPR.

4. Disclosure to Third Parties

We do not sell your personal data. Data is shared only with processors that help us run the service (such as our hosting provider and Paddle), and only to the extent necessary for the purposes described above. These processors are bound by data processing agreements as required by Art. 28(3) GDPR.

Content you submit to the Store — a review, a comment, or a template you publish — is not disclosed to a processor but published: it is visible to everyone who uses the Store, and publicly reachable on the internet. Section 2.5 describes what each of these contains and which name, if any, is shown with it. Store data is not passed to our payment provider, and it is not linked to your purchase record.

5. Data Retention

We keep personal data only as long as necessary for the purpose it was collected for, or as long as statutory retention periods require. In particular, invoices and tax records are retained for the legally mandated period (typically 10 years under German tax law); other data, such as contact-form messages, is kept only for as long as needed to handle your request. Content in the Store follows its own periods, described in section 2.5: hidden comments and the reason given with an abuse report are deleted after 90 days, while published contributions stay until they are removed on request or with the entry they belong to. After the applicable period, the data is deleted or anonymised.

6. Your Rights

Under the GDPR you have the right to:

  • access the personal data we hold about you (Art. 15 GDPR);
  • have inaccurate data corrected (Art. 16 GDPR);
  • have your data erased (Art. 17 GDPR);
  • restrict processing of your data (Art. 18 GDPR);
  • receive your data in a portable format (Art. 20 GDPR);
  • object to processing based on legitimate interest (Art. 21 GDPR).

To exercise any of these rights, contact us via the contact form. You also have the right to lodge a complaint with a data protection supervisory authority. The authority competent for the controller is the Bavarian State Office for Data Protection Supervision (Bayerisches Landesamt für Datenschutzaufsicht, BayLDA), Promenade 18, 91522 Ansbach, Germany.

7. Data Security

This website is served over an encrypted TLS/SSL connection to protect data in transit. Please note that data transmission over the internet (for example, by email) can have security gaps; complete protection against access by third parties is not possible.

8. Changes to This Policy

We may update this Privacy Policy to reflect changes to our service or legal requirements. The current version is always available on this page.