Privacy Policy | Mobile App Devs

Last updated: September 2026

This policy covers mobileappdevs.net and the enquiries sent to us through it. If anything below is unclear, write to info@mobileappdevs.net and we will explain it in plain language rather than in more of this.

In one paragraph

This site has two forms. Whatever you type into one of them is sent to us by email and kept as a record so we can reply and, if you become a client, run your project. Nothing else about you is gathered in the background: there is no advertising pixel, no social widget, no session recorder, no third-party spam-protection service and no fingerprinting. We do not sell your information and we do not share it for advertising. Analytics is not currently enabled on this site — if that changes, this page changes with it. You can ask us to delete what we hold at any time using the address at the end.

Who is responsible for it

Mobile App Devs is a mobile app development studio. We work Monday to Friday, 10:00–19:00 Indian Standard Time. For the purposes of this policy we are the business that decides what happens to anything you submit here. You can reach us by email at info@mobileappdevs.net or by phone at +1 341 208 1344.

The two places you can send us something

Neither form asks you to create an account, and neither asks for anything we do not need in order to reply.

1. The enquiry form on the contact page

Submitting it sends us exactly these fields, and nothing else:

Name and email address — both required, because they are how we address and send the reply.
Phone or WhatsApp number and company name — optional, used only if you would rather we called.
What you need — the option you pick from the list, such as a new app, an MVP, a rebuild or support only.
Platforms — whether you want iOS, Android, both, or want us to advise.
Where you are now — the stage your project is at.
Budget range and timeline — the options you select, so the reply is about your situation rather than generic.
Whether you ticked the NDA box — recorded as a yes or a no, so we know to send a mutual NDA before discussing detail.
Your message — required, and passed to us exactly as typed. Please do not paste passwords, API keys, card numbers, health information or anything similar into it; if you need to share credentials during a project we will set up a proper channel for that.
The date and time of submission — added by the server, not by you.

2. The email capture on the cost estimator

The estimator itself runs entirely in your browser. Moving through the options and seeing a figure sends us nothing at all. Only if you choose to submit the short form alongside your result do we receive:

Name and email address.
The range that was displayed to you and a summary of the options you selected, so the reply can refer to the estimate you actually saw rather than asking you to describe it again.
The date and time of submission.

The spam checks, and why no third party is involved

Two mechanisms protect both forms, and neither of them contacts an outside service or profiles you.

A server-side arithmetic question. The page shows you a simple sum such as “4 + 7”. The two numbers and an expiry time are carried in a signed token in the form itself, so our server can check your answer without storing a session or a database row and without asking anyone else. The token expires after a short window, which is why a form left open for a long time will ask you for a fresh sum. No cookie is set, and nothing about the check leaves our server.
A hidden honeypot field. There is a field on each form that is positioned off-screen and never shown to a person. Automated submissions tend to fill in every field they find; a submission with anything in that one is discarded. Nothing is recorded about it.

There is deliberately no reCAPTCHA, no hCaptcha and no equivalent product on this site, because those services observe your behaviour on the page and report it to a company you have no relationship with, which is a steep price for keeping out a few bots.

What happens after you press send

Two things, both of them deliberate:

The submission is emailed to us. It goes to a single internal mailbox that our team reads. The message is sent through a transactional email relay — a third-party service that exists to deliver application email reliably — acting as a processor on our behalf. We are not naming the internal mailbox here, but it is a normal business inbox and the same people answer it as answer the phone.
The submission is also written to the server-side log. This is a safety net, not surveillance. If the email relay fails, an enquiry that would otherwise vanish can still be recovered and answered. The log entry contains the same fields the email contains and nothing more, it sits on our own hosting, and it is rotated and cleared on the schedule described under retention below.

Why we are allowed to process it

Because you asked us to. Every field described above comes from a form you chose to fill in with the purpose of getting a reply, and we use it for that reply, for the quote or estimate that follows, and — if you go ahead — for running and invoicing the project. We do not use enquiry details to build a marketing list, and we do not add you to a newsletter for having contacted us.

