Privacy policy

Last updated: 03 November 2026

This is a translation. The German version is legally binding.

1. Controller

EA Digital Solutions e.U., Liebenauer Hauptstraße 41, 8041 Graz, Austria
Email: office@vedutum.com

2. Principle

We collect as little data as possible. Visiting the public pages sets no cookies, visits are only counted by our own cookieless audience measurement (section 3), there are no advertising or remarketing trackers, and no content from third parties (fonts, maps, videos, social media plugins) is loaded. Fonts, images and logos are stored on our own server or in our storage service and are delivered from our own address; your browser makes no connection to any other provider for them. The 3D model, the demo and the sun position slider on the public pages are calculated entirely in your browser — no provider's model is called and no input is transmitted.

In the software and on a share page, too, nothing loads that would require consent: no statistics script, no third-party service in the browser. The only cookies there are the session cookie after sign-in and the language cookie when you switch the language; both are described under section 8. This is why there is no consent dialogue in the software or on share pages.

3. Hosting, database and server log files

The website is operated by Vercel Inc., 440 N Barranca Ave #4133, Covina, CA 91723, USA; the application runs in the data centre in Frankfurt am Main. Content, enquiries and project data are held in a database of Neon Inc., 209 Orange St, Wilmington, DE 19801, USA (data centre in Frankfurt am Main; the connection to it is encrypted). Uploaded plans, models and generated images are held in the storage service Vercel Blob of Vercel Inc.; the storage region is Frankfurt am Main (Vercel region fra1). When a page is requested, Vercel processes technically necessary data on our behalf: IP address, date and time of the request, the page requested, the amount of data transferred, browser type and operating system, and the page visited before. This data serves to deliver the website, for security and to defend against attacks, and is deleted after a short time. The legal basis is Art. 6(1)(f) GDPR.

Data processing agreements (Art. 28 GDPR) exist with both providers. As both companies are based in the USA, access from the USA cannot be ruled out. The transfer relies on the adequacy decision on the EU-US Data Privacy Framework where the provider is certified, and otherwise on the European Commission's standard contractual clauses (Art. 45 and Art. 46(2)(c) GDPR).

The audience measurement runs only on the public pages. Requests to the software (/app), the dashboard, the portal and the admin area are never counted.

4. Google Analytics – only with your consent

To see which pages are read and how many enquiries and registrations the website produces, we use Google Analytics 4 on the public pages, a service of Google Ireland Limited, Gordon House, Barrow Street, Dublin 4, Ireland. It is not loaded in the software or on share pages. The service is loaded only if you have consented beforehand. Without your consent, no Google script is loaded, no cookies are set and nothing is transmitted to Google.

After your consent, Google processes on our behalf: pages viewed and time spent, referrer, approximate location based on the truncated IP address, device type, browser and operating system, and events such as submitting the contact form. Cookies are set in the process (among others _ga and _ga_<ID>, lifetime up to two years) and a random identifier is assigned, by which returning visits are recognised.

We have chosen the settings so that the IP address is truncated, no Google signals are collected and no data is used for personalised advertising. Through Google's consent mode, advertising and personalisation purposes remain permanently set to “denied”; only the statistics function is enabled. The retention period in Google Analytics is limited to 14 months.

The legal basis is your consent (Art. 6(1)(a) GDPR, § 165(3) TKG 2021). A data processing agreement exists with Google. Processing in the USA by Google LLC cannot be ruled out; it relies on the adequacy decision on the EU-US Data Privacy Framework, in which Google is certified, and additionally on the standard contractual clauses (Art. 45 and Art. 46(2)(c) GDPR). Information from Google: policies.google.com/privacy.

You can review and change your settings at any time, and withdraw a consent you have given as easily as you gave it: Open privacy settings

