Privacy policy
Who we are
awow.io is operated by Vergence B.V., Fornheselaan 254, 3734 GE Den Dolder, the Netherlands. Chamber of Commerce (KVK) 96476133. VAT (BTW) NL867627670B01. The controller for the processing described here is Vergence B.V., reachable at privacy@awow.io. We are not required to appoint a Data Protection Officer and have not appointed one, so privacy questions go to that same address.
What this website collects
This website is informational. It sets no cookies, runs no analytics, carries no advertising and loads no tracking pixels. Fonts, stylesheets and images are all served from this domain, so reading these pages sends your browser to no third party. We process three things.
| data | purpose | legal basis | retention |
|---|---|---|---|
| Request logs written by our hosting provider: IP address, user agent, requested path | Operating and securing the site | Our legitimate interest in a working, secure website, Art. 6(1)(f) | Written and held by Microsoft as part of the hosting service, under its own terms. We do not switch on site analytics, we take no copy of these logs, and we do not use them to identify visitors. |
| The email address you submit to the waiting list | Contacting you when access becomes available | Steps taken at your own request before any agreement, Art. 6(1)(b) | Until we contact you and you decline, until you ask to be removed, or 24 months after you join, whichever comes first |
| The content of email you send to any awow.io address | Answering you | Our legitimate interest in replying to correspondence, Art. 6(1)(f) | 24 months after the last message, unless it forms part of a contract record |
The waiting list form transmits nothing by itself. It opens a pre-addressed message in your own mail client, and we receive your address only if you choose to send that message.
We take no automated decisions about you and we do no profiling.
Who processes this data for us
| provider | what they do |
|---|---|
| Microsoft Azure (Static Web Apps) | Hosts this website and writes its request logs |
| Microsoft 365 (Exchange Online) | Receives and stores email sent to awow.io addresses, including waiting list requests |
| Cloudflare | Authoritative DNS for awow.io. It answers name lookups and does not carry or see the content of your visit. |
We do not sell personal data, we do not share it for advertising, and we use no other third-party service on this website.
Your rights
Under the GDPR you may request access to, correction of, or deletion of personal data we hold about you. You may also object to processing, request restriction, and request portability. Where we act on a request you made, you can withdraw that request at any time. Write to privacy@awow.io. We answer within one month, and we will tell you if a complex request needs the further two months the GDPR allows. You may lodge a complaint with the Dutch Data Protection Authority, the Autoriteit Persoonsgegevens.
The AWOW product
The AWOW product is separate from this website, and processing there is governed by the data processing agreement we conclude with each customer rather than by this page. Because where the processing happens is the first thing people ask, this is how it stands in the current version of the product.
- Your systems of record stay yours. The knowledge base is a git repository in your own Azure DevOps. Raw transcripts, run outputs and exports are written to a storage account you register and own. Traces and token costs land in your own MLflow. Inference runs on your own Databricks serving endpoint, so prompt content goes to your model and model spend lands on your bill.
- Orchestration runs on our infrastructure. Scheduling, the tenant registry, entitlement and audit metadata sit in a control plane we operate. In this version the job runner that reads your systems and writes back to them also runs on our Azure infrastructure, so content passes through it while a job is running.
- One working copy sits on our side. The agent that answers questions keeps a read-only clone of your knowledge base repository on our infrastructure. Your Azure DevOps repository stays the system of record, and the clone is disposable and rebuilt from it.
- That placement is configuration, not architecture. The runner and the agent are built to move into your own tenant without a code change, and moving them is on the roadmap.
Access is granted through your own Microsoft Entra ID with administrator consent, which you can revoke at any time. Credentials are held as references to your own Key Vault, never as copied values.
Hosting and international transfers
This site runs on Microsoft Azure Static Web Apps, deployed in the West Europe region. Static content is served from Microsoft's global edge network, so a copy of the page may be delivered from a location closer to you. Where Microsoft transfers data outside the EEA, it does so under its own standard contractual clauses.
Changes
We update this page when our practices change and revise the date above.