DRAFT – not legal advice. This document is a working draft for founder and lawyer review. It is not in force, may be incomplete or wrong, and must not be relied on until reviewed by a qualified lawyer. Text in [SQUARE BRACKETS] is a placeholder.

Privacy Policy

Last updated: 11 November 2026 (draft)

1. Who is responsible

The controller of the personal data described in this policy is [OPERATING ENTITY], [ADDRESS], [REGISTRY NUMBER], VAT ID [VAT ID] ("we", "us"). You can reach us about privacy at [CONTACT EMAIL]. [DECISION: whether a data protection officer is appointed; if so, add contact details here.]

This policy covers the cadshot website, dashboard and API. It explains what personal data we handle, why, for how long, and what rights you have under the EU General Data Protection Regulation (GDPR).

2. Two different roles

Where we are the controller. For account data, billing data, request logs and website usage data, we decide why and how the data is processed. This policy describes that processing.

Where we are a processor. The files customers send to the API for rendering, and the images produced from them, are processed only on the customer's instructions. If such a file happens to contain personal data (for example an author name in file metadata), the customer is the controller and we are its processor under the Data Processing Agreement. If you are an individual whose data is contained in a customer's file, please contact that customer first.

The in-browser converter. The converter on our website runs locally in your browser using WebAssembly. Files you open in it are not uploaded and we never receive them.

3. What data we process

CategoryWhat it containsWhere it comes from
Account dataEmail address, hashed API keys (the key itself is shown once and not stored), plan, usage counters, billing statusYou, and your use of the Service
Sign-in dataOne-time sign-in tokens sent by email; a session cookie for the dashboardGenerated by us
Billing dataStripe customer and subscription identifiers, invoice details, billing name and address, VAT ID, payment status. Card numbers are collected and held by Stripe; they never reach our servers.You and Stripe
Request logsRequest id, API key id, input format, triangle count, timings, byte sizes, status code, and IP address. Logs never contain file contents or file names.Your use of the API
Demo endpoint dataIP address, used to apply the per-IP rate limit on the keyless demo, plus the same technical log fields as aboveYour use of the website demo
Advertising data (free tool pages only, when advertising is switched on) [DRAFT – LAWYER TO REVIEW]Cookies and similar identifiers, IP address, browser and device information, the page you visit, and your consent choices, collected by Google through Google AdSense. The files you open in the free tools are processed in your browser and are never sent to us or to Google.Your visit to a free tool page
Website analyticsAggregated, cookieless page statistics (page, referrer, country, device type). No cookies, no cross-site or persistent identifiers.Your visit to the website
CorrespondenceMessages you send us and our repliesYou
Error reports (optional, if enabled)Technical error details such as stack traces and request ids; no file contentsOur systems

Input files are processed in memory or temporary storage only for the duration of the render and then deleted. They are never stored afterwards and never used for training machine-learning models or for any other purpose. Rendered outputs are cached for at most 30 days, keyed by a hash of the file and parameters, and then expire automatically.

We do not intentionally collect special categories of personal data and we do not carry out automated decision-making that has legal or similarly significant effects on individuals.

4. Why we process it and on what legal basis

PurposeData usedLegal basis (GDPR)
Creating and running your account, signing you in, providing the API, metering usageAccount, sign-in, request logsArt. 6(1)(b) – performance of a contract; where the account holder is a company, Art. 6(1)(f) – our legitimate interest in providing the Service to our customer
Billing, invoicing, tax and accountingBilling dataArt. 6(1)(b) and Art. 6(1)(c) – legal obligations under tax and accounting law
Security, abuse prevention, rate limiting, troubleshootingRequest logs incl. IP address, demo endpoint data, error reportsArt. 6(1)(f) – our legitimate interest in keeping the Service secure and available
Understanding how the website is usedCookieless analyticsArt. 6(1)(f) – our legitimate interest in improving the website using aggregated statistics
Showing advertising on the free tool and converter pages, which pays for the free tools (personalised ads only with your consent) [DRAFT]Advertising dataArt. 6(1)(a) – your consent, given or refused in Google's consent message, for cookies and personalised ads (and the consent rules for storing information on your device under the ePrivacy Directive as implemented nationally); where you refuse, Google shows limited or non-personalised ads as described in its policies
Service and legal notices (changes to terms, security or billing notices)Email addressArt. 6(1)(b) and (f)
Answering enquiriesCorrespondenceArt. 6(1)(f) or, for pre-contract requests, Art. 6(1)(b)
Establishing, exercising or defending legal claimsAny of the above, as necessaryArt. 6(1)(f)

