Privacy Policy

The short version

This website has no accounts, no logins, no advertising and no analytics. It stores nothing about you on a server, because it does not have one — every page is a static file.

• The enquiry form never transmits to us. It assembles your answers into a WhatsApp message that you choose to send.
• One item is written to your browser's local storage: which currency you picked on the pricing page.
• We hold whatever you actively send us — an email, a WhatsApp message — and the project material you give us to build with.

The rest of this document is the same statement, spelled out.

What this policy covers

This policy covers websoup.in and the personal information the studio handles when you enquire, when we work together and afterwards.

It does not cover websites we have built for clients. Those are owned and operated by the client and carry their own privacy policies — Websoup is not the controller of data collected through them once a project has been handed over.

What we collect

Only what you hand over, and only for as long as it is useful.

• Enquiry details — your name, business name, phone number, email address and the description of what you want built.
• Correspondence — the emails and messages exchanged with you.
• Project material — text, images, logos, credentials for services you ask us to configure, and anything else you send us to build with.
• Billing details — the records needed to invoice you and keep proper accounts.

We do not collect special-category data, we do not buy contact lists, and we do not build profiles on visitors.

How the enquiry form actually works

This is the part most policies gloss over, so here it is precisely.

The form on the contact page runs entirely in your browser. When you press send, a small script validates the fields, formats them into a plain-text message, and opens WhatsApp with that message pre-filled. Nothing is posted to a Websoup server at any point — there is no endpoint to post to.

You then decide whether to press send inside WhatsApp. If you close the tab instead, nothing reaches us and nothing is stored anywhere but your own device.

Once you do send it, the message travels through WhatsApp and is governed by WhatsApp's own privacy terms in addition to this one.

Why we hold it

• To reply to you and to scope, quote and deliver the work you asked for — the basis is performing a contract, or taking steps at your request before one exists.
• To run the studio properly: invoicing, accounting and keeping records of what was agreed. The basis is our legitimate interest, and in the case of tax records, a legal obligation.
• To show completed work in our portfolio. The basis is our legitimate interest in demonstrating what we build; see the portfolio clause in the terms, and tell us in the brief if a project must stay private.

We do not use your details for marketing. There is no newsletter to unsubscribe from.

Cookies, storage and analytics

This website sets no cookies. It runs no analytics, no tag manager, no advertising pixel and no session recording, which is also why you were never shown a consent banner — there is nothing to consent to.

It writes exactly one key to your browser's local storage, websoup:ccy, remembering whether you chose USD, GBP or INR on the pricing page. It never leaves your device and clearing your browser data removes it.

Third parties in the page

One external request is made when you load a page here: the display typeface is served by Google Fonts. Requesting a font necessarily discloses your IP address and browser details to Google, which is subject to Google's privacy policy. No other host is contacted, and the page renders in a system font if that request fails.

Beyond the page itself we rely on ordinary business services — an email provider, WhatsApp for messaging, a static host for these files, and payment services when invoicing. Each handles data under its own terms; we share with them only what the task needs.

We never sell personal information, and we never pass it to anyone for their own marketing.

How long we keep it

• Enquiries that do not turn into projects are deleted once the conversation is clearly finished.
• Project correspondence and files are kept for the life of the engagement and a reasonable period afterwards, so we can support what we built.
• Credentials you shared for setup are removed from our side once the work is handed over. Change them anyway — that is good practice regardless of who held them.
• Financial records are kept as long as tax and accounting rules require.

Your rights

Depending on where you live you may have the right to ask for a copy of the personal information we hold, to have it corrected, to have it deleted, to restrict or object to how we use it, and to receive it in a portable form.

Write to hello.websoup@gmail.com and we will act on it. We will not charge you for asking and we will not make you explain why. If you believe we have handled your data badly, you are entitled to complain to your local data protection authority.

Security

The site is served over HTTPS as static files, which removes most of the attack surface a database-backed site carries. Correspondence and project material sit in access-controlled accounts held by the two of us and nobody else.

No system is perfectly secure. If a breach ever affected your information we would tell you, plainly and promptly, rather than waiting to be asked.

Children

This is a business-to-business studio site. It is not directed at children and we do not knowingly collect information from anyone under sixteen. If you believe a child has sent us personal information, contact us and we will delete it.

Changes and contact

If this policy changes, the updated version is published here with a new date at the top. Material changes affecting information we already hold will be raised with you directly.

The studio is the data controller for the purposes described above. For anything on this page, write to hello.websoup@gmail.com.

End of document · 22 August 2026