GoLocomotiveYour data
Where your app's data lives, who can reach it, how it is backed up, and how you take it with you.
Where it lives#
Your live app's data is one database file and one folder of uploaded files, on our production server, in a folder only your app's system user can open. Files can also live in a storage bucket of your choice, compatible with Amazon S3.
The working copy that agents change runs on our build machine, with its own separate data. Agents work there only. They have no access to the production server or to your live data.
Who can reach it#
| who | reaches | how |
|---|---|---|
| your users | what their role allows | the app's screens, through its server rules |
| your own AI | what the signed in account allows | the app's MCP server, through the same rules |
| the app's root account | everything in the app | used by our portal to manage your users at your request |
| our agents | the working copy only, never the live data | see How agents are contained |
| other customers | nothing | each app is a separate process, database and system user |
What the app keeps about people#
- Accounts: email, name, role, a one way hash of the password (never the password itself).
- The devices an account signed in from, to send new device alerts. A user can list and remove theirs.
- The journal, when your app turns it on: who changed what, with the internet address and browser of each change.
- Nothing else unless your app's data holds it. Your app holds what you ask it to hold.
Backups#
Backups run inside the app, on a schedule and with a store you choose (the server's disk or a bucket). Each one is a full, consistent copy of the data at one moment. See Backups.
Take it with you#
Your app's code and data are yours from day one. You get the full repository on request, at any time, and you leave with it whenever you want. The locosdk version your app runs comes with a perpetual license.
- The code is a full repository: every file of your app and its whole history of changes.
- Lists export to CSV, filtered as you like.
- The whole database is a standard SQLite file in the open PocketBase layout. PocketBase, an open source backend, opens it as it is.
- Backups are zip files of the data folder, in the same format PocketBase uses.
When the app goes offline#
Undeploy stops the live app and takes its address down. Its data stays on the server, so a later deploy brings it back as it was.
Not published yet#
- A data processing agreement and the legal terms of the service.
- The name of our hosting provider and the region of the production server.