Privacy notice

This notice explains which personal data IESDesk keeps, why we keep it, how long we keep it, and who helps us.

Last changed:

On this page

Who is responsible

Ağustos Teknoloji Ltd. Şti. is the data controller for IESDesk.

  • Address: Barbaros Mah. Denizmen Sok. 21/2, 34668 Üsküdar/İstanbul, Türkiye
  • Email: agustos@agustos.com
  • Istanbul Trade Registry no.: 358564-0
  • MERSIS no.: 0059004540100019
  • Tax office: Üsküdar, tax no.: 0590045401

This is the information notice of Article 10 of the Turkish Personal Data Protection Law No. 6698 (KVKK). It also gives the information that Articles 13 and 14 of the EU General Data Protection Regulation (GDPR) require.

Send each question about your data to the email address above. When you write to us, the privacy notice of agustos.com covers your message.

The data we keep, and why

Each item below says what we keep, why we keep it, the legal ground, and how long we keep it. The legal grounds come from Article 5 of the KVKK and Article 6(1) of the GDPR.

Your account

What we keep
Your email address, and your password as a one-way hash. Nobody can read your password from the hash. We also keep the dates of your sign-up and your email confirmation, your saved diagram themes, your report sheet logo, the name and the footer line for your report sheets, and your API tokens. We keep each API token only as a one-way hash, with the name that you gave it, its last four characters and the time of its last use.
Why
We use it to give you a private account and to sign you in. We also use your email address to send the emails that the service needs.
Legal ground
Our contract with you (KVKK Article 5(2)(c), GDPR Article 6(1)(b)).
How long
While your account is open. For a closed account, see How long we keep data.

Sign-in records

What we keep
For each sign-in: the time of the sign-in and the time of its last use.
Why
We use them to keep you signed in, and to end a sign-in that you do not use for 30 days.
Legal ground
Our contract with you, and our legitimate interest in a secure service (KVKK Article 5(2)(c) and (f), GDPR Article 6(1)(b) and (f)).
How long
Until you sign out, reset your password or close your account. A sign-in that you do not use for 30 days ends, and we delete its record within a day.

Your files and your work

What we keep

The IES and LDT files that you upload to a batch, a job or a saved comparison, and their file names.

The metadata that IESDesk reads from the files, and your edits.

For each metadata sheet that you download, a copy of its cell values. For each sheet that you upload, the list of problems that IESDesk found. IESDesk does not keep the sheet file that you upload.

For each Generate job, the variant sheet that you upload and the rows that IESDesk reads from it.

The files that IESDesk makes for you: export ZIP files, diagram ZIP files, report sheet ZIP files, variant ZIP files and CSV files.

Photometric files are technical data. They can still hold personal data, for example the name of a test engineer.

Why
We use them to do the work that you ask for, and to show you your earlier work.
Legal ground
Our contract with you (KVKK Article 5(2)(c), GDPR Article 6(1)(b)).
For the quality checks of Generate jobs: our legitimate interest in correct results (KVKK Article 5(2)(f), GDPR Article 6(1)(f)).
How long
  • Uploaded files: 30 days after the upload. You can delete them earlier on the batch page.
  • Export ZIP files: 30 days after the export. You can delete one earlier on the batch page.
  • Diagram ZIP files: 30 days after the diagram job ends.
  • BUG Rating and ULOR jobs: IESDesk deletes each uploaded file as soon as it has the result. The results and the CSV file stay for 30 days after the upload.
  • Report sheet jobs: IESDesk deletes each uploaded file, or its copy from a batch, as soon as it has the sheet. The ZIP file of sheets and its manifest CSV file stay for 30 days after the job starts.
  • Generate jobs: IESDesk deletes each source file as soon as it has written the variants of that file, except the copies for quality checks (see below). It deletes the variant sheet when the job starts. The ZIP file of variants, the result CSV file and the rows of the sheet stay for 30 days after the upload. IESDesk deletes a job, with its files, when it waits 24 hours with no change and no start.
  • Quality checks of Generate jobs: for a small share of Generate jobs, IESDesk runs a second engine in the background and compares the results. It keeps a copy of each source file until that check ends, and in any case for at most 2 days. If the two engines give different results, it keeps the source file, its file name and the variant rows of the job until the job's 30 days end, so that we can find and fix the error. Only our own team uses these copies, and only for this check. We do not give them to anyone else and do not use them to train AI. Then we delete them.
  • Checks of the results: for a sample of BUG Rating, ULOR, report sheet and diagram jobs, IESDesk keeps a copy of each file for about two days at most. It makes the result a second time from the copy and compares the two results, then it deletes the copy. When IESDesk deletes the job, or when you close your account, IESDesk deletes the copy at the same time. When you delete files from a batch, IESDesk also deletes the copies of the diagram jobs of that batch.
  • Metadata sheets: 30 days after the download. The problem lists of the uploads go with their sheet.
  • Saved comparisons: the files 30 days after the comparison.
  • The history of your batches, diagram jobs and saved comparisons, with the file names, the metadata, the figures and your edits, stays after the files are gone. It stays while your account is open, so that you can see your earlier work.

