Skip to content
Security and privacy

Customer data under control, from order to erasure

Basketly processes personal data from shop orders. That is why it encrypts it, limits access by role and erases it after a set time.

Team settings with roles and the retention period

Screenshots from a demo organisation. People and numbers are fictional.

What it looks like

Meta gets a hash, your team sees what it needs

Phone and e-mail are hashed before they leave the server. The role decides what shows on a person card, and the retention period keeps the CRM tidy by itself.

A hash instead of a number

Phone and e-mail are normalized and hashed with SHA-256. Meta only gets the hash in the last column.

The Viewer role

Without the right to edit clients, phone and e-mail are partly hidden and SMS texts are not shown.

Retention period

From 6 to 120 months, 24 by default. You can also erase a person at once, on request.

Background jobs without personal data

The job queue shows progress and errors but stores no personal data, so everyone on the team can see it.

Example data

Hashing and encryption

Each kind of data has its own protection, from the order to sending to Meta.

DataHow it is protected
E-mail and phone sent to MetaNormalized and hashed with SHA-256 before sending
Tokens, secrets and submission contentEncrypted with AES-256-GCM
Sessions in the appHttpOnly cookies and CSRF protection
Each organisation’s dataKept apart, access checked on every request
Personal data in automation runsEncrypted and erased after 30 days

Roles and masking

Four roles: owner, admin, operator and viewer. A viewer sees a masked phone and e-mail, and SMS text is hidden from them.

Person card with data shown according to role

Retention and erasure

Set the retention period from 6 to 120 months (24 by default). You can erase a person by hand on request, with a line in the log.

  1. 1

    You set the period

    From 6 to 120 months without activity, 24 by default.

  2. 2

    A clean-up every night

    People inactive for longer are erased together with their history.

  3. 3

    What is needed stays

    Event fingerprints without personal data, so the same conversion is never sent twice.

  4. 4

    Peace for those who asked

    The “Do not text” list stays, and unsent Meta events are cancelled.

Background jobs without personal data

The job queue shows progress and errors but stores no personal data, so every team member can see it.

Background jobs without personal data

Run it on your own server

Basketly is a single executable with a built-in database. On the Custom plan you can run it on your own infrastructure.

This page describes how the product works. It is not legal advice: agree the legal basis for processing and your consent wording with your lawyer.

Security and privacy

Frequently asked questions

Can’t find your question? Write to us

Not on its own. Hashing limits what reaches Meta, but you still need a legal basis and a privacy notice. Before a shop is connected, a segment is sent to Meta or an automation with texts is switched on, an admin confirms the legal basis.

Yes, on every plan, because we process your customers’ data. On the Custom plan the terms are negotiable. Write to us and we will send a draft.

Saved connections can no longer be decrypted and have to be reconnected. Keep the key in a secret manager and do not change it without a plan.

Get started in under 5 minutes

Connect your shop and Meta and see how many purchases really arrive.

  • Free up to 100 orders a month
  • No developer needed
  • Purchase balance and self-check