Privacy Policy

Your projects stay on your phone

The apps you make (their name, website address, colours, pages, contact details and icon) are saved on your phone. Making and testing apps needs no account and no sign-in. Deleting a project in the app, or uninstalling the app, removes it from your phone. The one exception is a paid app: see Publishing on Google Play.

Reading your website

When you type a website address, the app downloads that site's public home page, directly from your phone, to suggest a name, a colour and an icon for your app. Only public information that any visitor sees is read. To verify that a website is yours, our server reads the public page or file you add the code to.

What is sent when you build

To turn a project into an installable app, the app sends it to our build server, which runs on Google Cloud in the United States. A build request contains:

• the project itself: app name, website addresses, colours, pages, the contact details you entered and the icon picture;
• the Google AdMob app and banner IDs you paste, only if you add ads to your app;
• your phone's processor type, so a test app is built for it;
• your account identifier (see below).

The server keeps:

• The built app files and their build records (app name, package name, version, times and a technical build log) so you can download them. Test builds are deleted after 7 days, builds for Google Play after 30 days.
• A copy of an unpaid app's last test build: its settings (including the contact details you entered) and its icon, from which its free publishing kit is made (the privacy page, store listing drafts, Data safety file and store graphics). It is replaced by each new test build and deleted, with that kit and its privacy page, after 90 days in which the kit is not opened and the app is not built.
• An app published free (the free plan): which of NasrTech's AdMob apps it shows ads from and whether those ads are switched on. The app asks a small public file at start whether to show them; that file holds no personal data. Deleting your account switches them off.
• The store assets pack: whether your subscription is active and until when, and the framed screenshots you made from pictures you added (kept with your app's kit, deleted with your account).
• Single app's 24-hour offer: the offer code made for you and when it ends; the code is deleted on Gumroad when the 24 hours are over.
• The version number and a fingerprint of each Google Play build (no personal data), so the same version can go from testing to Production after its files are deleted.
• An upload key made for each of your apps, so every later build of the same app installs as an update and Google Play accepts it. It is stored encrypted and used only to sign your builds. You can export it in the publishing kit. Keys of apps that were never published and not built for 180 days are deleted.

Your account

The first time you build, the app creates an anonymous account with Firebase Authentication: a random identifier with no name, email address or phone number. It keeps your builds and keys apart from everyone else's and applies fair daily limits. The server also sees your IP address with each request, which it uses for rate limiting only.

To publish on Google Play you sign in with your Google account (optional otherwise). Firebase then links your Google account's email address and name to that identifier, so a paid app, its key and its updates come back when you sign in on a new phone. You can sign out in Settings › Account.

Menu & Booking App Maker and Nasr App Maker, our website-to-app maker, share the same server and account system. If you sign in with the same Google account in both, it is one account, with the same apps and plans, and deleting it in one app deletes it in both.

Publishing on Google Play

The app can publish your app on Google Play:

• Payment. Publishing an app is paid through Google Play: one payment for one app (Single app), or a monthly or yearly plan. Google handles the payment; we never see your card or bank details. Our server checks the purchase with Google Play and keeps the order number, the date, the app it paid for and a fingerprint of the purchase token.
• A saved copy of each paid app. Each build for Google Play saves a copy of that app's settings (including the contact details you entered) and its icon to your account, so you can restore it on a new phone.
• Your publisher details. The name and email you give as the app's publisher, your website's privacy link, your answers about what your website collects and, if your website has accounts, its account deletion link. They are shown publicly on the privacy page we host for that app (a page Google Play links to), and fill in its Data safety answers.
• Publishing from the app. If you choose to, the app can publish for you. We create a Google Cloud service account just for you (its email address starts with pub-), which you invite in your own Play Console with the permissions you choose; you can remove it there at any time. Our server uses it only when you tap Check or Publish, to send Google Play the version and what you prepared in the publishing kit: the store listing texts, icon, feature graphic, screenshots and Data safety answers. We keep a record of each publishing job (the track, the version, the steps and Google's answers), not your listing texts.
• Store screenshots. The pictures you add are framed on your phone. When you publish from the app, they are uploaded to our server, re-encoded and sent to Google Play. They stay on your account, so a retry doesn't need them again, until you delete your account.

AI icons

A paid app can get icons drawn by AI. When you tap Create with AI, our server asks Higgsfield, an AI image service, to draw one icon from a description made only of your choices: a business type, a style and a colour. Your website, its text, your contact details and other personal data are never sent. The picture is kept on your account (up to 10 per app) until you delete your account.

Photos in your app's pages

You can add photos from your phone to your app's pages (for example your dishes, products or shop). You add them while signed in with your Google account. The app makes them smaller on your phone and removes their location and camera details, then keeps them privately on Google Cloud to build your app. A photo is deleted 60 days after it was last uploaded or used in a build, or when you delete your account. Photos of an app you published on Google Play are also kept with that app's saved copy, so you can restore it on a new phone, until you delete your account. The app files we build that contain your photos are deleted after 7 days (test copies) or 30 days (Google Play builds). We never show your photos to anyone except inside the apps you build.

To keep harmful pictures out of the apps we build, the photos of an account without a paid plan are checked once, automatically, by Google Cloud Vision SafeSearch (adult or violent content) before they go into a build; Google processes them only for that check, and we keep its answer (no picture) so a photo isn't checked twice. A photo that fails the check can't be built into an app. The sample photos in our ready designs are ours, made for these templates.

Analytics and crash reports

• Firebase Analytics records usage events (for example, that a build finished) with a device model and country. It never includes what you type. The app doesn't use the Android Advertising ID.
• Firebase Crashlytics records crash reports with the device model, Android version and a technical stack trace, so faults can be fixed.

You can turn off usage statistics at any time in the app: Settings › Share usage statistics. You can also reset or delete your Advertising ID in your phone's settings.

No ads

The app shows no ads, and we don't sell or share your information with anyone for advertising.

The apps you make

The apps built for you contain no analytics or tracking from us.

• Without ads, an app asks only for the Internet permission and shares nothing about its users, including their location.
• With ads (your choice, with your own Google AdMob IDs), the app includes Google's Mobile Ads SDK. It collects device identifiers such as the Advertising ID, an approximate location derived from the IP address, and app interaction and diagnostic data, and shares them with Google to show and measure ads, after asking for consent where the law requires it (for example in the EEA and the UK). You are that app's developer: the privacy page we host for it and its Data safety answers say this.

Free test builds show a small “Made with” badge and always use Google's test ads, never your real ones; apps built for Google Play have no badge. Your website inside your app keeps its own privacy practices.

Permissions we use

• INTERNET — to read your website, send builds to the server, check purchases and download the built app.
• Google Play's billing permission, for the publishing purchase.
• POST_NOTIFICATIONS and RECEIVE_BOOT_COMPLETED — only if you allow notifications: reminders the app schedules on your phone (for example, to finish an app you started), set again after the phone restarts.
• Saving to Downloads uses Android's standard file saving, with no storage permission. The app never installs anything itself: you install your test app from Downloads.

Children

The app is a tool for business owners, is not directed at children under 13, and we do not knowingly collect information from them.

Deleting your account and data

In the app: Settings › Account › Delete account and data. This deletes from our server your upload keys, the privacy pages we host for your apps (they stop working), your paid apps and their saved copies, your publisher details, builds, website checks, your publishing account (we delete it on Google Cloud) and its job records, the screenshots and photos you uploaded, your AI icons and your sign-in. Paying again is needed to publish an app again. We keep only the order number and date of each payment, for tax and fraud checks.

Without the app, email support@nasrtech.dev from the Google account you signed in with, and say you want your Menu & Booking App Maker account deleted. We delete it within 30 days and reply when it's done. Built app files are also deleted on their own (above). Note that a deleted upload key can't sign updates for apps already on Google Play, so export it first if you'll publish updates.

Changes to this policy

We may update this policy; changes will be posted on this page with a new "Last updated" date.

Contact

Questions about this policy: support@nasrtech.dev

← Back to Menu & Booking App Maker