Privacy statement
How Schaduwplan handles your data.
Short and honest: we collect as little as possible. The 3D viewer works without an account and without tracking cookies. What you do in the viewer (address, scenario, projects, optional attachments) stays locally in your own browser until you erase it yourself. One exception: with an error report we send the address you are working on and what you typed in the search bar to our error monitoring (Sentry), so we can fix the error. To purchase a report we need, at a minimum, your email and the address of the report.
Last updated: 11 November 2026
In short
Schaduwplan is a web application for sunlight studies (bezonningsonderzoek) on Dutch addresses. The 3D viewer runs entirely in your browser: we do not record what you do. Only when something goes wrong do we send an error report to our error monitoring. What we do do is explained per section below.
- No tracking cookies, no advertising pixels, no ad networks. What we do do: error monitoring via Sentry (EU) across the whole site, and in the logged-in part of the app pseudonymised product analytics via PostHog (EU), linked to your account id. On public pages no persistent identifier and no cookies. See Processors below.
- If something goes wrong on the site, your browser sends an error report to Sentry (EU). It contains the address you are working on in the viewer (street, house number, postcode, town, municipality, BAG identifiers and coordinates) and what you typed in the search bar in the same session. Without that data we cannot reproduce an error at a specific address. See Processors.
- Address searches go directly from your browser to PDOK (Kadaster). 3D models are fetched via our own Cloudflare cache from 3DBAG; height data from PDOK and Ellipsis Drive (the official AHN distribution partner). Once an address has loaded, we check once with Ruimtelijke Plannen (Informatiehuis Ruimte / DSO), via our own proxy, whether the zoning plan there publishes a building plot with maximum heights — that is how we know whether we can offer that feature. See Third parties & sources.
- Your work (addresses, projects, optional attachments, any height uploads) is kept by the viewer functionally in your own browser — in localStorage and IndexedDB. None of it reaches our servers; only an error report carries the address (see above). See Cookies & local storage and the cookie statement for the full list.
- When you purchase a report we process your email, invoicing details and the address of the report.
Controller
The controller within the meaning of the GDPR (Article 4(7)) is:
- Trade name: Schaduwplan
- Business: Schaduwplan is operated as a sole proprietorship (eenmanszaak) under Dutch law.
- Chamber of Commerce (KvK) number: 99118998
- VAT ID: NL005372731B91
- Registered address: the business address registered with the Chamber of Commerce can be retrieved via kvk.nl. For formal correspondence and GDPR requests the email address below is sufficient.
- Contact: [email protected] — for privacy questions, support, complaints and everything else.
- Data Protection Officer: Schaduwplan does not qualify as an organisation for which the GDPR (Article 37) requires a DPO. Questions you would put to a DPO can be sent directly to [email protected].
Age & minors
Schaduwplan is intended for use by people aged 16 or over (Article 8 GDPR, Dutch implementation practice). The service is not aimed at children under 16 and we do not knowingly collect personal data from minors.
Do you suspect we have unintentionally collected data from a child under 16? Email [email protected] — we will delete that data without undue delay.
Which data we process
Depending on how you use the service, different categories of data are processed. We deliberately split them into "locally in your browser" (which Schaduwplan technically cannot access) and "at Schaduwplan":
Locally in your browser (functional storage, only on your device — we cannot reach it):
- Recently searched addresses — at most 6, in localStorage, so you can jump back quickly in the address bar. Contains street, house number, postcode, town, RD/WGS84 coordinates and BAG id.
- Saved projects — in IndexedDB (database
schaduwplan, storeprojects), when you save a scenario via Projects → Save. Contains the address, planned buildings, measurement points and the chosen moment in time. Any heights derived from a GeoTIFF upload are included as a measured value in the saved project — we never keep the raw GeoTIFF itself ("extract-and-discard"). - Scene source data — in IndexedDB (database
schaduwplan-sources): the answers the viewer fetched for an address from 3DBAG, PDOK (BAG buildings, Kadaster parcels) and AHN (height rasters), so a paid report computes with the same data as the preview. Open geodata, no personal data; the request addresses do contain the coordinates of the area around your address. An answer is used for up to 7 days after the source delivered it; after that the viewer erases it the next time you open it. When you sign out or delete your account, the viewer erases the whole database. At most 200 MB; above that the oldest answers go first. - Permit attachments — in localStorage, when you upload a PDF or photo of a building permit or drawing under "Adjust source data" to support a manual height correction. At most 5 MB in total.
- Waitlist email — in localStorage, if you leave your email address via the "Sign in / accounts are coming" popover. That email stays on your device until the real account functionality goes live — only then do we explicitly ask you again to submit it.
- Temporary session state — in sessionStorage, to hand over a chosen address from the landing page to the viewer and to remember "do not show again" choices within one session. Erased as soon as you close the tab.
Full keys and retention periods are listed in the cookie statement.
At Schaduwplan (only when you buy a report):
- Report purchase: your email address, the address of the report, and (for Business) optionally a company name and KvK number for invoicing.
- Payments: Stripe processes the payment. We only receive a transaction reference, amount and date — no card number.
- Contact: when you email [email protected] we keep that correspondence.
- Server logs from our hosting (Cloudflare Pages): technical access data (IP address, timestamp, requested path) as every web server does. Cloudflare keeps these for a short time for security and debugging and does not share them with us in aggregated or identified form.
- Error reports (Sentry): when something goes wrong, the report contains the technical error, the address you are working on (street, house number, postcode, town, municipality, BAG identifiers and coordinates) and what you typed in the search bar in the same session. Search input is only sent if an error occurs in that session.
What we use that data for
- Delivering the purchased report (PDF by email).
- Processing payments and issuing invoices.
- Answering contact requests.
- Finding and fixing errors (error reports via Sentry).
- Legal obligations (tax retention duty on invoices).
We never use your data for marketing purposes beyond your request, never sell it to third parties, and carry out no profiling.
Legal basis (GDPR)
- Performance of the contract — for delivering the report you purchase.
- Legal obligation — for invoicing and the tax retention duty.
- Legitimate interest — for handling your contact requests, and for finding and fixing errors. An error that occurs at one address only cannot be found without that address. You can object to this (see Your rights).
Third parties and external sources
To make the 3D viewer work we connect to a number of external services. Some connections run directly from your browser to the source, others run via our Cloudflare cache (so we do not overload the upstream API and you get faster responses):
- PDOK Locatieserver (Kadaster) — address autocomplete and BAG building resolution. Directly from your browser. A government service; no personal data recorded beyond the search itself.
- 3DBAG (TU Delft + 3DGI) — 3D building models and building attributes. Via our Cloudflare Pages function at
/api/bag3d/*(24-hour edge cache, because 3DBAG sends no CORS headers). Open data, CC BY 4.0; no personal data — although Cloudflare does log standard access metadata such as IP and timestamp for security. - PDOK (AHN4) — height data via WCS. Directly from your browser. Open data.
- Ellipsis Drive (AHN5 / AHN6) — more recent height data, only when 3DBAG is outdated for your building or could not produce a roof fit. Ellipsis Drive is a Dutch SaaS appointed by AHN as the official distribution partner for AHN5+ (see ahn.nl/dataroom). Directly from your browser. No personal data.
- Ruimtelijke Plannen API (Informatiehuis Ruimte / DSO) — building plot and maximum eaves and building height from the zoning plan, for the permitted building volume. Once per loaded address, automatically, so the viewer knows whether this zoning plan is published digitally; after that only if you click “Try again” yourself. The coordinate of the searched address then goes via our own Cloudflare Pages function at
/api/rp/*to this government service; our API key stays server-side. Read responses are edge-cached for at most 24 hours; the searches are kept for at most 7 days in a shared response cache. What is kept there is the government service's own answer — open planning data — under a key in which your address is not readable. That is a readability measure, not anonymisation: the real protection comes from the access boundary and the 7-day retention. The values you confirm stay in your browser and only enter your report at checkout. - Cloudflare Pages — our hosting. Serves the website and the 3DBAG cache from EU edges. Cloudflare sees standard web server logs (IP, timestamp, path).
- Stripe (Stripe Payments Europe Ltd, Ireland) — for payments (not yet live at the time of this statement). An EU processor with its own privacy policy.
We use no Google Analytics, no Meta Pixel, no Cloudflare Web Analytics and no advertising or social tracking. For error monitoring we use Sentry (EU) with privacy-conservative settings; for product analytics in the logged-in part PostHog (EU). Both are described in detail under "Processors" below. Fonts (Fraunces, Inter Tight, JetBrains Mono) are bundled into our build via @fontsource — so no request goes to Google Fonts or a comparable CDN.
Linking your own AI
In the viewer, “AI connector” links your own AI assistant, for example Claude or ChatGPT, to the scene in your tab. Your AI reads the scene and places structures, measurement points and windows. This is what happens to your data:
- The scene stays in your browser. Your own AI gives the instructions; your browser carries them out in the tab you have open.
- Our link service only passes things on. The service at
schaduwplan.nl/mcp(a Cloudflare Worker) passes your AI's instructions to your browser and the answers back. These can hold data from your scene, including the address. The service holds them in memory only while it passes them on, and does not store them. Only the address line your tab shows and your tab's IP address are held while your tab is connected: the address line to tell your AI when it links, the IP address to limit how many new connections one network opens at once. After that the IP address stays in the counter below for up to one hour. - Log. For each call, and when a link starts or ends or your tab connects, the service writes short lines to Cloudflare Workers Logs: which tool your AI used, whether it worked, how long it took and a shortened hash of the link. When an AI app connects, its name is logged too. Never an address, a coordinate, text from your scene, the pairing code or a token. Cloudflare itself records the URL of each request; when your tab reconnects, that URL holds the number of the link. That number opens nothing without the secret only your tab knows.
- Abuse limits. The service counts per IP address of your tab or your AI (per /64 block for IPv6) how many new links and wrong codes or tokens there were in one hour. That counter lives in Cloudflare KV and disappears after one hour.
- Product analytics and error reports. PostHog receives that you asked for a code, that an AI linked and that a link ended, with the reason (for example Unlink or expired) and whether an AI was linked. Per call it receives: the tool name, the outcome (worked or an error code), the duration, whether the tool changes the scene, and the name of the AI app. Never the code, a token, an address, a coordinate, a building or the content of a call or answer. When your AI places something, the same goes along as for placing by hand: for a structure its kind (for example extension), the scenario and that your AI placed it; for a measurement point the number of points and whether it belongs to a window. The same events go along as a trail in an error report from the viewer to Sentry. When running a call fails, an error report goes to Sentry with the tool name, the name of the AI app and only the place in the code, without the error message itself; otherwise the same data as every other error report from the viewer (see In short).
- Your AI sees the scene, including the address. What your AI provider (for example Anthropic or OpenAI) does with your conversation falls under that provider's terms and privacy policy. You choose and use that AI yourself; the provider is not a processor of Schaduwplan.
- End of the link. The link ends when you click Unlink, when your tab reloads or has been closed for more than a minute, when another window takes it over, after 30 minutes without a call from your AI, after 8 hours at most, and when Schaduwplan ends the link. For 8 hours after that the service keeps only the fact that the link ended, so your AI is told; then nothing of it is left.
Legal basis: legitimate interest. The link only works when the service passes the instructions on, and the log and the counter keep the service safe and running. You can object to this (see Your rights); you can also simply not use the link.
Processors (GDPR Art. 28)
For the services listed below we work with a data processing agreement (DPA) or the supplier's standard DPA. All with an EU establishment or an EU-residency guarantee. A complete up-to-date list, including DPA versions and transfer mechanisms, is in our sub-processor register (GDPR Art. 30).
- Cloudflare, Inc. — hosting (Cloudflare Pages, Workers, R2 object storage, Queues, DNS). EU edges; R2 bucket in EU jurisdiction; standard DPA and EU SCCs for any transatlantic sub-processing.
- Supabase Inc. (eu-central-1, Frankfurt) — database (Postgres with Row Level Security), authentication and Realtime broadcasts for the customer dashboard. Own DPA with EU SCCs Module 2.
- Stripe Payments Europe Ltd (Dublin, Ireland) — payment processor for the paid reports: Stripe Checkout for the transaction, Stripe Tax for automatic VAT calculation and Stripe Invoicing for invoice generation. EU entity, PCI DSS Level 1, own DPA.
- Resend (eu-west-1, Ireland; Plus Five Five, Inc.) — transactional email (report ready, payment error) via the subdomain
mail.schaduwplan.nland SMTP relay for Supabase Auth emails (password reset, email verification). EU SCCs Module 2 + EU-US DPF. - Sentry (de.sentry.io, Frankfurt; Functional Software, Inc.) — error monitoring for the frontend and the render Worker. With an error in your browser, Sentry receives the address you are working on (street, house number, postcode, town, municipality, BAG identifiers and coordinates) and what you typed in the search bar in the same session; after sign-in linked to your account id. We send no IP address (
sendDefaultPii: false), no session replay, sample rate 10% for performance traces. Own DPA v5.1.0 with EU SCCs Module 2. - PostHog, Inc. (eu.posthog.com, AWS Frankfurt) — product analytics. On public pages without a persistent identifier and without cookies (
disable_persistence: true); in the logged-in part linked to your account id for conversion-funnel analysis, with opt-in via the terms of use at registration. No session recording, no heatmaps, no autocapture. Own DPA + EU SCCs Module 2. - Zoho Corporation B.V. (EU) — incoming email for
hello@,privacy@,security@and similar aliases under@schaduwplan.nl. Standard Zoho DPA based on Model Contractual Clauses. - Backblaze, Inc. (B2, region EU Central, Amsterdam) — storage of our encrypted offsite backups of the database and the report files. Those backups are encrypted with OpenPGP before they are sent; Backblaze does not hold the key and cannot read the contents. Standard Backblaze DPA with EU SCCs; Backblaze is certified under the EU-US Data Privacy Framework.
Any future expansion of the stack will be added to this statement in advance, at least 30 days before it is put into use. Sentry and PostHog were announced on this date (2026-05-14) and go live with the Schaduwplan paid-backend MVP. Since 2026-09-19 Backblaze replaces Zoho WorkDrive as the backup store, without that notice period: Backblaze stores only encrypted files and has no access to their contents.
International transfers
We aim to process data within the European Economic Area (EEA). Cloudflare and Stripe are, however, part of groups with US parent companies, which means supporting processing may occasionally take place outside the EEA. Where that is the case, we rely on the standard safeguards the GDPR prescribes:
- a valid adequacy decision of the European Commission (such as the EU-US Data Privacy Framework, insofar as the receiving party is certified under it); or
- the European Standard Contractual Clauses (SCCs), supplemented where appropriate with additional safeguards such as encryption and pseudonymised processing; or
- another appropriate safeguard in accordance with GDPR Chapter V.
An up-to-date list of our processors and their transfer mechanism is available on request via [email protected].
How long we keep data
At Schaduwplan:
- Report data (the scene with its measurement points and the report PDF): 12 months after purchase, for support and recalculation. After that we delete it automatically, unless you ask us to keep it longer. What stays: the address, the report ID, the hash of the PDF and the issue date, so that a court or municipality can still check that a PDF really came from us. If you delete the report or your account, the address goes too. An order you do not complete is deleted after 12 months.
- Invoices: 7 years (statutory tax retention duty, Art. 52 AWR).
- Contact emails: at most 24 months.
- Backups: an encrypted copy of the database (daily) and of the report PDFs (weekly), kept outside the production environment. Daily copies are overwritten after 31 days, monthly copies after 6 months. An overwritten copy stays as a hidden version for 30 more days and is then deleted automatically.
- Hosting / server logs: Cloudflare keeps access logs at edge level for at most a few days by default. We ourselves log nothing structurally. Error reports at Sentry, with the address and the search input, are kept for at most 90 days.
Locally in your browser — we do not set these periods, you do:
- sessionStorage is erased as soon as you close the tab.
- localStorage and IndexedDB remain until you erase them via your browser settings, via "Clear recent addresses" / "Remove attachment" in the viewer, or until your browser cleans up on its own (e.g. iOS Safari eviction after prolonged inactivity). The viewer erases the scene source data itself: each answer the next time you open the viewer after 7 days, and all of it when you sign out or delete your account.
- For projects you can optionally allow
navigator.storage.persist()so the browser does not clean up your work unprompted.
Your rights under the GDPR
You have the right to:
- Access to which data we hold about you.
- Correction of inaccurate data.
- Erasure ("right to be forgotten") within what the tax retention duty allows.
- Restriction of processing.
- Data portability.
- Object to processing based on legitimate interest.
- The right to complain to the Dutch Data Protection Authority (autoriteitpersoonsgegevens.nl).
Questions about your rights? Email [email protected]. We respond within the statutory period of four weeks.
Account and data deletion
You have the right to have your data and (future) account deleted.
- Local data (3D viewer) you can erase yourself via the browser settings for schaduwplan.nl, or via the "Delete" buttons in the viewer.
- Self-service at schaduwplan.nl/app/settings — if you have an account, you can there (a) delete your account with all associated report data at the press of a button, and (b) download a JSON export of all your data (Art. 20 GDPR — right to data portability). Confirmation follows immediately in the UI.
- By email is also possible, from the email address known to us, to [email protected]. We confirm the deletion within the statutory period of 30 days (extendable by 60 days for complex requests).
- What we are legally required to keep: invoices remain under the tax retention duty (Art. 52 AWR — 7 years), even after a deletion request. A deletion request for this category is refused on the basis of Art. 17(3)(b) GDPR (statutory retention duty). If you delete a report or your account, we delete the address, the scene with its measurement points and the report PDF at once. A record stays with the report ID, the hash of the PDF and the dates, linked to the invoice. When you delete your account, we unlink that record from your account. One exception: if there is a dispute about your payment (a chargeback through your bank or credit card), we keep the report and the data as evidence while that dispute runs, and after that until 12 months after purchase.
- Backups: your deletion takes effect immediately in the live environment. We do not search or edit backups — they are overwritten automatically and the old version is deleted 30 days later, so at most 7 months after your request your data is gone from those too. We restore a backup only on data loss, never to bring deleted data back.
- Stripe keeps a payment history separate from Schaduwplan. If you also want their copy deleted, you can do so via privacy.stripe.com.
Security
The website runs on Cloudflare Pages with TLS 1.3. Payment data is processed by Stripe with PCI DSS Level 1 compliance. Emails are sent and stored encrypted (TLS). Report PDFs are stored encrypted. Local browser storage is accessible only to you — we have no read access to it.
We back up the database every night and the report PDFs every week. Those backups are encrypted before they leave our build environment, and the key that opens them is kept offline — so the storage provider cannot read them. Every backup is restored into a throwaway database in the same automated run and checked for completeness; if that fails, the run fails visibly instead of silently.
Data breaches
Should a data breach involving your personal data unexpectedly occur and present a risk, we will report it in accordance with Article 33 GDPR within 72 hours of discovery to the Dutch Data Protection Authority. Where the breach is likely to result in a high risk to your rights and freedoms, we will inform you directly without undue delay (Article 34 GDPR). Do you suspect a breach yourself? Email [email protected] as specifically as possible.
Changes to this statement
We announce substantial changes via a banner on the website at least 30 days before they take effect. Small editorial changes we publish quietly, with an updated "last updated" date at the top.
Contact
Questions, complaints or requests: [email protected]. We respond within one business day.