Skip to main content
Clinqly

Security, stated only as far as we can verify it.

What we do today to protect business and customer data, described without badges.

  • Separation in the database

    Row-level security is enabled on the tables that hold business and customer data, with policies that scope every read and write to the organisation it belongs to. A query that forgets to filter returns nothing rather than someone else's rows.

  • Each location is its own boundary

    Within a group, a location's customers, conversations, services and diary belong to that location. Working across branches is a separate, explicit scope, resolved on the server against real memberships, so it can only ever narrow.

  • Permission per person, per action

    Someone covering another branch can read its work and reply to its customers without being able to write off its opportunities. Team portal users see only their own appointments, hours and profile.

  • Connections

    Messaging channels are connected through their official business interfaces. When a team member connects a calendar, the access token is encrypted at rest and can be revoked at any time. The site and product are served over HTTPS.

  • Payments

    Clinqly never holds card details. Deposits are taken through the business's own Stripe account, and Clinqly receives Stripe's confirmation of payment.

  • Shared links and approved content

    Booking pages and manage links carry a noindex directive, so a leaked link does not become a search result. The receptionist answers only from the published version of each knowledge source, never from drafts.

Each practice above can be checked in the product today. Nothing beyond it is claimed on this page.

What we do not claim, and how to reach us.

Clinqly holds no security certification and has not completed a third-party audit. There is no published uptime commitment and no data-residency guarantee. If your organisation needs any of those, ask before you go live and we will tell you where things actually stand rather than point you at a badge.

Security questions, or something you think we have got wrong: hello@clinqly.io. Tell us what you found and how to reproduce it, and please give us a chance to fix it before publishing.

  • Can another Clinqly business see my customers?

    No. Access is scoped to your organisation in the database itself, so a query that failed to filter returns nothing rather than another business's rows.

  • Can staff at one of my locations see another location's customers?

    Only if you have given them a membership at that location. Working across branches is a deliberate scope, and the server resolves it against real memberships rather than trusting the browser.

  • Do you have a DPA?

    Our data-processing terms are being finalised and are subject to legal review. If your organisation requires one, talk to us before going live and we will work through your requirements directly.

  • Where do I find who processes our data?

    The privacy policy names each subprocessor and what it does. Security describes how access is controlled; privacy describes what is collected and why.

Questions about how Clinqly behaves? Ask them on the walkthrough.

We use essential cookies to keep Clinqly working. We also use analytics to understand how people use our website and improve it. You can change your preferences at any time.

Cookie policy