We store your decision exclusively locally in your browser (Local Storage, key vedutum.consent.v1) so that we do not have to ask you again on every visit. This storage is technically necessary to implement your choice; it contains no identifier and is not transmitted to us. If you delete the website data in your browser, this decision is deleted as well. The legal basis for this storage is § 165(3) TKG 2021 (strictly necessary).

5. Contact form and email

Enquiries made through the contact form are stored in our access-protected system and forwarded to us by email (via the email provider named under section 8). We process name, contact details, where applicable the company, and the content of the enquiry solely to answer it and to prepare a quotation. The legal basis is Art. 6(1)(b) GDPR. Enquiries that we have marked as completed are deleted automatically six months afterwards; if a collaboration comes about, the statutory retention periods apply.

Newsletter. If you sign up for our newsletter in the footer of the website, we store your email address, the language chosen, the time and wording of your consent, the page of the sign-up and the browser identifier. You first receive an email with a confirmation link (double opt-in); the sign-up only counts once you click it, and we do not use unconfirmed entries. The legal basis is your consent (Art. 6(1)(a) GDPR), which you can withdraw at any time via the unsubscribe link in every issue; the address is then marked as unsubscribed and no longer written to. The newsletter comes once a month and is put together automatically from new articles and the software's new features; a few days before sending, the issue is with us for review. Every issue contains the unsubscribe link, also as the unsubscribe function of your mail program (List-Unsubscribe). For each issue we store to which address it went and when, so nobody receives it twice. Sending runs through the email provider named under section 8. There is no open or click tracking.

Push notifications. On the pages under “Knowledge” you can switch on notifications about new articles. This happens only if you click “Activate” on the card “New articles as a notification” and then agree in your browser's dialogue; before that, the page asks for nothing and stores nothing. Your browser then registers a subscription with its manufacturer's push service: for Chrome, Edge and other Chromium browsers, Firebase Cloud Messaging of Google Ireland Limited (Gordon House, Barrow Street, Dublin 4, Ireland); for Firefox, the push service of Mozilla Corporation (USA); for Safari, the Apple Push Notification Service of Apple Inc. (USA). These services deliver our messages to your device; processing in the USA cannot be ruled out. We store the address of the subscription at the push service (endpoint URL), the two keys with which each message is encrypted, the language of the page, the browser identifier, the time of the last notification and the number of failed deliveries, but no name and no email address. When a new article appears, we send the article's title, short description and link once, encrypted, through this service; the manufacturer sees that and when a message goes to your device, not its content. To display it, your browser stores a script of this website (service worker at /sw.js); we set no cookie for this. If you choose “No thanks”, your browser remembers this for 30 days in local storage (entry eads-push-dismissed with the time; not transmitted to us). The legal basis is your consent (Art. 6(1)(a) GDPR, § 165(3) TKG 2021). You can withdraw it at any time with “Deactivate” on the same card or by switching off notifications for this website in your browser settings. With “Deactivate” we delete the entry immediately; if the push service reports that a subscription no longer exists (for example after being switched off in the browser), we delete it at the next dispatch.

6. Software and customer projects

Account. For an account in the software we process name, email address, where applicable office or company, the password in encrypted form (hash), the plan, the balance and consumption in points, the language chosen, whether the guided tour has been completed, the settings for white label and the visible AI labelling and, once a plan has been taken out, the Stripe identifiers named below. To lock an account after repeated wrong passwords, the sign-in system also stores the number of failed sign-in attempts and, in the case of a lock, the time until which it applies. The legal basis is Art. 6(1)(b) GDPR. When an account is created, we hold the IP address for one hour in the server's working memory in order to allow at most three accounts per connection and hour; it is not stored in the database (Art. 6(1)(f) GDPR, protection against abuse). For customers of the software, the data processing agreement (Art. 28 GDPR) also applies; it comes into being when an account is created and names the sub-processors in full.

