Security & data

How Qualimize handles your lead data

Qualimize keeps each customer's leads in a separate workspace that only that customer's team can reach, enforced in server code rather than in the browser.

When a lead changes stage, Qualimize sends Meta's Conversions API the event name, a status code and contact details hashed with SHA-256, never plain-text email, phone or name, and never notes or follow-ups.

Meta access tokens are encrypted with AES-256-GCM, passwords are hashed with bcrypt, and sign-ins, exports and deletions are written to an audit log.

  • SHA-256 hashed match keys
  • AES-256-GCM encrypted tokens
  • 3 roles, checked on the server

Last reviewed against the product code on . See also our Privacy Policy and Terms of Service.

01 · Meta Conversions API

What we send to Meta, and what we never send

When a rep moves a lead to a stage your Admin has mapped, Qualimize sends one server event to Meta. This is everything in it.

Sent to Meta

  • The event for the stage. Contact, Lead, SubmitApplication or Purchase, depending on which of the four signals your Admin attached to the status.

  • A status code. A short code for the lead's status (lead_status), so you can tell events apart in Meta's Events Manager.

  • Hashed contact details. Email, phone, first and last name, plus city, state, postcode and country when your form asked for them. Normalised and SHA-256 hashed with Meta's official Business SDK before they leave our servers.

  • Lead IDs. Meta's own lead ID for Instant Form leads, and a SHA-256 hash of Qualimize's internal lead ID.

  • Browser signals, for website leads. The fbc and fbp click cookies, IP address and browser user agent when they were captured. Meta's specification requires these unhashed, so they are sent as captured.

  • Value, on Purchase only. The deal value and currency you recorded. If none is recorded, a nominal value of 1. No other event carries a value.

  • A stable event ID. The same lead reaching the same stage always produces the same event_id, so a repeat can never be counted twice.

Never sent

  • Plain-text email, phone number or name
  • Notes, follow-up tasks or the activity timeline
  • Answers to your other form questions
  • Which rep worked the lead, or anything about your team
  • A deal value on any event other than Purchase
  • Meta's relay email addresses (@devnull.facebook.com), which identify no one

Events go straight from Qualimize’s servers to Meta, marked action_source: system_generated. Every send is listed in Settings. How the signals work is on the Meta Conversions API page.

02 · Your Meta connection

How your Meta connection is stored

Qualimize connects to your own Meta Business account with a token you create there. Here is what happens to that token.

Encrypted before it is saved

The token you paste from your Meta Business account is encrypted with AES-256-GCM, using a fresh random IV every time and an authentication tag that makes tampering detectable. The key lives in server configuration, not in the database.

Never sent back to the browser

Once saved, the token is only decrypted on the server at the moment of a call to Meta. Settings shows a fixed mask, so even an Admin cannot read the token back out of Qualimize.

Admins only

Connecting Meta, changing the token, the Pixel or the stage mapping all require the Admin role. Managers and Sales Executives see whether Meta is connected, nothing more.

Signed webhooks

New leads arrive through Meta's webhook. Each delivery's HMAC-SHA256 signature is checked against Meta's app secret, and anything unsigned or mismatched is rejected.

03 · Roles

Who can see what

Every workspace has three roles. The workspace owner is an Admin. There is no read-only viewer role.

Can theyAdminManagerSales Executive
See leadsYesAll, or their team'sOnly assigned to them
Create and edit leadsYesYesYes
Assign leads to repsYesYesNo
Export leadsYesYesOnly their own
Import leadsYesNoNo
Delete leadsYesNoNo
Invite, disable or remove usersYesNoNo
Connect Meta and change credentialsYesNoNo
Company-wide dashboard and analyticsYesYesNo

“Their team’s” applies when two-tier lead distribution is switched on and the Manager owns a team. Without it, a Manager sees every lead in the workspace.

04 · Workspace isolation

Your workspace is yours alone

Isolation is enforced in server code on every request, not by hiding things in the interface.

One organization per customer

Every workspace is its own organization, and each user belongs to exactly one. Data is kept apart logically inside one PostgreSQL database, not in a separate database per customer.

Filtered on the server

Lead lists, search and exports are filtered by your organization ID on the server, and opening a single lead first checks that it belongs to your workspace. The browser never decides which workspace it is looking at.

Real 403s, not hidden buttons

Permissions are checked in server code before a page renders or an action runs. A user without the permission gets a 403 response, even if they type the URL directly.

Suspension takes effect at once

If a workspace is suspended, or an Admin disables a user, their sign-in stops working on the next page load, without waiting for the session to expire.

