Privacy policy

Who we are, and what this policy covers

Seeve builds automated operating paths for businesses in Saudi Arabia. This policy covers the see-ve.com website and its pages, and our internal space at hub.see-ve.com and its forms — that is, what you share with us as a visitor, as someone interested in our services, or as a client filling in a set-up sheet.

Data belonging to your own customers, flowing through a system we build for you, is governed by the service agreement signed between us — not by this page. There, the data stays in your business's accounts and we act on your instructions.

What we collect

• What you send us yourself: your name and mobile number through the site's form, plus your type of business and a note if you choose to write them — both optional.
• Limited technical context with the request: the country code the request came from, and the page you came from. They help us understand the enquiry before replying.
• Your IP address — momentarily only: used to stop abuse of the form (a limit on attempts). It is not stored with your enquiry and never reaches our team.
• What you type into the digital-employee demo: your messages in the chat box, and the line of business you picked or typed. It travels a different path from the form, described in its own section below.
• Anonymous visit statistics: visit counts and which pages are read most, through Cloudflare's analytics — with no cookies and nothing that identifies you personally.

And if you message us on WhatsApp, what you send there is also subject to WhatsApp's own policy; we see it as it reaches us.

Why we collect it — and why not

For one reason: to contact you about your enquiry and arrange the diagnostic session if you want one. And what you type into the employee demo is used for one thing: generating the next reply to you. That is all.

• We do not sell your data, and we do not rent it to anyone.
• We do not use it for marketing campaigns, and we do not add you to a mailing list.
• We do not share it with ad networks, and there is no advertising tracking anywhere on this site.

Where your data actually goes

When you submit the form, the request travels this path:

• Your browser → a server on our own domain (hosted with Cloudflare), over a connection that is encrypted by force.
• Then → our automation platform on our own server inside the Riyadh region, where the request is checked against automated spam.
• Then → an internal notification to our team over Telegram so we see your enquiry quickly and reply. Telegram is an external service with servers outside the Kingdom, so the notification carries only your name, business and note, never your mobile number.
• Alongside → a row in a Google Sheets file owned by Seeve's own account, holding the name, mobile number, business, note and time of the enquiry, so no enquiry gets lost among messages. Google's servers are outside the Kingdom too.

Beyond those two, your enquiry reaches no third party.

The digital-employee demo: a different path

The “try your digital employee” box on the home page does not follow the path above. What you type there travels this route:

• Your browser → a server on our own domain (with Cloudflare), over a connection that is encrypted by force.
• Then → the AI model provider which generates the employee's reply — currently DeepSeek. With every message it receives the whole conversation up to that point. It is a third party outside the Kingdom (its servers are in China), and what reaches it is governed by its own policy, not by this page.
• Meanwhile → temporary storage on our server so the employee remembers what you said two messages ago. The conversation is kept for one hour from your last message, then deleted automatically, and nobody on our team reads it.

That is why the notice under the box says: do not enter personal or confidential details. The employee itself explicitly asks for a sample name and a made-up number. And if you type a mobile number or an email anyway, our server masks it before storage — but it will already have reached the model provider in that message.

• IP address: a session counter is kept against it for one day (a limit of five sessions per visitor per day), then deleted automatically. It is never linked to the conversation text.
• A technical log with no text: for each reply we record the turn number, the line of business, whether the reply was blocked, and the tokens consumed — so we know the demo works and what it costs. The log contains neither your messages nor the employee's replies.

The demo knows nothing about your business and is connected to no system, and we do not use your conversation to train any model.

The set-up sheet on hub.see-ve.com

If we send you a link to a set-up sheet — such as “WhatsApp bot operating decisions” — what you write in it travels this route:

• First, it is saved in your own browser the sheet saves your answers on your device as you go so nothing is lost if the page closes, before anything reaches us. Nothing is sent to us until you press “send your answers”.
• Then → storage on our domain with Cloudflare the sheet is stored exactly as you sent it, over a connection encrypted by force, in storage owned by Seeve's own account. Cloudflare's data centres for this storage are outside the Kingdom.
• Then → our automation platform on our own server inside the Riyadh region, to alert our team over Telegram that your sheet has arrived (the alert carries your organisation's name, your name and how many questions you answered, without your mobile number) and to index it in a Google Sheets file owned by Seeve's own account so we can find it again. Telegram and Google are both outside the Kingdom.
• Then → an internal summary by an AI model We send the sheet's text — only your role and your answers, without your organisation's name, your name or your mobile number — to the model provider Z.ai, a third party outside the Kingdom. It returns a summary of contradictions and gaps in the answers so we can prepare for our call with you. The summary is for our team only, and we do not use your sheet to train any model.

The sheet holds your organisation's name, your name and role, your mobile number and your answers, and it reaches no third party beyond those named above.

• IP address: used momentarily for rate limiting only; it is not stored inside your sheet and never reaches our team.
• Your copy's link: after sending, we give you a read-only link to a copy of your answers. Anyone holding the link can open it, so keep it as you would any business document.

Your own customers' data never passes through this sheet — the sheet holds operating decisions, not data.

Google user data

Seeve's internal tooling connects to Seeve's own Google account (Sheets, Drive, Gmail) to run our operations. This access is limited to our own account; we do not request or access our clients' Google accounts. Our use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.سياسة بيانات مستخدمي خدمات واجهات قوقل، بما فيها متطلبات الاستخدام المحدود.

How long we keep it

Twelve months from our last contact, then it is deleted. And if you ask for deletion before that, we delete it without asking why.

Conversations in the employee demo: one hour from the last message; the session counter: one day — both deleted automatically, no request needed.

Set-up sheets follow the same period: twelve months from our last contact. When deleted, they are removed from our live systems within thirty days of your request, and from our encrypted backups within ninety days as those rotate.

Cookies: there are none

This site places no cookies on your device — none for tracking, none for advertising, not even for preferences. That is why you see no cookie consent banner here: there is nothing to consent to. In rare cases our security provider (Cloudflare) may set a temporary technical cookie to verify that a visitor is a real browser and not an automated program.

Your rights — and how to exercise them

Under the Kingdom's Personal Data Protection Law, you may ask to:

• see what data of yours we hold, and receive a copy of it.
• correct anything inaccurate.
• delete your data, and withdraw your consent at any time.
• object to our processing of it, or restrict it.

How we protect what we hold

• The whole site runs over enforced encryption, and any unencrypted visit is redirected automatically.
• The form is protected by a secret key shared between our own servers, so a stranger cannot inject requests into our path.
• A per-visitor limit and an overall limit on attempts, which stop automated flooding.
• Access to enquiries is limited to whoever needs it in order to reply to you.

No system is without risk — but what we promise here is what is actually in place, not what we wish for.

Children, changes, and contact

Our services are aimed at businesses. They are not directed at anyone under eighteen, and we do not knowingly collect their data.

If we amend this policy, the “last updated” date at the top of the page changes, and the current text is the one in force.