Operator and scope
Vibaci, trading as KORRHAUS operates the KORRHAUS planning tools and in-chat sock Designer at https://agents.korrhaus.nl/mcp. KORRHAUS is a registered trade name of Vibaci.
This notice covers the public connector and temporary in-chat design session. Account registration, saved customer projects, prices and purchases on the KORRHAUS website are covered by the website's privacy information.
Your design and artwork
The Designer processes colours, construction choices, quantities, size splits and optional branding text. Selected logo files are processed in the interface to prepare the visual preview. A bounded summary of the current configuration is shared with the AI conversation so that supported edits can be proposed. Original artwork files, transfer credentials and customer sign-in credentials are not included in that intended summary.
When you ask for starter designs, the studio name, brand colours and style preferences you give are used to draw three temporary designs. The service returns them to the conversation and the interface and does not store them.
The four planning tools continue to calculate public guidance and brief links. They do not create a customer account or order. Do not include credentials, payment details, health information or unrelated confidential information in prompts or design fields.
Temporary chat editing
To deliver an edit to the correct open Designer, the service stores a random session identifier, hashes of scoped access credentials, revision and expiry information, and a bounded proposed edit with its delivery status. This can include branding text you ask the assistant to change. These editing records contain no original artwork, complete customer project or customer profile. Google Cloud Firestore hosts these records.
Session access expires after 30 minutes; a proposal expires after at most five minutes, within that session. An applied, rejected or superseded proposal has its patch text cleared. Explicit interface teardown also clears patch text and revokes the session. Closing a browser cannot guarantee delivery of teardown.
Access expiry is not a promise of immediate physical deletion. The temporary session database uses an expiry-based cleanup policy. Cleanup is asynchronous: expired records may remain in storage while deletion is pending; the application rejects expired access independently. Provider cleanup typically occurs within 24 hours after expiry, but that is not a guaranteed deletion deadline. Disconnecting the plugin or clearing your browser does not by itself delete server records. Use the support contact below for a data request.
Continuing on the KORRHAUS website
When you explicitly choose the enabled website-transfer action, the service sends the current configuration and original and prepared artwork to KORRHAUS's transfer service. The transfer envelope is encrypted in storage. Random transfer identifiers, digests, expiry and import state support access checks and safe retries. A secret link allows the website to load that transfer for your review; it is kept in the interface rather than the intended model-visible response. Treat that link as private.
Transfer access expires two hours after creation; retrying does not extend its original expiry. Expiry prevents new access and is not immediate erasure. An independent cleanup job is scheduled every 15 minutes in bounded batches to clear expired encrypted transfer payloads. Replay, claim and artwork-retry metadata are scheduled for deletion seven days after transfer expiry. Scheduling is not a guaranteed physical deletion deadline: interruptions, backlog and provider backups can delay removal. The job does not delete artwork attached to a saved customer project; that follows the website project policy. The transfer database backup policy retains seven backup copies, a count-based rule rather than a seven-day erasure deadline; point-in-time recovery logs are retained for seven days. Expired data may therefore remain in older backups until those copies rotate out. Restored data must still pass access-expiry checks. Importing a design is not an order. You review it on the website and sign in there for account saving and business eligibility checks.
The website can retain a local draft for recovery. Browser drafts remain until replaced or removed by the Designer, you clear site data, or the browser removes them. Saved account projects follow the website's own data policy.
Hosting and service logs
Google Cloud hosts the public service and transfer backend. Standard security and reliability logs may include IP address, timestamp, request path, response status and error class. The existing service logging configuration retains ordinary request and application logs for 30 days and required infrastructure audit logs for 400 days. These are log retention periods, not deletion periods for design records. The connector application does not log original artwork, raw session credentials or complete transfer envelopes. Your AI provider processes the conversation under its own terms.
To learn whether starter designs help studios, the service records anonymous usage events, such as cards shown, a design chosen, a logo added or the website opened. An event holds its type, the design style, the kind of AI app, the language, a random identifier for that set of cards and simple counts, such as how many brand colours were given. It holds no studio name, colours, artwork, design text or conversation text. Usage events are application logs and follow the same 30-day retention.
Your controls and requests
You can design without a business account, decline a proposed edit, stop using the Designer, or choose not to transfer a design. Keep your original artwork. Contact KORRHAUS support to request access, correction or deletion of service-related information, subject to identity verification and applicable security and legal retention requirements.