Passwords
There are none. Signing in is a single-use code sent by email, dead after 10 minutes, and an authenticator app can be added as a second step.
Security
Where BackendFree runs, what it never keeps in a readable form, how it handles the hard parts of bookings and payments, and what it does not claim.
In short
Everything is stored at DigitalOcean, LLC, Frankfurt, Germany. There are no passwords, no stored visitor IP addresses, no card numbers, and no artificial intelligence provider anywhere in the stack.
This page claims no certification. Every line is something the code or the deployment does. Updated 22 October 2026.
There are none. Signing in is a single-use code sent by email, dead after 10 minutes, and an authenticator app can be added as a second step.
Stored in a form they cannot be recovered from, and shown once, when they are made.
Never stored. The key made from one cannot be reversed and changes every day.
They never reach the platform: a customer types them into the payment provider's own page.
The hard parts
The database refuses the second booking, rather than a query that checked a moment earlier and was right at the time.
Opening hours are local wall clock and instants are UTC, converted once, on the website's own timezone. Clock-change weekends included.
Nothing confirms a booking except the payment provider itself. Coming back from a payment page confirms nothing, which is what stops a free appointment being one back button away.
Everything kept for an operational reason has a window it is deleted after, secrets are encrypted at rest, and API keys are stored as hashes. Your customers' names and emails are the part you cannot afford to improvise.
Every amount is a whole number of the smallest unit, cents or rappen, from the database to the payment provider. A decimal or floating point money field fails the checks every release has to pass.
No API answer may be stored by a shared cache. A CDN keys on the address, and the address never says which website asked: the key does.
Not claimed
The documents behind this page
Questions
At DigitalOcean, LLC, Frankfurt, Germany. The service and its data are hosted there, and the sub-processor list names every other company that can see any of it, and where.
No. There is no artificial intelligence provider anywhere in the stack, so nothing is sent to one.
Yes, it is already published. For your appointments, customers and visitors you are the controller and this platform is your processor. The agreement is that contract, with the measures and the sub-processors in its annexes.
It goes, with everything in it. Each website's content, appointments, customers and analytics are deleted, then the account. Payment records stay, as accounting records. Deleting is refused while a website can still take payments, so that is switched off first.
The Data Processing Agreement is published, and it is the processor contract you can hand over.