Who else touches it

Our hosting provider, which runs the server this site sits on and necessarily processes the request that carries your submission.
A transactional email relay, which delivers the notification message to our mailbox.
Our business email provider, where the resulting message is stored and read.

Each of them handles your information to provide their service to us and not for their own purposes. We do not pass anything from these forms to advertisers, data brokers or any other third party.

Cookies

This site sets only the functional cookies WordPress itself uses, for example if someone signs in to the administration area. As an ordinary visitor reading these pages you will generally not be given one at all. There are no advertising cookies, no tracking cookies and, at present, no analytics cookies. Neither form sets a cookie, and the spam check deliberately works without one.

Analytics

There is no analytics on this site at the moment. No measurement script is loaded, no analytics cookie is set, and no visit data is sent anywhere. This is not a promise for all time — if we do turn analytics on, this section will describe what it collects before it starts collecting it, rather than afterwards.

What this policy does not cover: the apps we build

This is worth stating clearly, because it is the most common confusion on a site like ours. When we build a mobile app for a client, that app is the client’s product. They are the ones who decide what it collects, they write its own privacy policy, and they complete the privacy and data-safety declarations that Apple and Google require for the store listing. We advise on all of that, and we will push back hard on collecting data an app does not need, but we are not the controller of your data as a user of somebody else’s app. If you have a question about an app you downloaded, its own listing names the company responsible for it.

How long we keep things

Enquiries that do not become projects — kept for up to twenty-four months, because people frequently come back the following year with the same idea and a budget, then deleted.
Enquiries that become projects — kept for the length of the engagement and afterwards for as long as we need them for contractual, accounting and tax records.
Server-side delivery logs — rotated and cleared within a few months; they exist only as a recovery route for a failed email.
Ordinary web server request logs — kept briefly by our host for security and diagnostics under their own retention schedule.

Security

The site is served over HTTPS. Both form handlers verify a one-time token before accepting a submission, which stops a third-party page from posting on your behalf, and every field is sanitised on the server before it is used. Access to the mailbox and the hosting account is limited to the people who need it and protected by two-factor authentication. No arrangement is perfect, and we would rather say that than claim otherwise — which is also why the forms tell you not to send credentials or sensitive personal information through them.

Your rights

This site is not targeted at a single country, and the rights you have depend on where you live. Many data protection laws — including those in the European Economic Area, the United Kingdom, India, Brazil, Canada and several US states — give people some combination of the right to know what is held about them, to get a copy, to have errors corrected, to have it deleted, to object to or restrict certain uses, and not to be treated worse for asking.

Whatever your local law says, our practice is the same for everyone: email info@mobileappdevs.net from the address you contacted us with, tell us what you want done, and we will action it and confirm in writing, normally within thirty days. There is no charge and no form to fill in. If your local law also gives you the right to complain to a regulator, you can do that without asking us first.

International transfers

We work to Indian Standard Time and our suppliers operate internationally, so information you send may be processed on servers outside your own country. Where that happens it is on the basis of the service agreements we hold with those suppliers, and the safeguards do not change what is described above: the same limited fields, the same purpose, the same retention.

Children

This site sells development services to businesses. It is not directed at children and we do not knowingly collect anything from one. If a child has submitted a form here, tell us and we will delete it.

Links to other sites

Some pages link out — to WhatsApp, to app store listings, to platform documentation. Once you follow one of those links you are on someone else’s site under their policy, not ours.

Changes to this policy

If what the site does changes, this page changes with it, and the date at the top moves. We will not quietly broaden what we collect and leave a stale policy sitting here describing a version of the site that no longer exists.

A note on what this is

This is a plain-language description of how one small business handles the information sent through its own website. It is not legal advice, and it is not a substitute for advice from a qualified professional about your own obligations. If you are writing a privacy policy for an app we are building for you, we will help you work out what it needs to say — but the document itself should be reviewed by your own lawyer.

Contact

Questions, corrections or a deletion request: info@mobileappdevs.net or +1 341 208 1344, Monday to Friday, 10:00–19:00 IST.