Use of the software. So that we know whether the software is used and where it gets stuck, we record for each account when a sign-in and a sign-out took place and which steps followed: project created, floor plan read, image or video generated, share link created, brochure created, order. We store the time, the account, the type of step, a short label (such as the project name) and the points consumed. We do not store the IP address, device, browser or pages visited, and there is no evaluation across several websites. The legal basis is our legitimate interest in secure and traceable operation (Art. 6(1)(f) GDPR). We delete these records automatically after twelve months, and immediately with the account.

The office's brand. In the account you can store a logo, two colours, a typeface, contact lines and a website. The logo is reduced in size in the browser and stored with us as a small PNG in the database; all of it appears on your brochures, on the brochure page and on the social media images that you generate, and is deleted with the account. The legal basis is Art. 6(1)(b) GDPR.

Project. For a project we store what you create and generate in it: title, name of the client, address and coordinates of the plot, notes, instructions for the image model, uploaded floor plans and 3D models, the recognised geometry, the neighbouring buildings from OpenStreetMap, generated images, clips and panoramas, the logs of the model calls (instruction, settings, duration, points), comments made through the share link and the approval. The purpose is the agreed service (Art. 6(1)(b) GDPR). Panoramas and sun studies are created entirely in your browser and are transmitted to us only when you save them in the project.

Recognition, image and video. For recognising floor plans (unless Anthropic reads them, see the next paragraph), the check run and the generation of images and clips, we transmit the uploaded plan page, the model view generated in the browser (including depth image) and your free-text instructions for the image model to Google Ireland Limited, Gordon House, Barrow Street, Dublin 4, Ireland. We do not pass on account data. What is printed on the plan page goes along, however — including a title block with client, address, planner or stamp; crop or black it out before uploading if it does not belong there. The calls run through Google's developer interface on the paid tier. Processing is not tied to a region (Google's worldwide data centres, so also by Google LLC in the USA); Google stores inputs for a limited time for abuse checks and does not use them to train its models. We do not store the view sent to the model; the instruction and settings of each call remain as a log in the project for twelve months and are then deleted automatically. A data processing agreement (Art. 28 GDPR) exists with Google; the bases named under section 3 apply to the transfer to the USA.

Reading floor plans with Anthropic. The walls, openings and rooms of a floor plan may be read by a language model from Anthropic. Our contracting party is Anthropic Ireland, Limited, 6th Floor, South Bank House, Barrow Street, Dublin 4, Ireland; processing also takes place at Anthropic, PBC in the USA. For this we transmit the plan page and your note for the reading, but no account data. What is printed on the plan page goes along, however, including a title block with client, address, planner or stamp; crop or black it out before uploading if it does not belong there. If the reading at Anthropic fails, the Google model named above reads the same plan. The calls run through Anthropic's business customer interface. Under its commercial terms (as of 17 June 2025) Anthropic may not use customer content to train models. According to Anthropic (as of 1 July 2026) it deletes inputs and outputs within 30 days, unless it has to keep them longer: up to 2 years for a violation of its usage policy, or because of legal obligations. The legal basis is the agreed service (Art. 6(1)(b) GDPR). Anthropic's data processing addendum (Art. 28 GDPR) applies; for the transfer to the USA it contains the standard contractual clauses of the EU Commission.

Plan samples to improve recognition. For every floor plan recognition we keep a plan sample: the file as you selected it (for a PDF the whole document, not only the page read; up to 4 MB), the page sent to the model together with the crop and the lines read from a vector PDF, the model's response, the recognised geometry and — as soon as you save the plan in the editor — the state as corrected by you. With these we check where the recognition goes wrong and measure new versions of the instruction against the stored corrections before we put them into use. We do not use the samples to train a model and do not pass them on to third parties; only for this comparison is the stored page sent again to the Google or Anthropic models named above, under the same conditions as for recognition. Only we, as the operator, can view them, not other customers. What is printed on the plan is contained in it, including a title block with names or address. The legal basis is our legitimate interest in reliable recognition (Art. 6(1)(f) GDPR). We delete plan samples automatically after twelve months, immediately with the project or the account, and at any time on your request to the address named under section 1.

