Cloud data: the same records on every device
How do I stop my app losing its records when the browser is cleared or I switch phones?
Open the Cloud data tab on the manage screen, set a passcode and turn it on, then ask the builder once to keep the records in the cloud and publish again. After that the app's ledger, stock or attendance is kept on our servers, and anyone with the passcode sees exactly the same records from any phone or computer. It is on the Business and Commerce plans.
The whole thing in one line
Whatever your app keeps track of used to live only in the browser it was typed into. Turn cloud data on and it is kept on our servers instead, so anyone you give the passcode to sees exactly the same records from their own phone or computer.
What was actually going wrong
Say you built a staff salary ledger. Names, salaries, what you paid, what is still due, all typed in. It looks perfect. But those records were being kept inside that one browser on that one phone, and three things followed:
- Open it on another phone or computer and the ledger is empty. The link travels; the records do not.
- Clear that browser's data, or lose the phone, and it is gone. We could not get it back either, because it was never on our servers in the first place.
- A colleague or your accountant could not see the same ledger. Each of them got their own separate, empty copy.
For a menu or an about page none of this matters. For a ledger, a stock list, an attendance register or a customer list it is the single biggest problem there is. Cloud data exists for exactly that.
What cloud data is, and what it is not
What it is: a place on our servers that belongs to your app, where it keeps its records and reads them back. It opens with a passcode. The same records on any device.
What it is not: it is not a database you log into and run SQL against, or open phpMyAdmin on to create tables. The hosting is still static: PHP, WordPress, WooCommerce, Node, Python and MySQL do not run here. What changed is that your app's records are no longer trapped in one browser.
Who has it
The Business and Commerce plans. It is not on free sites, and not on the 6,999 BDT lifetime hosting either, because the storage, the backups and the screening behind it cost something.
Moving up to Business includes the lifetime hosting in its price, and if you have already paid the 6,999 you pay only the difference, never the full price twice.
Turning it on
Three steps, and it is the third one people skip.
1. Open the manage screen. The "Manage site / app" button in the sidebar, then the Cloud data tab along the top.
2. Set a passcode and press Turn it on. At least 6 characters. This is the passcode you will hand to the people who should see the records, so do not use your phone unlock PIN or a bank password here.
3. Tell the builder once. Setting a passcode does not by itself make the app store anything in the cloud; the app's code needs a small change, and the builder makes it for you. Go to the builder and ask, in Bengali or English:
"Keep the records in the cloud so they open on any phone."
Then publish again. Skip this step and cloud data will be switched on quite happily while the app carries on saving into the browser.
How the app behaves afterwards
An app whose whole job is keeping records will show a small passcode box when it opens. Enter the passcode, the records come down from the server, and from then on everything you type goes back up by itself. The phone remembers the passcode, so it is not asked for every time.
If instead you have a public shop site with a hidden owner view inside it, tell the builder to put the passcode box only in that view. A public page should not greet every customer with a password box.
Nothing you already had is lost. Whatever was in your browser when you turned it on is pushed up to the server on the first sync. An empty cloud never wipes your existing ledger.
Who to give the passcode to
Whoever has it can see the records and change them. There is no separate record of who wrote which row, so this is not a login system; it is the key to the shop's cash box.
When someone leaves, go to the Cloud data tab and change the passcode. Every phone opened with the old one is signed out the moment you do.
How much it holds
| Plan | Names | Total space | Saves per day |
| Business | 5,000 | 10 MB | 10,000 |
| Commerce | 20,000 | 50 MB | 30,000 |
A "name" is not a row. An app usually keeps everything under two or three names like "entries" or "staff", and one name can hold thousands of rows. One name holds up to 64 KB, which is a ledger of a few hundred lines.
If the numbers look small, do the arithmetic: 1 MB alone is roughly ten thousand rows of an ordinary salary ledger, and Business has ten times that.
What may not be kept here
Some things we refuse outright, and we will not store them even if the app sends them:
- Passwords, PINs, MPINs, OTPs
- Card numbers and CVVs
- API keys and secret tokens
If the app sends one, it is not saved and the reason appears on screen. That can sound annoying, but the rule is there for you: the only reliable protection for these is not keeping them anywhere. And on the day somebody builds a phishing page on this platform to collect stolen PINs, this is the rule that keeps every other customer's site from being blocked alongside it.
Getting your records out
At the bottom of the Cloud data tab, Download all data (JSON). The whole thing in one file, any time, at no cost. These are your records, and the way to put them in your own hands stays open.
Beside it, Delete all data. That removes everything from the server and cannot be undone, so download the file first.
Turning it off and deleting it are different things. Clearing the passcode closes the door; the records stay exactly where they are, and setting a new passcode brings them all back.
A few honest limits
- This is not multi-user accounting software. If two people change the same ledger at the same time, whoever saved last wins. In a small shop or office that never bites, but it is worth knowing.
- There is no per-person trail. Everyone with the passcode is the same person as far as the system is concerned.
- The hosting is still static. No program of yours runs on the server. This is somewhere to keep records, nothing more.
- It is in the backups. These records go into the platform's regular backups, and a copy of those goes to a different company's servers.
Questions
Does the 6,999 BDT lifetime hosting include cloud data?
No, it starts at Business. Lifetime hosting gives you the site, the forms and the inbox, but the app's records stay in that browser. Moving up to Business includes the lifetime hosting in its price, and if you already paid the 6,999 you pay only the difference.
Can I add it to an app I built a long time ago?
Yes. The age of the app makes no difference. Turn cloud data on, ask the builder once, and whatever is sitting in that browser goes up on the first save.
What if I forget the passcode?
Set a new one from the manage screen. The stored records are untouched; the phones opened with the old passcode simply ask for the new one.
Can visitors see my records?
Nobody sees anything without the passcode. And if the app is a public shop site, ask the builder to keep the passcode box inside the owner view only.
Can support see my records?
No. Support can open your manage screen and see whether cloud data is on and how much space is used, but the records themselves and the download are closed to them, and they cannot change your passcode either.
How is this different from my inbox?
The inbox is where other people's submissions land: an order or a message someone filled in a form to send. Cloud data is where the app itself keeps what it remembers: the ledger, the stock, the attendance. Plenty of shops need both.