Who we are
BVT Global Services (“BEVIEL”, “we”, “us”), registered at Santiago Surco, Lima 15054, Peru, is the controller of the personal data described here. Our data protection contact is legal@beviel.com.
Where you use BEVIEL to process personal data belonging to your own customers or staff, you are the controller of that data and we act as your processor, on your instructions.
What this covers
This policy covers BEVIEL Cloud, the BEVIEL desktop application, the BEVIEL Gateway and this website. It sits alongside the Terms of Service, which govern the service itself.
It does not cover a Model Provider you connect with your own credentials, or the third-party services you link to a workspace. Those are governed by their own policies — see Where your code goes.
What we collect
| Category | What it is | Where it comes from |
|---|---|---|
| Account | Name, email address, password hash, and the plan you selected with the entry point you selected it from | You, at sign-up |
| Federated identity | If you sign in with GitHub or Google: your provider id, email and display name. We never receive your password for those accounts | GitHub or Google, if you choose them |
| Workspace content | Your source code, prompts, project files, configuration and generated output — including any personal data you put in them | You, as you work |
| Provider credentials | API keys for the model providers you connect, held encrypted and used only to make the calls you ask for | You, when you connect a provider |
| Usage and cost | Which model ran, token counts, duration, success or failure, and the cost attributed to a run | Generated as you use the service |
| Technical | IP address, browser and OS, timestamps, and error diagnostics when something fails | Automatically, from your requests |
| Support | What you send us when you report a problem or ask a question | You |
| Payment | None. No plan can currently be purchased, no payment method is taken, and no card data reaches us | — |
We do not buy personal data, and we do not build advertising profiles.
Where your code goes
This is the question worth answering precisely, because the answer depends on which model you chose — not on us.
| Path | Who receives your prompt and code | Under whose terms |
|---|---|---|
| Your own API key | The provider you connected | Your agreement with them. We are not a party to it and cannot change what they do with it — read their policy |
| BEVIEL-managed inference | A provider we hold the relationship with, reached through the BEVIEL Gateway | This policy. They are our sub-processors — see §6 |
| Local model | Nobody. It stays on hardware you control | — |
We do not use your code, prompts or output to train AI models, and we do not permit our managed-inference sub-processors to train on them either.
A provider you connect with your own key is outside that commitment — whether they train on your input is set by the plan and account you hold with them, and some consumer tiers do.
Only what a request needs is sent. The service assembles context from your workspace — the files and symbols relevant to what you asked for — rather than transmitting an entire repository, and it records which model handled each request so you can see after the fact where your work went.
Why we use it
| Purpose | Data used | Legal basis (UK/EU GDPR) |
|---|---|---|
| Providing the service | Account, workspace content, provider credentials | Performance of a contract |
| Authentication and account security | Account, federated identity, technical | Contract; legitimate interests in keeping accounts secure |
| Showing you what you used and what it cost | Usage and cost | Contract |
| Diagnosing failures and improving reliability | Technical, usage, error diagnostics | Legitimate interests in a service that works |
| Preventing abuse and enforcing the terms | Technical, usage, account | Legitimate interests in protecting the service and its users |
| Support | Support messages, and workspace content only if you send it | Contract |
| Product announcements you asked for | Account email | Consent — withdrawable at any time |
| Legal and accounting obligations | Account, transaction records | Legal obligation |
We do not make decisions about you by automated means that produce legal or similarly significant effects. Generating code is not a decision about you.
Who else processes it
We use third parties to run the service. Each one is bound by a written contract, may process your data only on our instructions, and is listed here before it starts.
| Purpose | Sub-processor | Location |
|---|---|---|
| Hosting and databases | None engaged | — |
| Network, DNS and DDoS protection | None engaged | — |
| Transactional email | None engaged | — |
| BEVIEL-managed inference | None engaged | — |
| Error monitoring | None engaged | — |
Every row says the same thing, and it is an answer rather than a gap: nobody processes your personal data on our behalf today. The hosted service is not deployed, so there is no database in anyone else’s building and no mail relay sending on our behalf. BEVIEL operates no managed inference: a model runs on your own machine, or at a provider you chose and pay directly. And no error-reporting or crash-reporting service is built into the website or the applications — that one is a fact about the code rather than a policy, and you are welcome to check it.
The only third party that receives anything at all is the public CDN that serves this page’s JavaScript. It sees your IP address because your browser fetches a file from it directly; it processes nothing for us, so it is not a sub-processor. It is named, with what it does and does not see, in §12.
The columns are the commitment. The first time we engage anyone — a host, a mail relay, an inference provider we pay for you — they appear here with a purpose and a location before they start, and we publish the change on this page and by email to account holders at least 30 days before it takes effect.
A provider you connect with your own credentials is not our sub-processor. They are yours.
How long we keep it
| Data | Kept |
|---|---|
| Account details | While your account exists |
| Workspace content | While your account exists, then deleted within 30 days of deletion |
| Backups | Deleted content persists in backups for up to 35 days, then expires |
| Provider credentials | Until you remove them, or your account is deleted |
| Usage and cost records | 7 years, because tax and accounting law requires it |
| Technical logs | 90 days |
| Support correspondence | 3 years from the last message in the thread |
| Records we must keep by law | For the period the law requires |
Each period above is a promise about deletion behaviour, not an estimate: if we say deleted content is gone in 30 days, the system has to make that true. Where an enforcing mechanism is still being built we will hold to the shorter of the stated period and what the law requires, and we will correct this table rather than quietly outlive it. Export your work before deleting an account.
International transfers
We are established in Peru, so if you live anywhere else your data is processed outside your own country as soon as it reaches us. There is no onward destination beyond that today: §6 is empty, so nothing is passed to a third country by a sub-processor.
Peru is not covered by a UK or EU adequacy decision. Where we receive personal data from the United Kingdom or the EEA we therefore rely on the European Commission’s Standard Contractual Clauses — with the UK International Data Transfer Addendum where the UK GDPR applies — alongside the safeguards in §10. Ask us at legal@beviel.com for a copy.
When a host or any other sub-processor is engaged, it appears in §6 with its location before it starts, and this section names the new destination and the transfer mechanism at the same time.
How we protect it
- Encryption in transit (TLS) and at rest.
- Provider API keys are stored encrypted and are never displayed back to you in full after they are saved.
- Passwords are stored as salted hashes. We cannot read your password and will never ask you for it.
- Workspaces are isolated, and file operations are confined to the project boundary you are working in.
- Access to production data is limited to staff who need it, and is logged.
No system is perfectly secure. If a breach affects your personal data we will notify the relevant supervisory authority within 72 hours where required, and tell you without undue delay where the risk to you is high.
Report a vulnerability to security@beviel.com.
Your rights
Subject to local law, you can ask us to give you a copy of your data, to correct it, to delete it, to restrict or stop a particular use, or to provide it in a portable format. You can object to processing we base on legitimate interests, and withdraw consent at any time without affecting what was done before.
Most of these you can exercise yourself in the product: your account page shows what we hold, workspaces can be exported, and account deletion is self-serve. For anything else, contact legal@beviel.com. We answer within one month and do not charge.
If your data is in a workspace owned by an organisation, ask them first — they control it, and we will refer your request to them.
Children
BEVIEL is a professional development tool and is not directed at children under 16. We do not knowingly collect their data; if we learn we have, we delete it. Contact legal@beviel.com if you believe a child has created an account.
Changes to this policy
We will update this policy as the service changes. The version and date at the top change with it, and for material changes we will notify account holders at least 30 days’ notice before they take effect rather than relying on you to re-read the page.
Contact and complaints
Privacy questions and rights requests: legal@beviel.com. Postal: BVT Global Services, Santiago Surco, Lima 15054, Peru.
If you are unhappy with our answer you can complain to your data protection authority — in the UK, the Information Commissioner’s Office; in the EEA, the authority where you live or work. We would rather you raised it with us first, but you do not have to.
Version 1.0 — effective 26 August 2026. This is the version of this policy currently in force. If we change it, the version number and both dates above change with it, and account holders get at least 30 days’ notice of a material change before it takes effect.