Photos of the plot. For the “Place in photo” function you can upload photographs of the plot into a project (reduced in the browser to 2000 pixels; date taken and focal length from the EXIF data are adopted, other EXIF data are not evaluated). The purpose is the agreed service: the model is placed into the photograph (Art. 6(1)(b) GDPR). For this we transmit the photo together with the model view generated in the browser, the mask and the depth image to Google Ireland Limited named above as processor, under the same conditions as for images from the model. A photograph of the plot can show third parties — passers-by, neighbours, vehicles with licence plates, neighbouring houses. You are responsible for the photograph: make people and licence plates unrecognisable before uploading, and do not upload photos that you are not allowed to use. The photo, the control points set, the calculated camera, the marked area and the generated montage are stored in the project and shown on the share page for as long as the project exists; they are deleted with the project, and you can delete individual photos in the software yourself at any time.

Address, neighbouring buildings and aerial image. If you enter a plot address in a project, we send this address to determine the coordinates to the Nominatim service of the OpenStreetMap Foundation, St John's Innovation Centre, Cowley Road, Cambridge CB4 0WS, United Kingdom. To query the neighbouring buildings, we send the coordinates to public Overpass servers (FOSSGIS e.V., Germany; Kumi Systems e.U., Austria; private.coffee, Austria) and, as a fallback, to the interface of the OpenStreetMap Foundation, and for the aerial image of the plot, depending on location, to basemap.at (operated by the City of Vienna for the cooperation of the Austrian federal states), to the Federal Office of Topography swisstopo (Switzerland) or to Geobasis NRW (Bezirksregierung Köln, Germany). For the terrain, we send a grid of coordinates around the plot to the open elevation service OpenTopoData (Copernicus EU-DEM), a privately operated public service. It is reached through the network of Cloudflare Inc. (USA); the operator does not state where the server behind it is located, so processing outside the EU cannot be ruled out. Only coordinates are sent, no address and no name. For the brochure, your browser queries, with the same coordinates, the same Overpass servers directly for named places within a radius of 1.5 km (schools, shops, doctors, stops, green spaces, sights, restaurants and cafés); the server concerned then sees your device's IP address, as with any retrieval of a website. If none responds, the VEDUTUM server makes the same query; if a project has only coordinates, we determine the address once via Nominatim's reverse search. We pass the list of these places with their distances, without address and without account data, to the same AI service as for recognition, which proposes three to five short sentences about the location; you can change or delete them in the project. Only the address or coordinates are transmitted, no account data; the providers see VEDUTUM's server address, not yours. The legal basis is Art. 6(1)(b) GDPR. For the United Kingdom and Switzerland, adequacy decisions of the European Commission exist.

Energy sketch. When you open the “Energy” tab of a project, the VEDUTUM server sends the coordinates of the plot (latitude and longitude, no address, no account data) to PVGIS, the service of the European Commission's Joint Research Centre (JRC, Ispra, Italy), and receives a typical climate year and, if modules are on the roof, their yearly yield. For plots in North and South America, the server asks the PVWatts service of the National Renewable Energy Laboratory (NREL, USA) with the same coordinates and the module data instead, if PVGIS does not answer and a key is configured for it; processing outside the EU is then possible. The results are stored with the project. The legal basis is Art. 6(1)(b) GDPR.

Share link. Anyone who opens a share link is not recorded personally; all that is counted is that the page was opened, and when it was last opened. Anyone who leaves a comment through a share link transmits the text entered, the name given voluntarily and the marked point in the model or image; these details are stored assigned to the project so that the commissioned office can read them (Art. 6(1)(b) GDPR, in relation to the commenting person Art. 6(1)(f) GDPR). If the commenting person approves the state via “Approve draft”, their name, the time and the optional comment are stored on the project so that the office can trace the approval. Name, text and point of every comment as well as name and date of the approval are visible on the share page to everyone who knows the link; the office decides who it gives the link to and can withdraw it at any time. No cookie is set and nothing is stored in the browser; only someone who switches the language receives the language cookie named under section 8.