Files on the free tools

View, Compare, UGR Table, and the one-file pages of Diagrams, BUG Rating, ULOR and Lighting Scenes read your file in your browser where they can, and send our server only the results to draw the page. When the browser cannot read a file, and on the Report sheets page, the page sends the file to our server, which reads it. In both cases IESDesk keeps no copy of the file, and you need no account. One exception: when you are signed in and choose Save to Your files, Compare keeps your comparison and its files in Your files for 30 days.

Edit in your browser

What we keep
When you edit in your browser, a count for each day of the files that you opened, exported, that IESDesk refused, that you changed, and that you saved to Your files. We keep no file name and no value from a file.
Why
We use it to know how Edit is used and to find faults.
Legal ground
Our legitimate interest in a service that works (KVKK Article 5(2)(f), GDPR Article 6(1)(f)).
How long
While your account is open.

Refused files

What we keep
When a tool refuses a file or cannot calculate it, we count the message that it showed, the tool and the day. We keep no file name and no value from the file. When you are signed in, or when the work is a job of your account, we also link the count to your account.
Why
We use it to answer your questions about a refused file, and to find the files that IESDesk must learn to read.
Legal ground
Our legitimate interest in a service that works and in good support (KVKK Article 5(2)(f), GDPR Article 6(1)(f)).
How long
The link to your account: 30 days, or until you close your account. The count with no account stays.

Feedback

What we keep
The message that you send with "Send feedback", the page where you sent it, the time, and the screenshots that you attach.
Why
We use it to fix problems and to make IESDesk better.
Legal ground
Our legitimate interest in a better service (KVKK Article 5(2)(f), GDPR Article 6(1)(f)).
How long
While your account is open. For a closed account, see How long we keep data. Screenshots: 30 days after you send them.

Product news

What we keep
The email address that you give in the news form, the date when you confirmed it, and the date of our last confirmation email.
Why
We send one email to confirm the address. We send news only to a confirmed address, and only the news that the form promised.
Legal ground
Your explicit consent (KVKK Article 5(1), GDPR Article 6(1)(a)). You can take back your consent at any time. Each news email will have an unsubscribe link, or you can write to us.
How long
Until you unsubscribe or ask us to delete it. If you do not confirm the address, we delete it 30 days after our last confirmation email. An address that you gave before 28 September 2026 gets its confirmation email when IESDesk launches.

Attempt limits

What we keep
Counters of the attempts to sign in, sign up, reset a password, confirm an email address, join the news list, and use the free tools. Each counter is keyed by your IP address, or by your account when you are signed in. A second counter limits the account emails that one address gets. It is keyed by a one-way hash of the email address, not by the address.
Why
We use them to stop automated attacks, and to stop floods of email to one person.
Legal ground
Our legitimate interest in a safe service (KVKK Article 5(2)(f), GDPR Article 6(1)(f)).
How long
A counter of attempts counts for 1 or 3 minutes, and the email counter for 1 hour. Then they stop counting. The cache deletes old entries when it stores new ones, normally within 2 weeks.

Page visits

What we keep
When you open a page of iesdesk.com, Plausible counts the visit for us. It keeps the page address, the address of the page that sent you, the browser, the operating system, the device type, and a location (country, region and city) that it finds from your IP address. Plausible stores no IP address, no raw browser details and no cookie. It counts a visitor with a code that changes each day, so it cannot link your visits across days or across websites. The password reset page, the email confirmation page and the news confirmation page send nothing to Plausible, because their address holds a secret link.
Our server also tells Plausible when a tool gives you a result, when you create an account and when you confirm your email address. It sends the name of the tool, the file format (IES or LDT) and whether you are signed in. It sends no file name, no file content and no email address. It passes your IP address and browser details to Plausible so that Plausible can count the visit, and Plausible treats them as above. IESDesk keeps no copy of these events.
Why
We use the counts to learn which pages and tools people use and how they find IESDesk.
Legal ground
Our legitimate interest in knowing how the site is used (KVKK Article 5(2)(f), GDPR Article 6(1)(f)).
How long
Plausible keeps the counts until we delete the IESDesk site from our Plausible account.

