Skip to content
We3vision

Legal

Privacy Policy for United Kingdom clients

We3vision Private Limited · Version 1.0 · Last updated 17 November 2026

After Brexit the United Kingdom has its own version of the GDPR. This page tells UK clients and visitors what we do under it. It follows the same ideas as the European Union page, but the papers, the authority and the transfer tools are British.

19 sections

Laws this page follows

  • UK General Data Protection Regulation (UK GDPR)
  • Data Protection Act 2018, as changed by the Data (Use and Access) Act 2025
  • Privacy and Electronic Communications Regulations 2003 (PECR): cookies and marketing messages

01Who we are and what this page covers

We3vision Private Limited ("We3vision", "we", "us") is a web, app, AI, metaverse, UI/UX, CRM, SEO and brand-design company. Our head office is in Surat, Gujarat, India and we have an office in Marburg, Germany. This page explains how we handle personal data for people and companies in the United Kingdom: visitors of our website, people who write to us, people who apply for a job, and the clients for whom we build and run projects.

A short rule that sums it up: we collect only what we need, we use it only for the work it was given for, we keep it safe, we do not sell it, and we delete or return it when the work is over.

02How we work on a client project

Every project goes through the same steps. At each step this is what happens to data:

  • 1. Enquiry: you write to us (form, e-mail, phone, chat). We keep your name, contact details and what you ask, only to reply and to make a quote.
  • 2. Agreement: we sign a contract and, when the project handles personal data of your customers or staff, a data processing agreement. It says what we may do with the data and for how long.
  • 3. Design and build: our team works on your requirements, content and, if needed, test data. We ask for test or sample data first. Real customer data is used only when the project cannot be tested without it, and only after you agree.
  • 4. Testing and launch: the project runs on servers you choose or approve. Access for our team is limited, named and logged.
  • 5. Support and updates: we see your live data only when you ask for support, and only as much as needed to solve the problem.
  • 6. Handover and end: we hand over the code, content and data, and delete our copies (see 'How long we keep data').

03What data we collect

We do not ask for sensitive data (health, religion, political opinion, biometric data, passwords of private accounts) for our own purposes. If a project needs it, the client tells us in writing and we apply stricter rules.

  • Website visitors: pages visited, device and browser type, approximate location from the IP address, and the cookies described below.
  • People who write to us: name, e-mail, phone number, company, country and the message, from the contact form, chat or e-mail.
  • Job applicants: the CV, contact details and what the applicant sends us.
  • Clients: company and billing details, names and contact details of the client's team, project files and the accounts we need to work on the project.
  • Data of a client's customers or staff, which a client lets us handle inside a project (see the next two sections). We do not collect this data for ourselves.

04How we save a client's data

The data of a client belongs to the client. We keep it like this:

  • Where: on the client's own servers or accounts where possible, otherwise on project servers that the client approves. The place (country) is written in the contract.
  • Who can open it: only the named members of the project team, each with a personal account. No shared passwords. When a person leaves the project or the company, the access is closed at once.
  • How it is protected: encrypted connections (HTTPS/TLS), strong passwords with two-step sign-in where the tool has it, separate working copies for each client, and regular updates of the software.
  • No private places: client data is not kept on private phones, private e-mail accounts or personal cloud drives.
  • Backups: made only where the project needs them, with the same protection, and removed on a schedule.
  • Records: we keep a log of who got access to what, and we keep a written plan for a data breach.

05Where a client's data is used

A client's data is used only in these places, and nowhere else:

  • To build and test the project the client ordered (website, app, CRM, AI tool, store, VR/AR world, design).
  • To run, host and support the project after launch, when the client asks us to.
  • To fix a fault, find the cause of a problem and improve the security of that project.
  • To meet a legal duty (for example when a court or authority asks, in a lawful way).
  • We do NOT use a client's data to train our own AI models, to make our own advertising, to sell to others, or for another client's project. If an AI tool in the project processes the data, we use only the tools the client has approved and the client is told which tool it is.