Help: support chat, messages to us and feature requests. Under “Help” in the software you can ask questions, write to us, attach files (JPG, PNG, WebP or PDF, up to five per message and 4 MB each at most; photos and screenshots are shrunk in the browser first) and send feature requests. For this we store your messages and attachments, our replies and those of the AI support, the times, the state of the conversation or request and its link to your account. Attachments are kept in the Vercel Blob storage service (section 3) and are only delivered through an address that first checks that you or we are signed in. Your requests are visible only to you and to us, not to other customers. The AI support answers first, labelled as AI (Art. 50 AI Act): for this we transmit your message, the earlier course of this conversation (up to 16 messages), our product description and a short summary of your account (name, practice, plan, point balance, end of the free month, team, number of projects, plans and images) to Anthropic PBC, San Francisco, USA, whose language model Claude writes the answer; we do not transmit your e-mail address or your attachments. Anthropic processes this data through its business API as a processor (Art. 28 GDPR), does not use it for training and deletes it according to the rules of that API; the transfer to the USA is based on the EU Commission’s standard contractual clauses in Anthropic’s data processing agreement (Art. 46(2)(c) GDPR). You can skip the AI support at any time (“Write to the team directly, without AI”) or hand over to a person (“Talk to a person”); messages with an attachment, or about invoices, refunds, data protection or legal matters, go to us without AI. When a conversation is handed to us or a new request arrives, we receive an e-mail with the beginning of the message (at most one per conversation and hour). When we reply or the state of your request changes, you receive an e-mail with the link into the software. The purpose is support under our contract with you (Art. 6(1)(b) GDPR). Conversations, with their messages and attachments, are deleted 24 months after the last message, requests 24 months after their last change, attachments uploaded but never sent after one day; with the account everything goes at once. The data export under “Account” includes conversations and requests.

Payment. Payments (card or SEPA direct debit) are handled by Stripe Payments Europe, Ltd., 1 Grand Canal Street Lower, Dublin 2, Ireland as payment service provider: when a plan is taken out, name, email address, billing address, where applicable VAT number and the payment data are entered on Stripe's payment page and processed there; we store only the customer number, the subscription number, the date of the next billing and the number of the last paid invoice (Art. 6(1)(b) GDPR). We never see card or account data; Stripe's payment page sets its own cookies on stripe.com, to which Stripe's privacy policy applies. Stripe is certified under the EU-US Data Privacy Framework.

References. On the “References” page we show projects only if the office has expressly released them with consent in the software and we have reviewed them; what is shown are title, images and the share page, never the address and never the client's name. In this gallery view the comments are hidden and the approval appears without name and without comment. The consent can be withdrawn in the software at any time, and the entry then disappears immediately (Art. 6(1)(a) GDPR). Customers are not named as a reference without their express consent.

Retention and deletion. Projects together with plans, models, images, logs of the model calls and comments remain stored for as long as the account exists. The office can permanently delete a project in the software at any time; all files and comments of the project go with it immediately, and a share link stops working. Logs of the model calls and plan samples we delete automatically after twelve months regardless. You close your account yourself in the software under “Account” (if a subscription is running, cancel it beforehand in the customer portal). From that moment the account is locked: signing in no longer works, all sessions end, share links and brochures are switched off, connections to AI assistants end, and we send no more mails except the confirmation. So that an accidental click does not cost everything, we keep the locked account for 30 days: for seven days you restore it yourself with the link in the confirmation mail, until day 30 on an informal message to us. For this period we additionally store the time and the optional reason for closing, the switched-off identifiers of share links and brochures (to give them back on restore) and a hash of the restore link. After 30 days we delete the account with all projects, files, logs, comments, support conversations, our internal notifications about the account and the mail log automatically and for good; of the archive entry only the account number and the dates of closing and deletion remain, without name or email address, as proof of deletion. The legal basis for keeping the account during the 30 days is our legitimate interest and yours in getting an accidentally closed account back (Art. 6(1)(f) GDPR); if you want immediate deletion, write to us and we delete without the waiting period. Also under “Account” you receive an export of your data as a JSON file (Art. 20 GDPR). We keep invoice data and orders for seven years (§ 132 BAO).

