Version 1.0. Only the German text is binding. This English version is for understanding only.
Parties
Controller (the "Client"): the office (a brokerage or a sole agent) that uses Immvela and accepts this agreement electronically through an owner or admin (section 6.2).
Processor (the "Contractor" or "SNS"): SNS Software Solutions GmbH, Schrötlgasse 8a, 1220 Vienna, Austria, company register number FN 683051, Commercial Court Vienna, VAT ATU83471949, represented by its managing directors Samuel Winch and Samson Adefris Belachew, email office@sns-austria.com. "Immvela" is a product of SNS, not a separate legal entity.
The main contract is Immvela's terms of use or, for an office in the pilot, the pilot agreement between the Client and SNS.
1. Subject matter
1.1 Tasks. SNS provides the Immvela software as an online service at app.immvela.com and in doing so processes personal data on the Client's behalf. Processing means storing, displaying, organising, transmitting to the sub-processors in Annex 2, exporting and deleting data that the Client and its users enter or upload, for the following functions, as far as they are unlocked for the Client:
- (a) Quill (listing texts): drafts of social captions, brochures and Exposés from facts the user confirmed; storing the drafts and the texts the user kept; the property chat.
- (b) Dossier (documents): storing property documents (for example the Energieausweis, Grundbuchauszug, tenancy agreement) with a dated trail; reading proposed values out of documents, which are used only after the user confirms them; requesting documents from owners through an upload link.
- (c) Vignette (virtual staging): furnished variants of the Client's photos.
- (d) Verlag (publishing): publishing posts to the social accounts the user connected and fetching those posts' total figures.
- (e) Export and deletion under section 3.8.
1.2 Relation to the main contract. This agreement supplements the main contract. On data-protection matters this agreement prevails.
1.3 Data categories. The following categories of personal data are processed:
- (a) User data of the Client's staff: email address, password (stored only as a hash at Supabase), office name, language, display and chat settings, role in the office.
- (b) Business cards and brand data: name, role, phone, email, office address, portrait, logo.
- (c) Property and listing data: address, property type, confirmed facts (for example living area, year built, price, energy figures), free-text selling points, listing status and dates.
- (d) Documents: property documents (among others the Energieausweis, Grundbuchauszug, Nutzwertgutachten, Wohnungseigentumsvertrag, tenancy agreement, title deed, owners' meeting minutes), which can name third parties; files owners upload through the link; the log of requests to owners and property managers with the answer status; the dates an Energieausweis was shown and handed over.
- (e) Media: photos, videos, floor plans, staged images, brochures as PDF. Photos can show people, house numbers and occupied interiors.
- (f) Generated texts, texts the user edited or kept, the user's style statements, the user's chat messages about a property.
- (g) Connected social accounts: encrypted access tokens, account id, display name (for LinkedIn the email address instead), scheduled posts, total figures per post (nothing about individual commenters).
- (h) Activity log: who generated, confirmed, requested or published what and when; some entries hold contact details printed on brochures, the user's style statements or short free text.
- (i) Counters of AI calls and stagings per user.
Special categories of personal data (Art. 9 GDPR) are not intended. The Client does not upload documents whose purpose is processing such data. A single document, such as a tenancy agreement, can contain such data in a given case; nothing technical prevents it.
1.4 Data subjects.
- The Client's staff with their own login (agents, assistants, office managers) and colleagues for whom a business card is created;
- owners and co-owners of the properties, sellers and buyers, tenants, creditors, property managers and issuers of energy certificates, as far as they are named in documents or upload files through the link;
- people visible in uploaded photos or videos.
Prospective buyers and leads are not recorded in a structured way at present. If that changes, this agreement is supplemented.
1.5 Purpose. The sole purpose of the processing is providing the functions in 1.1 to the Client under the main contract.
1.6 SNS's own purposes. Not covered by this agreement is processing SNS does as its own controller: setting up and unlocking logins, contract administration and communication with the Client, security and abuse protection of the service (including server logs and the bot check at sign-in once it is switched on), reading feedback sent through the feedback button, and anonymised aggregate usage statistics under the main contract. SNS's privacy policy applies to those.
2. Term
2.1 This agreement runs for the term of the main contract and ends with it, without notice.
2.2 The duties under section 3.8 (return and deletion) and confidentiality under section 3.2 continue after the end until all data is returned or deleted.
3. Obligations of the processor
3.1 Instructions (Art. 28(3)(a) GDPR). SNS processes personal data only on the Client's documented instructions, including on transfers to a third country. The instructions are set out in this agreement, in the main contract and in the use of Immvela's functions by the Client's users (for example uploading a document, starting a read, starting a staging, publishing a post). The Client gives further instructions in text form (email to office@sns-austria.com). If EU or Austrian law requires SNS to process further, SNS tells the Client before processing unless that law forbids it.
If SNS receives an authority's or court's request for the Client's data, SNS informs the Client without delay where lawful and refers the authority to the Client.
3.2 Confidentiality (b). SNS uses only persons for the processing who committed to confidentiality in writing before starting, or who are under a statutory duty of secrecy (notably § 6 DSG). The duty continues after their work ends.
3.3 Security of processing (c, Art. 32 GDPR). SNS takes the technical and organisational measures in Annex 1. SNS may update them to the state of the art provided the level of protection does not fall.
3.4 Sub-processors (d). See section 5.
3.5 Data-subject rights (e). SNS helps the Client, with suitable measures, to answer requests under Chapter III GDPR (access, rectification, erasure, restriction, portability, objection) in time. Specifically:
- access and portability: an export of the office's data as a machine-readable file (section 3.8);
- rectification: confirmed facts can be corrected in the product; everything else on request;
- erasure: users can delete photos, videos, scheduled posts, connected accounts and documents no confirmed value was read from; SNS deletes everything else on instruction within 30 days. A single person cannot be removed from inside a stored file (for example a PDF); only the whole file can be deleted. A document a confirmed value was read from is deleted only once that value has been replaced or removed.
If a data subject sends a request to SNS, SNS forwards it to the Client without delay and tells the person so; SNS does not answer it itself.
3.6 Assistance under Art. 32 to 36 GDPR (f) and breach notification. SNS helps the Client with the security of processing, notifications to the supervisory authority, notifying data subjects, a data-protection impact assessment and a prior consultation, taking into account the nature of the processing and the information available to SNS.
If SNS becomes aware of a personal-data breach affecting the Client's data (including at a sub-processor), SNS reports it to the Client without undue delay and at the latest within 48 hours of becoming aware, by email to the office's owners and admins. The report contains, as far as known: the nature of the breach, the categories and approximate number of people and records concerned, the likely consequences, the measures taken and proposed, and a contact person. Missing details follow as soon as they are available. Notifying the authority and the data subjects is the Client's task. SNS's immediate measures include pausing single functions and rolling back a faulty release (Annex 1, C).
3.7 Record of processing. SNS keeps a record under Art. 30(2) GDPR.
3.8 Return and deletion after the end (g). Within 14 days after the end the Client tells SNS in text form whether it wants (a) an export, (b) deletion or (c) both. Without an answer in that time, (b) applies.
- (a) Export. SNS hands over a machine-readable file (JSON) with the office's data (properties, listings, confirmed facts with their source, the document index, the media index, texts, the activity log and so on) and, on request, the stored files (documents, photos, media) in their original format. Access tokens of social accounts are never exported, for security. The export goes to the Client as an office, never to an individual user; it also contains every user's chat messages, which in the product only that user sees.
- (b) Deletion. Within 30 days SNS deletes the office with all its data in the database, all the office's files and the logins of every user who belongs to no other office, and confirms the deletion in text form.
- (c) Limits of deletion. Not reached: copies already sent to Anthropic or fal.ai (deleted under their retention rules, Annex 2); logs at Vercel, Trigger.dev and Sentry until they expire; posts published on social platforms (the user removes them there); sub-processors' backups until they rotate; files the Client downloaded.
- (d) SNS knows of no statutory duty of its own to keep the Client's data. Whether the Client must keep documents is the Client's decision; Immvela states no retention period.
If a user leaves the office during the term, SNS deletes the login on the Client's instruction. That user's listings, texts, media and log entries are assigned to a colleague the Client names and are not deleted; the user's social connections, scheduled posts, chat messages and own business card are deleted.
3.9 Evidence and audits (h). SNS gives the Client all information needed to demonstrate compliance with this agreement and allows audits by the Client or an auditor it appoints who is bound to confidentiality. Audits are done primarily by written information and documents (including the sub-processors' evidence, such as certificates or audit reports). An on-site audit at SNS's offices is possible with two weeks' notice during business hours. SNS runs no data centre of its own; there the respective sub-processor's evidence is used. Each party bears its own costs.
3.10 Unlawful instructions. SNS tells the Client without delay if it believes an instruction infringes the GDPR or other EU or Austrian data-protection law, and may suspend it until the Client confirms or changes it.
4. Place of processing
4.1 The database and stored files are at Supabase in the EU (Frankfurt am Main, region eu-central-1). The app's server functions run at Vercel in Frankfurt am Main (region fra1). Error reports go to Sentry's EU region.
4.2 The following processing takes place outside the EU, mainly in the USA:
- Anthropic: text generation for Quill, reading documents and, where it is switched on for the office, understanding the messages the user types in the property chat. When a document is read the complete file is sent. Processing is global; EU-only processing is not set up for this interface.
- fal.ai (USA), only as far as Vignette is unlocked for the Client: fal.ai receives a link to the original photo valid for one hour and fetches it from there; the link carries internal ids of the office and the user. No EU processing is set up.
- Trigger.dev (API Hero Ltd, United Kingdom): background jobs (for example publishing scheduled posts, fetching figures, making brochures as PDF). The region is still to be confirmed; according to the vendor the infrastructure is, among others, at Amazon Web Services in the USA.
4.3 Transfers to third countries go only to the recipients in Annex 2 and only on the basis stated there (an adequacy decision, for example for the EU-US Data Privacy Framework for certified recipients or for the United Kingdom, or EU standard contractual clauses under Implementing Decision (EU) 2021/914). By accepting this agreement the Client instructs these transfers.
5. Sub-processors
5.1 The Client authorises the sub-processors in Annex 2 (general written authorisation under Art. 28(2) GDPR). fal.ai counts as authorised only as far as Vignette is unlocked for the Client.
5.2 SNS informs the office's owners and admins in text form at least 14 days before adding or replacing a sub-processor. The Client may object within that time on an important data-protection ground. After an objection SNS may switch the affected function off for the Client, or either party may end the main contract with immediate effect.
5.3 SNS binds each sub-processor by contract to data-protection duties substantially equal to those of this agreement (Art. 28(4) GDPR). For vendors that offer only standard terms, this is done by accepting their data processing terms.
5.4 If a sub-processor fails its data-protection duties, SNS is liable to the Client for it under Art. 28(4), second sentence, GDPR.
5.5 Not sub-processors are the social platforms (Meta, LinkedIn, TikTok, Google/YouTube) that posts are published to on the user's instruction through the user's own account; they are recipients the user chooses.
6. Final provisions
6.1 Liability. Art. 82 GDPR applies to liability; otherwise the main contract's liability rules apply.
6.2 Conclusion and record. This agreement is concluded electronically (Art. 28(9) GDPR): an owner or admin of the office accepts it in Immvela by clicking and declares in doing so that they are authorised to conclude it for the office. SNS records the version, a checksum (SHA-256) of the accepted German text, the person who accepted, their role in the office and the time. The text of every version stays available at app.immvela.com/avv/ followed by the version number, and can be saved and printed.
6.3 New versions. SNS tells the office's owners and admins about a new version in Immvela and by email. It applies to the Client once an owner or admin accepts it; silence is not acceptance. The previous version stays in force until 30 days after that notice. Adding or replacing sub-processors follows section 5.2.
6.4 Law and courts. Austrian law applies. The courts of Vienna have jurisdiction.
6.5 Severability. If a provision is invalid, the rest stays valid; it is replaced by a provision that meets Art. 28 GDPR.
Annex 1: Technical and organisational measures (Art. 32 GDPR)
SNS runs no servers or data centres of its own; physical security sits with the sub-processors.
A. Confidentiality
| Measure | How it is done |
|---|---|
| MeasurePhysical access | How it is doneNo own data centres. Physical security at Supabase (database, files) and Vercel (app) as they state. |
| MeasureLogins: personal accounts | How it is doneEveryone has their own login (email and password, the password stored only as a hash at Supabase). Logins are not shared. A new login reaches no function until SNS unlocks it by hand or through an invite link. |
| MeasureLogins: bot check | How it is doneCloudflare Turnstile on the sign-in, sign-up and password pages is built and not yet switched on. |
| MeasureAccess: separating offices | How it is doneEvery table with office data carries an office id. The database limits a user to their office's rows with row-level security. The server functions also check the sign-in, the active office and the module's unlock themselves before they read or write. |
| MeasureAccess: inside the office | How it is doneRoles "owner/admin" and "agent". Some data only the person sees (for example chat messages), some the person and the office's admins (for example media, texts, social connections), some every member (properties, listings, documents). |
| MeasureAccess: files | How it is doneThe storage areas for media and documents are not public. Files are reached only through short-lived signed links the server issues after a permission check (for example 60 seconds for documents, one hour for the photo handed to fal.ai). |
| MeasureAccess: service key | How it is doneA database key with full rights is used by the server only for specific operations after its own permission check. SNS staff use it only through hand-run tools (unlocking, export, deletion) that show a preview by default and write only after an explicit confirmation. An automated check in development keeps keys out of the code. |
| MeasureEncrypting stored access tokens | How it is doneSocial tokens are stored encrypted with AES-256-GCM; without the key the app refuses to run rather than store them unencrypted. |
| MeasureEncryption at rest | How it is doneAccording to the vendor, Supabase encrypts the database and storage at rest. |
| MeasurePseudonymisation | How it is doneNot in general. Text generation sends Anthropic no office name, user id, email or phone number; it does send the property address and confirmed facts. |
| MeasureData minimisation when reading | How it is doneOwner names are not read out or stored as structured data. The file itself can contain names and is sent whole when it is read. |
B. Integrity
| Measure | How it is done |
|---|---|
| MeasureTransfer control | How it is doneConnections to the app, to Supabase and to the vendors use HTTPS (TLS). |
| MeasureInput control | How it is doneAn activity log records who generated a text, confirmed a value, uploaded a document, sent a request or published a post, and when. Confirmed facts store their source and who confirmed them. Values read from documents are proposals only and are used once a user confirms them. Confirmed facts are never overwritten; new entries replace them. |
C. Availability and resilience
| Measure | How it is done |
|---|---|
| MeasureBackups | How it is doneBy Supabase, as it states. A restore has not been rehearsed so far. |
| MeasurePausing single functions | How it is doneQuill, document reading and Vignette can be paused one by one or together; new runs are then refused before any vendor call. This takes effect after a new deployment and does not stop calls already running. |
| MeasureRolling back faulty releases | How it is doneA written procedure for rolling back at once to an earlier release at Vercel. It does not undo database changes. |
| MeasureCost protection | How it is donePer-user limits apply to AI calls and stagings; the database checks them atomically. |
| MeasureMonitoring | How it is doneError monitoring with Sentry in its EU region, without text from the properties; a status endpoint of the app. |
D. Regular review
| Measure | How it is done |
|---|---|
| MeasureReview before changes | How it is doneEvery code change runs automated checks (among others office separation, keys in code, completeness of export and deletion) and is reviewed before merge by a second instance that did not build it. |
| MeasureHandling security incidents | How it is donePausing and rolling back as in C; notification under section 3.6. |
| MeasurePrivacy-friendly defaults | How it is doneNo analytics, advertising or tracking cookies; nothing is unlocked without SNS acting. |
| MeasureSub-processor control | How it is doneSub-processors only under Annex 2. |
Annex 2: Sub-processors
| Sub-processor | Service | Location | Transfer basis |
|---|---|---|---|
| Sub-processorSupabase Pte. Ltd., Singapore | ServiceDatabase, sign-in, file storage; sending the sign-in and password emails. All data in 1.3, including documents and photos | LocationEU, Frankfurt am Main (eu-central-1) | Transfer basisSupabase's data processing terms as part of its terms of service, with EU standard contractual clauses |
| Sub-processorVercel Inc., Walnut, California, USA | ServiceRunning the app and all server functions; server logs. Every request and response, including documents on their way to Anthropic | LocationEU, Frankfurt am Main (fra1) | Transfer basisVercel's data processing terms with EU standard contractual clauses; Vercel is certified under the EU-US Data Privacy Framework |
| Sub-processorAnthropic Ireland, Limited, Dublin | ServiceAI text generation (Quill), reading documents (Dossier) and, where it is switched on for the office, understanding the property chat's messages. Quill: property address, confirmed facts, selling points, style statements, the user's earlier texts, the user's instructions for reworking a text. Dossier: the complete file. Chat: the message the user types in the property chat. Not: office name, user id, email, phone | LocationGlobal; no EU processing set up | Transfer basisAnthropic's data processing terms as part of its commercial terms, with EU standard contractual clauses |
| Sub-processorFeatures & Labels, Inc. (fal.ai), San Francisco, USA; only as far as Vignette is unlocked | ServiceVirtual staging (Vignette). A link to the original photo valid for one hour, the instruction text with the user's optional free text, the result image | LocationUSA | Transfer basisfal.ai's data processing terms with EU standard contractual clauses (Module 2) |
| Sub-processorAPI Hero Ltd (Trigger.dev), England and Wales, no. 14441978 | ServiceBackground jobs: publishing scheduled posts, renewing access tokens, fetching figures, making brochures as PDF. The jobs handle ids, media files and access tokens | LocationUnited Kingdom; region still to be confirmed | Transfer basisAdequacy decision for the United Kingdom; Trigger.dev's data processing terms |
| Sub-processorFunctional Software, Inc. (Sentry), San Francisco, USA | ServiceError monitoring. Error reports and technical details of the request, without text from the properties; personal data only as far as error reports contain it | LocationEU region | Transfer basisEU-US Data Privacy Framework; alternatively EU standard contractual clauses, under Sentry's data processing terms |
| Sub-processorEstateSync GmbH, Germany; only once portal publishing is switched on for the office | ServicePublishing to property portals. Listing data and photos; once enquiries flow back, also the enquirer's contact details and message | LocationGermany; some of EstateSync's own sub-processors are in the USA | Transfer basisEstateSync's data processing terms, concluded when SNS accepted its terms; for its providers in the USA, Art. 46 GDPR safeguards as EstateSync states |
| Sub-processorStadt Wien (open data, data.wien.gv.at), Austria; only once Lage is switched on for the office | ServiceLocation data from the City of Vienna's open data. A search pattern of the street name and the property's postal code, no house number | LocationAustria | Transfer basisNo transfer to a third country |
| Sub-processorCloudflare, Inc., USA; only once switched on | ServiceBot check (Turnstile) at sign-in, sign-up and forgotten password. The person's browser data on those pages, a check token | LocationAs Cloudflare states | Transfer basisNotified under section 5.2 before it is switched on |
Training AI models. Anthropic (text, document reading) is contractually barred from training its models on the data we send. fal.ai (staging) does not train on the photos we send, according to its terms, but may use anonymised or aggregated usage data to develop its own models.
Not sub-processors are the social platforms (section 5.5), Adobe (only two watermark model files are downloaded, no personal data) and GitHub (development; the feedback counter sends only a count and a time).
Annex 3: Retention and deletion
| Data | Kept for now | Who can delete |
|---|---|---|
| DataPhotos, videos, media | Kept for nowUntil the user deletes them or the end | Who can deleteThe user, in the product |
| DataStaged images not kept | Kept for nowUntil discarded or kept | Who can deleteThe user (discard) |
| DataDocuments | Kept for nowExempt from the media cleanup; until deleted | Who can deleteThe user, unless a confirmed value was read from the document; then SNS on instruction |
| DataFiles uploaded by owners | Kept for nowRefused, discarded and unfinished uploads are cleaned up automatically; a received upload stays until the user decides | Who can deleteThe user (accept or discard) |
| DataProperties, listings, confirmed facts, texts, chat | Kept for nowUntil the end | Who can deleteSNS on instruction |
| DataActivity log (including feedback messages) | Kept for nowUntil the user or the office is deleted | Who can deleteSNS on instruction |
| DataSocial connections, scheduled posts | Kept for nowUntil disconnected or deleted | Who can deleteThe user, in the product |
| DataAcceptances of this agreement | Kept for nowUntil the office is deleted; if a person who accepted is deleted, the entry stays without their name | Who can deleteCannot be changed |
| DataCopies at Anthropic, fal.ai, in logs at Vercel, Trigger.dev and Sentry, on social platforms | Kept for nowUnder each vendor's or platform's rules | Who can deleteOut of SNS's reach |