Privacy policy
Last updated 2026-10-21
Your board photographs are used for your identification and its confirmation record, and for nothing else unless you switch that on yourself. Everything we run is in the EU except the companies named in section 5. You can export or delete all of it from your account page without asking us, and delete it from the deletion page without signing in.
1. Who is responsible for your data
The controller is KAUDATA RAČUNALNIŠKO PROGRAMIRANJE D.O.O., Kidričeva cesta 2 B, 3320 Velenje, Slovenia. Registration numbers and tax numbers are on the imprint page.
For anything about your data, write to [email protected]. You will get an answer within one month, which is the period Art. 12(3) allows.
Our data protection officer is Aljaž Božiček, KAUDATA d.o.o., and can be reached at [email protected].
We are the controller for everything described here, including the photographs you upload, except what Google does with what its ads receive (section 8b). We decide what is stored, for how long, which AI provider reads it and what goes into the marking database, and we apply the same answer to every customer. Nobody can instruct us to handle their uploads differently.
That matters if you are a repair shop rather than a lone technician, because you may be a controller of your own customer’s data and may need a data processing agreement with us under Art. 28. Read section 5a before you assume you have one.
2. What we collect
- What you upload. Photographs of a component and the board around it, the marking as we read it, the package, the designator, the device make and model, and the circuit context you type or answer.
- Your account. Email address, and your name and profile picture if you sign in with Google. Locale and country, and the language of the page each identification was asked from and each purchase was made from. No password, because we do not use them.
- Billing. Billing address, country, VAT identification number if you give one, and what you bought, or the free trial you started and the code you started it with, if any. Card details go straight to Stripe and never reach our servers; for a free trial, Stripe saves the card so that the charge at its end can be made.
- Evidence of your location. Billing country, the country that issued your card, and, where the network in front of our servers tells us, the country your IP address resolves to. EU VAT law requires two of these, and we store each of them we have.
- Confirmations. Whether an identification fixed the board, which part it turned out to be, and any note you add.
- How visitors arrive. When a page is opened from a link on another site, the domain of that site, such as example.com, is added to a count for the day. Nothing else is kept with it: not the page the link was on, not your address, and no cookie or account, so the count cannot be traced back to anyone.
- Codes not in our tables. When no part in our tables is printed with exactly the code you type, we count that code to know which codes to add, keeping only the code and its count, never who searched or from where, for 13 months after it was last searched for.
- How the website is used. Each page you open, measured with Matomo. Section 8a says what that records and how to object.
- Ads on public pages. We collect nothing for them ourselves. The website shows Google’s ads to visitors who are not signed in, and Google receives your IP address, information about your browser and device, and the address of the page directly from your browser. Section 8b says what else Google receives and what you can choose.
- Your network address, when you use the service without an account. A keyed hash of it counts the free identifications made without an account, because a cookie or an app install costs nothing to replace. We keep the hash, never the address, with the month and the number of identifications made from it, and the same hash beside each identification or lookup it counted, so that one that fails can be given back. Everyone on the same network shares the count. Section 7 says how long it is kept.
- Through an AI assistant. When ChatGPT, Claude or another AI assistant looks a code, a value or a part number up in WhatSMD for you, our server receives what it looks up and the network address the request comes from: the assistant's server, or your computer if the assistant runs there. We keep no record of what was looked up. We keep a keyed hash of the network address and, if the assistant sends an anonymised user identifier as ChatGPT does, a keyed hash of that, never the address or the identifier itself. They are used only to limit how often one address or one person can ask, and are deleted within 3 days. Otherwise we count only how many lookups each assistant made with each tool each day.
- Technical records. Request logs including IP address.
- What you type into the free-text fields. The circuit context, your answers to the questions we ask back, and any measurement you note down. These go to the AI provider with the photographs, so do not put a customer’s name or contact details in them.
- A team. If you are in a team on the Shop plan: its name, who owns it, who is in it and since when, the team’s monthly count, and the invitations the owner has sent, each with the address it was sent to. Section 3a says who sees what.
- A subscription bought in the app. If you subscribe in the iPhone or Android app, what Apple or Google tells us about that subscription. Section 4a says what that is.
- Your answers about results. When you tell us whether a search found your part, which listed part it was or was not, or what was printed, we keep the code, your answer, the part numbers and those few words, with the day, for 25 months. After a photograph we also keep the identification it continued, which links the answer to your account, browser or app until that identification is deleted, and to nobody after; otherwise we keep nothing about who you are or where you connected from. An answer about a teammate’s identification is kept with theirs and is in their export. A “This was it” or “Not this one” on an answer of your own is kept with that answer and goes when it does.
- Codes you ask to be told about. If you ask us to email you when a code is added, we keep your email address, the code, the language of the page and when you asked and confirmed. Without an account we first email a link to confirm, and delete the request if it is not confirmed within 7 days. Once the code is added we email you once and delete the request; if it is still missing after 12 months, we delete it then. Every such email has a link that deletes all your requests, and signed in you can cancel them on your account page.
2a. Businesses we write to
Sometimes we write to a repair shop to offer it WhatSMD. For that we keep the business name and town, the business email address, contact form or business social-media account (such as Instagram) it published, the page where we found it, and the dates and content of our messages and of any reply. We use only addresses and accounts a business has published for its customers, never a private one.
We write once with the offer, and at most once more if there is no reply. On a business’s social-media account we write the same way, as a direct message: once, at most one follow-up, and a reply there is enough to make us stop. The legal basis is our legitimate interest in offering our service to businesses that could use it (Art. 6(1)(f)).
We keep this for at most 12 months after our last contact, then delete it. If you ask us not to write again, we keep only your address or account name and the date, for as long as we write to businesses, so that we never write to you again.
To object, just reply to our message, or write to the address on the imprint page. We stop, and we do not write to you again. You can also ask to see or delete what we hold, through the contacts in section 1, and complain to a supervisory authority as section 10 says; in the United Kingdom that is the Information Commissioner's Office.
3. Why, and on what legal basis
| What we do with it | Legal basis |
|---|---|
| Running an identification you asked for: reading the photo, retrieving candidates, ranking them and storing the result | Performance of a contract, Art. 6(1)(b) |
| Your account and sign-in, and keeping your identifications and listing them in your history | Performance of a contract, Art. 6(1)(b) |
| Taking payment, running free trials and the reminder before one ends, issuing invoices, and keeping the VAT records and the evidence of your location that the law requires | Legal obligation, Art. 6(1)(c), and performance of a contract, Art. 6(1)(b) |
| Recording your confirmation that a part fixed the board, and adding the marking-to-part pair to our marking database | Legitimate interests, Art. 6(1)(f): making the service accurate |
| Keeping the service running and safe: error reports, abuse and fraud prevention, cost limits | Legitimate interests, Art. 6(1)(f) |
| Understanding which parts of the product are used, and which site a visitor arrived from | Legitimate interests, Art. 6(1)(f) |
| Emailing you when a code you asked about is added to our tables | Consent, Art. 6(1)(a). You can withdraw it at any time with the link in every email about it, or on your account page |
| Writing to repair shops to offer them WhatSMD, and remembering who asked us not to write again | Legitimate interests, Art. 6(1)(f): offering our service to businesses that could use it (section 2a) |
| Recording that a deletion or an export was asked for and carried out | Legal obligation, Art. 6(1)(c): showing we honoured the request, Art. 5(2) |
| Using your photographs beyond your own identification, to improve the models we use | Consent, Art. 6(1)(a). Off by default, and nothing does this today (see section 4) |
| Running a team on the Shop plan: its members, its invitations, its shared monthly count, and showing each member the identifications the others start in it | Performance of a contract, Art. 6(1)(b): the one the business made with us for its team. For someone invited who has not joined yet, legitimate interests, Art. 6(1)(f): letting them join the team that invited them |
| Recognising a subscription you bought in the app as yours, keeping your access in step with it, and confirming the purchase to Google | Performance of a contract, Art. 6(1)(b) |
| Showing ads from Google on the website’s public pages to visitors who are not signed in, to help pay for the free service (section 8b) | In the EU, the EEA, the UK and Switzerland: consent, Art. 6(1)(a), for personalised ads and for cookies used for more than detecting fraud, given in Google’s consent message. Legitimate interests, Art. 6(1)(f), for limited ads and the cookies Google says they use only to detect fraud. Elsewhere, legitimate interests, Art. 6(1)(f) |
We do not sell your data, and we do not profile you to make decisions about you. We give Google nothing for its ads ourselves, not your account and not your email address. Google’s ad code does run inside the pages with ads, though, so it can see what those pages show and what you type or upload there (section 8b).
3a. If you are in a team on the Shop plan
A business buys the Shop plan for its staff, and the person who buys it owns the team. Being in a team changes who sees some of your data. This is exactly what.
- Who is in the team. The owner and every member see each member’s email address and the date they joined. The owner also sees the address of each invitation still open.
- What is shared. An identification you start while the team is on the Shop plan is filed under the team. Every member can see it in the team’s history with your email address beside it, and can open, read and continue it: its photographs, what you typed and measured, the answer, and whether it fixed the board. They can add their own measurements and answers to it.
- What stays yours. What you identified before you joined, your account details, your invoices, your answers about the AI provider and your photo-training choice. Publishing an identification to a public link stays with whoever started it. Deleting one stays with whoever started it and the team’s owner, and deletes it for the whole team. When the team’s plan ends, nothing is shared any more, and each person keeps what they started.
- Invitations. To invite someone, the owner gives us their email address. We keep it with the invitation and email them once, in their own account’s language, or the owner’s if they have no account, naming the team and the owner’s address. The invitation stays open for 14 days, and is deleted at the first daily clean-up after it is accepted, declined, withdrawn or has expired.
- Leaving. If you leave or are removed, what you identified for the team stays in its history. If you close your account, you leave the team at once, and when the account is erased 30 days later, what you identified is erased too, including what the team could see. If the owner closes theirs, the team takes no one new and its plan runs to the end of the period already paid for, but no longer than until the owner’s account is erased. At that erasure the team is deleted, and each member keeps what they identified.
4. Your board photographs
A board photograph is often a customer’s property, and it can show a serial number, an asset tag, a repair sticker or a name. We treat the photographs accordingly.
- They are used to read the marking, to give the model the visual context it needs to rank candidates, and to keep the record of the identification you can look back at.
- They are not used for anything else. Not to train a model, not to build a public dataset, not for marketing. There is a photo training setting in your account, off by default, which is the switch we would use if that ever changed. Today nothing reads it, because no such training or export exists. If we build one, the switch will gate it, it will stay off until you turn it on, and turning it off again will apply from that moment onwards.
- They are stored under keys nobody can guess. Reads go through a signed link that stops working after 15 minutes, so a URL copied out of a page expires.
- Delete an identification from History or from its own page and its photographs go with it, together with the stored objects themselves. Delete your account and all of them go.
- If you publish a result page, the photographs on it become readable by anyone who has the link, which is the point of a shareable result. Stop sharing on the result page withdraws the link and it stops working. Look at what is in frame before you publish, because we cannot know whose board it is.
- Search engines are asked not to index shared result pages, for the same reason. That is an instruction to a crawler and not a lock: a published link works for anyone who has it.
- An identification made without signing in is kept against a cookie rather than an account, and erased with its photographs 90 days after it was made. History in that browser lists it with the day it is kept until, and you can delete it sooner. If you shared it, the shared link stops working when it is erased. When you sign in, History offers to move this browser’s identifications onto your account; nothing moves unless you choose it, because a shared computer may hold someone else’s work. Once moved, they are kept as your account’s other identifications are.
Please do not upload a photograph containing personal data you have no basis to share with us. If you do it by accident, delete the identification from History or from its own page, or write to us and we will delete it.
4a. The mobile app
The WhatSMD app for iPhone and Android phones uses the same service as this website, and everything in this policy applies to it. It adds these:
- An install id. The first time it runs, the app makes a random value, keeps it in the phone's secure storage and sends it with every request. It does for the app what the anonymous key does for the website (section 8): it shows that the results of identifications made without an account are yours. From version 1.3.0, History in the app lists the identifications made on that install without an account, each with the day it is kept until, and you can delete one sooner; when you sign in, it offers to move them onto your account, and nothing moves unless you choose it. The free identifications themselves are counted for your network, not for the install (section 2). It is not taken from the phone and says nothing about the phone or about you, and reinstalling the app makes a new one. We never store it as it is, only a keyed hash of it, which is also what the records of which steps of the product were used are kept under (section 7).
- A sign-in code instead of a link. The app signs you in with a six-digit code sent to your email address, because a link would open in the browser rather than in the app. A code works once and for 10 minutes, and we keep only a hash of it until it is used or runs out. Once you are signed in, the app keeps its sign-in token in the phone's secure storage until you sign out.
- Your permission before anything goes to the AI provider. Before the app first sends a photograph, or what you tell it about a circuit, to OpenAI (section 5), it asks you, naming OpenAI. We keep each answer: yes or no, the provider it named, the date of this policy, the time, and the account or install it came from. Without a yes on record, the app's requests that would reach OpenAI are refused. A later no is kept the same way and stops them again. Searching by typing a code never reaches OpenAI and never needs your permission.
- Reports on answers. If you report an answer in the app as wrong, offensive or something else, we keep the reason and any note you write with that identification, to check how accurate the answers are.
- Deleting your account from the app. Signed in, you can delete your account from the app as you can from the account page on the website, with the same result: sign-in stops at once, on every device, and the data is erased 30 days later (section 9).
- Your team. If you are in a team on the Shop plan, the app shows its name, your role, its seats and the team’s monthly count, and the team’s identifications as section 3a describes. Members and invitations are managed on the website.
- Subscribing in the app. The app sells the Tech plan as a subscription through the App Store and Google Play. For those purchases Apple or Google is the seller: they take the payment, charge the VAT, renew, cancel and refund under their own terms, and handle your payment details under their own privacy policies. We never receive your card, your bank details or your Apple or Google account.
- How a purchase finds your account. Signed in, the app gives the store a reference we make from your account's id, so the purchase comes back to the account that made it. It is not your address and names nobody to the store. A purchase stays with the account that made it: restoring it while signed in to another account is refused, and the app then shows the address of the account it belongs to, with most of it hidden.
- What we receive about it. From the app and from Apple's and Google's messages to our server: the store's reference for the subscription, the product and plan, whether it was a test purchase, whether the period running is a free trial, its state (active, in a grace period, retrying payment, paused, ended, refunded or revoked), when the paid period ends, whether it renews, and the price and currency the store charges. We check Apple's signature on each, and read Google's back from Google, before we use it. We ask Apple and Google about a purchase only by the store's own reference, and tell Google that we have recorded it; we send them nothing else about you.
- How long. The subscription's record is kept while your account exists and erased with it, and holds only the latest summary we verified, never the store's signed receipts. Each message a store sent us is kept on record for 90 days (section 7).
- Deleting your account does not cancel it. Only you can cancel a subscription bought in the app, in the App Store or Google Play. Closing your WhatSMD account leaves it running, and the app, the account page and the deletion page say so first and link to the store.
5. Who else processes your data
We use these companies to run the service, and give each one only what its job needs. The list is built from how this deployment is configured, so it lists exactly who it sends data to: each company by name, and the network provider in front of our servers by what it does.
| Who | What for, and what they see | Where |
|---|---|---|
| Network provider | Answers for our domain, and carries the traffic between you and our serversYour IP address and your requests, including what you send, while they are in transit | United States |
| Stripe | Card paymentsYour email, billing address, card details, and what you bought | United States and Ireland |
| Resend | Sign-in links, receipts, account email and the emails about codes you asked forYour email address and the contents of those messages | United States |
| OpenAI | The AI model that reads the marking and ranks the candidatesYour photographs, as image data, and the circuit context you type. Not your name, your email or any account identifier | United States and Ireland |
We send the AI provider the images and the text, and nothing that names you: no account identifier, no email address, no session identifier.
What OpenAI publishes about data sent through its API: it is not used to train or improve OpenAI’s models unless the customer opts in to sharing it, and it is kept in OpenAI’s abuse-monitoring logs for up to 30 days, longer only where the law requires it or where OpenAI needs it to protect its services or others from harm. We call OpenAI’s Responses API without switching its storage off, so OpenAI also keeps each response for at least 30 days. These are OpenAI’s own terms, on its data controls page, not settings this application makes.
What binds each of them, and what covers data that leaves the European Economic Area:
- Network provider: Its data processing agreement is part of its terms of service, and it is certified under the EU-US Data Privacy Framework.
- Stripe: Its data processing agreement is part of the Stripe services agreement, and Stripe, LLC, which receives the data in the United States, is certified under the EU-US Data Privacy Framework.
- Resend: Its data processing addendum is part of its terms of service, and transfers out of the EEA are made under the standard contractual clauses the addendum incorporates. Resend is also certified under the EU-US Data Privacy Framework.
- OpenAI: A customer in the EEA contracts with OpenAI Ireland Ltd. OpenAI’s data processing addendum is part of its services agreement, and transfers out of the EEA are made under the standard contractual clauses or an adequacy decision of the European Commission.
This table does not include Google’s ads on the website (section 8b): for them, Google does not process data for us but decides for itself what it does with what it receives.
5a. If you are a business photographing a customer’s board
A board on your bench usually belongs to someone else. A photograph of a bare board is a photograph of a thing and not personal data at all. It becomes personal data when it carries something that points at a person: a serial number you can match to a repair ticket, an asset tag, a name sticker, a screen with something on it.
When that happens you are the controller of that data, because you decided to photograph it and to send it to us. What we are is the question, and the honest answer today is that we are a separate controller and not your processor. Three things in how the product works make that so, and each one is a design decision rather than an oversight:
- We use what you send for a purpose of our own. A confirmation you submit can be promoted into our marking database, which is our asset and the thing that makes the next technician’s answer better. A processor may not do that.
- We set the retention periods, and there is no way for you to change them.
- There is no channel through which you could instruct us. There is no per-customer configuration and no contract in which your instructions would be the thing we follow.
The practical consequence is on you rather than on us, and the terms say so: you need your own basis for handing us a photograph that carries your customer’s data, and the cheapest way to have one is not to: frame the shot on the component, and keep names, serial numbers and tickets out of the text fields.
Business customers can ask for a data processing agreement under Art. 28 at [email protected].
6. Where your data lives
The application runs on servers Kaudata operates in Slovenia (EU). Its database runs on the same servers.
Photographs and invoices are stored on those servers as well, on a disk of the application's own, and so are the backups of them and of the database.
Your requests reach those servers through a network provider, which sees your IP address and your requests while they are in transit. It is in the table in section 5, described by what it does.
The companies in section 5 established outside the EU are the network provider in front of our servers, Stripe, Resend and OpenAI. What each one sees is in the table.
7. How long we keep it
| What | How long | Why |
|---|---|---|
| Identifications, results and the photographs attached to them, made while signed in | Until you delete one yourself, or your account | They are your working history. You can delete one yourself from History or from its own page, and its photographs, answers and share link go with it |
| Identifications made without an account, with their photographs | 90 days, then erased with the photographs, unless you delete one sooner or move them to your account when you sign in | There is no account to keep them on, so we erase them. Until then, History in the browser they were made in lists them with the day each is kept until. A shared link to one stops working when it is erased |
| The count of free identifications made without an account: a keyed hash of the network address, the month and the number | The month it counts and 3 days after it ends, then deleted, and the hash taken off the identifications and lookups it counted | It is only needed while the month runs. It holds a keyed hash of the address, never the address |
| Lookups through an AI assistant: a keyed hash of the network address, and of the assistant's anonymised user identifier where it sends one | At most 3 days | Only needed while the limit on how often one can ask runs. What was looked up is not kept at all |
| Your account | Until you delete it. Deletion takes effect immediately and the records are erased 30 days later | The 30 days is a recovery window against an accidental or hostile deletion |
| Confirmed marking-to-part pairs promoted into the marking database | Indefinitely, with your account no longer attached | Once separated from the account it is no longer personal data, and it is what makes the next answer better |
| Invoices, payment records and the evidence of your location behind them | 10 years from the end of the year they relate to | Slovenian VAT law and the EU one-stop-shop rules require it. These cannot be deleted on request |
| The raw record of a payment as the payment provider sent it | 90 days after it arrives, once it has been processed | The order and the invoice are the accounting record. This copy is kept only to investigate a payment that went wrong |
| Your free trial: when it ran, the billing details and the card's country recorded for its first charge, and the code it was started with | While your account exists; erased with it. The first charge copies what its invoice needs onto the order, which is kept as invoices are | To make and invoice the charge at the end of the trial, to keep to one trial per account, and to count how often each code is used |
| A subscription bought in the app, as the store last told us about it | While your account exists; erased with it | To keep your access in step with the store's record of what you bought |
| The record of each message Apple or Google sent us about a subscription | 90 days after it arrives | To show which messages were applied, and to answer a question about a subscription |
| Sign-in sessions | 90 days, or until you sign out, or immediately when you delete your account | Long enough not to be asked every week, short enough to expire on a lost device. Expired sessions are deleted daily |
| Sign-in links | 15 minutes. Deleted when used, or daily once expired | A link is only useful for as long as it takes to open the email |
| Sign-in codes (the app) | 10 minutes. Deleted when used, or daily once expired | A code is only useful for as long as it takes to read the email |
| The app's answers about the AI provider | Given signed in: as long as the account, then deleted with it. Given without an account: 13 months | So we can show that you agreed, and to what, for as long as that matters |
| Reports on answers from the app | As long as the identification they are about | They are about that answer and are no use without it |
| Answers about whether a search found the part | 25 months | Long enough to see how the answers change from one year to the next. After a photograph, an answer is linked to that identification while it exists, and to nobody after |
| Requests to be emailed when a code is added: your address, the code and the language | Unconfirmed: 7 days. Confirmed: until the code is added and you are emailed, and at most 12 months | So we can email you once when the code is added. After that email we keep a keyed hash of your address for 2 days, so no address gets more than one a day |
| Your membership of a team on the Shop plan | While you are in it: until you leave, are removed or close your account, or until the team is deleted with its owner’s account | It is what puts you on the team’s plan and shows you its identifications |
| Invitations to a team, with the address each was sent to | Until accepted, declined, withdrawn or expired after 14 days, then deleted at the next daily clean-up | It holds the address of someone who may never have an account, so it is kept no longer than it is open |
| Account deletion requests made without signing in | The link works for 24 hours. The request is kept for 24 months | It is the record that a request was made and honoured. It holds a keyed hash of the address, never the address |
| The cached answer the model gave for a photograph | Until the entry expires, and never longer than 90 days | It is keyed by a hash of the image rather than by your account, so deleting the account does not reach it; the age limit does |
| A "Look it up for me" request: the code, anything you typed with it, and the answer | 7 days after it is asked for, or sooner when the account is erased | So the answer can be shown while it is being worked out, and again if you come back to it. It holds a keyed hash of who asked, never your address. The parts it confirmed stay in our marking tables without it |
| Our own record of which steps of the product were used | 13 months, or until you delete your account | Long enough to compare a month with the same month a year earlier, and no longer |
| The log of what an administrator did, and of every export, deletion and erasure | 24 months | It is how we answer for what happened to an account. Your address is removed from it when your account is erased |
| Backups of our servers, which include the database and the stored photographs and invoices | Taken regularly by Kaudata’s own backup system. Something erased disappears from them as the older copies expire | So the service can be put back after a failure or a mistake. They stay on our own servers, and are used for nothing but restoring the service |
| Server and request logs | As long as the servers that write them keep them. No fixed period is set, so we publish none | To find and fix faults, and to look into abuse of the service. They are deleted by the system that keeps them, not by the daily job below |
| Website analytics: the record of each visit to this website (section 8a) | At most 25 months. Aggregated statistics that no longer relate to anyone are kept | Deleted by Matomo itself, on our own server, not by the daily job below |
Every period above that we set ourselves is enforced by a job that runs daily and deletes what has reached it. Where a row says that another system deletes the records, that system does it, not our daily job.
8a. Website analytics
We measure how this website is used with Matomo, an analytics tool we run ourselves at analytics.kaudata.si on servers operated by KAUDATA d.o.o. We do not share the data with anyone. Requests to the analytics server pass through the network provider that carries its traffic. Matomo does not use cookies.
For each page view it records the page address and title, the page you came from, the time, your browser, operating system, device type, screen size and language, and your approximate location (country, region and town), which is looked up from your IP address. It also records clicks on links to other websites and on file downloads. On the search, marking, price and information pages that is the link's address without its query string; on every other page, such as your account, your results and sign-in, it is only the other website's address, or for a file from this website its address with any identifier removed. Only a shortened IP address is stored: the last two of the four parts of an IPv4 address, or everything after the first three of the eight groups of an IPv6 address, are removed.
We use this to see which content is read and to improve the website; the legal basis is our legitimate interest (Article 6(1)(f) GDPR). Records of individual visits are deleted after at most 25 months; aggregated statistics that no longer relate to anyone are kept. You can object at any time with the switch below. Your browser then stores one cookie, mtm_consent_removed, which records only that choice.
8b. Ads on the website
To help pay for the free service, the website shows ads from Google on its public pages: the search, the SMD code book and the marking pages, the guides, the resistor colour code and capacitor code pages, How this works and Pricing. Only visitors who are not signed in see them; anyone signed in sees none, whatever their plan. There are no ads in the iPhone and Android apps. Nor are there any on sign-in, on the history and account pages, beside the result of an identification or a shared result, or on the legal pages.
When a page with ads opens, your browser loads Google’s ad code from Google’s servers. Google then receives your IP address, information about your browser and device, the address of the page, which on the search includes the code you searched for, and the page you came from, together with any cookies Google set in your browser before. The ad code runs inside the page, so it can also see what the page shows and what you type or upload there. We give Google nothing for its ads ourselves.
In the European Union, the rest of the European Economic Area, the United Kingdom and Switzerland, Google first shows its own consent message. It asks whether Google and the advertising partners it names may store and read cookies and similar data on your device and use them for ads. What follows depends on your answer:
- If you consent to personalised ads, Google may use cookies and similar storage to choose ads from your interests and to measure how they perform.
- If you consent to cookies but not to personalised ads, Google shows non-personalised ads, chosen from the page you are reading and your approximate location. Google says these still use cookies to limit how often an ad is shown and for aggregated reports.
- If you do not consent, Google shows limited ads where it can. They are not personalised, and Google states that the cookies and local storage they use serve only to detect fraud and invalid traffic, a use for which Google does not require consent.
You can change your answer or withdraw your consent at any time with Privacy and cookie settings at the foot of a page with ads, which opens Google’s message again. Withdrawing consent does not affect what was done with it before.
Elsewhere, third-party vendors, including Google, use cookies to serve ads based on your prior visits to this website or other websites. Google’s use of advertising cookies enables it and its partners to serve ads to you based on your visits to this website and other websites on the internet. You can opt out of personalised advertising in Google’s My Ad Center, and out of other vendors’ use of cookies for personalised advertising at www.aboutads.info.
For what it does with this data, Google is a controller in its own right, not a processor working for us. It explains its use in How Google uses information from sites or apps that use our services, and lists the cookies its ad products set, with how long each lasts, on its cookie information page. For visitors in the European Economic Area and Switzerland, the Google company responsible is Google Ireland Limited, Dublin, Ireland. For visitors in the United Kingdom it is Google LLC, in the United States. Google may transfer the data to Google LLC, which is certified under the EU-US Data Privacy Framework.
In the EU, the EEA, the UK and Switzerland, our legal basis for personalised ads, and for cookies used for more than detecting fraud, is your consent. That is Art. 6(1)(a) GDPR, and the consent that the Slovenian Electronic Communications Act, ZEKom-2, requires before information is stored on or read from your device. For limited ads, and the cookies Google says they use only to detect fraud, it is our legitimate interest in funding the free service (Art. 6(1)(f)). Elsewhere it is that same legitimate interest.
9. Your rights, and how to use them
Under the GDPR you can ask for a copy of your data, correct it, delete it, restrict or object to what we do with it, and take it elsewhere in a machine-readable form. Where we rely on your consent you can withdraw it at any time, without that affecting what happened before.
Two of those are buttons on your account page rather than an email to us.
- Export. Account, then export. You get a JSON file with your account, every identification, every result, every confirmation, your orders, your invoices, your subscriptions, including any bought in the app, your free trial, your answers about the AI provider, your reports on answers, your “Look it up for me” requests, your requests to be told when a code is added, your team membership and the invitations sent to your address. Identifications a teammate started are theirs, and are in their export rather than yours. The file does not include these records we also hold about you: the usage events (section 7), the record of the model calls made for you, any check of a VAT number, the monthly and daily counts of your use, and your sign-in sessions. Write to [email protected] and we will send them to you.
- Delete. Account, then delete account. If you cannot sign in, use the deletion page instead: it emails a link to the account’s address, which works once, for 24 hours. Either way the account is closed immediately, your sessions are ended, a subscription paid on this website is set to end with the period already paid for (one bought in the app is not: only you can cancel it, in the App Store or Google Play), and processing stops. The records are erased permanently 30 days later, photographs included. What outlives that is in section 7: the invoices and the VAT records behind them, for 10 years, because tax law requires it; the log that the account was closed and erased, with your address removed; and records keyed by something other than your account, such as a cached model answer or a payment record, until their own period ends.
- Stop sharing. On any result you published, the button beside the share link withdraws it.
- Photo training consent. A single switch in your account settings, off unless you turn it on. Section 4 says what it does and does not currently do.
If you used the service without an account, there is no account page to do any of this from. History in the browser you used lists the identifications made there, known by that browser’s anonymous key (section 8), each with the day it is kept until, and you can delete one from History or its own page. They are erased 90 days after you made them, unless you move them to an account when you sign in.
For anything the buttons do not cover, write to [email protected].
10. Complaining about us
Tell us first if you can, at [email protected]. You also have the right to complain to a supervisory authority. In Slovenia that is the Information Commissioner, Informacijski pooblaščenec, Dunajska cesta 22, 1000 Ljubljana. If you live elsewhere in the EU, you can go to the authority for your own country.
11. Changes to this policy
When this policy changes, the date at the top changes with it. If a change materially affects how we handle what you have already given us, we will email you before it takes effect.