Interface for AI assistants (MCP). At https://www.vedutum.com/mcp we operate an interface according to the Model Context Protocol through which AI assistants such as Claude or ChatGPT answer questions about VEDUTUM (estimate points, sun position and shadow, check a plan file, print resolution, search our articles, example project and its 3D view, getting started) and — after your account has been connected, see the following paragraph — work in your projects; described on the page AI assistants. It becomes active only when someone sets up VEDUTUM as a connector in their assistant and the assistant calls a tool in response to a question. In doing so we receive the details the assistant transmits for the tool (such as a place or postcode, quantities, a file type, search terms, a project number, a link to a plan file or a desired setting), the IP address of the calling server — usually a server of the platform, not the connection of the person asking — and the identifier of the calling program (user agent). We hold the IP address exclusively in the working memory of the server instance in order to allow at most 120 calls per minute; only the calls of the most recent minute are counted, and the address is stored neither in a database nor in a file. We evaluate the user agent only to mark the links in the response with the platform (utm_source). The details transmitted and our responses are not logged; we neither receive nor store anything of the conversation with the assistant. No cookie is set; the public tools need no account. What is counted per day is how often which tool was called from which platform, whether an account was connected, the account's ID number if one was connected, and whether the call succeeded; in addition, per account, the events connection, disconnection, registration via the connector, first plan recognition and first payment. These counters contain no details of the request and no IP address; we use them for a weekly report to ourselves as the operator and delete the ID number with the account. Independently of this, the server log files of the hosting described under section 3 arise. For the sun position and the address of a building plot, we send the place given to the Nominatim service of the OpenStreetMap Foundation named above under “Address, neighbouring buildings and aerial image”, and for the surroundings the coordinates to OpenStreetMap and the EU-DEM elevation data as described there; these services see VEDUTUM's server address in the process. If a tool loads a floor plan from a link at your request, our server retrieves that address; the operator of the address sees our server. The legal basis is Art. 6(1)(f) GDPR, with a connected account Art. 6(1)(b) GDPR; our legitimate interest is answering a request that the user triggers themselves in the assistant, measuring whether the connector is used, and protecting the interface against overload. For the conversation with the assistant, the providers of the platforms are independently responsible, such as Anthropic for Claude and OpenAI for ChatGPT; their privacy policies apply to it (Anthropic, OpenAI).

Connecting an AI assistant to your account. If a tool needs your account, the assistant signs you in with us via OAuth 2.1: you sign in on our site with your VEDUTUM account (or create one, as described under “Account”) and expressly allow the connection; the page states where the response goes. For every connection we store the ID number of your account, the identifier and the stated name of the program (for programs that register themselves also their redirect addresses and, where applicable, a hashed key), the address to which the sign-in returned, the time of the connection, of the last use and of a disconnection, and the agreed scope. Sign-in codes and access tokens we store only as a cryptographic hash: the code is valid for ten minutes, an access token for one hour, the refresh token for up to 90 days and it is replaced at every renewal. Under Account → Connections you see and disconnect every connection; after that no token works any longer. When the account is deleted, we delete the connections as well. What the assistant changes on your behalf (creating a project, having a floor plan read, furnishing, draft, photovoltaics, address and surroundings, share link) we store like any change in the software; the state before the last change made via the assistant we keep on the project so that it can be undone. If the assistant has a floor plan read, everything stated above under “Recognition, image and video” and “Plan samples” applies to the file. The interface does not generate images or videos. The legal basis is performance of the contract on the use of VEDUTUM (Art. 6(1)(b) GDPR).