The application runs on Vercel and the PostgreSQL database is hosted by Supabase. Other service providers are listed in our Privacy Policy.

05 · Sign-in

Sign-in and account protection

Email and password sign-in, with the protections below built into every account.

  • Passwords are hashed with bcrypt (cost factor 12). The plain password is never stored.
  • Passwords must be 8 to 72 characters.
  • A new account must verify its email address before it can sign in.
  • Sign-in attempts are limited to 10 per email address and 50 per network address every 15 minutes.
  • A failed sign-in shows the same message whether the email exists or not, so the form cannot be used to discover accounts.
  • Sessions use a random 256-bit token in an HttpOnly, Secure, SameSite cookie. Only a SHA-256 hash of it is stored, so a copy of the database cannot be used to sign in.
  • Password-reset and verification links are single-use, expire, and replace any earlier link. Resetting a password signs that user out on every device.

On every page

  • HTTPS enforced with HSTS for two years, including subdomains
  • Pages cannot be framed by other sites (clickjacking protection)
  • A Content Security Policy limits where scripts and connections can go
  • Camera, microphone and location access are switched off

06 · Retention

Data retention and deletion

Your data stays while you subscribe, is locked but kept for 90 days after, and is then deleted automatically.

  1. 01

    While subscribed

    Your workspace data is kept for as long as your subscription is active.

  2. 02

    Subscription ends

    The workspace is locked, but nothing is deleted. Restoring an active subscription restores access and data.

  3. 03

    After 90 days

    A daily automated job permanently deletes leads, follow-ups, activity, campaigns, Conversions API send logs, messages and support tickets.

The 90-day deletion keeps your account record, user logins and billing records (see section 7 of the Privacy Policy), along with workspace settings such as your saved Meta connection.

Export your leads any time

Download leads as CSV or Excel, including the answers from your Meta forms. Exports follow the same role rules as the lead list, and each one is recorded in the audit log.

Deleting a lead

Admins can delete leads one at a time or in bulk. The lead, its activity timeline and its follow-ups are removed straight away. The audit log keeps a record of the deletion, including the lead’s name and email, and the Conversions API send history keeps the lead’s email.

07 · Activity logs

A record of who did what

Security-relevant actions are written to an audit log with who did it, when, and the details. Qualimize’s code only ever adds entries; it has no function to edit or delete them. Inside your workspace, every lead also has its own activity timeline.

When Qualimize staff sign in as one of your users, the session is logged, and every action taken during it records both the staff member and the user.

Logged, among others

  • Sign-ins and failed sign-ins, with IP address and browser
  • Password resets and email verification
  • Users invited, disabled, or given a new role
  • Meta connected, disconnected, or its token, Page or Pixel changed
  • Changes to which statuses send which Meta event
  • Lead imports, exports and deletions
  • Every time Qualimize staff sign in as one of your users

08 · Questions

Security, answered

What buyers ask before they connect their Meta account and move their leads in.

Something not covered here?
Ask us on the contact page

Only as SHA-256 hashes. Email, phone and name are normalised and hashed with Meta's official Business SDK before they leave Qualimize's servers, so plain-text contact details are never sent. Notes, follow-ups and answers to your other form questions are not sent at all.

It is encrypted with AES-256-GCM before it is saved, decrypted only on the server when Qualimize calls Meta, and never sent back to the browser: Settings shows a fixed mask. Only Admins can connect Meta or change the token, and each change is written to the audit log.

No. Each customer is a separate organization, and lead lists, search, exports and lead pages are all checked against your organization's ID on the server. The isolation is logical, inside one PostgreSQL database, and is enforced in server code rather than in the browser.

Qualimize's platform administrator can sign in as a user of your workspace, for example to help with setup. Each such session is recorded in the audit log with the staff member's identity, and every action taken during it records both the staff member and the user.

No. A Sales Executive only sees leads assigned to them, and an export only includes leads the person exporting can see. Every export is recorded in the audit log. Only Admins can import or delete leads.

Your workspace is locked but nothing is deleted for 90 days, and restoring an active subscription restores it. After 90 days an automated job permanently deletes leads, follow-ups, activity, campaigns, messages and support tickets. Your account, user logins and billing records are kept.

Passwords are hashed with bcrypt and never stored in plain text. New accounts must verify their email, sign-in attempts are rate-limited per email and per network address, and session tokens are stored only as SHA-256 hashes. Resetting a password signs the user out on every device.

The application runs on Vercel and the database is PostgreSQL hosted by Supabase. The full list of service providers is in the Privacy Policy.