Security

How Receptek protects your workspace.

A plain description of the controls built into the product today: who can do what in a workspace, how access is restricted, how secrets are handled, and how integrations are protected. If something here does not answer your question, email us.

Account roles and permissions

Every member of a workspace has one role. Roles limit which settings a person can change.

Primary Owner and Co-owner

Manage billing, the team, receptionist setup, integrations, and security settings. Only the Primary Owner can transfer ownership of the workspace.

Admin

Manages receptionist setup, integrations, and the team, including inviting Staff. Admins cannot change billing or security settings.

Staff

Works with calls, transcripts, appointments, follow-ups, and messages. Staff cannot change receptionist setup, integrations, billing, or the team.

Enforced on the server

Role checks run on the server for workspace API requests, not only in the interface. A request from a role without the required permission is refused.

Workspace access

Your data is scoped to your workspace and to signed-in members of it.

  • The dashboard and onboarding require a signed-in session. Unauthenticated requests are redirected to sign-in.
  • Workspace data is stored with database row-level security policies, so queries are limited to the workspace a member belongs to.
  • Passwords must be at least 10 characters. When email verification is on, a new account confirms its email through a secure link before onboarding continues.
  • Settings → Security can sign out every other signed-in session while keeping the current one active.
  • Authenticator-app two-factor sign-in and a workspace activity log are not available yet.

Secrets and credentials

Provider credentials and integration tokens stay on the server.

  • Keys for telephony, AI, payments, and email providers are read from server configuration and are never sent to the browser.
  • Google Calendar access granted through Google sign-in is stored on the server and read through a server-only database function when a booking needs it.
  • Webhook signing secrets are generated on the server. After creation only a masked prefix is displayed.
  • Settings and integration routes return generic error messages to the browser. Details are logged on the server, with sensitive values redacted from those logs.

Integration safeguards

Traffic between Receptek and other services is verified in both directions.

Inbound webhooks

Telephony callbacks are checked against the provider’s request signature before they are processed, and billing webhooks are verified with the payment provider’s signing secret. Each delivery is recorded so repeats are not processed twice.

Outbound webhooks

Destinations must be public https:// addresses; localhost and private-network addresses are refused. Every request is signed with HMAC-SHA256 over a timestamp and the body, and carries an idempotency key.

Slack

Only Slack incoming-webhook addresses are accepted, and Receptek sends messages to the channel you choose; it does not read your Slack workspace.

Calls and transcripts

Conversation audio is not recorded. Calls are stored as transcripts and summaries inside your workspace, and your team controls who can see them through roles.

What this page does not claim

We would rather be clear than impressive.

This page describes controls that exist in the product. It is not a certification, an audit report, or a service-level guarantee. Receptek does not currently publish penetration-test results, compliance attestations, uptime commitments, or data-residency guarantees. If you need specific assurances for your business, email support@receptek.ca and we will tell you plainly what we can and cannot confirm.

Found something, or have a security question?

Email us with as much detail as you can. Please do not include passwords or customer personal information in the message.

support@receptek.ca