Retrievals and visits from AI assistants. To find out whether and how AI assistants use our content, on every request for a public page we check two details that the browser or the retrieving program sends anyway: the identifier of the program (user agent) and the referring page (referrer) together with the markers in the address (such as utm_source). If the user agent matches a published AI crawler (such as ChatGPT-User, OAI-SearchBot, GPTBot, Claude-User, ClaudeBot, PerplexityBot) or a visit comes from the page of an AI assistant (such as chatgpt.com, claude.ai, perplexity.ai, gemini.google.com), we increase a daily counter with the date, type of signal, name of the assistant or crawler and the page requested. We likewise count a newly created account if the registration was opened through a link from our interface for AI assistants. Only this counter is stored: no IP address, no complete user agent, no referring address, no cookie, no assignment to an account or a person; other visits are not recorded. The counters therefore contain no personal data and are kept as statistics. The legal basis for the brief check of the details sent along is our legitimate interest in measuring the reach of our offering in AI assistants (Art. 6(1)(f) GDPR); since nothing is stored on or read from your device, no consent under § 165(3) TKG 2021 is required.

7. Use of artificial intelligence for the website content

For drafts of the texts of this website we use language models of Anthropic PBC (USA) through their business customer interface. No personal data of visitors is processed in the process; the drafts are based on our own content and publicly available sources and — as soon as we send first approaches to companies — the publicly available company data of the business contacted (source OpenStreetMap, the business's website). Every draft is reviewed by a person before publication. Enquiries from the contact form are not transmitted to AI providers. What we use which methods for is stated on the page AI transparency. Images and clips on this website are created in our own software and are labelled there as generated views.

AI assistant (chat at the bottom right). The chat is the HOHEIT Concierge, a service of our company, loaded from www.hoheit.at. When you open it and write, your messages are transmitted to www.hoheit.at and processed there to produce an answer from our stored knowledge; for this we use a language model of Anthropic (Anthropic PBC, San Francisco, USA), to which the message is transmitted without your name and without contact details, unless you write these into the chat yourself. The answers are labelled as AI (Art. 50 AI Act). The conversation history is kept in your browser's local storage (no cookie) and stored by us for 90 days, then deleted. If you fill in the enquiry form in the chat or upload a file, we treat that like an enquiry through the contact form (Art. 6(1)(b) GDPR). After a few messages the assistant asks for name and email address so that we can reply; without these details the conversation ends.

8. Sign-in area, cookies and email dispatch

The sign-in area is intended for maintaining the content and for customers of the software. On sign-in, a technically necessary session cookie is set (payload-token, readable only by the server (httpOnly), valid for seven days from the last sign-in; Art. 6(1)(b) GDPR, § 165(3) TKG 2021). Anyone who switches the language in the software or on a share page thereby sets the cookie vedutum-lang with the value “de” or “en” and a lifetime of one year; it contains no identifier and serves only to keep the chosen language on the next visit (technically necessary for the function expressly requested, § 165(3) TKG 2021). For signed-in persons we additionally store the choice on the account. We also store on the account whether the guided tour of the software has been completed, so that it does not start again. If the office has protected a share link with a password, entering the correct one sets a cookie vedutum-share-… (readable only by the server, seven days, only for this link) that contains nothing about you but merely proves that the password was entered; failed attempts are counted per link for fifteen minutes without storing your address. Visitors to the public pages receive no cookie; on a share page only the language cookie when switching and, where applicable, the password cookie are set, otherwise none.

We send emails to account holders to confirm the account, to reset the password (the link in it is valid for one hour), for new comments and approvals through a share link, for our reply to a message under “Help” and a new state of your feature request, for payment events, two days before the free month ends and when the account is closed or restored (service mails, Art. 6(1)(b) GDPR). For dispatch we use the mailbox office@vedutum.com with our email provider easyname GmbH, Canettistraße 5/DG, 1100 Vienna, Austria. Generated images and videos carry metadata that label them as AI-generated (see AI transparency); this metadata contains no account data, no address and no labels from the project, but only the fixed statement that the image or video is AI-generated and the reference to the labelling obligation on publication.

Tips, news and offers to customers. Account holders also receive a few automated mails about their own use of VEDUTUM, in three kinds that can each be switched off: tips and getting started (in the first weeks, for example when no floor plan has been uploaded yet, a plan has been read or the free month ends in a week), product news (at most twice a month, a summary of new features) and offers (one offer after the free month ends, one message about a month later, and holiday promotions). Which mail goes out when follows fixed rules: sign-up date, end of the free month, plan, whether a plan was uploaded or read and whether an image was made, number of projects and points; the texts are templates, no AI model evaluates your data for this. At most one such mail a day, tips and offers at most one in three days and four in 30 days; paying accounts get no tips or offers, team members nothing about the plan, and while a support request waits for an answer, tips and offers pause. The legal basis is § 174(4) of the Austrian Telecommunications Act 2021 (direct marketing of our own similar products to customers; the option to refuse is offered at sign-up and in every mail) and our legitimate interest in looking after customers (Art. 6(1)(f) GDPR). You can object at any time free of charge: with the tick box at sign-up, with the links “No more …” or “Unsubscribe from everything” at the bottom of every such mail (no sign-in needed, the link is signed with your account number), through the unsubscribe function of your mail program or in the software under “Account”. We store your choice with the time of the last change and a send log (kind of mail, subject, recipient address, language, time, delivery status), so that no mail arrives twice and the limits are kept; the log is deleted with the account. We measure neither opens nor clicks: the mails contain no tracking pixel, the links lead straight to our pages. The links carry campaign parameters (utm_source, utm_medium, utm_campaign) without any personal identifier; they are only evaluated if you have consented to statistics on the website (section 4), and then only as a count per campaign. Whether someone takes out a plan after a mail we count from the send log and the plan change on the account, not from behaviour in the mail. Images in these mails are hosted on our own domain. Discounts from such a mail are deducted automatically in the Stripe checkout; to do so we check at checkout whether the mail went to your account.

First approach to companies. We write to selected companies whose business contact details are publicly accessible (the business's website and imprint, OpenStreetMap, Google business profiles). For this we store company name, website, the business email address, where applicable the name of the responsible person given in the imprint, our observations about the website and every message sent with its time. Sending runs through the service Resend (Plus Five Five, Inc., USA; processing in the Ireland data centre) from the address adam@mail.vedutum.com. Resend reports delivery, bounces and complaints to us. We also count whether a message was opened (via an invisible image that is loaded from t.mail.vedutum.com when it is opened) and whether a link in it was clicked (links lead via t.mail.vedutum.com for this purpose); time and number are stored, assigned to the individual message. Before every dispatch we compare the address with the ECG list of the RTR and our suppression list. The legal basis is our legitimate interest in the business first approach (Art. 6(1)(f) GDPR); a data processing agreement exists with Resend. Every message contains an unsubscribe link. A click on it or an informal reply is enough: we then enter the address and domain permanently in our suppression list and do not write again. We keep the suppression list so that your objection is respected permanently; we delete the other details at any time on your request.

9. Your rights

You have the rights of access, rectification, erasure, restriction of processing, data portability, objection and withdrawal of consents given (Art. 7(3), Art. 15 to 21 GDPR). To exercise them, contact office@vedutum.com informally; you carry out the export and deletion of your account yourself in the software under “Account”. Direct complaints to the Austrian Data Protection Authority, Barichgasse 40-42, 1030 Vienna, www.dsb.gv.at.

10. Changes

This policy is adjusted when the website or the legal situation changes. The version published here at the time applies.