Privacy notice
Who is responsible for your data
This site is operated by Brandeck Decks LLC (demo), trading as Brandeck. Brandeck Decks LLC (demo) decides what is collected here and why, and is the controller of your personal data. BranderUX runs the technology behind the site and processes that data on Brandeck Decks LLC (demo)'s behalf.
You are talking to an automated AI
The assistant on this site is an automated AI system operated for Brandeck, not a person. What you type is sent to the AI providers listed below so an answer can be written, and that answer can be wrong; check anything that matters with Brandeck.
Giving your details is voluntary
Nothing here obliges you to give personal details, and you can browse and ask questions without signing in. If you decline a detail the assistant asks for, the only consequence is that it cannot finish that particular booking, order or request, cannot send you a sign-in code, and cannot tailor its answers to you.
What is collected
- Conversations. Your questions, the assistant's answers and the screens it showed you are stored. Whether or not you sign in, the turns of a single visit are grouped under a random session key, and a stored classification of that session (what it was about and how it went) is kept against the same key.
- What you submit. A booking, order, enquiry or form submission is stored as a record belonging to Brandeck: the details you typed, the fact that you submitted them, a one-line summary of your request written by the assistant, where your visit came from (the page you landed on, the site that sent you and any campaign tags or ad click ids in the link you followed) and which conversation it came from. Brandeck reads those records, can add its own status and notes to them, can be emailed when one arrives and can have them sent on to its own systems; BranderUX stores and delivers them on Brandeck's behalf.
- Your account, if you sign in. Your email address, a name if you give one, the times you signed in, and any small service preference you ask the assistant to remember.
- Sign-in codes. A code you request is stored while it is valid. It is marked used when you use it and removed later by a nightly purge of used and expired codes. It is not destroyed the instant you use it.
- Technical request data. The network request behind every page and call (IP address, browser user agent, the address requested and timing) reaches our hosting provider and its server logs.
What it is used for
Running this site's assistant, and nothing else: answering you, signing you in, recording and passing on what you book, order or ask for, preventing abuse, and letting Brandeck see how its assistant is doing. Your data is not sold and is not used to advertise to you.
What Brandeck can see
In its analytics console Brandeck can read the full transcript of any conversation on this site. While you are signed in, your name and email address are attached to those transcripts. An automated AI analyst also reads them, in order to answer Brandeck's questions about them, including automated quality reviews across BranderUX customers, triggered by BranderUX staff. That analyst can also read the records you submit. Brandeck can also connect an AI assistant of its own to BranderUX and let it read these transcripts and the records you submit.
Who else receives your data
BranderUX uses the service providers below to run this site. Each row names the provider, the country its systems are in, and what reaches it.
Your data therefore leaves Israel: it is stored and processed abroad, in the countries named below.
Anthropic PBC (Claude models)
United States
What reaches them: the question a visitor types and the assistant's answer; the business data the assistant looked up to answer (catalogue rows, bookings, requests); the business's brand settings, house rules and skills; a signed-in visitor's name, email and remembered preferences when personalization is on; answers routed here through the AI gateway are sent without the gateway's zero-data-retention flag and fall under Anthropic's standard retention: Anthropic states that it deletes its API's inputs and outputs within 30 days, except where its usage policy or the law requires keeping them longer; the direct paths named here fall under the same retention; query enhancement and screen selection for embedded surfaces; the insights analyst, which reads stored visitor transcripts, the records the agent collected and the names and email addresses of signed-in visitors to answer the owner; the session classifier, which reads each stored conversation to label its topic and outcome; admin-triggered quality reviews (AgentEvalService), which read stored transcripts across BranderUX customers to score answers, cross-tenant by design; the serve fallback, when the AI gateway fails before a visitor's answer starts.
When: Answer-quality stops 1, 2, 4 and 5 run on this provider by default; a business whose stop is on another provider does not reach it.
https://www.anthropic.com/legal/privacyOpenAI (GPT models)
United States
What reaches them: the question a visitor types and the assistant's answer; the business data the assistant looked up to answer (catalogue rows, bookings, requests); the business's brand settings, house rules and skills; a signed-in visitor's name, email and remembered preferences when personalization is on; answers routed here through the AI gateway are sent with the gateway's zero-data-retention flag, so the provider is told to keep nothing after answering; a model that does not support the flag is retried once without it, and that turn falls under the provider's standard retention, as does any direct path named here.
When: No answer-quality stop is mapped to this provider by default; it receives data only if an administrator maps a stop to one of its models, or an owner adds their own key for it.
https://openai.com/policies/privacy-policyGoogle LLC (Gemini models)
United States
What reaches them: the question a visitor types and the assistant's answer; the business data the assistant looked up to answer (catalogue rows, bookings, requests); the business's brand settings, house rules and skills; a signed-in visitor's name, email and remembered preferences when personalization is on; answers routed here through the AI gateway are sent with the gateway's zero-data-retention flag, so the provider is told to keep nothing after answering; a model that does not support the flag is retried once without it, and that turn falls under the provider's standard retention, as does any direct path named here.
When: Answer-quality stop 3 runs on this provider by default; a business whose stop is on another provider does not reach it.
https://policies.google.com/privacyVercel Inc. (AI Gateway)
United States
What reaches them: every hosted assistant turn on its way to the model provider: the visitor's question, the business data in the answer, the brand and house rules; each turn on a model other than Claude carries the gateway's zero-data-retention flag, which asks it to route only to a provider that keeps nothing after answering; when no provider serves that model under the flag the turn is retried once without it, and that provider's standard retention applies to it; a turn on a Claude model is sent without the flag, so the standard retention of the provider that answers it applies.
https://vercel.com/legal/privacy-policyVercel Inc. (hosting and delivery)
United States
What reaches them: the network request behind every page and API call: IP address, user agent, URL and timing; server logs of those requests.
https://vercel.com/legal/privacy-policyGoogle LLC (Google Cloud: Cloud Run, Cloud SQL, Memorystore, Cloud Storage, Cloud Logging)
United States (us-central1)
What reaches them: a business's records: catalogue items, bookings, orders and customer requests; visitor accounts on published sites, their conversations with the assistant and their remembered preferences; application logs; for a design-partner key issued before per-project keys existed: a record of each call it makes (endpoint, response time, and the caller's IP address and browser identifier) in Firebase Firestore.
https://cloud.google.com/terms/cloud-privacy-noticeGoogle LLC (Sign in with Google, and the sheet picker for the Google Sheets CRM)
United States
What reaches them: when a visitor on a published business site chooses Continue with Google: the fact that they are signing in to that site, and the name, email address and Google account id we keep from what Google returns.
When: Only when a BranderUX account holder chooses Sign in with Google or reaches the step that chooses an existing spreadsheet for the Google Sheets CRM in Google's file picker, or a visitor on a published business site chooses Continue with Google.
https://policies.google.com/privacyComposio (Sampark, Inc.; connector hub)
United States
What reaches them: the business's authorization for its own connected apps (calendar, mail, CRM), held under the project id; the arguments and results of any connected-app action the assistant runs, which can carry a visitor's name, email or booking details.
When: Only when the deployment has a connector hub configured AND the business connected an app through it.
https://composio.dev/privacy-policyUpstash Inc. (Redis, abuse prevention)
United States
What reaches them: a request counter under a one-way, peppered digest of the caller's IP address (the address itself is never sent, and no request content is).
When: Only when the deployment configures a Redis URL and token; otherwise rate limiting stays in the server's own memory.
https://upstash.com/trust/privacy.pdfjsDelivr, operated by Volentio JSD Limited (script CDN for the element runtime)
United Kingdom (the operator); the CDN answers from the edge nearest the visitor
What reaches them: the IP address, browser identifier and page address of a visitor whose browser fetches a script from the CDN; no account, conversation or record data.
When: Only when a page renders a custom element; the sandbox frame loads its runtime libraries from the CDN.
https://www.jsdelivr.com/terms/privacy-policy-jsdelivr-netResend, Inc. (transactional email)
United States
What reaches them: a visitor's email address and one-time sign-in code, when they sign in to a published site; in an escalation email to the business: the visitor's name, contact details and request as typed; in an access request to the business, when its site requires approval: the visitor's name and email address; in a new-record alert to the business: what the visitor submitted (name, contact details, request), the assistant's one-line summary, where the visit came from (the channel, the campaign and the referring site) and, for a returning customer, the name and status the business's CRM shows for them; in the daily summary and in a notice about the business's CRM: the visitor's name or a contact detail.
When: Only when a published site sends a sign-in code or asks the business to approve a visitor, the assistant hands a visitor's request to the business by email, or the business gets an email about its records: a new-record alert, the daily summary or a notice about its CRM.
https://resend.com/legal/privacy-policyEndpoints the business configures itself (its own API, store, webhook or CRM)
unknown (the business chooses the destination)
What reaches them: what a visitor submits when the business wired a form or action to its own endpoint: typically a name, contact detail and the order, booking or request itself; read-only lookups against the business's own catalogue send no visitor data; when the business set a webhook: every new or updated record, with what the visitor submitted, the assistant's summary, where the visit came from, its status and follow-up date and, for an update, what changed (the text of a note the business added included); when the business connected its CRM: every collected record, the assistant's summary, where the visit came from and, when turned on, the conversation; later, the notes the business adds, corrections to the person's details, status changes and a visitor's opt-out from marketing.
When: Only for a business that configured a live data source, a custom write endpoint, a webhook or a CRM. The business chooses the destination and its own privacy notice governs it.
How long it is kept
- Conversations, the record of your activity on this site and the stored classifications of your sessions are deleted permanently 180 days after they are created, and sooner than that on a busy site, where only the most recent 2000 exchanges a business has had are kept at all.
- An action left waiting for your confirmation is kept for 90 days.
- A sign-in code is removed once it has been used or has expired, by the nightly purge.
- A booking, order, enquiry or form submission belongs to Brandeck and is kept for as long as Brandeck keeps its own business records.
- Your account is kept until you delete it.
Your rights
Israeli law gives you the right to inspect the personal data held about you (section 13 of the Protection of Privacy Law) and to ask for data that is incorrect, incomplete, unclear or out of date to be corrected or deleted (section 14).
While you are signed in, the account menu on this site does three of these immediately. “Export my data” downloads your profile, your recorded activity, your conversation transcripts, the records you submitted here, actions waiting on you and the stored classifications of your sessions; a very long history is capped, and the file states the cap it applied. “Edit my name” corrects the name held about you. “Delete my data” deletes your account and its recorded activity, your conversation turns, the stored classifications of those sessions, actions waiting on you, the records here that are your own, and every sign-in code ever sent to your address.
There is one thing deletion does not reach: a booking, order, enquiry or form submission you already sent to Brandeck is Brandeck's own business record and stays. Your account is detached from it, so it no longer identifies you.
Israeli law does not grant a general right to erasure, and this notice does not promise one. What the account menu deletes is exactly what is listed above.
Signed in or not, you can write to Brandeck at lev@branderux.com. A request that arrives that way is handled by Brandeck, not by BranderUX. An anonymous conversation carries no name or email address, so we cannot match it to the person who wrote it.
Contact
Brandeck is the controller of your personal data and answers questions about it at lev@branderux.com.
The technology behind this site is provided by BranderUX (branderux.com), which holds and processes that data for Brandeck (a "holder" under Israeli law).