Server logs

What we keep
For each request to IESDesk: the time, the IP address, the browser details, the page address and the result. The logs hold no passwords, email addresses, file names or file content.
Why
We use them to keep the service safe, and to find and fix faults.
Legal ground
Our legitimate interest in a safe service that works (KVKK Article 5(2)(f), GDPR Article 6(1)(f)).
How long
Each version of the application keeps at most 10 MB of log, and removes older lines. Each week, the server removes the old versions with their logs and keeps the five newest.

Chat apps

You can connect IESDesk to a chat app that you choose, for example Claude or ChatGPT. The app can then use the IESDesk tools with your account.

IESDesk sends the answers of its tools to that app. An answer can hold the names of your files, the values of their text fields, for example the name of a luminaire or its maker, and the figures and pictures of a result. A file name or a text field can hold personal data, for example a name. An answer is not built to hold a whole file, or the angle and candela tables of a file.

The company that runs the app, for example Anthropic or OpenAI, gets these answers because you ask for it. That company decides how it uses them, under its own terms and privacy notice. It is not one of the companies in Who else handles data, because it does not work for us. It can be outside Türkiye and the EU. We send the answers abroad only to do the work that you ask for in the chat (KVKK Article 9, GDPR Article 49(1)(b)).

The files that you drop in the IESDesk box in the chat go straight to IESDesk. They are not sent to the AI of the app. When the box cannot open in your app, the chat gives you a link to a page on iesdesk.com. The files that you send on that page also go straight to IESDesk.

What we keep
  • For each connected app: the name of the app, the date of the connection and the time of its last use. You see them in Connected apps on your account page.
  • The keys that let the app use your account. We keep each key only as a one-way hash.
  • The files that you send from the chat, their names, and the changes to their text fields that you ask for in the chat.
  • For each Confirm or Download button in the chat: a one-way hash of its key, and the work that it belongs to.
  • For each day and each tool: the number of checks of your account, and the number of times that it reached a limit. These counts hold no file name.
Why
We use it to connect the app and to do the work that you ask for in the chat. We use the counts for the daily limits, and to set the size of the limits. Each time an app connects to your account, we send you one email. It helps you find a connection that you did not make.
Legal ground
Our contract with you, and our legitimate interest in a safe service with fair limits (KVKK Article 5(2)(c) and (f), GDPR Article 6(1)(b) and (f)).
How long
  • An upload of one, two or three files: at the latest 25 hours after you send it.
  • An upload of a folder: 30 days, as the uploaded files of a batch.
  • The record of a connected app: while the app is connected. After a disconnect, we delete it 30 days later. If an upload of that app stays longer, the record goes with that upload.
  • The keys of an app: at most 30 days after IESDesk makes them. An app that does not use IESDesk for 30 days must sign in again.
  • Confirm and Download buttons: about 1 day after you press the button, or after it stops working.
  • The daily counts of checks: 30 days.

You can disconnect an app in Connected apps on your account page. A password reset or a closed account disconnects every app. When you close your account, we also delete at once every file that you sent from a chat app, except the files that the chat moved to Edit. Those stay as the files of an Edit batch and go when their 30 days end.

How long we keep data

Each item above gives its period. These rules also apply:

  • When you close your account, IESDesk at once deletes your sign-in records, your diagram themes and the link of your refused files to your account. It also deletes your BUG Rating, ULOR, report sheet and Generate jobs, and your diagram, report sheet and variant ZIP files. It also deletes your report sheet logo, the name and the footer line for your report sheets. Your API tokens and your connected apps stop working.
  • A closed account keeps your email address, your password hash, the history of your batches, diagram jobs and saved comparisons, and your feedback. Your uploaded files and export ZIP files go when their 30 days end.
  • To delete all of it, write to agustos@agustos.com from the email address of your account. We delete your account and all data that belongs to it within 30 days.
  • Deleted data stays in the daily server backups of Hetzner for up to 7 more days. Then it is gone.
  • Each night, IESDesk also keeps an encrypted copy of the database and the uploaded files. Each copy stays for up to 31 days. Then it is gone.
  • After we delete an account on request, we keep a one-way hash of its email address and the date. Nobody can read the address from the hash. We use it only to delete the data again if we must restore a backup. We delete the hash 60 days after the erase.

