Skip to content
We3vision

Legal

Privacy Policy for European Union clients

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

The General Data Protection Regulation (GDPR) applies to a project for a client in any country of the European Union or the EEA, and to every person there whose data we handle. This page tells what that means for the way we work. (Germany has its own page for the German additions.)

21 sections

Laws this page follows

  • General Data Protection Regulation (EU) 2016/679 (GDPR)
  • ePrivacy Directive 2002/58/EC and the national cookie laws of each country
  • Standard Contractual Clauses of the European Commission (Decision 2021/914) for transfers to third countries
  • National data protection laws of each member state

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 European Union and the EEA: 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.

07Why we may use data (legal bases, Article 6)

  • Contract: to answer your enquiry, make a quote and do the work you ordered.
  • Consent: for the newsletter, for optional cookies and for anything else where we ask 'do you agree?'. You can withdraw it at any time.
  • Legitimate interest: to keep our site secure, to stop spam and abuse, and to run our business. We weigh it against your rights first.
  • Legal duty: for tax, accounting and when an authority asks us in a lawful way.

08Controller and processor

For our own website, enquiries, job applications and business contacts we are the controller. For the personal data that a client's customers or staff enter into a project we build or run for the client, the client is the controller and we are the processor under Article 28. We sign a data processing agreement with each client and keep a record of the processing (Article 30).

09Transfers outside the EU/EEA (Chapter V)

Our team in India has no adequacy decision of the European Commission. When the team can see EU personal data, the transfer is covered by the Standard Contractual Clauses (module 2 controller to processor, or module 3 processor to processor), a written transfer impact assessment, and added measures: encryption, limited and logged access, and a duty to challenge an unlawful order from an authority. Our German office in Marburg is part of the same group of We3vision.

10Sub-processors

We use a sub-processor (for example a hosting or e-mail service) only with the client's approval, with the same duties in a contract as ours, and we tell the client in advance about a change so it can object. The list is sent on request.

11Data breach

We tell the client without undue delay and within 24 hours of finding a breach of the client's data, so the client can tell the authority within 72 hours (Article 33) and the people where the risk is high (Article 34). For a breach of our own controller data we tell the authority and the people ourselves.

12Privacy by design and impact assessments

We build projects with data minimisation and default settings that protect privacy (Article 25). If a project is likely to be high risk (profiling, large-scale sensitive data, AI that decides about people), we help the client do the data protection impact assessment (Article 35) before it goes live.

13Your rights and complaints

  • Access, correction, erasure, restriction, portability and objection (Articles 15 to 21).
  • Withdraw consent for the future.
  • Complain to the supervisory authority of the country where you live, work or where the issue happened.

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).

14Who 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.

15How 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.

16Security 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.

17Data 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.

18Cookies

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.

19Children

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.

20Changes 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.

21Contact 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.