This page explains, in plain terms, how Servetic protects the data you and your customers put into the app. It is not a substitute for the Privacy Policy, which is the legal document if the two ever need to be read against each other.
Encrypted in transit
Every connection between your browser, Servetic's servers and connected providers (such as Google Calendar) is encrypted using TLS/HTTPS. There is no unencrypted step in between.
Encrypted at rest
Data held in the database, including OAuth tokens and calendar connection details, is encrypted at rest by the database provider while it is stored, not only while it moves.
Isolated at the database level
Every business's records are isolated at the database level, so one business cannot reach another business's data through the platform. Access to production data is restricted to authorized personnel who need it to operate the service.
Card payments never touch Servetic's servers
Card payment details are never stored on Servetic's servers. When you connect Stripe, PayPal or Square, card handling runs through that processor's own PCI-compliant systems, not through Servetic. See Connect a payment gateway for how to set one up.
Requesting access, correction or deletion
You can request access to, correction of, or deletion of your Servetic account information by contacting support@servetic.com. A request about one of your own customers' records should normally come from you as the business, since you control that relationship, not from the customer contacting Servetic directly.