Who else handles data

These companies run parts of IESDesk for us. They use personal data only to give their service to us.

  • Hetzner (Germany) runs the server that holds the database and the uploaded files. The server is in Falkenstein, Germany. Hetzner keeps daily backups of the whole server for up to 7 days.
  • Cloudflare (United States) carries all traffic between your browser and the server, and protects the site against attacks. Its R2 storage keeps the files that IESDesk makes for you in its Eastern Europe (EEUR) location. These are the export, diagram, report sheet and variant ZIP files. They are also the BUG Rating, ULOR, report sheet and Generate result CSV files. R2 storage also keeps the encrypted nightly copies of the database and the uploaded files, in its EU jurisdiction.
  • Resend (United States) sends the emails of IESDesk from its EU region in Ireland. The emails come from hello@mail.iesdesk.com.
  • Plausible Insights OÜ (Estonia) counts the page visits on iesdesk.com. It stores its data in the EU and sets no cookie.
  • Designmodo Inc. (United States) runs Pulsetic, which checks every 5 minutes that two status pages of iesdesk.com answer. It gets no data about users.

We give data to a court or a public authority only when the law requires it (KVKK Article 5(2)(ç), GDPR Article 6(1)(c)).

Transfers abroad

  • The server is in Germany, and Plausible keeps its data in the EU. Under the KVKK, storage on a server outside Türkiye counts as a transfer abroad.
  • Cloudflare, Resend and Designmodo are companies in the United States. Cloudflare handles your traffic in the data centre nearest to you, which can be outside the EU and Türkiye.

We use the safeguards of Article 9 of the KVKK and Chapter V of the GDPR for these transfers, such as standard contracts. Ask us which safeguard applies to each company.

When you connect a chat app, we send the answers of IESDesk tools to the company that runs it. This transfer has no standard contract: we make it because you ask for it. See Chat apps.

Cookies and browser storage

IESDesk sets two cookies. The service needs both of them, so the site shows no cookie banner.

  • _iesdesk_session is set on every page. It holds the messages that a page shows after a form, and a security token against forged forms. Your browser deletes it at the end of the browser session.
  • session_id is set when you sign in, and keeps you signed in. It stays until you sign out, for at most 30 days after your last visit.

The light or dark theme that you choose in the application stays in the local storage of your browser. It never leaves your browser.

When you open files for Edit in this browser, the files, your edits and the list of your batches stay in the storage of your browser (IndexedDB) on this computer. IESDesk does not receive them, unless you choose Save to Your files: then your browser uploads the files and your edits to Your files, as an upload does. They stay for 30 days, or until you delete them on the page or clear the data of your browser.

The scene layers that you turn on or off (Isolux lines, Grid) stay in the session storage of your browser until you close the tab.

The page counts of Plausible use no cookie and no browser storage.

IESDesk sets no tracking cookie and no advertising cookie.

Your rights

Article 11 of the KVKK and Articles 15 to 22 of the GDPR give you these rights:

  • Learn whether we process your personal data, and get a copy of it.
  • Learn why we process it, and whether we use it only for that purpose.
  • Learn who receives it, in Türkiye or abroad.
  • Have wrong or incomplete data corrected.
  • Have your data deleted.
  • Have the recipients told about a correction or a deletion.
  • Limit how we use your data.
  • Get your data in a common, machine-readable format.
  • Object to a use that relies on our legitimate interest.
  • Object to a result that only automated analysis produces and that harms you. IESDesk makes no such decision about you.
  • Take back your consent for product news at any time.
  • Claim compensation for a loss that unlawful processing caused.

To use a right, write to agustos@agustos.com from the email address that your request is about. You can also send a letter to the address above. We answer within 30 days, free of charge.

You can also complain to a data protection authority. In Türkiye, this is the Personal Data Protection Board (KVKK Board). In the EU, you can complain to the authority of the country where you live or work.

No sale of data

We do not sell personal data. We do not share it with advertisers or data brokers. If your browser sends a Global Privacy Control signal, nothing changes, because there is no sale or sharing to stop.

Changes to this notice

We publish each change on this page and change the date at the top. When a change affects how we use your data, we tell you before the change takes effect.