Legal
Datenschutz / Privacy Policy for Germany
We3vision has an office in Marburg, Germany, and works for German companies. German law adds to the EU data protection rules (GDPR): the Federal Data Protection Act (BDSG), the rules on cookies and end devices (TDDDG) and the rules on the legal notice (DDG). This page says what a German client can expect and what we sign.
22 sections
Laws this page follows
- General Data Protection Regulation (GDPR, DSGVO)
- Bundesdatenschutzgesetz (BDSG), the Federal Data Protection Act
- Telekommunikation-Digitale-Dienste-Datenschutz-Gesetz (TDDDG, formerly TTDSG): cookies and access to the end device (section 25)
- Digitale-Dienste-Gesetz (DDG): legal notice (Impressum) of a website
- The data protection laws of the German states (Landesdatenschutzgesetze) for clients in the public sector
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 Germany: 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.
07Data processing contract (Auftragsverarbeitungsvertrag, AVV)
When we handle personal data for a German client, Article 28 GDPR needs a written contract. We sign it before we get access to the data. It says: what we process and for how long; that we act only on the client's documented instructions; that everyone on our team who sees the data is bound to secrecy; which technical and organisational measures (TOMs) we use; that we help with the rights of data subjects and with breaches; that we use sub-processors only with the client's approval; and that we delete or return the data at the end.
We can sign the client's own AVV template or give ours. The text can be in German or in English.
08Technical and organisational measures (Article 32 GDPR)
- Access only for named team members who need it for the project, with their own accounts and two-step sign-in where the tool allows it.
- Encryption of data in transit (HTTPS/TLS) and, where the client's setup allows, at rest.
- Work on the client's systems or on project servers, not on private laptops or personal clouds.
- Separate working copies for each client, deleted at the end of the project.
- A written plan for a breach, and a log of who got access to what.
- Training of the team about data protection and secrecy.
The full list is attached to the AVV and can be sent before you sign.
09Where the data is hosted
For German and other EU clients we agree where the project data is stored before the project starts. Where the project needs it, we use servers in Germany or the EU. Our development team is in India, which is a country without an EU adequacy decision, so access from India is a transfer to a third country: we cover it with the EU Standard Contractual Clauses (see the European Union page) and extra measures (encryption, limited access, logging).
11Legal notice (Impressum) and privacy page
A German business website needs a legal notice (section 5 DDG) and a privacy notice that is easy to find from every page. We add both to the websites we build, with the text the client gives us or a draft that the client's lawyer checks. The notice about this site is on the Contact page: We3vision Private Limited, Surat, India, with the German office in Marburg.
12Employee data and works councils
If a project handles data of employees (an HR tool, a time sheet, an intranet), section 26 BDSG and, where there is one, the works council (Betriebsrat) are involved. We build the project so that the client can show what is processed and why, and we do not build functions that watch the performance or behaviour of staff unless the client confirms that the works council agreed.
14Your rights
- Information and access (Article 15), correction (16), erasure (17), restriction (18), data portability (20), objection (21).
- Not to be subject to a decision made only by a machine that affects you in a big way (22).
- Withdraw consent for the future at any time (7).
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).
16How 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.
17Security 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.
18Data 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.
20Children
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.
21Changes 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.
22Contact 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.

