Who does what
You are the controller. You decide what to upload, why, and what to do with the results. That includes deciding whether a drawing containing someone's name or address should be uploaded at all.
We are the processor, for the content you put into the Service: your drawing files, the measurements taken from them, and your exports. We act on your instructions and nothing else.
We are the controller, not your processor, for the data we hold about our own relationship with you — account names and emails, seat roles, Paddle reference IDs, sign-in logs, support correspondence, and marketing consent. That's our own contractual relationship with you and your team, and it's described in our Privacy Policy instead.
What we process, and why
Purpose. To provide measure.expert: storing the drawings you upload, running automatic scans over the sheets you select, letting you measure and correct them, and producing your exports.
Duration. For as long as your subscription runs, plus the deletion period below.
Categories of data subject
- The people on your team who use the Service
- People who happen to appear in the drawings you upload — architects, your own clients, site contacts named in title blocks or annotations
Types of personal data
- Whatever appears inside your drawing files: names, addresses, project references, annotations, revision histories
- Measurements and exports derived from those files
Drawings shouldn't contain health data, biometric data, or anything else under GDPR Article 9. Don't upload it. The Service isn't built for it and we haven't assessed it for that use.
Our obligations
- We act only on your instructions. Your instructions are: our Terms, this agreement, and whatever you do in the Service itself. If you want us to do something else with your data, put it in writing and we'll tell you whether we can.
- If we think an instruction breaks the law, we'll say so before acting on it — as Article 28(3)(h) requires.
- Everyone who touches your data is bound to confidentiality, in writing, and stays bound after they stop working with us.
- We keep your data secure using the measures in Annex B. Those are real measures, not aspirations — if something in Annex B stops being true, we update it.
- We help you answer data subject requests. If someone asks you for access, correction, deletion or portability of data sitting in your account, and you need us to act on it, we'll help within a reasonable time. Most of it you can do yourself in the Service.
- We help you meet your own obligations under GDPR Articles 32 to 36 — security, breach notification, and data protection impact assessments — as far as the information is ours to give.
- We tell you about breaches without undue delay once we become aware of one, with what we know at the time: what happened, which data and roughly how many people are affected, what we're doing about it, and who to contact. We don't wait until we have the full picture to make the first call.
- We delete your data when you're done. See "Deletion" below.
- We show our work. We'll give you the information you need to verify we're meeting this agreement — see "Audits" below.
Sub-processors
You give us general authorisation to use sub-processors. The current list is in Annex C.
- Every sub-processor is bound by written terms at least as protective as this agreement.
- We stay fully responsible for what they do. If a sub-processor causes a problem, that's ours to answer for, not something we point at them for.
- We'll tell you 30 days before adding or replacing one. If you object on reasonable data protection grounds within those 30 days, we'll try to find a workable alternative. If we can't, you can terminate the affected part of your subscription without penalty for the remaining term.
- Emergency replacements — where a sub-processor fails or has to be dropped for security reasons — may happen faster. We'll tell you as soon as we can.
Where your data is processed
Your drawings, measurements and exports are processed in the European Economic Area. Hosting, authentication, transactional email and our auto-scan engine all run in the same EU region.
If that ever changes and personal data has to go outside the EEA, we'll rely on a European Commission adequacy decision where one covers the destination, and where none does, on the Standard Contractual Clauses together with a transfer impact assessment and whatever technical measures it identifies. We'll update Annex C before that happens, not after.
Our group. Colleagues at other companies in our group (defined in the Terms) may access your data where a task requires it — support escalation, development, administration. Every current group entity is in the EEA or a country with an adequacy decision; the list is in Annex C.
Paddle sells you the subscription as merchant of record and handles your payment data as an independent controller under its own privacy policy. That data isn't processed on your instructions or ours, so it's outside this agreement entirely.
Audits
- First stop is documentation. We'll provide the information needed to demonstrate compliance with this agreement — Annex B, our sub-processor terms, and answers to reasonable written questions.
- If that isn't enough, you can audit. Once per calendar year, on 30 days' written notice, during business hours, in a way that doesn't disrupt the Service. More often if a supervisory authority requires it or if there's been a breach affecting your data.
- Audits are at your cost, and anyone conducting one must be bound by confidentiality and can't be a competitor of ours.
- We'll cooperate properly with these. We're a small team, and the practical limits above exist so audits stay workable — not to avoid scrutiny.
Deletion
When your subscription ends, your access stops immediately and we delete your data from our systems within 60 days, in line with the Terms.
Where the law requires us to keep something, we keep only that, only for as long as required, and it stays protected by this agreement while we hold it.
If you want your data returned in a specific format rather than just exported through the Service, ask before your subscription ends — we can't retrieve it afterwards.
Your obligations
- You warrant you have a lawful basis for the personal data you upload, and that you're allowed to give it to us to process.
- You're responsible for what's in your files. If a drawing contains someone's name or address that doesn't need to be there, strip it before uploading — we'd rather not hold it.
- You give your own people the privacy information they're entitled to. We don't have a direct relationship with the individuals named inside your drawings, so we can't do this for you.
- Your instructions must be lawful. If they aren't, we won't act on them.
Liability and term
- Liability under this agreement is subject to the cap in our Terms. This agreement doesn't create a separate or additional pool of liability.
- This agreement runs as long as we process personal data for you, and its confidentiality and deletion obligations outlast it.
- If this agreement and the Terms conflict on data protection, this agreement wins. On anything else, the Terms win.
- Dutch law applies, and disputes go to the courts of Amsterdam — same as the Terms.
Processing summary
- Subject matter
- Processing of personal data contained in drawing files, measurements and exports, on your instructions, to provide measure.expert.
- Purpose
- Storing the drawings you upload, running automatic scans over the sheets you select, letting you measure and correct them, and producing your exports.
- Duration
- For as long as your subscription runs, plus the deletion period in "Deletion" above.
- Data subjects
- The people on your team who use the Service
- People who happen to appear in the drawings you upload
- Data types
- Whatever appears inside your drawing files: names, addresses, project references, annotations, revision histories
- Measurements and exports derived from those files
- Special categories
- None. The Service isn't built for GDPR Article 9 data and hasn't been assessed for it.
- Location
- European Economic Area — a single EU region for hosting, storage, compute, authentication, transactional email and auto-scans.
Technical and organisational measures
These are the measures actually in place. Nothing here is aspirational.
Access control
- Role-based access; production access limited to named individuals who need it
- Multi-factor authentication required for administrative and production access
- Access removed promptly when someone stops needing it
- Authentication handled by AWS Cognito in an EU region
Encryption
- TLS for all data in transit
- Encryption at rest for stored files and databases
Infrastructure
- All application hosting, storage, compute, authentication and transactional email on AWS in a single EU region
- Automatic scans run on our own engine within that same region — no third-party AI service receives your files
Monitoring and response
- Access to production systems is logged
- Sign-in events and IP addresses retained for 90 days for security purposes
- Breach notification process as described above
Organisational
- Written confidentiality obligations for everyone with access
- Written data processing terms with every sub-processor
- Small, named team — no outsourced development or support
We don't hold ISO 27001, SOC 2, or any other third-party security certification. We'd rather say so than imply otherwise. The infrastructure we build on (AWS) holds its own certifications, but that's AWS's, not ours.
Sub-processors
Amazon Web Services EMEA SARL (38 Avenue John F. Kennedy, L-1855 Luxembourg) — hosting, storage, compute, authentication and transactional email, all in the eu-central-1 region (Frankfurt, Germany). Bound by the AWS Data Processing Addendum.
Google Workspace — receives some support notifications forwarded from Amazon SES. EU region.
If this list grows, you get the 30 days' notice set out in "Sub-processors" before the new sub-processor starts processing.
Paddle.com Market Limited (company number 8172165, 30 Old Bailey, London EC4M 7AU, United Kingdom) — independent controller for payment data, as described above.
Access may extend to any company within our group, as defined in the Terms — foryouandyourcustomers Baar AG (Switzerland) and any company in which it holds, directly or indirectly, a majority interest. Every current group entity is located in the Netherlands, Germany, Austria, Greece, Bulgaria or Switzerland — EEA, or for Switzerland, a European Commission adequacy decision — so no Standard Contractual Clauses are currently required for intra-group access.
If the group ever includes an entity outside the EEA or an adequacy country, this needs updating before that access happens, not after.
Questions about any of this?
Email support@measure.expert.