Security and hosting
The short answer
Every platform we build runs on managed infrastructure with encrypted connections, row-level database permissions, and automatic backups. Each person signs in as themselves and sees only what their role allows. The data stays in your database, owned by you, and we can show you exactly who can reach what.
Signing in
- Individual accounts with individual passwords. No shared logins between staff.
- Email and password, or sign in with Google where you prefer it.
- Password reset by emailed link, with the link expiring after use.
- Sessions expire, and signing out ends the session on that device.
- Client and staff areas are separate, so a customer signing in never lands in your internal tooling.
Permissions
Permissions are enforced in the database itself rather than only in the interface. That distinction matters: hiding a button stops someone clicking it, while a database rule stops the data being returned at all, even to a crafted request.
Roles are defined per platform around how your business actually works. An owner, a manager, a technician, and a customer each see a different slice, and a customer signed into the portal can only ever reach records tied to their own account.
Encryption and data handling
- All traffic runs over HTTPS, with certificates renewed automatically.
- Data is encrypted at rest on managed database infrastructure.
- Passwords are stored as one-way hashes, never in readable form.
- Secrets such as payment and email keys live in server-side configuration and are never sent to the browser.
- Card payments run through Stripe, so full card numbers never touch your platform or ours.
Backups and recovery
Databases are backed up automatically on the managed platform, with point-in-time recovery available, so a bad import or a deleted record can be recovered rather than reconstructed from memory.
Code lives in version control, so any release can be rolled back. Hosting is redundant across a global network rather than a single machine in a single location.
Hosting
Platforms are served from a global edge network, which is why pages arrive quickly regardless of where the visitor is. Hosting, certificates, scaling, and infrastructure monitoring are included in the monthly subscription rather than billed separately or left for you to manage.
Because the platform is ordinary code, it can also be hosted elsewhere. Nothing in the architecture ties you to a single provider.
Who at SpinFlow can see your data
Access is limited to the people working on your build, for support and maintenance. We do not sell data, we do not share it between clients, and we do not use one client's business data to train anything for another.
If you need access narrowed further, say so during discovery and we will scope it that way from the start.
Common questions
Questions about security and hosting
Where does my data live?
In a managed database dedicated to your platform, encrypted at rest, with automatic backups and point-in-time recovery. It is your data and you can export all of it at any time.
How are staff and customer permissions kept apart?
Permissions are enforced by database rules tied to the signed-in account, not just by hiding parts of the interface. A customer request for a record outside their account returns nothing.
Do you store card details?
No. Card payments are handled by Stripe, so full card numbers never reach your platform.
What happens if something breaks or data is deleted by mistake?
Code releases can be rolled back through version control, and the database supports point-in-time recovery, so an accidental deletion can be restored rather than retyped.
Bring your security requirements to discovery
If you have a compliance checklist, an access policy, or an IT team with questions, we would rather answer them before the build than after.