06Where our own data (visitors, enquiries, applicants) is used

  • To reply to you and make a quote.
  • To run, secure and improve our website (find errors, stop spam and attacks, see which pages are useful).
  • To judge a job application.
  • To send you news about our work, only if you agreed, and with a link to stop.
  • To keep the accounts, taxes and contracts that the law needs.

07Controller and processor

For our own site, enquiries and job applications we are the controller. For a project we build or run for a UK client, the client is the controller and we are its processor. The written contract that Article 28 UK GDPR needs is signed before we get the data.

08Transfers to India

India has no UK adequacy regulation. When our team can see UK personal data we use the International Data Transfer Agreement (IDTA) or the UK Addendum to the EU Standard Contractual Clauses, and we keep a transfer risk assessment. We add encryption, limited access and logging.

09Cookies and e-mail marketing (PECR)

On a UK website we build, a cookie that is not strictly necessary starts only after the visitor agrees. Marketing e-mails go only to people who said yes, or to existing customers about similar services with a simple way to stop them (soft opt-in).

10Data breach

We tell the client without delay and within 24 hours of finding a breach, so the client can report it to the Information Commissioner's Office (ICO) within 72 hours when the law says so.

11Your rights and complaints

  • Access, correction, erasure, restriction, portability and objection. Rights about automated decisions.
  • Withdraw consent at any time.
  • Complain to the Information Commissioner's Office (ico.org.uk), the UK authority.

Use a right: Write to info@we3vision.com with the subject "Privacy request". We answer within the time the law of your country allows (30 days at the latest unless the law says less).

12Who we share data with

We do not sell personal data. We share it only with: our own team members who need it; service providers who work for us under a contract (hosting, e-mail, project tools, payment services, analytics), who may use it only for us; the client for whose project we process it; and authorities when the law says we must.

A provider that holds a client's data is called a sub-processor. We tell the client before we use one and the contract gives it the same duties we have. The list is available on request.

13How long we keep data

We may keep data longer only if a law needs it or for a legal claim, and then only the part that is needed.

  • Enquiries that do not become a project: up to 24 months, then deleted.
  • Job applications: up to 12 months after the job is filled, unless the applicant agrees that we keep it longer.
  • Client contracts, invoices and tax records: as long as the law of the place requires (in India, usually 8 years).
  • Project working copies and a client's data: deleted, or returned to the client, within 90 days after the project ends or earlier on the client's written request. Backups disappear within 30 more days. If the contract says something else, the contract wins.
  • Server and website logs: usually up to 12 months.

14Security and data breach

We protect data with the measures above and we improve them over time. No system is 100% safe. If we find a breach that touches your data, we tell the client without delay (within 24 hours of finding it) and give the facts that the client needs to tell the authority and the people, as the law of the country requires.

15Data across borders

Our development team works from India, and we have an office in Germany. A client's data may therefore be seen or processed in India or Germany, and on the servers the client approves. When the law of the client's country limits such a transfer, we use the tool that law asks for (for example standard contractual clauses) and tell you in the country page.

16Cookies

Our website uses the cookies that it needs to work (for example to remember your choices). Where the law needs your consent for other cookies, we ask first and you can change your mind at any time in your browser. We do not use cookies to sell data.

17Children

Our website and services are for businesses and not for children. We do not knowingly collect data of children under 13 (or the age that the law of your country sets). If a client's project is meant for children, the client must get the consent of the parents and we build the steps into the project. If you think a child sent us data, write to us and we delete it.

18Changes to this policy

When the law or our way of working changes, we update this page and the date at the top. For a big change we tell our clients by e-mail. Older versions are available on request.

19Contact us

We3vision Private Limited, Surat, Gujarat, India. E-mail: info@we3vision.com. Phone: +91 7383216096. Our German office is in Marburg: see the Contact page for the address. Write "Privacy request" in the subject. If you are not happy with our answer, you can complain to the data protection authority of your country (named on the page of your country).

This policy explains how we work. It is not legal advice. For a project with special legal needs, we sign the contract and data processing agreement that your lawyer asks for.