Data protection, built into the service
The service is built to keep as little of your data as possible, for as short a time as possible. Here, in plain words, is what happens to an uploaded STEP file and to the little else the service knows. The binding details are in the privacy policy.
Uploads are deleted automatically
Without an account an upload exists only for the watermarked preview: the upload is deleted for good 2 hours after the preview run — the files and the records that go with them. If you press “Sign in” or “Create an account” on the job's page, that one upload is kept for another 24 hours from the press. Registering holds the upload until the confirmation link expires, 72 hours; after that the usual rule applies again. With an account the period you choose applies: 15 minutes after the download, or at most 7 days. New files restart the period, up to 30 days after the upload. A part sent with “Report a problem” stays until 90 days after the answer. Any job can be deleted sooner at any time.
Page views are counted only as daily totals
The service counts page views as daily totals. The totals show which pages are read, where readers come from and where the service runs into trouble. They are counted per page, per region and per device type, phone or computer. A region is a state or canton in Germany, Austria and Switzerland, and the country elsewhere. Referring websites are counted by their domain only. For the count the server reads the IP address, the browser's name and the referring address. Every browser sends all three with every request anyway. The region is looked up from the IP address in a table on the service's own server. The address is not stored for the statistics but discarded immediately. Uploads, finished drawings, sign-ins, errors and refused forms are counted as daily totals in the same way. Only the number per day is kept: no IP address, no hash of one, no identifier. Refusals under overload are the one exception: the service counts them per cause and deletes them after 14 days. Nothing is stored on or read from your device for the counting, and the pages carry no counting pixel. The daily totals are kept for 24 months and then deleted. The legal basis is Art. 6(1)(f) GDPR. The legitimate interest is knowing how the service is used, so that the service can be improved.
The paper size is guessed from the language, not from a location
The paper size the upload form offers first is guessed from the browser's language setting alone, not from a location.
What the pages keep in your browser
Besides cookies, the pages keep a few entries in the browser's own storage (localStorage and sessionStorage). The German TDDDG treats browser storage exactly like cookies. Each entry is either strictly necessary for a function you started or keeps your own choice. A file card you closed, for example, is kept as your choice. A remembered choice says nothing about who you are. The choice is stored only when you click or tap yourself, and lapses 90 days after your last choice. After a save, one entry carries what you saved or your place to the next page. The next page deletes the entry as soon as the entry is read. Opening a page stores nothing. The one exception is the page of a guest's job, which notes the way back. No entry is sent to the server. The cookies page lists every entry with the entry's purpose, what writes the entry and how long the entry stays.
Without an account: one job per browser, limited per connection
Without an account, one browser keeps one job at a time. An upload without an account sets a cookie holding a random value. The cookie expires no later than the job is deleted; being technically necessary, the cookie needs no consent. In addition, at most 3 jobs without an account can start from one internet connection within 60 minutes. They are counted with a checksum of the IP address, made with a key only the server holds. The address itself is not stored, and nothing links an entry to a job or an account. The checksum is still pseudonymised personal data. The purpose is protecting the server capacity of the preview, free until a download, against abuse. The legal basis is the operator's legitimate interest in that protection. Each entry is deleted after 60 minutes. The limit neither stores nor reads anything on the device and therefore needs no consent. The privacy policy names the provisions.
No tracking, no advertising cookies, no banner
The service sets only technically necessary cookies. They serve signing in, the remembered key, protecting forms and the one job without an account. There are no cookies for advertising, analytics or profiling, and therefore no cookie banner. Exactly which cookies these are is listed on the cookies page.
Passwords as a checksum, the one secret encrypted
A password is stored only as the checksum of a memory-hard function (scrypt) with a random salt; it cannot be reversed from it. The one secret that has to stay readable — the optional two-factor key — is stored encrypted, with a key the server holds. That honestly protects against a stolen database file or a leaked backup, not against the operator.
Your files are trade secrets
Uploaded geometry is treated as what it is: the customer's trade secret. It is not used for training, not handed to third parties and not used for the operator's own purposes — only to produce the drawings you ordered.
Hosting in Germany
The server stands in Nuremberg, the encrypted backup copy in Falkenstein, both with Hetzner Online GmbH. A data processing agreement with Hetzner is in place.
Mail through INWX, the certificate from Let's Encrypt
Every email the service sends leaves through the mail server of INWX, such as a confirmation or reset link. INWX receives the recipient's address and the message. The operator's mailboxes are at INWX as well. The certificate of the encrypted connection is issued by Let's Encrypt. Let's Encrypt receives only the site's domain names and the operator's contact address, never data of visitors.
Access log
The web server (Caddy) also keeps an access log with the time, IP address, method, host name, the path requested without its query string (the part after the question mark), status code, response size, duration and user agent. Login details and keys (the Authorization, Proxy-Authorization and X-API-Key headers), cookies (Cookie and Set-Cookie), the referring page (Referer), query strings and any user names or passwords in an address are not logged; the access log holds neither keys nor login details. An internet connection that keeps sending refused requests is blocked by the server, read from the access log, at its firewall for 15 minutes. The access log is started afresh every day; each entry is deleted no later than 14 days after it was written. To preserve evidence of attacks, the server copies the previous day's log lines every night, encrypted, to a store of Hetzner outside the server (Storage Box): the server's system journal (which includes the sign-ins to the server), the access log and the log of the operator's actions (with internal account numbers, without e-mail addresses). The copy holds only what the three logs already hold; each daily copy is deleted after 12 days, so no copied line becomes older than 14 days. While a security incident is being investigated, the operator keeps a copy of the logs of the period concerned until the investigation is closed, for one year at most (Art. 6 (1)(f) GDPR). The web server accepts payment notices only from the IP addresses Paddle publishes as the senders of its notices: it compares the IP address of each request to the notice address with Paddle's list and stores nothing further for it. For troubleshooting, the service records how the reading of each uploaded file ended: the day, the file format and its version, the exporting program as the file's header names it, the step, the outcome, the reason and the duration, and for a fault of the service the place in its program code. The file's name and content, part names, the job and the account are not stored, only a checksum formed with the server's key by which two entries of the same file can be recognised; each entry is deleted after 90 days.
What is left after a deletion
Little, and no drawing and no file. First, a checksum of your email address with a date, made with our own key. The checksum keeps deleting and reopening an account from refilling the free parts (Article 6 (1) (f) GDPR). Second, your declarations: the answer to the check question and whether you order as a consumer or a business. A consumer's two declarations on the right of withdrawal and an API partner's duty confirmation belong to them. Your choice of unit and your confirmation of the dimensions belong to them too. Each declaration stays with its moment, wording, job and your account's details, for the defence of legal claims (Art. 17(3)(e) and Art. 6(1)(f) GDPR). Each one is deleted 10 years after the end of its calendar year. Third, without a link to your account, the billing and payment rows, refunds, download records and payment notices stay. They are deleted 10 years after the end of their calendar year. The operating log keeps an account number which now points to nobody. The privacy policy gives the details.
Messages from the operator and notice after a data breach
The operator may email customers about their own order, account or a legal matter, never with advertising. In the operator area the address stays hidden. Each look at the address and each message is logged with time and reason.
If a personal-data breach likely brings a high risk, the operator notifies the persons concerned by email without undue delay. Where individual mails are impossible or disproportionate, a public notice on the website takes their place.
Common questions about data protection
Is my uploaded 3D file stored?
Without an account the file is deleted for good 2 hours after the preview. With an account your period applies: 15 minutes after the download, or at most 7 days. New files restart the period, up to 30 days after the upload.
Do you track my location or IP address?
No. Statistics take only the region from the IP address, at most a state or canton, then drop the address. Daily totals carry no identifier; refusals under overload are counted 14 days per connection checksum. Without an account, an IP checksum stays 60 minutes for the limit, a second until the job is deleted. The address is kept only in the server's logs and their copy, to fend off attacks. Each entry is deleted after 14 days at the latest.
Are my files used to train anything?
No. Uploads are trade secrets; they are neither used for training nor shared with third parties.
Where is the data hosted?
In data centres in Germany: the server is in Nuremberg, the backup copy outside the server in Falkenstein.
What about AI and AI crawlers?
We do not use your data to train AI. Slatlyn reserves the use of its content for text and data mining, also in machine-readable form. Our server does not send the imprint or the legal texts naming the operator to crawlers that identify themselves as AI crawlers, among them GPTBot, ClaudeBot, CCBot and PerplexityBot. Every other visitor reads the imprint in full.