We do not send marketing email without your consent, and we do not sell personal data. Providing an email address is necessary to create an account; without it we cannot provide the keyed API.

5. Cookies and analytics

Our website analytics are cookieless. The only cookie we set ourselves is a strictly necessary session cookie that keeps you signed in to the dashboard; it does not require consent. The Stripe checkout page is operated by Stripe and may set its own cookies under Stripe's policies.

Advertising [DRAFT – applies only once advertising is switched on; lawyer to review]. The free calculator and converter pages show ads from Google AdSense. Google Ireland Limited sets cookies and similar identifiers to show, measure and limit ads and to prevent fraud, and acts as an independent controller for that data. Visitors in the EEA, the UK and Switzerland are asked for their choice in a consent message (Google's certified consent management platform) before such cookies are used for personalised ads; you can change your choice at any time with the “Privacy and cookie settings” link in the footer of those pages. How Google uses this data: policies.google.com/technologies/partner-sites. The home page, pricing, documentation, the dashboard and the API show no ads and set no advertising cookies.

6. How long we keep data

DataRetention
Input filesDuration of the render only; then deleted
Rendered outputs (cache)At most 30 days, then automatic expiry
Request logs, including IP addressesAt most 30 days
Sign-in tokensUntil used or expired ([15 minutes – TO CONFIRM])
Session cookie[SESSION LIFETIME – TO CONFIRM]
Account dataWhile the account exists; deleted within [30] days of account closure
Aggregated usage counters needed for invoicingAs billing records, below
Invoices and billing recordsAs required by tax and accounting law ([typically 5 years from the end of the relevant tax year in Poland – TO CONFIRM])
Correspondence[Up to 3 years after the last contact – TO CONFIRM]
Website analyticsAggregated statistics only; no data about identifiable individuals is kept

The Data Retention Statement gives the same information in plain language.

7. Who receives data

We use service providers for hosting, content delivery, payments, transactional email and analytics. They act as our processors under written agreements, except where they act as independent controllers for their own obligations (Stripe does so for parts of payment processing, such as fraud prevention and financial regulation). The current list, with purposes and locations, is on the Subprocessors page.

We may also disclose data to professional advisers, to authorities where the law requires it, and to a successor in the event of a merger or sale of the business, subject to this policy.

8. International transfers

The Service is hosted in the European Union and we store account data, logs and cached outputs there. Some providers are, or belong to, groups based outside the European Economic Area (in particular in the United States) and may process limited data there, for example network-level data handled by a content delivery network or payment data handled by Stripe. Where personal data is transferred outside the EEA, we rely on an adequacy decision of the European Commission (including, where the provider is certified, the EU–US Data Privacy Framework) or on the Commission's standard contractual clauses, with supplementary measures where needed. You can ask us for a copy of the relevant safeguards at [CONTACT EMAIL]. [TO CONFIRM per provider once the subprocessor list is final.]

9. Security

We apply technical and organisational measures appropriate to the risk, including encryption in transit, storing API keys only as hashes, isolating each render in its own process without network access, EU hosting and deletion of input files immediately after processing. No system is perfectly secure; if a personal data breach creates a risk to you, we will inform you and the supervisory authority as the law requires.

10. Your rights

Under the GDPR you have the right to:

To exercise a right, write to [CONTACT EMAIL]. We respond within one month; this may be extended by two further months for complex requests, in which case we will tell you. We may need to verify your identity. Exercising your rights is free of charge unless a request is manifestly unfounded or excessive.

11. Complaints

You may lodge a complaint with a data protection supervisory authority, in particular in the EU member state where you live or work or where the alleged infringement occurred. Our lead supervisory authority is [TO CONFIRM: the President of the Personal Data Protection Office (Prezes Urzędu Ochrony Danych Osobowych, UODO), ul. Stawki 2, 00-193 Warsaw, Poland, uodo.gov.pl]. We would appreciate the chance to address your concern first.

12. Changes to this policy

We may update this policy as the Service changes. The date at the top shows the latest version. We will notify account holders by email of material changes.